Release notes for version
This article contains the release notes for logi.CAD 3 version 3.23.1.
Up-to-date informationen within online-version
Please check the online-version (provided under http://help.logicals.com/) whether new pieces of information have been added since this user manual (as PDF/HTML/Word) has been published; e.g. the release notes quote new problems or there are new articles in the troubleshooting- or FAQ-section.
The online-version of the release notes for logi.CAD 3 is available under: https://help.logicals.com/lco3docu/latest/user-documentation/de/release-notes-fuer-version – Use the version picker (above the
table of contents) to switch to the relevant version of
logi.CAD 3.
Release-Notes for previous versions of logi.CAD 3 are provided in the online-version under https://help.logicals.com/lco3docu/latest/user-documentation/en/release-notes-fuer-version only.
General information
About compatibility: |
If you have used a previous version of logi.CAD 3 and you want to use the current version, see "Are my projects upwards and downwards compatible?" for important information. Recommended, if you are using projects that have been created in a previous version of logi.CAD 3: Clean the imported projects.
|
On the Log4j security vulnerability: |
See "Is the IDE affected by the Log4j security vulnerability (December 2021, CVE-2021-44228, Log4Shell)". |
About system libraries: |
|
About the illustrations in the IDE documentation: |
Depending on the configuration of your logi.CAD 3 version, the FBD-editor and its elements might be displayed differently in your logi.CAD 3 version than illustrated in the IDE documentation. This is the case, if logi.cals or the system integrator has changed the styles for the FBD-editor. Subsequently, the illustration in the IDE documentation are symbolic images and the representation in your logi.CAD 3 version takes precedence for the valid representation. In case of doubts, please contact logi.cals or your system integrator. See "Color and style for FBD-elements determined by data type" for details. |
General information for runtime system and target systems
About the →runtime system : |
If you are using logi.CAD 3 version 3.23.1, install and use the version 5
.18.0
of the runtime system.
If you are using an older version of the runtime system, it might not be possible to successfully connect to the target system from within logi.CAD 3 (see troubleshooting article "No connection to the target system, but there are error messages)". |
About →Raspberry Pi : |
See the tutorial "Putting Raspberry Pi into operation" which version is recommended by logi.cals for usage. |
New features in logi.CAD 3 version 3.23.1
The new features for previous versions are listed in the release notes for the previous versions, e.g. in the release notes for V3.23.0
This section informs you about the latest new features for this version.
ID |
Component |
New feature |
62558 |
Safety-relevant application, Building the application |
The HTML-report that is generated when the application is built (also called build report) does now contain the information whether a task is defined as IO task. This information is displayed along with the other data for the program structure. This new information is of particular interest when building safety-related applications. |
62386 |
Safety-relevant applications, FBD-editor |
If you are creating safety-relevant applications, keep in mind that calls of blocks are no longer automatically updated when you open the FBD-editor if the interface for the blocks has changed in the interface editor. However, you remain able to update a changed interface yourself by selecting the call and pressing Ctrl+1 or the F5-key. You can find more details on the update under "Updating existing calls for changed interfaces". |
56347 |
Safety-relevant application |
When developing a safety-relevant application, IOs can be accessed by assigning IEC hardware addresses to global variables in the PLC application. To grant this possibility, the following statements/keywords are now supported:
Observe that you need to follow some safety-specific instructions when IOs are accessed. For instance, it is necessary to perform an IO test. See the logi.CAD 3 document "Safety instructions on working with the IDE", article "Warnings/notes for accessing IOs" for all safety-specific instructions relating to accessing IOs. |
62945, part 1 |
Safety-relevant application, |
Elemens have been provided as new features since the logi.CAD 3 version 3.16.2 that has been qualified as a version for developing safety-relevant applications and/or libraries for them. The following list contains new features and changes that are relevant to the user when using version 3.23.1 (instead of version 3.16.2) for the purpose of developing safety-relevant applications and/or libraries. New safety-relevant features for V3.23.1:
Added safety-relevant restrictions for V3.23.1:
The document "Safety instructions on working with the IDE" has been updated to reflect the changes to version 3.23.1. See "Safety instructions on working with the IDE" for information on this document (incl. on its release and detailed changes). Also check the list provided under "Changes affecting the code generation" for changes that affect the automatically generated C-code (and thus the built application), even if you do not make any changes in the safety-relevant application yourself. |
62945, part 2 |
Safety-relevant application, |
The following list contains new features and changes that are relevant to the system integrator when using version 3.23.1 (instead of version 3.16.2) for the purpose of developing safety-relevant applications and/or libraries.
Also check the changes for the user (see ID "62945, part 1") whether those new features and change might have an additional impact on the integration of logi.CAD 3 into a safety-related system. As mentioned in the list: The document "Integraton Manual" has been updated to reflect the changes to version 3.23.1. This integration manual is only provided in the package for the qualified version of logi.CAD 3. Contact logi.cals, if you are interested in this package and/or the integration manual. |
New features relating to the runtime system and target systems
ID |
Component |
New feature |
|
|
none |
Fixed problems in logi.CAD 3 version 3.23.1
The fixed problems for previous versions are listed in the release notes for the previous versions, e.g. in the release notes for V3.23.0
ID |
Component |
Fixed problem |
60996 |
Application navigator |
Renaming a program instance may also change the name of the PLC-object. |
61082 |
Access control |
It is possible to delete resources without the appropriate access control rights when using the quick access search bar. |
61086 |
Access control |
It is possible to rename resources without the appropriate access control rights when using the quick access search bar. |
61094 |
Opening help |
The local help is not opened for the PLCopen blocks. |
61158 |
Access control |
It is possible to open the project settings without the appropriate access control rights when using the quick access search bar. |
61162 |
Access control |
The access control configuration of one project with the deactivated feature "Edit access control configuration" can be manipulated after copying files from a different project with activated feature. |
61179 |
Access control |
An exception is caused when selecting the command "Access Rights..." in the application navigator. |
61191 |
Access control, artifact identity |
In case of the deactivated feature "Edit application logic", the file for the artifact identity is not created when saving an already changed editor under a different name. |
61203 |
Access control |
An exception might be caused when importing an existing access rights configuration. |
61395 |
Access control |
An exception is caused when creating a project, if the IDE was started with enabled access control and with the -noSplash option. |
62166 |
IDE Documentation |
The online help, local HTML help, and PDF files might not contain the complete list of blocks with internal error diagnostics.
Additional information: The problem affects the online help prior to October 10th, 2023 but also local HTML helps and PDF files created for this release and/or previous releases. |
62748 |
FBD-editor, global variables |
The list of the declared variables might still display the changed data type although the change for the data type has been undone. |
62759 |
Application navigator, global-object |
Dragging and dropping a global variable with a physical address onto the POU within the application navigator creates a faulty external variable. |
62764 |
FBD-editor, external and global variables |
Information are not transferred to the external variable, if a global variable is dragged into the FBD-editor. |
62769 |
Global-object, Application navigator |
Deleting a global-object causes the PLC-object (containing a reference) to be highlighted as faulty. |
62893 |
FBD-editor, IDE documentation |
When pasting a value field with a variable for an existing FBD-element, the IDE documentation differs from the implementation.
In reality, the existing FBD-element is highlighted as faulty, namely the connector Motor1. |
63454 |
FBD-editor |
Overlapping lines prevent the clear determination of the connected FBD-elements. |
107232 |
FBD-editor, safety-relevant applications |
The call of a function block in a value field is incorrectly highlighted as safe logic. |
107650 |
Safety-related applications, Building the application |
The SEL_DWORD block cannot be used in safety-related applications. |
107660 |
IDE documentation, PLCopen blocks |
Information about particular DiagCode is not included in the HTML help for 3 PLCopen blocks.
Additional information: The information is not included in the HTML help for V3.23.0 and V3.23.1. However, it was added to the online help as of V3.23.1 in the middle of November. |
Changes affecting the code generation
The following changes in logi.CAD 3 version 3.23.1 affect the automatically generated C-code (and thus the built application), even if you do not make any changes in the application yourself. Observe that when you load the application, the changed code will be loaded onto the PLC.
Change |
Starting with version |
More information on the change |
Changed specification -0.0 in the C-code (when -0.0 has been entered in the ST-code) SAFETY |
V3.21.0 |
See ID "56121" in the release notes of the specified version |
Inserted cast LC_TD_REAL or LC_TD_LREAL in the automatically generated C-code (when REAL#-0.0 or LREAL#-0.0 has been entered in the ST-code as typed literal)SAFETY |
V3.21.0 |
See ID "55996" in the release notes of the specified version |
Changed result when dividing the minimum value for a data type by -1 and for a return value of the same data type SAFETY |
V3.22.0 |
See ID "56417" in the release notes of the specified version |
Changed order for statements within an FBD network with a feedback loop (in the default configuration) SAFETY |
V3.22.0 |
See ID "57509" in the release notes of the specified version |
Changed order for statements within an FBD network with a feedback loop (in the case of -Dlc3.fbdPreserveFunctionOutputs=TRUE ) |
V3.22.0 |
See ID "57550" in the release notes of the specified version |
Changed determination of the memory size for the SIZEOF block: new determination by the data type of the input IN, formerly: determination by the transferred element |
V3.23.0 |
See ID "60072" in the release notes of the specified version |
Restricted usage for the SIZEOF block, MEMCMP block, MEMCPY block and MEMSET block |
V3.23.0 |
See ID "60072" in the release notes of the specified version |
Improvement of a suboptimal definition of the values for true and false; This does not change the generated code but it is possible that a different binary code is generated. |
V3.23.0 |
See ID "60586" in the release notes of the specified version |
Note: The flag SAFETY means that the change must be taken into account in particular when developing safety-relevant applications. A change without this flag applies to a functionality/configuration which is not supported for the development of safety-relevant applications. |
Known problems in logi.CAD 3 version 3.23.1
ID |
Component |
Known problem |
49494 |
Application navigator, |
When several function blocks have been created in the same ST object, the command "Delete" in the application navigator deletes all function blocks in this ST object without any previous information. |
49498 |
Application navigator |
The command "Go Into" in the application navigator does not behave as expected. |
59175 |
Teaming up to create applications, vendor blocks |
The automatically generated H-/C-files for vendor blocks are not automatically locked. The editor for them is not opened in a read-only mode. |
59213 |
"Instances" view, vendor blocks |
The fingerprint of the application is not updated in the "Instances" view when changing C-sources. |
59774 |
Building the application |
Changed applications for PTK GCC 10.2.x may fail to build. ninja: error: FindFirstFileExA(c/:/prj/bur/saturn/runtime-spdesigner/counter1/src-gen): The filename, directory name, or volume label syntax is incorrect. Additional information: The problem occurs only if the platform toolkit does not contain the forceRebuild setting or the setting is set to FALSE. |
59779 |
FBD-editor, memory consumption |
A memory leak occurs when scrolling through extensive FBD-objects.. |
60255 |
FBD-editor, "Problems" view |
The quick fix to resolve errors in the"Problems" view may not work.
Workaround: none existing |
60268 |
Test framework |
A test suite with a name that is too long cannot be exported to Excel. 'Exporting test suite to Excel' has encountered a problem. An internal error occurred during: 'Exporting test suite to Excel' Cannot invoke 'org.osgi.framework.BundleContext.getBundle()' because the return value of 'com.logicals.lc3.api.common.BundleInformation.getBundleContext()' is null Workaround: Shorten the name of the test suite. |
60476 |
IDE documentation |
The order of 2 illustrations in an article of the IDE documentation is wrong. |
60703 |
Validating the application |
Syntax errors might be caused when using the content assist to suppress warnings for rule violations.
Workaround: none existing |
60726 |
IDE |
The changed file association is ignored for opening a data type from a library configuration. |
60771 |
Migration |
The migration of constants may cause an error in the target project. |
60776 |
LD-editor |
No emphasis is displayed when reconnecting existing link elements within the LD-editor. |
60783 |
Access rights |
A dialog for saving the changes is displayed by mistake. |
60825 |
Interface editor |
The preview of the interface editor is not updated correctly when undoing the creation of a value field. |
60829 |
Interface editor |
It may not be possible to undo the creation of a comment field within the interface editor. |
60833 |
Interface editor |
The deletion of elements within the interface editor may need to be undone twice. |
61171 |
Teaming up to create applications |
The "Team Monitor" view does not determine the status changes on the team server at the expected interval. |
61175 |
Access control |
It is possible to turn a folder into a namespace folder and vice versa without the appropriate access control rights to edit the application logic.
Workaround: none existing |
61183 |
Access control |
It is possible to assign a USING instruction for accessing a namespace folder and delete this instruction without the appropriate access control rights to edit the application logic.
Workaround: none existing |
61187 |
Artifact identity |
The artifact identity is not created/updated when turning a folder into a namespace folder or assigning a USING instruction for accessing a namespace folder. |
62735 |
List of declared variables |
A STRING variable cannot be changed in the dialog. |
62839 |
OLT-field |
Special characters within OLT fields are not evaluated as expected when debugging an application. |
106944 |
List of the declared variables |
The initial value of declared variables might not be changed. |
106952 |
Properties field, FBD-editor |
The application cannot be built if the characters * / are contained in a property field in FBD. The application for the PLC (resource "name1" , platform toolkit "name2" ) cannot be created/loaded. Check the views "Error Log" and "Problems" for more information. An error occurred during compiling or linking the code image (error code: 1 ). Workaround: Do not use the characters * / in the string literal on the right side of the assignment operator ":=". |
106958 |
ST-editor |
The application cannot be built if the characters */ are contained in a property field in ST. The application for the PLC (resource "name1" , platform toolkit "name2" ) cannot be created/loaded. Check the views "Error Log" and "Problems" for more information. An error occurred during compiling or linking the code image (error code: 1 ). Workaround: Do not use the characters */ in the string literal on the right side of the assignment operator ":=". |
107041 |
Application navigator, global-object |
A global-object can be renamed to an invalid name in the application navigator. |
107075 |
FBD-editor |
The call of a block can be enlarged, although this should not be possible. |
107327 |
Global-variables-editor |
The global-variables-editor might not display the expected icon for some variables.
This means that the icon
or
is displayed for such variables in the global-variables-editor. But only the icon
should be used for this. |
107348 |
Building the application |
Building an application might lead to linker warnings. |
107379 |
FBD-editor |
The IDE documentation differs from the implementation in a special case for replacing a block call.
Here is the illustration from the IDE documentation in which the value field with the access SR1.Q1 became faulty after a block SR has been replaced by a block TON: |
107391 |
ST-Editor, building the application |
It might not be possible to build the application due to a called method. The application for the PLC (resource "name1" , platform toolkit "name2" ) cannot be created/loaded. Check the views "Error Log" and "Problems" for more information. An error occurred during compiling or linking the code image (error code: 1 ). After the attempt to build the application, the messages are displayed in the Problems view. Here are the messages for the customer scenario in which the problem occurred: 'LC_VD_GAUC_TESTARRAYGLOBALVAR' undeclared (first use in this function) expected expression before 'LC_TD_FunctionBlock_APPLICATIONCOREx2EFB_TESTFB' expected expression before 'LC_TD_FunctionBlock_APPLICATIONCOREx2EFB_TESTFB' implicit declaration of function 'LC_GV_ACCESS_ARRAY' ; did you mean 'LC_GV_ACCESS_FB' ? [-Werror=implicit-function-declaration] Workaround: none existing |
107403 |
Applikation navigator, namespaces |
Moving/copying a subfolder into a namespace folder does not update the namespace for the included objects. |
107419 |
Applikation navigator, namespaces |
Objects in nested namespace folders do not have a nested namespace. |
107430 |
Global-variables-editor |
Undoing/Redoing the delete action for all sections does not work as expected. |
107517 |
Building the application, ST-editor, FBD-editor |
It is not possible to build the application, if a function block variable is assigned to the ANY input of a function block. Example in ST
PROGRAM MyTest VAR rs1 : rs; END_VAR SEL(IN0 := rs1); (* The input 'IN0' of 'SEL' is declared with the generic data type 'ANY' . *) END_PROGRAM In this case, the following messages are displayed: Faulty source files. The application for the PLC (resource "name1" , platform toolkit "name2" ) cannot be created/loaded. Check the views "Error Log" and "Problems" for more information. An unexpected error occurred: File <path>\<project>\src-gen\lcpu___mytest.c is missing. Additional information: The problem also occurs in the FBD-editor. There, the line between the value field containing the function block variable and the ANY input of the function block is highlighted as faulty. The following error message is reported by mistake for this line: Safety conflict: The unsafe output cannot be assigned to a safe input. Workaround: none existing |
107558 |
FBD-editor |
The initialization of structure elements is not possible when creating a new structured variable via the content assist. |
107563 |
FBD-editor |
An exception is caused by a wrong array initialization when creating a new structured variable via the content assist. class com.logicals.lc3.api.model.st.pou.impl.ArrayConstantImpl cannot be cast to class com.logicals.lc3.api.model.st.expression.StructureConstant (com.logicals.lc3.api.model.st.pou.impl.ArrayConstantImpl and com.logicals.lc3.api.model.st.expression.StructureConstant are in unnamed module of loader org.eclipse.osgi.internal.loader.EquinoxClassLoader @9dada78 ) ... Workaround: Go the the list of the declared variables and double-click the created variable to open the dialog to modify its data. In the field Initial value, delete the wrong initial value 1 for the above example. Accept the changes in the dialog and save the FBD-editor. |
107568 |
List of the delared variables |
An exception is caused when initializating structure elements while creating a new structured variable in the list of the declared variables.
Workaround: First, create the variable without the intial value. Then double-click the created variable to open the dialog again. In the field Initial value, enter the initial value, e.g. (Elem1 := true) for the above example. |
107681 |
FBD-editor |
When using the content assist to create new variables, a possible conflict to existing variables of another variable section is not reported. The existing variable is automatically used. |
107713 |
Access control |
An exception might be caused when importing an existing access rights configuration. |
If your problem is not listed in this list, check these sections: Troubleshooting and FAQ
Addendum: Known issues after the release of logi.CAD 3 version 3.23.1
This section was last updated on: 2023-12-13
For issues discovered after the release of logi.CAD 3 version 3.23.1, please refer to the release notes of the successor versions. Both the list of known problems and the list of fixed problems might contain descriptions of problems that are relevant for logi.CAD 3 version 3.23.1.
Issues that have been reported after the successor version has been released are listed below. This list is updated at regular intervals (see the date after the section heading). If you need more up-to-date information, please contact logi.cals .
ID |
Known problem |
58528 |
Formatting the PLC object might cause an error in the specifications for PARAMS. As a result, it is not possible to load the application onto the PLC. Example of specifications for communication with the gateway
{ TARGET usRTSTarget_Win PARAMS := '{ (* other data *) }, "infrastructure" : { (* other data *) "parameters" : { "programmerExec" : "<at:var at:name=" PROGRAMMER " />" , "programmerParam" : "<at:var at:name=" FILENAME " /> C:\\temp\\RTSCode.upload.dll" , (* other data *) } } }'; END_TARGET } If you format the code in the PLC object using the context menu command Source, Format or the keyboard shortcut Ctrl+Shift+F, the path specification after "programmerParam" is reformatted incorrectly, as spaces are inserted before and after the : character. So, the example C:\\tempRTSCode.upload.dll becomes: C : \\tempRTSCode.upload.dll |
107259 |
Unexpected behavior of features in the case of the missing configuration variable -Dlc3.serverport=50055. |
107764 |
FBD-elements are highlighted as faulty in the opened FBD-editor, if the corresponding C-file has been opened while cleaning the project. |
107789 |
The sort order might not be as expected, when moving multiple global variables or sections in the global-variables-editor. |
107784 |
The document "Safety instructions on working with the IDE" (version 3.0) included in the local HTML-help does not contain some restrictions.
Even if the above items are not listed in the section "List of unsupported and restricted elements" of the document in version 3.0, you must not use the specified section when developing safety-relevant applications. Regarding the external libraries for vendor blocks, contact the system integrator whether these libraries may be used when developing safety-relevant applications. |
108037 |
An exception occurs during the SiL/PiL test for a library block. |
108015 |
The IDE documentation on the safety parameter editor does not contain information on the valid range for floating point value.
Moreover, if a specified value cannot be precisely interpreted as a floating-point number, the safety parameter editor corrects the value to the corresponding floating-point number.
Workaround after 12 December 2023: See the article " Viewing or changing the current parameter values " in the online documentation for the information on the floating point values (as specified as above under "Additional information on the floating-point values"). |
108088 |
The initial value of declared variables might not be changed. |
108128 |
Specific notations for duration literals, date and time literals and time of day literals are not supported when defining intial values for outputs in the test case.
If you use this notations, the tests will be failing because the intial values are not considered as expected. Workaround: Use this notation to define the initial value in the test case:
|
108006 |
The integration manual does not contain information that some time tests depend on the timer frequency of the target system and how to proceed if the target system uses a different timer frequency than 1 kHz or 10 kHz.
As the expected values of the tests depend on the timer frequency of the target system, these tests might fail, if the target system uses a different timer frequency than 1 kHz or 10 kHz. |
108185 |
Wrong C-code is generated, if you call a function block instance declared as an in-out variable. Subsequently, it is possible that memory on the PLC is overwritten. Example
FUNCTION_BLOCK MyFBwithIO VAR_IN_OUT iMyFB1 : MyFB1; (* The function block 'myFB1' is used as type for the function block instance declared as in-out variable. *) END_VAR iMyFB1(); (* Here the function block instance is called. *) END_FUNCTION_BLOCK FUNCTION_BLOCK MyFB1 ... END_FUNCTION_BLOCK Workaround 1: Do not declare a function block instance as an in-out variable. |
Checksum for components of logi.CAD 3 version 3.23.1
Component |
Version |
Checksum |
Description |
logi.CAD 3 IDE |
version 3.23.1 |
c64a170987e709afd5aa0ea21530020c |
checksum of configuration\com.logicals\application.md5 (in relation to the installation folder of logi.CAD 3) |
system library Standard |
version 3.6.0 |
639b002d2100561b900f7d214cc1cc7a |
checksum of index.md5, contained in plugins\com.logicals.library.lc3lib_3.23.1\libautoinstall\com.logicals.lc3.library.standard__3.6.0.ZIP (in relation to the installation folder of logi.CAD 3) |
system library PLCopen Safety |
Version 1.1.0 |
0956a48b08a7d9380ec23e3118a0c355 |
checksum of index.md5, contained in libraries\autoinstall\com.logicals.lc3.library.safety.plcopen__1.1.0.ZIP (in relation to the installation folder of logi.CAD 3) |