ECoS Firmware 4.2.7

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

Notification

Error

ECoS Firmware 4.2.7

Options

View

Previous Topic Next Topic

mmervine		#1 Posted : 25 December 2019 17:39:22(UTC) Retweet
Joined: 30/01/2006(UTC) Posts: 1,884 Location: Keene, NH		ECoS firmware 4.2.7 has been released. Google translation: The new firmware corrects a problem with Märklin noise decoders, which will be installed in many Märklin locomotives ex works from summer 2019. Locomotives with these decoders could not automatically log on to an ECoS with mfx. The cause is a software error in these decoders, which only occurs if RailCom is active on the track at the same time. In firmware 4.2.7. the track signal generation has now been adjusted so that these decoders behave correctly again, since it is not foreseeable whether and when Märklin will fix the error. Furthermore, up to 500 user-defined locomotive images are now released and the 7A Booster 50012 will be recognized by the ECoS.
		Märklin C-track, Marklin Digital & ECoS, multi-era French & Swiss http://www.ete-ene.org/m...mervines-layout-gallery/

2 users liked this useful post by mmervine		xxup, Bigdaddynz
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 : 25 December 2019 18:07:44(UTC) Retweet
Joined: 23/07/2014(UTC) Posts: 8,107 Location: ENGLAND, Didcot		Originally Posted by: mmervine ECoS firmware 4.2.7 has been released. Google translation: The new firmware corrects a problem with Märklin noise decoders, which will be installed in many Märklin locomotives ex works from summer 2019. Locomotives with these decoders could not automatically log on to an ECoS with mfx. The cause is a software error in these decoders, which only occurs if RailCom is active on the track at the same time. Well, that explains something, I wondered why mfx locos wouldn't register on my Roco Smartrail unit which tries to identify a loco using railcom. I found I had to turn off mfx in the loco for it to be found.


User Profile View All Posts by User View Thanks

Goofy		#3 Posted : 25 December 2019 20:06:42(UTC) Retweet
Joined: 12/08/2006(UTC) Posts: 9,019		The best way is to set at CV 50 adress by choice protocol first by disabled mfx and MM.
		H0 DCC = Digital Command Control


User Profile View All Posts by User View Thanks

kiwiAlan		#4 Posted : 26 December 2019 19:52:07(UTC) Retweet
Joined: 23/07/2014(UTC) Posts: 8,107 Location: ENGLAND, Didcot		Originally Posted by: Goofy The best way is to set at CV 50 adress by choice protocol first by disabled mfx and MM. That is exactly how I did it Goofy, in fact it is the only way on a loco.


User Profile View All Posts by User View Thanks

clapcott		#5 Posted : 28 December 2019 08:16:05(UTC) Retweet
Joined: 12/12/2005(UTC) Posts: 2,435 Location: Wellington, New_Zealand		Originally Posted by: mmervine Google translation: ... The cause is a software error in these decoders, which only occurs if RailCom is active on the track at the same time. I am curious .... For there to be an error, there must be a expectation (specification) that has been agreed to first I am wondering When(Where documented) did Marklin state that their "...noise (sound?) decoders, which will be installed in many Märklin locomotives ex works from summer 2019.' were compatible in an environment where " ...RailCom is active .." or, to ask it the other way around, Which agreed specification (NEM) has not been met (I an not "assuming" that Marklin adhere strickly to the NEM standards , but this might be a neutral reference point when debating compatibility between the ECos and the Marklin supplied decoders - rather than taking one or the others biased view on how compatibility works) What I am actually really interested n researching is HOW the mfx (mfx+) and Railcom protocols are expected to work together, including the limitations Parallel to this it would be nice to know why it is only the " decoders, which will be installed in many Märklin locomotives ex works from summer 2019 " - that are affected. - how they are identified - the "known" firmware version that is allegedly faulty - whether Marklin has responded to this allegation (i.e have they actually accepted it as a "software error" and if so are they even intending to address it. note: the outsourcing contract that Marklin has with their decoder supplier might very well include specification requirements that preclude the concurrent compatibility with RailCom. And finally, out of interest, why not disable the RailCom protocol from the controller.
		Peter

1 user liked this useful post by clapcott		David Dewar
User Profile View All Posts by User View Thanks

ocram63_uk		#6 Posted : 30 December 2019 00:25:41(UTC) Retweet
Joined: 07/01/2015(UTC) Posts: 704 Location: England, Suffolk		when you download the new SW zip file the release notes are both in German and English, there is no need to use transle.google.com which is rubbish for this.


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.