Hi Bob. I can see the sensor states changing when the script is running and the trams are triggering them. I have not been lucky enough to catch if the state changes, or not, when the issue occurs. However, covering the sensor that has been ¡°missed¡± with my finger causes the tram to stop, indicating that the script was still waiting for a state change before continuing. Note that the problem is not dedicated to any one of the sensors. The script normally does exactly as required, but then, out of the blue, the tram fails to stop where it should. The AIU leds tell me that the sensors are operating correctly.
Could it be a data traffic/timing issue causing the change in state to be missed?
A little more info - when a tram passes over a sensor, the AIU indicates more than one change of state, when the front, middle and rear sections of the tram pass over the sensor. However, the state of the JMRI sensor only changes once.
Thoughts?
