Tony,
?
I second Steve's suggestion
Instead, I'd strongly suggest turning on the TRACE logging for jmri.jmrit.dispatcher and carefully read through that output.
?
I've used traces and it was very helpful. I could see what was being checked (e.g. Signal speed, Block occupancy) when and why the code made throttle changes.
--
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
