On Sat, Nov 30, 2024 at 11:10 PM, Ken Cameron wrote:
Pawel,
?
Use the LocoNet Monitor and turn on timestamps to measure the delay or absence of delay. I would consider it a fault if Dispatcher was somehow bypassing the delay. But a trace with those timestamps would prove it.
?
It is a fault then... :(? ?
Take a look, with 600ms delay set in the connection settings, here is the sequence of turnout changes generated by a Route:
As you can see 600ms delay is inserted between every two commands.
?
And now Dispatcher with the same settings:
600ms delay setting was completely ignored... Just 31ms between the first two commands, and no more than 256ms between any other...
