Hi Don
I did not know that the DCS100 didnt keep at least the F1-F4 and F5-F8 packets refreshed on the track along with speed, the DCS50/51 I know does that ( when we use these we make sure we use no functions above 8 for that reason). The DCS52/210/240 also keeps the F9-F12, F13-20 and F21-F28 packets refreshed on the rails. If you dont have a DCC sniffer a way to check is set the horn on and then put the loco on the track.
When we have had the bell fail to stop (only fails to stop always starts) we never see the Stop bell on the loconet monitor, its something to do with the section being released before the stop action is performed, Ive never been able to trace it.
Your train stopping problem is almost certainly related to the errors and warnings in the log.? When using logix to fire sensors for dummy blocks they must fire in the correct order, the null pointer exception isnt good and Ive never seen one like it (which is a surprise since Ive crashed out every bit of code in dispatcher at some point!)
I have double checked the stopallocating sensor and it works. I did notice that after selecting the sensor in the drop down you must click on another field else it does not take (this happens a lot in the tables), so after youve saved reopen the transit and check it did update.
Steve G.
