The attached pdf file shows the steps and pictures from JMRI of the CV pane and DCC++ Traffic Monitor, which show how JMRI is reporting a read failure -- because it does not understand that the error in writing to CV204 is an expected result, when the value of CV201 is greater than 100. I would like some help in understanding whether the problem is something that should be fixed in a decoder definition file, or if it might require a programming change in JMRI. It could also be an issue with the decoder, or it could be user error. Here is further explanation and work-around on groups.io: https://groups.io/g/jmriusers/message/186411 The attached pdf file shows the steps and pictures from JMRI of the CV pane and DCC++ Traffic Monitor, which shows how JMRI is reporting a read failure -- because it does not understand that the error in writing to CV204 is an expected result, when the value of CV201 is greater than 100. Decoder model 1527 TCS WOW121 Diesel v4 on GEN-MB1 with KA2 Keep Alive Results are from JMRI 4.21.3 and DCC-EX 3.0.3. Same results on JMRI 4.19.. and DCC++ Classic. In the DCC-EX setup, I send the commands <D ACK LIMIT 75> and <1 PROG> [without brackets in JMRI]. The higher ACK LIMIT is helpful for my external current sensing setup. <1 PROG> turns on the power to the programming track, so that the Keep Alive remains charged. I updated to JMRI 4.21.3 to issue the ACK LIMIT command. See topic 'Update JMRI:' https://mstevetodd.com/enhancing-your-rpi-jmri
I have made some progress. I added some code to a test version of DCC++EX to avoid the error that causes JMRI to stop before completing the read of indexed 4 CV sounds. Will further advise on whether this becomes a standard feature with DCC++EX. My question for today is whether the status lines I'm seeing (while reading decoder) in JMRI 4.21.4 (Windows 10) are new in that version. I don't see them in 4.21.3 (RP3b), unless I have the current monitor open. I should probably update both versions to 4.21.5. The attached file has a couple of the JMRI panes, showing some indexed CV read errors and some lines captured from DCC++ Monitor.
