TonyWalsham said:
Stanley.The facts are, the BELTROL R/C system can operate a DCC compliant QSI sound decoder. Therefore the BELTROL R/C is compatible with said QSI sound decoder. I am quite within my rights to say it is compatible even though I KNOW that term can be misleading to the newcomers.
I did not say it was COMPLIANT with DCC. That would be simply untrue.It is the use of misleading information by others to promote their “agendas” that I am trying to illustrate.
Illustration is fine but lets get the facts straight.
-
The QSI sound decoder is not DCC compliant. QSI only claims compatible. It is close to being compliant but to be compliant you need to pass the complete tests and not a subset of the tests. Hopefully their next chip will allow them to be fully compliant.
-
QSI supports multiple protocols. One is indeed DCC. A second is the Quantum DC reversal protocol.
-
It is the Quantum DC reversal protocol you are using. If indeed you are using the complete protocol and can control the full features then indeed you are within your rights to say you are fully compatible with the QSI sound decoder. If you are only using a subset of this QSI unique protocol then saying you are compatible is just as misleading as some of Lewis’s recent statements.
Indeed you are also correct that saying that your system can control some of the with features of the QSI DCC sound decoder. Implying in any way that you are doing anything related to DCC would be deceptive and I am glad read that you agree.
Lewis has indeed said some rather stupid things of late. I suspect he does not realize just how silly some of his statements are. Myself I think the Revolution is a good system and after his engineers make a few generations of improvements it likely will be a great system.
DCC is a set of specifications for a protocol. It is clearly possible to have hard to use systems that implement DCC and it is also just as clear that you can have easy to use systems that implement DCC. The user interface is not part of the DCC specification so any statement about how hard or easy it is to use DCC is a statement about a particular implementation and not a statement about DCC.
As another example you can have excellent motor control in a DCC decoder or terrible motor control in a DCC decoder. Motor control is not covered in the specification so any statement of DCC motor control is just as silly as a statement about how hard or easy it is to use DCC.
Unfortunately there are more then a few that confuse an implementation of DCC with the protocol specification. Lewis has unfortunately put his foot in his mouth by his misstatements about DCC. Hopefully more then Lewis can learn from this experience.
Stan Ames