ESU micro v5-- can't write new sound data

[reinhardtjh]

Here's what I get with a brand new LokSound 5 DCC Micro



And this is after updating the firmware to the most recent in LokProgrammer V5.0.9  (I haven't installed 5.0.10/11 yet)



I also just loaded the Soo #1002 2-8-2 sound file into it with no problems.  But I didn't expect any, I haven't modified it at all.  I was just checking.  It took about 40 minutes.

I'm running the LokSound Programmer (V5.0.9) software on Windows 10 (yuck) inside an Oracle Virtualbox (V6.0.14) VM on my MacPro 2009 (OS X V10.13.6 High Sierra) with 3.33GHz CPU's.  There is 2GB of memory allocated to the VM and the USB port is set to the FTDI USB/serial cable.

[u18b]

Thanks John.
This does point toward some kind of corruption.
Thank you.

Since this is my first ESU sound decoder, I had nothing to go by.
Helpful.  Thank you.

[RBrodzinsky]

Ron,  did you try reading the extended decoder info?  That is what John is reporting above.   I believe you are reporting the data from the tab at the top of the LokProgrammer pane.  Can you try double checking (Extended Decoder info is under the Programmer menu option)

[u18b]

Rick,
I think I did and I don't recall seeing anything- but my memory is fuzzy.

I'll look at it tonight.
I finally heard from ESU and Matt said it sounds like some kind of corruption has taken place and locked the decoder.
I'll be sending it back tomorrow.

On another forum, an experienced ESU modeller said he has heard/seen more issues with v5 than v4, so he thinks there are some kind of teething issues.  It may be a small percentage of us that have these problems, but if it's you, it's very frustrating.

[u18b]

Here you go.
This doesn't mean much to me.

[reinhardtjh]

Ron,

  That's pretty much what I see when I looked at the extended decoder data.  It's mostly version numbers and build dates.  My decoder was from June of 2019.  YOur's is a few months newer.

[reinhardtjh]

Just for completeness, I installed LokProgrammer software V5.0.11 and then updated the same decoder to the latest firmware.  The memory size stayed at 128 MBit and all looks well.  So it's probably that something corrupted Ron's update or the decoder had a problem which cause the bad memory size to show.

[u18b]

Pete,  @peteski

You were asking for more specific details.

I wrote a dissertation for you.   
The whole ugly story.

https://groups.io/g/Loksound/topic/esu_loksound_micro_v5_can_t/71802936?p=Created,,,20,1,20,0::recentpostdate%2Fsticky,,,20,2,0,71802936

EDIT:  Resolution.  I needed to report closure.  I received the replacement decoder from ESU.  Installing a new sound file went perfectly the first try.
Also, Linux and Virtual Box were not the issue.   Both worked fine.   Glad this is over.

[peteski]

Thanks Ron. That ugly story (presented as a single write-up, instead of being presented in smaller chunks is very enlightening.
I also did not appreciate Dave's desire to shut me down.  Just because he is an ESU expert (which he is), and he determined that the decoder was bad, he did not want to entertain any additional discussion.  Well sorry Dave, I don't work that way. You are an expert, but I know the best (at least for my needs).

[Kentuckian]

The last three ESU decoders I have used have had to be replaced. ESU is great on replacement and there were no issues at all getting new decoders. I will say that I bought them from dealers that are not well known; I have never seen them mentioned here on TRW. I believe that John Columbo estimates his decoder failure rate at about 5%. I have drank the ESU kool-aid and have also purchased a tester and programmer.

I have learned my lesson - only use reputable dealers. I know that even that is no guarantee, but everything that I have purchased from the well-known dealers has worked right the first time.

[u18b]

Interesting.
I only have experience with one decoder.
And mine came from Tony's Train Exchange.  Historically a leader in DCC retail.

[reinhardtjh]

Yes, Tony's should be good.  As are Bryan at Streamlined Backshops and I have had good experience with Yankee Dabbler also.

Ron,  since yours worked for a time I doubt it was anything the dealer did.  You probably just got "lucky" and experienced some sort of glitch that caused the microcode to go haywire.  Might not have even been a component failure, but a software thing.

[RBrodzinsky]

Of my first 4 LS 5 installs, I had one that just went into never-never land, too.  Neither Alec (at ESU) nor I could figure it out, but they were quick on the replacement.  I am concerned that these decoders, as circuitry continues to shrink so that we can access more functionality, are reaching the edge of where "uncontrolled environments" (i.e., most hobbyist's work benches) are tolerated. 

[peteski]

Yes, Tony's should be good.  As are Bryan at Streamlined Backshops and I have had good experience with Yankee Dabbler also.

Ron,  since yours worked for a time I doubt it was anything the dealer did.  You probably just got "lucky" and experienced some sort of glitch that caused the microcode to go haywire.  Might not have even been a component failure, but a software thing.

I agree that blaming the failures on dealers is irresponsible.  Unless you requested a sound project to be installed by the dealer, they just take the boxed decoder and ship it to you.  They do not touch or test it.  But if the dealer did handle the decoder (as in installing a sound project) then they could have damaged it by improper handing.  But in those cases, the decoder would likely be DOA (not behave strangely).

As it has been said, these decoders are state-of-the-art super-miniaturized complex electronic circuits. They can easily be damaged by static electricity which is so prevalent in the winter.  And of course more complex software usually comes with more bugs and glitches.  Unfortunately that is the price to pay for all those nice features these decoders have.

[Kentuckian]

I agree that blaming the failures on dealers is irresponsible.  Unless you requested a sound project to be installed by the dealer, they just take the boxed decoder and ship it to you.  They do not touch or test it.  But if the dealer did handle the decoder (as in installing a sound project) then they could have damaged it by improper handing.  But in those cases, the decoder would likely be DOA (not behave strangely).

Two of my three recent failures had dealer installed sound files.