DCS WIFi APP will not recognize a particular engine

Some folks have reported once past 5 engines, the app would not allow them to add more.  I haven't seen any update lately.  I'd be curious to know as I am helping our local store, Imperial Trains, with the MTH WiFi day on the 23rd.  If this is a bug it would be nice to know.

I had 7 on mine with one issue due to duplicate addresses on two locos. Next weekend when I install the 3 WIU's on my layout and get a bunch of MTH locos I'll see if I have that issue. Robert, make sure your loco does not have a duplicate address as another loco, the app will not allow you to add a loco with a duplicate address and it doesnt change addresses on the loco when adding to the app. Changing the address is something you will have to do with the remote

Addresses can be changed in the App...mine shows 98 available.

I had 2 locos with duplicate address, when the app scanned the TIU for active locos it did not add the 2 with duplicate addresses, when I scanned the TIU a second time it added one of the duplicate locos, im not sure but I think it just picked the first one it saw. For me I knew which ones were duplicates because when I started up one the other started as well. I still needed the remote to add the engine and change the address but I suppose I could have removed one of the duplicates and then changed the address of the other one then re-added the loco.

Barry what is the bug, and does it apply to specific parameters, or a random issue?  IE, why one engine adds and another won't?  G

As always everyone...thank you for the insights! Your help in invaluable...and  I am grateful I can turn to this forum with questions!

George,

The bug is that if the DCS App finds an engine which has the same DCS ID# (actually, internal engine ID# which is one greater than its DCS ID#), it will not add it to the remote, thinking that the engine is already in the app's engine list as active, inactive, or ready to be added. This is because the app only compares engines based on engine ID#, not on other criteria as does the DCS Remote.

When the DCS Remote encounters an engine with the same internal engine ID# as one already in the remote, it conducts a second matching process and, if it really is the same engine, it states "Engine in Remote" and then displays the engine. However, if it's a different engine with the same ID#, it will add the engine to the lowest available DCS ID# and change the ID# in the engine.

That's how the app should act, as well. When I reported the bug to MTH, I was told that it would be in the enxt release of the app.

Barry Broskowitz posted:

Addresses can be changed in the App...mine shows 98 available.

Not in this case.

Robert cannot change the engine's ID# because a bug in the app won't let it be added. This bug will be corrected in the next release of the app.

Can't you change the engine address that the App already found then add the second engine?

I am having a somewhat similar issue. I am trying to add an engine (CAT F40PH - 30-4047-1) that has it's own unique id number from all others.  During the add engine process on in the app, the engine ID number shows up but it displays no description of the engine. When I press the engine ID number, it disappears and the purple TIU light begins to flash on the WIU. The app also loses connection to the TIU and I have to reboot the WIU to reestablish communication. 

I have tried changing the engine ID to a much higher number with the DCS remote and had the same result.

Any ideas?
THANKS!!

I think I resolved my own issue.  I reset the engine back to factory defaults and added it again to the DCS remote.  I then used the DCS remote to change address to the same address the engine had before.  I then added the engine to the app using a test track and worked flawlessly. I then moved it to the layout and now it seems to be working normally. 

Strange that whatever the problem was with this engine that it was able to crash the WIU completely. A little testing before I resolved my issue revealed that the WIU was completely unresponsive. It was no longer active on my home network and the device wouldn't respond to a network PING request.