Hi Jorgen
Here a CS3 v2.5.2 user from France with one loco with ESU LokSound5 mini, using MFX (M4) protocol. All my other locos are with Märklin MFX Sound decoders

I may be wrong of course but here is what I think:
- I believe ESU decoders cannot use all the MFX programming tools designed for Märklin decoders
- it is advised to program all CVs using DCC mode
- having no ESU sound programmer I didn't dare to reset the loco BUT on Märklin mSD3 (Sound decoders) making a reset does not clear the sound files and this makes sense as you cannot revert to any "factory" database (too much space wasted). So my guess is your Sound files have not disappeared but are not refered to anymore (fonction key, etc)

Here is my only loco with an ESU LokSound5 mini

I hope this helps
Cheers
Jean

The feeling I get is that CS3 is working in the background of searching decoder environment and suddenly it hits STOP.

One scenario is if you have an engine with 5 decoders on the layout and you close editing on M mfx/mSD decoder, it suddenly goes into stops after half minutes.

It’s unstable…

It would be a good idea for M to pick up the phone and call ESU (in their language) so the mfx standard doesn't take different paths

off topic....

There should be a requirement for a decoder standard in general, so manufacturers must support each other with applications that can read and update decoders through different devices.

Here a good example of minimum requirement that can write and reade Zimo cv settings https://www.beathis.ch/zcs/index.html when M mDT3 application doesn't manage to read their own decoders still until this day

a little upstreams should be appreciated from all type of mfx decoder also with CS2/CS3, and USB-pin Programmer should read out older mfx decoder....



Totally pointless with all these different decoder readers, except making money

I had to go back to 2.4.x because of this problem and now the CS 3+ works again with my LokSound 5 XL decoder

it start with 2.5.1, then they realised beta 2.5.2(0) and nothing change, and the final 2.5.2(6) with the same issues....

ESU spread the information on their forum that 5 decoder wasn't the issues, after a while they also publish M information of next released 2.5.2(6) will solved the issues.

That is never going to happen, after the bad blood from the original cs1/ms1 fiasco that ESU were making for Marklin, and resulted in the relationship going very bad.

What about to test Märklin locomotive by use DCC protocol in the CS3?
How does it works now with latest upgraded version?

I believe it can be done by deleting the mfx version of the locomotive in CS3 and then turn off all other protocols than DCC in the CS3 setting. Then you can set up programming the locomotive in DCC, and turn off mfx in the CV 50 on the locomotive so that it only reacts to DCC. Maybe it is value 4 in CV 50 (but look in the manual of the locomotive first). When it is then all set up with an appropriate address (other than 3) you can turn on all the other protocol settings in the CS3.

Hope it is explained correctly (use the programming track). (Deleting the mfx version of the locomotive is not mandatory but practical).

With your good input, I get more and more courage to try on my CS3 with DCC + the Roco locomotive.

I have already written to a local Märklin man about whether we should do it together.

I have suggested to him, that we start with DCC & the locomotive and see what it brings (I know one with ECOS, so it is in reserve).

If it goes well and the braking distance is reduced + possibly the sounds reappear then maybe we'll be brave enough to push my CS3 back to 2.4.x, where all was well.

It will be exciting, what we will be missing from the new update!

So when there is new information, there will be informations.

But thanks for your advice

Mine is also a CS3+, and whether there is something in the hardware is probably not easy to find out!

I have also read on Stummis, that some had solved the problem with Loksound 5 by deleting the locomotive and reloading it, but it did not return the correct sounds/noises!

Only to wait until the next update when others report various odd issues in addition to 5 decoders on Stummis...

For large developmental changes, between long periods of time.

I delete loksound 5 loco and reload on CS3+. It works fine. No problem.

Yes