Commissioning

Order matters here: the gateway builds its list of paired switches when it starts, so every pairing change ends with a restart.

Everything below is run on the boat's Brain.

1. Wire it and check it lives

CAN 1 to the MUXEN bus, CAN 2 to the Scheiber bus, power on. The system LED must blink once a second. Anything else: see Common mistakes.

2. Find it on the bus

muxen-uds -i can0 uid --scan

A factory box has no instance number yet (InstanceNum = 255) and publishes nothing until it gets one. This scan finds it anyway.

3. Give it its identities

The gateway is two MUXEN devices, and both need an instance number:

Device	Function	What it is
SFSP receptor	22	the Scheiber bridge — the important one
Generic I/O	17	the relays and inputs of the box itself

A box that has never been configured is addressed by its UID, not by its instance. The UID comes from the scan above:

# the Scheiber bridge, here instance 0
muxen-uds -i can0 uid --uid <the-box-uid> --instance 0 --preferred-function-code 22

# the box's own I/O, here instance 4
muxen-uds -i can0 uid --uid <the-box-uid> --instance 4 --preferred-function-code 17

--preferred-function-code is not optional here: this box answers on two functions, and without it the tool does not know which of the two you are numbering.

Instance numbers run 0…62 and must be unique per function on the boat. Do this one box at a time — two unconfigured boxes on the bus at once collide on the parking address.

4. Check the Scheiber side is alive

The lighting blocks are found on their own. Within a few seconds of powering the Scheiber bus, each block appears as a MUXEN lighting device:

mosquitto_sub -h 127.0.0.1 -t 'device/8/#' -v      # lighting blocks
mosquitto_sub -h 127.0.0.1 -t 'device/22/#' -v     # the bridge itself

If the bridge publishes and no lighting block appears, either the installation has none, or the Scheiber bus is not reaching the gateway.

5. Pair the switches

A switch is paired by writing its identifier into one of 63 slots, SfspInter0 … SfspInter62. The slot number becomes the instance number of the MUXEN switch: the switch written into SfspInter5 appears on the boat as switch instance 5. Pick the slots deliberately — they are the numbering the rest of the boat will use.

Watch the bridge while you press:

mosquitto_sub -h 127.0.0.1 -t 'device/22/<instance>/state' -v

Press a button on the switch you want to pair. The gateway reports the identifier of any switch it does not recognise:

device/22/0/state {"UnknowInterId":305419896,...}

Write that number into the slot you chose, and restart the box:

muxen-uds -i can0 -F 22 -I 0 writeconfig --name SfspInter5 --value 305419896 --reboot

Repeat for each switch. After the restart, pressing that switch publishes on device/23/5/life — a MUXEN switch, ready to be assigned to anything.

A switch already paired stays silent on the state topic — that topic only reports unknown switches. To re-read the identifier of a switch that is already paired, turn on the "report every switch" mode first:

muxen-uds -i can0 -F 22 -I 0 routine --action 1 --routine 2 --payload 01   # on
muxen-uds -i can0 -F 22 -I 0 routine --action 1 --routine 2 --payload 00   # off

The mode is not saved: it is off again after a restart.

6. Check the count

The bridge publishes how many switches it has loaded:

mosquitto_sub -h 127.0.0.1 -t 'device/22/<instance>/life' -v

NbEmulatedInter must equal the number of slots you filled. If it is lower, a slot did not save, or the box has not been restarted since.

7. Keep a copy

muxen-uds -i can0 -F 22 -I 0 readconfig --save-as-csv scheiber-pairing.csv

The pairing is the only thing in this installation that cannot be recovered from the equipment itself. A factory reset erases it, and re-pairing means walking the boat pressing every switch again.