AngusMcDoon
Well-known member
Of all the YAPPs I have produced over the years the most useful one I have found has been my anchor watcher. This links to the boat's data network to get a continuous update of depth, SOG, position, windspeed, heading and boat position (and later on, atmospheric pressure). Limits can be set on these values and if any reading goes beyond the limits an alarm sounds. Although chart plotters can usually provide this feature for position they are often not near where the skipper sleeps and use significant electrical power. The anchor watcher devices have all been low power and able to be moved around (albeit with a cable) to be positioned near the sleeping skipper's head.
The previous 3 incarnations, going back to 2013, have all been physical devices that get their boat data from a Seatalk 1 bus which I had at the time. The first had no user interface and had to be configured using an app on a laptop which was a bit of a kefuffle. I have no pictures of it but the original thread is here...
YAPP Low power Seatalk Anchor Watcher
The next one had its own display and buttons and could be configured from it's own user interface. The thread is here...
YAPP New Achor Watcher - with user interface
The pictures from the thread have gone but this is what it looked like...
Then the whole standalone anchor watcher disappeared and the same functionality was incorporated in a larger device that did a whole host of things. Atmospheric pressure was added at this point. The thread is here...
Return of the YAPP
and it looked like this...
That device lives on with the new owner of my old boat, but as I don't have it any more, it's time for a new one.
The previous incarnations all received their data from an old Seatalk 1 network. The new boat won't have that with the network being NMEA2000. I was going to make a device similar to the above with a NMEA2000 interface instead of Seatalk 1, but then had a change of plan. Rather than have a device I've made by my head when I sleep I instead will send the boat data out via Bluetooth and implement the anchor watching functionality in an Android app - as I'm likely to have my phone near me anyway. As this is a phone app, the project is a YappApp.
Getting the NMEA2000 boat data out via Bluetooth - that will use the same device that I send the same data via Bluetooth to OpenCPN - described in this dull thread that no-one is interested in here...
NMEA2000 to Bluetooth YAPP
Now to the Android app. I have to stay from the start that phone apps of any kind are not really my thing, and the language it's programmed in (Java) is new to me. Android apps are, I found out, one enormous bloated kerfuffle, so it's been a bit painful. Getting it to look nice (known as flower arranging by us hardcore low level types) is also not my thing, so it looks a bit functional rather than pretty. But here it is...
There's a big connect button for connecting to Bluetooth. The device has to have been previously paired. Once connected you can set your limits and also see the live data coming through. You can enable or disable any particular item. Once set up you press start which starts the watching and then looks like this...
The blue box at the bottom will show your anchor wanderings around but as I have no boat to test it on at the moment it's not showing anything. If an alarm goes off then a loud sound is made and an alarm dialog is shown...
An alarm also happens if the Bluetooth connection is lost or if any expected data doesn't arrive within the expected time. There's also a rearm time during which no repeat alarm will happen. This should be configurable but isn't yet. The app is shown running on a tablet but also runs on a phone as well. It will keep running even when the screen is off.
I've tested it on a 5 year old device and a 1 year old device and it works on both. It's a beta at the moment. It works on my test network with simulated data but hasn't been tested in real life yet.
It's built using Android Studio. It's open source and can be found under the app folder here...
GitHub - miniwinwm/BlueBridge
The previous 3 incarnations, going back to 2013, have all been physical devices that get their boat data from a Seatalk 1 bus which I had at the time. The first had no user interface and had to be configured using an app on a laptop which was a bit of a kefuffle. I have no pictures of it but the original thread is here...
YAPP Low power Seatalk Anchor Watcher
The next one had its own display and buttons and could be configured from it's own user interface. The thread is here...
YAPP New Achor Watcher - with user interface
The pictures from the thread have gone but this is what it looked like...
Then the whole standalone anchor watcher disappeared and the same functionality was incorporated in a larger device that did a whole host of things. Atmospheric pressure was added at this point. The thread is here...
Return of the YAPP
and it looked like this...
That device lives on with the new owner of my old boat, but as I don't have it any more, it's time for a new one.
The previous incarnations all received their data from an old Seatalk 1 network. The new boat won't have that with the network being NMEA2000. I was going to make a device similar to the above with a NMEA2000 interface instead of Seatalk 1, but then had a change of plan. Rather than have a device I've made by my head when I sleep I instead will send the boat data out via Bluetooth and implement the anchor watching functionality in an Android app - as I'm likely to have my phone near me anyway. As this is a phone app, the project is a YappApp.
Getting the NMEA2000 boat data out via Bluetooth - that will use the same device that I send the same data via Bluetooth to OpenCPN - described in this dull thread that no-one is interested in here...
NMEA2000 to Bluetooth YAPP
Now to the Android app. I have to stay from the start that phone apps of any kind are not really my thing, and the language it's programmed in (Java) is new to me. Android apps are, I found out, one enormous bloated kerfuffle, so it's been a bit painful. Getting it to look nice (known as flower arranging by us hardcore low level types) is also not my thing, so it looks a bit functional rather than pretty. But here it is...
There's a big connect button for connecting to Bluetooth. The device has to have been previously paired. Once connected you can set your limits and also see the live data coming through. You can enable or disable any particular item. Once set up you press start which starts the watching and then looks like this...
The blue box at the bottom will show your anchor wanderings around but as I have no boat to test it on at the moment it's not showing anything. If an alarm goes off then a loud sound is made and an alarm dialog is shown...
An alarm also happens if the Bluetooth connection is lost or if any expected data doesn't arrive within the expected time. There's also a rearm time during which no repeat alarm will happen. This should be configurable but isn't yet. The app is shown running on a tablet but also runs on a phone as well. It will keep running even when the screen is off.
I've tested it on a 5 year old device and a 1 year old device and it works on both. It's a beta at the moment. It works on my test network with simulated data but hasn't been tested in real life yet.
It's built using Android Studio. It's open source and can be found under the app folder here...
GitHub - miniwinwm/BlueBridge
Last edited: