2019-08-16, 02:06 PM
How would xdr encapsulate it?
Already sensors in pypilot can have different sources such as:
1) gpsd
2) arduino motor controller
3) nmea serial
4) nmea tcp
If the data is available from more than one source, the one with most priority (roughly that order) is taken.
So it would not be difficult to support nmea drive motor temperature at all, but the real question is, what nmea sentence and what format would be used?
It is also feasible to support additional possible 2 sources
1) signalk client - a client connects to pypilot and provides the data
2) signalk node server - pypilot is given the ip of a signalk node server from which to receive data
The first option is relatively easy but I don't see any use cases yet, unless it could be the node server which provides the data as a client. The second option I am not as sure how to deal with, but it would likely need additional info, like which keys it should subscribe for which host.
Already sensors in pypilot can have different sources such as:
1) gpsd
2) arduino motor controller
3) nmea serial
4) nmea tcp
If the data is available from more than one source, the one with most priority (roughly that order) is taken.
So it would not be difficult to support nmea drive motor temperature at all, but the real question is, what nmea sentence and what format would be used?
It is also feasible to support additional possible 2 sources
1) signalk client - a client connects to pypilot and provides the data
2) signalk node server - pypilot is given the ip of a signalk node server from which to receive data
The first option is relatively easy but I don't see any use cases yet, unless it could be the node server which provides the data as a client. The second option I am not as sure how to deal with, but it would likely need additional info, like which keys it should subscribe for which host.