LokSound Select HO Scale Onboard IM SD40-2

[davefoxx]

I downloaded the IM file, which is the same file number 73408 as from the ESU website.  I got the same results, including the sound slot 20 incorrectly getting the Brake Set/Release.  D'oh!

DFF

[RBrodzinsky]

Have you tried a different project?

[RBrodzinsky]

Out of curiosity, I downloaded the 73408 file this morning, and loaded into a brand new 73800 Select Mirco decoder. Now granted, the LP "converts" the project to the Micro version prior to writing to the decoder, but it shouldn't change any of the sound slot contents.  After loading the decoder, I used the LP's Drivers' Cab, and Drive Hold worked just as it should on the LokTester.  This shows the project on the web site is good (which I hadn't seen confirmed).

I am now wondering if there is something specifically wrong with the decoder in Dave's loco.

[davefoxx]

Yes, file number 73408 worked on my Atlas GP40-2.  It’s definitely not the sound file causing the problem.  But, interestingly, BOTH of my IM SD40-2s have the same result.  I don’t think it’s a bad decoder, instead there’s something with this series of decoders.

DFF

[davefoxx]

Out of curiosity, I pulled the shell off of one of the SD40-2s.  I pulled the decoder out, so I could get a good picture of it and figure out what it is.

Top:


Bottom:


DFF

[RBrodzinsky]

That is a standard LokSound decoder. There is no way to visually tell V4.0 vs Select (on the micros, they write either “4” or “S” on the shrink wrap).

There are two things which bother me in the second photo.  At the upper left, that tail of solder from the soldering that wraps up near the second hole in the left most column, and the tail of solder between the two soldering pads on the component in the upper right corner. I don’t have any of these to physically look at and compare, but there might be a bridge formed. Not sure what impact that would have.

[peteski]

That doesn't look like a solder bridge to me. It is light reflecting from the solder mask at the edge of a copper trace which runs diagonally between the solder pads (which appear to be connected by that trace anyway).

[davefoxx]

If it was a solder bridge, the decoder works (other than the Full Throttle features) even after my clumsy teardown to pull the decoder out.  Thankfully, the locomotive still works after I put it back together, and I didn't even have to reconsist it with the other SD40-2.   

DFF

[davefoxx]

Problem solved.  I now have the Full Throttle features working on an HO Scale Intermountain SD40-2, because:

1) I’m a moron; and

2) I neglected to write the sound files to the decoder.

I’m not sure why everything else seemed to work, unless those features were already onboard and I was merely tweaking the factory settings.  The second SD40-2 is on the programming track now and similarly being updated.

I wonder how many other locomotives I failed to update correctly.  This is embarrassing, but if it helps somebody else . . . feel free to bring on the facepalms.

DFF

[Jbub]

No facepalms from me. You had the best dcc minds on the forum looking at this and no one suggested to make sure the sound file wrote to the decoder.

[peteski]

No facepalms from me. You had the best dcc minds on the forum looking at this and no one suggested to make sure the sound file wrote to the decoder.

Oh boy, have you read the entire thread?    From post #3, that has been discussed. In post #12 Dave said that he even downloaded another sound file.  When he talks about downloading sound files, one expects him to install them onto the decoder!! They aren't much good sitting on the laptop running LokProgrammer! 

Or am I missing something here too?

[davefoxx]

@peteski,

Hey, don't blame @Jbub for my mistake.  I didn't realize there was the additional step and thought that "Write Decoder Data" took care of it.  Everything seemed to work on locomotives that I programmed prior to these SD40-2s, despite not hitting "Write Sound Data," including adding the Full Throttle features (unless I somehow dumb-lucked my way through that procedure).  Somebody explain that.  This stuff isn't necessarily intuitive for some of us, and there's no great instruction manual that I've found.

DFF

[peteski]

@peteski,

Hey, don't blame @Jbub for my mistake.  I didn't realize there was the additional step and thought that "Write Decoder Data" took care of it.  Everything seemed to work on locomotives that I programmed prior to these SD40-2s, despite not hitting "Write Sound Data," including adding the Full Throttle features (unless I somehow dumb-lucked my way through that procedure).  Somebody explain that.  This stuff isn't necessarily intuitive for some of us, and there's no great instruction manual that I've found.

DFF

Not really blaming anybody here. It seems to be just a misunderstanding.  I thought that you saying that you even downloaded different sound files, you actually installed them onto the decoder.  I also recall a mention (either here, or maybe in another thread about your ESU adventures). That writing a sound file to the decoder takes 20-30 minutes.  I guess everybody involved expected you to know that it is different than just updating the decoder's config (CV) settings.  The important thing is that the problem is resolved.

[Jbub]

Yes Pete, I've read the thread. We all assumed that when Dave said he downloaded the file that he was writing the file to the decoder. We asked him several times to make sure he updated the decoder, which is not the same as writing the sound file iirc.