DCS Remote Commander question (the IR low end one)

You have to do full factory reset with the DCS not the dcs commander or transfomer either. Then they should run with remote commander and also if premier engines make sure your switch is in dcs not dcc and your three rail and two rail switch in three rail.

Yes you can do a full factory reset with the DCS Commander. It says so in the manual and in Barry's book. I sat with the manual in my hand and followed the steps. Hold reset until Feature flashes, release, push it again until Factory flashes, the press SEL. And it did reset my K-4 from 2 to 1.

Frank

I believe there was a recent thread stating that the SuperSnap lockon degrades the DCS signal. Try bypassing it and see if you get better results.

Barry,

They are sitting on Fastrack at this time, wired straight to the tabs under the track. First thing I thought of.

The caboose lights up when placed on the Fastrack with the other engines.

Frank

That's exactly how my tinplate layout is wired:  FasTrack, with the DCS Remote Commander receiver connected to the track via the two standard FasTrack hook-up wires (attached to the tabs under the track).

No operational problems whatsoever, except when I forget to point the remote at the receiver when I'm trying to initiate or change some action.

You stated:

Supersnap terminal also lit up

Disconnect it from the track completely.

Since the engine(s) power up "silent" that's a good indicator the base receiver unit is sending out commands to the engine.  That is, the so-called "watchdog" DCS signal is sent to all engines on the track on power up which keeps them silent until they receive a subsequent DCS command (typically Start Up being the first command).

My guess is when you performed the factory resets, these somehow did not take whether from weak engine battery or whatever.  The experts will correct me, but I thought that if you can read the engines address (for example, you suggest you could "read" that it was address 1), then this means it has an assigned address rather than being at the desired factory "unassigned" address.

Very clever! I will try that. I did the reset then "added". I'll do the reset and not add.

Frank

I believe if you're in the position to "read" the address, the engine is added to the remote, and it's no longer at address zero.  The only way to read the address is by having the engine added to the remote, thus making it NOT in factory reset condition.

Here's the procedure I followed some months ago to reset an engine to Factory Default:

MTH Factory Default reset:

Here are the steps I followed, after some trial-and-error, to get an MTH 254E (PS3) to reset to factory default so it would once again operate on my tinplate pike, which is currently only equipped with the DCS Remote Commander:

1.  Placed engine and only this engine--on the track of my full DCS layout (which is separate from the tinplate layout).

2.  Added engine to the active list per the usual procedure.

3.  Pressed "Startup" and waited for the sounds, lights, etc. to start up (which occurs almost instantly).

4.  Selected "Menu" on the remote

5.  Scrolled to and selected "Advanced"

6.  Scrolled to and selected "Factory Reset"

7.  Scrolled to and selected the proper engine-- in this case "Green 254"

8.  Selected and confirmed selection (at this point the sounds became a bit louder and distorted)

9.  Selected "Shut down"

10.  Turned off track power

11.  Moved the engine to my tinplate layout, and plugged in the DCS Remote Commander to power the track

12.  Pressed the "SU/SD" button on the DCS Remote Commander remote and all worked fine from that point on

The only change I'd do to Allan's procedure is after confirming the Factory Reset, I'd just kill the track power, I don't push any more buttons on the remote.  I've never had a failed Factory Reset doing that.

Alright guys, the reset and removal of the engine without an add was the answer. My wingman (wing girl?) will be very happy. Stan the Man, thanks!

Frank

Roger that. Problem to solution in under 24 hours.