Gemini Profiling System
0695-SOM-00001, Issue: 03
59
© Tritech International Ltd.
Troubleshooting
The software reports that no sonars are detected
VDSL System
– Check all cabling between Gemini Hub and the sonar and verify that
the sonar is powered correctly with appropriate voltage at the sonar. If the VDSL
cables are OK and the sonar is operational and the problem will be either the network
connection between Gemini Hub and the PC or the network configuration on the PC.
Note
It may take up to 1 minute to establish a stable VDSL link.
Ethernet System
– 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 -
for Ethernet systems this needs to be a cable of at least Cat5e standard. If the sonar
has successfully established a link then the problem will be with the network settings
on the PC.
Note
Ethernet connection requires Cat5e cable for the entire cable run (max
80m) – lengths of untwisted cable must be kept to an absolute minimum.
All Systems
– Some firewalls have been known to cause this issue. Contact the
network administrator for advice if the sonar is connected to a network where
disabling the firewall would present a security risk.
Note
If a fault with the Gemini Hub is suspected the sonar head should be
connected directly to the computer using an optional Gemini Ethernet/
VDSL adapter and bench test cable. Contact
Tritech International Ltd
for
more details.
Sonar is present but will not ping
VDSL System
– Check the reported link speed – it must be greater than 10Mbit·s
-1
downstream to function correctly. If it is less than this then the cable run is either too
long or the VDSL twisted pair is of poor quality.
All Systems
– Check your network settings on the PC. Typing
route print
from
the command line will show the PC routing table. The sonar and PC must be on the
