rrinker hobo9941 There's a little tiny gremlin in there. Well someone has to work the throttle, brakes, bell, and whistle. I expect there's two in there - someone has to fire it, too. --Randy
hobo9941 There's a little tiny gremlin in there.
There's a little tiny gremlin in there.
Well someone has to work the throttle, brakes, bell, and whistle. I expect there's two in there - someone has to fire it, too.
--Randy
So that is why some people get a mysterious derailment issue.... The little gremlins responsible for track upkeep and repair went on strike for better wages...
Ricky W.
HO scale Proto-freelancer.
My Railroad rules:
1: It's my railroad, my rules.
2: It's for having fun and enjoyment.
3: Any objections, consult above rules.
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Was forgetting...make it a habit of always dispatching locos after use.However,you don't have to if you are to use the same one the next time.When the adress blinks simply hit loco and go BUT do not type the adress again...you would then create the conflicting throttles situation you just had.Safest thing is to always dispatch adresses.
DCS51 manual page 38...quite simple to do.Do it for every adress you remember using with your Zephyr,it may save you eventual future headaches.
Well I seemed to have resolved the problem... thanks to some suggestions.. resetting the decoder didn't fix it... also I hooked up my n-scale decoder and got the "same" issue... it had looked like my test decoder was causing the problem... but I really didn't think so... Jacktal referred to stored memory issues... so I reassigned my HO scale decoder to another address (the one that it will be eventually when in the loco)... and the problem went away.... it ran and worked beautifully... seems like the "03" address originally assigned had some funky stuff in the programming .... so I then reassigned the address in my N-scale decoder and that worked fine also....
glad it wasn't any bad electronic issues... but Jacktal,,, one thing I couldn't find in my documentation was how to "erase" the stored memory you referred to...
Also... during all this I occasionally kept getting "FULL" messages which indicated I had maxed out my locos assigned... documentation said my dcs51 would purge this.. but didn't know how that happenned... so that the full story...thanks everyone for all the info... and problem is solved... joeg
Jacktal Was the adress used (in this case 03) dispatched from the command station after a previous use?Depending on the DCC set in use,locos have to be erased from the command station's memory so that past commands don't corrupt the newer ones.Failing to do this may result in the CS sending more than one set of instructions to the decoder,it being in a loco or not,this resulting in weird operation.I'm guessing this could be.......
Was the adress used (in this case 03) dispatched from the command station after a previous use?Depending on the DCC set in use,locos have to be erased from the command station's memory so that past commands don't corrupt the newer ones.Failing to do this may result in the CS sending more than one set of instructions to the decoder,it being in a loco or not,this resulting in weird operation.I'm guessing this could be.......
Yes, that was part of my problem too. Since I'm new to DCC it was hard to figure out that there were multiple issues at hand & what they were - not dispatching the locos from the throttles - and the decoders slowly failing, on two premium locos no less.
thanks Arto... If I can't solve the problem with resets I will contact Digitrax and see if they can shed some light... its possible that it may be bad... joeg
I had a similar problem with a BLI Paragon2 EMD E6A. It turns out the decoder was bad. Eventually the B unit started doing the same thing. BLI replaced both decoders N/C even though they were more than a year out of warranty. Nice to see some companies still stand behind their name and products even when they have no obligation to do so.
That is a possibility but the manual doesn't refer to it... I have a smaller new decoder available (still packaged up)... I'm going to hook that one up and see if the throttle reacts the same way as the other decoder... haven't had a chance to do this yet... I'll keep you posted... joeg
Is it possible that this is part of the testing that the decoder tester does? I don't have one of these, but perhaps it has some sort of test cycle that does exactly what you describe.
It takes an iron man to play with a toy iron horse.
The decoder isn't installed into a train.. it is wired to a Ulrich decoder tester.. and the tester is attached to the track... all functions work... but the "train" runs like its stopping at road crossings every few minutes... it does this if you keep the throttle at any position for any length of time... sound lights throttle/motor response are all good except for this pecular "running".. it is selected as "03". I haven't done a reset.. but will and I'll let you know... but I'm sure its a cv setting that I'm missing...
Make sure your wheels and track are clean. I have had strange things happen because of dirty track or wheels.
Normal procedure if there are issues is to do a decoder reset. Cycle track power and the loco should run on address 3.
Rich
If you ever fall over in public, pick yourself up and say “sorry it’s been a while since I inhabited a body.” And just walk away.
Didn't know exactly how to describe it... but I have a new digitrax sdh166d and I have it hooked up to a Ulrich decoder tester...before I install it into a loco... all seems to be working fine.. except when I throttle it to any speed and leave it there.. the loco runs for about 2-3 mins then it throttles down slowly, bell rings couple of times... and engine sounds go to idling... then maybe a steam blowoff... then it starts to pick up speed again.... I've been looking for a cv setting somewhere that would cause this.. but has me stumped. It doesn't act like a short circuit or programming problem.. it acts like its under a control that is causing the engine to run for a while.. then come to a stop... the start up again...
Is there a setting that causes the train to do occasional stops at crossings,,,etc... that what it sounds like its doing... any help would be appreciated... thanks
this is my first attemp to get a decoder installed and am a newbie at this... thanks joeg