Eclipse 3D Imaging Sonar
Document: 0690-SOM-00001, Issue: 01
40
© Tritech International Ltd.
6. Troubleshooting
The software reports that no sonars are detected
Check all cabling to the sonar and verify that it is powered correctly with appropriate
voltage at the sonar. Also check that the correct cable is in use - this needs to be a
cable of at least Cat5e standard.
If the Eclipse is connected and powered through a vehicle Ethernet infrastructure it
may be helpful to isolate it from the vehicle and connect directly to the Eclipse SPU.
Use the 10m test cable and bench PSU to make a direct connection to the Eclipse.
Make sure that the Eclipse is connected to the correct network interface on the rear
of the SPU (i.e.
do not
use the motherboard connector).
Note
Ethernet connection requires Cat5e cable for the entire cable run (max
80m) and any lengths of untwisted cable must be kept to an absolute
minimum.
Sonar goes offline while operating on deck
The sonar head outputs heat to the body casing (using it as a heatsink) which is
dissipated to the surrounding water during normal operation.
In order to protect the internal electronics from damage due to overheating a thermal
cut-off will shut down the sonar if it gets too warm. It will be necessary to allow the
unit to cool down before it will operate again.
The unit should not be operated out of water for extended periods.
Update rate is slow and there are sometimes large gaps
between pings
There may be noise induced onto the Ethernet cables, be sure to route these as far
away as practicable from noise sources.
