Rob and John,
On 24 Aug 2019, at 4:01 AM, John Griffin <johng.sst@...> wrote:
The general procedure is to select new locomotive, identify the decoder (or if you know the decoder just select it). Once identified switch to the CVs sheet and read full sheet. However, You haven't given us any information on the decoder type, your system, anything. The more information you supply, the more likely we can find a solution to your problem.
Asking JMRI to "Read Type from Decoder" should always be the first step. Selecting a model because you think that's the model you have is a potential cause of problems.
Reading the full decoder is essential (particularly with ESU decoders where there are no "standard defaults"). For other brands/models the defaults information stored in JMRI is usually based on supplied documentation and may not be correct.
Because of a known (but as yet unresolved) race condition with certain decoder settings variables in JMRI code:
1) Use "Read Full Sheet" on the CVs pane instead of "Read All Sheets". It is less likely to cause errors when reading a decoder with lots of CVs.
Once finished, some may be missed (displayed in red). Use "Read Changes on Sheet" as many times as needed until no red items remain.
(Hint: Click on the Status column in the CVs pane until you see a down arrow. All the Red items will then be at the top.)
2) After you make changes on a programming sheet, better not to Write/Read changes on that programming sheet. Instead, switch to the CVs pane and use Write/Read changes on (the CVs) sheet. The result is the same but it will never trigger the race condition.
(You may see a number of messages in the JMRI System Log like this:
"ERROR - Variable=xxxxxx; Busy goes false with state IDLE". Ignore these as they don't indicate a real error, we'll fix the problem in a later JMRI release.)
Dave in Australia
