Is there a way the user can decide when an engine should go inactive? Why does the App decide when an engine goes inactive?
I was laying track today and testing my progress with a PS2 PCC car. Everytime I would start the system, that engine would be inactive.
How can I get engines to stay active until I decide I do not want them active any longer?
Thanks
Ron
Replies sorted oldest to newest
MTH did change the app so that consists of engines stay active until you change them.
I believe it's in the way the app is designed. When you cycle the app, it's like doing a read on the remote. It looks for whatever is available.
I believe MTH can change any behavior they wish to an extent. They have to keep in mind all of the system quirks until the remote is no longer in play.
I'm not sure why your engine keeps going inactive though? It should be active if it's getting power when the system boots.
Engineer-Joe posted:
I'm not sure why your engine keeps going inactive though? It should be active if it's getting power when the system boots.
Well maybe you accidentally identified the problem Joe. The engine was on unpowered track that I would flip a switch AFTER the Z4000, TIU, WIU were powered. All of my engines sit on dark sidings until I decide I want to run them. The remote does not seem to behave this way. Strange that the WiFi would.
Ron
The Wi-Fi and app reads the track automatically where the remote doesn't.
Iv'e wondered the same thing. I have engines that sit on un-powered sidings that show as active. I can move an engine to a siding, shut it down, power off the siding, do a refresh and it still shows as active. I have come to the conclusion that the app does not have the code to recognize when an engine is inactive. Even when starting up fresh after being shutdown for the night it will still show engines as active when they are not. I just don't worry about it and start the engine I want.
Access to this requires an OGR Forum Supporting Membership
