Hello All
Can the Digitrax PR3 be used as a standard programmer? I’m trying one with an Atlas gold loco and not having any luck. The computer is windows 7 and it sees the PR3 but when trying to read the CV’s of the loco it gets errors and doesn’t read. I’m also using the external power supply so it can be used stand alone.
Yes absolutely, I have no problem reading and programming QSI decoders. My set up is however with JMRI/Windows XP Pro not Windows 7.
My train computer runs Win 7 Home Premium, and my PR3 reads Atlas gold locos (and also P2K’s with QSI sound) just fine.
What software are you using, and what are you using to power the PR3?
YES I have an Atlas MP15 locomotive with the QSI sound decoder. I have both a PR3 and MS100 with a Windows XP personal computer and JMRI Decoder Pro for programing. No problems.
I also use the PR3 as a stand alone programer with my laptop, Windows Vista and JMRI Decoder Pro. No Problems.
The software I am running (And learning) is decoder pro. I have it set to the PR3 in stand alone program mode. It looked like it was downloading ok to the decoder but I didn’t have time to test it. It just wasn’t reading it. Maybe I was using the wrong version of QSI decoder. I was trying version 7 when maybe it should have been 6. I’ll have to try that tonight.
The loco is the MP15DC.
The PR3 is a Digitrax product. It can program other decoders, but only the standard functions.
It will download sound files into Digitrax SFX sound decoders. It will NOT download sound files into any other kind of sound decoders, though. So, you should be able to read and write CVs in your QSI decoder, but you can’t change the sound files.
I may not be up to date on their latest products, but I don’t think QSI has a user-downloadable sound decoder.
Can you read none sound decoders?
Like I posted before, when I first hooked mine up all I could read where none sound decoders. Hopefully Simon1966 will chime in due to the fact he fixed mine. It been a year ago, so I don’t remember the details clearly. First he gave me a different USB cable. Then he went into Comfig and assigned the PR3 a USB port that was on the front of the computer.
Sometimes, if the wheel or test track is little dirty, I will get a error 308.
After you get it working, I am sure you will like it.
Ken
Which version of JMRI? Some changes to the QSI definitions were put in about 2.9.5 to fix an issue with reading QSI V7 decoders. I’d really suggest you upgrade to 2.10 if you haven’t already.
And if you use the “Ident decoder” button in JMRI, it will read the decoder information and present you with the correct decoder definition. I’ve found that it’s very accurate in correctly identifying the particular QSI version you’re reading.
Also, you never did tell us what you’re using to power your PR3. The originally-recommended PS12 was pretty anemic, and the newer PS14 is better. But for sound decoders, something in the 16v to 18v range is better still (the PR3 can handle up to 20v). I use a 1.1 amp, 18V power brick from an old printer with my PR3.
Thanks
The version is the latest one which is 2.10
I tried the Ident Decodeer and was receiving errors.
Th epower supply is the Digitrax PS14
I haven’t tried a non sound decoder yet.
What is the error number you are receiving?
If it is a reading time out error, 99% of the time it is from a wrong com port in the set up.
Other errors may be due to a faulty USB cable or port, I have seen this more than once.
Thanks all
I Just got home and will try what has been suggested today, starting with cleaning the track.
When I looked up the MP15DC in DecoderPro to answer someone else’s question, I found it listed under QSI version 6.
After playing some more I’m getting error code 308 which is no ack from loco.
I tried a bachmann 70 tonner without sound and getting same thing
I also tried one of my soundtraxx loco’s and when trying to identify I get the 308 but the PR 3 has a high pitched noise while trying to read.
As it sits now the decoder pro is set for PR3 stand alone mode. The pr3 USB light is one second on and one second off. The stat light flashes about every 2 seconds. When trying to read a decoder it flasher faster.
The com port settings are set to the current port which is 4, matched th57600 baud with hardware flow control on to match decoder pro. I don’t see anywhere that it mentions the correct data bit, parity and stop bit. The port is set for default N,8,1
I’ve since tried a different power source which is 13.5 volts DC with no change.
I also noticed that If there is no loco on the track and I try to read a CV I get a 301 code saying no loco. If a loco is on the track I get a 308 code
Got anything with a plain NCE, Digitrax, or TCS decoder in it? The Bachmann dcc on-board decoders are notoriously troublesome. I haven’t tried much since I just set up my program/test track, but I had no problems with one of my P2K GP-7’s with a TCS decoder on the PR3. My Zephyr has programmed everything I’ve tried so far, but I’ve never tried a Tsunami. It did handle QSI and Loksound, and the old Sountraxx LC decoder I had, as well as Digitrax, NCE, and TCS non-sound decoders.
–Randy
Thanks
I have only 2 non sound decoders and they;re both bachmann.
About half are Atlas Golds and the rest are Tsunami’s Broadway limited, and MTH.
Tomorrow I’ll bring my laptop from work home since it has windows XP installed and give it a try.
It seems weird that it’s going throught the paces and nothing is programming or reading.
I guess I’ll have to try to find a higher voltage power supply as well.
I would all so pick up a new USB cord as well.
Forgot to add, I also swapped the USB cable with my printer and no change.
Have you tried the PR3 with the SoundLoader program from Digitrax?
I have a PR2. It works with SoundLoader, but I’ve never been able to make it work with JMRI. I am using an old MRC power supply, and people have suggested that it’s not strong enough for the PR2.
Anyway, the simpler SoundLoader program may help you make sure your COM ports are set up correctly.
When you will install the PR3 on Win XP, make sure the com port you use is the one windows indicate in the peripherique device manager. But you may have already done so.