ZIMO MX1, MX1EC, MX1HS Instruction Manual

COMMAND STATION MX1, MX1HS, MX1EC Page 1

INSTRUCTION MANUAL

STANDARD HIGH OUTPUT ECONOMY

MX1 MX1HS MX1EC

Chapter

1. Introduction......................................................................................................................................................................2

2. Overview..........................................................................................................................................................................2

3. Specifications ..................................................................................................................................................................2

4. Power supply – external transformer...............................................................................................................................4

5. Connecting cabs (throttles)..............................................................................................................................................4

6. Connecting the main and programming track..................................................................................................................4

7. Controls and applications................................................................................................................................................5

8. The DIP switches (back of MX1).....................................................................................................................................6

9. The auxiliary inputs (shuttle, AOS… )..............................................................................................................................7

10. The CONTROL bus (booster connection)......................................................................................................................8

11. The Configuration Variables..........................................................................................................................................9

12. MX1HS as Booster-Unit...............................................................................................................................................11

13. Fuses...........................................................................................................................................................................11

14. SOFTWARE Update....................................................................................................................................................12

15. The software ZST (ZIMO Service Tool).......................................................................................................................12

16. AOS – Automatic Operating Sequences......................................................................................................................13

17. The “old” (ASCII-oriented) Interface.............................................................................................................................15

18. The “new” binary Interface Protocol.............................................................................................................................18

IMPORTANT NOTES to SOFTWARE and SOFTWARE UPDATES:
Software that determines the characteristics and functions of this product is stored in a FLASH-

EPROM.
Current software is available at no charge from www.zimo.at (UPDATES). The software can be in-

stalled with the help of the program “ZST” (Zimo Service Tool) but also at the DOS level with the
program LOADHEX. The ZST program is available for download from the above web site at no
charge.

Updates can also be performed by exchanging the EPROM with a new one from ZIMO for a mini­mum charge of EUR 10.00 to EUR 15.00 (handling and burning of the chip). An additional EUR

10.00 will be charged if the old EPROM is not sent back. More information at:
Some functions may depend on the software level of other components. It is therefore recommended

to use matching software in the different ZIMO components.
ZIMO cannot guarantee that future functions (including the ones covered in this manual) will be im-

plemented as planned or in the time frame suggested.

NEW manual format November 2006, SW-Version 3.00 ----- 2006 11 05

EDITION

Old editions (old format) ----- to 2006 04 11

www.zimo.at .

Page 2 COMMAND STATION MX1, MX1HS, MX1EC

1. Introduction

The command station is the central processing unit of a DCC system (according to NMRA definition it
is a combination of “command control station” and “power station”).

The command station uses the CAN bus cable to communicate with the cabs and if applicable with
accessory modules, track section modules and other modules.

The command station sends stabilized and short circuit protected power to the track, which also in­cludes the control information for locomotive and accessory decoders in the standardized NMRA­DCC format, the MOTOROLA data format or both (see below).

Control information and data formats . . .

“Data format” indicates the kind of data transmission used to send information from control units (command sta­tions, cabs…) to mobile decoders in locomotives or fixed decoders for switches or signals. The following data for­mats are relevant:

DCC (Digital Command Control): this is a data format standardized by the NMRA (National Model Railroad Asso-

ciation) and is also used by DCC systems and decoders of other manufacturers like Lenz, ROCO, LGB, Digitrax,
NCE and others.

MOTOROLA: A data format used by Märklin under the name “Märklin digital”, “Delta” as well as Märklin's own

new “mfx”. All recently produced Märklin locomotives come with an appropriate decoder installed. Decoders operat­ing with the MOTOROLA format can be controlled with a ZIMO system and if required simultaneously with DCC de­coders.

Each data format can be selected with switches marked „DCC“ and "MOT" on the back side of the
command station. The version MX1EC is equipped with jumpers instead of switches. All command
stations are delivered with the DCC mode enabled and the MOT disabled.

It is recommended to enable only the data format that is actually being used! This improves the data
flow to the track: data for each engine is sent faster and repeated more often. Disabling the DCC
format in a MOTOROLA only set-up simplifies the handling and control: locomotive and turnout ad­dresses can be entered in the cab without a prefix.

2. Overview

The command station is available in 3 versions..

Up to 8A of track power; separate outputs for main and programming track

MX1

The

standard com-

mand station

MX1HS

The

high

output command

station

MX1EC

The

economy com-

mand station

(may be part of layout). 2 CAN bus sockets, RS232 interface, 8 inputs for
automated shuttle operations, AOS events, external panic button, 4-pin
control bus socket for the control and feedback of external boosters (other
brands are also suitable). 2-line LCD display (2 x 16 characters) for the dis­play of volt and amp readings for both track outputs as well as CAN bus ac­tivity, error messages, programming and AOS information and more.

Up to 2 x 8A of track power at two equal track outputs, independently ad­justable track voltage, parallel connection of both track outputs is possible
(16A); one output may serve as programming track. Otherwise identical to
MX1 with the same software; configurable with jumpers for the use as a
large booster MXBOO (as slave unit of another command station with 2 x
8A).

Identical to the MX1 in terms of power (8A track power), processor and
memory capacity as well as software. Priced lower due to a simpler hous­ing, simpler connections, LED chain instead of an LCD display for volt and
amp indications (an external 2 x 16 display is available as accessory). Only
one track output, which is used for the main or programming track.

3. Specifications

Transformer input: maximum voltage (~) .......................................................................... 28 V

Track outputs, adjustable power *** )........................................................................ 12 to 24 V

Main track output (“SCHIENE 1), max. power **) ................................................. 8 - 10 A ***)

Programming track output of the MX1 (“PROGRAMMIERGLEIS”) max. power ................. 3 A

Programming track output of the MX1HS (“SCHIENE 2”), max. power ............................. 8 A

Dimensions MX1, MX1HS (B x H x T, incl. rubber feet) ............................. 210 x 90 x 210 mm

Dimensions MX1EC (B x H x T, incl. rubber feet) ...................................... 210 x 60 x 210 mm

Weight ................................................ 1,5 kg (MX1) , 2 kg (MX1HS) , 1 kg (MX1EC)

*) In accordance with consumer protection laws, a maximum of 24V is allowed for toy applications; ZIMO products
are however not declared as toy and the command station can operate with up to 28V transformer input.

**) When using a transformer with a secondary output of 25V (i.e. ZIMO TRAFO25), the maximum track current of
8A is only available at a track voltage setting of no more than 20V. The achievable track power (current) will be less
with track voltages above 20V.
8A of power can be achieved with up to 24V on the track when using a 28V transformer.

***) ATTENTION: It is important to adhere to the allowable track voltage settings specified for the decoders in use,
especially when using third party decoders!

COMMAND STATION MX1, MX1HS, MX1EC Page 3

LED’s for
“TRAFO 2” (and “SCHIENE 2” (main track) )

“”

TRAFO 1 (and “SCHIENE 1” (prog. Track)

on MX1HS

Track voltage regulator

(12 to 24 V)

SCHIENE 2 SCHIENE 1

Main track Prog. Track

(nur MX1HS)

Contrast setting for

LCD Display

.

Traf o- I n put (Sin gle LED),

All other LED’s for track

voltage (green) and power

(yellow) indication

Trac k vol t age regulator

(12 bis 24 V)

.

Page 4 COMMAND STATION MX1, MX1HS, MX1EC

4. Power supply – external transformer

ZIMO command stations do not have a direct mains connection. An external transformer must be
connected to the “TRAFO” terminal on the back panel. In order to fulfill local regulations use only ap­proved transformers (i.e. UL or other applicable agencies).

The requirements for the transformer used (or each of the two transformers in the case of the
MX1HS) as the primary power supply are:

Rated output 24 to 28V, nominal power at least 50VA, preferably 100 to 200VA.

Commercially available model railroad transformers (or power packs) are not suitable because the
voltage is usually too low and load dependent and supply too little power. Transformers of up to 28V
are recommended for large-scale applications if track voltage of more than 20V is required!

2 Transformer
for MX1HS !

Tr af o
24 V
to 28 V

Note to the „CAN bus“ (Cable from command station to cabs and other modules) . . .

Ready made CAN bus cables can be obtained from ZIMO in standard and custom length (see price list) but can
also be made by the end user; the required 6-conductor cable, connectors (package of 50) and the special mount­ing pliers are also available from ZIMO.

Connecting several cabs to the CAN bus is in most applications problem free (up to 10 cabs or other modules on
the bus. With up to 50m total cable length and no more than 2 cabs at the end of the 50m cable, or no more than 5
at the end of a 20m cable)

If the number of cabs or the distance to the command station is higher, some threshold values and countermea­sures need to be considered (terminating resistors, typically 150 to 330 Ohm between the center pins of the CAN
bus connector of the farthest module, contact ZIMO if needed !).

Tr af o
24 V
to
28 V

Tr af o
24 V
to 28 V

5. Connecting cabs (throttles)

All ZIMO command stations come equipped with two identical 6-pin RJ-12 CAN bus sockets (inter­nally connected) that accepts 6-conductor can bus cables, which are used for the data transfer be­tween the command station and cabs as well as other ZIMO products (accessory modules, track sec­tion modules etc.).

Every ZIMO cab also contains the two CAN bus
sockets so that all cabs may be daisy-chained
without the use of any special distribution
boxes.

Instead of connecting all cabs with each other
(daisy-chain), a 6-conductor bus cable can be
installed on the layout with appropriate
distribution boxes to which cabs can be
connected where needed.

6. Connecting the main and programming
track

… to the standard command station MX1 ...

The MX1 command station is equipped with two track output sockets.

• the output “MAIN”, to which the main track of the layout is
connected to. This output is rated at the full 8A.

• the output “PROG”, to which a section of track, isolated at
both ends from the rest of the layout track, is connected that
serves as the programming track for programming loco ad­dresses (and CV’s) of locos equipped with a DCC decoder.
This could be a ZIMO decoder or decoders from other manu­facturers such as Lenz, Roco etc. This output is limited to 3A.
Exceeding this limit turns the power to this output off and is
shown in the MX1 display with “UEP” - as opposed to “UES” af­ter the main track output is turned off.

If no programming procedure is running, the programming track may be part of the layout and used
in the same way. Naturally, power on that track section is always limited to 3A. With the help of the
DIP switches on the back side of the command station the power can be further reduced (down to 1A
or even no load), which can be useful when testing a newly installed decoder to reduce the risk of
damage to the decoder in case of wiring errors.

To programming track

To m ai n trac k

COMMAND STATION MX1, MX1HS, MX1EC Page 5

If the programming track is part of the layout (main track) that allows locomotives to drive from the
main track on and off the programming track (both rails isolated) the polarity of the two has to be the
same for both (pin N, pin P) !

… to the high-output command station MX1HS ...

The MX1HS is equipped with two 8A rated outputs marked
SCHIENE 1 and SCHIENE 2, whereas the output SCHIENE 2 also
functions as the programming output “PROG” as soon as a pro­gramming procedure is started with the cab or the computer.

Therefore, with a MX1HS the main track must be removed from the
output SCHIENE 2 = PROG and the programming track connected
instead, before any programming procedure is started in “service
mode”!

ATTENTION: Before proceeding with programming a locomotive,
make sure that the programming track is the only
the output SCHIENE 2 = PROG. If any part of the main track re­mains connected, all locomotives on that track will also be re­programmed!

The two outputs SCHIENE1 and SCHIENE 2 (except during pro-

track connected to

To programming track
(or second power dist rict
of an MX1HS)

To m a i n tr a ck

gramming) supply power to two power districts of a layout. They can also be wired in parallel to cre­ate one powerful district.

ATTENTION: Do not wire the two MX1HS outputs in parallel when track section modules MX9 are in
use on the layout!!

… to the economy command station MX1EC ...

The MX1EC has only one track output, which can be used fo r
either the main track or the programming track.

ATTENTION: Before any “service mode” programming proce­dure (before the procedure is started with the cab or a com­puter) with an MX1EC, the main track must be disconnected
from the track output and the programming track plugged in in­stead! This can be accomplished with an external switch or by
switching the track connectors on the MX1EC.

If the main track remains connected by mistake during a pro­gramming procedure, all locomotive and accessory decoders
will also be re-programmed!!

Possible protection procedure: See CV’s #31 - 38, “Enable
programming”!

Operate
switch
or
switch
plugs !

Main track

Program m ing track

Main track

Program m ing track

The track polarity in principle is of no importance. However, if track section modules MX9 are

employed the polarity is important and the track output pin “P” must be connected to the rail that is
gapped for building track sections, while the “N” output pin is connected to the common uninterrupted
rail.

The diameter of the track supply wire must be adequate...

… otherwise speed and lights may fluctuate and in serious cases lead to communication breakdown,
but also…

…causes the wiring to overheat to the point that it catches fire, especially in case of parallel wired
outputs (high currents)!

It is recommended that a cable diameter of at least 0.75 mm

2

(20 AWG); at least 1.5 mm2 (14AWG)
for wires longer than 5m (15ft) is used. Larger layouts should be fitted with several drop feeders (@
every 5m) to prevent noticeable voltage drops along the track.

7. Controls and applications

… on the standard command station MX1 and high-output MX1HS ...

After connecting a transformer to the input connector “TRAFO” (or two transformers on a MX1HS),
the three green LED’s light up (or four green LED’s on the MX1HS).

At first, the LCD display goes through a start-up sequence showing the device type, software version
and self test results if the DIAG switch is in the proper position. After the start-up sequence the stan­dard display shows track voltage and power of both track outputs (SCHIENE 1 and 2).

LED’s for
TRAFO 2, SCH IENE2,
TRAFO 1, SCHIENE 1

()MX1HS only

LEDs (green) for “TRAFO” input indicate
adequate voltage from transformer
(only one LED on Mx1 because only

To

To

To

To

one transformer is connected; two
LED’s on MX1HS because two
transformers are connected)

LEDs for “SCHIENE” (by-color LED’s, red/green)
Track power on

green:

red:

Trac k po we r off

(Most often due to short circuit)

After power-up:

Displays de vi ce t ype and the
software-version; self-test messages.

During normal operation:

Volt and Amp display for both track outputs

or short circuit displayed (UES, UEP),
CAN bus load in % (C:),
CAN bus error (E:).

Marking “SL” : C omm and station o perates as booster
(all data format switches to OFF)

During decoder program m in g a nd read-outs (using
the ca b) :

Display of CV numbers and values (the MX1

display is easier to read than the MX2).
During oth er de f in iti on e vents (e.g. Autonomous

block control): Information help to support the
operator.

Adjust track voltage here

(12 24 V)

SCHIENE 2 SCHIENE 1

()MX1HS only

to

.

Contrast adjustment

for LCD Displ ay

DCC, MOT, VAR

Page 6 COMMAND STATION MX1, MX1HS, MX1EC

… on the economy command station MX1EC …

(and connection of the external MX1DIS display)

The MX1EC does not have a built-in display like the standard MX1 command station does, but the
same display is available as an external module (part # MX1DIS) that can be connected to the
MX1EC. See below!

A built-in light bar (LED’s) on the front of the MX1EC serves as a rough indicator for applied t rack
voltage and power.

Power (transformer)

Green single LED in the light bar indicates track voltage in steps of 2V;

ellow LED bar indicates current draw (scale is not linear, with finer

Y
graduation in the lower range). LED’s change to red color just befor
reaching the maximum amperage (that is with the default setting of 7A).

Volt and Amps are indicated simultaneously if possible; the amp display

ill automatically fade out when track voltage changes are made. The

w
last LED on the right lights up red in case of overload situations (short
circuit on track or input voltage from transformer too low).

Light bar i ndicates tr ack voltage

(green) and Amps (yellow)

To connect

an external MX1DIS display module

proceed as follows:
Remove the screws on each side of the MX1EC and

lift the top off the co
socket inside (see drawing at left) and plug in the
cable that comes with the display module. Lead the
cable to the outside above the RS232 connector on
the back and reinstall the top.

The displayed information is largely identical to the
built-in display of the MX1 (see
one volt and amp meter since only one track output is
present on the MX1EC.

Adjust voltage from

12 to 24 V

e

0,1 A 0,2 A 0,5 A 1 A 3 A 6 A

.

14 - 16 V 22 - 24 V
18 - 20 V

12 - 14 V 20 - 22 V
16 - 18 V

mmand station. Locate the 16-pin

above), but only shows

8. The DIP switches (back of MX1)

… on the standard MX1 or high output MX1HS command station ...

The data format switch DCC, MOT, VAR:
The command station as delivered is set to operate in the DCC data format

only. If required, the MOTOROLA mode can be selected instead or in addition
to the DCC format.

The switch VAR is not used for now. It can be used in the future for selecting
another data format or for the distinction of different variants of a given data
format.

The diagnostic switch DIAG:
This switch (or jumper on the MX1EC) is for the planned actuation of a com-

prehensive self t
back wires etc.); will be impleme

The switch is also used for a general switch-over from the 8 to 12 function
mode.

… on the economy command station MX1EC ...

T

he data format jumpers DCC, MOT, VAR:

The same meaning and functions apply as to the switches abov
delivery.

… on the high output command station MX1HS as booster …

all three data format switches DCC, MOT and VAR are set to OFF, the command station is in the

If
booster mode (also known as slave unit), which means it will reproduce the control
command station MX1, MX1HS or a compatible third party product once connected
CONTROL wires (see chapter “The CONTROL bus). This mode is indicated in the right margin of the
display with “SL” (= SLAVE).

For the unit to function as a true booster (converting a MX1HS to a MXBOO) it is also necessary to
change internal jumper positions; see chapter “MX1HS as booster unit”! If more than one booster is
used set each booster to a uniqu
ber of boosters to 15).

… The switches 5 - 8 on the MX1 or MX1HS … (but not MX1EC) …

ON / OFF

Switch 5 ON (turn ON briefly, then OFF): Clearing all priorities in the DCC queue

- quicker reaction times by eliminating addresses which are no longer relevant.

Technical explanation: The command station continuously sends out commands to all 10239
addresses (send cycle); this is used to refresh the data in the loco decoders and allows the
loco number recognition to function. The priority of each single address varies – highest prior­ity is given to recently changed data (when a cab was used), followed by active addresse
the recall memory and so on all the way to addresses that were activated in the past and fi
never been used (lowest priority).

est at system s

tart up (memory function, output tests via feed-

nted with a future software update.

e number sequence with the dip switches 5 – 8 (this limits the num-

is marked on the DIP switch body

e; also set to the DCC format only at

signals of another

with them via the

s (in the

cab display), in

nally such that have

COMMAND STATION MX1, MX1HS, MX1EC Page 7

Switch 7 ON: Output PROG is limited to 1 A, normally it is limited to
3 A for MX1 and 8 A for MX1HS).

Switch 7 and 8 ON: Service mode programming is locked! Prevents start of the
programming process by mistake; useful for MX1HS, where the PROG output is
used alternatively as a normal track output (”SCHIENE 2”).

Switch 8 ON: Output provides powe
procedure; driving on the programming track that is normally possible is locked;
may be useful if unsure about the proper installation of a decoder – less chance
of destroying the decoder.

All switches ON: Erases command station memory; useful if unexplainable
malfunctions point to a possible messed up memory.

… If “old” ZIMO decoders operating in the 8-func

NOT RELEVANT FOR SYSTEMS AND DECODERS FROM 2003 AND UP
IMO decoders were delivered in the 8-function mode until the year 2002; if these decoders should

Z
not or can not be switched to the 12-function mode the command station, which (beginning
has always been delivered with the 12-function mode on, can be switched to the 8-function
with the following procedure (“general switch-over” of all addresses).

>> Turn off command station (unplug transformer from main); with the un-powered command sta­tion:
Place the DCC, MOT, VAR switches to OFF and the DIAG switch to ON
(with a MX1EC pull the DCC, MOT, VAR jumpers and install the D

>> Turn on command station (plug-in transformer); with the command station powered up:
Bring the VAR switch or jumper in the desired position; the position the
switch or jumper is left in deteremines the selected mode:
OFF (or jumper pulled) = 8-function / ON (jumper installed) = 12-function mode.

>> Power down the command station within 10 seconds, place all switches
or jumpers to the normal position (i.e. DCC ON).

>> Command station is ready to resume normal operation.
NOTE: A disagreement between the system and decoders regarding the 8

noticed by functions 5 – 8 not operational (not just functions 9 and up!) as
MAN-Bit function!

The “general switch-over” to the (old) 8-function m
ceptional cases; an address specific adjustment is the better choice (either in the decoder with CV
#112 or the system through the cab).

r to the track only during a programming

tion mode are used …

IAG jumper).

ode described above should only be used in ex-

in 2003)

mode

- or 12

-function mode is

well as the non-working

9. The auxiliary inputs (shuttle, AOS… )

on the MX1 or … on the MX1EC …

…

MX1HS …

(9-pin socket) (10-pin socket)

he command stations are equipped with 8 inputs that can be used with track switches or other ex-

T

rnal input components such as reed switches etc. One of the pins is a 5V output that can be used

te

supply external switches with the necessary voltage; however, any other positive voltage (up to

to
24V) can also be used to trigger these inputs (i.e. track voltage, which is the case when track
switches are used).

By default (alterable by configuration variables), the first 7 inputs are programmed for shuttle train
operation, switch ladder actuation or as “event inputs” for automatic operating sequences (AOS).

Regarding the a
train operations: see CV’s #41 – 56 in this manual. For definition and operation of AOS’ see chapter
“AOS – Automatic Operating Sequences”, CV’s #100, 101 below and the MX31 manual.

The eighth (last) input can be used (by default) for connecting a panic button that initiates an emer­gency stop of all locomotives when actuated. Any positive voltage can be used as input, i.e. the 5V
from pin 1 or from the track.

llocation of shuttle train inputs: see MX31 manual; stop-over times during shuttle

Shuttle

Page 8 COMMAND STATION MX1, MX1HS, MX1EC

10. The CONTROL bus (booster connection)

T is

he CONTROL bus establishes communication between the command station and boosters that

t by

he command station sends information out through the “DCC-out” connector, which is reproduced
the boosters and receives information back from the boosters regarding over current conditions of
booster units.

An NMRA standard exists for the CONTROL bus protocol (although not passed by the NMRA at the
time this manual was written), which makes the use of third party products possible provided they
adhere to th

In case of a pure ZIMO configuration that connects a ZIMO command station with ZIMO boosters (a
MX1HS may also be used as a booster if the appropriate jumpers are in the p roper positions – see
chapter 15), the information fe
bly via the CAN bus, because more information is accessible (e.g. about failed power districts). In
this case the wiring is to be done according to the upper of the two following drawings:

is standard.

edback is normally not transmitted via the CONTROL bus but prefera-

COMMAND STATION MX1, MX1HS, MX1EC Page 9

11. The Configuration Variables

The command stations offer the possibilities to modify certain char

ion variables. New features are introduced at the ZIMO web site www.zimo.at

t
new editions of this manual.

How to program or read out configuration variables is covered in the chapters “Addressing and Pro­gramming” of the cab manuals (MX31…). The usual programming procedure is started by pressing
the “E” key followed by th

e “MAN” key and enter “100” as the command station address.

CV Name Range Default Description

Max. c

#5

#6

#7

#8

#9

#10

#11

#12 RS 232 1 - 6

urrent on

SCHIENE 1 (MAIN)

Max. current on
SCHIENE 2 = PROG

Switch-off delay
SCHIENE 1 (MAIN)

Switch-off delay

DCC Tim

ing

1-Bit“ microsec

SCHIENE 2

Volt meter
corrections

SCHIENE 1
Volt meter

corrections
SCHIENE 2

= Length of „

0 - 80

0 - 8 A )

0 - 80

0 - 8 A

0 - 254

2 - 508

ms )

0 - 254

2 - 508

ms )

90 - 110 102

90 - 110 102

146 - 162

( =

( =

( =

( =

( = 8 A )

( = 8 A )

0,5 s )

0,5 s )

This CV defines the maximum allowable current for output
“SCHIENE 1”

80

is triggered tha
(Default 80 = 8 A)

This CV defines the maximum allowable current for output

80

“PROG” or “SCHIE
current protection is

(Default 30 = 3 A for MX1, 80 = 8 A for MX1HS)
After an over current situation is recognized (i.e. short cir

the command station switches to a “holding curre
duration of the delay time, which means the track v
being reduced to limit current flow to 10A. After the delay
time has elapsed, the output is shut-off completely (i.e.

250

“UES”). With this procedure it is possible to bridge very brief

( =

short circuits that often occur at frogs without shutting the
layout down.

The default delay is for some application too long (a “short”
could leave burn marks on N-scale wheels) and it is recom
mended to low

Same as CV # 7, but for “SCHIENE 2” or “PROG” output.

250

NOTE: The full range of adjustment in CV #8 is only effectiv

( =

for MX1HS; the delay time of the MX1 is always limited to
100ms (can only be varied between 0 and 100ms).

Larger CV value = smaller display value
and vice a versa.

(Adjusting range about 2 V).
Larger CV value = smaller display value

and vice a versa.
(Adjusting range about 2 V).

The short DCC bits (value “1”) can be modif

158

viating from the NMRA standa
decoders.

= 1: 1200 bit/s

4

acteristics by means of configura-

or can be studied in

(MAIN track) before the over-current protection

t shuts the power off.

NE 2” (MAIN trac

triggered that shuts the power off.

er the delay time if necessary.

k) before the over-

cuit)

r the

nt” fo

oltage is

rds. Useful for some third party

ied in length de-

CV Name Range Default Description

Bit rate ( =

1200 bit/s ( =

to

38400

bit/s )

#13

#14

#15

#19

#20

-

#21

e

#22

#23 Clearing priorities

#24

Handshake

Number of
preamble bits

Number of
preamble bits in
service mode

Address for anal
locomotive

Stop time before
direction change

Stop time after
direction change

Time interval for
turnout ladders

HARD RESET
and
memory erase

a

20 – 30 23

og

a

( = 0 to

( = 0 to

( = 0 to

0, 1 1

10 - 30 26

1 - 127 0

0 - 255

2 sec)

0 - 255

2 sec)

0 - 255 70

2 sec)

111,

222

2 sec )

2 sec )

0,5 sec )

1 0

0,

= 2: 2400 b
= 3: 4800 bi

9600

= 4: 9600 bit/s

/s

bit )

= 5: 19200 bit/s
= 6: 38400 bit/s

= 0: no Handsha
= 1

Number of 1-bits (s
command and the first byte
nizes the serial data transm

The default value (26) includes the special ZIMO ACK an
interpacket bits (4 + 10 bits), which leaves 12 “real” preambl
bits. If the ZIMO features “Signal controlled speed influence”
and “loco number identification” is not used, the
preamble bits can be reduced to 14 (the minimum number
required according to NMRA RP’s).

Number of preamble bits during service mode programming
at the “PROG” output.

The address entered here allows the control of an “analog
locomotive” (without de

= 0
this setting should always be retained if no analog
locomotive is intended to be used (DCC signal is more
efficient).

These times are effective if the direction key on the cab i

255

pushed “on the fly”, with the loco moving (without stopping

( =

the loco first).
By default, the direction is changed (headlights switching) 2

seconds after the end of the stop time is reached (per cab

255

settings, the decoder’s CV #4 is not being considered) and

( =

after another 2
rection is started.

Turnout ladders are defined with the cab by “sample actua­tion” with addresses 700.1, 700.2 … 799.7.

( =

When a turnout lad
delay entered in CV #22 is applied between the single switc
commands.

Entering the value “1” clears all priorities in the DCC send
cycle (same as with switch 5, see chapter “Controls…”)

CV #23 automa
ways returns a 0.

This is a pseudo-programming (the value entered is not
stored, always remains 0)

0

= “222”: HARD RE

it/s

t/s

ke RS 232

: RTS/CTS Handshake

hort bits) between the end of a DCC

of the next command; synchro-

ission in decoders.

d

e

number of

coder) with the cab.

: no analog locomotive can be controlled with the cab;

s

seconds the acceleration in the opposite di-

der so defined is actuated later, the time

h

tically resets to 0, so reading out this CV al-

SET, all CV’s are set to default.

Page 10 COMMAND STATION MX1, MX1HS, MX1EC

CV Name Range Default Description

(from SW version 2.14)

Amp meter
calibration

“SCHIENE 1

#25

(MAIN)
“SCHIENE 2”

#26

(PROG)
“General

switch-over”

#27

to 8-function
or 12-fun

System state a

#29

power up

#31

„AUX.IN“- Input

#32

application

#33

ATTENTION: When

#34

an input is used i

#35

an AOS applicat

#36

the pertaining

#37

must be set to “0”!

#38

#
41, 42
43, 44

Stop time before

45, 46

after

47, 48

change during shut-

49, 50

tle train operation.

51, 52
53, 54
55, 56

#57
#58
#59

Activating of a

#60

turnout ladder with

#61

an external switch.

#62
#63
#64

Initialization of
priorities in the send
cycle.

for DCC-Addr <

#81

for DCC-Addr > 127

#82

”

ction mode

a direction

fter

CV

n

ion

or

127

1 - 55

2

2 0

1 - 55

0, 1 1

0, 1, 2 0

0 - 5

1 - 255

( =

1 - 255

sec )

11 - 99

-

0 9

-

0 9

= “111”: Clears memory (as with switches, see page 7).

If the display deviates from 0 without a corresponding load
on the track outputs, the display for each output can be re-

0

duced in 10mA steps.
Values 255 to 128 invert the values to “-1” to “-127”.

= 0: All loco decoders are set to the 8-function mode.

: … to the 12-function mode.

= 1

= 0: Normal operation
= 1: Broadcast stop (SSP)
= 2: Track power off (AUS)

One CV for each of the

0
0
0
0
0
0
0
2

0, 0
0, 0
0, 0
0, 0
0, 0
0, 0
0, 0
0, 0

0
0
0
0
0
0
0
0

7
7

: Input not active (or AO

= 0
= 1: Shuttle train operation (
= 2

: Panic button connected (initiates a broad
= 3: Panic button connected (turns track pow
= 4: Activates a turnout ladder
= 5: Shuttle train operation and turnout ladder activa
= 6: Push-button switch for programming lock release

2 CV’s for each of the 8 “AUX. IN” – Inputs!
These CV’s take effect only if the pertaining CV is set to

automatic shuttle train operation (value 1 in CV’s #31…
One of the two CV’s (e.g. #41) for stop times

CV (e.g. #42) for stop times after the automati
rection.

One CV

for each of the 8 “AUX. IN” – Inputs, which only take
effect if the input is set for turnout ladder activation (value 4
in the pertaining CV #31….38).

Tens digit: Turnout ladder group address (1 - 9 = 701 – 709)
Ones digit; Number key (1 – 9) on the cab defined for this

turnout ladder.

All addresses are set to the priority specified in this CV after
power up.

= 1: Priority as before power-off
= 2: Priority 3
= 3: Priority 4
= 4: Priority

8 “AUX. IN” – Inputs!

S)

5 (lowest priority)

allocated with the cab)

cast stop)

er off)

before and one

c change o

tion

38).

f di-

CV Name Range Default Description

# TOROLA 0 9 herwise 4

83 for MO

Addresses remain
in higher priority

#84

after deactivation
from the cab

Adapt programmin
procedure to

#91

party decoder
Broadcast stop

initiated on main

#92

track while pro­gramming on th
programming tra

Programming on t
programming tra

#93 60 - 240 150

Maximum power

A

cknowledgment

#94 10 - 20 30

ower

p

Max. number of
„ACK W

#95

ackages

p
„Reset Packages“

#96

after programming
start

LGB pulse chain

#99

send

#100 al-CV’s AOS See Chapter “Automatic Operating Sequences“! Speci

third

e

ck.

ck:

ait“

- 7 = 5: Priority 3 when speed > 0, ot

0, 1 0

g

0 - 3 0

0, 1 0

he

70

= 6: Priority 4
= 7

: Priority 3 when speed > 0, otherwise 5
= 8: Addr.>127 removed from
= 9: Addr.>127 removed from

= 0

: Priority of addresses (> 127) is lowered some time after
they were cleared from the cab.
= 1: Addresses remain permanently in priority 3

CV #84 = 1 is recommended for larger la
large addresses > 127.

Disadvantage: addresses that were e
remain in high priority and reduce the send cycle
Therefore erase priorities once in a while!

= 0: Normal
= 1/2/3: Turn track power off before/after or before + after
the programming procedure.

= 0

: Broadcast stop (SSP) prevents unintended start up’s in
MX9 sect
= 1: Trains on main track run unhindered during
programming.

= 60: 100 mA
= 150: 250 mA
= 240: 400 mA

Changing this CV may help programming / reading locomo­tives that always c

= 10: 17 mA
= 30: 50 mA
= 120: 200 mA

Changing this CV may improve the recognition of acknowl­edgment pulses

Programming ev
decoders.

15

Number of “ACK Wait” packages at the start of the pro­gramming procedure, or the number of “Reset Package

30

that are sent after the programming procedure.

+/- 10 ms Change this CV in case the functions on LGB en
gines don’t function properly.

when speed > 0, ot

ions. New with SW-version 2.05!

onsume power (i.e. with sound modules).

and CV read-outs in “difficult cases”.
ent details to help with “difficult” third party

herwise 5

send cycle when speed = 0
send cycle

ntered accidentally also

youts with many

efficiency.

s”

-

COMMAND STATION MX1, MX1HS, MX1EC Page 11

12. MX1HS as Booster-Unit 13. Fuses

The high-output version MX1HS can also be used as a slave unit and operates identical to the “real”
booster unit MXB

In o er to “convert” a MX1HS to a booster, jumper positions need to be changed inside:

rd

A 4-pin “CONTROL” connector become

fter removing the top cover, the two jumpers just ahead of the

vi ht position (MX1HS as command

sible (see drawing below). Both jumpers are normally in the rig

station).
When both jumpers are moved to the left position the MX1HS becomes a slave unit and is only us-

able as such. Furtherm
boosters are employed a booster number must also be set. See the chapter “The CONTR
connecting a booster (slave) with a master command station!

OO.

ore, the switches DCC, MOT and VAR must be set to OFF and if several

OL bus” for

Master Slave

Slav Mastere

MX1
or
MX1HS

2 Fuses (3 in the MX1HS) are accessible after removing the top cover; one (two in the MX1HS) of
them are 8A fuses in the left rear close to the TRAFO input; the other (2A or 4A) in the center near
the CAN bus outputs.

If an 8A fuse blows, the whole power supply to the command station itself and all connected modules
is interrupted (n
reason is a defect in the command station. A one-time replacement of the fuse can be tried.

A blown 2A (or 4A) fuse interrupts the power to the CAN bus, which is noticed by the “dark” cabs. In
most cases it is not due to a defective command station but rather a defective CAN bus cable (short
between power and ground). Replace the fuse and locate the defective cable by swapping each one
with a known good one, starting at the command station.

othing lights up…) or the second power district (on an MX1HS). In most cases the

8 A - Fuse (Trafo)

Connector for ext. Display

Connector for
Bidirectional
Detector

2 A - Fuse (CAN Bus)

MX1EC

Flash-EPROM

Page 12 COMMAND STATION MX1, MX1HS, MX1EC

14. SOFTWARE Update

As is the case with most ZIMO components, the MX1 command station contains a micro processor
for which softwar
vised and made available to all users.

The software is preferably replaced with the help of a computer and appropriate HEX files and an
update program that are available f
program “ZST”!

If an update via computer is not possible or an update from a version older than 10 is required (ver-

on is displayed during power up), the FLASH-EPROM itself would have to be replaced (a new

si
EEPROM is available from ZIMO).

To replace a FLASH-EPROM:
The socket containing the FLASH-EPROM is located inside the command station on the left (MX1,

MX1HS) or to the front (MX1EC). Carefully remove the FLASH-EPROM from its socket and push the
new one a

emove the top cover only after the command station is powered down and the transformer un-

R

lugged.

p

e that controls all functions is stored in a FLASH-EPROM. The software is often re-

rom the ZIMO web site: www.zimo.at

ll the way down. Be careful not to damage the socket or the solder joints!

See below regarding the

15. The software ZST (ZIMO Service Tool)

The software ZST has been available for download at no charge from the ZIMO web site

www.zimp.at since September 2004. It is suitable for easy updating of command stations and all

connected modules containing FLASH-EPROMS (MX21, MX31, MXFU…) and will continually be ex­panded (Equipment-CV programming, CAN bus monitoring, statistical evaluations, data back-up and
more).

For inspection purposes, the co
tive, ZST is running, what is currently being processed between ZST an
its progress. For example:

ZST MX21 LISTE (= Search for and identify connected cabs).
ZST MX21 UPDATE (= New software upload for a s

ZST MX1 CV PR
ZST MX1 UPDATE
ZST CAN BUS
ZST RAM BACKUP
and much more.

2. line shows progression in % or bytes).
OG (= CV’s can be read-out and changed).

mmand station display shows that the serial data connection is ac-

d the command station and

pecific cab is in progress,

.

ZST MX21 LISTE
3 G E F U N D

COMMAND STATION MX1, MX1HS, MX1EC Page 13

r

16. AOS – Automatic Operating Sequences

From SW-version 2.05 (in MX1, MX1HS, MX1EC) !

What is an “Automatic Operating Sequence” (AOS)?

In principle, it is a timed and most often continuous replay of previously recorded sequences of drive
and switch commands.

In the course of a “sample run”, all commands from a cab addressed to a locomotive (speed, direc­tion, functions) and accessories (turnout and signal positions), together with th
stamps are being recorded and stored in the command station. Additionally so-called events, which
are signals from track switches, reed switches or similar are also recorded. Executing a stored oper­ating se

quence later plays back the recorded commands, where the recorded events are used for the

necessary corrections in time (by comparing the actual events with the recorded events).
With “AOS”, shuttle train operations with stop times, signaling and sound effects even w

ore alternating trains are possible but also more complex processes like repetitive shunting move-

m
ments.

Any number of locomotives and accessories may be

part of a sequence. Each sequence is recorded

separately; but several sequences can of course be played back simultaneously.

Recommendations to “event” triggers:

Track contacts, reed switches (with magnets on locomotives), photocells etc. can all be used as
“event” triggers and connected to the “AUX.IN” inputs of the command station; see chapter 8.

In many cases one single “event” in the sequence is sufficient. With the track configuration shown
below for example, an alternating shuttle service of

two trains can be defined, that is, from each of
the two dead-end sections to the right a train should move to the end of the common track (far left) ,
stop, and return to its own track. The track contact in the common section is the “event” input and al­lows for automatic time-modifications to the sequence (increase or decrease) in order to compensate
for changes in driving behavior (warm-up etc.).

Example of an “event” trigger location for an operating sequence (AOS):

to one of the
“AUX.IN” inputs

to track output “SCHIENE” of
the command station.

Recording an operating sequence by means of a sample run:

Described here using a MX2 cab, but equally valid when using a newer cab (MX31) if used “like an
MX21”.

Future software versions of the MX31 will have extended adjusting and subsequent correc-

ve actions; see MX31 manual!

ti

he MX2 (MX21, MX31...) uses the definition procedure for turnout ladders for this, particularly the

T
special group addresses range between 790 and 799. New software for the MX2 is therefore not re­quired.

eir relative time

ith two or

The memory location of an operating sequence is determined by the group address (AOS – group)
790….799 and the location number 1…8 of each group.

For both, recording and executing an operating sequence, the g
cab just like a loco address but activated with the “A” key (for a module address). The ca
cates with the LED above each number key 1 – 8 whether the locations concerned ar

roup address is first entered in the

b then indi-

e still free or al-

ready occupied:
Key-LED green:

Location is empty (ready for a new recording)
Key-LED yellow: Location is full (a new recording is only possible after deleting the old)
All key-LED’s flashing red

To delete a memory location press the “C” key together with the corr

: Memory full (no further definitions are possible)

esponding key.

To start recording a sample run, press the desired location key (1….8) for at least 1 second; which
the cab confirms with the

Key-LED flashing red/green:

Recording of a sample run in progress.

Before starting with the sample run, bring the locomotive(s) and accessories to their start position,
activate them on one or several cabs or make sure they are easy accessible (in recall memory); to
facilitate the whole process it is recommended that another cab(s) is used than the one the AOS
group (709….799) was initiated with.

IMPORTANT: Since all cab commands are being recorded during a sample run, abstain from running
other trains or operating other accessories; furthermore all MX8 and MX9 modules should be discon­nected from the CAN bus (otherwise their function would be disturbed during an AOS execution
later)! The layout itself however may remain connected.

After the recording has started (when the key-LED flashes red/green), all cab activities are being re­corded and the sample run may begin. All train movements, loco functions, turnout and signal actua­tions must now be made exactly the way they should later be operated when the AOS is played back
endlessly.

At the end of the sample run, all locos should be back to their starting point; otherwise there will be
no endless replay possible. The recording is ended by pressing the same location key briefly (the key
with the LED flashing red/green)

Key-LED ye llow:

memory location is full,

. The indicator then changes to

if the recording was successful. If the key-LED turns green, the recording was not possible. If during
or at the end of a recording the

Key-LED flashes red:

the memory has been exhausted (no recording takes place).

AOS-specific information di tion:

Useful information is shown on the
ever not depend on the display, that i

or

y

l

f

t

n

rre

c

u

n

c

f

r o

for AOS

e

y

seque

l

b

a

e

d

m

b

pl

u

a

s

L

di

Us

ore

N

t

s

e

s

d

e

sequ

)

s

ory

te

y

m

e

(B

m

s

m

e

p

u

me

nc

e

f

e

re

F

ace

p

s

splayed by the command sta

MX1 display during a sample run; the recording itself does how-

s it is also possible with a MX1EC that doesn’t have a display.

As soon as an AOS procedure is entered (input and activation

ry

of a group address on the cab), the upper line switches to the

o

OS

A

r

o

display of statistical data of current AOS memory: the number
of already stored sequences and the occupied memory space.

Note: The displayed occupa
mum available space reserve

n

cy rate in percent relates to maxi-

d for AOS of the currently installed

software version. This
value can change without the perators input (without deleting or
adding of sequences), by up
new software or if the memory
of loco names).

o

dating the command station with

is used for other tasks (i.e. storing

O

)

A

ck

d

a

b

re

y

d

to

a

l

d

s

(p

A

p a

g

u

a

n

i

c

n

o

l

gro

n

u

S

O

A

n

n

e

a

ress

nu

n

o

ti

u

t

Sta

e

v

e

v

“e

i

mber

t

t

s

c

a

d

,

n

f nex

d

o

e

” a

t

t

s

c

e

en

S

Exp

“Ev

”

t

d

S

)

s

e

t

.

tc

By

s

catior

n

tu

di

a

t

n

i

s

ounter (i

c

gres

o

r

ep

p

t

s

a

Page 14 COMMAND STATION MX1, MX1HS, MX1EC

The lower line is active during a sample run; that is after the recording
was started by pressing the appropriate number key for at least one
second.

y

r

n

p

Sam

in

e

e

r

nize

d

rog

p

p

u

Gro

c

o

l

g

d

o

umb

a

c

i

t

a

red

n

to

n

re

s

t

o

s

La

d

u

n

r

s

a

s

e

l

s

e

r

s

r

m

”

e

and

nt

d

m

e

v

d

)

e

s

“e

s

e

u

se

yt

y

l

t

(B

e

c

urren

C

spa

This is especially useful to confirm whether the expected “events” are

o

s

i

h

t

e

r

c

coming and how much memory is being used up for this sequence.

n

fo

e

qu

The displa

y also shows deleting actions and other pr

line); as well as error messages:
Error #2: Memory for pla

yback administration is full *)

ocedures (lower

Error #3: Memory is full

*) can be freed by deleting sequences.

Executing a stored operating sequence:

Described here using a MX2 cab, but equally valid when using a newer cab (MX31) if used “like an
MX21”. Future software versions of the MX31 will have extended adjusting and subsequent correc­tive actions; see MX31 manual!

The playback is started the same way as a sample run recording, by entering the group address on
the cab as you would for a loco address but accepting it with the “A” key instead. The LED’s above
each number key (1….8) indicate whether the memory locations are empty or occupied:

Key-LED green:
Key-LED yellow:

memory location is empty

memory location is full (playback activation is possible)

To activate a stored operating sequence playback, press the key of the desired “yellow” memory lo­cation; which is acknowledged by

Key-LED flashing yellow:

operating sequence is running.

Before the operating sequence can be played back, the locomotives involved must be at their re­spective starting positions, as they were when the sequence was started for the recording.

Any cabs showing an active loco address that is part of this sequence will have that address auto­matically deactivated (address is flashing).

ATTENTION: The loco addresses part of an operating sequence must not be activated with the cab
while the sequence is being played back!!

To end a playback, press the same key briefly; all trains that are part of this sequence are being re­turned to their starting location and automatically stopped. Once again the

Key-LED yellow:

memory location is full but no longer in playback mode.

If the trains need to be stopped immediately, press the key twice.

AOS-specific information displayed by the command station:

Depending on the CV #101 setting (see below), useful information during playback of an operating
sequence is shown by the MX1 display either temporarily (about 20 sec, default) or permanently (C V
#101, Bit 0 =1).

The upper line shows common data about the AOS memory (as during a recording); the lower line is
of most interest about the “event” handling: it becomes visible whether the timing during playback
matches the sample run and whether the “events” are being recognized properly. For this purpose,
the “events” are shown with prefixes:

N.. = This is the next expected “event”; the playback of stored commands is being executed as
planned (that is after the stored “events”).

W ..= The “event” is expected now, that is no more commands are to be executed ahead of this
“event”. If the train is late (compared to the sample run), the playback is delayed until the “event” i s
triggered in order to re-synchronize the sequence.

S.. = The “event” was triggered earlier than expected (the train was faster than during the sample
run); the playback speed is increased to re-synchronize the sequence; that is the commands up to
this point are processed faster.

B..= The next “event” is (still) locked (because it is also the past “event” triggered by axles of the
train, which is being expected).

E.. = “Event” is happening.
X00 = This operating sequence contains no “events” (no synchronization possible).

MX1 – Configuration variables for Automatic Operating Sequences (AOS):

These parameters are absolutely valid for MX2 and MX21 cabs; with an MX31 cab and future soft­ware version an individual setting for every operating sequence is possible. See MX31 manual!

CV #100: Simulation of overdue “events”. In case an “event” that was stored during a sample run re­cording has not been triggered, the sequence is aborted after 1 minute by default (CV #100 = 0);
most often though in connection with an accident (collision at the end of the run or similar). With

CV #100, Bits 0 – 5 = 0….63 a time is defined after which a reaction takes place if an “event” is over­due, namely

when Bit 7, 6 = 00 the operating sequence is being aborted;
when Bit 7, 6 = 01 (decimal + 64) the “event” is being simulated.
For example: If CV #100 = 69, the overdue “event” (compared to the recorded “event”) is generated

artificially after 5 seconds and the operating sequence will continue.
CV #101: pertains to the MX1 display when executing a stored operating sequence; by default the in-

formation is displayed only briefly and thereafter switches back to the normal MX1 volt and amp me­ter display. This does not affect the display during a sample run recording, which is always displayed
permanently:

Bit 0 = 0: Display is used “normally” (Volt and amp meter ….), not for AOS
Bit 0 = 1: The last activated sequence is continuously being displayed and updated.

COMMAND STATION MX1, MX1HS, MX1EC Page 15

17. The “old” (ASCII-oriented) Interface

This section is only of interest to users that want to operate the layout with an external computer but
don’t want to use the ready made software “STP”.

The serial interface of the MX1 command station allows the control of trains and accessories by a
computer as well as the polling of current route and switch data from the computer.

The interface at the MX1 is a 9-pin Sub-D socket; the connection with a computer is done with a 1: 1
serial cable.

The following described protocol was adopted from the previous product of the MX1 “model 2000”
command station described here and ensures compatibility to already existing applications. A more
powerful (alternative) protocol is in preparation (binary instead of ASCII).

Data transmission parameters:

9600 bit /s (default) - 8 bit - no parity - number of stop-bits 1 or 2.
(higher speed selectable with CV #12).

Computer to MX1 command format:

COMMAND ID - INFORMATION BYTES - CARRIAGE RETURN
(defines the command) (command data) (always last byte of a command)

The COMMAND ID is an ASCII letter (i.e. S, F, K etc.), which identifies the kind of command and
also determines the meaning of the information byte that follows.

With the command ID “S” only one INFORMATION BYTE follows in the form of another ASCII letter
(S, A, E).

All other command ID’s can be followed by a row of INFORMATION BYTES, which are however not
coded as binary but rather as two ASCII characters that represent the hexadecimal value (function
“HEX$” in BASIC).

At the end of each command, a CARRIAGE RETURN code must be present (“CHR$(13)” in BASIC).

Example of opening the interface and sending a loco command in BASIC:

OPEN “COM1:9600,N,8,1,CS,DS,CD” FOR OUTPUT AS #2
PRINT#2, “F”; “N”; HEX$(Loco address); HEX$(Speed step);

HEX$(Data byte1); HEX$(Data byte1); CHR$(13);
“F” is the command ID for loco commands; “Loco address” and “Data byte” are in decimal form (i.e.

loco address = 123, the data byte is a combination of speed and functions, see below); CHR$(13) is
the concluding carriage return.

ATTENTION: A leading “0” must be entered with values of <16!
All information bytes (loco address, speed step, data bytes etc. as described in the following com-

mands) must be sent to the MX1 command station in the form of two ASCII characters. The “HEX$”
function however sends in many BASIC versions only one character for values smaller than 16
(hexadecimal characters “0” to “F”). A “0” must be added as a leading character in such cases; if
possible with corresponding BASIC commands or by defining a special function that always produces
two characters.

Note for the creation of commands in other than a BASIC environment:
Sending the respective command ID (ASCII) does not present a problem. Coding of information

bytes is as follows: a loco address of “123” for example corresponds to the hexadecimal figure “7B”,
which is being sent as the two ASCII characters “7” and “B” (only capital letters are allowed as hexa­decimal characters!). The same applies to data bytes: for example, the “L function ON” and the
speed step 14 in a loco command result in a hexadecimal figures “1” and “E”, which are send as AS­CII characters. ATTENTION: always two ASCII characters per information byte (add a leading zero if
necessary).

Description of individual command types:

NOTE: In case of a MX1 command station sending out several data formats (DCC, MOTOROLA),
the respective loco or accessory address must contain a data format prefix:

“N” for DCC (for ZIMO and other NMRA-DCC compatible decoders) / “M” for MOTOROLA (Märklin
decoder).

Broadcast stop and track power OFF/ON commands: Command ID “S”

The entire command consists of only the command ID “S” and another letter, which represents its
content, as well as the obligatory carriage return:

“SS”; CHR$(13) - Broadcast stop ON (stops all trains).
“SA”; CHR$(13) - Track power OFF.
“SE”; CHR$(13) - Track power and broadcast stop OFF (normal operation commences).

Loco command: Command ID “F”

Besides the command ID “F”, the loco command consists of the appropriate loco address and the
data bytes, which contain the information about speed, direction and functions.

“F”; data format prefix (“N”,"M") HEX$(loco address);
HEX$(speed step); HEX$(data byte 1), HEX$ (data byte 2),
HEX$ (data byte 3), CHR$(13)

Data format prefix- only “N”, “M” allowed, see note above.
Loco address - decimal value (1 to 255); use HEX$(0) with single digit values
Speed step - Speed step of the currently active speed step systems
Data byte 1 - Bit 7 MAN-Bit
Bit 6
Bit 5 Direction (0 = forward, 1 = reverse)
Bit 4 Headlights ON/OFF (= DCC-Function 0)
Bit 3/2 DCC – speed step system
(01 = 14 speed steps, 10 = 28 steps, 11 = 127 steps;

Bit 1 Deceleration time “BZ” (definable with command “B”) ON/OFF
Bit 0 Acceleration time “AZ” (definable with command “A”) ON/OFF
Data byte 2 - Bit 0-7 Functions 1-8 ON/OFF
Data byte 3 - Bit 0-3 Functions 9-12 ON/OFF

Page 16 COMMAND STATION MX1, MX1HS, MX1EC

How the decimal value of the data byte that is entered to the above HEX$-function is calculated, ex­plains this example: “MAN” turned OFF, lights ON, direction reverse, speed step system “0-28”, “AZ”
and “BZ” OFF results in the binary word “00111000”, which in turn is the equivalent to the decimal
value of 0 x 128 + 0 x 64 + 1 x 32 + 1 x 16 + 1 x 8 + 0 x 4 + 0 x 2 + 0 x 1 = 56.

Function inversion command: Command ID “U”

This command allows inversion of direction and/or function outputs; this is sometimes useful in com­puter applications.

“U”; Address prefix, HEX$(loco address); HEX$(data byte 1); HEX$(data byte 2); CHR$(13)
Data format prefix - only “N” and “M” or “Z” are allowed
Loco address - decimal value (1 to 255),
Data byte 1 - bit assignment like command “F”, inversion with“1" (except 3/2)
Data byte 2 - bit assignment like command “F”, in version with“1"
Data byte 3 - bit assignment like command “F”, in version with“1"

Acceleration/deceleration (AZ/BZ) - command: Command ID “B”

Adjustment of “AZ” and “BZ”, which are the acceleration and deceleration times controlled by the
MX1 command station. Not to be confused with the configuration variables # 3 and # 4 in the decod­ers! “AZ” and “BZ” is independent of these configuration variables and it can also be used for non­DCC decoders. Note that “AZ” and “BZ” is turned ON and OFF with the “U” command.

“B”; data format prefix; HEX$(loco address); HEX$(data byte); CHR$(13)
Data format prefix - only “N” and “M” or “Z” are allowed, see note above.

Loco address - decimal value (1 to 255)
Data byte - Bit 0-3 BZ (0 - 15)
Bit 4-7 AZ (0 - 15)

Shuttle train command: Command ID “P”

This command allocates particular locomotives to the shuttle train inputs 1 to 4 of the command sta­tion (see the cab operating manual for details on shuttle train operations).

“P”; data format prefix; HEX$(loco address); HEX$(data byte); CHR$(13)
Data format prefix - only “N” and “M” or “Z” are allowed, see note above.

Loco address - decimal value (1 to 255)
Data byte - Bit 0-3 Shuttle train inputs 1-4, forward
Bit 4-7 Shuttle train inputs 1-4, reverse

Query of extend address indexing Command ID “E”

Locos with extended addresses (128 - 10239) are accessed with the usual commands listed above,
but instead of the address itself, an automatically assigned internal index address (128 - 255) is
used; which first needs to be ascertained with the help of the “E” query:

“E”; HEX$(High-byte of the loco address); HEX$(Low-byte); CHR$(13)
The command station then supplies an index message; such a message is delivered for addresses

>128 after each loco command to validate their assignment (unused loco addresses can lose their
initial index address if required).

Commands for accessory DECODERS: Command ID “M”

An accessory command is similar in its structure as a loco command; the data byte contains the ac­tuation information of 4 (in the DCC and MOTOROLA format) or 8 (in the ZIMO data format) turnouts
or signals.

“M”; data format prefix; HEX$(Accessory decoder address); HEX$(Data byte); CHR$(13)
Data format prefix - only “N” and “M” or “Z” are allowed

Accessory decoder address - decimal value (0 to 255); for MOTOROLA only to 63.
Data byte (DCC-data format) Bit 7 9. Address bit (Address range 0 to 510 !)

(The same for MOTOROLA- Bit 3 Switches ON or OFF (1=ON, 0=OFF)
format but without Bit 7) Bit 2-0 Number of the output to be switched

NOTE: If a switch command cannot be executed because another accessory command is currently
being processed, the MX1 answers with

“???; CHR$(13)”

The switch command must be repeated (in intervals of about 500 msec) until the negative answer is
no longer returned.

Commands for accessory MODULES: Command ID “N”

In contrast to the loco and accessory DECODER’s, the switch commands here are combined with
the command ID “N”. There are therefore two implementations of the command, depending on the
“switch type”.

“N”; HEX$(Module address); HEX$(Data byte); CHR$(13)
Module address - 800 to 863

Data byte as command - Bit 0-5 Number of the MX8 output
Bit 6 Position (0 = left, 1 = right)
Bit 7 = 1 (ID for command byte)
Data byte for query Bit 0-7 = 0 (ID for query)

Status query: Command ID “Z”

The command station is queried about the track voltage, broadcast stop and the available data for­mats (DCC, MOTOROLA, ZIMO).

“Z”; CHR$(13)

COMMAND STATION MX1, MX1HS, MX1EC Page 17

Query the command station memory: Command ID “A”

With this command the command station delivers information about current loco and accessory data
for a specific locomotive or accessory address.

“A”; F/W selection; Data format prefix; HEX$(Loco or accessory address); CHR$(13)
F/W selection - “F” = Loco address, “W” = Accessory address

Accessory address - if the DCC data format is used, a second data byte must be sent, of which
only Bit 7 as the highest DCC address is being evaluated (address range up to 510).

Commands in conjunction with routes: Command ID “W”

These commands relate to routes (turnout ladders) that are defined and called up with the cab (se e
cab manual). These route definitions are stored in the MX1 command station; the route memory can
be read out, re-installed or deleted via the MX1 computer interface. This allows the route definitions
to be saved in an external computer and if needed to be restored again (i.e. after loss of the MX1
memory or for transfer to another command station).

“WCLEAR”; CHR$(13) - Delete all routes.
“WO”; CHR$(13) - Send all stored route definitions to the computer.
“WI”; CHR$(13) - Reload routes from the computer.
If the data structure of the “WI” command is known (will be added later), it will be possible to define

routes in the computer and send them to the command station.

Commands in conjunction with lines: Command ID “O”

These commands relate to lines (block control) that are defined and called up with the cab (see cab
manual). These line definitions are stored in the MX1 command station; the memory can be read out,
re-installed or deleted via the MX1 computer interface. This allows the line definitions to be saved in
an external computer and if needed to be restored again (i.e. after loss of the MX1 memory or for
transfer to another command station).

“OCLEAR”; CHR$(13) - Delete all lines.
“OO”; CHR$(13) - Send all stored line definitions to the computer.
“”; CHR$(13) - Reload lines from the computer.

If the data structure of the “” command is known (will be added later), it will be possible to define lines
in the computer and send them to the command station.

Register-Programming Command ID “R”

For addressing and CV programming of all NMRA-DCC compatible loco decoders (ZIMO and others)
and for programmable decoders with the MOTOROLA format (Uhlenbrock decoder); the address is
stored in configuration variable (register) 1. The programming is performed on the programming
track.

“R”; Data format prefix (“N”or “M”); HEX$(Register number); HEX$(new value); CHR$(13)
“RE” – Terminating the programming mode

The “R” command (same as the “Q”) triggers a register message that serves as acknowledgment!

Register polling (for DCC data format only!) Command ID “Q”

This command prompts the command station to send a register message, which is used for reading
out configuration variables of NMRA-DCC compatible loco decoders.

“Q”; HEX$(Register number); CHR$(13)

Programming-on-the-main (for DCC data format only!) Command ID “L”

“Programming on-the-fly” (or “programming-on-the-main”).
“L”; HEX$(Loco address); HEX$(Command bytes); NMRA-Instruction; CHR$(13)
Loco address - decimal value (1 to 127)

Data byte - Bit 0-2 Number of bytes of the NMRA telegram (excl. ECC)
Bit 3-5 Number of desired telegrams
Bit 7 = 1: Address is locked out of the normal send cycle.
= 0: Address is controlled normally after the desired number of
telegrams have been sent.
NMRA-Instruction (up to 5 Bytes) - “On-the-main” – Command according to NMRA - RP 9.2.1

Special command:
Laa00 unlocks address aa without sending new data.

Message formats from MX1 to computer:

Command station status (“Z” query):

“Z”; HEX$(status byte); CHR$(13)
Status byte - Bit 7 MX1-Generation (0 = “old”, 1 = “new”)

Bit 6 1 = ZIMO-Data format active (Type and jumper)
Bit 5 1 = DCC- Data format active (Type and jumper)
Bit 4 1 = MOTOROLA- Data format active (Type and jumper)
Bit 0 Broadcast stop (1 = ON, 0 = OFF)
Bit 1 Track power (1 = ON, 0 = OFF)
Bit 2 UES-Short circuit protection (1 = ON, 0 = UES OFF)

Memory report (after “A” query):

“A”; F/W-Selection; data format prefix; HEX$(Loco or accessory address);
HEX$(speed step); HEX$(Data byte 1); HEX$(Data byte 2);
HEX$(Data byte 3); HEX$(AZ/BZ); HEX$(Group byte); CHR$(13)

F/W-Selection “F” = Loco address, “W” = Accessory address
Data format prefix - only “N”, “M” allowed
F..- or M..address decimal value (1 to 255);
additional Byte for DCC data format with
Bit 7: 9. address byte; Bit 0: 0 = paired bits, 1 = single bits)
Speed step or accessory position – as in “F” or “M” command
Data byte 1 - Format same as data byte 1 in “F” command
Data byte 2 - Format same as data byte 2 in “F” command
AZ/BZ-Values - Format same as data byte in “B” command
Data byte 1 - Bit allocation same as in “F” command

Page 18 COMMAND STATION MX1, MX1HS, MX1EC

Data byte 2 - Bit allocation same as in “F” command
Data byte 3 - Bit allocation same as in “F” command
or
Group byte - Bit 0 Cab activity (0 = not active, 1 = active, address in display)
Bit 2 Loco decoder feedback (1 = received)

Register report (after “Q” query):

“Q”, HEX$(Error code), HEX$(Register number); HEX$(current value); CHR$(13)
Error code - 0 = successful read-out of register number

Index report (after “E” query or loco command for extended address):

“E”, HEX$(Index addressee), HEX$(loco address high byte); HEX$(low byte); CHR$(13)
Error code - 1 = “Old” ZIMO data format is active (jumper).

3 = Address is < 128 (not extended address)
5 = Index address is not assigned to a loco address.

Error messages in form of an index address (Index address < 128 is an error message!).
0 = no data block available.
1 = “Old” ZIMO data format is active (Jumper).
3 = Address is < 128 (must be used as normal address).

18. The “new” binary Interface Protocol

1. Communication basics:

The basic communication format is N,8,1 (no parity, 8 data bits,1 stop bit). Communication speed
ranges from 1200 to 38400 bit/s and can be selected via CV12. The default value is 9600 bit/s.

2. Flow control

Flow control is done via hardware (RTS/CTS). It is necessary to use a serial cable with at least 5
wires which also connects the RTS and CTS lines between PC and command station. Hardware flow
control can be disabled by setting CV13 to 0. Default value is 1 (hardware flow control enabled).

3. The new binary communication

The new binary communication consists of data frames with the following structure:

• long frames:

<SOH><SOH>headerinfo_and_data[checksum16]<EOT>

• short frames (for frames of maximum 15 bytes):

<SOH><SOH>headerinfo_and_data[checksum8]<EOT>
To establish a data transmission independent of content, all data characters identical to control

characters have to be protected with the additional escape character prefix <DLE> and the
character itself is XOR'ed with 0x20.

control
character

Each data frame is immediately acknowledged by the receiver (level 1 reply). This reply may contain
the appropriate data if it's immediately available in the command station. Otherwise the request is
passed on via the CAN bus (to another station for example) and the subsequent incoming data is re­turned (level 2 reply).

<SOH> 0x01 <DLE>(<SOH>^0x20) start of a data frame
<EOT> 0x17 <DLE>(<EOT>^0x20) end of data frame

<DLE> 0x10 <DLE>(<DLE>^0x20) escape character

value

replacement

data

within

description

3.1. Header info

The header info describes the meaning of the data content of a frame. The length of the header info
is between 2 and 15 bytes. The first byte is the unique sequence-ID of the frame and must not be
identical in two different consecutive frames. If a frame has to be repeated, the sequence-ID remains
unchanged. The second byte specifies the message type and the meaning of additional header
bytes.

COMMAND STATION MX1, MX1HS, MX1EC Page 19

3.1.1. short frame protocol messages

General messages

Reset message
Header byte Value Description

1 0-255 unique sequence-ID
2 0 reset message

Reply: Ack for Reset (level 1)

Negative acknowledgement sent by command station
Header byte Value Description

1 0-255 unique sequence-ID
2 1 negative acknowledgement sent by command station

Reply: n.a.

Negative acknowledgement sent by PC
Header byte Value Description

1 0-255 unique sequence-ID
2 2 negative acknowledgement sent by PC

Reply: n.a.

Acknowledgement/reply sent by command station (level 1)
Header byte Value Description

1 0-255 unique sequence-ID
2 3 acknowledgement/reply sent by command station (level 1)
3 ID sequence-ID of the message that is being acknowledged

4..15 data optional: requested data or additional return code

Reply: n.a.

Acknowledgement/reply sent by PC (level 1)
Header byte Value Description

1 0-255 unique sequence-ID
2 4 acknowledgement/reply sent by PC (level 1)
3 ID sequence-ID of the message that is being acknowledged

4..15 data optional: requested data or additional return code

Reply: n.a.

Acknowledgement/reply sent by command station (level 2)
Header byte Value Description

1 0-255 unique sequence-ID
2 5

3 ID sequence-ID of the message that is being acknowledged

4..15 data optional: requested data

Reply: Ack (level 1)

Acknowledgement/reply sent by PC (level 2)
Header byte Value Description

1 0-255 unique sequence-ID
2 6 acknowledgement/reply sent by PC (level 2)
3 ID sequence- ID of the message that is being acknowledged

4..15 data optional: requested data

Reply: Ack (level 1)

Acknowledgement sent by command station for reset message
Header byte Value Description

1 0-255 unique sequence- ID
2 7 acknowledgement sent by MX1 for reset message
3 ID sequence- ID of the message that is being acknowledged

acknowledgement/reply sent by command station (level 2

)

Reply: n.a.

Page 20 COMMAND STATION MX1, MX1HS, MX1EC

Acknowledgement sent by PC for reset message
Header byte Value Description

1 0-255 unique sequence- ID
2 8 acknowledgement sent by PC for reset message
3 ID sequence- ID of the message that is being acknowledged

Reply: n.a.

Command station query
Header byte Value Description

1 0-255 unique sequence- ID
2 9 query command station

Reply: Ack (level 1) see also 4.5

Command station messages

These messages provide communication with the command station.

Track control
Header byte Value description

1 0-255 unique sequence- ID
2 0x0A command station instruction
3 0 track control
4 cAction 0 stop broadcast (stops all locos)

1 switch track voltage OFF
2 switch track voltage ON and re-enable broadcast
3 query status

Reply: Ack (level 1)

Return code Value Description

Status Bits dm000uts d ……. DCC (1 on, 0 off)

m …… Motorola (1 on, 0 off)
u ……. UES (1 UES on, 0 UES off)
t …….. track voltage (1 off, 0 on)
s ……. broadcast stop (1 on, 0 off)

Loco control
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A command station instruction
3 1 loco control
4 cAdr_hi loco address high byte

bit 6 + bit 7 format specifications (see
5 cAdr_lo loco address low byte
6 cSpeed Speed step in the actual speed step system

(DCC data signal: 0-14, 0-27 or 0-126; according to bit 3/2 in

cData1;MOTOROLA protocol: 0-14)
7 cData1 bit 7: MAN (override signal controlled speed limits)

bit 6: no function

bit 5: direction (0 = forward, 1 = reverse)

bit 4 headlights on/off (= DCC function F0)

bit 3/2 DCC speed step system (see

bit 1 decel. time “BZ” (definable by command “B”) on/off

bit 0 accel. time “AZ” (definable by command “B”) on/off
8 cData2 bit 0-7: function outputs 1-8 on/off (DCC only)
9 cData3 bit 0-3: function outputs 9-12 on/off (DCC only)

Reply: Ack (level 1) see also 4.8 and 4.9

Invert function bits
Header byte Value Description

1 0-255 unique sequence-ID
2 0x0A command station instruction
3 2 invert function bits
4 cAdr_hi loco address high byte

bit 6 + bit 7 format specifications (see
5 cAdr_lo loco address low byte
6 cData1 the following bits are toggled when set:

bit 7: MAN (override signal controlled speed limit)

bit 6: no function

bit 5: direction (0 = forward, 1 = backward)

bit 4 headlights on/off (= DCC function F0

bit 1 Decel. time “BZ” (definable by command “B”) on/off

bit 0 Accel. time “AZ” (definable by command “B”) on/off

4.6)

4.7)

4.6)

)

COMMAND STATION MX1, MX1HS, MX1EC Page 21

7 cData2 bit 0-7: function outputs 1-8 on/off (DCC only)
8 cData3 bit 0-3: function outputs 9-12 on/off (DCC only)

Reply: Ack (level 1) see also 4.8 and 4.9

Acceleration / deceleration (AZ / BZ) command
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A Command station instruction
3 3 acceleration / deceleration command
4 cAdr_hi loco address high byte

bit 6 + bit 7 format specifications (see
5 cAdr_lo loco address low byte
6 cAzBz bit 0-3: BZ (0 - 15)

bit 4-7: AZ (0 - 15)

Reply: Ack (level 1) see also 4.8 and 4.9

Shuttle train command
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A Command station instruction
3 4 shuttle train command
4 cAdr_hi loco address high byte

bit 6 + bit 7 format specifications (see 4.6)
5 cAdr_lo loco address low byte
6 cData bit 0-3: contact rails 1-4 forward

bit 4-7: contact rails 1-4 reverse

4.6)

bit 6 + bit 7 format specifications (see 4.6)

5 cAdr_lo accessory address low byte
6 cData bit 3: switching output on / off (1=on, 0=off)

bit 2-0: number of output that should be activated

Reply: Ack (level 1) see also 4.8 and 4.10

Query command station’s loco memory
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A Command station instruction
3 6 query loco memory of command station
4 cAdr_hi address high byte

bit 6 + bit 7 format specifications (see 4.6)

5 cAdr_lo address low byte

Reply: Ack (level 1) see also 4.8 and 4.11

Query command station’s accessory decoder memory
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A Command station instruction
3 7 query command station’s accessory decoder memory
4 cAdr_hi address high byte

bit 6 + bit 7 format specifications (see

5 cAdr_lo address low byte

Reply: Ack (level 1) see also 4.8 and 4.12

4.6)

Reply: Ack (level 1) see also 4.8 and 4.9

Accessory decoder command
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A Command station instruction
3 5 accessory decoder command
4 cAdr_hi accessory address high byte

Address control
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A Command station instruction
3 8 address control
4 cAdr_hi address high byte

bit 6 + bit 7 format specifications (see 4.6)

5 cAdr_lo address low byte

Page 22 COMMAND STATION MX1, MX1HS, MX1EC

6 cControl bits 7: 0 –address status query

1 – set address status according to bits 1-0
bit 5: 1: accessory address 0: loco address

bit 1: lock address when bit is set (no external changes
bit 0: log external changes when bit is set

Reply: Ack (level 1), Ack (level 2) see also 4.13, 4.11and 4.12

Read command station
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A Command station instruction
3 9 read command station

Reply: Ack (level 1) see also 4.14

Read/set a command station CV
Header byte Value Description

1 0-255 unique sequence- ID
2 0x0A Command station instruction
3 10 read/set a command station CV
4 Variable_hi Configuration variable number high byte that shall be read/set
5 Variable_lo configuration variable number low byte that shall be read/set
6 Value optional: if a value is present it will be set as new CV-value

Reply: Ack (level 1) also see 4.15 4.15

return code Value Description

NO_ERROR 0x00 No error within the request
ERR_CV_ADRESSE 0x07 Not a valid CV address

Current loco memory

If logging is activated for a loco address, this message is sent spontaneously whenever the loco
memory’s state changes due to external input.

Header byte Value Description

1 0-255 unique sequence-ID
2 0x0B command station message

)

3 0 current loco memory
4 cAdr_hi address high byte

bit 6 + bit 7 format specification (see 4.6)

5 cAdr_lo address low byte
6 cSpeed speed step of the current speed step system

(DCC data signal: 0-14, 0-28 or 0-126; according to bit 3/2 in
cData1;MOTOROLA protocol: 0-14)

7 cData1 bit 7: MAN (override signal controlled speed limit)

bit 6: no function
bit 5: direction (0 = forward, 1 = reverse)
bit 4 headlights on/off (= DCC function F0)

bit 3/2 DCC speed step system (see
bit 1 decel. time “BZ” (definable by command “B”) on/off
bit 0 accel. time “AZ” (definable by command “B”) on/off

8 cData2 bit 0-7: function outputs 1-8 on/off (DCC only)
9 cData3 bit 0-3: function outputs 9-12 on/off (DCC only)
10 cAzBz bit 0-3: BZ (0 - 15)

bit 4-7: AZ (0 - 15)

11 cStatus 1 … address is active

Reply: Ack (level 1)

Current accessory decoder memory

If logging is activated for an accessory decoder address, this message is sent spontaneously when­ever the accessory decoder memory’s state changes due to external input.

Header byte Value Descrip tion

1 0-255 unique sequence-ID
2 0x0B command station message
3 1 current accessory decoder memory
5 cAdr_hi address high byte

bit 6 + bit 7 format specification (see
6 cAdr_lo address low byte
7 cPair 0 … paired output function

1 … single output function
8 cOutputs state of the 8 outputs

4.7)

4.6)

COMMAND STATION MX1, MX1HS, MX1EC Page 23

Reply: Ack (level 1)

Accessory module messages (MX8)

Activate/deactivate spontaneous messages of an
Header byte Value Description

1 0-255 unique sequence-ID
2 0x17 MX8 control instruction
3 0 activate / deactivate spontaneous messages
4 MX8_ID address of the MX8 (1-63 not 801-863)
5 Output0 The bits 0-7 represent the module outputs 0-7
6 Output1 The bits 0-7 represent the module outputs 8-15.
7 Output2 The bits 0-7 represent the module outputs 16-23
8 Output3 The bits 0-7 represent the module outputs 24-31. The message

Reply: Ack (level 1)

Activate selected spontaneous messages of an accessory module
Header byte Value Description

1 0-255 unique sequence-ID
2 0x17 MX8 control instruction
3 1 activate additional spontaneous messages
4 MX8_ID address of the MX8 (1-63 not 801-863)
5 Output0 The bits 0-7 represent the module outputs 0-7
6 Output1 The bits 0-7 represent the module outputs 8-15.
7 Output2 The bits 0-7 represent the module outputs 16-23
8 Output3 The bits 0-7 represent the module outputs 24-31. The message

accessory module

forwarding is activated for all main sections if the corresponding bit
is set, otherwise it is deactivated. The odd bits of paired outputs
are meaningless.

forwarding is activated for all main sections if the corresponding bit
is set, otherwise it is deactivated. The odd bits of paired outputs
are meaningless.

Reply: Ack (level 1)

Deactivate selected spontaneous messages of an accessory module
Header byte Value Description

1 0-255 unique sequence-ID
2 0x17 MX8 control instruction
3 2 deactivate additional spontaneous messages
4 MX8_ID address of the MX8 (1-63 not 801-863)
5 Output0 The bits 0-7 represent the module outputs 0-7
6 Output1 The bits 0-7 represent the module outputs 8-15.
7 Output2 The bits 0-7 represent the module outputs 16-23
8 Output3 The bits 0-7 represent the module outputs 24-31. The message

Reply: Ack (level 1)

Set output of accessory module
Header byte Value Description

1 0-255 unique sequence-ID
2 0x17 MX8 control instruction
3 3 set output of accessory module
4 MX8_ID address of the MX8 (1-63 not 801-863)
5 cData bit 0-5: number of module output

Reply: Ack (level 1)

Query accessory module outputs
Header byte Value Description

1 0-255 unique sequence-ID
2 0x17 MX8 control instruction
3 4 query accessory module outputs
4 MX8_ID MX8 address (1-63 not 801 -863)

forwarding is activated for all main sections if the corresponding bit
is set, otherwise it is deactivated. The odd bits of paired outputs
are meaningless.

bit 6: position (0 = left, 1 = right)
bit 7 is not used

Page 24 COMMAND STATION MX1, MX1HS, MX1EC

Reply: Ack (level 1), Ack (level 2)

Read/set a MX8-CV
Header byte Value Description

1 0-255 unique sequence-ID
2 0x17 MX8 control instruction
3 7 read/set a MX8-CV
4 MX8_ID MX8 address (1-63 not 801 -863)
5 variable Configuration variable that shall be read/set
6 value optional: if a value is present it will be set as new CV-value

Reply: Ack (level 1), Ack (level 2)

Current accessory module output state

If spontaneous messages are activated for an accessory module’s output, this message is sent spon­taneously whenever it’s state changes.

Header byte Value Description

1 0-255 unique sequence-ID
2 0x18 MX8 message
3 MX8_ID MX8 address (1-63 not 801 -863)
4 0 Current output state
5 cData bit 0-5: module output number

see also 4.16

bit 6: position (0 = left, 1 = right)
bit 7 paired output

warding is activated for all main sections if the corresponding bit is
set, otherwise it is deactivated.

Reply: Ack (level 1)

Activate selected spontaneous messages of a track section module
Header byte Value Description

1 0-255 unique sequence-ID
2 0x15 MX9 control instruction
3 1 activate additional spontaneous messages
4 MX9_ID MX9 address (1-63 not 901 -963)
5 sections The bits 0-7 represent the main sections 0-7. The message for-

Reply: Ack (level 1)

Deactivate selected spontaneous messages of a track section module
Header byte Value Description

1 0-255 unique sequence-ID
2 0x15 MX9 control instruction
3 MX9_ID MX9 address (1-63 not 901 -963)
4 2 deactivate additional spontaneous messages
5 sections The bits 0-7 represent the main sections 0-7. The message for-

warding is activated for all main sections if the corresponding bit is
set, otherwise it is deactivated.

warding is deactivated for all main sections with their correspond­ing bit set, for all others the forwarding remains unchanged

Reply: Ack (level 1)

MX9-messages

It is possible to choose individual MX9 track sections for forwarding spontaneous status messages
(occupancy and loco numbers) as well as to query the current state of the module’s track sections.

Activate/deactivate spontaneous messages of a
Header byte

1 0-255 unique sequence-ID
2 0x15 MX9 control instruction
3 0 activate / deactivate spontaneous messages
4 MX9_ID MX9 address (1-63 not 901 -963)
5 sections The bits 0-7 represent the main sections 0-7. The message for-

Value Description

track section module

Reply: Ack (level 1)

Read the track section module’s occupancy state
Header byte Value Description

1 0-255 unique sequence-ID
2 0x15 MX9 control instruction
3 3 read the track section module’s occupancy state
4 MX9_ID MX9 address (1-63 not 901 -963)

Reply: Ack (level 1) see also 4.18

COMMAND STATION MX1, MX1HS, MX1EC Page 25

Read the track occupancy status and loco numbers of a main section
Header byte Value Description

1 0-255 unique sequence-ID
2 0x15 MX9 control instruction
3 4 read the occupancy state and loco numbers of the section
4 MX9_ID MX9 address (1-63 not 901 -963)
5 section main section number

Reply: Ack (level 1) see also 4.19

Set new speed limits of a main track section
Header byte Value Description

1 0-255 unique sequence-ID
2 0x15 MX9 control instruction
3 5 set new speed limits to the section
4 MX9_ID MX9 address (1-63 not 901 -963)
5 section main section number
6 Limit speed limit

(H=0, U=1, L=2, F=3, A=4, HU=5, UL=6, LF=7)

7 Limit2 optional: apply speed limit when reaching section A (bit 7=1) or

section B (bit 7=0); there is no speed limit change when reaching
the second section if this value is omitted

Reply: Ack (level 1)

Set LED-outputs of a track section module

Header byte Value Description

1 0-255 unique sequence-ID
2 0x15 MX9 control instruction
3 6 set LED-outputs
4 MX9_ID MX9 address (1-63 not 901 -963)
5 cGreen settings for „green-LED’s“ on connector “signals”
6 cRed settings for „red-LED’s“ on connector “signals”
7 cLedsA optional: settings for „LED’s-A“ on connector “occupancy indica-

tors”

8 cLedsB settings for „LED’s-B“ on connector “occupancy indicators”

Attention: after sending a message including the optional settings
for the leds on connector “occupancy indicators”, these outputs are
no longer controlled automatically by the MX9 and do not repre­sent the occupancy status!

Reply: Ack (level 1)

Read/set a MX9-CV
Header byte Value Description

1 0-255 unique sequence-ID
2 0x15 MX9 control instruction
3 7 read/set a MX9-CV
4 MX9_ID MX9 address (1-63 not 901 -963)
5 variable Configuration variable that shall be read/set
6 value optional: if a value is present it will be set as new CV-value

Reply: Ack (level 1), Ack (level 2)

Page 26 COMMAND STATION MX1, MX1HS, MX1EC

Main track section message

3.1.2. Long frame protocol messages

If spontaneous messages are activated for a track section module’s section, this message is sent
spontaneously whenever it’s state changes.

Header byte Value

1 0-255 unique sequence-ID
2 0x16 MX9 message
3 0 main section status
4 MX9_ID MX9 address (1-63 not 901-963)
5 section main section number (0-7)
6 B-Status occupancy status of main section 0

7 F-Status active speed limit
8 Zugnr1_H 1. loco number high byte

9 ZugNr1_L 1. loco number low byte
10 ZugNr2_H 2. loco number high byte
11 ZugNr2_L 2. loco number low byte
12 ZugNr3_H 3. loco number high byte
13 ZugNr3_L 3. loco number low byte
14 ZugNr4_H 4. loco number high byte
15 ZugNr4_L 4. loco number low byte

Reply: Ack (level 1)

Descript

V C S B A T T T
V: data valid
C: changed (since last transmission)
S: short circuit (main section off)
B: section B occupied
A: section A occupied
T T T: number of recognized loco numbers (0-4)

(H=0, U=1, L=2, F=3, A=4, HU=5, UL=6, LF=7)

ion

General messages

Acknowledge/reply sent by MX1 (level 1)
Header byte Value Description

1 0-255 unique sequence-id
2 255 acknowledge/reply sent by command station (level 1)
3 dd00nnnn nnnn … length of header

dd … additional data flow information (see 4.17)

4 ID sequence-id of the message that is being acknowledged

Reply: n.a.

Acknowledge/reply sent by PC (level 1)
Header byte Value Description

1 0-255 unique sequence-id
2 254 acknowledge/reply sent by PC (level 1)
3 dd00nnnn nnnn … length of header

dd … additional data flow information (see 4.17)

4 ID sequence-id of the message that is being acknowledged

Reply: n.a.

Acknowledge/reply sent by MX1 (level 2)
Header byte Value Description

1 0-255 unique sequence-id
2 253 acknowledge/reply sent by command station (level 2)
3 dd00nnnn nnnn … length of header

dd … additional data flow information (see 4.17)

4 ID sequence-id of the message that is being acknowledged

Reply: Ack (level 1)

COMMAND STATION MX1, MX1HS, MX1EC Page 27

Acknowledge/reply sent by PC (level 2)
Header byte Value Description

1 0-255 unique sequence-id
2 252 acknowledge/reply sent by PC (level 2)
3 dd00nnnn nnnn … length of header

dd … additional data flow information (see 4.17)

4 ID sequence-id of the message that is being acknowledged

Reply: Ack (level 1)

3.2. Checksum

The checksum includes all bytes of the original raw data of the data frame (i.e. header info and data)
but excluding the protecting escape characters and without XOR’ing with 0x20.

3.2.1. Checksum8

Checksum8 is an 8 bit checksum as it is utilized by various chip manufacturers (with the polyno­mial

458

1

+++ xxx , bit reversion for data and remainder, initialized with 0xff)

3.2.2. Checksum16

Checksum16 is a 16 bit checksum (CRC16/CITT: with the polynomial , initial­ized with 0xffff). All characters following the frame’s preamble (<SOH><SOH>) are included.

51216

1

+++ xxx

4.1. Reset message

The reset message provides a synchronization of the sending and receiving stations (either one may
be a PC or command station). After a reset, all buffers are cleared and the sequence ID’s are reset. If
the special acknowledgement for a reset message is received by the sender, everything is ok. If
there is no reply or a negative acknowledgement the reset message has to be sent again just as for
any “normal” message. In the rare case of a sequence ID conflict (the newly received reset message
has the same sequence ID as the last (non reset) message) the answer would be a “normal” ac­knowledgement for the previous message. In this case the reset message has to be re-sent with the
next sequence ID and thus resolve the conflict.

If the command station initiates a (spontaneous) reset of the serial communication, it will send a reset
message.

4.2. Negative acknowledgement

If a corrupt message is received, that is a message that fails the checksum test, a negative acknowl­edgement is sent. As it is impossible in these cases to determine whether the received sequence-ID
of the incoming frame is correct, it has to be assumed that it is incorrect. Therefore a negative ac­knowledgement message cannot contain the sequence-ID of the message it is referring to – the
sender must determine the erroneous message.

4.3. Acknowledge / reply - level 1

When a data frame is correctly received it is acknowledged with its unique sequence-ID. Additionally
requested data may be included in the reply if it’s immediately available in the command station –
data not available at this time will be sent seperat via acknowledge/reply level 2. Alternatively, there
may be a return code or data included to describe the result of the request.

4.4. Acknowledge / reply - level 2

A level 2 confirmation message is basically a normal message (including a reference to the primary
message) that has to be acknowledged by the receiver.

4. Protocol details

Each message has a unique sequence-ID. After sending the final EOT, an acknowledgment or reply
is expected for a specific length of time. If no such acknowledgement or reply is received, the mes­sage will be sent again with the same sequence-ID. If the reply is a negative acknowledgement, the
message is resent immediately. If a message with the same sequence-ID is received the appropriate
reply will be re-sent, as the original reply was obviously lost – any additional actions will be omitted
as they where fulfilled when the message was correctly received the first time. There are some rare
cases of messages that are never to be acknowledged – for example the confirmation messages
themselves (ACK, NAK).

In order to prevent the possibility of incorrect communication due to hardware related faults the con­firmation messages of the command station and PC are different.

Page 28 COMMAND STATION MX1, MX1HS, MX1EC

4.5. Reply to message 9 (command station query)

This is a long frame level 1 reply. The returned data (following the header bytes) includes the follow­ing information:

Byte number Value Description

1 cAddress_h unique (CAN-)address high byte
2 cAddress_l unique (CAN-)address low byte
3 cDevice device – ID
4 cRom_size ROM size of command station [32k –pages]
5 cRam_size RAM size of command station [32k –pages]
6 cPrintver_h print version main number
7 cPrintver_l print version sub-number
8 cVerison_h sw-Version main number
9 cVersion_l sw-Version sub-number
10 cDate_day sw-date day
11 cDate_month sw-date month
12 cDate_century sw-date century
13 cDate_year sw-date year
14 cSwitches switches
15 cDevelopVersion 00 Release or ASCII-pre-release versi ons (“a“,“b“..)
16 cBootRom_h boot ROM version main number
17 cBootRom_l boot ROM version sub-number
18 cBootRom_develop 00 boot ROM release or ASCII-pre-release versio n

(“a“,“b“..)

meaning of the device-ID:
device – ID device
1 MX1 2000 / HS
2 MX1 2000 EC

4.6. Address format specification

For messages:

Bit 7 Bit 6 Description

0 0 use protocol last used with this address
1 0 force DDC protocol
0 1 force Motorola protocol
1 1 reserved

For replies:

Bit 7 Bit 6 Description

0 0 not used
1 0 address uses DDC protocol
0 1 address uses Motorola protocol
1 1 reserved

4.7. Speed step system

The speed system bits are only meaningful for loco addresses using the DCC protocol.

For messages:

Bit 3 Bit 2 Description

0 0 use speed system last used with this address
0 1 force 14 speed steps (0-14)
1 0 force 28 speed steps (0-28)
1 1 force 126 speed steps (0-126)

For replies:

Bit 3 Bit 2 Description

0 0 not used
0 1 address uses 14 speed steps (0-14)
1 0 address uses 28 speed steps (0-28)
1 1 address uses 126 speed steps (0-126)

COMMAND STATION MX1, MX1HS, MX1EC Page 29

4.8. additional return code to a message

The reply to message 0x0A inherits an additional return code. This return code reflects the logical er­ror-status of the sent message. If the message is transmitted correctly but there is a logical error
within the message that prevents the command station from executing it, then the codes below indi­cate the error.

Return code Value Description

NO_ERROR 0x00 no error within the request
ERR_ADRESSE 0x01 not a valid address
ERR_INDEX 0x02 error with index of extended address
ERR_BUSY 0x04 The command station is busy with an other ac-

cessory decoder command
ERR_NO_MOT 0x05 Motorola jumper off
ERR_NO_DCC 0x06 DCC jumper off
ERR_CV_ADRESSE 0x07 not a valid CV address
ERR_SECTION 0x08 not a valid section
ERR_NO_MODUL 0x09 module with given address doesn’t exit

4.9. Reply to message 0x0A, codes 1, 2, 3, 4

If there is no error within a request, the level 1 acknowledgement contains additional information. If
the track status is not in normal operational mode, bit 0 is set. In this case the actual track status can
be determined via the track control message.

Header byte Value Description

1 0-255 unique sequence-ID
2 3 reply level 1 – short frame
3 xxx sequence-ID of the message being replied to
4 0 no error within the request
5 ff00ss0t

ff used format specification (see
ss used speed step system (see

t track status (0: normal operation, 1: fault)

4.6)

4.7)

4.10. Reply to message 0x0A, code 5

If there is no error within the request, the level 1 acknowledgement contains additional information. If
the track status is not in normal operational mode, bit 0 is set. In this case the actual track status can
be determined via the track control message.

Header byte Value Description

1 0-255 unique sequence-ID
2 3 reply level 1 – short frame
3 xxx sequence-ID of the message being replied to
4 0 no error within the request
5 ff00000t

ff used format specification (see
t track status (0: normal mode, 1: fault)

4.6)

Page 30 COMMAND STATION MX1, MX1HS, MX1EC

4.11. Reply to message 0x0A, code 6 (query command station loco memory)

If there is no error within the request, the level 1 acknowledgement contains the requested data. If
logging is activated for a loco address, this message is sent spontaneously as level 2 acknowledge­ment and the sequence-ID of the message being “replied to” is set to zero.

Header byte Value Description

1 0-255 unique sequence-ID
2 3 (5) reply level 1 (level 2) – short frame
3 xxx (0) sequence-ID of the message being replied to
4 0 no error within the request
5 cAdr_hi address high byte

bit 6 + bit 7 format specification (see 4.6)

6 cAdr_lo address low byte
7 cSpeed Speed step of the current speed step system

(DCC data signal: 0-14, 0-28 or 0-126; according to bit 3/2 in
cData1;MOTOROLA protocol: 0-14)

8 cData1 bit 7: MAN (override signal controlled speed limit)

bit 6: no function
bit 5: direction (0 = forward, 1 = reverse)
bit 4 headlights on/off (= DCC function F0)

bit 3/2 DCC speed step system (see Speed step system

4.7)

bit 1 decel. time “BZ” (definable by command “B”) on/off
bit 0 accel. time “AZ” (definable by command “B”) on/off

9 cData2 bit 0-7: function outputs 1-8 on/off (DCC only)
10 cData3 bit 0-3: function outputs 9-12 on/off (DCC only)
11 cAzBz bit 0-3: BZ (0 - 15)

bit 4-7: AZ (0 - 15)

12 cStatus 1 … address is active

4.12. Reply to message 0x0A, code 7

(query command station accessory decoder memory)

If there is no error within the request, the level 1 acknowledgement contains the requested data.

Header byte Value Descrip tion

1 0-255 unique sequence-ID
2 3 (5) reply level 1 (level 2) – short frame
3 xxx (0) sequence-ID of the message being replied to
4 0 no error within the request
5 cAdr_hi address high byte

bit 6 + bit 7 format specification (see 4.6)

6 cAdr_lo address low byte
7 cPair 0 … paired output function

1 … single output function

8 cOutputs state of the 8 outputs

4.13. Reply to message 0x0A, code 8 (address control)

Header byte Value Description

1 0-255 unique sequence-ID
2 3 reply level 1 – short frame
3 xxx sequence-ID of the message being replied to
4 0 no error within the request
5 ffa0sskl

ff used format specification (see
a 1: accessory address 0: loco address

ss used speed step system (see

4.6)

Speed step system

4.7)

k lock address if bit is set (no external changes)
l log external changes if bit is set

COMMAND STATION MX1, MX1HS, MX1EC Page 31

4.14. Reply to message 0x0A, code 9 (read command station)

Header byte Value Description

1 0-255 unique sequence-ID
2 3 reply level 1 – short frame
3 xxx sequence-ID of the message being replied to
4 cCurrent1_h current output 1 - integer
5 cCurrent1_l current output 1 - fraction
6 cVoltage1_h voltage output 1 - integer
7 cVoltage1_l voltage output 1 - fraction
8 cCurrent2_h current output 2 – integer (0 for MX1_EC)
9 cCurrent2_l current output 2 - fraction (0 for MX1_EC)
10 cVoltage2_h voltage output 2 - integer (0 for MX1_EC)
11 cVoltage2_l voltage output 2 - fraction (0 for MX1_EC)
12 cAux auxiliary inputs

4.15. Reply to message 0x0A, code 10 (read/set a CV of the command station)

Header byte Value Description

1 0-255 unique sequence-ID
2 3 reply level 1 – short frame
3 xxx sequence-ID of the message being replied to
4 0 no error within the request
5 cValue value of the CV

12 cOutput3 The bits 0-7 represent the module outputs 24-31. For paired

outputs (starting at output 0), the odd bits are meaningless.

Reply: Ack (level 1)

In cases where the command station receives no data from the specified accessory module or the
reply doesn’t contain any data

Header byte Value Description

1 0-255 unique sequence-ID
2 5 reply level 2 – short frame
3 ID sequence-ID of the message that is being acknowledged

Reply: Ack (level 1)

A new query of accessory module outputs cannot be started until the previous query is finished. In
case there is an unfinished query, a level 1 reply is shown with additional information according to
the active query.

Header byte Value Description

1 0-255 unique sequence-ID
2 3 reply level 1– short frame
3 xxx sequence-ID of the message being replied to
4 xxx unique sequence-ID of the message that requested the query
5 MX8_ID MX8 address (1-63 not 801-863) that is actually searched for

Reply: n.a.

4.16. Reply to message 0x17, code 4 (query accessory module outputs)

In a first step, the usual level 1 acknowledgment follows. The received data is forwarded as a level 2
reply with short frames. The data of the frame includes the following information:

Header byte Value Descrip tion

1 0-255 unique sequence-ID
2 5 reply level 2 – short frame
3 xxx sequence-ID of the message that is being acknowledged
4 cTime0 pulse-time 0 (CV 515)
5 cTime1 pulse-time 1 (CV 516)
6 cTime2 pulse-time 2 (CV 517)
7 cTime3 pulse-time 3 (CV 518)
8 cpaired Number of paired outputs (0,16,32)
9 cOutput0 The bits 0-7 represent the module outputs 0-7
10 cOutput1 The bits 0-7 represent the module outputs 8-15.
11 cOutput2 The bits 0-7 represent the module outputs 16-23

4.17. Additional data flow information

The fourth header byte of long data frames contains additional data flow information besides the
length of the header (original length without counting escape character prefixes). This information
describes whether there will be any consecutive frames with data.

Flow information in dd Description
00 no more data to come
01 more data will follow
10 more data will possibly follow

4.18. Reply to message 0x15, code 3

header byte value description

1 0-255 unique sequence-ID
2 0x3 reply level 1 – short frame
3 xxx sequence-ID of the message being replied to

(read the track section module’s occupancy state)

Page 32 COMMAND STATION MX1, MX1HS, MX1EC

4 0 No error within the request
5 B-Status0 occupancy state of main section 0

V C S B A T T T
V: data valid
C: changed (since last transmission)
S: short circuit (main section off)
B: section B occupied
A: section A occupied
T T T: number of recognized loco numbers (0-4)

6 B-Status1 occupancy state of main section 1
7 B-Status2 occupancy state of main section 2
8 B-Status3 occupancy state of main section 3
9 B-Status4 occupancy state of main section 4
10 B-Status5 occupancy state of main section 5
11 B-Status6 occupancy state of main section 6
12 B-Status7 occupancy state of main section 7

4.19. Reply to message 0x15, code 4

header byte value description

1 0-255 unique sequence-ID
2 0x3 reply level 1 – short frame
3 xxx sequence-ID of the message being replied to
4 0 No error within the request
5 Section main section number (0-7)
6 B-Status occupancy state of main section 0

7 F-Status current speed limit (H=0, U=1, L=2, F=3, A=4, HU=5, UL=6, LF=7)
8 Zugnr1_H optional: 1. loco number high byte
9 ZugNr1_L optional: 1. loco number low byte
10 ZugNr2_H optional: 2. loco number high byte
11 ZugNr2_L optional: 2. loco number low byte
12 ZugNr3_H optional: 3. loco number high byte
13 ZugNr3_L optional: 3. loco number low byte
14 ZugNr4_H optional: 4. loco number high byte
15 ZugNr4_L optional: 4. loco number low byte

(read the track occupancy state and loco numbers of a main section)

V C S B A T T T
V: data valid
C: changed (since last transmission)
S: short circuit (main section off)
B: section B occupied
A: section A occupied
T T T: number of recognized loco numbers (0-4)