|
I need help with accessing the programming track, which previously worked perfectly, but no longer.? For some reason the program will no longer correctly read values for the CVs when the loco is on the programming track.? It now reads 123 as the value for each and every CV.? Yet my NCE controller does correctly read the values.? Maybe I have something set up wrong?
I am open to suggestions. I tried searching for a related topic, but found nothing.? But then I am not good with key words. |
|
Norman, What version of Jmri?? Your symptom points to Preferences - Defaults being set to Internal. Jmri? 4.10 had a problem automatically doing this and not telling you. It continued into 4.12. I understand 4.14 due in a few days has this fixed. In the meantime, go to Edit-> Preferences -> Defaults and change anything set on Internal to your correct System. Save changes (lower left corner) and restart Jmri. Tom Wilson Colorado Springs, CO On Sat, Dec 22, 2018, 12:51 PM Norman Beveridge via Groups.Io <norman.beveridge=[email protected] wrote: I need help with accessing the programming track, which previously worked perfectly, but no longer.? For some reason the program will no longer correctly read values for the CVs when the loco is on the programming track.? It now reads 123 as the value for each and every CV.? Yet my NCE controller does correctly read the values.? Maybe I have something set up wrong? |
|
Go to your preferences and check your defaults tab, most likely have changed to internal. Change back to NCE.
The update JMRI to 4.14 when it is released, hopefully in the next day or two. -- Peter Ulvestad JMRI Users Group Moderator - ( ) Tam Valley Group Moderator - ( ) Sprog-DCC Group Moderator - ( ) Edmonton Model Railroad Association - |
|
123 is the key to the question.
toggle quoted message
Show quoted text
If you get "Found mfg 123 (Masoth Electronic, GMBH) version 123; no such decoder defined.", and/or all CVs return a value of 123 and long address 15,227 it is 100% certain that you cannot communicate with the decoder and that one of two possibilities have happened: 1) Preferences->Defaults has Service Programmer (and possibly other items) set to Infernal. 2) Preferences->Connections has System Connection set to Simulator. Possibility (1) is the most likely. It would most likely have occurred due to a previous failure to open a connection. If there is no alternative to Infernal, you currently have a problem with the connection to your DCC system and you need to resolve the connection problem before proceeding. If an alternative is available select that, restart JMRI and try again. Warning, the Infernal problem can happen again in the future if you have any connection problems. See comments at: /g/jmriusers/message/153294 This will be fixed in JMRI V4.14 -- Dave in Australia On 23 Dec 2018, at 6:51 AM, Norman Beveridge via Groups.Io <norman.beveridge@...> wrote: |
Peter Ulvestad