ESU eCOS Update 3.2.0 and 3.2.1 (June 2010)

[Adrian L]

I understand from the marklin-users.net forum that Windigipet may not work if I update my eCOS to the latest version.  Is this correct? What problem does it cause?

Thanks

[supermoee]

Hello Adrian,

the transfer of loc- and functionsymbols from/to the central is not working correctly. 

http://www.windigipet.de/foren/index.php?topic=63426.msg108065#new

rgds


Stephan

[Adrian L]

Thanks Stephan...

The Babel Fish translation of the link needs lots of work -

"Very honoured Win Digipet user for the ECoS 1, ECoS 2 and the CS 1 Reloaded by ESU the update 3.2.0 was published yesterday. Thus now the problem results after first tests for the users of all above mentioned centers that with this firmware from the current Win Digipet version no more locomotive/function symbols can be transferred into those or from the center on the part of the program. This suggested itself in the last days due to user messages the ECoS concerning 2, since this was already probably in the firmware the ECoS 1/CS1RL somewhat ahead. Therefore we inquired with ESU. ESU modified - like us today then communicated - interface minutes in these points. According to recent findings the driving/scolding and reporting enterprise are affected by it however in keinster way. We received changed interface minutes from ESU this evening. After first sifting now extensive adjustments at the 2009er version of Win Digipet are necessary (it will not give updates of the ProX), which will flow into the next Win Digipet update. And will first times not designate we know a schedule in addition since up-to-date still no update was planned and us the whole also something " kalt" got."

 I am fascinated by the phase "According to recent findings the driving/scolding and reporting enterprise are affected by it"..

Cheers

[Stefan Lersch]

Hi Adrian,

yes, it really needs a lot of work, especially when it drops the most important word in a phrase

According to recent findings the driving/scolding and reporting enterprise are affected by it however in keinster way.

It didn't translate "keinster". It means "absolutly not". So it's not affected.

[Hwnel]

Here's my attempt at a translation...hope it makes a little more sense.

Dear Win-Digipet User,

The update 3.2.0 is available since yesterday for ECoS 1, ECoS 2, and CS 1 Reloaded from ESU.

First tests identify a problem with these controllers that the firmware of these controllers and the current Win-Digipet Version do not transfer the locomotive and function symbols to or from each other.  EcoS 2 users have identified this in the last few days. The firmware was probably updated since the ECoS 1/CS 1 Reloaded.   We inquired with ESU if that was the case.

ESU informed us today that the Interface-Protocol was modified with these points.  According to recent findings, the driving, switching and feedback are in no way affected.
 
We received the modified Interface-Protocol from ESU this evening.  At first glance, there are major adjustments necessary in the 2009 version of Win-Digipet that will be incorporated in the next update. (There will be no updates for the ProX version)  A timetable for the update will not be given, as there was no update planned and this new circumstance surprised us.

Aloha,

Elliott

[Tom Blikstad]

Hello Mr. Peterlin.

It is a pity for every user of ECoS that we have to deal with these errors for a long time.

I see there will bee no update of ProX but did you consider a small one ?

I understand it was a surprice for everybody ...........

[Peterlin]

Hello Mr. Blikstad,

sorry, but there will not be an update for the old Pro X version.  You can use Win-Digipet and ECoS  further more but you can not transfer the locomotive and function symbols to or from each other.

We are now working on the update 2009.3b to solve the problem coming with the new update 3.2.0 of the ECoS protocoll.

best regards

P.Peterlin

[Tom Blikstad]

Thank you, that is even better.

[Adrian L]

Here's my attempt at a translation...hope it makes a little more sense.

... According to recent findings, the driving, switching and feedback are in no way affected....

Thanks Elliott.. Now "driving/scolding and reporting enterprise" makes much more sense...  In short, it says that you will have no problems as long as you do not add any new locos..

It also explains why there will be no Pro X update - Pro X never transferred mFx data from the eCOS to WDP (or even recognised mFx locos - even after the eCOS updates to support mFx)... To apply the "fix" to Pro-X would be a major effort that would in effect provide the 2009 version's functionality...  Personally, the improvement moving from Pro-x to 2009 was more than worth the upgrade cost - after I got over the shock of losing the automatic demand contact functionality...

In short - if you have an eCOS and are using mFx locos, then get cracking with your order for the 2009 upgrade... You won't be disappointed.. But don't upgrade the eCOS to 3.2.0 until Peter gets the "fix" ready for us..

Cheers

[Adrian L]

It looks like 3.2.1 was released today (3.2.0 was removed) and there is mention of changes to the PC interface.. Does this mean that there is no longer a problem using WDP?

[Markus Herzog]

Hello Adrian,

No, the problem concerning the function symbol transfer already exist. There were some programs who weren´t even able to startup due to the interface changes. This has now been changed by ESU.

We are currently working on this issue, but there has a lof testing to be done.

Regards
Markus

[Adrian L]

Thanks for the fast response Markus.. I guess I will have to wait a little longer before I update the eCOS.

Cheers