This looks good. Now if the program can control the rest of the layout switches/accessories, additional TIU and AIUs, control legacy/TMCC engines at the same time, this could be beneficial for large and somewhat complicated layouts.
Connecting all the systems, and running everything from one interface is not all that complex, once one knows how each system talks. TMCC put this information right in the user manual from day one. Legacy they released about a year ago. as far as I can tell, Mark here now has all the information needed for control of DCS, so it is surely possible, if he's willing to share. The problem, from what little information I can find, is that MTH will stomp, hard, on anyone that tries to market a product that talks to their system.
Using a $9.99 arduino clone I was able to make a cab1/TMCC issue psudo-dcs commands. Don't own a DCS system, so no real test, but I assumed that Mike, referenced in the original post had done good work, and that the system would read copied packets.
