This email is being sent to JMRI designers and to the DCC++ section of Train board. I have an issue program page 1 Configuration Variables (CVs). I am using JMRI software and DCC++ EX hardware. I try to program two locomotives. I try programming diesel locomotive with a soundtraxx Econami Part # 882004 and stream locomotive with a soundtraxx Trunami2 Part # 884001. First the Econami decoder: 1.) Could not program page 1 CVs with JMRI software and DCC++ hardware. 2.) Put engine on my main track that is power with MRC system. 3.) Changed the valve CV 31 to 16 and the valve of CV 32 to 1. 4.) Changed valves of page 1 CVs easily on my main track. 5.) Put engine back on program track control with JMRI and DCC++ EX. 6.) Changed valves of page 1 CVs easily on programming track now. 7.) Put engine back on main track. 8.) Changed CV31 and CV32 back to default valves. 9.) Put engine back on program track. 10.) Could not change page 1 CVs. 11.) I went back and forth many times with the same results. Second the Tsunami2 decoder: 1.) Could not program page 1 CVs with JMRI software and DCC++ hardware. 2.) Put engine on my main track that is power with MRC system. 3.) Changed the valve CV 31 to 16 and the valve of CV 32 to 1. 4.) Changed valves of page 1 CVs easily on my main track. 5.) Put engine back on program track control with JMRI and DCC++ EX. 6.) Still could not changed valves of page 1 CVs on programming track now. 7.) Put engine back on main track. 8.) Reset the valve CV 31 to 16 and the valve of CV 32 to 1. 9.) Put engine back on program track. 10.) Still could not change page 1 CVs. 11.) I went back and forth many times with the same results. I could always change the valves of the page 1 CVs on my main line track on my layout as long as I put the correct vales in CV 31 and CV 32. The page 1 CVs I changed were 1.407 (Forward Whistle Signal), 1.408 (Reverse Whistle Signal) and 1.409 (Stop Whistle Signal). Both engine acted correctly to all changes made on my layout track.
Interesting that the issue was opened in 2018. It looks like the fix should be included in JMRI 4.25.1. https://github.com/JMRI/JMRI/issues/4716 https://github.com/JMRI/JMRI/milestone/107
