On Feb 6, 2020, at 20:26, Peter Ulvestad <ulvestad@...> wrote:

?Here is a copy and paste from a post by Dave Heap

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.

--
Peter Ulvestad

JMRI Users Group Moderator - ( )
Tam Valley Group Moderator - ( )
Sprog-DCC Group Moderator - ( )
Edmonton Model Railroad Association -

?

I have run into a very specific programming issue with Econami and Tsunami2 decoders:

NCE PowerhousePro
JMRI 4.17 or 4.19 (upgraded after I first had this issue. It did not have an effect)

I cannot write the page or write changes to the page "Function Map" while in Program Track programming. The first Function will turn red, the programming track will shut off and power will immediately return to the layout. The program will lock and the only way out is to Ctrl+Alt+Del JMRI and open it again. This is the only page in either of these definitions that I cannot write page or write changes to page. I can successfully read any page in Program Track programming. I can write the page or write changes to the "Function Map" page while in Ops programming. Please let me know if you need more information regarding this issue.

Micheal Farley
Bismarck, ND

?

Bob,

After a lot of interruptions a block of time allowed me to investigate at least some of what you have described.

Unfortunately, I am not able to duplicate what you are describing with your icons. You appear to be using custom icons which would make it difficult for us to just examine an uploaded copy of your panel xml file unless you also uploaded all of those icons.

Normally we request one to upload the panel into the "Files/Problems being worked on" folder and report back to the thread with a link to the new entry or at least a unique name that we can find to tie it to the message. Additional files in different folders adds some complexity to that effort. Not impossible, but extra bookkeeping is required at both your end and at ours.

But before going down that route, there is an "issue" that involves your custom signal icon file location. Please note that this issue may or may not have anything to do with the symptoms that you have described. It is also possible that you have developed a coping mechanism that enables you to do what we always recommend JMRI users to never do.

The first icon in your list is identified with this line:

<held url="program:resources/icons/_RJE/Signals/SearchErrorFlash.gif" degrees="0" scale="1.0">

Which indicates that your custom icon, and all the others listed, reside in a folder named _RJE/Signals and is a subfolder of the JMRI distribution folder. Everything in the distribution folder will get overwritten during the next version update.

It is strongly recommended that each user keep all custom files in a folder that does not get overwritten. Depending on how one uses those custom files the protective process can be as simple as creating a subfolder of one's JMRI user's folder with something like "resources/icons/_RJE/Signals/" in your case. If the custom files are to be shared then one might use something like a Dropbox location. Often there is some choice that fits one's needs but is in between these extremes.

Once that folder is defined, then the options and preferences dialogs within JMRI and the xml files saved will have replaced "program:" with "preference:" or with "profile:" or with "settings:" or maybe a more complicated explicit local hardware or network name. JMRI will then default to that folder location. Numerous other message threads on this list provide details. Save copies with different names early and often as you make modifications.

My apologies for this long digression.

It will be either late this evening or tomorrow before I can get back to trying to duplicate your symptoms.

Cliff