Engine ID from a pair engines get swapped when I do a read function. For instance, a Hudson is now a T-1. And T-1 is now Hudson. One of the engines (new T-1) is on the track, the other is not. Only way to fix it is to delete both engines and add them again.
It Just started after returning from York with both TIU and Handheld updated from 5.0 to 6.0 and the new engine . Affecting both handheld and Wifi. Could it be something with the new engine? This is strange.
Replies sorted oldest to newest
Engine IDs stick with the engine unless Edited to another ID. Factory reset, or it's ID is taken with another engine when adding...
Having said that I've seen strange things happen when adding a number of engine without using a programming track... Engines borrow the name of a already added engine... Things along those lines.
Are you saying after a delete and re-add things are still messed up? I haven't upgraded to version 6 yet and don't have WiFI.
The topic is about engine address number changes not ID.
Address swapping happened once so far on each device. I will have to do more research.
I've had this happen once or twice before, but on a rare occasion. This time it happened back to back on same engine.
Huh...Are you talking about the name of the engine or it's ID number in the remote. The Spot in the remote is the engine's ID number.
As I mentioned above A programming track will eliminate this type of problem .
I was a little confused with nomenclature. The DCS companion calls it engine ID number. But when I edit the engine in the remote, it calls it "address". I think they are the same. It is used for communication between the engine and remote device.
I just restored the IDs by deleting and rentering the engine in both the remote and my iPhone and everything is ok so far. But I don't know what just happened or what could be the cause.
Yep Address and ID are the same. Glad you got it straighten out... I'm still not sure about upgrading to version 6.. 5 is working well.. No wifi here (yet)
Gregg, I've been using 6 for some time with no problems that I've noticed.
GREEG I would wait !!! I knew better than to get initial release, wish I would have never done this. Never did get the premium app to work and the standard app is worthless. It now sits unplugged on its own little shelf doing nothing!!
Clem
Clem, you must have a local problem. I've been using the $4.99 app, with 2 WIUs, since they were released, with no prohibitive issues. I've been using 6.0 and the premium app for about 2 months. All with no issues such as you have.
Access to this requires an OGR Forum Supporting Membership
