REMOTE "MISSING" number....okay so who has this happened to and how did you fix it?

yes, it happens

you have to reset it

you will loose everything in it

you should save a copy to the computer if you'd prefer

Joe is essentially correct in his post above.

However, going forward there are two things that you can do to mitigate the problem:

• Always be using the latest version of the DCS software. At present, I have personally found that the incidence of this particular problem occurring is greatly diminished using DCS 5.0, maybe even 0 incidents for me.
• Make it a practice to backup the contents of your remote every time you add, delete or change anything. This has bailed me out on several occasions over the years, particularly while beta testing DCS.

This and a whole lot more is all in “The DCS Companion 3rd Edition!" This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store!

If he saves the contents of another  remote with ID #1 to the computer he could then copy the contents to the remote with the missing ID #. 

Gregg,

If he saves the contents of another  remote with ID #1 to the computer he could then copy the contents to the remote with the missing ID #.

I'm not quite sure what you mean.

If he has another remote that is identical to the one that lost ID#1, then, yes, that would correct the problem.

Yeah That's pretty much what I meant.... .  or almost identical, you can always  make a few adjustments. Engine IDs should be the same in any remote  unless running in normal mode with engines associated with different tiu.

I have 5 that where identical until today.  Thank you all.  I have to reprogram 15 engines.

John C. posted:

I have 5 that where identical until today.  Thank you all.  I have to reprogram 15 engines.

If you mean you reset the remote and now have to add 15 engines back please use a programming track with only one engine at a time powered. Everything else should be on dead track.

After adding make sure the engine added with the same ID that's in the other remotes . If not the other remotes will not communicate with the recently added engine....

If it does add with a different ID you can always edit the address .

After adding I like to make sure the ID is going to stick by powering down the layout for a few seconds (maybe 15)     power up again and try  to start the engine.... 

What about the backup of one of the good remotes and restore to the bad remote as Barry and Gregg suggested above?

rtr12 posted:

What about the backup of one of the good remotes and restore to the bad remote as Barry and Gregg suggested above?

I have never done that, but am going to give it a shot.  I'm also going to get the required items to update my 2 TIUs and 5 Remotes.  I'm at 4.2 with the exception of 1 Remote that is the 5.0.

Not too hard as I recall, I was able to do it a year or so ago. I believe the DCS loader walks you through it, if memory hasn't failed again. I think you will be fine with it, and good luck!

John,

I'm at 4.2 with the exception of 1 Remote that is the 5.0.

Oh, really? That could be the cause of your missing engine slot issue.

It's a bad idea to mix and match DCS versions on a layout. That's one way that unusual problems, like yours, can  happen.

No matter how you go about this,,, A remote reset is the only way out. .Even if you had the remotes contents saved on the computer you still have to reset the remote when asked on the restore.

Bite the bullet and go for version 5.    Version 4./2 was terrible for super mode runners. 4.3 was much better. 5 is even better.

As for the missing ID.... It happens  every now & then....

I recommend saving the data on a remote, that is set up exactly as you want it--soft keys, loco #'s, etc--to a computer and then cloning all other remotes from the computer.  You will never have to re-add items.  If a remote gets fouled up, simply download the data from the computer onto the remote, a process which commences with a remote reset to clear it out.

Hi all,

I know this issue of "ghost" engines comes up from time to time, and the advice everyone has given is correct.  The best way to handle this bug is to get your remote the way you want it (all engines, tracks, switches, and accessories entered) and then back it up to the PC.  If anything ever goes wrong you can reset the remote and restore it from the file on your PC.  It's just like having your phone, tablet, or PC backed up to the cloud.  You have a way to restore your data when something goes wrong.

However, it's not entirely true that once a ghost has been created that it can't be fixed.  Contractually I can't go into all the details, but Barry and a few others on the forum can verify that I have cleared ghosts from their remote files in the past.  If you have a remote with a missing "ghost" engine address, feel free to send it to me for repair.  I need the remote data file that you back up to the PC and the engine ID# that's missing.  I can then send you back a corrected remote data file with the ghost cleared and the missing address restored as a blank slot.

While I can't share all the gory details, I can give you a brief explanation of how the ghosts get created.  There are two blocks of data in the remote data file for each engine.  One block contains the engine name and settings.  The second block contains the list of softkeys for that engine.  The remote reacts differently if either block of data is missing.  If block 2 (the softkeys) is empty the remote displays "MTC  MTC  MTC  MTC" for all the softkeys.  You see that one crop up a lot if you load an engine on a track with weak signal.  If block 1 (engine name and settings) is empty, but block 2 has softkey data, the remote doesn't know how to handle it.  The engine is "there," but it isn't.  That's when we see a missing "ghost" engine in the list.  This can happen when you add a new engine, edit the address of an existing engine, or delete an engine.  Something has to go wrong part way through one of those processes.  For instance, when you edit an engine address the remote copies both blocks of data from to the slots of the existing engine number to the slots of the new engine number.  It then goes back and deletes the data from the slots for the old engine number.  If the remote looses power part way through the edit (no, the batteries NEVER come loose ), the delete process may not have finished.   The same sort of failure can happen when you delete an engine.  The softkeys get deleted first, so if the remote looses power half way through you'll get a ghost.  The engine loading process is more complex and there are several ways things can get corrupted if you have weak track signal.  In short, it pays to use a programming track, keep fresh batteries in your remote, and make sure your batteries fit well.

I can personally attest to the fact that Dave can, indeed, correct this problem when it arises. I've asked him many times what is the format of the remote clone file so that I can do the fix myself. However, he claims "that if he told me, he'd have to ..." you can guess the rest.  

The best way to correct the problem is to always have a current, backed-up clone copy of your DCS remote available. Make a new clone after making additions to your remote and don't overlay an old clone when you make a new one. Also, it's worth the time to take a quick survey of the remote occasionally to ensure that its integrity is intact.

I do appreciate that you guys are explaining some of the reasons.

....it would be nice to rid the system at the operator level.

 So how about they develop a "find lost address" in the remote? It could self scan for address that are missing full info in both "blocks of data". Then maybe it would allow the operator a chance to review the slot and see if it is correct or not.

Joe, the problem is solvable at the operator level:  Back up your remote to a PC while it's working perfect.  It's very easy to do.

But doctor it hurts when I do that.

Well, don't do that!

Joe, have some self-confidence.  Even jackasses and elephants can do it.  Start the loader program, click on the save or restore icons, and there are the detailed instructions.