I would scrap it and get one of the TCS WowSteam decoders. I like Loksound but their steam sound files are limited. If you are wanting to standardize on one brand, it does make sense to go with another Tsunami. I really like the motor-control of the TCS decoders. They are on par with Loksound.
Tom
https://tstage9.wixsite.com/nyc-modeling
Time...It marches on...without ever turning around to see if anyone is even keeping in step.
Ok, I got the decoder back - sort of. I can acquire it, and some of the sound effects work, namely bell, whistle and coupler crank. However, the speed is completely messed up, and I cannot get the engine to stop, once it is driving. I have tried several times to change (e.g. re-program) the speed table with various settings, using both the basic speed table as well as the advanced speed table settings. Same result, I can accelerate the engine, but never stop it. Changing direction works too.
Unless someone has some additional input or experience, this decoder goes out ...
I have one QSI (Atlas Trainamster) but I switched everything else out for Loksound. I like standardization. All my non-sound locos have TCS.
--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 that response, Randy. I will try those buttons to wake my decoder up. However, shouldn't the reset that I performed have addressed that issue already?
This decoder is a mystery. I am considering switching it out for a Soundtraxx, I already have two TSU 1100 and am happy with those. Maybe standardizing brings some advantages.
Could be in one of the many "disconnect" modes that Quantum decoders have - might even get chuffs but no motion as the throttle is advanced, unless it has a chuff cam. Multiple presses of F6 are the usual default for waking it up, F9 multipel taps switch it into the various modes. If you remapped functions they coudl eb anywhere, but a reset should fix that.
It could be the SPROG or the decoder. To eliminate the SPROG, reset a different decoder and see what happens to the address when you reprogram it. If the address is correct, it's not the SPROG and it's not THAT decoder. Kind of leaves you with one alternative, and that's a new decoder for the 2-6-0.
I have a Sunset Models 2-6-0 Mogul with a Quantum Sound Decoder.
I ran it recently via JMRI and Sprog3 Command Station, and played around with the function keys on my EngineDriver throttle. At some point certain functions stopped working, and the engine would no longer drive.
Since I had a roster in JMRI with the decoder information, I decided to reset the the decoder, which appeared to work fine, with no error messages, and the decoder appearing to provide proper feedback after rewriting each CV (e.g. engine was nudging forward after each write step).
I then reprogrammed the address, put it on the main track, and idle sound came on. However, the engine wouldn't budge, and none of the sound functions (e.g. bell, whistle, etc.) would work. I went back on the program track, making sure I have the correct address. When I read the address, it was not the one I had programmed it to. So I wrote it again, without error messages. Then I read it again, and it was different. Tried that several time, every time it came back with a (seemingly random) different address.
Did anyone have similar issues with Quantum decoders? My understanding is that with the Sprog3, I don't need a programming booster (and should not use one).