2020-09-27, 08:14 PM
I have a simple setup with ocpn on pc with rpi running OP V2. OP signalk only receives opencpndata via UDP and forwards it to the AP via a 0183 serial usb.
After a slightly troublesome connection problem, it now works. However, if I set the AP to track mode, using an Opencpn route that I want to follow. It accepts the command but very quite triggers a large XTE alarm. If I zero it on opcpn, it's ok for a bit but soon returns. Looking at the data, I am curious, as the signalk data checker shows the XTE in meters, but the Raymarine display shows the same numbers, but as NM hence the error. So if the XTE is 0.01Nm, the same data is 185m on signalk but 1.85nm on the Raymarine display. The next number is 370m for 0.02. etc
If I connect the usb output directly to the pc and Opencpn, it's fine so OP is doing something strange.
Any help?
After a slightly troublesome connection problem, it now works. However, if I set the AP to track mode, using an Opencpn route that I want to follow. It accepts the command but very quite triggers a large XTE alarm. If I zero it on opcpn, it's ok for a bit but soon returns. Looking at the data, I am curious, as the signalk data checker shows the XTE in meters, but the Raymarine display shows the same numbers, but as NM hence the error. So if the XTE is 0.01Nm, the same data is 185m on signalk but 1.85nm on the Raymarine display. The next number is 370m for 0.02. etc
If I connect the usb output directly to the pc and Opencpn, it's fine so OP is doing something strange.
Any help?