This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Signal K naming question for LPG warning system
#1
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/d...ranch.html Do I simply assign the sensor as/ vessels/<RegExp>/sensors/<RegExp>/name for instance /vessels/sensors/LPG/Pentry? 


/Ranur
Reply
#2
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/d...ranch.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/...fuelregexp

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
Reply
#3
(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/d...ranch.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/...fuelregexp

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.
Reply
#4
(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/...tions.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.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)