I have an old computer I'm hoping to use with Decoder Pro. Its a Dell with Windows ME and has about 120 MB of RAM. I've downloaded Decoder Pro and it seems to work fine. I have a Digitrax DS100 that I had planned to use for the connection to my command station (Empire Builder). In order to connect the DS100 to my computer, I needed an adapter but now find that the plug from the monitor is too close to the port I need to use for the DS100 plug. I'm hoping a trip to the local computer store tomorrow will result in a solution to this problem. This computer will be used only for Decoder Pro and has nothing else running on it.
Reading the instructions at the Decoder Pro site relative to the DS100 tells me that I may have a problem with the baud rate and the DS100 won't work.
I would also like to know if the DS100 will work with Windows ME? If someone knows it won't, will any of the other options from Digitrax work? (Loco Buffers or PR3)
john
Soo 61245 I have an old computer I'm hoping to use with Decoder Pro. Its a Dell with Windows ME and has about 120 MB of RAM. I've downloaded Decoder Pro and it seems to work fine. I have a Digitrax DS100 that I had planned to use for the connection to my command station (Empire Builder). In order to connect the DS100 to my computer, I needed an adapter but now find that the plug from the monitor is too close to the port I need to use for the DS100 plug. I'm hoping a trip to the local computer store tomorrow will result in a solution to this problem. This computer will be used only for Decoder Pro and has nothing else running on it. Reading the instructions at the Decoder Pro site relative to the DS100 tells me that I may have a problem with the baud rate and the DS100 won't work. I would also like to know if the DS100 will work with Windows ME? If someone knows it won't, will any of the other options from Digitrax work? (Loco Buffers or PR3) john
I think you mean an MS100, not a DS100. Anyway, if so, then it might work for you but maybe not well. The more popular options are the Loco Buffer II and PR3s. I have both but they do require a USB port. If you only have a serial port, then you'll need to use the MS100. I'd suggest you try the MS100 and see how well it works. If you don't have an issue with dropped bits, then it will be Ok, If you have a USB port and end up needing a new interface, then I highly recommend the PR3.
Engineer Jeff NS Nut Visit my layout at: http://www.thebinks.com/trains/
John,
Although it is now retired in favor of a PR3, I used my MS100 for years with various combinations of laptop and desktop hardware running W95, W98, WinME, and XP. And most of those desktops were home-built "frankencomputers" assembled from old, cast-off hardware. So it wasn't like I was working with state of the art, tried and tested, foolproof machines.
But not once did I ever run into the ground loop or "dropped data" issues that some folks seem to say are inevitable with the MS100. I'm not saying those issues don't exist, but my own experience seems to indicate they're less prevalent than some would have you believe.
So if you already have the MS100, I'd say to go for it as long as the adapter you need isn't too expensive. Just don't let that old WinME machine nickel and dime you to death with adapters, and maybe more memory, and looking for drivers, etc. If you can get your hands on a machine running XP (they're cheap - Here's an example) you may be better off in the long run.
Steve
I guess it depends on what you are using the MS100 for. I never bothered with one, but I did see first hand the dropped data issue. At the Digitrax booth at the National Train SHow a couple years ago, they had a demo layout set up with a short length of N scale track with an RDC runnign on it. The track was divided into multiple blocks detected by a BDL168 and it had signals controlled by an SEC8. It was all automated with a PC running RR&Co connected to the Loconet via MS100 (this is before the PR3 ever came out). On one trip, the RDC just ran into the bumper and kept trying to push against it. The computer still showed the previous block occupied, not the end one, so it didn;t know to pause the 'train' and reverse direction. All because one Loconet packet was dropped byt he MS100. ANd this was a very low traffic system compared to implementing detection and signalling on eve a modest spare bedroom sized layout.
If the primary use of the MS100 is to generate program commands to program decoders, or other activity wher the majority of traffic is being sent from the computer, you should never see packet loss, but if you are relying on input to the computer from block detectors and so forth, it's more than an even bet that sometimes data will be lost. The more Loconet traffic there is (more detectors, more throttles, etc) the likelier it is. And the more stuff running on the computer, the more likely it is to lose data. This is where a device like the Locobuffer wins hands down, if the computer is momentarilty 'busy' it doesn't matter, the Locobuffer 'sees' all the packets and buffer it until the computer is ready to accept it. Witht he MS100, the computer must be ready to respond the instant a packet starts coming in on the Loconet, there is no ability to buffer the data untilt he computer is truly ready. Under DOS this probably was fine because witht he exception of certain add-on software, DOS could only do one thing at a time - so it could sit there just waiting for the Loconet data. Under Windows though, the computer can switch away from the Loconet-monitoring application at any time, and it takes some finite amount of time to switch back no matter how fast your computer is.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Wanted to report that I have been able to complete the connection with my MS100 after picking up an extra cable for the monitor. This allowed me to plug in the MS100 to the COM port.
From there, I set preferences and so far it works without any error codes appearing. I've changed some CV's and light settings on a few engines already.
Randy, thanks for your advice. I will probably look at purchasing the PR3 when I move into the areas you mentioned would be problematic with the MS100.
I may be back here if I have any troubles adjusting CV's for the consisting I want to do.
Thanks to all for responding.
I have a Digitrax DCS100 Command Station and DB150 which can be used as a command station or a booster. For years I used a MS100 to interface with my Digitrax system via a 550MHZ E-Machine (Windows 98SE) using a MS100. The old E-machine finally died and I moved my next older desk top PC to the basement (Windows XP). I purchased a laptop which doesn't have a serial port so I upgraded to a Digitrax PR3 so I could also program sound decoders. I was going to toss the MS100 but noticed the PC (Windows XP) had a serial port. I thought that I would try the old MS100. It works great!
I work a lot away from home and spend my evenings upgrading my locomotive fleet to DCC and sound. I have a short test track, PR3 and laptop (Windows Vista) with Decoder Pro for testing and progrming away from the layout. I have one of my DB150 boosters to run the test track, but use it as a command station. The PR3 allows me to read back CVs, which I could not do with the DB150.
Jim, Modeling the Kansas City Southern Lines in HO scale.