This article explains why your Deeper Quest or Deeper Spark sonar may not start scanning or may stop during use, and provides clear steps to restore normal operation.
Common Causes
Dirty or obstructed water sensors. The most common cause. If sensors do not detect water, scanning will not start or may stop randomly.
Air bubble on sensors (first use in water). An air pocket between the sensors and water can prevent activation.
Weak or lost connection. Connection issues may pause sonar operation.
Incorrect sonar settings. Certain beam angles may produce inaccurate readings in specific conditions.
Step-by-Step Troubleshooting
1. Remove Air Bubble (First Use in Water)
When placing the Quest or Spark in water for the first time, an air bubble may form around the water sensors.
Drive the boat manually for a short distance.
This helps remove the air bubble and allows sensors to detect water.
2. Inspect and Clean Water Sensors
For Deeper Quest:
Using the special tool from the green tool bag, that is located inside the Deeper Quest backpack, remove the weed guard, that is located on the Deeper Quest's side, where the charging port is located.
Use a sponge and some WD-40 or alcohol to clean up these metal contacts until they're clean and shiny.
For Deeper Spark:
Inspect the water sensors directly.
Use a sponge and some WD-40 or alcohol to clean up these metal contacts until they're clean and shiny.
3. Verify Connection Stability
Maintain a stable connection between your smartphone/controller and the Quest or Spark.
If sonar scan lags or freezes, try these tips to improve the connection: click here
4. Adjust Sonar Settings (If Depth Is Incorrect)
If the sonar shows incorrect depth (e.g., much deeper than actual):
Switch to the narrow beam (7°) for more accurate readings.
In shallow water below 5 m (16 ft) with a soft bottom, the 20° beam may produce inaccurate depth readings. Avoid using it in such conditions.
When to Contact Support
Contact support@deeper.eu if:
Sonar does not start scanning after all steps.
Scanning stops repeatedly despite clean water sensors and stable connection.
Depth readings remain consistently incorrect.