I have the new DCS Explorer that I got with a starter set. I runs all my old P2/P3 engines with no problems--except this one.
I put a P3 engine on the DCS Explorer track and added it. Ran fine.
Then I tried to run it on another loop using DCS Remote Commander. No go. I even tried the SND/DIR "-" factory reset--deader than dead.
I'm figuring that the DCS Explorer re-addresses the engines. I can't remember what address the DCS Remote engines were, but if it's "0" it doesn't look like that can be reset in Explorer.
If this is true, it's a real liability. Most of us who are not full DCS will want the flexibility of both systems.
If my guess on what's going on is correct, I'm urging MTH to change the code in the app to allow DCS Explorer users to change the address of engines. Right now that feature is a lock out.