I've added some extensions to my RTC program for conventional operation and for LashUps. Look on my web page for three new videos:
http://www.silogic.com/trains/RTC_Running.html
In the emails that I received about the program, several people asked about conventional operation. I hadn't considered that at first but it was not too hard to add.
What was a little harder was LashUps. As I dug into this, I saw that 90% of the intelligence about LashUps was in the TIU. When my program sends commands to the TIU, it only has to send the command and the engines in the LashUp. The TIU figures out which commands go to which engine and which commands have to get modified before they are sent (like for reverse running engines). I was impressed with what the TIU does.
Most of the work in the PC is managing the list of engines in the LashUp.
If your screen is big enough, the RTC program can display operation windows for 99 engines, two variable channels, and 20 LashUps at the same time.
I received an email from a person in the JMRI group. They were interested in incorporating the protocol in their train control program.
I'm preparing the RTC program for beta testing and I've written up a description of the protocol. So far, I've sent the program and protocol description to one person.
My intention is to release both pieces under the Free Software Foundation GPLv3.
To say it again, I figured this out just by looking at the RS-232 stream over the tether cable. No code disassembly, no logic analyzers, no opening up of Remotes or TIU's.
Mark
