ZIMO StEin User manual

StEin Stationary Equipment Module Page 1
StEin -INSTRUCTION MANUAL
short for
StEin
(= Stationary-Equipment) - Module
and
StEin expansion boards
Note: A separate instruction manual
will cover the external ICA boards
(via I2C bus).
EDITION
Preliminary Edition 2017 12 18
2018 01 02
2018 02 06
2018 05 13
1018 06 11
2018 06 19
2018 06 27
2018 07 20
2018 08 21
2018 10 20
2018 11 10
2018 11 30
2018 12 05
2018 12 15
2019 02 14

Page 2 StEin Stationary Equipment Module
CONTENTS
Chapter
Page
Product features and system configurations................................................................................ 4
1. Setup technical data, “StEin” configuration-strategy ............................................................... 6
2. Self-Update and Loading conf., sound and other data ........................................................... 11
3. The “button-procedures” for “manual operation” .................................................................... 12
4. Monitoring and operating with the MX32................................................................................ 14
5. The 8 Track Sections, Overcurrent and Short circuits............................................................ 15
6. Track sections, point detectors, point following commands.................................................... 18
7. Terminal loops....................................................................................................................... 19
8. The 8 outputs for8 turnouts / 16 Single consumers................................................................ 20
9. The speaker outputs of the StEin........................................................................................... 21
10. The Signal Boards at the I2C Bus ........................................................................................ 21
11. The Track Section Expansion Boards.................................................................................. 21
12. The Turnout Expansion Boards........................................................................................... 21
13. The Servos Expansion Boards ............................................................................................ 21
14. Prepared configurations and their activation........................................................................ 22
15. Description of the objects in the parameter sheets .............................................................. 24
16. Configuration Example (ZIMO N-Scale Show Layout) ......................................................... 31
17. APPENDIX: Glossary.......................................................................................................... 35

StEin Stationary Equipment Module Page 3
Notes to software versions and instruction manuals
This page is under construction
SOFTWARE and SOFTWARE-UPDATES:
To learn more about the current software version and to download a free copy, go to the ZIMO
website www.zimo.at and click on the tab “Update & Software” (“Update – System”).
General information:
ZIMO devices should not be installed in moisty or overheated locations. The air flow
must not be restricted (e.g. by covering) when in operation.
The wiring should not be squashed or put under tension. A tight fit of all connectors
is a prerequisite for faultless power or data transmission.
The devices should not remain under power unattended, i.e. the power supply (or
power supplies) should be disconnected from the power grid, ideally via a switchable
power bar or by pulling the plug from the grid.
Children under 8 years should use the equipment only when accompanied by an
adult.
The improper use or opening of the equipment without prior agreement may lead to
the loss of warranty.

Page 4 StEin Stationary Equipment Module
Product features and system configurations
“StEin”- Modules (Stationary-Equipment-Modules) are ZIMO DCC components that are
designed to work together with a ZIMO command station MX10; with limitations also to-
gether with one of the older MX1 command stations, but for the time being NOT with
THIRD PARTY SYSTEMS.
As the name implies, all kinds of “stationary equipment” found on a model railroad can
be connected to the “StEin” module, above all, track sections, accessories such as
switches, signals, uncouplers, point-detectors and speakers.
The operation and control of fully equipped track sections (with occupancy detection,
loco number recognition, local or global RailCom, short-circuit handling as well as the
ZIMO feature “HLU” for the “signal controlled speed influence”) is the central task of the
“StEin”.
The detector inputs on the “StEin” are most often (but not exclusively) used with track
sections, which complements the principle of train influence (placing speed limits on sec-
tions of track using the HLU method) by adding precise local train control (by using point
detectors such as track contacts, reed switches, infrared sensors etc.).
A partially functional alternative is the Roco “Z21 occupancy detector with RailCom” (manufac-
tured by ZIMO) for limited applications (i.e. when HLU is not needed).
The “StEin” is also an affordable alternative for accessory control to the normally used
stationary decoders (because those functions are included at no extra charge): The
“StEin” offers a number of functional advantages such as power supplied independently
from track power and the CAN bus as a powerful control and feedback path.
Using the “StEin” with the current ZIMO system, MX10 and MX32:
The minimum requirement for using the "StEin" consists of the MX10 command station
and the StEin module itself (or several modules). For reasons of operability, however, at
least one MX32 cab (later MX33) should be at hand, and usually a computer is also used
in connection with StEin applications.
HOW THE PIECES ARE CONNECTED TOGETHER IS ILLUSTRATED ON THE NEXT PAGE,
with explanations below:
-The “StEin’s” power supply for the track and accessory outputs:
A special feature of the "StEin"-concept is the origin of the DCC signal at the track out-
puts: "StEin" modules operate as boosters, which means, the DCC signal for both rails
("P" and "N") is generated by the module itself and synchronized with the outputs of the
command station (via the wires 7 and 8 on the extended CAN bus cable).
In contrast to this, the typical occupancy detectors on the market (including the Z21 occupancy and
RailCom detector manufactured by ZIMO) pass the signal through from the command station. Also the
“old” ZIMO track section modules MX9 work like that.
Therefore: The power amplifier of a track output of a “StEin” module is fed with DC power
that is applied to the terminal “+ track power” (and GROUND), not by the track output
of a command station. This DC voltage can easily be taken from the “DC-out” connection
(usually S1) of the MX10 command station, but can also be taken from an external inde-
pendent power supply.
Accessories connected to the “StEin” module (turnouts, signals etc.) are also supplied with
DC voltage, which is connected to the terminal “+ Accessory power” (and GROUND).
This is usually supplied by the output “DC-out” S2 from the command station and there-
fore separated from track power, but that is not mandatory: it could also be connected to
track power or an external power supply.
It is often the case that all the power (track power and accessories) is supplied by the MX10,
in which case a 3-conductor cable (2.5 mm2diameter suggested) is connected between the
3-pin socket on the MX10 (“DC-out”: S1, GROUND, S2) and the
3-pin socket on the “StEin” (+Track power, GROUND, +Accessory power).
(See schematic on next page)
-The input/output connections of the STEIN88V module:
8track section connections, with up to 8 A load capacity each (suitable for large-scale
trains) and occupancy detection from as little as 1 mA current draw (corresponding to an ax-
le resistor of 10 –20 KOhm),
short circuit detection and shutdown with adjustable thresholds and times,
local RailCom (address recognition) and global RailCom (receiving and forwarding of
complete reports on “channel 2”),
ZIMO HLU speed limits in 7 steps with function influence and location detection,
ZIMO ACKs for loco number recognition (alternative and complementary to RailCom).
8 turnout connections (double coil, motorized…) with extensive position and speed control,
also usable for 16 single connections such as uncouplers, lights etc.
16 logic level inputs for all kinds of sensors: rail contacts, photoelectric sensors etc.
1 I2C bus connection, for 16 signal or other boards mounted close to the accessory it-
self (signals: each board can supply 16 LED’s or several multiple signals),
2 speaker outputs for station announcements and similar, from the StEin’s internal sound
generator,
2 connectors for expansion boards (for more turnouts, servos etc.).
-Other “StEin” facilities:
The "StEin" is equipped with a numeric display (for displaying the module number and as
support for manual setup) as well as numerous control LEDs: occupancy status, short cir-
cuits, HLU status of each track section, input states, switching operations, various internal
voltages and operating states.
The 5 buttons are mainly used for manual module settings, for example: fixed HLU settings
on track sections (e.g. "slow" or "stop"), later also for automatic dependencies (such as
block control or hidden stations) but also for restarting after short circuits and turnout test-
ing etc.
The USB drive socket is used for software updates of the StEin module, but also to
load configurations that are created on external sheets; possibly also to load sound
files.
Using the “StEin” with the “old” ZIMO System, MX1 and MX31:
WILL BE ADDED LATER
ATTENTION: this 3-conductor cable is to connect “Pin 1 to pin 3 and pin 3 to pin 1“
(NOT 1:1).
ööööööööööööööööööööööööööööööööööööööööööööööööllll
siehhhhh
ATTENTION: do NOT use “Schiene 2” (track 2) for the programming track in SER-
VICE MODE, if “DC out S2” is used for StEin accessory power.
ööööööööööööööööööööööööööööööööööööööööööööööööllll
siehhhhh

StEin Stationary Equipment Module Page 5
In the example shown above, all the power for the layout’s track and accessories
is supplied by the MX10 command station (actually the power supply unit up-
stream) from the pins “S1” and “S2” of the “DC out” socket, but also the
DCC power amplifier of the MX10 track outputs “Schiene 1” or “Schiene 2”.
Cab MX32(FU) or
MX33(FU) tethered
CAN bus (6-pin)
To computer
(if system and StEin module is to work to-
gether with a dispatcher program)
6-pin CAN bus cable to the front
MX10 CAN socket
8-pin network cable
to the rear MX10
LAN socket
CAN bus (8-pin)
8-pin CAN bus cable (network cable de-
sign) to the rear MX10
CAN socket
Turnout connec-
tions
1 … 8
Logic inputs
1 … 16
Servo
connections
1 … 8
planned
planned
MX10 command station back side
StEin extension boards
planned
StEin module STEIN88V
Turnout connec-
tions
1 … 8
Logic inputs
1 … 16
2 x Speaker
I2C Bus for
signals
8 Signal lights
8 Signal lights
8 Signal lights
8 Signal lights
8 Signal lights
8 Signal lights
Up to 16 ICA boards
per “StEin”
Connect the I2C bus in a daisy
chain as shown (NOT in parallel)
Additional StEin Modules
STEIN88V and STEIN80G
Isolated rail sections: connected to the StEin outputs
marked “P”.
Continuous rail: connected to the StEin output marked
“N” or the MX10 output “N”.
Track outputs 1 … 8:
for common “N-rail” and
individual “P-rail” sections
All “N” pins are
internally parallel
To track 2
(Programming track)
ATTENTION: The DCC output “Schiene 2” is supplied by the same pow-
er source as the output “DC out S2”, which in this application example is
also used for the StEin to control turnouts and signals.
Therefore, the voltage and short-circuit handling is the same.
DC out S2
(for accessory power;
which
the StEin uses to operate turnouts etc.)
To track 1,
for layout track that is NOT
connected to StEin modules.
Common GROUND
(= System ground)
DC out S1
(Track voltage;
from this the StEin produces the DCC signal for the track outputs
1 … 8, the same way as the MX10 does for the “Schiene 1” output
Power Supply
Alternatively, a separate power supply can be
used to power accessories
from MX10
command
station
Common GROUND
(= System ground)
DC out S1
(Track voltage)
Accessory power from a ded-
icated power supply (i.e.
NGULF);
which the StEin uses to
operate turnouts etc.
to the StEin
to the StEin
In the example shown above, all the power for the layout’s track and accessories is
supplied by the
MX10 command station (actually the power supply unit upstream) from the pins “S1”
and “S2” of the “DC out” socket, but also the DCC power amplifier of the MX10
track outputs “Schiene 1” or “Schiene 2”.
In other more elaborate setups (e.g. if boosters are added) the "Power and Distribu-
tion Board" MX10AVP is used.

Page 6 StEin Stationary Equipment Module
1. Setup technical data, “StEin” configuration-strategy
“StEin” data model
Socket for USB-stick
for software update
and to load/save the configura-
tion data
2 CAN bus sockets to connect
with the MX10 command sta-
tion (only to the rear
CAN bus socket) and to the next
module
Only if it‘s NOT an MX10:
Track P N for synchronisation
3-fold screw terminal to
supply with running voltage
and accessory voltage: NOT on
output “Schiene” of the MX10,
bur “DC out”
Connections (or individual)
power supply units, max. 24 V)
Jumper to switch the supply of
the internal circuits (microcon-
troller, memory, etc), if desired
from the accessory voltage
(usual case) or from the higher
voltage (ACC or LOCO)
Connection (pin connector)
for
Expansion board 1
Connection (pin connector)
for
Expansion board 2
Speaker outputs
Display for module number und local
operation (buttons)
I2C - Bus to the signal board
8 turnout outputs (coils,
motor, EPL) or 16 single
consumers (e.g. uncoupler);
included in the 20-pin plug:
auxiliary voltages 5V and accessories
16 inputs and LED-indicators for point
detectors, photoelectric sensors, turn-
out feedback and more.
Note: brown letters mean taht the
connections are only available on
STEIN88V, but not on STEIN80G.
Buttons and LED indicators for local
operation and adjustment of config-
uration parameters
8 track section outputs on four 3-pin sockets, each with 2 “P” (“Positive rail”) and 1 “N” (“Negative rail”) connection.
For each section: HLU (red/yellow/green), occupancy (yellow), short circuit (blue).
CAN-Bus Control-LED:
Green flashing 1 Hz = up to 25/sec messages
2 Hz = up to 100/sec received
5 Hz = up to 250/sec
10 Hz = more than 250/sec
Red flashing = CAN transmission in flashing period
DCC signal control LED:
Green flashing 2 Hz = ok
Green/Red flashing = wrong polarity
(only possible if DCC via track)
Red flashing = NO DCC (HLU is not possible)

StEin Stationary Equipment Module Page 7
T E C H N I C A L D A T A :
Power for
Track (DC-out “S1” or “S2” from ZIMO MX10 or separate power supply) …………..….….. 12 - 24 V
Accessory voltage (DC-out “S1” or “S2” from ZIMO MX10 or separate power supply) …….. 12 - 24 V
CAN bus (usually from the MX10 or MX1 CAN bus socket) ……………................................. 12 - 35 V
Output current
on single track outputs (necessarily automatic short circuit switch-off) ................................. 8 A
total current of all 8 track outputs ………........................................................................... 10 A
for each turnout output (or other components) ……………………….………..………………… 2 A
total current of all 16 turnout outputs ................................................................................ 5 A
for the 5V auxiliary output .………………………..………………………………………………... 1 A
Others:
Minimum current flow at the track for reliable occupancy detection …….…………..…………... 1 mA
(the occupancy threshold can be set higher than 1 mA in the configuration data)
Internal consumption of the StEin from track and accessory voltage .......................................... 350 mA
Internal consumption from the CAN bus voltage (if not supplied by track or accessory) ….……. 150 mA
Dimensions ……..……………………………………………………………….………. 180 x 120 x 20 mm
The “HLU” - technique - also known as “signal controlled speed influence” and “location dependent
function control” - is integrated in ZIMO digital systems and ZIMO decoders *).
HLU is a communication protocol from one track output of the StEin module (former MX9 track sec-
tion modules) to the decoder located on the track section; HLU data can be different from one track
section to another (e.g. regarding HLU steps), they do NOT have addresses and are read individually
by each ZIMO decoder (and decoders of some other manufacturers).
HLU data usually contain commands to stop trains or reduce their speed to one of the 7 HLU steps;
see list above. HLU data reaches the decoders practically immediately, because it is sent out about
100 times/sec. For the track section outputs of the StEin, the interlocking program (on the computer)
usually sets HLU steps.
Similar to the central command station MX10, the StEin possesses high quality RailCom detectors,
however, 8 of them (for each of the 8 track sections). The analysis of the feedback from the vehicles
allows, for example, to show the position of a train on the controller and the interlocking program, or to
show the layout-dependent direction East-West.
Note to S E T T I N G S O F T H E M X 1 0 when using StEin modules
StEin modules have overcurrent and short circuit detection for every track section output; also see
chapter “The 8 track sections, overcurrent and short circuit”; here a short description:
In the “Parameter sheet”, every track section can be defined individually regarding overcurrent and
short circuit handling, whereby generally it is not very useful to set too many differences between the
track sections. Overcurrent (typical values between 1 and 3 A in parameters UESLAMP and
UESSAZT in the object lines of the track sections) leads to a delayed switch-off (in parameters UES-
LAZT and UESSAZT = turn-off time), in case of short circuits (typical threshold 4 to 8 A according to
KUSAMP) it turns off immediately; in both cases there is a number of automatic restarts (in parame-
ters UESLEAZ, UESSEZ, KUSEZT) after which the system is finally turned off.
The goal of these settings and procedures is that only the one track section is turned off, on which an
overcurrent or short circuit occurs. On the other hand, it would be wrong, if the supply of the running
voltage from the MX10 (to which the StEin modules are connected) would be turned off entirely in case
of an overcurrent or short circuit on a track section. To avoid such misconduct, certain rules have to be
complied with regarding “Voltage & Current”, namely the values for “OVC threshold” and “OVC turn-off
time”, sometimes also “OVC tol. current” can be used. All these settings are entered via the main menu
“VOLT & AMPERE detail”, and have to be set for the corresponding track output (1: or 2:) *).
Highest value for the turn-off parameters UESLAZT / UESSAZT Useful value
in the object lines for the track sections for “OVC turn-off time” in the MX10
100 ms (to write into the StEin object), means 0.1 sec 0.3 sec
200 ms (to write into the StEin object), means 0.2 sec 0.5 sec
500 ms (to write into the StEin object), means 0.5 sec 0.8 sec
700 ms (to write into the StEin object), means 0.7 sec 1.0 sec
The “OVC threshold” in the MX10 shall follow the following criteria:
1) according to the expected current consumption on the layout (or on the track output),
2) but at least the 2.5-fold of the higher overcurrent parameters UESSAMP
in the object lines of the track section. *)
*) Technical description added to the above described rules (especially the turn-off times):
Contrary to the track outputs of the central command station MX10, the outputs of the StEin do not
have a constant current regulation, which would bridge the time until the turn-off (the turn-off time).
The StEin hereby relies on the MX10; i.e. when exceeding the overcurrent threshold (according to
parameters UESLAMP or UESSAMP, as far as the current stays beneath the threshold for short
circuits KUSAMP) the current continues to flow in the amount provided by the output of the MX10
(according to “OVC threshold”). The track output of the MX10 thereby goes into its own turn-off ac-
cording to “OVC turn-off time” - therefore the value has to be set considerably higher than the over-
current turn-off times UESLAZT and UESSAZT in the StEin, so the StEin output turns off faster and
the rest of the layout is not affected.
HLU
H Halt
UH Zwischenstufe
U Ultralangsam
LU Zwischenstufe
L Langsam
FL Zwischenstufe
F Volle Fahrt
(A Spannung AUS)
5
L
i
m
i
t
s
7
S
t
u
f
e
n
RailCom ist ein Markenzeichen der Lenz Elektronik GmbH
im StEin

Page 8 StEin Stationary Equipment Module
The “StEin Configuration Strategy - Parameter sheets in Excel files”
This sub-chapter is an overview and does NOT contain all the information needed to cre-
ate a configuration data sheet. Detailed descriptions can be found further in this manual.
The numerous connections of the "StEin’s stationary facilities" (for track sections, turn-
outs, signals, etc.) can be used very flexibly, from N-scale layouts to garden railways.
The “StEin” modules are adapted through these "configurations" (= the setting of a
variety of parameters) to the particular circumstances and operational requirements.
No special computer tool is needed to configure the "StEin". In some cases it is enough
to have a configuration which is produced from a list of prestored “prepared configura-
tions”; this is also very useful for first start-ups; see description later in the manual.
The general method nonetheless is the “parameter sheet”, prepared by the computer
with a spreadsheet application, usually Excel (use of other programs possible but not
verified) which exports the “binary configuration file” to load it into the StEin module
via flash drive (or via LAN to the command station and via CAN to the modules).
Excerpt of a parameter sheet: some object lines for turnouts (not all columns are shown here); this
screenshot is for illustration only, no "meaningful" data shown
Due to the fact that the configuration can be changed during operation (interlocking pro-
grams and users may change parameters), the modified binary configuration can be read
out from the StEin module (saved on a flash drive) and imported into Excel, so a new
parameter sheet can be produced.
In sum, there are the following “conversion ways”:
Create a parameter-sheet on the computer and load > operable binary configuration
Create a prepared configuration via StEin buttons > operable binary configuration
Binary configuration file, from prepared configurations
created, read out > parameter sheet for further editing
Binary configuration file, in operation by interlocking program
modified, read out > new parameter sheet for further editing
The “parameter sheet”, as well as the corresponding “binary configuration” consists of a
list of “object lines”, complemented by cells with freely editable headlines and com-
ments. Each object line contains parameters for the respective "object" (turnout, track
section, signal, etc.); the meaning of each parameter depends on the type of object. But
among them is always (at least) the object’s connection point at the StEin; in the case of a
turnout, the turnout output number, which by the way does not necessarily have to be at
the same “StEin” module (on which the object line resides).
Excerpt from a parameter sheet: shown are some object lines for track sections (in this screenshot
most of the parameters correspond to the template GAZIMEN18 (therefore many fields use the same
content as above indicated with "), deviating values are entered in some fields. Note: some columns
are not shown in this excerpt due to lack of space, so that the important APUGA column is visible, which
shows the connection points for the track sections.
There are a certain number of parameters for each individual object (usually between 10 and
20), which, depending on the object type, include occupancy detection and overcurrent
thresholds with their associated response times, switching times, feedback properties, short-
circuit handling and more.
This organization is referred to as "object-oriented" (rather than "address-oriented") because there is
one row (one record) for each object (track, switch, etc.), not for every connection on the module (ad-
dress). The link between the object and its connection point(s) is made by parameters in the object line
(e.g., track output numbers or pins for the turnout drive).
Various methods have been prepared to make the creation (“filling in”) of parameter
sheets, which may already include hundreds of objects with thousands of parameters, even
for a medium-sized layout, fast, easy and clear (not every parameter must be typed indi-
vidually…).
The "prepared configurations” (already mentioned above, more details in this document):
For the connections on the StEin module (e.g. the 8 turnouts and the 8 track sections),
there are several sets of object lines with parameters suitable for typical applications; i.e.
for 8 typical HO double coil turnouts or for 8 motorized switch machines, or for track sec-
tions of an HO typical layout or a garden railway, etc. each with different variations.
The prepared configurations can be activated either directly on the module (using the
buttons on the "StEin"), but they are also available for download and use within a sepa-
rate parameter sheet, where they can of course be adapted as needed.
One of the available prepared configurations: 8 track sections with "normal" values for HO application:
each of the 8 track outputs of the StEin is used for an identically configured section,
the APUGA column (track section connection point; some center columns are missing in this illustration
to make the APUGA column visible) contains entries such as M.3, where "M" is replaced by the number
of the module the finished configuration is loaded into.

StEin Stationary Equipment Module Page 9
In addition to the lines for specific objects, a parameter sheet may contain lines for
object types; these are templates for the subsequent specific object lines, i.e. the specif-
ic objects which take over the parameters of the object types in every box they have de-
fined “ . Such lines (GATYP ...) are already used in the above examples; here is another
one:
This section of a parameter sheet defines two object types (some for double-coil turnouts with certain
parameters, and others for motorized switch machines), which are then assigned to the actual turn-
outs by specifying the name of one of these types..
Using the capabilities of the Windows Office Excel program, such as the copy and
search functions, the ability to apply color shading and much more, makes the creation
of parameter sheets more efficient and more manageable.
Examples of marked areas in the parameter sheet and highlighted lines
in the Excel sheet (without special meaning)
A parameter sheet may contain one or several or all StEin modules on the layout; it is
not absolutely necessary to create a separate parameter sheet for each module. It offers
the ability to group some modules together in one parameter sheet. The same file is
then loaded into each StEin module; each module only picks the proper lines (according
to the parameter MODULNR).
An example is shown here of a parameter sheet that contains object lines for multiple StEin
modules. For easier identification we added the additional column MODULNR to the usual col-
umns (see above), which holds the module number for which this line is determined.
Among the parameters of all object lines is also the "system-wide object number", e.g.
GASYNR, WEISYNR, etc. Here, the user can number track sections (this does NOT hap-
pen automatically), turnouts, signals, etc. of the whole layout. Using these numbers,
the interlocking program will then be able to access these objects (provided the soft-
ware has that capability) regardless of which StEin module (or type of StEin module)
an object is actually connected to.
In cases the module was sent in for reparation, a reconfiguration will not be necessary,
and it is even possible to design a layout without the exact knowledge of the modules
to be used (i.e. which types will be available at the start of construction).
: Plausibility control in the module (largely planned for future software versions) of the
configuration when loading them into the “StEins”
"System-wide object numbers" are assigned to these objects (track sections). The object line for the
GATYP has no object number; it applies automatically throughout the system.
CHAPTER REGARDING EXPORTING FROM EXCEL
WILL BE ADDED LATER
separators , and ; are allowed

Page 10 StEin Stationary Equipment Module
T h e “S t E i n” D a t a m o d e l
Non-volatile
memory
Active
configuration in
binary code
Program memory
Current software
in the
microcontroller
of the
StEin module
XILINX Chip
(programmable
logic)
Modifications of
parameters
using the StEin’s
buttons and dis-
play
Modifications of
parameters using
a computer
(with interlocking
programs) or
input device.
Software Update
Code letter when loading: “b”
StEin’s
USB socket
or via
CAN bus
.bin file
(StEin Software)
.svf file
(XILINX Data)
StEin’s
USB socket
or via
CAN bus
Code letter when loading: “u”
The clear text
configuration is
converted to a bina-
ry format so it can
be used in opera-
tion.
If the binary
configuration gets
modified, a new
clear text
configuration
(Paramenter sheet)
will also be created.
Active
configuration in
clear text,
that is the
ready
parameter sheet
or the
parameter sheet
made from
prepared con-
figurations
or the
newly modified
parameter sheet
Prepared
configurations,
pre-recorded
object lines,
i.e. choose from
several groups of
8 track sections
each.
StEin’s
USB socket
or via
CAN bus
StEin’s
USB socket
or via
CAN bus
StEin’s
USB socket
or via
CAN bus
StEin’s
USB socket
or via
CAN bus
StEin’s
USB socket
or via
CAN bus
Code letter when loading “c”
Code letter when loading: “F”
Code letter when loading: “s”
.cfg file
(Parameter sheet)
.cfe file
(Err.Param-sheet)
.cfm file
(Mod.Param-sheet)
.cff file
(Pre-finished conf)
.snd file
(Sound samples)
Selection of
prepared blocks of
configurations us-
ing the buttons and
display on the
StEin.
together with
software update
Loading the Configurations into the StEin:
The list of the object lines for the StEin
Module is called parameter sheet. This
sheet is created with the program Excel.
Exporting from Excel creates a .cfg file,
which can then be uploaded to the StEin.
Configuration data output by the StEin:
Err.Param-sheet: Details about incorrect in-
formation in the parameter sheet, in the
same format and layout.
Mod.Param-sheet: The parameters of the
original sheet can be edited using local in-
puts on the StEin or via interlocking pro-
grams. From that, a new parameter sheet
will be created for possible further editing.
Prepared configurations as alternative:
For a quick start-up or a permanent solution
for smaller applications, select groups of
object lines (i.e. 8 turnouts) that are already
in the software at the time of delivery (but
can be exchanged later with .cff files).
The so composed object lines can also be
converted to a Mod.Param-sheet and read-
out for external editing (see above).
Loading Sound:
Sound projects are created and loaded simi-
larly to sound decoders.

StEin Stationary Equipment Module Page 11
2. Self-Update and Loading conf., sound and other data
Of course, the software of the "StEin" module (like any ZIMO product) can be updated,
that is, new software versions can be installed as soon as they are available.
In addition to the software, there is a number of other data that must be loaded in the
form of files and sometimes also be read out: data for XILINX, configuration, sound.
Basically, all downloads are done either from the flash drive or (in a later software
stage) directly from the computer via the LAN port of the MX10 and from there to the
modules and the CAN bus.
Usually many StEin modules are in use on a layout, and therefore the updating procedure (and al-
so loading new configuration) would be very complicated if it had to be done for every module
separately.
Therefore, the StEin concept offers to load all modules on one layout simultaneously (new
software or configuration), in connecting the flash drive on one module (of your choice), which
then distributes the data to all other modules.
CONTROLLED PERFORMANCE (with “next”-buttons in the proce-
dure):
Starting point: Start in the normal state = Module number shown in the display, i.e.: 
Plugging in the flash drive for example 
This means: the first sign (in this case “3”) = the number of files for the
StEin on the drive; the second sign (in this case “b”) = the type of the first file.
“b” means that the file about to be loaded is a .bin file, which is a new software,
“c” …. is a .cfg file, which is a new configuration,
„n“ …. is a .snd file, which are new sound samples,
Button-3 Loads the file, in the case of “3b“, a .bin file, which is a Software-Update of ONE module
(or: Button-1 Skip this file)
Advance to the next file on the flash drive with a new file number
or
BUTTON-4 Loading a file (as above) but INTO ALL MODULES,
ONLY after finished loading IN ALL MODULES e.g. 
i.e. number of modules in which the loading procedure was successful
BUTTON-4 Next (= Accepted the completion of the loading procedure)
Ready to load the next file (displayed as above), e.g. 
Button-3 Loading the file, in this case a .cfg file, which is a configuration
(or: Button-1 Skip this file)
or
BUTTON-4 Loading a file (as above) but INTO ALL MODULES,
ONLY after finished loading IN ALL MODULES e.g. 
i.e. number of modules in which the loading procedure was successful
BUTTON-4 Next (= Accepted the completion of the loading procedure)
Ready to load the next file (displayed as above), e.g. 
Button-3 Loading the file, in this case a .snd file, which is a sound sample
(or: Button-1 Skip this file)
or
BUTTON-4 Loading a file (as above) but INTO ALL MODULES,
ONLY after finished loading IN ALL MODULES e.g. 
i.e. number of modules in which the loading procedure was successful
BUTTON-4 Next (= Accepted the completion of the loading procedure)
End of the updating and loading procedure:
Transmission and loading of ONE module successful flashing, transmission ERROR
in this case 3 files (software, configuration, sound, as described in the example
or
Transmission and loading of ALL modules successful flashing, transmission ERROR
in this case 3 files (software, configuration, sound, as described in the example
FAST PERFORMANCE (with 1 button only):
Plugging in the flash drive for example 
This means: the first sign (in this case “4”) = the number of files for the
StEin on the drive; the second sign (in this case “b”) = the type of the first file.
“u” means that the file about to be loaded is a .svf file (XILINX data)
“b” etc. - as with the controlled performance (see above)
Button-3 PRESS AND HOLD The complete updating and loading procedure in ONE mod-
ule runs without interruptions, i.e. the “NExt”-button “3” does not have to be pressed
or
BUTON-4 PRESS AND HOLD The complete updating and loading procedure in ALL mod-
ules runs without interruption, i.e the “Next” button 4 does not have to be pressed
Display at the end of the updating and loading procedure (as in controlled performance; see above).
A flash drive (in the root directory) may contain one or more (or all 5) file types,
but only one file of each type may be on the stick!
Code letter: “b” “u” “c” “F” “d”
Content: new software XILINX-Data Configuration prepared config. Sound files
ööööööööööööööööööööööööööööööööööööööööööööööööllll
siehhhhh

Page 12 StEin Stationary Equipment Module
*) current value is displayed
3. The “button-procedures” for “manual operation”
Although the “StEin” is usually not controlled manually (by using the buttons on the unit),
it may be helpful in certain situations:
- for the first time use (the “StEin” is ready for use as it comes with a “finished con-
figuration” activated at time of delivery - see next chapter), turnouts connected to the
StEin can be tested, as well as track sections set to H - L - U - etc. while observing
the effect on locomotives, even without a cab or a computer.
- while troubleshooting: signals can be controlled locally to ensure that the LED’s are
wired correctly or turnouts can be observed for proper operation.
- a short circuit on a track section can be cancelled locally and power restored.
Pressing and holding one of the 5 buttons on the StEin starts a procedure:
Button-1press/hold P-Procedures (track sections HLU, occupancy thresholds, module nr.)
Button-2press/hold F- Procedures (Restore after a short circuit/overcurrent)
Button-3press/hold A- Procedures (Activation of prepared configurations)
Button-4press/hold L- Procedures (Turnout switching)
Button-5press/hold E- Procedures (Single LEDs on signal PCBs)
Track sections setup procedures:
There are a number of "operation and adjustment procedures": P1, P2, P3...
First, use button-1 to select which procedure to execute:
Start with the module in its normal operating state (Address displayed), i.e.:
Press and hold button-1 (Button-1 P for “Procedure”) .
Hold or press button-1 several times 
Once the desired procedure number is reached: Wait for 1 sec dots disappear, i.e.:
continue with button-2 and -3 for individual control of the chosen procedure
(Meaning of buttons depends on procedure), for example:
Confirming a selection and executing a procedure or entering parameters; see below
or button-1 abort (i.e. after erroneous start); back to module number display, i.e.:
Timeout if no confirmation (i.e. Procedure selected but no further button pressed): 3 sec
Timeout if no action taken (Procedure selected, track output selected, but nothing more): 10 sec
Timeout if not continued (Procedure selected, an action executed - then, for example,
a track section set to the desired HLU value, but nothing after that): 30 sec
If a procedure is aborted by a timeout, the module number is displayed again, i.e.:
The procedures in detail:
P1 :Confirm with Button-2 ALL track section outputs are set to „F“(Drive): _
all track section HLU-LEDs turn green, after 3 sec: Display changes to
P2 :Confirm with Button-2 ALL track section outputs set to „H“(Halt).
all track section HLU-LED’s turn red, after 1 sec: Display changes to
P3 :Confirm with Button-2 occupancy threshold for ALL track section outputs are 
set to “dry” (threshold as per configuration), after 3 sec: display changes to 
P4 :Confirm with Button-2 occupancy threshold for track section outputs are 
set to “moist” (threshold as per configuration), after 3 sec display changes to 
P5 :Confirm with Button-2 occupancy threshold for track section outputs are 
set to “wet” (threshold as per configuration), after 3 sec display changes to
P6 :Select a track section with Button-2: 1, 2, 3, 4, 5, 6, 7, 8, 0, (cycl.) 1, 2… e.g.: *)
Select the HLU state with Button-3: A, H, U., U, L., L, F., F, (cycl.) A, H … e.g.:
Selects the HLU-State for a SINGLE track section.
ATTENTION - Selecting the track section “0” (which does not exist)
can be used to exit a procedure without taking further action; this is done with button-1.
PLEASE NOTE: the difference between the HLU states “U.“ and “U“ or “L.“ and “L“:
the “.“ (dot) means half a step lower, that is: “U.“ = “HU“, “L.“ = “UL“, “F.“ = “LF“
Confirm with Button-1 (Won’t abort in this case)
Applies the selected HLU setting to the track section,
corresponding HLU-LED for the track section changes.
Again Button-1 (without button-2, -3 etc. beforehand) Ends procedure, address returns
P7 :Select a track section with Button-2: 1, 2, 3, 4, 5, 6, 7, 8, 0, (cycl.) e.g.: 
Select the occupancy threshold with Button-3: b, d, h, (cycl.) b, d, h… e.g.: 
Selects the Occupancy Threshold for a SINGLE track section.
ATTENTION - Selecting the track section “0” (which does not exist)
can be used to exit a procedure without taking further action; this is done with button-1.
Confirmation with Button-1 (Won’t abort in this case)
Applies the selected setting to the track section
corresponding occupancy-LED for the track section flashes
Again Button-1 (without button-2, -3 etc. beforehand) Ends procedure, address returns:
P8 :With Button-2 or Button-3 Decrease / Increase the MODULE ADDRESS
Confirm with Button-1 Stores the new module address, procedure ends i.e.:
P9 :Select a track section with Button-2: 1, 2, 3, 4, 5, 6, 7, 8, 0, (cycl.) 1, 2… i.e.:
Starts the measurement with Button-3 AUTOMATIC OCCUPANCY (flickers)
THRESHOLD detection, taking into account the idle current
(e.g. by accessories).
Confirmation message when measurement is completed (after 1 to 2 sec)
PA :Automatic offset adjustment for all track sections.
PB :Display of the software version on the display

StEin Stationary Equipment Module Page 13
How to restore power after a short circuit/overcurrent:
Start with the module in its normal operating state (Address displayed), i.e.:
Press and hold button-2 (Button-2 F for “Driving again” 
the track section number where the short circuit/overcurrent is located
is shown automatically in the display while its corresponding LED flashes BLUE & YELLOW
(or –if several –the first affected section of the module).
Confirm by briefly pressing Button-2 Restores power to the track section: 
after 3 sec automatically
If several track sections are in an overcurrent or short circuit state:
Button-3 continues to the next shorted section, i.e. 2 x button 3 
As above …, button-2 Restores power to the track section 
after 3 sec automatically
or button-1 Abort back to module number e.g
So normally: that is, whenever a short circuit/overcurrent exists on one track section:
to restore power to that track section: 2 clicks on button-2: 1 x long (> 1 sec) and 1 x short.
Button procedure to switch turnouts:
Start with the module in its normal operating state (Address displayed), i.e.:
Press and hold button 4 (Button-4 L for “switching”) 
Hold button-4 or press repeatedly ,…
Once the desired turnout number is reached: Wait for 1 sec dots disappear, i.e.
Button-5 Operates the turnout, the switching position is indicated as or
Button-5 pressed together with button-3 “cleaning cycle” start or end
( = automatically switches the turnout for and back to clean its contacts)
Same as with external operation, the switching is made visible with the “5-LED group”.
Note: The representation with the 2 dots is not really required (but retains a similarity with other pro-
cedures), therefore: Turnout operation with Button-5 should work even if the two dots are still visible
(so there is no difference between "L.3." and "L 3").
Press Button-4 once or repeatedly moves forward to another turnout, i.e.
Press Button-3 once or repeatedly moves backwards to another turnout, i.e.
Wait for 1 sec dots disappear, i.e.
The newly selected turnout can be tested with Button-5…
Timeout if not confirmed (Turnout selected, but no other button pressed): 10 sec
Timeout if not continued (Procedure selected, an action executed, that is
the turnout was operated at least once but nothing after that): 30 sec
Abort back to module number i.e.:
or briefly press Button-1 Abort (i.e. after erroneous start); back to module number i.e.:
How to operate single LED’s on signal boards:
Start with the module in its normal operating state (Address displayed), i.e.:
Press/hold Button-5 
Hold Button-5 or press repeatedly ,…
Once the desired signal board is reached: Wait for 1 sec dots disappear, i.e.
Select the signal board output with Button-4: 1, 2, 3, 4… i.e.:
(the selected LED output is number 6 on the signal PCB 4)
continue with Button-3 Turns LED output ON/OFF and is displayed
or
Button-1 shortly Abort back to module number e.g.:
How to activate prepared configurations:
Start with the module in its normal operating state (Address displayed), i.e.:
Press/Hold Button-3 (Button-3 A for “Activate”) 
Hold or press button-3 several times 
Like this, “collections” of up to 100 prepared configurations are selected, of which there will
be up to 9. This option shall only be used in special cases. In most cases there is only
one collection; therefore stay with A.1., wait for 1 sec
dots disappear
Button-5 Setting of the number of the prepared configuration to be activated
(according to the list of prepared configurations, e.g.: 1 for “NNK”, 2 for “LLK”,
usually 8 track sections or 8 turnouts or others, each) e.g.
In case the number of the last prepared configuration is reached, or none at all)
Continue with Button-4 loading&activating the selected prepared configuration
if desired again:
Button-5 Setting of the number of the prepared configuration to be activated.
i.e. turnouts ADDITIONALLY to the previously selected track sections,
but not again 8 track sections (this would not be an addition),
which would overwrite the previously selected ones... e.g.
Continue with Button-4 loading & activating the selected prepared configuration
Can be repeated as often as you wish ... (useful for as many prepared configurations you have)
Button-1 shortly Abort back to module number e.g.:

Page 14 StEin Stationary Equipment Module
Touch the list to
switch between the half
or full screen display
4. Monitoring and operating with the MX32
The StEin List in the MX32 cab
Monitoring and operating stationary devices,
connected to the StEin modules.
The StEin LIST can be reached from the operating states LOCO or SWI with:
E-key + 8 StEin LIST
In the StEin LIST, all existing StEin modules in the system are arranged according to module num-
bers and represented by one line each; thus, depending on the presentation (half or full screen), few-
er or more modules are visible at the same time. Touching the screen anywhere in the list toggles be-
tween half or full screen display.
Briefly press the (Shift) - Key Switches the module line display between track sections,
switches, signals or inputs. The respective items displayed can be operated by the number keys.
GA - Track sections: for each of the 8 connections is displayed:
- the current HLU state (dot in color gradation, as the red-green LED on the module itself),
- the occupancy state (yellow dot, like the yellow occupancy LED on the module),
- Overcurrent and short circuit conditions (blue dot, similar to the blue LED on the module).
The display logic of the colored dots in the list is similar to the LEDs next to the screw terminals of
the track connections, although not identical for practical reasons.
The HLU states can be controlled by the controller:
- press corresponding numeric key to set it one step higher (i.e. HUH, HUU, etc.),
- press and hold the corresponding number key displays list of HLU states,
Select a state by the corresponding number key.
Restarting a track section after a short circuit with the corresponding number key!
WE –Turnouts or individual outputs: for each of the 8 turnout outputs (2 pins each) you see:
- the current turnout setting by means of an arrow, which, according to the feedback, is either filled
or empty; it flashes until the desired end position is reached (with motorized turnouts) or in the
event of a malfunction.
The turnouts can be operated from the controller:
- press the corresponding number key Switches the turnout back and forth.
IN - Switch inputs: for each of the 16 switch inputs
- the current state (green dot means: ON).
(Shift)-  Software of ALL StEin modules is shown in the list; (to get a rough idea)
E-key
8-key
so E+8

StEin Stationary Equipment Module Page 15
5. The 8 Track Sections, Overcurrent and Short circuits
Each of the 8 insulated track sections is connected to one of the “P” output pins; the “N”
rail is normally not sectioned off and is therefore continuous; the “N” pins on the StEin
are internally connected in parallel; it is therefore irrelevant whether only one of them is
used or all.
There are 3 control-LED’s for each track output, next to the “P” terminal:
- Top: the red-green HLU-LED: indicates the current HLU setting of the track section us-
ing a color scale from red (“H”) to green (“F”) or red flashing (for “A”).
- Middle: the blue overcurrent and short circuit LED: to control the processes dur-
ing overcurrent and short circuits; for detailed description see next pages, the
general meaning is always the same, though
solid blue: track section is currently switched off; either waiting for the next au-
tomatic reset, or finally (after reaching the maximum number of reset at-
tempts), for a manual reset.
flickering blue (about 10 kHz) in combination with steady light: track section
was automatically switched on again, but overcurrent is still present; therefore,
it will be shut down again shortly; typical picture resulting from this: alternat-
ing flickering and steady lighting.
flickering blue (about 10 kHz) without steady light: Immediate turn-off due to
short circuit and test-based reset in quick succession; final shutdown after 25 cy-
cles.
- Bottom: the yellow occupancy and RailCom LED: in addition to occupancy detec-
tion, received RailCom messages (Channel 2) are made visible by brief LED
flickers; this indicates how often loco address(es) are queried in a track section
through DCC commands.
Special case - yellow flashing (approx. 1, 2, 5 Hz): After the final shutdown
due to overcurrent or short-circuit (i.e. blue LED lit continuously), the yellow
LED shows the cause for the shutdown (slow overcurrent, fast overcurrent, or
short circuit).
Notes to wiring track sections:
The cable routing from track outputs to track sections usually, but not always, is doable
without problems: Cables wired in parallel can provoke capacitive or inductive crosstalk,
concerning data in forward direction (DCC signal, HLU information) as well as feedback
(RailCom, loco number impulses).
WILL BE ADDED LATER
Preliminary photo; the illustrated
display pattern is not possible under
normal
operating conditions.

Page 16 StEin Stationary Equipment Module
The overcurrent and short circuit handling of the StEin track sections
The 8 track section outputs of the StEin can take on different states individually, which are repre-
sented by the LEDs next to the clamps, but are also sent to controllers and computer (interlocking
program), to see the states and be able to take actions (e.g. restart).
See next page for graphic of display of track output states on the StEin itself.
The displays on controller and interlocking program are similar, but not completely identical and syn-
chronous, because the data traffic shall not overload CAN bus and radio.
1. As long as there is NO overcurrent or short circuit situation, one of two states is valid:
Normal operation-free (whereby one of the HLU steps H, UH, U, LU, L, FL, F, A is set) or
Normal operation-occupied (whereby one of the HLU steps H, UH, U, LU, L, FL, F, A is set).
2. Overcurrent - slow (threshold UESLAMP) or overcurrent - fast (UESSAMP): this is
NO short circuit, therefore NO immediate shutdown, but switch-off after defined switch-off time, after-
wards automatic restart according to parameter UESLAZT, UESLEZT, etc.
Track section states (the module reports) in this situation:
UES temporarily, i.e. UESL is detected and therefore switched on and off periodically, or
UES temporarily, i.e. UESS is detected and therefore switched on and off periodically.
LEDs on the StEin: blue LED flickers (=flashed rapidly), yellow LED (occupancy) does not change.
3. The track section is turned off once the shutdown period has elapsed (parameters UESLAZT or
UESSAZT) and a reset is awaited (after the reset-time has elapsed, that is the parameter UESLEZT or
UESSEZT).
Track section states in this situation as above (report is the same), therefore still:
UESL-temporarily, ... or
UESS-temporarily, ...
LEDs on the StEin: blue LED steady light, yellow LED (occupancy) does not change.
4. After the reset-time has elapsed (UESLEZT or UESSEZT), power to the track section is restored and -
in case overcurrent is still present - again (as above) the shutdown is awaited after the switch-off time
has ended (i.e. parameter UESLAZT or UESSAZT):
Track section states in this situation as above (report is the same), therefore still:
UESL-temporarily, ...
UESS-temporarily, ...
LEDs on the StEin: blue LED flickers, yellow LED (occupancy) does not change (like in 3.)
5. Depending on the number of reset attempts (parameters UESLEAZ or UESSEAZ), the above process
is repeated, i.e. track section states (the module reports) in this situation:
6. UESL-temporarily, ...
UESS-temporarily, ...
LEDs on the StEin: blue LED flickers, combined with steady light) yellow LED (occupancy) does not
change.
7. After the last power turn-off (when the power will not be restored again because the number according
to UESSEZT or UESLEZT was reached):
Track section states in this situation as above (report is the same), therefore still:
UESL switched off, because UESL requirement was still present after all restarts, or
UESS switched off, because UESS requirement was still present after all restarts.
LEDs on the StEin output: blue LED steady light, yellow LED flashes 1 Hz (UESL) or 2 Hz (UESS).
8. If a track section (from state UESL or UESS) is restarted manually, which can be done from the buttons
on the StEin, the controller or the interlocking program, the section enters normal operation, except
when overcurrent or short circuit is detected again immediately; in the latter: procedure as described
above.
Short circuit (threshold KUSAMP):
this is a “real” short circuit, in which case an immediate shut-down is essential, due to jeopardizing ve-
hicles and track material (and if set to 8A also the module itself is in danger); therefore, there is NO ad-
justable turn-off time; the number of restart attempts is also fixed, namely 50 (in the current software);
there is only an adjustable restart time (parameter KUSEZT), independently, first, 10 fast restart at-
tempts are made (intervals of 100 ms each for small frog contacts, etc.) and then the further ones after
the intervals set in KUSEZT, whereby the restart attempts decrease, because the intervals enlarge bit
by bit, at the last 50 attempts to approximately the 3-fold value. With the value in KUSEZT, also results
in the time until the final shutdown; e.g. with a typical value of KUSEZT = 1000 ms, the final shutdown
time is about 2½ min.
Track section states (the module reports) during these 25 restart attempts:
KS temporarily occupied, i.e. short circuit was detected at every restart attempt.
LEDs on the StEin output: blue LED flashes in accordance with the restart attempts, yellow LED (oc-
cupancy) does not change: steady light.
After 50 failed restart attempts, whereafter there is no automatic restart; i.e. after the final shutdown:
KS turned-off display status occupied, after all restart attempts have failed.
Note: the term “display status occupied” (instead of “occupied”) means that “occupied” is only presumed,
but due to a lack of power in the section, it cannot be verified.
LEDs on the StEin output: blue LED steady light, yellow LED flashes fast 5 Hz.
9. If a track section (from state KS turned-off) is restarted manually, which can be done from the buttons
on the StEin, the controller or the interlocking program, the section enters normal operation, except
when overcurrent or short circuit is detected again immediately; in the latter: procedure as described
above.
NOTE (for normal operation NOT relevant) to possible track section states which are NOT explained
above, but could be:
Running voltage off-display state free: Track section is completely powerless (but NOT HLU step A,
where there are no impulses for occupancy detection); only in special situations like missing synchronisa-
tion. Detectable on the StEin oputput: turned-off or anomalous HLU-LED
Running voltage off-display state occupied: Track section is completely powerless (but NOT HLU step
A, where there are no impulses for occupancy detection); only in special situations like missing synchroni-
sation Detectable on the StEin oputput: turned-off or anomalous HLU-LED
UESL turned-off display state free,
UESS turned-off display state free,
KS turned-off display state free: practically no or small difference to the actual state
“xxx turned-off display state free”; although it could be practical because of interlocking logic.

StEin Stationary Equipment Module Page 17
The light sequences of the blue LED
shown here in overcurrent situations
(i.e. alternately flickering or lit solid)
can only happen if the shutdown times
are relatively large (from @ 500 ms),
otherwise a solidly lit LED with very
brief interruptions is more likely.
Blue LED
Yellow LED
Blue LED
According to the configuration settings (shutdown times, reset times), overcurrents or short circuits are indicated by the blue LED in
particular phases of track power off (= blue LED ON) and reset attempts (= blue LED flickers).
Overcurrent threshold UESLAMP
-“long” overcurrent threshold is
exceeded.
Blue LED flickers at 10 Hz.
Power is restored after UESLEZT
expires (long reset time, i.e. 2
sec.)
Blue LED flickers again.
According to UESLEAZ (quantity i.e. 5),
several resets are attempted.
Blue LED flickers/lights up alternately.
Blue LED
Power turns off after UESLAZT
expires (“long” overcurrent time,
i.e. 2 sec.)
Solid blue LED.
Power turns off after UESLAZT
expires (“long” overcurrent time,
i.e. 2 sec.)
Solid blue LED.
Overcurrent conditions (current via UESLAMP, i.e. 1.5
A) are no longer exceeded. That ends the overcurrent
sequence, back to normal.
Blue LED is dark again.
Temporary overcurrent situation which
ends "in time", whereby a shutdown is
not initiated
IF it leads to a shutdown:
Blue LED is ON continuously,
Yellow LED indicates the reason for the
shutdown by means of the flashing rhythm.
Power is restored after UESLEZT
expires (long reset time, i.e. 2
sec.)
Blue LED flickers again.
According to UESLEAZ (quantity i.e. 5),
several resets are attempted.
Blue LED flickers/lights up alternately.
Power is permanently turned off after the last at-
tempted reset (i.e. 5).
Blue LED is ON, yellow LED flashes at 1 Hz
(Sign of a “slow overcurrent”).
Overcurrent threshold UESSAMP -
“fast” overcurrent threshold (i.e. 2.5A) is
exceeded.
Blue LED flickers at 10 Hz.
Yellow LED
Power turns off after UESSAZT
expires (“fast” overcurrent time, i.e.
1 sec.)
Solid blue LED.
Power is restored after UESLEZT
expires (“fast” reset time, i.e. 1.5
sec.)
Blue LED flickers again.
According to UESLEAZ (Quantity i.e. 8),
several resets are atempted.
Blue LED flickers/lights up alternately.
Power is permanently turned off after the last at-
tempted reset (i.e.after 8).
Blue LED is ON, yellow LED flashes at 2 Hz
(Sign of a “fast overcurrent”).
Power is restored after eliminating the cause by the switch board (computer), cab or the buttons on the StEin module (Button-2: press/hold once then briefly press again.
Short circuit threshold KUSAMP (i.e. 4A) is
exceeded, leads to immediate shutdown.
5 reset attempts after every 100 msec.
Blue LED flashes at 10 Hz.(~ 100 msec).
20 more (fixed number) resets are attempted in in-
tervals according to KUSEZT
(short circuit reset time, i.e. 200 msec.)
Blue LED flashes at 5 Hz.(~ 200 msec).
Power is permanently turned off after the last at-
tempted reset (after 25 –fixed number).
Blue LED is ON, yellow LED flashes at 5 Hz
(Sign of a “short circuit”).
Short circuit threshold KUSAMP (i.e. 4A) is
exceeded, leads to immediate shutdown.
5 reset attempts after every 100 msec.
Blue LED flashes at 10 Hz.(~ 100 msec).
20 more (fixed number) resets are attempted in inter-
vals according to KUSEZT
(short circuit reset time, i.e. 200 msec.)
Blue LED flashes at 5 Hz.(~ 200 msec).
Short circuit conditions (current above KUSAMP,
i.e. 4 A) are no longer present. This ends the short
circuit sequence, power back to normal.
Blue LED is dark.
Scale: 1 sec
NOTE: The timelines shown here are
examples
and correspond to finished
configurations for a typical HO layout.
The shutdown behavior can be changed
by editing the parameter sheet entries
(UESLAZT, UESLEZT, UESSAZT etc.)
Blue LED

Page 18 StEin Stationary Equipment Module
6. Track sections, point detectors, point following com-
mands
One StEin module has (inter alia) 8 outputs for track sections and 16 logic level inputs.
Those inputs are used for point detectors *), whereby less track sections are needed
otherwise. This results in a technically beneficial and at the same time cost-efficient way
of layout control:
*) Point detectors are usually simple contact rails, i.e. switching rails, or (reflex-) pho-
toelectric sensors.
Track sections for a mere “LZB” (continuous automatic train control) control:
Division of the track sections for two station-tracks and setting HLU-steps, if a route
from the entry-signal (left) into the upper station track with stop before the exit sig-
nal, is activated. So the train reduces speed bit by bit, from the middle speed step (L)
in a lower one (U) until Stop (H).
“LZB” in combination with “PZB” (intermittent automatic train control):
Less track sections by subdividing them by photoelectric sensors, more cost efficient
and more precise stopping points.
The interlocking program ensures that also pushing trains (loco on the rear side) brake
and stop correctly, by automatically setting the track sections ahead to the corre-
sponding HLU step when detecting the tip of the train.
.
Point detectors (rail contacts, photoelectric sensors, etc.) are assigned to one track sec-
tion each, by entering the connection point of the point detector into the object line of
the parameter APUGK1 (or APUGK2).
The purpose of the point detectors is to switch the track section from one HLU step to
another as soon as a train is detected; for example from L to H, displayed: L/H.
Point detectors are used in two situations;
- In “operation type 3” (i.e. operation by computer): On the driveway via HLU point fol-
lowing commands for the track section like L/H, U/H, LU/L, etc. Those are only valid
once: when leaving the corresponding driveway.
- In “operation type 0” or “1” by parameters PUFFIX, where equally L/H, U/H, etc. are
entered. Those are permanently valid for this section.
IMPORTANT:
-The point detector works independently of the occupation state of the track section.
-It is only valid once; i.e. when the change is done once, the point detector is deac-
tivated, especially if the HLU step (by other commands or keys) is changed.
-A point detector is
oin “operation type 3” reactivated exclusively by a newly received point following
command with new content; for example: after L/H would follow the point fol-
lowing command U/L (probably not practical), or if after L/H follows F and after
this again L/H (more probable).
oIn “operation type 0” or “1”, if the track section changed its occupation state af-
ter executing the point following command (e.g. L/H).
…
U HLU
LU
LL
LU/U/H
LU
L
P
P P
P P

StEin Stationary Equipment Module Page 19
7. Terminal loops
Terminal loop sections are built by two tracks sections next to each other (each con-
nected with a 3-pole plug).
……………………………..
PRELIMINARY TEXT:
Switching terminal loops - new strategy
At terminal loops both outputs are connected inversely,
when reaching the lowest overcurrent threshold (three values UELS, UESS, KUS),
the first time its polarity is reversed and other reactions are suppressed,
and the KS-polarity-reversing-time doubled to 2-fold detection
the second time (waiting for second measurement), double polarity-reverse time,
then x4, then x8, then (instead of 16) normal UES or short circuit handling
at restart after UES or KS again process as above
Display of coherence of both sections and the current polarity
Polarity display by HLU-LEDs:
long (0,4 sec on) - short (0,1 sec off) on P-pole / long (0,4 sec off) - short (0,1 sec on) on N-
pole,
when changing (starting with first switch for 2 sec): full on P-pole / dark on N-pole
(so, immediate synchronous visualization of every change).
With every short circuit that leads to reversing the polarity: Blue LED flashes
Occupancy LEDs of both outputs always synchronized (occupancy and RailCom)
Special measurement and display as indicator for probably too low set central command station:
If there is no repolarisation on the terminal loop section (ONLY at terminal loop sections) current
jump > 1 A and there is NO repolarisation (because MX10 obviously does not supply enough cur-
rent), warning by rapid jumps of the two yellos LEDs (inverted flashing with about 5Hz) for 5 sec
as warning for possibly failed plolarity-reverse attempt)

Page 20 StEin Stationary Equipment Module
8. The 8 outputs for 8 turnouts / 16 Single consumers
Switching turnouts or single outputs are connected to the corresponding displays on
the “5-LED-group”. Thereby, it is irrelevant what triggers the switching: operation on
the module itself by the key procedure "4" (turnouts, also "automatic cleaning"), or
from the controller (StEin LIST) or an interlocking program.
The left LED-pair (= the two left LEDs) are assigned to one turnout and the right-LED
pair to another. Each turnout actuation assigns one of the LED pairs to the relevant
turnout. As a result, the last two operated switches are always visible, that is their
"position LED" and their "impulse LED".
The “power LED” in principle indicates (in very large steps) the power consumption of
all 16 power amplifiers of the 8 turnouts or 16 individual outputs. If only coil turnouts
are present, or motorized turnouts are switched one by one (not all at the same time)
it is possible to draw conclusions as to the functionality of the turnouts (i.e. how much
time the turnouts require to switch).
The typical switching sequence of a double coil turnout looks like this:
Flashing of the position-LED means that a clear position cannot be determined by test
pulses.
Weichen-
ausgänge,
1...8
(rot,grün)
5V,MASSE
MASSE,ZUB
20-poligesBandkabelamStecker
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
5 V
MASSE
We iche 1, Richtung „rot”
We iche 1, Richtung „grün”
We iche 2, Richtung „rot”
We iche 2, Richtung „grün”
We iche 3, Richtung „rot”
We iche 3, Richtung „grün”
We iche 4, Richtung „rot”
We iche 4, Richtung „grün”
We iche 5, Richtung „rot”
We iche 5, Richtung „grün”
We iche 6, Richtung „rot”
We iche 6, Richtung „grün”
We iche 7, Richtung „rot”
We iche 7, Richtung „grün”
We iche 8, Richtung „rot”
We iche 8, Richtung „grün”
MASSE
Zubehörspa nnung