If a CV has a configurable range of values from 0-90, and JMRI reads the set CV value as 110, what is the result? Is it ignored? Does the decoder perform the same as if the CV were set to its max, min?
Unknown, it could do anything. Treat it as max, treat is as unset, treat it as min, treat is as if it rolled over at 90 (so act like it was 20) or just cause some strange unexpected behavior.
Does the decoder documentation back up the fact that JMRI says 90 is th emex? JMRI isn't always right/ Some person created that decoder definition in JMRI, and they could have mistyped something. Or the valid range changed with a firmware update to the decoderand the JMRI definition is still based off the old one. Only way to know for sure is to read the actual decoder manual and see what the manufacturer says.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
I knew Randy would eventually chime in on this. Randy, you've always got the answer!! Thnx
This is actually related to that smoke thing I've made other posts about.
I did a hardware reset on the brand new P3 BLI S2. It had a minor derailment going thru a turnout and the circuit breaker tripped. After that just a small amount of smoke was present while stopped. Start moving, no smoke.
But then I observed the same problem on the P2 BLI T1 duplex pulling another train on the other track at the same time of the derailment. So just out of curiosity (today) I put it on the programing track and took a look at the CV values and saw that the CV value for the smoke heater while moving was 110, well beyond the range of 0-90. And for smoke while stopped it was 30 (default = 50). I did not change any of these deliberately (that I know of).
Anyway, I'll be testing these again shortly.
I used the CV values in the BLI Operator Guide.