BLI PROGRAMING HELP!

[claycts]

I programmed ops mode and of course it works. This is a matter of my will to be able to use the program track, dcs100 and decoder pro to do all my engines. The ^&*(#$@^ engine is the infamous Genesis Challenger.

The Haunted one as it is known pulled a good one today.

Parked in the Engine terminal on the ready track. everything else is perfect. Stop operations (power and -) went up for a kidney break, came back (power and +) and a district breaker trips and the indicator board lights up. ONLY thing in that district is the Challenger. Shut down, Removed the Challenger and all is well again. Finished moving things (testing track work) and shut down, put the Challenger back on the SAME track, turned on the power and all is well again.

Maybe the engineer took a LONGER kidney break than me!

That was a setting problem on the PSfour, needed to go to 30 miliseconds instead of the default 10 miliseconds.

 

[scubaterry]

I used to have intermitent problems with my "super Chief" programming my BLI loco's. Sometimes it would work sometimes not. I recently got my first Tsunami and I could not program it at all. I finally broke down and got the Soundtraxx PTB100 program booster. I haven't had a problem since. It programs the Tsunami as well as all of my BLI loco's and my plethera of motor only Digitrax decoders. Money well spent.
Terry

[rrinker]

  If you're bound and determined, try the Soundtraxx PTB booster. If your program track is part of the layout, now you'll need a 3-positon switch. Or two switches - I'd prefer to set things up so the booster is NOT used when not needed - three choices: track power to run the loco inand out, program mode WITHOUT booster, and program mode WITH booster. Having not experimented with any of the program boosters yet, I don't know how good they are at avoiding decoder damage. One of the key reasons to put a new loco on the program track before the main is simply because the normal program track outputs don't carry enough energy to fry the decoder if it is shorted - plus power is only on the program track when the actual program signal is being sent. If it won't program - it's wired wrong (except maybe sound decoders...). Now, if the booster cranks the power up to the point where it can damage decoders if mis-wired, it kind of defeats the purpose. Maybe I'm paranoid. Maybe they react fast enough to a short that nothing bad can happen.

                                                --Randy

[claycts]

I programmed ops mode and of course it works. This is a matter of my will to be able to use the program track, dcs100 and decoder pro to do all my engines. The ^&*(#$@^ engine is the infamous Genesis Challenger.

The Haunted one as it is known pulled a good one today.

Parked in the Engine terminal on the ready track. everything else is perfect. Stop operations (power and -) went up for a kidney break, came back (power and +) and a district breaker trips and the indicator board lights up. ONLY thing in that district is the Challenger. Shut down, Removed the Challenger and all is well again. Finished moving things (testing track work) and shut down, put the Challenger back on the SAME track, turned on the power and all is well again.

Maybe the engineer took a LONGER kidney break than me!

[rrinker]

Crazy Idea:

I have a spare Prodigy DCC system. I can build a DCC program only track for the apin in the %^*$$ engines and do the others on the real program track with Decoder Pro.

Any feedback?

 Why bother? Like I said, Ops Mode on your Digitrax will work just fine. I just deleted my QSI manual download witht he intent of hitting the site for the latest version, but haven't done it yet. Actually if you have one of the Atlas Trainmasters they have the exact steps for setting the long address in Ops Mode int he manual that comes with it, although the sample numbers are for road numbers of the various Trainmasters. Just calculate CV17 and CV18 values for your desired road number and subsitute in the example.
 I do all my sound programming in Ops Mode, especially volume adjustments, since you can hear them immediately. Same with motor control stuff, the other week I was showing a friend how DecoderPro works on his N scale layout, DCS100. He had two scratchbuilt locos he wanted to speed match, so I was working on speed tables while they both ran around his layout. I actually recommended he leave them mismatched since they are different types of locos, but he also likes to operate by himself and won;t always have a second operator to run the helper. And a helper is REQUIRED - even a 10 car laoded train won't make the hill no matter how much of a run up at it you get - the locos are restricted to protoypical speeds anyway. Pull in behind with the second loco, and start shoving, then it makes it up the hill. Lots of fun, takes some skill too - this is N scale with code 40 track and finescale flanges and wheel tread widths. Read - easy to knock off the track.

                                        --Randy

[selector]

Crazy Idea:

.. for the apin in the %^*$$ engines .

Any feedback?

Well, I'll try.  First are we talking about 8 or 9 pin connectors in the %^$$ engines?

[claycts]

Crazy Idea:

I have a spare Prodigy DCC system. I can build a DCC program only track for the apin in the %^*$$ engines and do the others on the real program track with Decoder Pro.

Any feedback?

[Leighdrums]

Friends Layout:-  We needed to use a track programming booster with the Super Chief.  We use a SOUNDTRAX unit and this solved the address programming problems.  Just wire it into the programming track and use either the Digitrax 4 Digit address method or preferably the values to CV17 and CV18 way (see manuals for correct values).

My own layout:-  Did not need to use a track programming booster with Digitrax Super Empire Builder which uses DB150.  Can programme addresses on the main in OPs Mode.

All above with DT400 throttles.  We both have an assortment of BLI/Athearn/Trix/Tsunami etc sound decoders and have encountered no problems.

Hope this is of help from England, UK

[selector]

Randy's suggestion to mute the sound makes a great deal of sense.  Means less power wasted in the process on unneeded sound, and more avail for the inputs.  Take a small section of leftover track, hook up leads from it to the correct outputs on your controller, and do programming of your address in paged mode...if that works.  If not, then you'll have to do all of it in Ops mode, but you will have to figure out the hex equivalents of your addresses.  Not a big deal, but can be a pain.

My SEB does all of this with all decoders, from 100LC to Tsunami, to various orders of QSI.  But I still do Paged Mode on a small section of specific track for the addressing.  It is a pain because I have to remove the wiring from the layout to the controller at the outputs, install wires from the programming track, do the address, and then restore the wiring to the layout.

By the way, once the address is input to the QSI's, are you ensuring that your CV29 values are correct?  If you have any long addresses, you must immediately set CV29 to "38" in order to activate that new longer address.  Also, I have learned that you must pick up your throttle, dial in the new address after CV29 is set correctly, and then click the encoder to actually call up the loco, itself.  The address is there, and recognized, but the decoder is still in an anaesthetic fog...it won't make any sounds, light, or action until you physically acquire the loco.  Don't expect any activity just by powering up the track!

Same goes for the QSI's, sometimes, when the track has been shut down or the locos removed from the track for any length of time.  I find that my J1, especially, will do squat when I return it to the layout after an absence.  Then, as soon as I dial in its address, and click the encoder on the throttle (DT 400, so yours may not have encoders), that is the signal to the decoder to wake up.  Works every time.

I hope this helps to solve some riddles for you.

[claycts]

  Program it in ops mode, that always works. You can set everything in ops mode, even the address. If you have the real QSI manual it even has the steps to program the long address in ops mode, yo have to use the offset CVs to get there. Another trick that might work is make sure the thing is muted or in shutdown before moving to the program track.

 The only other option is to get a program track booster. Here things are not so clear - the Tony'sone works with BLI, but there are reports of it not workign with Tsunami. The Soundtraxx PTB seems to work with all of them. The whole thing seems like a bad desig to me, needing 'help' to program the decoders, although I've had no problems with my Zephyr.

                                     --Randy

Will try that.

In the instruction for the Gen #1 it says that you will need more power. In the Mike that I just got it programed with no problem on the Program track. You figure it I can not.

Gave up on the Genesis Challenger ordered a Soundtraxx for it.

 

[claycts]

Why not the DT400?  It's all I have, and therefore all I use.  I can program on the main (except for addresses) with the DB150, and I do it in Ops Mode.

What, specifically, is your intent with the Hudson?  New address, restore old address, program CV's for acceleration and deceleration, for volume, what?

All of the above. The problem is I have 4 of these things now (Ebay) and could live with (1) but the other (3) need to be done.

[rrinker]

  Program it in ops mode, that always works. You can set everything in ops mode, even the address. If you have the real QSI manual it even has the steps to program the long address in ops mode, yo have to use the offset CVs to get there. Another trick that might work is make sure the thing is muted or in shutdown before moving to the program track.

 The only other option is to get a program track booster. Here things are not so clear - the Tony'sone works with BLI, but there are reports of it not workign with Tsunami. The Soundtraxx PTB seems to work with all of them. The whole thing seems like a bad desig to me, needing 'help' to program the decoders, although I've had no problems with my Zephyr.

                                     --Randy

[selector]

Why not the DT400?  It's all I have, and therefore all I use.  I can program on the main (except for addresses) with the DB150, and I do it in Ops Mode.

What, specifically, is your intent with the Hudson?  New address, restore old address, program CV's for acceleration and deceleration, for volume, what?

[claycts]

Who is using a Power booster to program a BLI?

Decoder pro can not read the 1st Generatioin Hudson at all. BLI says not enough power in the Program track off the DCS100.

I am trying to AVOID using the DT400 to do the job. I have had to reset the Hudson after trying all modes on Decoder Pro.

Simple HELP!