开云体育

Locked Re: Struggles with warrants - cont'd #warrants


 

Keith,

In "Preferences -> Warrants" there is "Trace warrant activity on console" option. ?If you enable the option, you will get useful information on the system console.

Here is the result from a test configuration.

15:51:16,702 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" on warrant "Left to Right" launched. runState= Running [AWT-EventQueue-0]
15:51:16,706 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" sets Signal "Alpha-Left-A" for block "OB::Alpha-Left". [AWT-EventQueue-0]
15:51:44,727 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" entering block "OB::Alpha-Left". [AWT-EventQueue-0]
15:51:44,728 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" sets Signal "Alpha-Right-B" for block "OB::Alpha-Right". [AWT-EventQueue-0]
15:51:55,506 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" entering block "OB::Alpha-Main". [AWT-EventQueue-0]
15:51:55,511 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" decrease speed to "Medium" in 1,692ms due to Signal at block "OB::Alpha-Main". [AWT-EventQueue-0]
15:51:57,257 jmri.jmrit.logix.Engineer???????????? INFO? - Train "1243" begins ramp to speed "Medium" in block "OB::Alpha-Main". [CommandDelay(1243-Medium)]
15:52:00,277 jmri.jmrit.logix.Engineer???????????? INFO? - Train "1243" ends ramp to speed "Medium" at block "OB::Alpha-Main". [Ramp(1243)]
15:52:07,772 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" entering block "OB::Alpha-Right". [AWT-EventQueue-0]
15:52:07,774 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" sets Signal "Beta-Left-A" for block "OB::Beta-Left". [AWT-EventQueue-0]
15:52:13,662 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" entering block "OB::Middle". [AWT-EventQueue-0]
15:52:13,664 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" decrease speed to "Stop" in 2,048ms due to Signal at block "OB::Middle". [AWT-EventQueue-0]
15:52:15,760 jmri.jmrit.logix.Engineer???????????? INFO? - Train "1243" begins ramp to speed "Stop" in block "OB::Middle". [CommandDelay(1243-Stop)]
15:52:22,554 jmri.jmrit.logix.Engineer???????????? INFO? - Train "1243" ends ramp to speed "Stop" at block "OB::Middle". [Ramp(1243)]
15:52:37,513 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" can proceed. Signal "Beta-Left-A" sets aspect "Normal". [AWT-EventQueue-0]
15:52:39,564 jmri.jmrit.logix.Engineer???????????? INFO? - Train "1243" begins ramp to speed "Normal" in block "OB::Middle". [AWT-EventQueue-0]
15:52:49,374 jmri.jmrit.logix.Engineer???????????? INFO? - Train "1243" ends ramp to speed "Normal" at block "OB::Middle". [Ramp(1243)]
15:52:55,410 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" entering block "OB::Beta-Left". [AWT-EventQueue-0]
15:52:55,412 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" sets Signal "Beta-Right-B" for block "OB::Beta-Right". [AWT-EventQueue-0]
15:52:55,412 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" decrease speed to "Medium" in 54ms due to Signal at block "OB::Beta-Main". [AWT-EventQueue-0]
15:52:55,517 jmri.jmrit.logix.Engineer???????????? INFO? - Train "1243" begins ramp to speed "Medium" in block "OB::Beta-Left". [CommandDelay(1243-Medium)]
15:53:00,799 jmri.jmrit.logix.Engineer???????????? INFO? - Train "1243" ends ramp to speed "Medium" at block "OB::Beta-Left". [Ramp(1243)]
15:53:04,957 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" entering block "OB::Beta-Main". [AWT-EventQueue-0]
15:53:09,403 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" entering block "OB::Beta-Right". [AWT-EventQueue-0]
15:53:15,165 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" entering block "OB::Right-Approach". [AWT-EventQueue-0]
15:53:32,222 jmri.jmrit.logix.Warrant????????????? INFO? - Train "1243" ends warrant "Left to Right". Now occupying block "OB::Right-Approach". [Engineer(1243)]

The "sets Signal" lines indicate that the signal mast will be the controlling signal mast. ?It is not changing the aspect.

The "decrease speed" lines indicate the speed will need to be decreased, but the ramp down will be delayed by some time value. ?In theory, the delay and ramp down should result in a stop near the end of the block. ?NOTE: ?There is a bug that causes the message to always display "1ms". ?I have submitted a fix to display the correct value. ?That will be available in the 5.9.6 test release. ?

When testing with your layout, the ramp down delays tend to be in 20 to 60 second range.

Dave Sand



----- Original message -----
From: Keith Williams <directorsixfive@...>
Subject: Re: [jmriusers] Struggles with warrants - cont'd #warrants
Date: Wednesday, October 23, 2024 1:01 PM

Dave,
Very interesting.? To answer your questions:
1.? I tried both - created with an N-X and also with the learning?route.? The learning?route is the current one.? In learning?mode (auto run) the train runs at full "normal" speed, causing the late arrival messages to the next block when it is run at the real?"normal" speed for that block..
2.? Yes the loco roster has speed profiles for most of the loco's.? I was using 8235 (part of a consist w/8241) for my tests.

Comments about your results:
1.? I was not aware you could (should) revise the elapsed time, as the instructions say that if changes in the block require changes in the individual timing of a line, the overall timing of the block should?stay the same.
2.? Your?third point is where I am having difficulty.? The down ramp time may in fact be correct, but it starts at the wrong time
3.? Regarding Block 3 testing: when you say "When the time expired, I would get a delayed arrival for SM55.? If I did nothing, eventually it would ramp down and stop for the signal."? Where exactly did it ramp down for the red?? Normally (without messing with?the elapsed time values) it would enter the block, ramp up to the "normal speed, then realize that this was a siding block between divirging?points, and ramp back down to the required speed, normally "medium", then stop, usually only 15% or 20% into the block.? This would imply that the timing is fixed, based on the warrant "teach" speed, rather than?dynamic, based on the current speed.? This leads to your comment about changing the timing of the sidings.? I?will work on that.....!
4.? 60 Seconds is about 3 times the normal timing.? My "normal" speed is 50 sMPH, and "medium" is 25 sMPH
5.? This problem also occurs when running lap 1 or lap 2, which does not traverse any of the passing sidings. For example, if in MB1, traveling?toward MB2, and SM45 is thrown, giving a red signal, the train will stop about 20% into MB1, (Varies from 20% to 60%, but always very short of the signal) and send a message that it is waiting for the signal to clear before?it can proceed.

I will continue to test, to see if I can improve it.? Thank you?very?much for your efforts!? I do appreciate this!

On Tue, Oct 22, 2024 at 1:35?AM Dave Sand via <ds=dfm.sandsys.org@groups.io> wrote:

Keith,

I did a simulated test of Cleaner 3rd Lap.? Was this created using learning mode or as a NX warrant?? Does the loco roster entry have a speed profile?

I used Side Block 3 as the test case where the train has to stop for a Stop signal indication.

The general behavior is that when a train enters a block it ramps up to the block speed if necessary.? If a reduced speed is required at the end of the block, the down ramp time is calculated based on the current speed and the target speed.? The ramp values are in Preferences -> Warrants. ?

The elapsed time for Side Block 3 in the Warrant was about 22 seconds.? When the time expired, I would get a delayed arrival for SM55.? If I did nothing, eventually it would ramp down and stop for the signal.? Based on that clue, I tried several elapsed times. ?60 seconds worked.? The train ran at normal speed for 45 seconds and then spent 11 seconds ramping down to stop.

These are preliminary results and are not consistent from run to run.

Dave Sand



----- Original message -----
From: Keith Williams <directorsixfive@...>
Subject: Re: [jmriusers] Struggles with warrants - cont'd #warrants
Date: Sunday, October 13, 2024 1:38 PM

Dave, I just uploaded? it.? See if you can see anything im doing?wrong or not doing right, lol!

On Sat, Oct 12, 2024 at 2:54?PM Dave Sand via <ds=dfm.sandsys.org@groups.io> wrote:

Keith,

If you upload your current xml file to the group's ProblemsBeingWorkedOn file folder and indicated which warrant is not behaving as expect, we might be able to figure out what is happening.

Dave Sand


----- Original message -----
From: Keith Williams <directorsixfive@...>
Subject: Re: [jmriusers] Struggles with warrants - cont'd #warrants
Date: Saturday, October 12, 2024 8:18 AM

Nags,
this statement "The default is to incrementally slow the train before reaching the end of the approach block." is what I want to happen!? It does not.

On Fri, Oct 11, 2024 at 7:32?PM Nags via <snowy999=bigpond.com@groups.io> wrote:
Maybe this?
The checkbox Don't Ramp Speed changes Sets an option on how to change the speed when a signal or rogue occupation is detected ahead. The default is to incrementally slow the train before reaching the end of the approach block. Selecting the option will make an immediate speed change upon entering the approach block.
?
--
H.O. Australia (Layout in Progress)
Digikeijs DR5000 LocoNet
JMRI v5.8 DecoderPro/Warrants/CPE/SML/LogixNG
Windows 10










Join jmriusers@groups.io to automatically receive all group messages.