Factory Reset PS2 Engine using DCS Explorer

do a conventional reset with z 4000 1W 5B with 1/2 second intervals if it work correctly you will hear 2 whistle toots to let you know it's  been reset!

1 whistle and 5 bells in 1/2 second intervals  .

good luck

Alan

Bill,

In order to do a Factory Reset from the DCS App using the DCS Explorer (or using the DCS App with a WIU or using a DCS Remote), the engine must be in the app to begin with. Note that a transformer (conventional) reset is different and is not a DCS Factory Reset.

Regardless, this sounds more like an issue with your DCS Explorer, WiFi connection and/or layout than it does an engine issue.

More information would be helpful:

• What is your DCS Explorer's WiFi connection, MTH or Home?
• What smartphone or tablet are you using?
• What transformer are you using?
• Which LEDs are illuminated on the DCS Explorer?
• Have you ever previously been enable to add and/or operate an engine with the DCS Explorer?
• What version of firmware is in your DCS Explorer? It should be 1.2.
• What release number of the DCS App are you using? It should be 3.1.0.
• Describe exactly how you attempt to add the engine to the DCS App and exactly what happens at each step. Start when you enter the train room and leave nothing out.

Barry,

Thanks for your response. Correct, was able to successful reset a engine once its listed as an active engine. My problem is trying to reset the engine thinking that will resolve the "Request Time Out" when trying to add a new MTH PS2 engine. 

Reply to your questions above

• Using the MTH wifi connection
• Using iPhone 7 (Reinstalled app to get DCS explorer working initially)
• No transformer. Using DCS Explorer with provided wall plug feed to Lock-On
• Power Light Green. WPS Off. Wifi Pulsing Blue. Track light Red 
• Yes, successfully added engines before and after this particular engine.
• Version Firmare: v 1.0 (assuming information under unit is what you referred to). Unit came from RTR set. No flash/updates done.
• DCS App Version: v.3.1.0
• Below are steps when adding train first train that DCS explorer read followed by train that did through missing
  1. Plug in DCS explorer to track Lock-On
  2. DCS Lights: PWR=GRN; WI-FI=BLUE Track = RED
  3. Add engine #1 to track
  4. Opened app
  5. Track light turns purple. Engine illuminates 
  6. Added engine using APP > Add MTH Engine > Pressed "Start Up" and worked flawlessly.
  7. Removed engine 1 from track (Literally took engine off track - no shutdown). Engine one listed under inactive
  8. Placed different engine on track. Track light remained purple. Engine #2 immediately began to move (Engine was not added to app).
  9. Attempted to add engine #2 following steps in #6. Received timeout request during "Reading" sequence
  10. Removed Engine 2 and track light still remained purple. Engine #2 began to move again. Each time it moves, have no control over it.

Bill,

I see two possible problems.

Version Firmare: v 1.0 (assuming information under unit is what you referred to). Unit came from RTR set. No flash/updates done.

If you're not using firmware 1.2 in the DCS Explorer, you may encounter some small issues with engine control. Or maybe not. MTH wasn't real specific about what they changed on 1.2.

Placed different engine on track. Track light remained purple. Engine #2 immediately began to move (Engine was not added to app).

This, however, is troubling if you did this without turning off power to the track at all.

The DCS Explorer has, in my opinion, a design flaw. That is, there is no way to turn off track power without actually disconnecting the unit from the track. I've suggested to MTH that they build a "soft power switch" into the DCS App so that an operator can remove track power in order to change remove or place engines and rolling stock onto and off the track without risking a short circuit.

Further, when the DCS Explorer is disconnected from the track, it doesn't issue a watchdog signal when it is reconnected. This causes all DCS engines to turn on in conventional mode.

In your case, my concern is that you may have damaged the DCS Explorer, as happened to my son several months ago. In his case, he experienced a derailment and, after he cleared it, he found that the DCS Explorer's fuse had blown, which is not supposed to be a common occurrence.

After replacing the fuse, each time that he rebooted the explorer its behavior had changed. Instead of waiting for a refresh command before powering the track, it powered the track as soon as the explorer itself was powered on. Further, the watchdog signal was no longer being generated and any engines on the track immediately came up in conventional mode.

Even worse, any 5 volt PS2 engines began continuously blowing their horns and any 3 volt PS2 engines took off in forward under track power.

If he waited until the explorer completely rebooted and stabilized itself, he could issue a startup command and get em to be controllable from the app. However, any time he disconnected the power from the trac and plugged it back in again, or rebooted the explore, the problem came back.

Working with MTH R&D, we figured out that the explorer was now putting some DC voltage into the tracks, as well as the expected AC. The explorer had to be replaced.

I have since modified my son's layout by doing 3 things, which I would advise any DCS Explore user to do as well:

• Inserted a switch in line between the DCS Explorer and the tracks so as to be able to turn off power to the tracks to swap out equipment.
• Connected, in parallel with the DCS Explorer (passive mode), a DCS Remote Commander receiver so that any time that rack power is interrupted via the switch, a watchdog signal is sent to all engines on the track.
• Replaced the low amperage power supply (a Z500 brick) with a Z1000 brick to prevent a recurrence of the current overdraw that caused the original problem.

Is your problem engine a 3 volt PS2 (or maybe a PS3)? Does the other engine now behave the same way that the first engine behaves? If so, try the following:

• Disconnect the explorer from the track.
• Power up the explorer normally and allow its LEDs to stabilize.
• Place the problem engine on the track but keep a hand on it so it cannot move.
• Connect the explorer to the track.
• While holding the engine, attempt to add it to the explorer. If it adds, tap Shutdown.

If that works, send the explorer in for repair or replacement.

Report back with your results - good luck.

I was searching for a solution to the problem of adding Proto 2.0 engines to the DCS Explorer with the WiFi DCS app on my iPhone. I read on one of the forums that the Proto 3.0 locos are not polarity sensitive but that the Proto 2.0 locos are. My Proto 3.0 locos we loading up and running fine but I had three different Proto 2.0 locos that the Explorer just would not find. I am using Atlas track and the feeder section is not labeled + or -. I reversed the wires on the feeder and added all three Proto 2.0 locos without issues. Shut them down and restarted them again with no problem. I did discover that the battery has died in the Sd-24. As soon as you unplug the power the sound and lights would go off but the other 2 locos continued to run for 12 to 14 seconds after the power was removed. Hope this helps someone else.