RE: [Jmri-developers] LocoNet Stale Slot checking

[Alex S. <mai...@aj...>]

> Could you check that the slot still gets purged if it's being read=20
> like this?  I don't know whether the slot read will reset the timer.

Well on my system here I select a loco on my DT400 and then unplug it =
and
wait. The code starts to poll the slot after the 90s and then after a =
while
(200s I guess) the DCS100 purges the slot and then the next read catches =
the
status change so I expect that the slot read does not reset the slot =
purge
timer.

Maybe I should extend the slot stale timeout from 90s to 200s like the
DCS100. I picked 90 because that is about how often the DT400 refreshes =
it's
active slots.=20

It also depends on whether there are other cases where the DCS100 does
things internally that we care about but never get told about. For =
instance
when you break a Universal Consist in the DCS100 the slot that you =
remove
gets updated but the slot above in the consist chain does not. If you =
only
had two slots in the consist, the top slot just sits there still =
indicating
consist - top, when in reality it is now normal in-use. This problem can =
be
solved by looking at slot status changes and noting when a consisted =
slot is
removed and then doing a slot read on who it was linked to.

BTW I have not looked into why the slot monitor stops updating when in =
"Show
al slots" mode. Any ideas?

Alex