Hi all,

My latest purchase, the purple 37018 S2/6 has some issues when I try to run it on my Ecos1, with recent FW (4.2.2, I still need to update to 4.2.3). It is detected through mfx OK, and at first everything seems fine. But after a powercycle of my command station it often fails to respond to commands, and sometimes starts running at maximum speed before stopping. Also, propagation of commands seems very slow. Eg when I press the lights on it takes 1 sec before the lights actually go on.
Another recent new loco of mine, BR42 39044, seems to work fine, it exhibits none of the issues. But then again, my BR58 37587, also a relatively new purchase of last year, also has issues when power is cycled, and it fails to respond.

In an attempt to mitigate this I have disabled mfx on my BR58, and I run in DCC mode, but I don't think that fixed anything. The S2/6 has worse behaviour than the BR58 though, to get it to work again when it does not respond I have to cycle power to the rails multiple times. So I cannot say I'm confident it is the same issue. None of my other locos (50+, I stopped counting) have these issues.

Is this behaviour something you ESU Ecos users recognize? Is there a fix? Is it the loco decoder or the central station? I also noticed I cannot reprogram the latest mfx decoders from my Ecos. I guess this is expected behaviour as I already read some of you have the same issue.

Bert

Another edit: after changing that bit, also the programming interface of the mfx decoder seems to work again. Eg I can adjust the volume of the speaker. Thats also the case for my BR42, 39044, that otherwise seemed to work perfectly.

So all ecos users, if you want to properly use the latest mfx locos, set the asymmetric track signal setting to ON!!!

Bert