I moved on to speed match three BLI E8 Pragon2 locos.
I’ve only been changing CV5 values. On several occasions now, somehow, CV1 (loco address) seems to be changing to some random value and therefore changing the locomotive’s address.
SO, I’m wondering if the wire gauge I’m using to go from The DigiTrax PR3 or LokProgrammer the Programming Track is too small. For sake of convenience I’m temporarily using a couple of sections of Bachmann E-Z Track with one of those “grade crossing/connector” track sections. The wire is Bachmann E-Z Track, about 10’ long. Seems pretty thin. Using a wire gauge I’d say it’s 26awg.
I think it’s kind of weird that CV1 has changed “by itself” while changing only CV5, on two different locos, same brand, same model.
Arto, I don’t think the wire conditions you mention have anything to do with the problem. Hate to bring a negative comment, but those old QSI decoders are junk (ask me how I know). I would bite the bullet and just replace it with a current manufactuers’ decoder (Tsunami, LokSound, TCS)
Sorry Rich, one of the very few times we’ll have to agree to disagree. It’s not that I’m a QSI hater, but they have always had that wonky “go to sleep” issue and they often need to be reset. Plus, their sound file for diesel just doesn’t sound anything like a EMD nor an Alco. That said, they originated many years ago in the infancy of DCC and were life changing. It’s just that nowadays they’re a dinosaur. Just my $.02
Yeah, I realize that Rich. I just wanted to express why I was suggesting to Arto to consider replacements. In fact, my biggest issue with them is the sound file. One of my very first threads I started here 11 years or so ago was that the sound file, at least to my ears, sounds nothing like a diesel locomotive. IIRC, I think I mentioned it sounds more like a marine vessel engine. But at least certainly not an EMD nor an Alco. Motor control seems fine, now that I know the three CV sequence to reset it I can live with that, but the sound file . . . . [:(]
I beleive that some of the CVs won’t hold their changes and revert back to default setting after either a period of running or after power down and power up cycles. Same thing happened to me with older Soundtraxx Tsunami’s, which are every bit of “junk” as the QSI. Just a function of the technology of the era.
There is no doubt that the new Loksound V5 and Tsunami2 are better than their predecessors, but dealing with old technology can be rewarding too if you know the limitations.
I just keep the individual turbocharger and prime mover sounds turned down some on the QSIs so that the hisses, spurts, flange squeal, bells, and whistles/horns over power the PM. Which is probably more prototypical anyway.
Sorry about the confusion. To be clear…this thread I started is about three BLI PRAGON2 locos, not the BLI QSI equipped loco.
There are up to four locos I use in this consist. One BLI w/QSI, plus three BLI Paragon2. Obviously the QSI unit has way different performance characteristics than Paragon2. The QSi unit’s top speed is MUCH faster than the Paragon2 units, so I tried to to reduce it’s max speed first.
I decided to put the QSI loco aside for now, and focus on the three Paragon2 units.
Sometimes, when I change CV5 (using JMRI) on any of three BLI Paragon2 locos, the loco’s address changes. I suspect that’s what happened with the QSI loco described in my other thread/post.
When I put the loco back on the mainline with the changed CV5 value, it doesn’t respond. Eventually I discovered the loco wasn’t responding because CV1 had somehow also changed. The CV1 change does not show up on JMRI - UNTIL I do a “Read All Sheets”. Then I can see what number the address has changed to. And it’s always a three digit number. All my locos use the short two digit address. For all four of these locos (1 QSI + 3 Paragon2) the short address I use is 99 (all four units road number start with 99).
Hope this explains it better.
(PS: Chris, I agree with you. I avoid QSI equipped locos at all cost nowadays, and replacing the decoder is probably the best option)
EDIT: I don’t know if this makes any difference, but…FWIW
I have both a DigiTrax PR3 AND a LokProgrammer connected to the PC at the same time, PR3 on USB Com3, LokProgrammer on USB Com4. I manually change the wire connection from PR3 & Lok at the Programming Track. The PC is a brand new HP Win
Arto, my bad. It clearly states in your second sentence that they are Paragon equipped. I just didn’t originally read it carefully enough. I’ll do better! [:D]
As for the QSI decoder. Some had a magnetic read switch that was used for resetting. Sometimes they get accidentally reset during a derailment or going too fast into a sharp curve and I accidentally reset one with a magnetic uncoupling tool.
Pete, what value should I use for CV29 to disable DC? It looks like CV29 is related to a lot of other functions.
AND, now guess what (again)?
I did a “Read All Sheets” with JMRI one of the locos that I’m trying to slow down using CV5 (CV5=190). It showed CV2=2 (should be CV2=1) and the loco address (CV1) showed 99. Changed CV2 back to CV2=1. I put the loco back on the mainline - no response. Put it back on the programming track, “Read All Sheets” again, and CV1=127 - address changed again!
EDIT: Yep. Confirmed! CV1 changed back to 127 AGAIN. A repeat of what I posted above
CV1 should equal 3 if you’re using a long address over 0127. Anything under that is considered a short address.
CV29 configures a few things. DC disable, Direction, long address enable, and speed step 14/28-128. Use a CV29 calculator to easily get the proper setting. CV29 calculators can be found online if you Google. Once you enable long address then the decoder will ignore CV1 settings. If the decoder is not responding. Look at CV19. It may have a consist address present. Sometimes for some reason will not clear CV19 when breaking up a consist. Some of my Paragon and an NCE will keep CV19 for some reason.
Using JMRI, on the CV list shown under the CV Tab, CV1=99, the address I use for that loco. On the JMRI “Basic” tab, “Short Address” is selected, Active Address=99, Primary Address=99. Extended Address=128 for some reason. And “Address Format”=Short (one byte) address.
Well, now the other two Paragon2 are not responding on the mainline.
I’m at a complete loss as to how and why this is happening.
I guess that’s probably why I stopped bothering to change CV except for the address years ago. I thought I’d give this a try again but this is insane. All the documentation is inconsistent and in many cases outright wrong or conflicting.
I have support ticket into BLI. But I suspect this is going to be an ongoing/reccuring issue. Right now I feel like getting rid of all this stuff for all the time I’ve wasted.
I’ll second what Rich said. I’ve had several decoders (not QSI) where it seems like Decoder Pro changed the ID when I was adjusting other CVs. I have a separate programming track hooked up to my DCC system, and using that to change the ID back would work.
Guys…forget the QSI decoder for now. I’ve put that loco aside.
The problems I’m having now are regarding the Broadway Limited E8’s, all Paragon2.
Something keeps changing CV values that I have not changed! I’ve verified this repeatedly. And there really isn’t any consistency to what I’m seeing, except that the CV values keep changing without me doing anything. Oh, excuse me. The only thing consistent is the loco Address keeps changing to 127.
Like now for instance. I put loco #9967 on the Programing Track. Read the settings from the JMRI Basic tab. It says Primary and Active Address is 99. Save and Close the JMRI window. Change the PR3 Mode back to Interface. Put loco on mainline. Power On. Select loco 99 on the throttle. Loco powers up, sounds come on. But no throttle response. Prime mover sound is on but other sounds (bell, horn) do not respond. I put the loco back on the Programing Track, JMRI CV tab, Read Full Sheet. Sure enough. Loco address changed to 127. HOWEVER…when I had the loco on the mainline and it wouldn’t respond to address 99, I tried address 127, and got no response either.
All of this brings up the question again, of whether or not the 10’ long 26awg wire I’m using connecting the PR3 to the Programming Track is adequate
If I have to make ANOTHER (3rd) connection to the Programing Track, directly from the Command Station, bypassing the PR3 and LokProgrammer, this just adds yet another layer of complexity, works for some locos, not for others. I’m really getting tired of this. If things don’t work, thats fine. But what is really bugging me is there is absolutely no consistency to what’s going on.