CS3 software bug affecting motor type, when English is used as system...

Welcome Guest! To enable all features please Login or Register.

Notification

Error

CS3 software bug affecting motor type, when English is used as system language.

Options

View

Previous Topic Next Topic

bph		#1 Posted : 08 February 2022 13:42:33(UTC) Retweet
Joined: 04/08/2018(UTC) Posts: 1,155		Hello, This is a heads-up that there is most likely a bug in the cs3 software, that reads and programs mfx decoder motor type wrong. (CV52) The bug seems to only affect the CS3 when English is used as a system language. I tested all other system languages, and they seem to be ok. I'm currently using cs3 software 3.2.1 (8). (tried to restore it to original configuration etc, and that did not affect things) Bigdaddynz did a test on his cs3 and experienced the same. (also 3.2.1 (8)). here is an example from one of my locomotives: Note the difference in motor type. (CV52) Correct read out, of the mfx decoder in German. Wrong read out in English. the only change was the system language. (noting was programmed to the decoder). This also affects programming. E.G if the CS3 is used to set the motor type of a mfx decoder. the motor type is programmed wrong. note that programming using mDecoderTool with 60971 or through the CS3 is not affected. here is an example: the c90 is selected when the system is set to English: And a readout after in German shows that the mfx decoder was actually programmed with a bell anchor motor: a readout on the 60971, confirmed the same. This might not affect that many in reality, but if someone programmed a mfx decoder lately using a cs3 with software 3.2.1 (8) and English as system language, it's worth checking. I can not say if this affects other settings, or DCC etc, as well because I have not checked. But some caution is recommended, or use another language if possible. I have reported this to Märklin, and hopefully, they will look into it. (the initial response from Marklin customer service was not that positive so I had to investigate a bit more and provide more evidence). Thanks to Bigdaddynz , for helping to confirm this bug. According to Märklin, they are planning to release a "big" update to the CS3 this week or the next week. So hopefully that update will fix it. This is provided as information for those who find it interesting and/or might be affected. Personally, I program my decoders with mDecoderTool, and can use other system languages e.g. Swedish, Danish or German.

5 users liked this useful post by bph		Bigdaddynz, roberts, phils2um, Purellum, clapcott
User Profile View All Posts by User View Thanks


	Wish to join the discussion?! Login to your marklin-users.net community \| Forum account or Register a new forum account. Or Connect via Facebook

kiwiAlan		#2 Posted : 08 February 2022 21:45:25(UTC) Retweet
Joined: 23/07/2014(UTC) Posts: 8,464 Location: ENGLAND, Didcot		Originally Posted by: bph According to Märklin, they are planning to release a "big" update to the CS3 this week or the next week. So hopefully that update will fix it. I wouldn't bet on an update to this bug unless you notified them about 6 months ago. I would think most of the last three months will have been spent on regression testing of the software,whereby it gets run through many tests to test for previously found problems and/or 'corner cases'.


User Profile View All Posts by User View Thanks

bph		#3 Posted : 08 February 2022 22:13:27(UTC) Retweet
Joined: 04/08/2018(UTC) Posts: 1,155		Originally Posted by: kiwiAlan Originally Posted by: bph According to Märklin, they are planning to release a "big" update to the CS3 this week or the next week. So hopefully that update will fix it. I wouldn't bet on an update to this bug unless you notified them about 6 months ago. I would think most of the last three months will have been spent on regression testing of the software, whereby it gets run through many tests to test for previously found problems and/or 'corner cases'. You are probably right, but hopefully, it has been discovered by someone in the software department earlier or that it's a minor thing in the English software that is easy to fix (but I'm not a programmer so I can not tell). I did actually notify customer service last autumn, but the initial slow response to emails and their unwillingness to acknowledge it has caused it to drag out in time. I have not spent much time on it, and I was open to it that it could be something with my cs3. And here the other day I decided to test loading the initial settings and by chance, I did a readout when the system was still in German, and things were correct, but when the system changes back to English the bug was back. And as I wrote it's not a big thing, but it's nice to be aware of. Only time will tell when it will be fixed.......


User Profile View All Posts by User View Thanks

bph		#4 Posted : 01 December 2023 19:44:00(UTC) Retweet
Joined: 04/08/2018(UTC) Posts: 1,155		This bug was finally fixed in the CS3 2.5.1 software release.

3 users liked this useful post by bph		mbarreto, marklinist5999, dickinsonj
User Profile View All Posts by User View Thanks

marklinist5999		#5 Posted : 01 December 2023 20:28:43(UTC) Retweet
Joined: 10/02/2021(UTC) Posts: 3,881 Location: Michigan, Troy		As with many things, appropriations and executions take time.

1 user liked this useful post by marklinist5999		bph
User Profile View All Posts by User View Thanks

Users browsing this topic
Guest

Forum Jump

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.