¿ªÔÆÌåÓýTim, It seems I can write to them OK, but reading what's there in the first place is a challenge.? I'm doing read full sheet on the CV pane followed by multiple read changes on sheet to clear the red tabs, but after about 40 "read changes" tries on a Paragon 2 loco it went haywire.? I only rescued it by downloading individual CV values from the BLI technical reference and the operators manual supplied with the loco, then did a write full sheet (also on the CV pane) successfully.? Probably didn't get exact values for some CVs, which is what I'm trying to do in the first place.? My info: Please update to JMRI 4.16 (at least), preferably 4.17.4 (as it It fixes a significant issue in 4.16). A lot of water under the bridge since 4.14. I think you have done so, but check that you have followed the recommended procedure below exactly. (In particular, sort by status descending and do your retries on the CVs pane, not other panes/tabs.) If you find the same CVs keep appearing in red at the top of the "sorted by status descending " list, we need to know what they are as they may be CVs not supported by your particular model variant (we need to know the exact model as well). We can then change the definition files to exclude them if they are inapplicable. Dave in Australia Reading Decoder CVs 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 may 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. |
