Hans

The source id should match as well. 0 in this case. Do you see the device show up in the device list?

There's also the commissioning part that needs to happen. I've only upgraded to SignalK v2 yesterday and I see it still works as is. But, I'll look into moving it:...

The idea is that SignalK is the middleware and the v2 api can be the way commands can be sent/received.

The pi bit is irrelevant. As long as it runs nodejs and has a can0 interface, it should work quite easily. On my boat it ran on a RPi 3b+...

I have the same MFD, so that shouldn't be the problem. What does the script show when you run it from the command line?

``` {"B&G: User and Remote rename", 130833, PACKET_INCOMPLETE | PACKET_FAST, {COMPANY(381), LOOKUP_FIELDTYPE_FIELD("Key", 12, BANDG_KEY_VALUE), SIMPLE_DESC_FIELD("Length", 4, "Length of field 8"), MATCH_FIELD("Command unknown", BYTES(3), 65534, "0x00fffe"), STRING_FIX_FIELD("Short name", BYTES(8)), STRINGVAR_FIELD("Long name"),...

Another detail: the 'fe' field can set the number of decimals to display from 0x0 0 to 0x4 to 4. I played around with the nearby 00 and ff to...

@FarFarSouth wrote: > Hi Hans, > > I have been using pgn 130824 & 130833 combination with success. Below is the chunk of the C# code used to build 130833....

> No. I haven't found a way to display the units. BTW... which are the key codes for the User 1-32 custom fields? Have you tried to handle them like...

Agreed. I first tried to fix it further upstream, but that made some tests fail where Date is use to tell age of certain info. Hence the somewhat suboptimal re-parsing...