For some reason members (like me or Frank, or you) are not permitted to modify the Files section in any way. Can't upload files or even create folders. Seems very counterproductive. Not sure what the

Thank you TCC!

Frank, Does your decoder look similar to this one? Peteski

Frank, this is an OEM version of QSI Revolution decoder made for Walthers. It was used in the N Scale 2-8-8-2 loco and also in some H0 locos. Where did you find that decoder? I could use couple more m

You're welcome Frank -- I'm glad I was able to help out. Peteski

Morgan, Your questions about the verbal readback and acknowledgment features are answered in the QSI decoder manual. The one I have is QSI_CompleteReferenceManualForAllDecoders_V5_2_0.pdf Those featur

What does that mean? I never "logged onto" any decoder. Pe

Morgan, I just uploaded the manual I quoted to the Group's Files section, only to realize that it was already there under slightly different name. You can download that manual following this link http

Well Morgan, the trade-off between simplicity and functionality in sound decoders is that the better sound decoders are complex in order to maximize the sound fidelity. Think of the QSI, ESU, and ZIMO

If that is the case, IMO it is a strange name of the feature. That would mean a bi-directional communication between the decoder and command station. That would be similar to RailComPlus, a protocol a

Morgan, We agree! OSI is one of the more complex (and also feature-rich, and very configurable) decoders out there. Similar to ESU or ZIMO. There are less-complex (and simpler to program and understan

The horn/whistle on F2 conundrum is not really all that confusing if you understand American DCC. For whatever reason American DCC manufacturers decided that F1 will be by default assigned to activati

MOrgan, I really thing you are too worried about CVs (and how many CVs there are in some specific decoder)., CVs are just registers that retains configuration settings. In the days of simple non-sound

No need to be sorry Morgan. I'm glad you are reading (and quoting the QSI manual). "Some DCC controllers have separate horn/whistle and bell buttons, in addition to Function Keys assigned to horn/whis

Morgan, I have a far-fetched idea about this problem. Please put the loco on a programming track and read the contents of CV35 and CV36. Let me know what they are. Make sure to give me the correct val

Morgan, The manual I use is also v 5.2.0. The function mapping in CV33 - 46 is specifically defined in the NMRA DCC standard, and it is the standard all decoders adhere to. CV35 is for F1 and is suppo

Morgan, Digitrax is not announcing the "latchign F2" problem because it is a bug, not a feature. They don't want the world to know they stuff is buggy. I've been doing DCC for quite some time, but thi

Morgan, I was not asking to "run" the loco using SPROG - just press F2 on its throttle to see how the whistle behaved. But that's now water under the bridge. The main thing is that the QSI decoder is

Morgan, "hate" is a strong word. I said that I dislike DIgitrax products. I reserve "hate" for other situations. I dislike it because it to me seems awkwardly designed, implemented, and it's difficult

Well Morgan, Um, if you did try using the SPROG (or any other brand DCC system) to test the F1, you would have quickly discovered that the decoder was functioning properly. As I mentioned, those who u