Decoder Programming

Open decoder configuration

Open the Locomotive Manager, edit the locomotive and choose Decoder Configuration. RailKernel uses the locomotive’s assigned command station and protocol to open the appropriate DCC or mfx screen. Decoder access is available only when the selected connected command station supports the required operation.

A complete DCC decoder read

For a recognised decoder family RailKernel presents the documented CVs with their meaning, decimal, hexadecimal and binary representation and read status. Bit fields such as CV29 are expanded so that direction, speed steps, analogue operation and address mode can be understood without manually decoding a byte. Read Selected CV reads one value; the complete scan reads all automatically readable documented CVs and reports unavailable values without inventing data.

Reading and writing CVs

Current values can be shown simultaneously as decimal, hexadecimal and binary. Entering a new value in any representation updates the others before writing. Decoder CVs directly control physical decoder behaviour, so RailKernel deliberately keeps reading, interpretation and writing visible rather than hiding them behind a generic setting.

• Read the current value before changing it.
• Write only documented values whose effect you understand.
• Use a clean programming track and remove other locomotives from it.
• After a write, verify the value and test the locomotive before returning it to automatic operation.

Changing a DCC address safely

Use Change Address instead of editing CV1, CV17, CV18 and CV29 separately. The guided operation first reads the decoder’s actual address mode and current address. You choose a short address from 1–127 or a long address from 128–10239. RailKernel then calculates the required values, changes the CVs in a safe order and reads them back through the address that should be active at each stage.

1. RailKernel reads CV29 and the relevant short or long address CVs from the decoder.
2. You select the target address type and enter the new address.
3. A confirmation shows the Short → Short, Short → Long, Long → Short or Long → Long transition and the CVs that will change.
4. RailKernel writes and verifies every stage. A Long → Long change temporarily uses a verified short address so the decoder remains reachable while CV17 and CV18 are replaced.
5. Only after successful read-back does RailKernel update the locomotive definition to the new active address.

If a write acknowledgement is missed because the decoder changes address immediately, RailKernel verifies the result at both the old and expected new address. If a later stage fails, the dialog reports the last address at which the decoder was proven reachable and RailKernel retains that address.

Reading an mfx decoder

For mfx locomotives RailKernel opens an mfx-specific overview. It shows the mfx address and UID and groups the decoder’s announced parameter blocks into root information, commands, inputs, function mapping, motor, outputs, sound and formats. Raw bytes remain visible beside interpreted values. A single parameter can also be read directly for focused investigation. Unlike a DCC address, the globally unique mfx UID is the stable decoder identity and normally requires no manual address programming.

When a read times out

A locomotive appearing in the CS3 roster does not prove that its decoder is currently answering; the station may be showing cached registration data. If an mfx or DCC read times out, first test the same read on the command station.

• Check track power, wheel contact and that the locomotive is on the track belonging to the selected command station.
• Close any decoder editor already open on the command station.
• Confirm that the locomotive can drive or operate a function before reading the decoder.
• If the command station also times out, restart its decoder session or the station before changing anything in RailKernel.