Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Capacity remains at 0 with PGN 127505 #97

Open
macjl opened this issue May 19, 2024 · 0 comments
Open

Capacity remains at 0 with PGN 127505 #97

macjl opened this issue May 19, 2024 · 0 comments

Comments

@macjl
Copy link

macjl commented May 19, 2024

Hello,

I have a problem sending Fluid Data to N2k network. The currentLevel value seems Ok, but the capacity, or currentVolume sent is 0, even if it’s different in SignalK.

The data in SignalK are :

Path Value Units Timestamp Source
tanks.freshWater.2.capacity 0.16 m3 05/19 22:16:08 defaults
tanks.freshWater.2.currentLevel 1 ratio 05/19 22:58:33 N2kCan0.c032840050800042  (127505)
tanks.freshWater.2.currentVolume 0.16 m3 05/19 22:58:33 derived-data

But this is what is in signalk-to-nmea2000 logs :
May 19 20:52:51 2024-05-19T20:52:51.928Z signalk-to-nmea2000 tanks.freshWater.2.currentLevel,tanks.freshWater.2.capacity:1,
May 19 20:52:51 2024-05-19T20:52:51.929Z signalk-to-nmea2000 emit nmea2000JsonOut {"pgn":127505,"Instance":2,"Type":"Water","Level":100,"Capacity":0}

Is this a bug, or a misconfiguration at my side ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant