On Wed, Apr 16, 2025 at 06:50 AM, AD wrote:
What script is the warrants looking at?
A warrant is the script. A warrant/script for running the train is recorded and can then be played back (i.e. drives the train).
?
The script is created assuming all signals and blocks are clear. All actions including throttle settings are timed from when the train enters each block.? This is how it knows the speed, using the time and length of block. This also allows for dynamic speed profiling, when a train traverses a block too slow or too fast when compared to the script.
Aspect Speed to Value Mapping table (Warrant Preferences)
The automated train must know what to do when something changes.
For example, assuming the train is approaching a signal, the script indicates that at that point the train should be at 0.4 of its full throttle with an expected speed of 40mph.
'JMRI' needs to know what the aspect requires and that is defined in the preferences.
Looking up the table JMRI will calculate throttle/speed changes over the distance to the signal such that when the signal is reached it's at the required value. Say it's a Medium aspect with the speed value type
- If value is 20% 'Script', then the signal speed is 20% of the defined maximum speed and JMRI will adjust its speed as necessary
- Or if 30% 'Throttle', then the signal means 30% of maximum throttle and JMRI at some point will start to ramp down to that throttle setting
- Or if 40 'Miles per hour', then the signal speed is 40 mph, JMRI may not need to do any adjustments
- Or if 50 'Kilometers per hour', then the signal speed is 50 kph, JMRI at some point will start to ramp down to 50kph (31mph)
--
H.O. Australia (Layout in Progress)
Digikeijs DR5000 LocoNet
JMRI v5.10 DecoderPro/Warrants/CPE/SML/LogixNG
Java: OpenLogic jre-17.0.12.7 ? Windows 10
