I have a Bachmann 2-6-6-2 that I purchased used on eBay several years ago which the previous owner installed a Loksound direct decoder. This locomotive has been working great until today. I put it on the programing track to record the settings into JMRI and to increase the sound levels. After putting it back on the layout the locomotive will not move. It will sound the bell and whistle but won't move.
Any advice or idea what I did wrong?
Chris
Chris,
It's possible that you inadvertently changed the default address for your decoder. Try operating it on address "3" to see if it moves. You can also check which "active address" your locomotive is set to by clicking on the Basic tab in your locomotive's settings in Decoder Pro.
Tom
https://tstage9.wixsite.com/nyc-modeling
Time...It marches on...without ever turning around to see if anyone is even keeping in step.
Most of my locos have Lok sound decoders. I had a very similar problem. I realized that I inadvertently programmed cv 62 (can't remember what it does) when I meant to program cv 63 (master volume). I'd check out cv 62. just A personal experience, could be something else.
JJF
Prototypically modeling the Great Northern in Minnesota with just a hint of freelancing.
Yesterday is History.
Tomorrow is a Mystery.
But today is a Gift, that is why it is called the Present.
tstage Chris, It's possible that you inadvertently changed the default address for your decoder. Try operating it on address "3" to see if it moves. You can also check which "active address" your locomotive is set to by clicking on the Basic tab in your locomotive's settings in Decoder Pro. Tom
If he can play the bell and whistle, he's obviously accesed the correct address.
Verify all your functions (except F8) are turned off. You may have accidentally activated a brake or Full Throttle feature that will prevent the engine from moving.
Mark.
¡ uʍop ǝpısdn sı ǝɹnʇɐuƃıs ʎɯ 'dlǝɥ
Mark has a good point. You may have activated the independent throttle. Check functions 9 and 10. If you can, check your functions List and see what is active.
Mark R. tstage Chris, It's possible that you inadvertently changed the default address for your decoder. Try operating it on address "3" to see if it moves. You can also check which "active address" your locomotive is set to by clicking on the Basic tab in your locomotive's settings in Decoder Pro. Tom If he can play the bell and whistle, he's obviously accesed the correct address.
I could be dead wrong but I seem to recall that if a decoder loses its long address on at least some DCC systems, the lights (and sound) will respond to its long address which is still stored in the command station memory. In that case, the loco will respond to its short address on the throttle and move.
If I am wrong, it is Tom's fault.
Rich
Alton Junction
I would like to thank everyone for their replies. I checked all of the functions and 4,5,6,7 were all on. Once I turned off #4 the locomotive started responding.
Interesting that a function key on the throttle would prevent the loco from moving until that function key is toggled off. Seems kinda pointless, but whatever.
cscannon222 I would like to thank everyone for their replies. I checked all of the functions and 4,5,6,7 were all on. Once I turned off #4 the locomotive started responding. Chris
Nice that turning off those functions worked for you.
Would be nicer to know what function 4 was controlling. Some folks re-map the functions, so whatever your function 4 is/was might be somewhere else on another decoder.
maxmanWould be nicer to know what function 4 was controlling.
Function 4 is the dynamic brake. I juggle with primarily three different mfg. sound decoders and it can be a pain.
One of my personal frustrations appeared in the form of two "identical" WOW sound decoders from TCS. I installed them in a pair of F7 A and B units.
After some minimal programming I was giving them a "run-in" period and after a few laps noticed the B unit dragging its locked wheels.
Setting the throttle to zero and restarting both units rolled away just fine. Two minutes later the B unit's wheels were not turning again. I did a factory reset on both engines and ran them on address three.
This time while running the pair around I finally noticed some electronic "chirping" sound coming from the B unit
As it turns out there is an "alerter" feature I wasn't aware of. Why this was ON by default on one decoder but not the other is not understood by me. I finally dug into the TCS documentation to figure out how to disable the silly thing. When you hear the beeping you have some predetermined time to press yet another function button to "acknowledge" and keep your train from a full-service brake application.
Here's a thread about how to keep track of oddball functions.
http://cs.trains.com/mrr/f/744/t/264198.aspx
"Remapping" all my various decoder functions is on a list of far-away projects on my "to-do" list.
Good Luck, Ed
Speaking of function keys performing different functions, I recently completed a project documenting the function key for the Mars light on my locomotives.
Sixteen of my diesel locomotives have a Mars light. Five use F12, four use F1, four use F5, two use F7, and one uses F6. Go figure.
richhotrainSixteen of my diesel locomotives have a Mars light. Five use F12, four use F1, four use F5, two use F7, and one uses F6. Go figure.
Overmod richhotrain Sixteen of my diesel locomotives have a Mars light. Five use F12, four use F1, four use F5, two use F7, and one uses F6. Go figure. Why on earth wouldn't you go ahead and list them here?
richhotrain Sixteen of my diesel locomotives have a Mars light. Five use F12, four use F1, four use F5, two use F7, and one uses F6. Go figure.
Why on earth wouldn't you go ahead and list them here?
richhotrainJust to taunt you, Overmod!
Now can you please write up the results of your research for the rest of the community?
Yes, I know it's a diversion, and yes, I know it doesn't address the F4 question. But we've had quite a bit of confusion over how the Mars lights are implemented recently...
Overmod richhotrain Just to taunt you, Overmod! Well you did it, it worked, I threw my lunch across the room in a snit and forgetfully stamped my bad foot. Now can you please write up the results of your research for the rest of the community?
richhotrain Just to taunt you, Overmod!
Well you did it, it worked, I threw my lunch across the room in a snit and forgetfully stamped my bad foot.
I would think that the answer would be obvious. Because I was simply responding to the revelation that the F4 key would prevent the loco from moving after braking unless and until F4 was pressed once again. F4? Who knew?
So, my only point in responding was to point out that different decoders use the F-keys differently. I saw no point in listing each decoder since that was not the central issue of the thread.
But here goes.
Still would like to know what F4 did on the OP's loco.
That might be the default for dynamic brake, but he said the loco was puchased from someone else. That someone may have remapped the functions.
And why would a 2-6-6-2 have a dynamic brake in the first place?
I see in the linked topic that some people are thinking of writing CV's down on cards.
Here's what I'm doing, at least for now:
When I'm going to program a new locomotive, I first read and write down the CV's I am likely to be changing: 29, 17, 18, 3, 4 and sound level. The basics, to me.
I then change them to what I want. I then write that down.
The above goes into a manila folder, for each locomotive. Along with the instruction sheet that came with it. And any other notes and comments about that locomotive.
When an engineer is assigned a locomotive(s), he (me) is expected to familiarize himself with the equipment he will be using. For example, one set of E's has a function for cooling fan sound--only ones like that I've got.
Early on, I found it easier to read my notes if I used a standard format, typed it in and printed and "foldered" it. Recently I realized I might as well save that document on the computer--can't hurt and easier to re-do the folder sheet.
I got into doing the above when I wanted to do a real speed curve for a decoder that had a "keep alive". Having been told that I couldn't read the CV's on this kind of setup, I wrote ALL the numbers down.
Seemed like a good idea, so I kept doing it for everything, including decoder equipped passenger cars.
Ed