?

Yes, and i write in my post (If you like to have the file send me a pm.)

Märklin is in the final testing stage of a new update, so if it passes it will be officially released fairly quickly.

Hi,

the version 2.5.2 is expected to be available by the end of February.

Kind regards
Jörg

When Marklin releases it, the red dot will show up on the CS3 system menu. Why stress it? We can still run traffic.

I din't mean they do run like mine. Even if you use another automation software package, and are having issues, with other manufatuurers decoders, etc., you can at least still run trains using only basic CS3 functions.

Don't use ex-FAT, use FAT32. If the stick is to large a capacity to use FAT32 then that is another part of your problem. Don't use a stick bigger than 32GB.

I would also suggest to use the menu to select loading from the stick.

Where can I find v2.5.2?

hope they manage to keep what they promise, it's the final day

Did they mentioned what month they were talking about? :-)))

MC

yes, total confusion

still the same file name like the "beta" and PDF documentation is still showing 2.5.1 files

The new 2,5,2 (6) file is faulty

I have tried to download it 2 times, used 2 different USB sticks and get the same error message :

""Warning
The update image on the USB stick is faulty.
Please reload the update image or use a different USB stick.

This message comes up until the next restart of the CS3""

Someone else get this error message

The Maerklin guy in my local, Danish, forum says that the update will be rolled out for all CS3s over the coming days.

A online update to 2.5.2 worked fine


and a update for the MS2 was also included, new version 4.13

Norbert, I get that message, but only when I am in edit mode. I haven't tried to edit a loco twice.

I updated to v2.5.2 and the Loksound 5 issue is resolved. You need to delete the lok from CS3 and re-register. After that, everything is fine and you can edit the Loksound 5 decoders on CS3.

Hi
I am a bit off topic, sorry. I loaded the last CS3 version v 2.5.2(6) and it went well for my Märklin MFX locos but not so well for a Märklin loco fitted with the LokSound 5 micro decoder.

What happened:
- the firmware into the ESU decoder was modified by Märklin CS3 in a way that no physical fonction I use is operational anymore.
- the rest is working fine: Motor, sound etc.

What I tried
- at first I thought that NO Märklin wouldn't be stupid enough to modify the firmware of someone else's decoder (That they know poorly) so I tested the loco in analogue: I have sound but no lights so Märklin did modify without my consent my property and damaged it. I am outraged- of course I did many reset of the decoder using MFX and also DCC. In MFX, the loco was removed from the list and re-appeared as all MFX locos do. But no cure to my problem
- next, being a tenacious and a nasty person, also Engineer in electronics I immersed myself into the delicacies of CVs in ESU decoders (I have no ESU Lokprogrammer) and, gosh, it is a real gas factory (that's what we say in France when a product is overly complicated (warning, understatement here).
- I read the CVs in the decoder (using the CS3 in DCC mode), I red the CVs in the initial ESU project (thanks to the ESU LokProgrammer s/w) and the physical fonctions and I cannot locate where Märklin did some changes
- so it is still a work in progress (17 CVs per line for each fonction-key/ sound-logical-random fonctions among 72 lines or so and this is only a small part of the CV salad.

I must say Thanks Märklin for being so inconsiderate to your customers (by destroying their own property) and thanks to ESU to create such "gas factory" and totally user UNfriendly systems.
Cheers
Jean