How a device is addressed

A MUXEN device is a function — what kind of thing it is — and an instance — which one of them. The address is the two packed together:

address = function × 64 + instance

muxen-uds -d takes that address. -F and -I take the two halves separately, which is usually easier to read:

muxen-uds -i can0 -F 22 -I 0 readconfig     # function 22, instance 0
muxen-uds -i can0 -d 0x580  readconfig      # the same device

Instance numbers

Value	Meaning
0 – 62	a real instance, usable on the boat
63	the parking address: the box answers configuration but publishes nothing
255	the factory value, meaning never addressed; the box parks itself at 63

A box that has never been configured therefore answers a UID scan and nothing else. It has to be given an instance before it appears on the boat.

Addressing a box that has no instance yet

Find it by UID, then give it a number:

muxen-uds -i can0 uid --scan
muxen-uds -i can0 uid --uid <the-box-uid> --instance 0

Instance numbers are per function. Two devices of different functions may both be instance 0; two devices of the same function may not, and the second one to appear is the one that misbehaves.

On the Brain

The Brain publishes each device under device/<function>/<instance>/, so device/10/0/life is the first solar charger. A device with no usable instance publishes nothing at all.

Which functions each line publishes

Product line	Generic I/O (function 17)
CAN-CAN	yes, on every box of the line
CAN-MDV	none	publishes a remote battery switch (25) and a battery (5), not a generic I/O device
CAN-ENOCEAN	none	no relays, inputs or analog inputs on this board
BLOC 8 v2	none	publishes a power-output device (1); the outputs are the product, not spare I/O
CAN-SERIAL	yes, on every box of the line