Typically a sensor triggers different events depending on the direction of the traffic.įor a correct functioning of the automatic mode at least the events enter and in have to be triggered in each block. Events in brackets are optional.įor the opposite direction of the traffic the allocation is to be repeated from opposite view. For blocks with two sensors ( enter and in).Īs explained below in more detail the following general order of events takes place: enter→ (shortin) → (pre2in) → in. The events are generated sequentially pre2in is simulated. For blocks with two physical sensor only.Ī combination of enter and pre2in. The events are generated sequentially shortin is simulated. For blocks with one physical sensor only.Ī combination of enter and shortin. The events are generated sequentially in is simulated. Using timed events is disadvised! No forum support for event timers longer than 100msĪ combination of enter and in. Limited support Long timers can severely disturb automatic control if overlapping subsequent events. This kind of event is not suited for trains but solely for Car systems. It is not connected to a physical sensor, but is generated after an in event from the previous block. Use with care! For short trains and automobiles only. The use of this event is discouraged: Use BBT instead.įree previous block. To use the exit event after the in event, the exit event must be set to the general route "all enter +/-" because after the in event the "from block" is set to the current block. When this happens the train is stopped immediately and put back in manual mode. This event is used for extra safety and detects if a train does not stop with in the distance between in and exit. Use this event type only if the sensor has no further functionality. (Lissy, BarJut, RailCom, …) This information is compared in auto mode to the identity-code set in the Loco properties, in manual mode this identity-code is shown in the block symbol. Some sensor systems provide more information like the address of the passing locomotive. The status will be evaluated if a reserve request is put by a train to make sure the whole block is electrically free. No action is taken as long as it is not unexpected. In combination with loco property "Stop at pre2in" this will be used as in can be used instead of or in addition to shortin Reduce the train velocity to V_min in case no free destination is found or in case the train should wait. Suitable for short trains which should, e.g., stop in front of a station building. In combination with the loco property "Use shortin event" this will be used as in. This event also frees up the previous block locked by this train. If the train has to stop the velocity is set to zero. Velocity is set to V_mid 1), in case no free destination is found or in case the train should wait.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |