See instructions below.
That's not helpful. The latest Production Version is 4.16 and the latest Test Version is 4.17.6. Please be more specific.
Your NCE setup is fine. It's very similar to what I use and I do all the JMRI development work for LokSound V4 and 5.
(Also, I'm aware that you are probably new to this list but when asking a new question, you must start a New Topic (web version) or if using email a fresh email to "
[email protected]". Replying to an existing topic and asking a new question is what is called thread-hijacking and and causes lots of problems and confusion for those trying to help you, or just simply follow questions and answers.
Reading the full decoder is essential, particularly with ESU decoders where there are no "standard defaults". Each sound project has its own "factory defaults". All ESU sound decoders are manufactured effectively blank. When a Sound project is loaded to the decoder (using LokProgrammer software) part of the procedure is to write a new set of "factory defaults".
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, don't use 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'll also 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.
