Posts: 11
Threads: 2
Joined: Nov 2024
Reputation:
0
2024-11-20, 09:11 PM
(This post was last modified: 2024-11-21, 05:06 PM by skybolt.)
I hope this is the correct place and sorry for resurrecting this older thread.
But regarding the Signal K to NMEA 2000 plugin of Signal K, I have two batteries that come from Victron Smart Shunts and they are in signal k with paths of:
Signal K path
self.electrical.batteries.prtSmartShunt.(parameter name)
self.electrical.batteries.stbSmartShunt.(parameter name)
Source path
(venus.com.victronenergy.battery.288)
(venus.com.victronenergy.battery.289)
I am trying to get them into PGN127508 Battery Status, in instances 1 and 2. The path is displaying fine in Signal k instruments with all of the parameters populated.
I have tried those names and all perennation of them I can think of, along with port starboard and a few others. Nothing i use seems to work. No PGN127508 is being published on the N2K bus. I am checking with Actisense Reader and an NGT-1.
What are the names needed to be used for the batteries?
Posts: 212
Threads: 16
Joined: Nov 2020
Reputation:
22
If i remember correctly, that will just be
prtSmartShunt
&
stbSmartShunt
Posts: 11
Threads: 2
Joined: Nov 2024
Reputation:
0
I went that route and still no output of PGN's 127508. So I added in the Venus plugin and created new names of PRTBattery and STBBattery but still do not see any output attempts in the log.
I am using a YachDevices YDNR-02 as my interface for Signal K, is it possible that there is an issue emitting the output?
If I turn on the ve.can to N2K in the venus os then see the packets attempting to be emitted, but do not see them on the N2K bus. But I shouldn't have to have that on right? As there are valid paths in SK that hold the correct values.
Sorry very confused on this one.
Posts: 366
Threads: 6
Joined: Mar 2018
Reputation:
31
Activate sebug logging for the plugin to see in server log its output.
Should be just configuring battery instances like they are in the path after batteries and activating the pgn.
Posts: 11
Threads: 2
Joined: Nov 2024
Reputation:
0
Got to the boat and tried the debugging out, guess I have another issue because it's looks like it is being emitted but it is not on the N2K bus. So I must have a bigger issue going on.
Posts: 8
Threads: 2
Joined: Jul 2024
Reputation:
0
2025-07-01, 08:37 PM
(This post was last modified: 2025-07-01, 08:39 PM by wellsy.)
Similar topic on plugin sk to n2k plugin
My wind instrument (nasa marine 5wire) outputs the wind direction in +/- rads off the bow. Open plotter correctly interprets this but when the plugin converts it to 0-360 degrees format for NMEA 2000 it is outputting a negative number eg -90 degrees
When this data is picked up by my B&G chart plotter the wind direction is flipped by 180 degrees.
Here is the debug log for the plugin:
Jun 10 16:20:54 2025-06-10T15:20:54.605Z signalk-to-nmea2000 environment.wind.angleApparent,environment.wind.speedApparent:-0.349065850478568,3.446778650961703
Jun 10 16:20:54 2025-06-10T15:20:54.606Z signalk-to-nmea2000 emit nmea2000JsonOut {"pgn":130306,"Wind Speed":3.446778650961703,"Wind Angle":5.934119456701018,"Reference":2}
I have posted this on the plugin GitHub but no response. ChatGPT suggests all sorts of mods including using node red and data fiddler but I think the data fiddler on openmarine on RP5 is not the full version.
Grateful for any suggestions to resolve.
John
Posts: 212
Threads: 16
Joined: Nov 2020
Reputation:
22
If you want to fix that quickly, just send the value through node red and flip it back. Have you done any node-red work before?
