Screensaver mode issue may indicate that a computer power-saving feature is one element that is causing the problems.? If the power
saving feature also powers down USB devices (including the Sprog), then that can cause issues.?
?
For my part, I turn off all power-saving modes on computers running JMRI when they have mains available.? That way unexpected power-saving side-effects don¡¯t
cause DCC system problems.
I have a combination of latest stable JMRI on Lubuntu (or Mac) with Sprog Nano with the following:
During start up
Load WiThrottle server
Load Webserver
Load my railroad config
set all unknown sensors to inactive
set power on
set all turnouts to closed
set power off
The moment the power is turned on some of my loco's start racing and its not always the same.
Then the set all turnouts to closed takes a while as it works through roughly 30 switch decoder addresses.
Power off and all goes quiet.
If I then turn on the power again manually those loco's that raced before will do this again until you take control of them and change speed or direction.
They then come under control and stay that way for the rest of the session.
My Lubuntu system went into screensaver mode after 10 minutes and the same happened.
Any idea what can be causing this?
I don't think the problem happens when I use a Tams Command Station.
Must give this a try and observe.
Under some circumstances I use the Tams for providing track commands and the Sprog Nano only to control turnout/DCC decoders.
Would it be possible to e.g. send a "speed zero" command similar to what a break booster does as a script file similar to setting the power on/off?
This might provide a work around.
