More like "somone skipped that section when proofreading" It WAS accurate for the DT300 versions of those sets, but someone missed updating that section when they inserted the DT400 section after the DT400 was released.
There was a move afoot for a while on the Yahoo group to have people submit all the corrections to all the manuals. It seems to have fizzled, although if you bring that to their attention, they will put out an updated manual with the wording fixed. Digitrax DOES listen. What they don;t have is someone who's primary job it is to make sure the manuals are up to date and accurate.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Thanks for the clarification Randy. It seemed like the way to go but the Digitrax manual is somewhat "murky".
Joe
Yes, it's the SWCH key. No MODE because the DT400 has a key to directly access each 'mode'.
Randy:
Ken's correct there is no MODE button on the DT 400 but there is on the older discontinued DT 300. What now? Should he follow the switch setting proceedure outlined on page 79?
cudaken Randy, I went to page 107 and started reading. I was understanding just fine till I hit this. 5. Press MODE Key on the the throttle to enter Sw (switch) mode. There is no button labeled as MODE on my DT400? Jim, so you had to buy a new power supply to read your Blue Lines? I wonder if I hook my PR3 to my DB 150 if he could read the Blue Lines? Far as programing the motor decoders, I use a PK 2000 SD 7 for that, it shell lifts right off. Confused Yet Again, Cuda Ken
Randy, I went to page 107 and started reading. I was understanding just fine till I hit this.
5. Press MODE Key on the the throttle to enter Sw (switch) mode. There is no button labeled as MODE on my DT400?
Jim, so you had to buy a new power supply to read your Blue Lines? I wonder if I hook my PR3 to my DB 150 if he could read the Blue Lines?
Far as programing the motor decoders, I use a PK 2000 SD 7 for that, it shell lifts right off.
Confused Yet Again, Cuda Ken
Ken I have no problem whatsoever reading Blue Line sound decoders with the PR3 and Decoder Pro. Also to clear the command station memory you can use Decoder Pro it is much faster and easier.
Jack W.
Ken just make sure the output isn't more than the 15 volts max input on the PR3. Better measure it with a voltmeter. I'm finding out some of these DCC power packs put out up to 20 volts (HO).
I hate Rust
Hey Ken, I had the same problem yesterday with my Blue Lines. They've been good for 3 weeks, then...well. I fixed mine by reading that Blue Line operators booklet. Like Hamltnblue said in his post, also use direct mode programming. Be sure to remove your motor decoder. Set CV16 to 2 (with the decoder unplugged) for the sound and 1 for the motor decoder. Set CV15 to 1 to read/write to the motor decoder then set CV 15 to 2 to read/write to the sound decoder.
When I first got my Blue Lines I couldn't program them with the PR3 using the PS14 power supply. I used a spare Bachmann DCC power pack I had that was only reading just under 15 volts out put, the limit on the PR3 is 15 volts, and then I could program it. I read on Tony's train site about the Power Pax that Tony sells for around $50.00 to program Blue Line and Tsuamni decoders and others that 'hog up power" I purchased it though the Bachmann worked it had no protection, such as the Power Pax has, if a short occurred and could fry the decoder on the program track.
I'm taking a big interest in NCE and like the above poster, I would have purchased it if I had known, but no regrets the Power Pax works and I have peace of mind.
To program the motor decoder outside the Blue Line loco, I use NCE decoder tester. This is a cool inexpensive gadget,$19.50 at Tony and it does the job well.
Look in the manual about CV15 adn 16. They are the locks. What you basically do is set the sound decoder lock code to a number, say 3 with the motor decoder out. Then you install the motor decoder. It will be at the default code ( not sure what it is but it's in the book). When you set the address unlock the sound decoder and set it, then lock it. After that follow the same procedure with the motor decoder. Unlock it, and set it, but leave it unlocked if you want to change speed steps or any other thing. If you want to make any sound changes, lock the motor decoder and unlock the sound decoder before changing. It's a bit of a pain but works.
The other thing you can do is put the motor decoder in another engine to program and then put it back in the Blue Line.
Good Luck
Springfield PA
No the PR3 did not cause the problem.
WHat it sounds liek is that address 50 is still selected or in a consist with certain settings activated. See page 107 in the SEB manual where it shows you how to plug the DT400 directly into the DB150, set the switch to the OP position, dial up OpSw 36, set it to Closed, the set the mode to Sleep, then back to Run. This will clear all slots and consists. Then go bak to trying address 50 on the Blueline.
I love my Blue line engines, for the money hard to beat. But, they like to have decoder problems. Up to tonight fixing the problems have been easy.
Last weekend while Simon and the boys where over my Blue Line CSX AC 6000 sound stopped working. Here I thought Andrew just turned it off.
Tonight I pulled the motor decoder and tried using the PR 3 to read the decoder, would not read the engine.No big deal, hooked up the programing track to the Digitrax SEB and changed CV 8 to 8 using Direct Mode, all seemed fine. I then changed the address to its number which is 50. When I powered the track engine sound start ramping up and down, brakes on and off? Went back and set CV 8 again to default with 3 being the address. Sound was normal, changed address back to 50 and started the weird stuff again? Did this 3 or 4 times and same thing kept happing?
Then I did the CV 8 again and made the address 40, problem was gone? Went back to address 50 and the dumb stuff started up again! I could live with a different engine address, but rather keep its normal one.
Question are.
1 How do I get the PR 3 to read the Blue Line with out the Motor Decoder or with the Motor Decoder.
2 Do you think using the PR 3 caused the problem?
3 How to fix the problem so I can run address 50.
I will add, last night my Blue Line RSD lost it sound as well. I never used the MR 3, just the programing track and it is working fine?
If it cannot be broken or shorted out, I will fine a way Cuda Ken