Posts: 240
Threads: 45
Joined: Mar 2018
Reputation:
1
Hi,
I don't have temperature sensors on my arduino nano, but do have several on the pi.
Can temperature sensors, maybe by adding a signalK address, be added to Pypilot?
I'd like to assign a temperature sensor which is already added in i2c tab in openplotter, to the servo motor controller temperature.
Hope someone can help.
Kind regards,
Jamos
Posts: 2,355
Threads: 21
Joined: Jun 2016
Reputation:
75
Rudder feedback can be supplied via nmea0183, but so far not for motor temperature.
This could be supported as a sensor which could be received from one of several sources eventually. For now maybe you could set an alarm outside of pypilot which you will hear and you can shut the autopilot off.
Posts: 344
Threads: 5
Joined: Mar 2018
Reputation:
25
If you move forward with this would encapsulating Signal K data in NMEA0183 XDR sentences be feasible? Use Signal K paths as keys in XDR.
Adding support for this output format in Signal K server would be pretty simple.
It would provide a shared vocabulary to extend NMEA0183 and on the receiving end not require any additional connections.
Posts: 802
Threads: 46
Joined: Jun 2017
Reputation:
25
2019-08-16, 01:39 PM
(This post was last modified: 2019-08-16, 01:50 PM by jim321.)
the easy way
use node-red for alarm, relay, fan ect.
the linked item looks like its a stand alone device, set and forget.
Posts: 2,355
Threads: 21
Joined: Jun 2016
Reputation:
75
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.