Engineer-Joe posted:…..
I'm having different issues with large consists of mixed PS2 and PS3 engines after power cycles. I noticed it with the remote too so I was leaning towards this DCS version. I gave up searching and try to limit it's use. Overall, my app is working very well. Our grandson still prefers the app so it must be good.
I keep getting replies about signal strength or an engine that maybe not responding to commands from outside reasons like dirty track, etc.
The thing here is that when the mixed PS2 and PS3 consist is built, it works fine. It's after power cycling, or trying to run it days later for example, the consist won't work. I have to rebuild the consist. It seems that it's always the PS2 trailing or middle engines that get confused over directions or even lost by the software.
There was an instance where even the lead PS3 engine, got scrambled and had to be reset. On another occasion, a middle PS2 engine was lost and it took about a week for me to get the engine to be able to be recognized by the system again. It had a good battery and ran fine in conventional.
I traced and searched for the reasons for weeks and ended up abandoning the use of mixed consists of PS2 and PS3 for the growing pains of these types of results. I get replies of it's my fault (poor conditions) and I have ruled that out time and time again. I can run 6 O scale all PS3 engines or several all PS2 consists without these issues.
I think my next test should have been an all PS2 with at least 6 engines but to be frank, I'm tired of researching and shooting myself in the foot, only to come here with results that get bashed down to my problem only.
You should poll users (ones who run large consists) on what DCS version they are using, who have resisted upgrading because of these poor consist results.
