2024-10-28, 12:23 AM
So I have a Raymarine S3G autohelm, I am trying to get track data to it from OpenCPN.
I have coming out of OpenCPN as UDP and being picked up by SignalK the following:
Oct 27 23:18:57 2024-10-27T23:18:57.967Z signalk-server:events:connection:OPENCPN:opencpnroute $IIGLL,5144.250765,N,00611.631883,W,233244,A*29
Oct 27 23:18:57 2024-10-27T23:18:57.975Z signalk-server:events:connection:OPENCPN:opencpnroute $IIVTG,146.000000,T,,M,5.000000N,,,A*55
Oct 27 23:18:57 2024-10-27T23:18:57.987Z signalk-server:events:connection:OPENCPN:opencpnroute $IIVHW,146.000000,T,,,5.000000,N*55
Oct 27 23:18:58 2024-10-27T23:18:58.050Z signalk-server:events:connection:OPENCPN:opencpnroute $ECAPB,A,A,0.000,R,N,V,V,185.167,T,,94.915,T,155.167,T*20
First thing I noted was that the APB sentence has a null value for field 10, Destination Waypoint ID ... I would have expected to see 002 (as that is my second waypoint ID) in there.
the S3G does not appear to pick up the heading data, I am unsure why, but I suspect it is because the S3G is expecting magnetic headings ... it has no clue what the local magnetic variation is as far as I know, so it would be unable to convert True to Magnetic ... I did try ticking the "Send magnetic headings in ECAPB sentence" checkbox in OpenCPN ... but, it still sends true .. even after a restart, again, I have no idea why.
I am unsure how I would get the Distance to waypoint data to the S3G, not that it really needs it if it has a heading to steer, but it would be nice to have ... I would have thought the only way SignalK could know the distance to run, eta etc would be if it came out of OpenCPN on its UDP port?
I have coming out of OpenCPN as UDP and being picked up by SignalK the following:
Oct 27 23:18:57 2024-10-27T23:18:57.967Z signalk-server:events:connection:OPENCPN:opencpnroute $IIGLL,5144.250765,N,00611.631883,W,233244,A*29
Oct 27 23:18:57 2024-10-27T23:18:57.975Z signalk-server:events:connection:OPENCPN:opencpnroute $IIVTG,146.000000,T,,M,5.000000N,,,A*55
Oct 27 23:18:57 2024-10-27T23:18:57.987Z signalk-server:events:connection:OPENCPN:opencpnroute $IIVHW,146.000000,T,,,5.000000,N*55
Oct 27 23:18:58 2024-10-27T23:18:58.050Z signalk-server:events:connection:OPENCPN:opencpnroute $ECAPB,A,A,0.000,R,N,V,V,185.167,T,,94.915,T,155.167,T*20
First thing I noted was that the APB sentence has a null value for field 10, Destination Waypoint ID ... I would have expected to see 002 (as that is my second waypoint ID) in there.
the S3G does not appear to pick up the heading data, I am unsure why, but I suspect it is because the S3G is expecting magnetic headings ... it has no clue what the local magnetic variation is as far as I know, so it would be unable to convert True to Magnetic ... I did try ticking the "Send magnetic headings in ECAPB sentence" checkbox in OpenCPN ... but, it still sends true .. even after a restart, again, I have no idea why.
I am unsure how I would get the Distance to waypoint data to the S3G, not that it really needs it if it has a heading to steer, but it would be nice to have ... I would have thought the only way SignalK could know the distance to run, eta etc would be if it came out of OpenCPN on its UDP port?