Re: beating up a the dead(?) horse: CV21/CV22 (and EasyDCC)
Jens Wulf \(WRF\) <jens.wulf@...>
toggle quoted message
Show quoted text
-----Original Message-----
From: ARRJERRY@... [mailto:ARRJERRY@...]
Sent: Friday, 27. February 2004 05:31
To: QSIndustries@...
Subject: Re: [QSIndustries] beating up a the dead(?) horse: CV21/CV22 (and EasyDCC)
remember I (jw) wrote, as P.S.:
Lets not confuse the QSI problem with other Advanced Consisting.
[..]
Advanced consisting is basic to DCC and we need to solve this problem.
[jw] yes agree. we need to. See my PS above. This post was *NOT* about the CV19
problem with the QSI decoders. And there's an issue. Ther's *NO* problem with
Cv21/Cv22 on QSI decoders. We should stop mixing these two issue.
/jw
From: ARRJERRY@... [mailto:ARRJERRY@...]
Sent: Friday, 27. February 2004 05:31
To: QSIndustries@...
Subject: Re: [QSIndustries] beating up a the dead(?) horse: CV21/CV22 (and EasyDCC)
remember I (jw) wrote, as P.S.:
PS: I have not tested the CV19 "coma" issue. I have just poweredyou wrote:
down all above mentioned decoders/locos and going to wake them
up (if they do) in about 24 hours.
Lets not confuse the QSI problem with other Advanced Consisting.
[..]
Advanced consisting is basic to DCC and we need to solve this problem.
[jw] yes agree. we need to. See my PS above. This post was *NOT* about the CV19
problem with the QSI decoders. And there's an issue. Ther's *NO* problem with
Cv21/Cv22 on QSI decoders. We should stop mixing these two issue.
/jw