I am sorry if this has been mentioned. Has the audio feed back been turned off? Seems everytime I read a BLI decoder the engine address changes and needs to be reset. But why I don't know. I have just learned to expect it and deal with it.
toggle quoted message
Show quoted text
On 9/13/2019 5:50 PM, Dave Heap wrote:
Tim,
On 14 Sep 2019, at 7:16 AM, Tim Lux <timlux33@...> wrote:
So Dave, should I continue to try reading all CVs when I get a new (non ESU) locomotive?
I always do.
I did ask you before whether the CV numbers that fail are:
- Consistently the same? Can indicate that the CV is not supported by your decoder.
- Random? Usually a sign of poor track contact or even a DCC programming hardware design deficiency.
I???m just concerned I???m somehow altering what???s in there (example getting wrong addresses, Vhigh values, CV 29 showing short address preference when it was running on long address, etc). All these things happened to me on a Paragon 2 centipede, hence my uncertainty and desire to find the ???always-works??? method of reading these.
The only time JMRI alters what's in a decoder is when it reads indexed CVs, in which case it has to set the index CV(s) before reading these special CVs. It shouldn't be changing Vhigh values, CV 29 etc.
Such occurrences would indicate problems with the design of either the decoder or the DCC programming hardware. Or possibly poor programming track conditions (dirty track/wheels , long connecting leads etc.) leading to spikes that corrupt the decoder contents.
Dave in Australia
