proprietary sentences?
What does SK do with proprietary sentences (or more generally, any data on the N2K network that doesn't fit into the schema)?
I am trying to help a friend interpret B&G rudder angle sensor data to make a more open autopilot for B&G boats. Apparently there are some proprietary sentences between the B&G angle sensor and the instruments, but the B&G sensors will not physically fit on his boat. B&G ignores PGN 127245 if it's not from a B&G sensor. I would like to install an SK RPI on his network and log data from the start to see if we can figure out what B&G expects and emulate it, but I don't have access to the boat or instruments so I can't just try it out.
3 Replies
SK ignores stuff that is not in canboat or not in n2k-signalk. You can log and review the raw data for messages that are not supported.
You can also enable logging on the n2k connections. This will log the raw data into a file that you can take away from the boat and analyse at will
You can also keep a manual log of sequences you do, to help in post analysis
This shouldn't be that difficult. It's mostly about identifying as a B&G device. You can see how to setup the device here: https://github.com/htool/signalk-naviop-plugin/blob/main/index.js#L182
Then, you can read rudder data from SignalK and send it out over the emulated device.