ZIMO MX10 Instruction Manual

Central command station
Hide thumbs Also See for MX10:

Advertisement

Quick Links

INSTRUCTION MANUAL
CENTRAL COMMAND
STATION MX10
ZIMO's digital command station
This instruction manual contains elements which refer to features that are not yet fully imple-
mented.
The final implementation may differ from the descriptions and
display pictures.
SW 01.20.0001 - 2016 09 22
SW 01.20.0150 - 2017 01 31
SW 01.22.0001 - 2017 12 20
SW 01.24.0001 - 2018 07 30
Chapter
1.
Initial start-up of a ZIMO system ......................................................................... 4
2.
Power supply and technical data ........................................................................ 5
3.
Typical system arrangement ............................................................................... 6
The "Connection and distribution board" MX10AVP ......................................... 12
4.
5.
Rail connections, programming track, AOS in/out............................................. 15
6.
Track signal, Feedback, Database ................................................................... 17
7.
MX10 update, data import and storage ............................................................. 18
8.
Usage and operating elements ......................................................................... 19
"Roco Z21" app and other apps on the MX10 ................................................... 34
9.
Interlocking Program "ESTWGJ" on the MX10 ............................................... 35
10.
11.
USB connection to the computer ................................................................... 37
Annex: EMV audit report / TÜV Austria ..................................................................... 38
Annex: Declaration of Conformity and Warranty ....................................................... 38
EDITIONS
2013 03 15
2013 10 15
2013 11 23
2014 02 28
2014 04 04
2014 04 05
2014 12 02
2014 12 03
2014 12 10
2014 12 16
2015 02 04
2015 04 10
2015 05 27
2015 07 21
2015 10 20
2015 12 07
2016 02 11
2016 03 14
2016 04 05
2016 12 10
2017 05 16
2017 10.12
2018 05 03
2019 01 15

Advertisement

Table of Contents
loading

Summary of Contents for ZIMO MX10

  • Page 1: Table Of Contents

    Track signal, Feedback, Database ..............17 MX10 update, data import and storage ............. 18 Usage and operating elements ................. 19 “Roco Z21“ app and other apps on the MX10 ........... 34 ZIMO’s digital command station Interlocking Program “ESTWGJ” on the MX10 ..........35 USB connection to the computer ..............
  • Page 2 DCC SERV PROG settings YELLOW CV programming and read-out on the programming track (track 2) M,, Select files to update et on the rear side of the MX10. the decoder or to  MX10 Config GREY Various settings as language, radio channel, sniffer input, booster, etc.
  • Page 3 CAN bus To communicate with radio modules, ZIMO uses “Mi-Wi”, a “mesh network” track signal) for - for a 6-pole connection to ZIMO controllers 20 - 35 V = and modules; and/or based on components and the software of - External buttons for emergency stop and emergency OFF,...
  • Page 4: Initial Start-Up Of A Zimo System

    F-key - The controller (one of the two sockets) has to be connected to the MX10 (socket “ZIMO CAN”) via the CAN cable. A-key ATTENTION: Only use the fully symmetrical cable with identical plugs on both ends, DO NOT use the cable with a coloured plug on one side (which may be part of the start set).
  • Page 5: Power Supply And Technical Data

    (adjustable in 0.1 A steps) ..1 to 12 A 5 A power supply unit you can use a product from ZIMO or from another manufacturer, as long as it ful- - Turn-off time in case of overcurrent ..... (adjustable in 0.1 sec steps) ..
  • Page 6: Typical System Arrangement

    MX32. Additionally, a combination like this may also be used, when the Roco central station Z21, which was used up until now, is replaced by a ZIMO MX10 central station. This is usually the case, if you need MX10’s better performance or other characteristics as HLU.
  • Page 7 INSTRUCTION MANUAL CENTRAL COMMAND STATION MX10 Page 7...
  • Page 8 SW July 2018 - SW 01.24 and higher In case the “normal” track output of the MX10 (“S1” with 12 A traction current) is not enough to supply the layout, frankly, there are two possibilities: interconnecting the two track outputs (“S1” and “S2” with con- figuring “SYNC”...
  • Page 9 This can be guaranteed easily by certain lengths of wires and rails (whereby the sum one such socket per MX10, you have to use a CAN bus distributor (8-pole) for forwarding to a third of both poles is effective): (...) device.
  • Page 10 It is necessary to use both CAN buses, because there is a new, faster protocol between the “new” MX32, MX32FU - XNET and the MX10, which the “old” devices are not capable of. As soon as there is one device in the system circuit The “red” Roco Multimaus and Massoth DiMax Navigator communicate via “XPressNet”, the ZIMO- that operates with the old CAN protocol, the MX10 switch- called “XNET”.
  • Page 11 MX32’s function is not changed, as far as no MX8 and/or MX9 modules are connected additionally to MX10. the MX10’s CAN. If this is the case, the MX32 run in the “old” CAN protocol and therefore in the “MX1 A DiMAX radio receiver has 3 connection sockets. Connect the socket in the middle named “XPRESS- operation”...
  • Page 12: The "Connection And Distribution Board" Mx10Avp

    The easiest way to use the “Connection and distribution board MX10AVP” is with a bus distributor: The advantage over the direct while the central command station MX10 itself has two CAN sockets (front and back), this way 5 sock- connection to the MX10 (with ets are available, 4 of them on the MX10AVP.
  • Page 13 In case old and new generation devices shall work together, two separate CAN buses are used. This is modules “StEin”; all work on CAN-1. The StEin modules (as well as booster MX10) need timing infor- the same as using MX32 and MX31: mation for the DCC track signal, additionally to the actual CAN data bus, wherefore 8-pole CAN cables - old controllers (until MX31) and all accessory and track section modules (i.e.
  • Page 14 (“XNET”); MX10AVP has separated sockets “XNET-1” ad “XNET-2” (between the CAN sockets). - to control comfortably (via spring clips) the 16-pole pin connector on the MX10, i.e. 8 inputs (for con- tact rails, emergency stop buttons, etc.) and 8 outputs.
  • Page 15: Rail Connections, Programming Track, Aos In/Out

    5 A, at the best of 10 A. and are fully stabilised. The MX10 automatically switches the relay, so that it connects “Schiene 2” to the programming track, while a controller (and therefore the connection point “Schiene 2”) is in operation state SERV PROG .
  • Page 16 It is one of the basic tasks of a modern digital command station to support loading new software or sound into the decoder. Therefore - at least for ZIMO decoders - no extra updating and sound loading radio) controller. Only from there the operation can be resumed (“ON”).
  • Page 17: Track Signal, Feedback, Database

    “StEin” modules (stationary equipment modules); but those are not only simple local detectors, but also read global notifications (and forward them to the MX10), because on a big layout, the receiving quality can be much bet- ter on a single track section than on the command station’s position.
  • Page 18: Mx10 Update, Data Import And Storage

    After each update, the MX10 has to be disconnected from the power supply and restarted after about 1 minute, to make sure that all concerned circuit elements are started with the new software. In case there is no file on the flash drive, the MX10 can use (not available or damaged), the screen shows: “NO ZIMO FILES FOUND”...
  • Page 19: Usage And Operating Elements

    (e.g. because of long, badly connected cables). Leaving the “normal screen” is possible by the following events:  Insert flash drive (with the files to update the MX10 and/or the decoder software or to load (Flash drive) sound into the root directory)  screen...
  • Page 20 “main settings” for a perfect adjustment of threshold” in the “detailed setting” (see description be- individual needs. low). This display can also be reached via the MX10 Running voltage track 1 - upper value menu (chapter 8.8). Each of the values is displayed and has to be adjusted in- Track 2 - lower value dividually for track 1 and 2.
  • Page 21 Default Yes: the MX10 starts operation on track 1 after the stopping state is confirmed on the controller MX32. Target voltage on the output track 1 or track 2. This voltage is kept within a range of 1V; if this is not The programming track is not affected.
  • Page 22 Means: if track 1 is ON, it is set to (Broadcast Stop) BCSe when entering into the stopping operation. shown on their displays and and on the MX10’s display. Cancelling broadcast stop started by the rotary knob; going back to normal screen: Button 1...
  • Page 23 Those screens are the same as after starting broadcast stop (“BCS” a defect in the current limiting circuit. or “UNV”) from the MX10 or the controller. Therefore, also the procedure to re-start, etc. is the same:  Voltage error on track 1 / track 2 screen colour changes to RED, Button 1...
  • Page 24 Page 24 INSTRUCTION MANUAL CENTRAL COMMAND STATION MX10 Fahrzeugadresse markieren (Drehen, Drücken) FAHR BaseCab LOCO (driving operation via command station) THIS FUNCTION IS NOT YET IMPLEMENTED - THIS IS A DESCRIPTION OF THE PROJECT Starting point is the normal screen...
  • Page 25 Press rotary knob  program adjusted value into decoder; open next line BaseCab SERV PROG (programming CVs) If programming was successful (acknowledged by RailCom feedback) the MX10 displays: „ACK RC“ THIS FUNCTION IS NOT YET IMPLEMENTED - THIS IS A DESCRIPTION OF THE PROJECT...
  • Page 26 ON – BSC – OFF – ON – BCS – OFF … etc. NOTE: The same “BCS & OFF” screen is reached as well via the menu point of the MX10 as via the Press button 2 (MENU) ...
  • Page 27 - Booster Error: Configuration of the operating state after an overcurrent notification of the connected booster or by activating the emergency stop button via the “Boo UE” input of the booster socket (MX10 “Peak power” shows the highest voltage and current on each back ZIMO CAN).
  • Page 28 Calling up the decoder SW updates from the menu means that a SW update collection file or sound pro- This function is shown in parentheses on the MX10 and is ject previously stored in the MX10’s “file storage” shall be used; the available files are listed. In contrast therefore not implemented. You cannot call up the screen to the situation in which the updating procedure is started by inserting a flash drive to use a file directly “BaseCab OP PROG”.
  • Page 29 Monitor screen Menu points PC Config+Monitor GREY This function is shown in parentheses on the MX10 and is therefore not fully implemented. You can call up the LAN IP address and Mask setting. screen “MMx SIGNAL settings”, but not use it.
  • Page 30 The “flick- ering” frequency of a certain packet indicator (e.g. F or the NOTE: Driving operation is also possible without looking at the Object Database. In the ZIMO system,  third ) represents the sending intensity of this data.
  • Page 31 Press rotary knob  screen colour changes to GREEN, “BaseCab” - screen addresses manually (most of the time deleting whole address contingents) from the object database of the MX10, or of the whole system. Regarding the following steps within the menu point (”ObjectDB ve- *) Activision codes: hicles”) this is rather comfortable:...
  • Page 32 ObjectDB Sound projects GREY Lists of the sound samples stored in the MX10 (to play back via the “virtual address MX10 Sound”), software decoder collection file and sound projects for decoders (applicable via menu points “ZIMO decoder SW-Update” and “ZIMO decoder sound loading”) ...
  • Page 33 8.10 Insert flash drive with files to update decoder software or Decoder Update and Sound loading; directly from the flash drive or the MX10’s file memory load sounds; to copy into the “file storage” or to carry out directly THIS FUNCTION IS NOT YET IMPLEMENTED - THIS IS A DESCRIPTION OF THE PROJECT...
  • Page 34: Roco Z21" App And Other Apps On The Mx10

    In case, NO connection (WIFI symbol in the status bar in the upper right corner) can be made (IP ad- dress of the MX10 does not correspond to the router), the IP address on the MX10 has to be changed.
  • Page 35: Interlocking Program "Estwgj" On The Mx10

    OK, OK, OK, ... In case of a firewall, it has to be ensured that the MX10 sends data via the UDP ports 14520 (PC sends) and 14521 (PC receives commands; these ports are configured by default in the MX10 and can be changed in the MX10 menu under “PC Config+Monitor”...
  • Page 36 As described here for ESTWGJ, other interlocking programs can be connected with the MX10. NOTE: MX10 can not communicate via LAN and USB at the same time. As soon as the MX10 recog- nises a valid LAN connection, USB is deactivated.
  • Page 37: Usb Connection To The Computer

    This is a general description, valid for different applications, but NOT a certain programme. For the PC to communicate with an MX10 via USB, they have to be interconnected by a cable type “A If this tab is not available, to mini B”.
  • Page 38: Annex: Emv Audit Report / Tüv Austria

    Concerning the MX10 command station and MX32 controller. Declaration of Conformity: ZIMO Elektronik GmbH hereby declares that the product MX10 bears the EC mark and is built in ac- cordance with the provisions of Directives 88/378 / EEC; 89/336 / EEC; 73/23 / EEC.

Table of Contents