TMCC Command from MS DOS Prompt

I remember seeing a TMCC Windows Application that would run using the serial port. I'll see if I can track it down.

I found the author and sent him an E-mail off-list. I cc'd you.

Please keep us in the loop on this.

George

Jay,

Having done this myself over 20 years ago I can easily see why it's important, but its been so long that I can't remember where I stored the floppy disks that have my program on them.  Even if I did there's probably a 50/50 chance that they're unreadable after all these years.

At the risk of reinventing the wheel this thread contains a wealth of info on the general means for sending commands to TMCC, and Legacy, units (ignore the fact that the title focuses on the word "Arduino"):

https://ogrforum.com/...57#77875232662193957

You'll note within it that there are a number of different software programs and utilities referenced.  One of these may already be available from a forum member, or other source, to do what you want.  If not, the detail found in the thread should point you in the correct direction to write your own.

Keep us up to date on what you find.

Mike

Yeah Mike, I read that with great interest yesterday. But there were a couple references to links to code someone had uploaded on drop box, but I couldn’t find. I thought maybe because the thread was 3 years old.  However there were some code snippets posted that I’m going to have a look at today.

thanks

Jay, I can help you if you want code samples, but if all you want to do is test the electronics of a TMCC engine the following might be easier than figuring out how to program your serial port:

1) Construct a few 3-byte TMCC commands (0xFE 0xXX 0xXX) using the Lionel command reference, either by hand or by a program you write in java. The basic code to do that is this:

byte 2 = deviceType | (deviceID >> 1); // Byte 2 is combination of type field and first 7 bit of TMCC address
byte 3  = (deviceID << 7) | (commandField << 5) | dataField; // Byte 3 is last bit of TMCC address, command field (2 bits), plus data field

2) Using a serial monitor program that can send hex data out the serial port, just type in those hex sequences and send to the command base.

Even easier is to either take the engine and a chunk of track to a TMCC system or bring the TMCC system to the locomotive.

Sorry I wasted everyone's time and my own. Thought this would be REALLY easy, but in the time I've spent trying to figure it out, I could have driven 90 minutes to the nearest hobby shop and done as GRJ suggested. Would have been a lot more fun, too,

I just wanted to be able to type something like

>echo jay > com3

except instead of sending the letters jay, send three letters (characters) corresponding to the binary information that needs to be sent to the Command Base (something like ■☺∟). No bueno.

I know the serial port is connected to the Command Base, because when I use a serial monitor app, I see a string of bits appear when I plug in the Command Base. But when I try to send 3 bytes to the Command Base, I get nothing. No red light flicker on Command Base, no indication anywhere that any communication is happening.

Not trying to rule the world here, just trying to blow the **** horn! Don't need a Java program (or C++ or whatever) with several classes and hundreds of lines of code.

Maybe the Command Base is as bad off as the CAB1 was, but I just can't see it. When I give power to the track with no Command Base, the loco sounds fine. When I give power to the track with the Command Base turned on, I get no sound (but I do have lights).

I've got a ton of papers to grade and a two tests to prepare for Monday, so I was really hoping this would be fun and quick and simple. No, no and no.

There is a ton of great info in that Arduino thread, just nothing that helped me.

Thanks for all the input.

Hello guys. Finally got ahold of a good little app called serialsend. Was able to send a command to set the loco to engine 2. Then was able to send signals for horn (whistle in this case), bell, and change directions. And this is all done from the command prompt, which is what I wanted to begin with, although not quite as simple as I had hoped for (the serialsend has far more capability than I actually need for this little test).

However, I can't get the loco to move. I've tried setting the absolute speed to 1, 3, 5, 10, 20 and even though the red light on the Command Base flashes, I get no response out of the loco. I don't think the drive train is locked up, because I don't even hear the motor trying. So suggestions there would be welcome. I'll try messing with relative speed rather than absolute speed later tonight to see if that makes a difference. There is a switch on the bottom of the loco to turn Cruise Control on and off; does this matter? (sorry, long time since I've had a TMCC/Railsounds loco)

The smoke unit works, but I haven't sent codes yet to turn it on and off (just flipped the switch under the loco).

Appreciate all the input. Will post a video later if I can get it to move.

Hi Jay - sorry for not responding to you earlier; I was preparing for my own class today!

I have a vague recollection that not all 3rd-party TMCC implementations respond to absolute commands.  The CAB-1 only sent relative commands, not absolute ones, so most people wouldn't notice until Legacy came along and enabled the CAB-2 to send out TMCC absolute speed commands.

If you're not wedded to the command prompt I like CoolTerm as a serial monitor; easy to use in hex or ascii mode.

I was thinking that as I was typing. I'm so used to the ESU controllers, which have a 0 mph stop on the dial. I grabbed the Cab1 and realized that the wheel just turns freely (no max or min), thus I figured all commands would have to be relative rather than absolute. Will give that a try after my engineers ace their quiz, LOL.

@lionel1946 - I strongly recommend Java for the threading and the availability of serial modules.  I've been concerting Mark DiVecchio's DCS work (which is in MS C++) to Java.

Anthony

I think going from a canned program to send simple commands out the serial port to coding up modules in Java is a large leap Anthony!  Most of the folks here aren't programmers.

@gunrunnerjohn - I was going by his original comment,

"I’m very well versed in JavaScript and VBA and Java, but no idea how to write in C (although I’m sure I’d pick it up quickly). Like I said, not trying for full functionality here."

So I thought I'd make a plug for Java.

A

In that case, I retract my statement, I was talking in general terms for most folks reading this thread.  I'm the opposite, I'm well versed in C, but not so much in Java.

Here's a short video showing the operation. Very pleased that the RailSounds is still working great, and all the functionality I wanted tested fine. My audio is very low, but the loco audio is fine.

Before I put everything away, I tried to see if the TMCC signal and DCC signal (from my ESU ECOS system) would peacefully coexist... they do not. The whistle on the loco just blew non-stop!

So either I wire every district of the layout to toggle between TMCC and DCC, or I rip out the circuitry I just tested and replace with a DCC controller. Nice thing is, all the wiring is already done, including the tether between loco and tender. So if I go that route, it should go relatively smoothly.

@gunrunnerjohn - No worries, mate.  I would like to say Java is my language of choice but my current work-work uses PHP/JS.  I use C (Keil) for the 8051's.

After seeing @lionel1946 's video, I'm thinking I should focus more of my attention on TMCC/Legacy instead of this half baked crap that is DCS.  (My other thought is to design my own Digital Control system with focus on engine groups.)

A

@A. Wells posted:

(My other thought is to design my own Digital Control system with focus on engine groups.)

Kind of a limited market for that I would think.

@gunrunnerjohn - Market?  I just want to prove to myself that I can do it.  I even got back out of the bed last night to dig out one of my evaluation kits so that I could eye it longingly.  Then I started to cry...I loathe I2C. A

I wish I could find time to do some "prove to myself that I can do it" projects.

I would like to play(?) with the two routines mentioned in a couple of the preceeding post. When I went to download the apps all sorts of "Bells and Whistles" went off from my internet protection routines. Has anyone that downloaded these routines experienced any adverse affects due to malicious software included with the downloaded software?

Although I haven't had a chance to look at the source code yet, I'm pretty comfortable with the SerialSend program that I used. Comes from a very helpful professor across the pond, University of Dublin. No issues at all.

@lionel1946 - So, what are you going to try next in this saga?

That's it for now!

When I bought the TMCC Cab1 and Command Base on the cheap, I really just wanted to see if all the electronics were still in good shape. That was side-tracked when I saw the corrosion in the Cab1. I really didn't want to buy another Cab1, so I was quickly trying to find a way to test the loco using only the Command Base before having to return it to the seller.

Before I put all of the electronics away, I was able to confirm that TMCC and DCC will not peacefully co-exist. So the TMCC electronics are coming out and getting replaced with and ESU Loksound.

The only other 2-rail TMCC locos that were also done around that time were the Weaver VO-1000, the Atlas FM Erie-Built, and Atlas GP-60. Not much there to build a fleet with.

I didn't mention on this thread, but very interesting story about this Weaver 2-rail TMCC locomotive that I was testing on. I actually owned this loco back around 2005. Sold it when I realized that 2-rail TMCC was not going anywhere. I've been watching auction sites for years trying to reacquire in DC, because I really liked the little loco. Finally found this at an auction last year and had the winning bid. When I got the item home and started removing old mailing labels from the box, I saw MY NAME on one of the labels. So this is actually the same exact loco I sold in 2005-ish.