Here is some interesting backstory... when developing the High Rail SensorTrack recording feature, I noticed that a SensorTrack would not always remain in the "armed" state. A SensorTrack would transition from the "armed" state (red light is blinking) to "idle" (red light stops blinking) for no apparent reason. It would sometimes take a second or so, or even minutes for the issue to occur. I spent countless hours trying to determine the cause from the perspective of High Rail. I thought High Rail must be sending a "junk" message, or doing something goofy. But it turns out that is not the case. The issue is noise from other activity on the PDI bus, which forces the SensorTrack out of the "armed to record" state. You can duplicate the noise issue using a CAB2 remote and a little patience. So why did High Rail expose the issue? It's because High Rail must constantly ask an "armed to record" SensorTrack for its status in order to keep High Rail synchronized with the SensorTrack's current state. That extra bit of traffic from the "keep me in sync" commands apparently causes enough "noise" to disarm a SensorTrack (but not always, which is frustrating). Railsounds and I spoke at length about the issue. Within a short period of time a "terminator" showed up in the mail from Railsounds. All is well.
The images posted by cjack are from the High Rail post regarding this issue.
