Just bought a new laptop (Dell with Vista) and was looking forward to using DecoderPro but cannot get it to work with my NCE PowerPro system. The program times out waiting for a response from the NCE command station. I have posted this problem on the Decoder Pro users group site but still no solution. Any suggestions would be appreciated.
What interface are you using? The NCE USB one, or are you using a USB to serial cable? If the latter, go into Device Manager and look at just exactly which serial port your computer assigned the USB to serial adapter. It will likely be some oddball port liek COM5. This is what you need to put in JMRI for the port when selecting the NCE command station where it asks for the connection.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
I am using a USB to serial connection (not the NCE USB card). I have made sure the port designation is correct. I am beginning to suspect that the problem is with the command station (maybe the 2007 EPROM upgrade?) although I have no problems running or programing with the handheld cab.
dsmillerI am using a USB to serial connection (not the NCE USB card). I have made sure the port designation is correct. I am beginning to suspect that the problem is with the command station (maybe the 2007 EPROM upgrade?) although I have no problems running or programing with the handheld cab.
What specific make/model of USB to serial adapter are you using? There are some that do not supply all the RS232 control leads. I don't know which ones do or don't, but if you let us know what you are using someone may be able to provide more info.
Also, I remember that at least one make/model of USB to serial adapter won't completely plug into the NCE command station because of (if I recall) interference of the screws/nuts. Make sure that isn't the case, and that all the connections are secure.
Finally, if you're using an adapter or cable between the USB to serial adapter and the command station, be sure it's "straight through" and not a crossover or "null modem" adapter/cable.
HTH,
Steve
dsmiller I am using a USB to serial connection (not the NCE USB card). I have made sure the port designation is correct. I am beginning to suspect that the problem is with the command station (maybe the 2007 EPROM upgrade?) although I have no problems running or programing with the handheld cab.
Could be, but I'd think by this time if there is a difference for the 2007 EPROM it would be in at least the test version - I have the latest test version and the only NCE options are 2004 and 2006. Do you have the correct baud rate selected? Oh yeah - that's probably it. Go into Device Manager and select the port used by the USB to serial adapter and make sure the communications settings there match the requirements of the NCE command station. It doesn't matter that you already have the correct settings in the JMRI preferences, the Java they use to set serial parameters doesn't change them for Windows, at least not on XP and I doubt Vista either. In fact somewhere on the JMRI site is a FAQ I wrote about this. I had the same problem with my home built serial interface Locobuffer for my Digitrax system - JMRI was set to the proper speed but it wasn't actually using that speed - it was using what Windows set it to. Once I fixed the Windows settings it worked fine.
I am using a Keyspan adaptor (recommended by Decoder Pro). I have checked the connecting serial cable and it is a straight through cable. I verified that the baud rate in windows is correct. Still no luck.
I did notice that when I start up Decoder Pro, despite the initial "Error NCE Using ....." error,if I forge ahead and hit the 'Programming Track Programer' button thenthe 'Read Type from Decoder' button, a loco on the program track willjerk and the NCE command station track light will blink rapidly as ifreading the decoder but then eventually I will get the message "stoppingdue to error, timeout talking to command station". It is as if thecommand station is recieving commands from Decoder Pro but Decoder Prois not receiving anything from the command station.
DS,
I too have the same exact problem you describe. I have changed the port and baud rate as listed in hardware manager, but still not solid connection. I pushed forward like you and I also receive the 'stopping due to error, timeout talking to the command station.' I am going to try one the recommended cables from the website to see if this makes a differance. I'll let you know my progress. If you find the lucky combination, let me know.
Jeff
If I come up with a solution I will certainly let you know.
Dave
I have been using Decoder Pro for about two years with a Digitrax MS-100 and my old Pentiun III (550 MZ) and Windows 98 SE. It has worked fine but my wife gave me my first sound locomotive last year for Christmas.
I plan to upgrade part of my locomotive fleet with some sound decoders. So I need to upgrade the computer. I just purchased my wife a new lap top computer for Christmas. I told her that I would take her old laptop (Windows XP) to the basement train room. I also ordered a Digitrax PR3.
Decoder Pro continues to improve.
Jim, Modeling the Kansas City Southern Lines in HO scale.
Dave and all,
I replaced the serial cable with one from the recommended list and it now works. I did also delete and download a new version of Decoder Pro at the same time. I'm not sure which was the issue, but I suspect it was the cable.
Jeff,
Happy to see you got it working. Where can I find the recommended list for serial cables?
Dave,
I believe there is a list on JMRI's website. I purchase mine based on the recommendation from this website, http://siskiyou-railfan.net/e107_plugins/forum/forum_viewtopic.php?7826. The cable from www.geeks.com, was only $7, but shipping was $11. One other critical item I have noticed, the cable must be tightly plugged into the NCE. If not, error messages are present.
A older laptop with a Pentium Chip that is 500 meg or faster with a USB Port and windows XP will be just fine for the Decoder Pro. I have JMRI with a RR Cirkits Locobuffer adapter on my computer. There was attention paid to setting up the com port and the rate of baud. Once everything was settled it was possible to program the QSI engines, run them from the computer via mouse at the throttle panel and knock down the CV's quickly.
My favorite feature is the retaining of each engine's sheet. That way after a reset, one could simply re-dump the settings back onto the engine painlessly.
Without a laptop, you are tied to home. Should you travel you need a laptop, a cheap one that will do the work with USB. That way, if your engine misbehaves or otherwise get a little "mental" you can work on it right there wherever that may be.