LOST DCS ENGINE ID IN REMOTE

First off, did you try putting only that engine on a test track and doing a Recover Engine?  Next, just try to add it again.

I did add the engine, it placed it in ID 6. When I went to EDIT ID, and move it to 62, 62 is gone. I did not try Recover Engine - will have to try that now.

RAY

Hi Ray,

The recover engine won't do you any good in this case.  The "recover engine" feature brings back an engine that has stored an ID number outside the 0-99 range.  Since your engine is in the remote and running at ID #6 there's nothing wrong with the engine.

Address 62 can be recovered.  In fact, I recovered an engine ID for Barry not that long ago.  Make a copy of your remote data file and send it to me at the e-mail address in my profile.  I have to do a little manual editing of the file. 

OK, how and what do I need to do to make a copy of my "remote data file"? 

RAY

PS I have only 12 engine and doing a reset and then reloading all 12 engines using that STUPID thumb wheel and then having to scroll thought all the alpha/numeric characters is a real pain in the you know what. Why didn't MTH make it so that one can plug the remote into ones computer, and use the key board to load the information. Too simple, I guess.

Hi Ray,

You need to download the DCS Loader software from www.protosounds2.com and install it on your PC.  You'll need this to update your remote and TIU firmware as well.

Float over the icons in the software and find the one with the pop-up message "Transfer the Remote Data to the PC."  Click on it and PRECISELY follow the instructions step by step.

Dave,

Did you mean to go to PROTOSOUND2, because when I go to PROTOSOUNS2, with the "S", I do not get it.

RAY

Dave,

At the PROTOSOUND2 web site, there are several DCS loader programs;

• New DCS Loader Released - September 3, 2008
• DCS Loader Program Installation/Operating Instructions - March 26, 2013
• DCS Loader 64-Bit Version w/o .NET
• DCS Loader 32-Bit Version
• DCS Version 4.30

I'm not a computer expert, so I don't know what I should be looking for.

Thanks,

RAY

Hi Ray,

Sorry about the typo.  Yes, it's protosounds2.com

First, you must be running Windows (not Mac) to use the software.  Assuming you are, you need to see if you're using a 32 bit or 64 bit version of the operating system.  To find that, open the "Control Panel" and double click on "System."  If you have window 7 or Vista (and I think Win8) you'll see it listed there whether your system is 32 or 64 bit.  Download the DCS Loader program for your version.

Gregg, what were doing is getting around the problem of having to reset and re-install all the engines.  It is possible to get rid of a "ghost" in the remote by editing the remote data file.  Unfortunately, is requires a map of the file and the ability to read HEX.  I'm not at liberty to share the map of the remote data file, but I can correct the problem if Ray can send me his data file.

Thx Dave. A little over my head. I don't even know what HEX means.

That would be great Barry.  The Legacy LSU allows you to edit entries, I had a very similar issue with my Legacy remote for ID #2.  No matter how I tried, I couldn't clear it, I used the LSU and Shazam, I had it cleared.  That would be a great addition for the DCS loader.

Ray,

Any chance that that can be modified?

Not any time soon, unless it eventually winds up in the DCS smart device app.

And it will.  That's how we are implementing "Custom Names".  The engine name appears in the settings tab for each engine.  Tap and hold on the name (like any other editable feature in iOS or Android) and it opens a full QWERTY keyboard with upper and lower case letters allowing you to edit the engine's name without any scrolling.  Switch, Route, Accessory, Scene, and Track names will all work the same way.

Hi Glenn,

I didn't receive a message from you.  Go ahead and send your file to hikelogauge@gmail.com and we should be able to clear up the problem.  Please include in the e-mail what engine ID number is currently unavailable.

I was under the impression that the data in the remote could be downloaded into the computer and then the remote could be reset and the data reloaded. It was not clear to me if all the data like switches and accessories would be recovered. I'm looking for clarification here. I lost a number in the past and had to reload a lot of stuff as a result of having one of three remotes reset. I have one remote presently that is missing a number and I'm living with it for fear of having to reload a lot of data again. Having had a terrible experience years ago with trying to use the loader programs, I've decided to leave that to others with experience and proper cables, etc. I gather that both the TIU's and remotes need upgrading for the latest fixes. What are the chances of losing data with that?

Hi GHD,

The problem is when you download the remote's data to the PC the "ghost" will go with it.  Reseting the remote wipes out the "ghost," but when you restore the data from the back-up file on the PC the "ghost" gets reloaded along with everything else.

All data stored in the remote, including engines, lash-ups, tracks, switches, accessories, routes, scenes, as well as remote settings such as messages on/off, are incorporated in the remote data file.

The chances of corrupting a remote's data files during a firmware update are virtually zero.  The firmware and remote data are stored in different parts of the remote's memory.  However, it never hurts to backup the remote's data before up dating the firmware. 

Thanks Dave. Maybe that explains why the same # in the same remote ( 1 of 3) went missing again. George

Hi Dave,

I wanted to publicly thank you for helping me and the quick turnaround on the modification to my remote file.  I loaded what you sent back into my remote without any difficulties this evening using the DCS loader programs and address 22 is now present and in use again as well as everything else that was there. This was much quicker and far less frustrating than trying to reload all of my locomotives and recreating lash-up names.  So much good help is available on this forum for things I would otherwise have no idea how to do or fix.

Thanks again!

Glenn

I usually try to shake the remote upside down and see if the engine falls out, then i check the couch

Dumb question Dave.  Are you just finding the offset of the offending data in the hex dump and zeroing it out?

Glad I could help Glenn.

John, in short no.  I'm not at liberty to share exactly what I am doing.

GHD;

The process you mentioned about saving the data and then reloading it will work IF and only IF you save the data BEFORE the problem occurs.

Then you have an uncorrupted download that can fix your remote.

I periodically back up my remote data for this reason.

How many of us never back up the Computer ??? Same sort of problem happens there.

Thanks Russsell. What I learned here, for me anyway, is that I use 3 remotes and I keep them identical. One has a missing number currently. So if I decide to have them reset, I have to make sure one of the good ones is loaded into the PC for reloading the data. This looks to me like another bug for the fix it list. It also looks like Dave might be the only one who knows how to fix it. Just a minor inconvenience for a great system. 

 One has a missing number currently.

All that you have to do is load one of the good ones into a clone file on the PC and then restore that one into the one that's missing the slot. That will correct your problem.

This may actually be corrected in DCS 4.30 or possibly even in 4.20. During the 4.30 beta testing, which was extensive, I never lost a DCS ID#. The last time I lost a DCS ID#, other than 99 which I lost back in DCS 3.1, was in DCS 4.10.

Regardless, I've suggested to MTH that the ability to correct this problem be built-into a future Loader Program release.

Thanks Barry. As luck would have it, I lost a second number last night after posting my comment. I believe it happens during an engine shutdown. I don't know if there is any connection, but both times it happened, the engines involved had BCR's in them. I have Rev L TIU's and 4.1 in my remotes. Looks like 4.3 is coming my way soon.