Barry Broskowitz posted:For the past few hours, Marty Fitzhenry and I have worked the "can't run Legacy when using the DCS App Premium edition" issue. We conducted tests using the following hardware scenarios:
- Rev. L TIU with WIU connected via USB port
- Rev. L TIU with WIU connected via Serial port with serial Y cable
- Rev. I TIU with WIU connected via Serial port with serial Y cable.
Both TIUs were running DCS 6.0 and the WIU was at firmware 1.1. In all cases, a Lionel Legacy command base was also attached via the TIU's serial port.
In all 3 scenarios, a variety of Legacy and TMCC engines were added to the DCS App. For all of the engines added, the following was determined:
- All Legacy engines started up and ran successfully when set as "Legacy" mode
- All Legacy engines started up and ran successfully when set as "TMCC" mode
- All TMCC engines started up and ran successfully when set as "TMCC" mode
- All TMCC engines failed to start up and could not be operated at all when set as "Legacy" mode.
The conclusion is that the DCS App can operate Legacy engines in either Legacy mode or TMCC mode, and TMCC engines in TMCC mode.
This makes sense, since Legacy engines can understand both Legacy commands, from a Legacy Base or TMCC commands from a TMCC base, while TMCC engines can only understand TMCC commands from a TMCC base. The engine's setting as either Legacy or TMCC determines which type of commands are sent to the command base.
The above is completely consistent with the results obtained during beta testing of TMCC and Legacy engines.
It's also completely consistent with the DCS Remote, which controls both TMCC engines and Legacy engines as TMCC engines, using only TMCC commands.
Glad to read that it can be done. Couple of questions, what type of smart device were you running the app on and a new thought is were you connecting the smart device through the WIU WiFI direct or was the WIU communicating through your homes router and then your is connected to your homes network through the same router?
George
