¿ªÔÆÌåÓý

  1. Jmriusers
  2. Messages
Single Messages Topics Expanded Polls

Re: Calculating speed changes in automation

 

¿ªÔÆÌåÓý

Dave

Do you know how i can trace what dispatcher is doing to determine engine speed?

Are you able to look at the software code and determine the algorithm being used when dispatcher users head and tail detection and sml signals to determine speed.

Using Steve¡¯s implied info that it looks at 4 signals ahead of the train then ?there must be a name of a speed in the warrants table of signal speeds for each combination of lights and block occupation and block allocation. ?
I assume it¡¯s the max speed i set when creating a train x % in the warrant table modified by the block maximum. ? But that doesnt seam to give me the results i see in the loconet monitor.

Nat suggests that the speed info is in the system console after setting the debug item . While that works for warrants , giving him trace info, which he uses it doesnt work for dispatcher.

Tony




On Apr 24, 2025, at 9:29?PM, Dave Sand <ds@...> wrote:

?
Tony,

The LogixNG messages are from a year or two ago when I was helping out. ?To stop them, go to Tools -> Tables -> LogixNG. ?
<Screenshot 2025-04-24 at 8.26.44?PM.png>
Uncheck both entries. ?This will stop the LogixNG messages. ?Do a Store to retain the changes.

Dave Sand



----- Original message -----
Subject: Re: [jmriusers] Calculating speed changes in automation
Date: Thursday, April 24, 2025 7:32 PM

Dear Mr nag

You¡¯re confusing me.
Do i enter ¡®jmri.jmrit.dispatcher
Or jmri.jmrit.logix

Or both ,one after the other

I dont use warrants or oblocks -so why would i log them.

You say copy jmri.jmrit.logix¡¯
Where do i find that so i can copy it

If i dont change the debug it defaults to logixng messages which appear in the system console.
I dont know why as i dont use logixng.

Tony



On Apr 24, 2025, at 8:06?PM, Nags via groups.io <snowy999@...> wrote:
?
Hi Tony,
?
I wrote these notes back when I first needed to do a trace
You'll need to change it to? ?jmri.jmrit.dispatcher?
?
Debugging Log

Command steps can be output, viewed and copied in the System Console.

To allow Warrant/Oblock logging

From the main PanelPro menu select "Debug -> Display / Edit Log Categories".?

At the bottom, overtype "Root Logging Level" with "jmri.jmrit.logix".? Change DEBUG to TRACE, Click on "Set new Logging Level for this session".

The debug level messages for OBlocks and Warrants will now be written to the system console.

Copy =>?????????????????????? jmri.jmrit.logix

?


<inline.0.part>


?

System Console: access under Help tab. To extract log details, use the copy to clipboard then paste into Notepad text document. Note this change is only in effect during the session, after which it reverts to "Root Logging Level".

?
?
--
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
Join [email protected] to automatically receive all group messages.