release information codesys_v3.5 sp6 patch 4

8/21/2019 Release Information CODESYS_V3.5 SP6 Patch 4

1/15

Release Information

CODESYS

Profile: V3.5 SP6 Patch 4

Release Date: 28.05.2015

Template: Vorlage_tecdoc_Release_Information_V1.0.dotx


2/15

© 3S-Smart Software Solutions GmbH

T e m p l a t e : V o r l a g e_

t e c d o c_

R e l e a s e_

I n f o r m a t i o n_

V 1 . 0 . d o t x

CONTENTS

Seite

1

General 3

1.1 Responsible for the release 3

2 Important Information 4

3 Compatibility Information 5

3.1

Compatibility Information for End Users 5

3.2 Compatibility Information for OEMs 8

4 Known Restrictions 11

5 Features and Changes / Addressed Defects 12

6

Release Information 13


3/15

CODESYS Inspiring Automation Solutions 3/15 CODESYS


1 General

This document contains information on a product version which was released in compliance with our qualityguidelines.

1.1 Responsible for the release

Name Role

Dieter Hess Product Manager / CEO

Kevin Ketterle Manager Product Development (Base Technology)

Hilmar Panzer Manager Product Development (Application Technology)

Thomas Zauner Manager Product Development (Systems)

Monika Gottwald Quality Assurance

Responsibilities of the undersigned

Product Management

(Confirmation that the content of the version to be released meets the requirements of the ProductManagement)

Product Development

(Confirmation that the version to be released was developed in compliance with the relevant processdescription)

Quality Assurance

(Confirmation that the version to be released was released in compliance with the relevant processdescription)

Kempten, 28.05.2015 ____________________(Dieter Hess)

____________________(Hilmar Panzer)

____________________(Kevin Ketterle)

____________________(Thomas Zauner)

____________________(Monika Gottwald)

Note: If you are updating from a version older than this release, then please ensure that you read the releaseinformation documents for all releases since your version.


4/15



2 Important Information

Defective Libraries in CODESYS V3.5 SP6 Patch 2

The IoDrvProfinet, IoDrvEthernetIP and RPC libraries were damaged in the build for CODESYS V3.5 SP6 Patch

2. Therefore, these libraries cannot be compiled at this time.This causes unrecoverable compile errors to occur when the EtherNet/IP and PROFINET fieldbuses are usedwith the latest versions of these libraries.

Therefore we urgently recommend you use V3.5 SP6 Patch 3 or newer.


5/15



3 Compatibility Information

3.1 Compatibility Information for End Users

LMM: Wrong warnings are shown when there are compile errors (CDS-41523) Any of the missing library warnings might be a hint to the user for fixing the compile errors.The code might also contain references to POUs or global variables in libraries marked as optional, so warningsfor those libraries also cannot be filtered in the message output.

Compile: Negative string lengths reported as error (CDS-6656)

New error C0362 introduced for strings with size expressions evaluating to negative values

LMM, Compiler Version: Delete compiler versions < 3.4.0.0 (CDS-39898) Compiler versions < 3.4.0.0 can no longer be selected by the user.

SysComWin32: Automatic port detection (CDS-42524) To fix this issue, the compare algorithm for the following setting was slightly changed:[SysCom]Windows.CheckWithPortName.0=

In older versions the friendly name of the adapter must contain , now it must start with . Pleasecheck, if you have to adapt your settings in your gateway / runtime system configuration file.

RTE: New Microsoft Feature "FullMemoryDiagnostic" destroys code/data memory at runtime (CDS-41643) RunFullMemoryDiagnostic is disabled by default, as it potentially leads to a system crash if another system is

running on a non-Windows-core.

Library SysFileAsync (CDS-37782)

CmpAsyncMgr now removes an asynchronous job always at the end of the job execution. Therefore, the jobdoes not have to be removed at the end by the caller manually.

If you use SysFileAsync23.library in your PLC application:You have to update to SysFileAsync23.library v3.5.6.0 (as well as SysFileAsync.library v3.5.6.0) to avoidunhandled jobs in multiple, parallel, asynchronous file operations.

PROFINET Editor: Integrate IRT Scheduling (CDS-38577)

This is a preview to be released with V3.5 SP7.To enable the preview, add the following to the controller devdesc:

PNIOControllerParametersPNIOTopologyConfigParameterEditorStatusPageDeviceInformation

PROFINET IO Master Stack (CDS-35127) A combination of CIFX-based and 3S Controller in the same project is possible, but some IDE functions (using

communication to PLC) do not work reliably:- Status Page: Diagnostic data and alarms are not shown.- Scan Dialog: Functions “Get I&M-Data” and “Reset to Factory” do not work.

http://jira/browse/CDS-41523http://jira/browse/CDS-41523http://jira/browse/CDS-41523http://jira.3s-software.com/browse/CDS-6656http://jira.3s-software.com/browse/CDS-6656http://jira.3s-software.com/browse/CDS-6656http://jira/browse/CDS-39898http://jira/browse/CDS-39898http://jira/browse/CDS-39898http://jira.3s-software.com/browse/CDS-42524http://jira.3s-software.com/browse/CDS-42524http://jira.3s-software.com/browse/CDS-42524http://jira/browse/CDS-41643http://jira/browse/CDS-41643http://jira/browse/CDS-41643http://jira.3s-software.com/browse/CDS-37782http://jira.3s-software.com/browse/CDS-37782http://jira.3s-software.com/browse/CDS-37782http://jira.3s-software.com/browse/CDS-38577http://jira.3s-software.com/browse/CDS-38577http://jira.3s-software.com/browse/CDS-38577http://jira.3s-software.com/browse/CDS-35127http://jira.3s-software.com/browse/CDS-35127http://jira.3s-software.com/browse/CDS-35127http://jira.3s-software.com/browse/CDS-35127http://jira.3s-software.com/browse/CDS-38577http://jira.3s-software.com/browse/CDS-37782http://jira/browse/CDS-41643http://jira.3s-software.com/browse/CDS-42524http://jira/browse/CDS-39898http://jira.3s-software.com/browse/CDS-6656http://jira/browse/CDS-41523


6/15



CAN Download: Implement Network Scan (CDS-19463) CmpBlkDrvCanServer and CmpBlkDrvCanClient now support network scan.Therefore, some incompatible changes were necessary:- New PLCs are not compatible with old gateways anymore.- Default network interface name for CmpBlkDrvCanServer was renamed from Canbus0 to BlkDrvCanServer.- NodeID in configuration file of Gateway will now be used on bus. Please check that there are no NodeID

conflicts.

Furthermore, some new settings were introduced:- Capability to overwrite the default network interface name- More than one instance of BlkDrvCanClient is possible.- Task priority and cycle time of blockdriver can be changed in the configuration file (slowest supported cycletime is 100ms).

SM: SMC_SetControllerMode does not interrupt the ongoing movement when switching to position mode fromlower mode (CDS-41439) The interrupt behavior of SMC_SetControllerMode has changed when switching to position mode from current,velocity, or torque mode to position mode.

Previously, SMC_SetControllerMode did not interrupt an ongoing movement. Depending on the order ofexecution of the function blocks, this could lead to jumps in the set position.

The new behavior is that SMC_SetControllerMode will interrupt an ongoing movement when switching toposition mode and the axis is switched on (bRegulatorOn and bRegulatorRealState). The only exception isMC_Stop, which will not be interrupted by SMC_SetControllerMode.

SMC_SetControllerMode itself can be interrupted only by MC_Stop. In this case, it will create the new errorSMC_SCM_Interrupted.

Libraries, Online Change: Online Change for libraries needed (CDS-41378)

Until now (compiler version < 3.5.6.0), a library has been identified by name, vendor and version. If one of theselibrary attributes is changed, then the library will be a new, different library. The result is that all types in the newlibrary are incompatible to the types in the previous library. In other words, a function block FB in a library1.0.0.0 is a different function block in library 2.0.0.0. If the library changes and an online change is performed,then all instances of this function block are initialized and a copy code is not produced for these instances.Hence, the values are lost.

As of compiler version >= 3.5.6.0, this behavior changes. If all references to a library have the same version,then this version is ignored for the identification of the types in the library. Therefore, if the library is attractedwith a newer version, then the types in the library will match the types of the last download or compiler. Forexample, the same function block FB in the above example will be identified as the same function block, even ifthe library version changes. If the FB changes, then copy code will be produced for all instances. If the FB doesnot change, then all instances will be unaffected by the online change.

Please note: If the same library is attracted with different versions, then the version will be important to identifythe types, and online change will have the old behavior.

Visu, Online change: Evaluate and implement complete re-initialization after online changes affecting thevisualization (CDS-37646)

The mechanism that determines how the visualization implements the online change has been completelyreworked to achieve the expected stability. This improvement applies to compiler versions >= 3.5.6,visualization profiles >= 3.5.6 and runtime systems >= 3.5.5. Older combinations will still use the oldmechanism.

For users working with the visualization, the effect is that all active visualizations will close and restart (for thetarget visualization) or restart after a temporary communication error (for web visualization and remote targetvisualization) when an online change affecting the data layout of an application is executed. In addition, the newmechanism tightens the requirement to execute calls to visualization methods (programmatic selection,

http://jira.3s-software.com/browse/CDS-19463http://jira.3s-software.com/browse/CDS-19463http://jira.3s-software.com/browse/CDS-19463http://jira/browse/CDS-41439http://jira/browse/CDS-41439http://jira/browse/CDS-41439http://jira/browse/CDS-41378http://jira/browse/CDS-41378http://jira/browse/CDS-41378http://jira.3s-software.com/browse/CDS-37646http://jira.3s-software.com/browse/CDS-37646http://jira.3s-software.com/browse/CDS-37646http://jira.3s-software.com/browse/CDS-37646http://jira/browse/CDS-41378http://jira/browse/CDS-41439http://jira.3s-software.com/browse/CDS-19463


7/15



programmatically opening dialogs etc.) only from the VISU_TASK. As this requirement was also present before,due to unimplemented thread safety in the visualization libraries, this is not a compatibility problem.

On multitasking systems, the required name for the task running the visualization is VISU_TASK. Otherwise, acompilation error will be issued with further information.

On single-tasking systems supporting the visualization and online change, the online changes can delay theexecution of the IEC task for a longer time than before.

For customers working with the VisuElement Toolkit, please refer to the respective section in the toolkitdocumentation.

Visu, Styles: Create additional modern style (flat style) (CDS-39404) Requires both compiler version >= 3.5.6.0 and visualization profile >= 3.5.6.0

Visualization styles:When using a customized style, it is recommended to add the following new style entries and use them in theappropriate element properties in order to change the style from the customer style to the flat style without

changing the intended appearance. The new style entries are recommended also for adding visual elements toany visualization. (The sample style can be used as guideline.)

Table element selection color:New elements will use the stylecolor "table selectioncolor".In existing elements with used selection and an changed selectioncolor: the color also will be used with the flatstyle.In existing elements with no used selection: there will be no selection with the flat style too.In existing elements with used selection but unchanged selectioncolor: The selection used to be not visible, asthe selectioncolor white was used. When the flat style is used, now the white selection will be visible.To have a selectioncolor, that fits to all styles, change the colorvalue to the styleentry "table selectioncolor".

Colors:

BasicElement-Alarm-Fill-ColorBasicElement-Alarm-Frame-ColorBasicElement-Fill-ColorBasicElement-Frame-Color-> used for the colors for basic elements

Dialog-BackgroundColorDialog-ButtonColorDialog-HeaderColorDialog-ScrollbarColor-> to change the look for the dialogs like numpad or keypad

Element-Bar-GraphColor

Element-Bar-ScaleColor-> used for the barelement

Element-Button-FontColor-> for the button and time selector

Element-Meter-ArrowColorElement-Meter-LabelFontColorElement-Meter-ScaleColor-> for the meter

Element-Potentiometer-LabelFontColorElement-Potentiometer-ScaleColor

-> for the potentiometer

Element-Table-SelectionColor-> for the table

http://jira/browse/CDS-39404http://jira/browse/CDS-39404http://jira/browse/CDS-39404http://jira/browse/CDS-39404


8/15



Arbitrary Values:Dialog-UseHeaderColor-> for the dialogs, see explanation in example style

Element-MeterElement-Potentiometer

-> for the positioning of scale, see more details to different values in example style

Visu: Semi-transparent drawing (CDS-17581) With the new feature transparent, drawing semi-transparency can be configured by several elements, such asthe fill color of a rectangle or a polygon. For the web visualization, a target setting does not have to be set. Forthe target visualization, the feature must be activated by the device description because additional functionalityis necessary in the device.

The following setting must be set in the device description:

1

3.2 Compatibility Information for OEMs

All Platforms: Implement SysCpuGetContext() + SysCpuGetCallstackEntry2() (CDS-21148)

This feature can be used only with the following:- Compiler version >= 3.5.1.0- On the following platforms, a compiler definition must be specified in the DevDesc to enable a back trace onstacks in the runtime system code (external library calls). See CDS-23192:

ARM, CortexM3, MIPS, PPC, SH, x86-64 and x86/WindowsCE

generate_exceptioninfo

- Runtime system >= v3.5.6.0

Implementations:

- New interface function added to detect the call stack out of an external library call:RTS_RESULT CDECL SysCpuGetCallstackEntry3(RTS_I32 bIecCode, RegContext *pContext, void**ppAddress);

- SysCpuHandlingOS have to implement the following new helper function:RTS_UINTPTR *SysCpuSearchOnStack_(RTS_UINTPTR *pSP, RTS_UINTPTR pattern, RTS_RESULT*pResult)

- If SysCpuGetCallstackEntry2(RTS_I32 bIecCode, RTS_UINTPTR *pBP, void **ppAddress) at the OSimplementation returns ERR_NOTIMPLEMENTED, we do a generic back trace on the stack inSysCpuGetCallstackEntry3()

Known Issues:

- On WinCE / ARM, an exception in an external C-function cannot be caught by the runtime and it still leads tocrashes (CDS-41404).

http://jira.3s-software.com/browse/CDS-17581http://jira.3s-software.com/browse/CDS-17581http://jira.3s-software.com/browse/CDS-17581http://jira.3s-software.com/browse/CDS-21148http://jira.3s-software.com/browse/CDS-21148http://jira.3s-software.com/browse/CDS-21148http://jira.3s-software.com/browse/CDS-21148http://jira.3s-software.com/browse/CDS-17581


9/15



Watchdog: In the logger, the OmittedCycle watchdog must be separated from "normal" CycleExceed watchdog(CDS-40328) To separate an OmittedCycle watchdog from a "normal" watchdog, the following new exception number isprovided (e.g. in the event CMPID_CmpApp :: EVT_CmpApp_Exception as ulException parameter):

RTSEXCPT_WATCHDOG_OMITTED_CYCLE | RTSEXCPT_WATCHDOGSee SysExceptItf.h for details.

NOTE:Therefore, if you are not interested in the OmittedCycle watchdog, you have to disable this info to obtain onlythe RTSEXCPT_WATCHDOG exception with:if ( SysExcptIsException(ulException, RTSEXCPT_WATCHDOG) )

...= 3.5.6.0- In the DevDesc, you have to specify the following setting (see CDS-41052):

1

- On the following platforms, a compiler define must be specified in the DevDesc to enableback trace on stack in runtime system code (external library calls). (see CDS-23192):ARM, CortexM3, MIPS, PPC, SH, x86-64 and x86/WindowsCE

http://jira/browse/CDS-40328http://jira/browse/CDS-40328http://jira/browse/CDS-40328http://jira.3s-software.com/browse/CDS-38789http://jira.3s-software.com/browse/CDS-38789http://jira.3s-software.com/browse/CDS-38789http://jira/browse/CDS-40305http://jira/browse/CDS-40305http://jira/browse/CDS-40305http://jira/browse/CDS-39807http://jira/browse/CDS-39807http://jira/browse/CDS-39807http://jira/browse/CDS-39807http://jira/browse/CDS-38927http://jira/browse/CDS-38927http://jira/browse/CDS-38927http://jira/browse/CDS-38927http://jira/browse/CDS-38927http://jira/browse/CDS-38927http://jira/browse/CDS-39807http://jira/browse/CDS-39807http://jira/browse/CDS-40305http://jira.3s-software.com/browse/CDS-38789http://jira/browse/CDS-40328


10/15



generate_exceptioninfo

- Runtime system >= v3.5.6.0


11/15



4 Known Restrictions

Component Description JIRA ID

Return of licenses (LicenseManager

Not supported for device licenses

64-bit RTE CANopen on 64bit version is notsupported.

CDS-26049

64-bit Control Win Setup available in customerdownload area

64-bit Libraries Missing 64-bit support forfieldbus libraries

CDS-27530, CDS-27547, CDS-27543, CDS-27532

CmpHilscherCIFX: 64bit driver CAN, DeviceNet and EthernetIPare not available for this releasefor 64-Bit Targets. This portation

is covered by separate jiras(CDS-27545, CDS-41339 andCDS-41343).

CDS-29568

CmpSchedule: Improvement ofwatchdog handling

This improvement does not workon Linux and on VxWorks PPC

CDS-42284

WebServer: SSL support Not supported on Control RTEand Control RTE x64, QNX andVxWorks

CDS-29361

OpenSSL Available for webserver as aruntime component, no supportfor RTE, QNX and VxWorks

CDS-39063

Profinet I/O Master Stack Detach/Reconnect ProfinetSaves from network: If this isrepeated several times with alarge number of slaves,connection fails (CDS-42267)

Only one controller instance perPLC possible (CDS-41822 +CDS-41780), in case of RTE theused network interfaces have tobe of the same type (CDS-37463)

A mix of CIFX-based and 3SController in the same project ispossible, but some IDE functions(using communication to PLC)do not work reliable:

Status-Page: Diagnosis-Dataand Alarms are not shown.

Scan-Dialog: Functions “GetI&M-Data” and “Reset toFactory” don’t work.

CDS-35127

QNX The QNX runtime is not availableat the time of the release.

http://jira/browse/CDS-26049http://jira/browse/CDS-27530http://jira/browse/CDS-27547http://jira/browse/CDS-27543http://jira/browse/CDS-27543http://jira/browse/CDS-27532http://jira/browse/CDS-27532http://jira.3s-software.com/browse/CDS-29568http://jira.3s-software.com/browse/CDS-29568http://jira.3s-software.com/browse/CDS-42284http://jira.3s-software.com/browse/CDS-42284http://jira/browse/CDS-29361http://jira/browse/CDS-39063http://jira/browse/CDS-39063http://jira.3s-software.com/browse/CDS-42267http://jira.3s-software.com/browse/CDS-42267http://jira.3s-software.com/browse/CDS-42267http://jira.3s-software.com/browse/CDS-41822http://jira.3s-software.com/browse/CDS-41822http://jira.3s-software.com/browse/CDS-41822http://jira.3s-software.com/browse/CDS-41780http://jira.3s-software.com/browse/CDS-41780http://jira.3s-software.com/browse/CDS-37463http://jira.3s-software.com/browse/CDS-37463http://jira.3s-software.com/browse/CDS-37463http://jira.3s-software.com/browse/CDS-37463http://jira.3s-software.com/browse/CDS-35127http://jira.3s-software.com/browse/CDS-35127http://jira.3s-software.com/browse/CDS-35127http://jira.3s-software.com/browse/CDS-37463http://jira.3s-software.com/browse/CDS-37463http://jira.3s-software.com/browse/CDS-41780http://jira.3s-software.com/browse/CDS-41822http://jira.3s-software.com/browse/CDS-42267http://jira/browse/CDS-39063http://jira/browse/CDS-29361http://jira.3s-software.com/browse/CDS-42284http://jira.3s-software.com/browse/CDS-29568http://jira/browse/CDS-27532http://jira/browse/CDS-27543http://jira/browse/CDS-27543http://jira/browse/CDS-27547http://jira/browse/CDS-27530http://jira/browse/CDS-26049


12/15



5 Features and Changes / Addressed Defects

The link below leads to an Excel sheet which contains information on the new implementations and changes inthe current version:

Key, Summary, Description, Resolution, Priority, Issue Type, Components, Target User Group, Fix Version,

Release Note

Special release information for OEM partners can be found in the RID note with the filter ‘Target User Group’ for‘OEM’ or ‘OEM and End User’.

Features and Changes_Addressed Defects CODESYS V3.5 SP6 Patch 4.xls

OPC UA Server (CDS-5499)

An OPC UA server is now available as a runtime system component. The OPC UA server actuallysupports the "Micro Embedded Device Server Profile". OPC UA will ship by default with CODESYS ControlWin V3, CODESYS Control RTE V3 and CODESYS Control for Raspberry Pi.

http://server01/Daten/Qualit%C3%A4tssicherung/UpToDate/Releases/V3/Releases_CoDeSys_v3/V3.5/CODESYS%20V3.5%20SP6%20Patch%204/Features%20and%20Changes_Addressed%20Defects%20CODESYS%20V3.5%20SP6%20Patch%204.xlshttp://jira.3s-software.com/browse/CDS-5499http://jira.3s-software.com/browse/CDS-5499http://jira.3s-software.com/browse/CDS-5499http://jira.3s-software.com/browse/CDS-5499http://server01/Daten/Qualit%C3%A4tssicherung/UpToDate/Releases/V3/Releases_CoDeSys_v3/V3.5/CODESYS%20V3.5%20SP6%20Patch%204/Features%20and%20Changes_Addressed%20Defects%20CODESYS%20V3.5%20SP6%20Patch%204.xls


13/15



6 Release Information

This chapter describes the tests conducted during the release of the above mentioned version and thecorresponding results.

Test Environment Result

CAN RTE Passed / Released

Compatibility Passed / Released

Compatibility - Internal(Autotest)

Passed / Released

Compatibility (Autotest) Passed / Released

Compatibility Libraries(Autotest)

Passed / Released

Compatibility RTS Passed / Released

Compile (Autotest) x86 Passed / Released

Compile (Autotest) PPC Passed / Released

Compile General (Autotest) Win7/64 Bit Passed / Released

EtherCAT Control RTE Passed / Released

EtherCAT (Autotest)Control RTE, Ethernet Chip Intel Pro 100Control RTE, WinXP/32 Bit

Passed / Released

EtherCAT (Autotest) Linux, PPC Passed / Released

EthernetI/P (Autotest)Standard EthernetControlWin

Passed / Released

Example Applications(Autotest)

Passed / Released

FBD Win8/32 Bit Passed / Released

FBD_Codegen Passed / Released

Flow Control - LD/FBD Passed / Released

IEC Variable Access (Autotest) Passed / Released

IO Configuration Passed / Released

IO Configuration (Autotest) Passed / Released

LD Passed / Released

LD_Codegen Passed / Released

Licensing Gate (Autotest) Passed / Released

Monitoring Passed / Released

Monitoring (Autotest) Passed / Released

Online Change (Autotest) WinControl V3 Passed / Released

Online Help - Patch Passed / Released

OPC Server UA ControlWin Passed / Released

OPC Server UA Control PPC Passed / Released


14/15



OPC Server UA Control Raspberry PI Passed / Released

Performance - Internal(Autotest)

Passed / Released

Performance (Autotest) Passed / Released

Performance (Autotest) Passed / Released

PLC Handler Win7/32 Bit Passed / Released

PLC Handler (Autotest) Windows Passed / Released

Profibus - Online NetX Passed / Released

Profinet (Autotest)Control RTE APIC Win7/32 BitIEC-Stack

Passed / Released

Quality Gate Passed / Released

Runtime - Full (Autotest) Win7, Control Win Passed / Released

Runtime - Full (Autotest) Control RTE, Win7/32 Bit Passed / Released

Runtime - Full (Autotest) Control RTE 64 Bit, Win7/64 Bit Passed / Released

Runtime - Full (Autotest) Control Win, Win7/64 Bit Passed / Released

Visualization - Online - QualityGate

Target Web VisuWeb Server: Control WinBrowser: Chrome, Win7

Passed / Released

Visualization - Online(Autotest)

Target VisuRuntime: ControlWin, Win7

Passed / Released

Visualization - Online(Autotest) - Quality Gate

Win7, Control Win, Target Visu Passed / Released

Visualization - Online(Autotest) - Quality Gate

Win7, Control Win, Integrierte Visu Passed / Released


15/15


Document Release

Created Monika Gottwald QA 20.05.2015

Reviewed Benjamin Schurr QA 28.05.2015

Released Benjamin Schurr QA 28.05.2015

release information codesys_v3.5 sp6 patch 4

Documents