Scribd
Upload
14 views

Read Me

The CoDeSys installation prohibits installing newer versions into directories containing older versions to avoid compatibility issues from upgrading the .NET framework. Some applications downloaded with older versions may require online changes when logging in to versions 3.5 and greater due to the .NET framework upgrade. The mapping of IEC task priorities to OS priorities was changed in a linear manner in this release.

Uploaded by

w automation
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
14 views

Read Me

The CoDeSys installation prohibits installing newer versions into directories containing older versions to avoid compatibility issues from upgrading the .NET framework. Some applications downloaded with older versions may require online changes when logging in to versions 3.5 and greater due to the .NET framework upgrade. The mapping of IEC task priorities to OS priorities was changed in a linear manner in this release.

Uploaded by

w automation
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 3

Very important information:

1 Installation

In CoDeSys V3.5 we switched from version 2.0 to version 4.0 of the Microsoft .NET framework. The
framework version that is actually used is determined by the startup executable file (CoDeSys.exe).
In order to avoid any compatibility risks between these two versions, we decided that our setup will
prohibit an installation of CoDeSys V3.5 or newer into a directory which already contains any CoDeSys
version before V3.5 (If we allowed this, the CoDeSys.exe would be overwritten by the newest version
running on .NET 4.0, causing even the old CoDeSys version to be executed under .NET 4.0, which might
– unlikely, but not impossibly – cause compatibility problems).
2 Compatibility Information

Online Change [CDS-26087]


In some cases, applications downloaded with older versions, will ask for online change on login with the
version 3.5 and greater.
This incompatibility is caused by the upgrade from .NET Framework 2.0 to .NET Framework 4.0.

Mapping of IEC task priorities [CDS-23211]:


The mapping of IEC task priorities to OS priorities has changed with this release. This only affects
systems, where the available IEC task priorities do not match the number of available OS task priorities:
Now, the priority of an IEC task is mapped to the OS priority in a linear way. E.g.:
- IEC prio=10, OS prio range for all IEC tasks=64..80 --> IEC task prio on OS= 74
- IEC prio=11, OS prio base for all IEC tasks=64..80 --> IEC task prio on OS= 75
- IEC prio=32, OS prio base for all IEC tasks=64..80 --> IEC task prio on OS= 80

Previously, it was mapped this way:


IEC task prio / (32 / OS task range)
- IEC prio=10, OS prio range for all IEC tasks=64..80 --> IEC task prio on OS= 74
- IEC prio=11, OS prio base for all IEC tasks=64..80 --> IEC task prio on OS= 74
- IEC prio=32, OS prio base for all IEC tasks=64..80 --> IEC task prio on OS= 80

In the device description, the number of available priorities must be specified with the real available
priorities on the target:
<ts:section name="taskconfiguration">
<ts:setting name="mintaskpriority" type="integer" access="visible">
<ts:value>0</ts:value>
</ts:setting>
<ts:setting name="maxtaskpriority" type="integer" access="visible">
<ts:value>31</ts:value>
</ts:setting>

You might also like