开云体育

  1. Jmriusers
  2. Topics

Locked ESU Decoders #esu-decoders

 

I am a beginner on JMRI and only a year into DCC, so please be patient.? I had a dealer install a LOK sound in a 10 yo Athearn Genesis.? It worked fine but when I got JMRI working I wanted to reduce volumes and alter accel/decel.? I put in it on a program track and made some changes (I repeat I'm a beginner).? Back on main, the engine runs OK, but no sounds, no lights, and occasional run-away.? DecoderPro says this can happen and not to worry "just" download stuff from LOK Sound and upload to JMRI.? Huh?
A few facts:
1. 18", 24 ga wire, loosely twisted to prog track
2. 2 yo NCE Power Pro, 5 amp
3. 10 yo Lenovo T520 w/ Windows 10

I am years behind you guys.? For now all I want to do is simple, easy, standard decoder programming with JMRI.??
Thanks
[email protected]
 

OPPSSS!? Power Pro.

What version JMRI ?

You should also state what version? LokSound decoder was installed by dealer for you.? V4, V5, Select? ?

Marc
 

V.4 of LokSound.? Installed by dealer late 2017.? Ran OK until I "reprogrammed" to tune speed and volume

latest version of JRMI and JAVA (downloaded in past month)


-----------------------------------------

From: forfoum@...
To: [email protected]
Cc:
Sent: Wednesday December 4 2019 7:02:27PM
Subject: Re: [jmriusers] ESU Decoders #esudecoder

OPPSSS!? Power Pro.

What version JMRI ?

You should also state what version? LokSound decoder was installed by dealer for you.? V4, V5, Select? ?

Marc
 

Do a reset on the decoder.
You can't reprogram an ESU decoder with JMRI/DP, you can only change CVs.
Go over to the LokSound group on Groups.io, join, look in the files section for
a list of folks who will help out, it is in Word and pdf., you should find
someone there somewhat close to you, hopefully.

John

---------- Original Message ----------
From: Dan in NC <dkoenigshofer@...>
Date: December 4, 2019 at 7:21 PM




V.4 of LokSound. Installed by dealer late 2017. Ran OK until I
"reprogrammed" to tune speed and volume

latest version of JRMI and JAVA (downloaded in past month)

-----------------------------------------From: forfoum@...
To: [email protected]
Cc:
Sent: Wednesday December 4 2019 7:02:27PM
Subject: Re: [jmriusers] ESU Decoders #esudecoder

OPPSSS! Power Pro.

What version JMRI ?

You should also state what version LokSound decoder was installed by
dealer for you. V4, V5, Select ?

Marc

Links:
------
[1] /g/jmriusers/message/166661
[2]
mailto:[email protected]?subject=Re:%20Re%3A%20%5Bjmriusers%5D%20ESU%20Decoders%20%23esudecoder
[3]
mailto:forfoum@...?subject=Private:%20Re:%20Re%3A%20%5Bjmriusers%5D%20ESU%20Decoders%20%23esudecoder
[4] /mt/66587369/3891993
[5] /g/jmriusers/post
[6] /mk?hashtag=esudecoder&subid=7104874
[7] /g/jmriusers/editsub/3891993
[8] mailto:[email protected]
[9] /g/jmriusers/leave/defanged
 

开云体育

Dan,

On 5 Dec 2019, at 12:21 PM, Dan in NC <dkoenigshofer@...> wrote:

V.4 of LokSound.? Installed by dealer late 2017.? Ran OK until I "reprogrammed" to tune speed and volume

See instructions below.

latest version of JRMI and JAVA (downloaded in past month)

That's not helpful. The latest Production Version is 4.16 and the latest Test Version is 4.17.6. Please be more specific.

Your NCE setup is fine. It's very similar to what I use and I do all the JMRI development work for LokSound V4 and 5.

(Also, I'm aware that you are probably new to this list but when asking a new question, you must start a New Topic (web version) or if using email a fresh email to "[email protected]". Replying to an existing topic and asking a new question is what is called thread-hijacking and and causes lots of problems and confusion for those trying to help you, or just simply follow questions and answers.

Programming Decoders

Reading the full decoder is essential, particularly with ESU decoders where there are no "standard defaults". Each sound project has its own "factory defaults". All ESU sound decoders are manufactured effectively blank. When a Sound project is loaded to the decoder (using LokProgrammer software) part of the procedure is to write a new set of "factory defaults".

Because of a known (but as yet unresolved) race condition with certain decoder settings variables in JMRI code:

1) Use "Read Full Sheet" on the CVs pane instead of "Read All Sheets". It is less likely to cause errors when reading a decoder with lots of CVs.
Once finished, some may be missed (displayed in red). Use "Read Changes on Sheet" as many times as needed until no red items remain.
(Hint: Click on the Status column in the CVs pane until you see a down arrow. All the Red items will then be at the top.)

2) After you make changes on a programming sheet, don't use Write/Read changes on that programming sheet. Instead, switch to the CVs pane and use Write/Read changes on (the CVs) sheet. The result is the same but it will never trigger the race condition.

You'll also see a number of messages in the JMRI System Log like this:
"ERROR - Variable=xxxxxx; Busy goes false with state IDLE"

Ignore these as they don't indicate a real error, we'll fix the problem in a later JMRI release.

Dave in Australia







?
 

开云体育

John,

On 5 Dec 2019, at 12:50 PM, John <jonie41@...> wrote:

Do a reset on the decoder.

Correct advice.

You can't reprogram an ESU decoder with JMRI/DP, you can only change CVs.
Go over to the LokSound group on , join, look in the files section for
a list of folks who will help out, it is in Word and pdf., you should find
someone there somewhat close to you, hopefully.

Incorrect and misleading advice. You can program ESU decoders with JMRI DecoderPro, you just can't load new Sound Project files.

You must follow correct procedures for ESU decoders.

Programming ESU Decoders

You must use New Loco->Read Type from Decoder to allow JMRI to pick the correct definition file. Don't guess.

Reading the full decoder is essential, particularly with ESU decoders where there are no "standard defaults". Each sound project has its own "factory defaults". All ESU sound decoders are manufactured effectively blank. When a Sound project is loaded to the decoder (using LokProgrammer software) part of the procedure is to write a new set of "factory defaults".

Because of a known (but as yet unresolved) race condition with certain decoder settings variables in JMRI code:

1) Use "Read Full Sheet" on the CVs pane instead of "Read All Sheets". It is less likely to cause errors when reading a decoder with lots of CVs.
Once finished, some may be missed (displayed in red). Use "Read Changes on Sheet" as many times as needed until no red items remain.
(Hint: Click on the Status column in the CVs pane until you see a down arrow. All the Red items will then be at the top.)

2) After you make changes on a programming sheet, don't use Write/Read changes on that programming sheet. Instead, switch to the CVs pane and use Write/Read changes on (the CVs) sheet. The result is the same but it will never trigger the race condition.

You'll also see a number of messages in the JMRI System Log like this:
"ERROR - Variable=xxxxxx; Busy goes false with state IDLE"

Ignore these as they don't indicate a real error, we'll fix the problem in a later JMRI release.

Dave in Australia
[email protected]
 

Should he first RESET the decoder to default before the " READ FULL SHEET (CV Tab)? " ? ?

At this point, since he did write out values when he tried to change CV's for speed and volume, we do not know what he wrote out:? full sheet or all sheets
but clearly it was mre than a few CV's that got changed, no ?.

Marc
 

开云体育

Marc,

On 5 Dec 2019, at 1:42 PM, forfoum@... wrote:

Should he first RESET the decoder to default before the " READ FULL SHEET (CV Tab)? " ? ?

At this point, since he did write out values when he tried to change CV's for speed and volume, we do not know what he wrote out:? full sheet or all sheets
but clearly it was mre than a few CV's that got changed, no ?.

Thanks. Should have mentioned that...

Dan, the old advice about needing to get a LokProgrammer CV Export file should be further modified. Since ESU made changes to the default write settings in LokProgrammer, the situation of a Reset causing problems is very remote. I need to modify that documentation but can't find enough hours in the day...

Dave in Australia

1 - 8 of 8