DCC requires connections that are more precise than DC. When you wire the layout, take care that each connection is stout.
- Douglas
I had only 2 projects today, finish staining my wood deck out back that I had pressure washed 2 days ago, and run some more experiments with this NCE 'stuff'. Got the staining of the deck done before a late lunch, then started again with the dcc experiments.
To answer your question Randy I have a Digitraxx PS515 power pac I obtained from the same source as the NCEPro. I even took a meter to that power pack and determined the AC output was fine.
I decided to replace that 'back up' flat battery inside the control box as well, just to try and cover all the bases.
I started the experiments again trying different 'pair' combinations of those 4 locos. It appeared often that the shut down would occur when something inside one of the pair would trigger a little clitch that would act like a mini short and shut off power to the main tracks and cause the cab screen to go blank
I added 5th loco into the mix thinking that it was somthing triggered by the QSI decoders in most of those engines I was experimenting with. I chose one of my engines that had a Tsunami decoder in it.....Ahhh, same s___t!. I was beginning to believe it was some fault in my Cab itself or the base unit.
I just happen to have two other power supplies I had gathered up for possible future use, Since I had exercised most of my options, I decided to try and replace the power supply. WOWee it worked, no more shut downs, both engines kept running !!.It got me to thinking what could have gone wrong with this highly recommended digitrax power supply,...after all aren't these thing pretty simple units that either work or are burned up? Let me try one more experiment,...plugged it in and metered the output. It was fine. Let me cut a little off those ends of the wires and get brand new wire out in the open. Plugged that into my NCE unit, and IT WORKED NOW.
So my total problem was a lack of a good electrical connection with my power supply,...unbelievable.
Brian
My Layout Plan
Interesting new Plan Consideration
rrinker WHat are you using to power the NCE system with? The PH Pro doesn't come with a power supply, so you have to supply your own.
WHat are you using to power the NCE system with? The PH Pro doesn't come with a power supply, so you have to supply your own.
Here is the NCE warning:
BE CAREFUL
An NCE P515 power supply (15VAC - 5AMP) is the preferred transformer for your system. If you are using a different transformer be sure to measure the actual no load voltage before connecting it to your system. Many 16 Volt transformers put out 19 to 20 Volts with no load. If you have a transformer that puts out more than 18 Volts do not use it. The maximum input voltage to your Power Pro or PB105 is 18 Volts AC. Voltages higher than 18 Volts AC will ultimately destroy your booster resulting in an expensive repair charge.
Rich
Alton Junction
WHat are you using to power the NCE system with? The PH Pro doesn't come with a power supply, so you have to supply your own. That everything shuts down, including the cab display, seems to indicate the power supply is what is shuttign down, or the voltage is droppign unde rload to less than the PH Pro can reliably run on.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
So I have my NCE Pro set up with a separate program track and mainline track. I got out several locos with factory sound/dcc decoders to see if I could read them on the programming track, and run them on the mainline.
On the programming track, I was actually able to read the manufacturer's code on several of the decoders. There was one I could not read, a BLI E-7 C&O with a QSI decoder.
I then took these 4 locos to the mainline track, and was able to run each of them individually.
I then tried to place 2 locos on the mainline track. Each time, regardless of the combo of engines the pair would turn on for a very brief time, then the status light would begin to flash very quickly, the engines (and track) would shut down, and the cab display would go blank/dead?What's wrong here? The mainline should be capably of running multiple locos??
I'm just starting to try to learn and use my NCE Pro system. Some of my first experiments were with sound equipped Broadway locos. The QSI ones did present some problems, and then when I began to read about all the variables and exceptions with these various decoders, the fear came that this DCC programing was going to be a much more involved process than I envisioned. I had hoped that these multiple differences between systems and decoders had been simplified by now in its development.
It's costing $$ already. Found out that the Bachman DCC Loco I have has a EZ Command Diesel Decoder with VERY few programing options. So I bought an NCE BACH-DSL replacement full function deccder to replace it. I figure it's a good one to try replacing a decoder on since it's a pretty cheap DCC locomotive.
Gary
gdelmoro Installed and working!
Installed and working!
You're in the big leagues now, Gary.
gdelmoro Ok got the PTB-100 today seems simple to hook-up. Just 1 question, do the black wires connect to the power supply that supplies the command station or do I need to purchase a separate wall wart? If I can I would like to tap into the terminal block that feeds the Track Busses on the feed side.
Ok got the PTB-100 today seems simple to hook-up. Just 1 question, do the black wires connect to the power supply that supplies the command station or do I need to purchase a separate wall wart?
If I can I would like to tap into the terminal block that feeds the Track Busses on the feed side.
One way to do it is to connect the two black wires to the power inputs to your command station. This is the same connection as the outputs from the command station power supply.
The other way is to connect the two black wires to a separate power source such as a wall wart or power pack. I use this option.
Be sure to observe the minimum and maximum voltages stated in the PTB-100 instruction sheet.
richhotrain Yeah, but we're not talking about Crandell (Selector), we are talking about Gary (the OP) who has an NCE Power Pro that cannot read a QSI Quantum decoder on the Programming Track because NCE never bothered to upgrade its command station to read sound decoders. Now that Gary has ordered a PTB-100, once it is installed, he will be able to read, and more importantly write to, the QSI Quantum decoder, and any other sound decoder, on the Programming Track. Rich
Yeah, but we're not talking about Crandell (Selector), we are talking about Gary (the OP) who has an NCE Power Pro that cannot read a QSI Quantum decoder on the Programming Track because NCE never bothered to upgrade its command station to read sound decoders. Now that Gary has ordered a PTB-100, once it is installed, he will be able to read, and more importantly write to, the QSI Quantum decoder, and any other sound decoder, on the Programming Track.
richhotrain selector Interesting you should say that, Randy. I learned that tip on my own, but sort of by accident/luck/wondering-if-the-system-needed-a-pause from me. I would hit the button to enter the add on the DT400, but learned to pause-two-three before hitting the button on the "long add y?' Once I caught on, I have never had a swing and a miss. Dunno, Randy said "no booster needed", but the booster is needed to get the Power Pro to read the QSI decoder on the programming track. Once I installed the PTB-100, I never again had a problem trying to read a sound decoder on the programming track. Rich
selector Interesting you should say that, Randy. I learned that tip on my own, but sort of by accident/luck/wondering-if-the-system-needed-a-pause from me. I would hit the button to enter the add on the DT400, but learned to pause-two-three before hitting the button on the "long add y?' Once I caught on, I have never had a swing and a miss.
Interesting you should say that, Randy. I learned that tip on my own, but sort of by accident/luck/wondering-if-the-system-needed-a-pause from me. I would hit the button to enter the add on the DT400, but learned to pause-two-three before hitting the button on the "long add y?' Once I caught on, I have never had a swing and a miss.
Dunno, Randy said "no booster needed", but the booster is needed to get the Power Pro to read the QSI decoder on the programming track. Once I installed the PTB-100, I never again had a problem trying to read a sound decoder on the programming track.
Might need it to read, but a lot of people rush out to get program track boosters thinking they can't write to the loco. They read OK on my Zephyr. All the program track boosters in the world won't help Selector - his DB150 has no readback capability. However, that DB150 does put out a stronger program pulse than most systems with a dedicated program track, so while it can't read anything - there's nothing it can't write. The bench programming system at the club, if I don;t have my PR3 program track, is a DB150 and throttle. Most common thing is address change - we operate on a first come, first serve basis, so the guy with 2102 who was there helping set up gets to stay 2102 and the next one that shows up has to be something else.
Only thing is, you can't wait TOO long or the prompt times out and you have to start over. I usually just take advantage of the fact that it repeats the prompt until you exit programming - so if the first time I hit Y it doesn't work, it will the second or third time.
rrinker You should do CV29 LAST, after CV17 and CV18, otherwise yoou runt he risk of getting the loco set on a completely unknown address. As for what the value of CV29 was BEFORE he set it to 38 - frankly, what does it matter? It was wrong for a long address, that's for sure. My beef with sooome oof the 'simpler' systems isn't that there is no CV readback - it's that there is no dedicated program track, which means it's easy for the beginner to program every loco on the tracks. Sometimes it may be nice to knwooo what's in there befoore starting, but in a case like this where what was in there was wrong - don't think it would have helped much. I'd lay odds that it was 6, which is the default, since it wasn't being changed, plus the loco ran on address 3. I also suspec the automated long address programming, where it calculates CV17 and CV18 and CV29 for you, in the PowerPro has the same problem with QSI that the Zephyr does - it sends out the 3 CV values too fast for the QSI decoder too process. I had the same issue until I got a DT400 throottle, the automated address programmign on it prompts you to enable a long address, therefore there is human 'wait time' built in to the process so by the time you hit the Yes button, the QSI decoder is ready to accept the CV29 value. I had no issue programming older Broadway (when they used QSI) and Atlas locos with my Zephyr once I got the extra throttle. No booster needed. Just a 'wait state'. --Randy
You should do CV29 LAST, after CV17 and CV18, otherwise yoou runt he risk of getting the loco set on a completely unknown address.
As for what the value of CV29 was BEFORE he set it to 38 - frankly, what does it matter? It was wrong for a long address, that's for sure. My beef with sooome oof the 'simpler' systems isn't that there is no CV readback - it's that there is no dedicated program track, which means it's easy for the beginner to program every loco on the tracks. Sometimes it may be nice to knwooo what's in there befoore starting, but in a case like this where what was in there was wrong - don't think it would have helped much. I'd lay odds that it was 6, which is the default, since it wasn't being changed, plus the loco ran on address 3.
I also suspec the automated long address programming, where it calculates CV17 and CV18 and CV29 for you, in the PowerPro has the same problem with QSI that the Zephyr does - it sends out the 3 CV values too fast for the QSI decoder too process. I had the same issue until I got a DT400 throottle, the automated address programmign on it prompts you to enable a long address, therefore there is human 'wait time' built in to the process so by the time you hit the Yes button, the QSI decoder is ready to accept the CV29 value. I had no issue programming older Broadway (when they used QSI) and Atlas locos with my Zephyr once I got the extra throttle. No booster needed. Just a 'wait state'.
It matters because that was why he could not get the loco to respond to the long address. My guess is your guess. The value was probably 6. That meant that he did not program CV29 to accept a long address. Plus, it may have been that CV1 (short address) was 'on' and that CV17 and CV18 were not properly valued.
gdelmoro honestly, I DON'T KNOW. But I guess it must have been 6 because the 128 speed option worked.
honestly, I DON'T KNOW. But I guess it must have been 6 because the 128 speed option worked.
gdelmoro that's interesting ! I finally got the address changed. I changed CV29=38 then CV17 then 18 and it worked. CV29 was the key. I originally tried to do it the NCE way was I o with the BLI Locos but it didn't work.
that's interesting !
I finally got the address changed. I changed CV29=38 then CV17 then 18 and it worked. CV29 was the key.
I originally tried to do it the NCE way was I o with the BLI Locos but it didn't work.
Uh.....I think setting the long address in a decoder is governed by the NCE manual, not the QSI manual.
I just set any loco on the track and follow the instructions in the first few pages in the NCE manual.
Is OP doing something more complicated than that?
Thanks Rich, Glad you're on this forum!
gdelmoro Thanks everyone. I purchased the booster. Ill try the CV29 and let everyone know how it goes. Are NEW QSI decoders different? How so?
Thanks everyone. I purchased the booster. Ill try the CV29 and let everyone know how it goes. Are NEW QSI decoders different? How so?
http://www.atlasrr.com/DCC/New%20Features%20Available%20with%20Quantum%20Titan%20Sound%20Decoders.pdf
Stevert Actually, that's not quite correct for Indexed CV's. So not the same as different bits within a single CV.
Actually, that's not quite correct for Indexed CV's.
So not the same as different bits within a single CV.
Here is a link to the QSIs primer on indexed CVs.
http://docs.wixstatic.com/ugd/0f7119_a2df90ce109347f493ec8c95253ec6a9.pdf
Easy reading for a complex subject.
maxman richhotrain Unfortunately, the Power Pro Programming Track has not been updated to program sound decoders without the need for a booster. I suspect that if they did come up with a mod or add on to do this, it would still be easier/less expensive to purchase a PowerCab. You would end up with all the capability, plus an extra cab. I don't know what the currently available power boosters cost, but Streamlined Backshop is having a summer sale on the PowerCabs right now for $137 plus shipping.
richhotrain Unfortunately, the Power Pro Programming Track has not been updated to program sound decoders without the need for a booster.
I suspect that if they did come up with a mod or add on to do this, it would still be easier/less expensive to purchase a PowerCab. You would end up with all the capability, plus an extra cab. I don't know what the currently available power boosters cost, but Streamlined Backshop is having a summer sale on the PowerCabs right now for $137 plus shipping.
gdelmoro Ok guys I tried to do what the manual said but the address remains at 3. The manual says check the chart (which shows CV17=219 & cv18=99) the next bullet says set CV49 to 129. So I did all three in that order and nothing. Guess I'll try setting CV29 to 38 (based on a CV29 calculator), maybe that's the problem. Well, I lowered that LOUD sound to a nice level, THAT worked
Ok guys I tried to do what the manual said but the address remains at 3.
The manual says check the chart (which shows CV17=219 & cv18=99) the next bullet says set CV49 to 129. So I did all three in that order and nothing.
Guess I'll try setting CV29 to 38 (based on a CV29 calculator), maybe that's the problem.
Well, I lowered that LOUD sound to a nice level, THAT worked
Programming on the Main (POM) is best left for what I call "testing on the fly", not for the basic programming of a decoder.