System emergency stop
Emergency stop
Operational disruptions
The question that keeps cropping up is how best to react to faults that occur during operation of a model railway system, such as short circuits in the track or impending collisions, wrong turns, etc.
In both the TC Forum (German and English parts) specific situations are described and solutions discussed.
This was also the case at the TC Stammtisch in Munich.
Unfortunately, the TrainController variants Bronze and Silver do not offer the same functions as operations as the GOLD variant.
Users of the Bronze or Silver version may be able to perform the action in the form of "a quick finger" manually via the TC menu bar(s).
Incident scenarios
In diesem Dokument wird der Versuch unternommen ein Lösungskonzept für die verschiedenen Störfall - Szenarien anzubieten.
This document attempts to offer a solution concept for the various incident scenarios.
The methods and procedures presented here do not claim to be "error-free" and are certainly "capable of improvement".
The solution concept must be "ported" to the respective user's needs.
How it works
Object functions (from left to right):
- STOP / Emergency Stop - switch: causes all trains to stop and blocks all (new) train journeys as well as those already started using block locks
- RELEASE - button: removes the train journey and block locks, sets the TC system to stop; Preparation for general release using the START button in the top TC menu
- Emergency stop sensor activation (switch): enables the suppression of the (occupancy) detector information
- Summary determination of a fault (trackman): switches on the "STOP / emergency stop switch" when a fault is detected by a detector
- Detector (e.g. track or switch): reports the re-connection of the track voltage after a fault * or the "statement" that a fault has occurred
- Detector (e.g. emergency stop button on the system): reports a fault triggered by the user
What is needed?
A function that continues to stop the train journeys, but allows individual objects on the system to be operated specifically and individually.
It should also be possible to specifically terminate individual train journeys so that they cannot start again.
Download document
The document can be accessed as a PDF under the title "TC-EmergencyStopWhat_to_do.pdf".
No changes in frozen mode
As long as TrainController is in frozen mode, it is strictly forbidden to change the state of the system. Frozen means frozen. This applies to the entire system.
Frozen mode
As a general rule and for security reasons, the state of an object may not be changed while the session is frozen or stopped.
This means: When frozen or stopped,
- no schedules can be started,
- no blocks can be reserved,
- no routes can be activated,
- no switches can be switched,
- no buttons can be pressed,
- no macros or operations can be carried out, etc.
In particular, this also means that the system operation to start the system cannot be performed while the system is frozen.
This is a fundamental principle and cannot be changed.
If you want to change something on the system when it is frozen, TrainController must be switched to the emergency stop ("red hand").
TrainController usually goes into the frozen state when the command station is switched off or reports a short circuit.
Restart after emergency stop
In this post, Mr. Freiwald has described the correct procedure.
If TrainController has been switched to emergency stop, there are no longer any running train journeys. TrainController therefore no longer has control over trains that are running (or have been set in motion). The control center should (if possible) be set in such a way that when the control center is switched back on, the previously running trains are not automatically set in motion by the control center. From this state, all previously active train journeys can then be restarted using a menu command (but with the current or updated train positions).
Weblinks
- Emergency stop: Forum
- Instructions: TC-NotAus-Was_tun.pdf"
- Frozen mode: Forum
- TC-wiki: Emergency stop in case of fault
- -- Jens Mohr 19:03, 16. Mai 2014 († 2023)
- bearbeitet: Wohlmannstetter (Diskussion) 14:59, 15. Apr. 2021 (CEST), Uslex (Diskussion) 11:30, 18. Jul. 2022 (CEST), Uslex (Diskussion) 19:19, 16. Jul. 2024 (CEST), DeepPurple 16:21, 16. Jan. 2025 (CEST)