Error Messages
error-code E1
A short circuit on the programming track has occured. Please
make sure that the loco is not derailed and that there’s no fault in
the wiring of the programming track.
A newly converted loco may have a faulty wired decoder.
error-code E2
Trying to read the decoder didn’t have a result because the loco
didn’t answer.
Please make sure that the loco is not derailed and that there’s no
fault in the wiring of the programming track.
A newly converted loco may have a faulty wired decoder.
error-code E3
the result of reading a decoder is higher than 99 and therefore the
Lokmaus®2 can’t display it on their 2-digits display. It can display
values from 00 to 99. If the result is higher then you get this er-
ror-message.
error code E6
The actual RocoNet address of the Lokmaus®2 is already in use.
After this error message the Lokmaus®2 automatically starts to
search for a new free device-address. If you have disabled the au-
toconfiguration you must correct the device address yourself.
How to change the device-address you can read on page 28.
error code E7
The actual RocoNet address of the Lokmaus®2 is not addressed.
This error message may occur because you added more devices
to the system than defined in the menu C8.
How you raise the number of devices you read on page 29.
This error message can also appear in the moment that you plug
the Lokmaus®2 to the system very slowly. The data transmission
is connected later than the power supply of the Lokmaus®2.
This error is corrected automatically after a short time.
error code E8
A data communication error in the RocoNet has happened. If the
system doesn’t continue after this error message please unplug
the amplifier from the transformer and re-plug it.
error code E9
The Lokmaus®2 has received an unknown command or the data
transmission was disturbed. This error message also occurs if you
try to read a decoder but the Lokmaus®2 is plugged to an amplifier
(e.g. the amplifier 10761) that doesn’t support this feature.
By pressing ‘STOP’ you release this error message.
32
