3/6 PS3 engines I’ve attempted to run with this system haven’t worked. Just sit there. I don’t understand why either they all do, or all don’t, but why the split? All Railking. Working: Chessie GP9, Conrail RS3, UP 2-8-0, from the starter set the remote commander was included in. Not working: WM GP7, EL FM TM, PRR K4. Any ideas? So far, all PS2 engines recognize start up command. Remote commander is hooked up to a Z1000 brick, not the Z500 brick that was included with set. Thanks.
Replies sorted oldest to newest
If any of the locos were run in DCS prior to attempting to operate with the Remote Commander, they must be reset to factory address 0. PS3 locos made after 2014 can be reset using the a Remote Commander by pressing SND DIR “-“ keys in sequence with a confirmation two whistle/horn blasts, if successful. Locos may prior to 2014 (IIRC) and all PS2 locos require a factory reset using a TIU.
Jon - thank you. That did the trick. All 3 responded. Coupla PS2s bought used need DCS resets.
Jon - 4/5 PS2s took the cure and are now responding to Remote Commander. My friend performed an engine reset that should’ve deleted #5 from the DCS remote. He performed the reset twice, and it still appeared in the engine roster. Any idea what this could be? The engine is a WM VO1000 30-2643-1. Thanks.
@Mark V. Spadaro posted:Jon - 4/5 PS2s took the cure and are now responding to Remote Commander. My friend performed an engine that should’ve deleted #5 from the DCS remote. He performed the reset twice, and it still appeared in the engine roster. Any idea what this could be? The engine is a WM VO1000 30-2643-1. Thanks.
If it has a battery it may need replaced.
Good thought, Marty, but it has a bcr2 in place, and I believe it read good ot high on the battery charge.
In conventional do the shutdown sounds linger for a time after power is dropped?
I can’t be absolutely sure, but, I believe that to be correct. I will check for certain later.
Once you do the factory reset with the DCS system, you need to drop power and remove the TIU from the picture. If you add the engine back in, the factory reset no longer applies and the DCS-RC won't recognize it.
GRJ - the fella that was working the handheld said he did the exact same thing to do the reset, that was done on the 4 other PS2s which worked successfully.
What can I see, it appears that hasn't had a successful factory reset. Not much more I can discern from a distance.
If the engine stayed in the remote (you said remained in roster) a DCS reset did not occur. I guess the issue is whether the engine has a good DCS signal with the TIU. If just a battery problem, the engine would have deleted from the remote, but when track power removed the engine would not reset the memory since power of the battery BCR not available. But if the engine did not delete from the remote, something else is going wrong. Try a DCS signal strength test with the engine started and running via the TIU. G
Access to this requires an OGR Forum Supporting Membership
