Bob,
On 3 Jan 2020, at 4:23 PM, Bob P <comm4rgp@...> wrote:
Can read and write most pages, but on new Tsunami 2 and Econami programming, the Function Map page appears stuck on writing the first change, of which all appear to be indexed CVs. Doesn't matter which function is changed, it appears unresponsive. A new topic which I'll search for guidance.
This almost certainly indicates you have an NCE Power Pro system.
Power Pro CV Limitations
==================
Due to a firmware issue, the NCE Power Pro is:
- Capable of reading values correctly from any CV in the range 1-1024** inclusive in Program Track mode.
- Incapable of writing values correctly to any CV>256 in Program Track mode. The wrong CV is written. For example, a write attempt to CV275 will instead reprogram CV19!
- Capable of writing values correctly from any CV in the range 1-1024** inclusive in Program on Main mode.
** If using the Pro Cab, you can only program CVs in the range 1-999 inclusive. You need software like JMRI DecoderPro to access the full 1-1024 range.
Notes:
1) This is unrelated to the concept of indexed CVs. Your NCE system is unaware of this concept, everything is just a CV. The indexed concept only exists in the decoder (and JMRI DecoderPro if you use it).
2) JMRI DecoderPro will not attempt to write to any CV>256 in Program Track mode. It protects your decoder from CV corruption.
3) JMRI DecoderPro is able to program CVs>256 in Program Track mode for ESU decoders only. This is because ESU has provided an in-decoder workaround to deal with DCC systems having this problem and JMRI automatically uses this workaround when needed.
4) The original Tsunami decoders are unaffected by this problem. For Tsunami2 and Econami, any attempt to write CVs in Program Track Mode on the Function Map, Sound, Alt Sound Levels, and DDE panes will be blocked by JMRI, but you will need to restart JMRI to continue (I'd like to fix that but it's not easy and I don't have the time).
5) The JMRI workaround with affected decoders is to read and save the roster entry in Program Track, close and reopen in Program on Main mode when changing affected panes.
6) This problem has nothing to do with PTB-100 or any programming track booster. That is related to programming track hardware limitations and not related to the CV>256 firmware issue. It is an unrelated separate question.
