Release notes for version
This article contains the release notes for logi.CAD 3 version 3.19.0.
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.
|
On the Log4j security vulnerability: |
See "Is the IDE affected by the Log4j security vulnerability (December 2021, CVE-2021-44228, Log4Shell)". |
About system libraries: |
|
Enum-Editor (53638 |
The graphical enum-editor to be used to edit and create enums (= data types with named values) has been disabled in logi.CAD 3 version 3.19.0 due to known bugs. As a consequence, you can edit and create enums only with the textual ST-editor in logi.CAD 3 version 3.19.0. See " Declaration of a data type with named values (enums) in ST " for the necessary ST-syntax. Additional Information: If the release notes for version 3.19.0 contain additional items for the enum-editor, these items are not relevant for version 3.19.0. |
General information for runtime system and target systems
About t he →runtime system : |
If you are using logi.CAD 3 version 3.19.0, install and use the version 5
.16.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.19.0
ID |
Component |
New feature |
48701 |
In the application navigator, it is now possible to copy and paste a resource by dragging and dropping the resource while holding the Ctrl key. So far, this action has only been possible by using the commands Copy and Paste in the context menu of the object. |
|
48706 |
Application navigator |
The button Link with Editor is now also supported in the application navigator. This means that changing the active editor updates the selection in the application navigator as well. |
48710 |
Application navigator |
When copying and pasting a namespace folder in the application navigator, the namespace of the pasted objects is adjusted to the new name of the namespace folder. Previously, the namespace of the original namespace folder has been kept for the pasted objects. |
48840 |
Project explorer, |
In the project explorer and application navigator, read-only folders are displayed with the decorator at the name. It is not possible to create new objects/folders in such a read-only folder within the application navigator. Note: Usually, only a system integrator or administrator makes a folder of the project to be a read-only folder. Therefore, the documentation "Administrator's Manual" contains the information on how to do this. |
52266 |
Vendor blocks,
|
logi.CAD 3 provides the possibility to create vendor blocks in C and integrate them into your custom library. The logi.CAD 3 user documentation contains now instructions how to do this. See "Creating vendor blocks for the application or a library". So far, these instructions have been provided in the documentation "Administrator's Manual". |
52419 |
Application navigator |
It is now possible to delete projects in the application navigator. This possibility is analogous to the one in the project explorer, See "Deleting project" if you need information about the option Delete project contents on disk (cannot be done) in the dialog. |
52452 |
Headless tools |
logi.CAD 3 provides a new command line interface (also known as headless tools) that allows you to create a project. Details: See "Automated creating of projects". |
52588 |
Creating custom libraries |
The statement BASE_TEST_SOURCE in a library configuration is now also supported for the standard library type LOGICAD but only in specific variants of logi.CAD 3. This statement is only relevant, if a library element is tested by using the test framework. |
52819 |
Creating projects |
If you select the project template logi.CAD 3 Project ... in the start dialog of the project wizard, the project wizard displays another dialog to select the actual project template. Depending on your logi.CAD 3 configuration, this dialog might list further project templates. In this case, select the best suited project template before you enter the project name and the position of the new project in the concluding dialog of the project wizard. For the other project templates, you directly go from the start dialog of the wizard, where you select the project template, to the concluding dialog, where you specify the project name and the position of the new project. |
53407 |
ST-editor |
The pragma "{ DoNotValidateThisFile ('') }" can be used to ignore elements in an ST-object when validating the application. When using a previous version of the library, errors/warnings regarding such library elements will still be reported when a project has been cleaned, although the basic ST-object did contain the pragma "{ DoNotValidateThisFile ('') }". |
53524 |
global-variables-editor |
Global variables are declared and edited in the global-variables-editor. It is also possible to enter a description and a comment for the global variable. Until now, the ' character was not supported for this. |
TF-1831 |
Test framework |
The test framework is providing the possibility to consider the initial value of a local variable specified within the application when a test is executed. For this to work, you must enter the new test mode useImplValue in the worksheet Defaults of the test suite, delete the specified initial value in this worksheet and delete the column for this variable in the worksheet for the test case. See "Example 5: Test case for addition with initial value of a local variable" for more information about the necessary steps. |
New features relating to the runtime system and target systems
ID |
Component |
New feature |
|
|
none |
Fixed problems in logi.CAD 3 version 3.19.0
ID |
Component |
Fixed problem |
52170 |
Importing projects |
An exception might occur when importing several projects from an archive. |
52309 |
Application navigator |
The content of Templates is not updated correctly after deleting/renaming objects.
|
52402 |
Application navigator |
The dialog to rename the program instance displays a wrong name. |
52489 |
ST-editor, |
It might not be possible to build the application, if a variable based on a structured data type is to the input of a FORCEMRK block. 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 ). Example
PROGRAM Program1 VAR iFM : FORCEMRK; i : MyStruct; END_VAR iFM.IN := i; END_PROGRAM TYPE MyStruct : STRUCT el1 : INT; END_STRUCT; END_TYPE |
52502 |
FBD-editor, |
It might not be possible to use a named element from a namespace as an initial value. |
52526 |
FBD-editor, |
The information regarding the fully qualified names of function block instances might differ between the graphical and textual FBD-editor. |
52538 |
FBD-editor |
The refactored data type is not updated in an opened FBD-editor. |
52613 |
Project explorer |
The context menu for the last selected object is opened for the empty area of the project explorer. |
52617 |
IDE, |
The menu key to open the context menu is only supported for some components of the IDE. |
52637 |
LD-editor |
The IDE is terminated, if an LD-editor is closed with the keyboard shortcut Ctrl+W. |
52644 |
Refactoring, |
Refactoring a data type might take longer than expected, if an affected FBD-editor is open. |
52702 |
FBD-editor |
An error message may contain UNTYPED instead of the concrete data type. Type conflict: The output with type INT cannot be assigned to the input with type UNTYPED. Type conflict: The output with type UNTYPED cannot be assigned to the input with type TIME. The same problem might occur for other blocks as well as well as when the block output is connected to a variable of a different data type, such as CHAR. |
52709 |
Namespace, |
A confusing message is displayed for a missing namespace of a language element. |
52714 |
Namespace, |
The dialog for "Assign Using..." does not contain all existing namespaces. |
52761 |
Building the application |
The building of an application for a specific customer platform seems to fail.
You will notice the following messages in the error log, if the building of your applicatiion is affected by the exception: File 'Path\file' does not exist ... File 'Path\file' does not exist Exception while dispatching event com.logicals.lc3.api.events.BinaryBuildEvent [topic=com/logicals/events/BinaryBuildEvent] {} to handler com.logicals.buildservice.buildreport.BuildReportBroker @4c73e29 |
52792 |
ST-editor |
Using a named value in a nested namespace is handled differently. Beispiel
Namespace NS1 TYPE light : INT(red := 0 ); (* the data type with the named value *) END_TYPE END_NAMESPACE Namespace NS1 Namespace NS2 (* nested namespace that repeats the keywords *) TYPE myType1 : int (e1 := light#red); (* the usage of the named value is OK; it is NOT highlighted as faulty *) END_TYPE END_NAMESPACE END_NAMESPACE Namespace NS1.NS2 (* nested namespace with the full qualified name *) TYPE myType2 : int (e2 := light#red); (* the usage of the named value is highlighted as faulty *) END_TYPE END_NAMESPACE |
52870 |
ST-editor |
The application cannot be built for an application with an initialized array of a function block with instance parameters. Example
PROGRAM Program1 VAR iFB01 : ARRAY [ 1 .. 1 ] OF FB01 := [(Var1:= 1 )]; END_VAR END_PROGRAM FUNCTION_BLOCK FB01 VAR PUBLIC { instanceParam } { noCodeGeneration } Var1 : INT; END_VAR END_FUNCTION_BLOCK Additional information: Instance parameters are a part of instance data that are additional data elements for the function block. Usually, such instance data elements exist only for function blocks within a library provided by a system integrator. If you want to enter instance data elements for a block within the graphical user interface of logi.CAD 3, you require a logi.CAD 3 variant that has been enhanced by a system integrator. |
53090 |
Project explorer, |
Open and closed projects are displayed with the same icon. |
53299 |
Test framework |
A SiL-test with test coverage is not executed successfully when the system library "System" is missing.
|
53485 |
TC6 XML import |
The imported project contains an error that a function block instance is declared as BOOL variable by mistake. |
53530 |
Global-variables-editor |
Saving a global-object with a named value as an initialization value for a global variable destroys the global object.
Moreover, the Error Log view displays the following message: Save failed |
Known problems in logi.CAD 3 version 3.19.0
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. |
52694 |
Migration wizard |
The migration wizard does not export the POUs into the migrated project when logi.CAD 3 incl. the migration wizard is installed in a path with blanks. |
53502 |
List of declared variables,
|
A variable cannot be renamed, when it uses an illegal data type that is reported as a warning by the validation.
Additional information: The moving of a value field containing the variable with the illegal data type (without saving the change) has the effect that the validation is reset. If keeping the unsaved state for 2 minutes (or longer), it might become possible to rename the variable, even if the list of the declared variables displays the warning icon. But it has also been observed that the renaming action could still not be executed. |
53510 |
Headless tools |
2 command line interfaces (also known as headless tools) return a misleading error.
These headless tools are affected by the problem:
Workaround: none existing |
53514 |
Headless tools |
The headless tool for the automated loading of an application onto the PLC reports an unlikely code image fingerprint. |
53589 |
FBD-editor |
Resizable blocks with internal value fields behave unexpectedly. |
53615 |
Application navigator |
When creating a new program instance in the application navigator, an exception might be caused. Example for global variable in the PLC-object
RESOURCE local ON BuiltInPlc { ON_CHANNEL := LocalChannel } VAR_GLOBAL GVar1 : INT := NS1.Color#Red+ 3 ; (* 'NS1' is the namespace, 'Color#Red' is the enum , '+3' is the operator and the literal. *) END_VAR Workaround: none existing |
53606 |
Workspace |
Using a workspace with umlauts and importing a project into the workspace spams the error log with exceptions. |
53619 |
Global-object |
Copying a global-object does not rename the contained GLOBALS section as expected. |
53684 |
Building the application, |
The application cannot be built and loaded onto the PLC, if safe-convert functions with safe data types are used. |
53650 |
Application navigator |
Objects can be dragged into a read-only folder. |
53654 |
Application navigator |
Objects can be deleted from a read-only folder. |
53664 |
Application navigator, |
Inserting a call of a block with the same name from another namespace via Drag&Drop is not possible. |
53669 |
TC6 XML import |
The import of a TC6 XML file from a path with blanks is not successful. |
53685 |
Application navigator, |
The application navigator displays unexpected sub-items for LD-objects. |
53689 |
Application navigator, |
An ST-interface is not displayed in the application navigator. |
53693 |
Application navigator, |
The application navigator allows you to create a global-object in the Project blocks folder. However, these objects are not displayed there. |
53697 |
Application navigator, |
The application navigator allows to unexpectedly drag the PLC-object or its sub-elements into another folder. |
53701 |
Application navigator |
Copying/pasting of an object by dragging and dropping does not work as expected. |
53720 |
Global-variables-editor |
The data type of a global variable cannot be changed to an illegal data type, if this data type would be reported as a warning by the validation. Workaround:
|
53765 |
TC6 XML import |
An exception is caused when importing a TC6 XML file. |
If your problem is not listed in this list, check these sections: Troubleshooting and FAQ