block-routes-en
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| block-routes-en [2019/01/13 16:24] – rjversluis | block-routes-en [2019/03/01 01:32] – [Event] rainerk | ||
|---|---|---|---|
| Line 50: | Line 50: | ||
| * ident | * ident | ||
| * shortin | * shortin | ||
| + | * [empty] - without assignment to an event, usable for locomotive functions. See: **[[# | ||
| For detailed explanation see chapter __**[[: | For detailed explanation see chapter __**[[: | ||
| | Events maybe multiple defined to enable multiple sensor systems like magnets and current detection. |\\ | | Events maybe multiple defined to enable multiple sensor systems like magnets and current detection. |\\ | ||
| + | ===Sensor without event === | ||
| + | A sensor, which is assigned to the block without event, are passed the parameters for actions. This provides the information about the current locomotive triggering the sensor (%lcid%) in order to trigger a loco function (whistle, high beam on, etc.). It is irrelevant whether this sensor is arranged before or after the block. It should be noted, however, that all sensors assigned to the block are checked for " | ||
| + | :!: Without occupancy or reservation of the block, the triggering of this sensor also generates the state //GHOST//. | ||
| \\ | \\ | ||
| ==== End pulse (endpulse) ==== | ==== End pulse (endpulse) ==== | ||
block-routes-en.txt · Last modified: 2024/01/25 14:43 by rjversluis