Hi Bob
The Locos I noticed this with were fitted with ESU V4 LokSound decoders. ?But I now believe the issue I saw was probably just another manifestation of my fundamental problem which is a DCS100 which occasionally misses a LocoNet packet,
The problems I have seen are when a LocoNet command such as turn a Horn On/Off or to Start/Stop a locomotive is missed when running auto trains.
Missing a Horn start is not obvious, ?Missing a Horn stop is very obvious. ?Issuing a Monitor Slots command immediately after a loco does not turn off its horn shows that F2 is still on in the DCS100 but the F2 off command was sent to LocoNet (as seen on a second JMRI running on a second computer eaves dropping onto the LocoNet via a second PR4).
A missed Loco start (Set speed of loco x to YY) command is evidenced by an auto train not starting a Transit or following a Pause until another Set speed of loco in slot x command is sued onto locket. ?Again refreshing Monitor slots shows the DCS100 did not get the Set loco speed command.
A missed Loco stop (Set speed of loco x to 0) command generally breaks auto trains, results in memory leaks and eventually a processor core running parts of JMRI goes to 100% and JMRI freezes for a period of time. ?A JMRI restart is required to re-establish auto train operation. ?Again I have confirmed that JMRI sent the command to LocoNet and that the DCS100 did not see it.
I have separated the layout control LocoNet (turnouts, block detection and signalling) from the DCS100 LocoNet ?(i.e. LocoNet and LocoNet2) and still observed the same behaviour with a similar frequency of occurrence. ?Tonight I was able to carry out the ultimate test using a borrowed DCS100. ?So far I have run for over 5 hours without any drop LocoNet commands with the system configured back to a single LocoNet bus.
So it looks like my DCS100 has issues not seen on another. ?
Thanks?
Don McG
