I've digged a little more into the problem.
If i connect gps + wind directly to pypilot (attribution in "serial" tab of openplotter), Pypilot forward nmea gps to 20220 but not wind. But in pypilot client, gps source is set to none (and wind too), and i was unable to activate gps.
If I connect only gps on serial, it's not forwarded.
If I try to forward nmea (output) on kplex on port 20220, pypilot doesn't seem to receive data (even if wind has added checksum).
If I forward from node-red wind packet adding checksum to pypilot (on 20220), it work, i've the wind data on pypilot and I can use it !
So i do a node-red configuration outputing both on pypilot and on kplex (so I can debug easily).
I add gps on node-red.
I've digged a little more into the problem.
If i connect gps + wind directly to pypilot (attribution in "serial" tab of openplotter), Pypilot forward nmea gps to 20220 but not wind. But in pypilot client, gps source is set to none (and wind too), and i was unable to activate gps.
If I connect only gps on serial, it's not forwarded.
If I try to forward nmea (output) on kplex on port 20220, pypilot doesn't seem to receive data (even if wind has added checksum).
If I forward from node-red wind packet adding checksum to pypilot (on 20220), it work, i've the wind data on pypilot and I can use it !
So i do a node-red configuration outputing both on pypilot and on kplex (so I can debug easily).
I add gps on node-red.
Finally, i get this configuration:
![[Image: node_red.png]](https://khetzal.info/files/priv/pypilot/node_red.png)
I listen on 40440 for kplex output and I connect to 127.0.0.1 20220 for pypilot output.
On kplex, i see that i've all my data (gps + wind).
On pypilot, wind.source is tcp, but gps.source still to none.
Since it's an usb gps mouse, and i've a lowrance elite 5 ti, i will try with the lowrance as source to see if it's the same.
Moreover, i don't know if it's important or not, but i've found somewhere in your code a typo (not sure but i think), MVW insead of MWV:
![[Image: mvw.png]](https://khetzal.info/files/priv/pypilot/mvw.png)
If i connect gps + wind directly to pypilot (attribution in "serial" tab of openplotter), Pypilot forward nmea gps to 20220 but not wind. But in pypilot client, gps source is set to none (and wind too), and i was unable to activate gps.
If I connect only gps on serial, it's not forwarded.
If I try to forward nmea (output) on kplex on port 20220, pypilot doesn't seem to receive data (even if wind has added checksum).
If I forward from node-red wind packet adding checksum to pypilot (on 20220), it work, i've the wind data on pypilot and I can use it !
So i do a node-red configuration outputing both on pypilot and on kplex (so I can debug easily).
I add gps on node-red.
I've digged a little more into the problem.
If i connect gps + wind directly to pypilot (attribution in "serial" tab of openplotter), Pypilot forward nmea gps to 20220 but not wind. But in pypilot client, gps source is set to none (and wind too), and i was unable to activate gps.
If I connect only gps on serial, it's not forwarded.
If I try to forward nmea (output) on kplex on port 20220, pypilot doesn't seem to receive data (even if wind has added checksum).
If I forward from node-red wind packet adding checksum to pypilot (on 20220), it work, i've the wind data on pypilot and I can use it !
So i do a node-red configuration outputing both on pypilot and on kplex (so I can debug easily).
I add gps on node-red.
Finally, i get this configuration:
I listen on 40440 for kplex output and I connect to 127.0.0.1 20220 for pypilot output.
On kplex, i see that i've all my data (gps + wind).
On pypilot, wind.source is tcp, but gps.source still to none.
Since it's an usb gps mouse, and i've a lowrance elite 5 ti, i will try with the lowrance as source to see if it's the same.
Moreover, i don't know if it's important or not, but i've found somewhere in your code a typo (not sure but i think), MVW insead of MWV: