ESU LokSound 58751 decoder

[woodone]

Was wondering how most of you test a drop-in type decoder like an 58751.
I solder some short jumper wires from the decoder to my decoder tester.
On this decoder , it is giving me fits.
Programer tells me it does not find the decoder?
Well with soldered connections I can not see that I would have-a bad connection.
Any ideas on this-
Will check this AM if there might be a Programer update.
I did try to program a series 5 sound file first- no go, so then I tried a 4 series sound file, same result- can not find decoder.

[peteski]

ESU makes decoder testing fixtures for decoders with no wires, but I don't think they make one for this decoder.

But since this is a plug-n-play decoder, why not install it in the model, then test it?  The model will act like a fixture. Unless you are installing it in a model which is not plug-n-play.

As for testing the decoder using the LokProgrammer, instead of trying to program it, start the LokProgrammer, then open a new project or just start with no project, then under the "Programmer" menu "read decoder data" . That will attempt to communicate with the decoder to extract its CV values and identity.

I don't think that (unlike using standard programming track) some electric load (like motor) is required when LokProgrammer reads ESU decoder's CVs.  Just the left and right track connections. If LokProgrammer fails to read it, then the decoder has a problem, or the connections to the track pads on the decoder are not being made. 

Even older version of the LokProgrammer software should be able to read a new decoder - it should then tell you that there is some sort of compatibility problem.  "Decoder not detected" just means that the LokProgrammer is not seeing any decoder on the programming track.

[woodone]

Morning Peteski.
Well,it might be PM, now where you are.
I used to install and then tried to program ( note tried).
I had too many failures.
So I started to program and then install, which worked out better for me.
There was too much time wasted when I did the install first and then found out I had a decoder.problem
In this case it saved me some time- I do not have any lights to remove along with their wiring.
Programmer says this—-The decoder detected is not supported ? Well if is detected I am guessing it is getting track power.
So , why will it not program?
I will have to look.,into the fixtures to work, on the drop ins.

[peteski]

Morning Peteski.
Well,it might be PM, now where you are.
I used to install and then tried to program ( note tried).
I had too many failures.
So I started to program and then install, which worked out better for me.
There was too much time wasted when I did the install first and then found out I had a decoder.problem
In this case it saved me some time- I do not have any lights to remove along with their wiring.
Programmer says this—-The decoder detected is not supported ? Well if is detected I am guessing it is getting track power.
So , why will it not program?
I will have to
 look.,into the fixtures to work, on the drop ins.

Well, if you look at your initial post, you stated "Programer tells me it does not find the decoder?". That is quite different than "not supported decoder".  My answer was for the error you mentioned. If "not supported" is the error, then yes, you likely have to get a new version of the LokProgrammer software.

Curious - what version of LokProgrammer are you using?

[woodone]

Yes, you are correct- I have tried a different way to try to get Programer. Coumpter is upstairs have to go up and check the version of the programmer. Will be back, takes time now after some heart work done on me—new pacemaker!

[woodone]

Well I finally got up the stairs to check ESU programmer version-
Well so much for that Idea - computer will not turn now! Just my luck!
Second question- seems like the components on the decoder could be touching the frame haves where it is very narrow.
Anyone install the 58751 into a Atlas unit note this?

[Dwight in Toronto]

I picked up a new Atlas GP38 at a train show back in March.  It had factory dcc, but the decoder performance was horrible so I installed a 58751.  And yes, I found that there is indeed a potential short-to-frame to watch out for. 

The factory decoder was fitted with very small clips (I’m going to assume copper or PB), press-fit to grip onto the track power pads on each side of the decoder board.  The board, with these clips attached, was then, in turn, press-fit into the slots on each frame half so as to convey track power to the board.  Without the clips, the slots in the frame halves were much deeper than the thickness of the decoder pc board - so much so, that the track power pads could not touch their respective intended contact points.  The tiny clips are very effective at eliminating that sloppiness.

Since the 58751 board was just as thin as the factory board, I re-used those clips during the install.  They fit nicely and certainly did the job.   However, I found that the clip was a wee bit wider than the pad on one side of the ESU board, and that it was possible for the clip to just barely touch one of the other components towards the inside edge of that power pad, resulting in a short.  Rather than rely on a friction fit, I backed the clip off slightly, then gave it a quick tap with the soldering iron to keep it slightly distant from the inner edge of that pad.

Sorry, no photos, but I hope this long-winded explanation might be of some help. 

[woodone]

Thanks for your feed back Dwight.
My SD35 did not have those clips.
I was concerned with some of the components on the board touching the frame halves on each side.
I machined the center of the frames a bit so there was some clearance between the board and the frames.
I have seen these clips on other Atlas locos, but I do not use them.
A touch of solder on the pads works for me.