WTF am I doing wrong when programming ESU Loksound Select Micros on m SD40-2s

[Ed Kapuscinski]

Ok, I'm at a loss guys.

I just took delivery of my sound equipped SD40-2 fleet, and I'm having a hell of a time trying to program them.

I've got my PR3 hooked up directly to the programming track with a power supply feeding it (to get the necessary juice).

When I tell JMRI to identify the decoder I get this:

[ Guests cannot view attachments ]

It reads the decoder manufacturer and version as 123.

But I know it's a Loksound Select Micro, so I choose that programmer and open it up.

In there, when I read the basics back from the decoder, I get.

[ Guests cannot view attachments ]

Then, on the list of all CVs, when I read them, I ALSO get 123.

[ Guests cannot view attachments ]

I get the same result with all four of them, so I figure it's something in my setup not them.

What am I doing wrong?

[mu26aeh]

I'm not sure JMRI is set up yet for those decoders.  But I was able to at least get the road numbers changed on mine.

[Bendtracker1]

Ed I don't think you can program those decoders with JMRI like Adam stated?
That is the same kind of garble I got when I was playing with one a few months ago.

I was able to program the basic stuff like the address with my Digitrax DT402D fine, but not much else.
I was told you needed an ESU programmer.

[mu26aeh]

"I've got my PR3 hooked up directly to the programming track with a power supply feeding it (to get the necessary juice)."

What do you mean to get the necessary juice ?  You don't mean as a booster do you , IMRC/ESU says you don't need one.

http://www.intermountain-railway.com/customerservice/instructions/N-SD40-2-Insert-Dec-2016.pdf

[John]

Ed .. found this on JMRI

Dave Heap
Jul 5
As far as CV programming is concerned, the latest version (V4.7.7) of JMRI is just as capable as the latest LokProgrammer (V4.5.3).

LokProgrammer is very much faster at Read All Sheets and Write All Sheets than JMRI.
JMRI can Read and Write single sheets or Variables/CVs. Lokprogrammer cannot
JMRI can Program on Main. LokProgrammer cannot.
JMRI can read CV export lists from LokProgrammer. LokProgrammer cannot read any CV export lists.
LokProgrammer can write new Sound Projects and rewrite project default CV settings. JMRI cannot do either.
JMRI can correctly identify the decoder type of any fourth generation ESU decoder.
You must "Read Type from decoder" in New Loco and use the chosen definition.
You MUST Read Sheet before making any changes to ESU decoders. Every sound project has different default values.


If you are programming speed tables, ESU interprets speed tables slightly differently. You ned to use the correct ESU definition and read the instructions on the Speed table pane carefully. Program Track or Program on main work equally well for Speed Tables (or any other pane, but you must Read Sheet first for the complex panes where you are not changing everything).
I added the last ESU updates only a few days ago and they are in V4.7.7.
I have a good working relationship with Matthew Herman of ESU LLC. The latest ESU firmware incorporates a change I negotiated on behalf of NCE system users for full compatibility with NCE Advanced Consisting.
I have put a lot of development time into adding ESU-specific features to JMRI.

--
Dave in Australia

[nstars]

I have no problem with programmign Loksound V4.0 and Loksound Select decoders with JMRI. Reading CV's with JMIR will indeed take much longer (about half an hour).

Marc

[jdcolombo]

Ed, what version of JMRI are you using?

I've got no problem with JMRI 4.8 identifying the decoder as an ESU Loksound, though I do have to select "LokSound Select" manually.  My setup reads all the CV's just fine.

PC -> PR3 -> Chief command station

John C.

[Ed Kapuscinski]

Ed, what version of JMRI are you using?

I've got no problem with JMRI 4.8 identifying the decoder as an ESU Loksound, though I do have to select "LokSound Select" manually.  My setup reads all the CV's just fine.

PC -> PR3 -> Chief command station

John C.

I had just downloaded 4.8.

Are you programming using the outputs on the PR3, or the ones from your DCS200?

[jdcolombo]

I had just downloaded 4.8.

Are you programming using the outputs on the PR3, or the ones from your DCS200?

The DCS.  Computer w/JMRI, hooked to PR3 via USB, PR3 hooked to Chief via Loconet cable, programming track wired to Chief.

John C.

[Ed Kapuscinski]

The DCS.  Computer w/JMRI, hooked to PR3 via USB, PR3 hooked to Chief via Loconet cable, programming track wired to Chief.

John C.

That's wild. That was the first setup I tried too, and all I got were the 123s.

Maybe I'll try updating JMRI again when I get back from Vegas.

[central.vermont]

Maybe I'll try updating JMRI again when I get back from Vegas.

Remember Ed, what happens in Vegas stays in Vegas!!

Jon

[jpwisc]

That's wild. That was the first setup I tried too, and all I got were the 123s.

Maybe I'll try updating JMRI again when I get back from Vegas.

Why didn’t you say you were in town?!?

[Ed Kapuscinski]

Why didn’t you say you were in town?!?

I'm in town!

But generally because it's a decently packed schedule with my conference attendance and presenetation.

[bman]

While mine are not the sound equipped Dash 2's Ed, down at the club on our DCC running the latest version of JMRI I was able to select any one of the many ESU decoders.  Of course I cheated as one of our members is involved in the JMRI project and had him watching over my shoulder. 

[Ed Kapuscinski]

Ok, turns out that some JMRI settings got jacked while doing the upgrades, and that was causing the 123 readbacks.

Fixed those, and things are working like a champ.

Next question, are you guys using the Micro Select or the Micro Select Direct programmers?

[ Guests cannot view attachments ]