ModelRailroadForums.com is a free Model Railroad Discussion Forum and photo gallery. We cover all scales and sizes of model railroads. Online since 2002, it's one of the oldest and largest model railroad forums on the web. Whether you're a master model railroader or just getting started, you'll find something of interest here.
I'm in the process of re-programing my locomotives from NCE back to Digitrax using JMRI. The decoder I'm trying to
program is from QSI. I have lights and sound, but no movement. Can't figure out why I can't get the engine to
run. This has happened to me several times and when I did get it running, I did something but did not write it
down and I forgot what I just did. Hey, I'm old, don't laugh you will be old soon enough (LOL)
Any ideas?
JRP
Not sure what you are trying to do. The DCC standards should allow any DCC system to control any DCC decoder. Did you consist them together in NCE? If so set CV19 to 0. NCE builds consists with decoder CVs while Digitrax just keeps track in the command station. If you didn't consist them it should work on either system without any changes.
I guess I'm dumb, but why would one need to "re-program" locos when switching from one dcc control hardware unit to another?
I have both the Roco z21 -and- the Digikeijs DR5000 (and I use JMRI, too).
For train operations on the layout, I use the z21 app, which works with everything above. It runs on my Samsung Galaxy tablet (9.2").
I can take an engine off the layout (currently set up to use the DR5000), and bring it upstairs to my test track (which uses the Roco z21), and everything "just runs".
NO "re-programming" needed. It just works.
OP:
I'd try resetting the engines that "won't work" back to "factory" (usually by setting CV8 to "8").
Then try again.
I'm in the process of re-programing my locomotives from NCE back to Digitrax using JMRI. The decoder I'm trying to
program is from QSI. I have lights and sound, but no movement. Can't figure out why I can't get the engine to
run. This has happened to me several times and when I did get it running, I did something but did not write it
down and I forgot what I just did. Hey, I'm old, don't laugh you will be old soon enough (LOL)
Any ideas?
JRP
First, put down the mouse and step away from the computer.
Second, place the engine on the track and perform the factory reset for QSI decoders, which IIRC is a three step, multiple cv setting process.
Third, confirm it runs on your layout properly using address 03.
After doing that, then you can play with jmri again.
Now that I think more about it, don’t most QSI decoders have a lock setting by hitting F9 a number of times? Or F10? It’s been years since I messed with one but I think there is one that will run sound and lights, but the engine won’t move.
Software reset is as you've been doing with the CVs, but then tilt the loco or remove power from the track for around 6-7 seconds, then restore power, wait for a response, usually 3 toots.
Here's a video I found from BLI showing how to do a reset.
You didn’t answer if you consisted the locos using NCE. That could cause the issue you were describing when going back to Digitrax. The fix is CV19 to 0.
You didn’t answer if you consisted the locos using NCE. That could cause the issue you were describing when going back to Digitrax. The fix is CV19 to 0.
He hasn't answered a lot of things. He seems to be obsessed with forcing his QSI decoder to accept programming for a Digitrax decoder, and wondering why it isn't working.
I'm in the process of re-programing my locomotives from NCE back to Digitrax using JMRI. The decoder I'm trying to
program is from QSI. I have lights and sound, but no movement. Can't figure out why I can't get the engine to
run. This has happened to me several times and when I did get it running, I did something but did not write it
down and I forgot what I just did. Hey, I'm old, don't laugh you will be old soon enough (LOL)
Any ideas?
JRP
What you describe is back asswards. Any NMRA-compliant DCC system will program any decoder.....but that's the key, it requires talking to the decoder. And the decoder determines the language used. In the case of QSI decoders, you must preform three separate steps, after which you MUST remove power to the rails. The Digitrax systems do this automatically when programming in Paged Mode. They don't do it if you do the reset in Ops Mode....and your decoder reset won't 'take' unless you do remove power, even for a fraction of a second.
From the NMRA:
'...Resetting QSI Decoders to factory default The Broadway, Atlas, and Lifelike equipped with QSI (ID 113) DCC sound engines use a different reset procedure. Check the manual that came with the engine. Some use a magnetic “wand” for the reset. If there is no “wand” then open the engine or access hatch and find the reset jumper. Remove the jumper and restore the track power. There will be an audible acknowledgment from the engine at the end of the reset sequence (usually 3 toots of the whistle/horn). Replace the jumper and test out using address 3. If a “wand” is present, locate the internal reset reed switch and place the “wand” over it for a moment. When track power is restored the engine will go through its reset procedure and let you know when done. To find the internal reset (reed) switch, place the engine on active track. Slowly move the “wand” over the top of the engine or tender until the engine alerts you, audibly responds, by a message. QSI also has a user software reset using the following multi step procedure: (1) Place engine on main track if it is still responding to its address. If not responding you may need to use the program track. (2) Set CV49 to 128 (3) Set CV50 to 255 (4) Set CV56 to 113 As the decoder in the engine resets you will hear an audible response, 3 toots or it may talk to you. Test the locomotive using address 3. You can then go ahead and set the loco number as you desire and/or reprogram other CV’s. An irritating part with the QSI decoders is that when they do get corrupted by a short, the locomotive affected can be very erratic in operation, resetting to default will put you back in control of its performance...'
The problem may actually not be the programming but the Digitrax Loco roster instead.
Clear your loco roster on your command station then try running the loco again.
