Page 36 TETHERED CONTROLLER MX32, RADIO CONTROLLER MX32FU
14. DRIVING AND CONSIST CONTROL
There are two versions of consisting in the DCC world:
- using a “consist address” in the decoder (in CVs #17 & 18), which is set to an identical value in the
participating vehicles of a consist,
- using the system by sending identical, de facto simultaneous driving commands (in reality quick
successive commands), to all addresses involved in the consist.
The second type, which is the system-controlled consist formation is
the preferred method by ZIMO due to the higher flexibility.
The ZIMO system distinguishes between two types of system-controlled consisting:
BASIC INFORMATION ABOUT SYSTEM-CONTROLLED CONSISTING:
- Double-headers or consists, means linking together two or more vehicles (= addresses). This causes all en-
gines in the consist to react the same when a new speed, direction, MAN or RG command is sent to any one of
them. Functions on the other hand are still controlled individually for each decoder in the consist.
- A consist resides in principle NOT "in the system" (command station), but always in "a controller”, i.e. a MX32
controller (or in a ZIMO app.) Either the consist was established in this controller, or it was set-up in another
controller and taken over by this one.
- Consists "do NOT reside" in the command station but are "copies" there, that is, they are also linked with the
formation in the "residence-controller". On the one hand, this is due to the need for existing traction to prioritize
the DCC rail signal (or other formats), on the other hand, traction will continue to exist if the "residence device"
is removed from the system (or the radio connection is broken); It can therefore continue to be taken over by
another device, which then functions as residence device.
- Whenever a consist (or an address thereof) is activated (enters the LOCO window), the controller (in which
the consist resides at the latest after taking it over) informs the command station of the consist parameters
(addresses, settings,...). This message takes precedence over the current content related in this respect in the
command station, IF this command station is the home system. If not; see below:
INTERNAL REMARKS: All situations related to consists being transferred from one system to another via the
residence controller are difficult.
PRELIMINARY NOTE: Turning power off and back on should - as usual – change nothing: The residence controllers
retain their consist, The "copies" in the command station are retained, regardless of whether the respective residence
controllers are still present at power-up.
PRELIMINARY NOTE 2: The brake-up of a consist is only possible in a residence controller. This means, if an address
is called up, which belongs to a consist that is marked with "FT" and is taken over with the U-Key (to the current “resi-
dence controller”), the consist can now be resolved or individual addresses be removed or added to it. These process-
es are once again immediately "copied” to the central command station.
ATTENTION: Every consist in the residence controller must be provided with information as to which "home system"
(command station ID) it belongs to. It is certainly possible to have consists in one controller that were built in different
home systems or are acquired by take-over from the home system the controller is currently connected to.
If a residence controller is connected to a new command station (recognizable by the new "home system"), the control-
ler initially does not contain a copy of the consists that reside in this command station. Only in case a consist residing
in the controller is to be activated, it will be copied to the command station, BUT ONLY IF THIS is possible (i.e. all par-
ticipating addresses do not yet exist.) Otherwise it will be rejected and a corresponding message appears on the con-
troller display.
“Consists” vs. “Trains”
The goal in both cases is that two or more vehicles are controlled at the same time by one cab
(ZIMO cab or app), i.e. always drive at the same speed and in the same direction. For this purpose,
the desired double-header whether consist or "train" must be previously defined. The differences be-
tween the two types of consists are:
“Consists” (current chapter) “Trains” (Chapter 17)
Several vehicle addresses are provided with a consist number
(T1, T2, T3...) by placing a corresponding marker in the LoR (lo-
co recall memory) of the cab.
The speeds and directions of the addresses involved in a
consist, always match each other, irrespective of to which
vehicle (or address) a change is made.
A “Train” is formed by either transforming a consist or by its
own definition procedure.
The "train" distinguishes itself by its own name, which must be
assigned to it (not just a consist number). This makes it to an inde-
pendent object.
Consists are usually used to couple several locomotives with
each other or to logically connect a pilot car on one end of a
shuttle with the engine on the other end.
A "train" usually consists of at least one engine (locomotive) and
several cars, each equipped with their own decoders whose order
can also be defined. Dedicated procedures allow for a comforta-
ble logical (or also the physical) "coupling / uncoupling”.
The vehicles participating in a double-header or multiple consist
remain listed in the LoR (loco recall memory) and ObjectDb (ob-
ject database) as separate objects. There are sorting options,
and shortcuts for fast switching between the loco addresses.
To Next Page
Loading...