Premium wifi app question

What am I doing wrong?

Don't refresh the app unless you have to do so.

Refresh acts like a DCS Remote READ command. It sorts DCS engines into the Active and Inactive engine lists depending upon whether or not they're sitting on powered tracks. Also, just like the DCS Remote's READ command, all TMCC, Legacy and DCS lashups got to t he Inactive list.

The solution is to do the following from the Engine Roster Screen:

• Tap Edit
• Use the slider to the right of the TMCC or Legacy engine to move that engine up into the Active List.
• Tap Done.
• Tap the engine to select it.
• Go back to the Engine Control Screen and operate the engine.

This is all in The DCS WiFi Companion, coming soon!  

Thanks Barry,

The Legacy engine's number is 12, but the DCS app puts it in

address 4 because that's the next available opening.

I put the engine in program mode and set it to address

12 and saved it in the app and it worked once. As soon as I

went back to the engine list it was back in address 4.

My TMCC diesel works fine but not the Legacy one.

I have a bunch of Legacy and TMCC engines yet to add

and don't want this problem to repeat it self.

I hope you can advise me.

Tom

'

Tom,

It doesn't sound like there's any real issue. The DCS App is acting as intended.

Once a TMCC or Legacy engine is added to the DCS App, it's order in the engine list cannot be changed. You can change its TMCCC/Legacy ID# but not its DCS ID#, which is only a "placeholder" as far as DCS is concerned.

This is exactly the same way that DCS works, and has always worked, when using the DCS Remote.

In order to get your TMCC/Legacy engines into the DCS App where you want them to be, you can use the same method that's used to do so in the remote. Make sure, by adding nonexistent TMCC engines, that the next available slot is the one that you want the engine to go into. When you've finished adding your "real" engines, you can delete the nonexistent engines.

Still having problems with running Legacy engines. My TMCC engines are working fine in the App.

I deleted the Legacy engine and tried to add it again using the same process as my TMCC engines but selecting Legacy instead of TMCC, and put in the Legacy's engine address then pressed save. The engine comes up in the active list but will not start or run at all. I also tried another Legacy engine but it didn't work either.

Do you have a Legacy command base or a TMCC command base? If you don't have a Legacy command base you can't use Legacy commands.

I have a Legacy base installed. I found if I change the Legacy engines to TMCC engines they work!

Is there a fix coming soon for this problem?

I see other folks are having the same issue.

Thanks

Please see my last post and let me know if this issue has a solution yet.

Thank

Is there a fix coming soon for this problem?

Using iOS, AFAIK there is no issue. It works fine for me.