2021-03-05, 08:22 AM
(This post was last modified: 2021-03-05, 08:39 AM by richarddaneel.)
(2021-03-04, 08:04 PM)ironman Wrote:(2021-03-03, 07:27 PM)richarddaneel Wrote: Please help me as I have done this but can not get pypilot to detect the gps.
(2021-03-03, 10:28 PM)seandepagnier Wrote: I'm not sure why pypilot is unable to directly receive the gps data from signalk though.
The zeroconf mechanism, through which pypilot (almost) automatically connects to a signalk database, only works when signalk's server setting 'mdns' is switched 'on', which it does not seem to be by default. If that is switched on, you will find an Access Request under the signalk Security menu, which you have to approve. Mind you, many setting changes in signalk require a restart to become effective.
Hi Ironman
Thanks for the reply. The 'mdns' was off and changed it but there is no Access Request under Security menu even after restart. Ironman, if I go to signalk-server:events:nmea0183 debug window I can see the gps sentences are there but somehow pypilot does not see them, any help appreciated
Richard
(2021-03-05, 03:51 AM)seandepagnier Wrote:(2021-03-04, 09:25 AM)richarddaneel Wrote: Hi Sean
Thanks for the reply. One problem could be the data transfer. As you can see in the picture the OUT sentences (port 20220) are all in red. Not sure why but I have tried various versions and they are all the same so I think they are not valid. This is a fresh install of Raspbian on a RPi4 with only OpenCPN installed so no Openplotter and no SignalK to mix things up. However, the Pypilot plugin still does not receive the data, any ideas will be appreciated.
Richard
I am not completely sure, but is pypilot actually running on 127.0.0.1?
What if you try to connect with "telnet localhost 20220" ?
Hi Sean, Thanks for the reply. As you can see in the picture if I follow your previous suggestion and "output this data as a nmea repeater or autopilot route" checkbox in opencpn then I get the sentences sent in blue. However, if I change the host to localhost on TCP port 20220 there is still no recognition by pypilot and the output messages are still in red and, thus, not valid.