Hi all…
I just picked up the Digitrax Super Chief DCC set and I very impressed with the set… Has anybody connected their PC to the Command/Booster using the serial cable interface? If so have you tried to read the commands using hyperterminal or another program… I would love to be able to create my own program to put Loconet command on the interface to control the trains via my pc…
Thanks
Ryan
Ryan,
What you want to do is to download a program from JMRI called Decoder Pro. That should do the trick for you. A number of the members here on the forum use and like it very much. It’s great for storing and recording CV settings for your individual locomotives. You can also use it to program and run a signal system on your layout. And…(here’s the best part)…it’s FREE!
Tom
Ryan,
What you need to get is the Locobuffer USB from RR Circuits http://www.rr-cirkits.com/ it is a far superior PC interface for the loconet than the Digitrax PC interface.
Tom is spot on with the suggestion of the JMRI suite. Not only does it have decoder programming capability but it offers many Loconet specific tools including traffic monitors where you can see all the commands broadcast on the loconet. There is also a scripting language to allow you to create your own automation sequences. There is a throttle function where you can create a virtual PC throttle for a specific loco. The best part is that it is free! Tom gave you the link already.
Simon,
What makes the Locobuffer better than the Digitrax cable? The locobuffer seems to be about $40 more ($70 total) vs the Digitrax ($30).
I am just getting ready to buy a digitrax system and want to use the computer interface for signalling, etc.
Thanks
Chuck
I use the Locobuffer USB and Decoder Pro with Super Chief Radio system. When I was researching this I heard a lot of people complaining about issues with the Digitrax buffer. Also an additional adapter is needed with the Digitrax buffer to use USB. It is designed for a serial interface.
Chuck,
The Digitrax MS100 is merely a level shifter that converts the computer’s serial port voltages, to voltages that are compatable with LocoNet. There are no timing or other considerations, so (for example) the computer could “speak” at the wrong time. The result would be a LocoNet collision, and some LocoNet traffic might be missed or dropped as a result. It also operates at the LocoNet baud rate, which is not a normal serial port baud rate. This difference has been known to cause communication problems.
The LocoBuffer products, on the other hand, are just that: Buffers. They can “hold” traffic coming from either side until the other side is ready for it. In the example above, if the computer “spoke” at the wrong time, the LocoBuffer would hold that traffic until the LocoNet was able to “listen”. Since they are “smart” devices they also have the ability to talk to each end (computer and LocoNet) at the correct baud rate.
The LocoBuffers are also more versatile connection-wise. Depending on the specific model, they work reliably with either USB or serial ports, or with a USB to serial adapter. But for some folks, the MS100 just won’t work with a serial port that otherwise functions just fine.
You said the magic word - signalling. Do NOT waste money on an MS100, get the Locobuffer. As the name implies, it is buffered - meaning th eloconet packets are buffered int he Locobuffer’s memory until the PC reads them. The MS100 relies on the computer seeign eacha nd every packet ‘live’. If something delays the program that is reading the MS100, the packet will be missed. And it does happen. I actually saw it happen right in the Digitrax booth at the National Train Show this past summer. They have a simple straight line track set up with an N scale loco goign back and forth, it has a BDL168 block detector and an SE8C signal decoder to drive signals for a demo. A PC is attached via an MS100 running a simple script in I think RR & Company - whent he script sees the loco enter the last block at one end, it pauses the loco, then reverse it. Likewise for the end block at the other end. WHile I was standing there, the loco went to one end and then just stayed there pushing against the bumper block. Why? Because the packet from the BDL168 that said “block 8 is now occupied” was missed by the PC running the script.
If you have a little electronic experience you can buy a PC board from Hans Deloof and parts from Mouser or Digikey and build your own Locobuffer - that’s what I did. Cost me about $40 or so. This makes a serial
Hey Guys…
What Thanks for the info on that other cable, good thing I haven’t ordered the other one yet… What I am looking to do is create a virtual DT 400 on my PC using LABVIEW. For those who know what LABVIEW is it is program to control equipment in an engineering setting… I am looking to be able to create a simpler interface so my kids and nephews/nieces can run the trains since I have the Digitrax chief System which is hard for 7-10 years to work with… By working with Labview I should be able to write the commands to the Loconet but I need to know the bit patterns or Interface Specification for the Loconet commands… Does any body know the format for them that go to the command station??
Thanks…
On the Digitrax web site you can download the Loconet Personal Edition PDF, this describes the format for Loconet commands and what they do.
–Randy
Or, you can just use JMRI. It’s already got customizable software throttles, and it’s free:
http://jmri.sourceforge.net/tools/throttle/ThrottleMain.html
Steve