roco:roco-z21-en
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
roco:roco-z21-en [2019/01/07 12:18] – [Power Manager] rjversluis | roco:roco-z21-en [2023/05/15 09:33] (current) – [LocoNet detectors] cds | ||
---|---|---|---|
Line 2: | Line 2: | ||
[[: | [[: | ||
[[: | [[: | ||
- | * [[: | + | * [[: |
\\ | \\ | ||
{{: | {{: | ||
Line 10: | Line 10: | ||
=====Z21/ | =====Z21/ | ||
[[http:// | [[http:// | ||
+ | |||
+ | |||
+ | \\ | ||
+ | ===== Notes ===== | ||
+ | * LocoNet sensor modules from Digikeijs seems not compatible with the Z21. | ||
\\ | \\ | ||
Line 23: | Line 28: | ||
* 28 Loco functions | * 28 Loco functions | ||
* Switch/ | * Switch/ | ||
- | * Timed switch commands for coils¹ | + | * Timed switch commands for coils ((Commands for the same address are rejected in case the timer did not yet elapsed.)) |
* Sensor report evaluation | * Sensor report evaluation | ||
* Switch report evaluation | * Switch report evaluation | ||
Line 30: | Line 35: | ||
* Programming RMBus | * Programming RMBus | ||
* CAN Z21 10808 detector support | * CAN Z21 10808 detector support | ||
- | \\ | ||
- | ¹) //Commands for the same address are rejected in case the timer did not yet elapsed.// | ||
\\ | \\ | ||
+ | |||
===== Setup ===== | ===== Setup ===== | ||
{{: | {{: | ||
- | ====Hostname==== | + | ====Hostname/IP-Adresse==== |
Factory default is 192.168.0.111 which is also used if left empty.\\ | Factory default is 192.168.0.111 which is also used if left empty.\\ | ||
Line 46: | Line 50: | ||
====Locomotives==== | ====Locomotives==== | ||
+ | :!: //Only use this option in case locomotives are controlled by an external throttle which connects directly to the Z21/ | ||
This option is needed for getting (speed, direction and function) info events from the Command Station of manually((External throttle)) controlled locos to synchronize Rocrail clients.\\ | This option is needed for getting (speed, direction and function) info events from the Command Station of manually((External throttle)) controlled locos to synchronize Rocrail clients.\\ | ||
Without this option the subscription on loco info is done individually for each loco after a speed or function command is send from Rocrail.\\ | Without this option the subscription on loco info is done individually for each loco after a speed or function command is send from Rocrail.\\ | ||
- | ====Xpressnet GBM==== | + | |
- | This option must be set if RailCom detectors are connected to the Xpressnet | + | ==== Report absent ==== |
- | (Blücher GBM16XN)\\ | + | If this option is activated, it will be reported if a loco ID is no longer recognized by a RailCom detector. |
+ | \\ | ||
+ | |||
+ | ==== Check Hostname ==== | ||
+ | | :!: Disable this option, and use the static Z21 IP address, if no sensor events are coming in. :!: | | ||
+ | Use this option only if the Z21 the static IP address has been assigned a hostname.\\ | ||
+ | In all other cases this option should be deactivated.\\ | ||
+ | **Note:** //For Network experts only!// | ||
+ | \\ | ||
+ | ====Booster events==== | ||
+ | This option must be activated, if Booster events should be received from the the z21 controller. | ||
+ | \\ | ||
+ | ====LocoNet detectors==== | ||
+ | This option should only be activated | ||
+ | It activates OPC_MULTI_SENSE events. For more information see capital **9.5** // | ||
+ | **Note:** //Leave this option disabled in case no RailCom detectors are connected.// | ||
+ | \\ | ||
+ | ====multiMAUS==== | ||
+ | Check if the event is originated by the multiMAUS to signal Rocrail that it is a field event.\\ | ||
====Program FB==== | ====Program FB==== | ||
Line 62: | Line 85: | ||
- :!: Program address zero after the sensor module has acknowledged. | - :!: Program address zero after the sensor module has acknowledged. | ||
+ | ==== Switch time ==== | ||
+ | Default output activation time for switches.\\ | ||
+ | This value is only used in case the __**[[: | ||
+ | **Note:** //The output of the switch will only be reset after this time in case its activated.// | ||
\\ | \\ | ||
Line 74: | Line 100: | ||
| 1 | Loconet | 1.2 | | | 1 | Loconet | 1.2 | | ||
Switches, outputs and signals do only use the address field.\\ | Switches, outputs and signals do only use the address field.\\ | ||
+ | :!: If both address and port are set > 0 the addressing will be recalculated back to FADA. This is not recommended. (2.1.1577+)\\ | ||
====Sensors==== | ====Sensors==== | ||
+ | **Tip:** Use the [[: | ||
+ | |||
^ Bus ^ Network ^ Z21 Firmware ^ Remark ^ | ^ Bus ^ Network ^ Z21 Firmware ^ Remark ^ | ||
| 0 | R-Bus | 1.0 | | | | 0 | R-Bus | 1.0 | | | ||
- | | 1 | LocoNet | 1.2 | LocoIO, DR5088RC(Feedback), GBM16XN, DR5088RC(Block) | | + | | 1 | LocoNet | 1.2 | LocoIO, DR5088RC(Feedback), |
| 3 | CAN | 1.29 | Roco Z21 CAN Detector | | | 3 | CAN | 1.29 | Roco Z21 CAN Detector | | ||
===Flat addressing=== | ===Flat addressing=== | ||
Line 86: | Line 115: | ||
\\ | \\ | ||
====Special Feature ==== | ====Special Feature ==== | ||
- | In the default setting of the z21 / Z21 there is an address offset of +4 between Multimaus and Rocrail. This means that in Rocrail the addresses 1-4 can not be used. If e.g. address 1 of the multimouse is to be used in Rocrail address 5. But there is an elegant way to eliminate this shift. To do this, connect the z21 to the computer via the z21-maintenance-tool, | + | In the default setting of the z21 / Z21 there is an address offset of +4 between Multimaus and Rocrail. This means that in Rocrail the addresses 1-4 can not be used. If e.g. address 1 of the multimouse is to be used in Rocrail address 5. But there is an elegant way to eliminate this shift. To do this, connect the z21 to the computer via the z21-maintenance-tool, |
\\ | \\ | ||
- | =====GBM16XN===== | ||
- | | :!: **Activate only in case of GBM16XN detectors!** | | ||
- | This option will activate evaluating LAN_LOCONET_DETECTOR messages to support the GBM16XN detectors.\\ | ||
- | The reported input address is increased with one to meet the GBM16XN settings. This conflicts with normal LocoNet!\\ | ||
- | Z21 firmware: 1.24+\\ | ||
- | |||
- | \\ | ||
===== Power Manager===== | ===== Power Manager===== | ||
To add the Z21 to the __**[[: | To add the Z21 to the __**[[: | ||
{{roco: | {{roco: | ||
- | The address is fixed to 21.\\ | + | The address is fixed to 21, Interface ID is optional.\\ |
{{roco: | {{roco: | ||
+ | \\ | ||
+ | =====CAN Detector===== | ||
+ | Disable all emulation with the Z21 Maintenance Tool to prevent unwanted events:\\ | ||
+ | {{: | ||
\\ | \\ | ||
Line 111: | Line 136: | ||
The Z21 cannot access the LAN when connected to an ' | The Z21 cannot access the LAN when connected to an ' | ||
The easiest way to get connected is to add a small Desktop Ethernet Switch between the ' | The easiest way to get connected is to add a small Desktop Ethernet Switch between the ' | ||
+ | | :!: **"Set track power, by start of Z21, to STOP position" | ||
\\ | \\ | ||
==== z21start ==== | ==== z21start ==== |
roco/roco-z21-en.1546859883.txt.gz · Last modified: 2019/01/07 12:18 by rjversluis