+- OpenMarine (https://forum.openmarine.net)
+-- Forum: OpenPlotter (https://forum.openmarine.net/forumdisplay.php?fid=1)
+--- Forum: How do I...? (https://forum.openmarine.net/forumdisplay.php?fid=3)
+--- Thread: Signal K naming question for LPG warning system (/showthread.php?tid=2406)
Signal K naming question for LPG warning system - Ranur - 2020-03-08
Hi guys. Rather than lashing out a fortune for a LPG sensing system, I want to add a couple of MQ6 sensors to my OP installation and connect them through SigKsens via an ESP8266. My plan is to get a notification and and an alarm through Node Red/Watchdog if gas level exceeds a certain level. Here to the newbie question: As I understand it Signal K has a loong list of predefined http://signalk.org/specification/1.0.0/doc/vesselsBranch.html Do I simply assign the sensor as/ vessels/<RegExp>/sensors/<RegExp>/name for instance /vessels/sensors/LPG/Pentry?
/Ranur
RE: Signal K naming question for LPG warning system - tkurki - 2020-03-10
Quote:Hi guys. Rather than lashing out a fortune for a LPG sensing system, I want to add a couple of MQ6 sensors to my OP installation and connect them through SigKsens via an ESP8266. My plan is to get a notification and and an alarm through Node Red/Watchdog if gas level exceeds a certain level. Here to the newbie question: As I understand it Signal K has a loong list of predefined http://signalk.org/specification/1.0.0/doc/vesselsBranch.html Do I simply assign the sensor as/ vessels/<RegExp>/sensors/<RegExp>/name for instance /vessels/sensors/LPG/Pentry?
All the data you ever get is coming from sensor of one kind or another - that does not add anything of value to the path, so don't put it there.
See https://signalk.org/specification/1.4.0/doc/vesselsBranch.html#vesselsregexptanksfuelregexp
so
/vessels/<RegExp>/tanks/fuel/<RegExp>/type should be 'lpg'
and then use paths like
/vessels/<RegExp>/tanks/fuel/<RegExp>/pressure
/vessels/<RegExp>/tanks/fuel/<RegExp>/currentLevel
RE: Signal K naming question for LPG warning system - Ranur - 2020-03-10
(2020-03-10, 08:23 PM)tkurki Wrote:Quote:Hi guys. Rather than lashing out a fortune for a LPG sensing system, I want to add a couple of MQ6 sensors to my OP installation and connect them through SigKsens via an ESP8266. My plan is to get a notification and and an alarm through Node Red/Watchdog if gas level exceeds a certain level. Here to the newbie question: As I understand it Signal K has a loong list of predefined http://signalk.org/specification/1.0.0/doc/vesselsBranch.html Do I simply assign the sensor as/ vessels/<RegExp>/sensors/<RegExp>/name for instance /vessels/sensors/LPG/Pentry?
All the data you ever get is coming from sensor of one kind or another - that does not add anything of value to the path, so don't put it there.
See https://signalk.org/specification/1.4.0/doc/vesselsBranch.html#vesselsregexptanksfuelregexp
so
/vessels/<RegExp>/tanks/fuel/<RegExp>/type should be 'lpg'
and then use paths like
/vessels/<RegExp>/tanks/fuel/<RegExp>/pressure
/vessels/<RegExp>/tanks/fuel/<RegExp>/currentLevel
As usual - I guess my lack of competence shine through in my inability to clearly state the purpose, but I am using a "sniffer", a MQ-6 sensor to see if there is a gas leak. In order to get visual and audio alarm, I'd like to convert the value from this into SignalK. It is in other words not a matter of Lpg level.
RE: Signal K naming question for LPG warning system - tkurki - 2020-03-11
(2020-03-10, 09:17 PM)Ranur Wrote:(2020-03-10, 08:23 PM)tkurki Wrote: /vessels/<RegExp>/tanks/fuel/<RegExp>/pressure
/vessels/<RegExp>/tanks/fuel/<RegExp>/currentLevel
As usual - I guess my lack of competence shine through in my inability to clearly state the purpose, but I am using a "sniffer", a MQ-6 sensor to see if there is a gas leak. In order to get visual and audio alarm, I'd like to convert the value from this into SignalK. It is in other words not a matter of Lpg level.
That would then be under /notifications, for example /sound notifications/tanks/fuel/<tankid>. The fact that this is lpg related would just go to the message.
See https://signalk.org/specification/1.4.0/doc/notifications.html
We could also add a notifications.leak well known path to the specification.
To be honest I am not entirely happy with this, I don't think we did a particularly good job in fleshing out the notification mechanism, but per 1.0 this is how it would be.