If you want to trigger when a pin is connected to ground then the gpio pin needs to be configured as pull up, otherwise it's always connected to ground internally. In this example there are 3 pins being used, when pin 26 is connected to ground it turns the LED on pin 16 on, then if pin 19 is connected to ground it turns the LED off again.
On openplotter V0.11.7 alpha.
![[Image: jaxYtit.png]](http://i.imgur.com/jaxYtit.png)
![[Image: 9CBBid0.png]](http://i.imgur.com/9CBBid0.png)
![[Image: u0aebhZ.png]](http://i.imgur.com/u0aebhZ.png)
Creating a waypoint in opencpn doesn't look so easy though:
From
https://opencpn.org/wiki/dokuwiki/doku.p..._sentences
Edit: Though digging deeper...
https://opencpn.org/flyspray/index.php?d...sk_id=1595
On openplotter V0.11.7 alpha.
Creating a waypoint in opencpn doesn't look so easy though:
From
https://opencpn.org/wiki/dokuwiki/doku.p..._sentences
Quote:xxWPL - Waypoint Location Used to send routes and waypoints up to a GPS receiver. OpenCPN does not process these sentences as input.
Edit: Though digging deeper...
https://opencpn.org/flyspray/index.php?d...sk_id=1595
Quote:I've just recently realised that, in theory, OCPN should read-in a WPL sentance in the context of APRS, and generate a specific AIS target. If this is the case, the contextual menu (right click on the AIS target/target query) should offer the possibility of creating a waypoint.Actually creating the nmea sentence might be a job better suited to node-red - quite easy to get at the signalk data, or anyone know how to do that as bash?