Big mistake

Gotta ask Barry or GunRunner John.

If the remote cannot bring up an inactive engine, the odds are that it's due to some reason other than the aborted READ command.

If you have another remote, does it find the inactive engines? Remember, they need to be on powered tracks in order to be found and accessed.

Regardless, recover the remote's contents by resetting the remote and restoring it using a previously-saved remote backup file. That should put you back where you were before the READ incident.

For future reference, turning off the layout could only make things worse, not better, since doing so would make all engines lose power and go into the Inactive Engine List. Turning off the remote before the READ completed  (the only way would be to remove a battery) could definitely case problems. The best course of action would have been to just let the READ finish.

Barry thanks. On another post you said it would only be a matter of time until I put all my devices on the same rev level. Well today's the day. It's all going to my tech for 6.0! Your book for the wifi installation is next on my list. Fwiw my other remotes were fine. Due to the early problem in the system years ago, I got in the habit of loading all my engines using the #1 tiu. This kind of had the same feeling as that old bug. Anyway, it's time to take the next step forward to 6.0. I bought the banana plugs and relocated the tiu's getting ready for this. Thanks for all your advice. George 

Question---When the remote is backed up on the computer, can that file be downloaded on a thumb drive for future use?

I would think so! It is just a file. Maybe check the size of the remote file and make sure you have the available space on the TD.

 I have been using the read for a good long time again. That old bug hasn't bit me in several versions.

I tried to run a consist outside the other day, and 2 engines were run on my basement TIU. They wouldn't come up until I used the "read" w/ 6.0.

No problems and it works well now.

GHD, very definitely.  On my laptop and on a thumb drive I have a long list of backups, with dates in the file names.  We have an old, very slow netbook that is small and is able to handle DCS jobs, so the thumb drive is a handy way to transfer files.  When I was upodating TIUs & remotes at York, I had some "clients" who asked me to save their remote data and then email it to them; the thumb drive was the vehicle I used to transfer that data from the netbook to my internet-connected computer at home.

Anyone who does not back up a remote is being very unwise.  When something goes sour & the remote needs to be reset, having it backed up makes for a simple task.

Thanks RJR. With all the early changes in computer hardware and software I never took interest in downloading software. Having the right computer with the right cables didn't interest me. It seems like things have stabilized a bit so I may take interest in it. Is the program to do the remote backup a stand alone program or part of an MTH suite of programs? I guess it's time to get out Barry's book.

Part of the latest Loader program, which is user friendly. Select a function, and on screen instructions for it pop up.

We agree on the necessities for having remote backup. How is this going to work when we don't have remotes?

Is there any compatibility with Macs yet for backing up remotes?

Roger

Is there any compatibility with Macs yet for backing up remotes?

What do you mean "yet"? It's always been possible to use an Intel-based Mac to do everything the Loader Program does, as long as it's configured properly.

The DCS WiFi Companion 1st Edition has a section that details exactly how to use the Loader Program on a Mac.

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