Skip to content

Commit 99d41cd

Browse files
committed
documentation: How to stop trains
A description was added regarding alternatives on how to stop trains.
1 parent 0a74e99 commit 99d41cd

4 files changed

Lines changed: 39 additions & 2 deletions

File tree

extras/HowToStop.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# <a name="HowToStop"></a>Alternatives to stop trains #
2+
3+
This page describe possibilities to implement emergency stops.
4+
5+
## 1) Interrupt the signal between command station and boosters ##
6+
A first possibility is to interrupt the signal that flows between master station and boosters. In the figure below the yellow wire (difficult to see...) from LZV100 to boosters can be interrupted by the safety decoder's relay. This figure shows how the current board is connected.
7+
8+
Boosters that do not receive a valid DCC signal will remove power from the tracks. The disadvantage of this approach is that GBM decoders, which are also powered from the tracks, loose their status as well.
9+
![boosters](boosters.png "boosters")
10+
11+
## 2) Connect the E and M terminals of the command station ##
12+
A second possibility is described in the Lenz LZV100 manual and shown in the picture below (copyright picture is Lenz). A push button may connect the E terminal to M (Masse). If the button is pushed, power will be removed from the tracks. In principle this should provide the same functionality as described above.
13+
14+
The Lenz manual also describes that E between boosters and LZV100 may be connected permanently. The disadvantage of that is that a short-circuit at one booster will remove power from all other boosters, and this also all GBM decoders. This is undesirable in my specific case, where some decoders are powered from track.
15+
16+
![Emergency stop](lzv100.png "Emergency stop")
17+
18+
## 3) XpressNet: Stop operations request ##
19+
A third possibility is to let the decoder generate an Xpressnet *Stop operations request* (`Binary: 0010 0001`). This instruction tells the command station to immediately stop sending DCC packets to the track and to switch off the DCC track power. After turning off the track power, the command station sends Track power Off as a broadcast message several times to all XpressNet devices. The Traincontroller software, as well as all handhelds, will be informed of the emergency stop.
20+
21+
Like the previous alternatives the disadvantage of this approach is that GBM decoders will loose power.
22+
23+
## 4) XpressNet: Stop all locomotives request ##
24+
A fourth possibility is to let the decoder generate an Xpressnet *Stop all locomotives request* (`Binary: 1000 0000`). This instruction tells the command station to send DCC-RESET messages, which immediately stop all locomotives. The command station sends everything stopped to all XpressNet devices. The Traincontroller software, as well as all handhelds, will be informed of the emergency stop.
25+
26+
The advantage of this approach is that the DCC track power remains switched on, so that GBM decoders keep working. ALl lights (and other functions)
27+
will be switched off, however.
28+
29+
The current AtMega 16 based safety decoder board is unable to generate XpressNet messages. However, the lift decoder board does include all hardware to generate XpressNet messages, and a RS-485 library for this board was already implemented.
30+
31+
# AtMega 16 based safety decoder board #
32+
The AtMega 16 based safety decoder board can operate in two different states: **Local** and **Remote**
33+
34+
In the **Local** state it uses the first approach above to stop trains.
35+
36+
In the **Remote** state it sends a RS-Bus message to Traincontroller, which should subsequently uses the fourth approach to stop trains (`Einfrieren`). Also handhelds use this approach (although this may be reconfigured to the third approach).

extras/boosters.png

205 KB
Loading

extras/lzv100.png

11.3 KB
Loading

readme.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,9 @@ If such accessory message has not been received, the safety decoder assumes the
99
Whereas the watchdog function uses a rather *brute-force* method to stop trains (by removing power from the tracks), the safety decoder has also the ability to stop trains in a more *graceful* way by informing the train controller program via RS-Bus messages that the user pushed an emergency stop button. The train controller program has now the opportunity to bring all trains to a controlled stop, for example by sending an XpressNet stop all locomotives request / emergency stop command. The safety decoder will now monitor if the computer program has indeed ordered all trains to stop; if trains are still moving the safety decoder will activate the relay to force a *brute-force* stop.
1010

1111
Links to further information:
12-
- [details of the decoder's operation](extras/Description.md#Description)
13-
- [used addresses and configuration](extras/Addresses.md#Addresses)
12+
- [Details of the decoder's operation](extras/Description.md#Description)
13+
- [Used addresses and configuration](extras/Addresses.md#Addresses)
14+
- [Alternatives to stop trains](extras/HowToStop.md#HowToStop)
1415

1516
### Compatible DCC systems ###
1617
The safety decoder was specifically designed for a LENZ (LZV100 / LV102). The decoder is able to send RS-Bus messages, and the relay can connect the LZV100 master station to the LV102 boosters.

0 commit comments

Comments
 (0)