Thanks Steve,
is there any particular program I can use on Windows to edit the file? I seem to remember notepad gives a very weird format.
I will take out all the stop sensors from the sections and see how the layout reacts.
My trains are varying between block length and half block length of the main running lines, excluding smaller turnout blocks etc obviously. usually loco + 4-5 coaches.
all wheel are resistance wheels, track is cleaned regularly.
i don¡¯t think the sensors are going active/inactive/active, however I do have one block that goes inactive even though the BDL168 sensor is still active (I suspect one of my Logix has a mis-informed conditional, even my turnout controlled turntable moves occasionally). This block is no-where near the problem area, though.
I feel it¡¯s unrelated because I don¡¯t see sensors change state when the overlap occurs, I¡¯ve repeated it every time I¡¯ve run dispatcher watching sensors, blocks etc to see any oddities and I¡¯ve been dumbfounded trying to find evidence of why, which is what I¡¯m sure you¡¯re experiencing too.
I will also try a ¡°disconnected¡± version of my panel file. Loconet simulator and panel sensors to emulate blocks being occupied, and attempt to cause it manually.
Failing that, I¡¯ll edit the default file, however I do that, and debug it and do a video as well just to prove I¡¯m not crazy
although we are all a little crazy, let¡¯s be honest.
thanks! Sorry this has been such a pain.
--
Thanks
Mitch
