Troubleshooting: the app can't get data from my boat
SonarBuddy listens to your boat's instruments over Wi-Fi (NMEA 0183 over TCP). It never sends anything to them. Work through these in order.
1. Is the phone or iPad on the boat's Wi-Fi?
The phone must be on the same Wi-Fi network as the chartplotter or gateway: either the boat's router or the chartplotter's own Wi-Fi hotspot. A marina or shore Wi-Fi network will not reach your instruments.
Check: Settings → Wi-Fi shows the boat network. If the app reports that your phone's address is on a different network from the plotter's (for example the phone is 192.168.1.20 and the plotter is 10.10.10.190), you're on the wrong Wi-Fi network, or the plotter address is wrong.
2. Is "Local Network" access allowed?
iOS asks once: "SonarBuddy would like to find and connect to devices on your local network". If you tapped Don't Allow, the app can't see your instruments.
Fix: Settings → Privacy & Security → Local Network → turn SonarBuddy on. Then stop and start logging again.
3. Is the plotter sending NMEA 0183 over the network?
- B&G, Simrad, Lowrance: the chartplotter serves NMEA 0183 on port 10110. Use the chartplotter's IP address (on B&G this is shown under the network or Wi-Fi settings). If the connection is "refused", the plotter is reachable but not serving data on that port. Check that the plotter's network NMEA 0183 output is on. Menu names vary by model and software version.
- PredictWind DataHub: turn on its NMEA TCP output (Services → NMEA). The default is the DataHub's address (often 10.10.10.1) on port 11102.
- Raymarine and Garmin plotters don't send NMEA 0183 over Wi-Fi by themselves. You need a gateway, for example a DataHub, a Signal K server or a Wi-Fi NMEA gateway. Point SonarBuddy at the gateway's address and port.
What connection errors mean
- Connection refused: something answered at that address, but nothing is listening on that port. The port is wrong, or the NMEA output is off.
- Timed out / host unreachable / no route: nothing answered. The IP address is wrong, the device is off, or the phone is on a different network.
- Local network access denied (policy denied): see step 2.
- Closed by plotter: the plotter dropped the connection. Some plotters allow only a few NMEA clients at once; close other apps that are connected to it.
Connected, but no depth
- The sounder must be powered and the transducer in the water. Many sounders show no depth when the boat is out of the water or in very shallow water or aerated water.
- The depth must reach the plotter's network. If the plotter itself shows depth, it's usually forwarded too. If you use a gateway, check it sees depth (DPT or DBT sentences).
- If position arrives but depth doesn't, the problem is the depth source, not the app.
Connected, but no position
SonarBuddy needs the boat's GPS position (GGA or RMC sentences) as well as depth. Check the plotter has a GPS fix.
Logging stops when the screen is locked
- Allow location access Always (Settings → SonarBuddy → Location → Always). The app uses it to keep logging while locked; the blue location indicator shows it's on.
- Don't swipe SonarBuddy away in the app switcher; that stops logging.
- Low Power Mode can pause background work. Keep the phone charging on passage.
Uploads
Logs are saved on the phone and upload automatically when there's internet, including later at anchor or in port. The Uploads screen shows each file's status. "Waiting" just means there was no internet yet.
Signing in
- The code is in the email's subject line. Always use the newest email; older codes stop working once a new one is sent.
- Check the spam folder. You can request a new code after 60 seconds.
SonarBuddy is not a navigation aid. Depths are for "check this" information only.
← All help articles · Still stuck? Open Help in the app, or email mail@sonarbuddy.com.