It is not the job of dispatcher to pace the commands, the fact that someone put it a delay in routes when it should not have been placed?
?
OK, but as Ken noticed earlier, even if we ignore the separate "additional delay" settings in Routes, there is a global JMRI setting in the connections, that should enforce the delay between all turnout commands sent from the JMRI. Routes and other turnout controls follow it, but Dispatcher does not. Whether it theoretically is a Dispatcher job to pace the commands or not, it should not ignore the setting that is in the connections...
