Sonar troubleshooting
Product will not start up (restart loop)
TroubleshootingSonarPossible causes |
Possible solutions |
|---|---|
Sonar disabled: |
Enable Ping from the Fishfinder app’s sounder tab: . |
Incorrect transducer selected: |
Check that the correct transducer is selected in the Fishfinder app’s Transducer tab: . |
Damaged cables: |
|
Damaged or fouled transducer: |
Check transducer condition, ensuring it is not damaged and is free from debris / fouling. If necessary, clean or replace the transducer. After cleaning or replacement, coat the transducer using a water-based anti-fouling paint. |
Wrong transducer fitted: |
Check product and transducer documentation, and ensure that the transducer is compatible with your system. |
External sonar module: SeaTalk HS / RayNet network problem: |
Check that the unit is correctly connected to the Display or network switch. Check all connections, ensuring connections are secure, clean and free from corrosion. Replace if necessary. |
External sonar module: Software mismatch between equipment may prevent communication: |
|
No depth reading / lost bottom lock
Possible causes |
Possible solutions |
|---|---|
Transducer location: |
Check that the transducer has been installed in accordance with the instructions provided with the transducer. |
Transducer angle: |
If the transducer angle is too great, the beam can miss the bottom. Adjust transducer angle and re-check. |
Transducer kicked-up: |
If the transducer has a kick-up mechanism, check that it has not kicked up due to hitting an object. |
Power source insufficient: |
With the product under load, using a multi-meter, check the power supply voltage as close to the unit as possible, to establish actual voltage when the current is flowing. (Check your product’s Technical specification for power supply requirements.) |
Damaged or fouled transducer: |
Check transducer condition, ensuring it is not damaged and is free from debris / fouling. If necessary, clean or replace your transducer. After cleaning or replacement, coat the transducer using a water-based anti-fouling paint. |
Damaged cables: |
|
Vessel speed too high: |
Slow vessel speed and re-check. |
Bottom too shallow or too deep: |
The bottom depth may be outside of the transducer’s depth range. Move vessel to shallower or deeper waters as relevant, and re-check. |
Ping depth limit set: |
If using a transducer with greater than 600 W power, check if the Ping depth limit has been enabled: . If you are in water deeper than the specified Ping depth limit, the transducer may not provide depth readings. Disable or adjust the setting, and then re-try. |
Poor / problematic image
Possible causes |
Possible solutions |
|---|---|
Targets will appear differently if your vessel is stationary (e.g.: fish will appear on the display as straight lines): |
Increase vessel speed. |
Scrolling paused or speed set too low: |
Un-pause or increase sonar scrolling speed. |
Sensitivity settings may be inappropriate for present conditions: |
Check and adjust sensitivity settings, or perform a Sonar reset. |
Damaged cables: |
|
Transducer location: |
|
Transducer kicked-up: |
If the transducer has a kick-up mechanism, check that it has not kicked up due to hitting an object. |
Damaged or fouled transducer: |
|
Damaged transducer cable: |
Check that the transducer cable and connection is free from damage, and that the connections are secure and free from corrosion. |
Turbulence around the transducer at higher speeds may affect transducer performance: |
Slow vessel speed and re-check. |
Interference from another transducer: |
|
Unit power supply fault: |
Check the voltage from the power supply, if this is too low it can affect the transmitting power of the unit. |
If you are experiencing issues with the fishfinder app scrolling image, you can record a video file of the issue that can be sent to Raymarine technical support for analysis. For details, refer to: Diagnostics sonar recording