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:

See "Release notes for system libraries".

About t he →runtime system :

If you are using logi.CAD 3 version 3.16.0, install and use the version 5 .14.0 of the runtime system.
The installation package for the runtime system is included in the delivery range of logi.CAD 3.

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)".
See the FAQ article "When to update the version of the runtime system on the PLC?", if you need information on how to check whether the runtime system version appropriate for logi.CAD 3 is used on the PLC.

About →Raspberry Pi :

See the tutorial "Putting Raspberry Pi into operation" which version is recommended by logi.cals for usage.

47255

"Instances" view

The "Instances" view might not respond after unlocking a computer. Also, the FBD-editor does not display any logic.
Fix: The problem according to the following scenario no longer occurs.
Scenario for problem: It is possible that logi.CAD 3 does not react anymore or does not display the correct content after unlocking the computer. The problem was observed during these steps:

• You start logi.CAD 3 and bring the Instances view to the foreground, e.g. to create applications or to load them to the PLC.

• You do not use the computer for some time until the sleep mode is activated by the computer itself. The Instances view is still in the foreground at this time.

• You unlock the computer.

Effects: The Instances view cannot be used. An opened FBD editor does not show any graphical logic

47914

Read-only FBD-editor with instance context

After switching from the read-only FBD-editor to the edit mode, it might not be possible to resize existing FBD-elements.
Fix: After this switching, it is also possible to resize existing FBD-elements.
Scenario for problem: Depending on your logi.CAD 3 configuration it is possible that an FBD-editor with instance context is read-only. However, if changes to the logic are necessary, it is possible to switch to the edit mode. In this edit mode, however, it is not possible to resize the existing FBD-elements (such as blocks, value fields, comment fields).

49287

FBD-editor with instance data

A variable might get instance data when the instance data are changed for a different variable.
Fix: Only the required instance data are set.
Scenario for problem: When the instance data for a block is changed in the FBD-editor, instance data might be set for a variable although this variable is actually not affected. At present, there are no more details on this problem.
Additional information: Instance data elements 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.

49439

LD-editor

Some keyboard shortcuts (such as Ctrl+S for Save and Ctrl+Z for Undo) do not work in the LD-editor.
Fix: The mentioned keyboard shortcuts are working in the LD-editor again.
Scenario for problem: It is not possible to save the changed content for an LD-editor by pressing Ctrl+S. Other shortcuts are also not supported, such as Ctrl+Z to undo that last action or Ctrl+A to select all elements in the ladder diagram.

49450

Interface editor

Removing an input variable with an attached value field makes the block faulty.
Fix: Removing an input variable with an attached value field does not cause the error anymore that is described in the following scenario.
Scenario for problem: It is possible to create a value field within the interface of a block. Such a value field is attached to a block input. If you delete an input variable with an attached value field and save the changes, the block becomes faulty. In this case, the following message is displayed in the Problems view: "Input-name" is not an input variable.

49504

FBD-editor

The order of the comments about the evaluation of the FBD-networks within the textual FBD-editor might not be correct.
Fix: The order of the comments according to the following scenario is correct.
Scenario for problem: When you are saving an FBD-editor, comments are inserted in the FBD-object by default. These comments are consisting of ST-statements that describe in which order the networks in FBD and their FBD-elements are evaluated. These comments are visible only in the textual editor, If there are more than 2 connected value fields for one function output, only the first 2 assignments are listed in the comment. The other assignments are missing.

49509

Service edition

In the service edition, it is not possible to view a ladder diagram in the graphical LD-editor.
Fix: Now ladder diagrams are displayed correctly, i.e. within the graphical LD-editor, in the service edition.
Scenario for problem: In the service edition, you import existing projects. When the project contains LD-objects and you try to open such an LD-object, the content is displayed in the default text editor instead of the graphical LD-editor. This problem occurs because there are some files missing in the installation package for the service edition.

49530

List of declared variables

It is possible by mistake to delete the name of a variable in the list of declared variables.
Fix: It is not possible anymore to delete the name of a variable in the list of declared variables as described in the following scenario.
Scenario for problem: The list of declared variables lists the existing variables. In an FBD function block, it is possible to delete the name of a variable in this list and save this change. Subsequently, the message Unexpected character ':' is displayed in the Problems view because the variable no longer has a name. If you exit the FBD editor and open it again, the logic is no longer displayed, but this message: File contains syntax errors. Please fix them in the textual FBD-editor.

49683

ST-editor,
Building/loading the application

The application cannot be built if certain ST-operators are used for initializing array variables.
Fix: The application can be built for the following scenario.
Scenario for problem: If you are using the ST-operator ** or MOD for initializing an array variable (see the
following example), no message is displayed in the Problems view indicating a problem. If you now attempt to build the application or load it onto the PLC, these errors will be displayed:

It is only now that error and information messages are displayed in the Problems view, indicating a problem with the ST-operator.

49839

Importing the Simulink model

The import of a Simulink model into a project contains a fatal error when calculating the data sizes on the target system.
Fix: The error when calculating the data sizes on the target system is fixed.
Note: Observe to execute both partial steps of the import with the same version of logi.CAD 3. These partial steps are:

1. Exporting the Simulink model as logi.CAD 3 MATLAB export bundle

2. Importing the logi.CAD 3 MATLAB export bundle into logi.CAD 3

Scenario for problem: Due to a fatal error when calculating the data sizes on the target system, the import of a Simulink model into a project might cause problems or even crashes when execution the application on the target system.

49937

Editors

The "Outline" view displays <unnamed> for named values.
Fix: The Outline view and the quick outline do not display <unnamed> for named values anymore. Moreover, a specific icon is displayed for the named values for a better distinction.
Scenario for problem: In case of data types for named values, the Outline view does not display the value but the text <unnamed>. The same problem also occurs for the quick outline (the quick outline is displayed on top of the currently active editor).

49944

"Force Markers" view

When double-clicking a force marker in the "Force Markers" view, no values of the variables are displayed in the open FBD-editor.
Fix: The values of the variables are displayed in the open FBD-editor for the following scenario.
Scenario for problem: It is possible to switch from the Force Markers view to the declaration of a FORCEMRK block by double-clicking the force marker in the view. When you do this, the object with the declaration of the force marker is opened in the FBD-editor. However, this FBD editor does not display any value of the variables.

50023

Saving editors,
Creating custom library

A possible internal error when saving a block (actually during the code generation) is the reason for a subsequent error when creating the library.
Fix: The observed crashes when saving this block no longer occur. The following error when creating the library according to the following scenario no longer occurs.
Scenario for problem: When saving a block with an ST code as in the following example, it is possible that no C-/H-file is generated. However, this failure to generate the C-/H-file is not reported. Only if you create a library that contains this block, you will get information that the library cannot be created. The reason for this is the missing C-/H-file for the block.

Additional internal information: The non-deterministic resolving of ANY datatypes for the used vendor block has caused occasional crashes due to which the C-/H-files were not generated.

50721

"Force Markers" view

When double-clicking another force marker in the "Force Markers" view, it is tried to open a new FBD-editor.
Fix: The already open FBD-editor is used for the following scenario.
Scenario for problem: It is possible to switch from the Force Markers view to the declaration of a FORCEMRK block by double-clicking the force marker in the view. When you double-click another force marker, it is tried to open a new FBD-editor.

50414

Validating the application

The rule "Connections from an output of a function block are not allowed to a VAR_IN_OUT variable" does not report an error correctly.
Fix: The assignments according to the following scenario are reported now.
Scenario for problem: The model rule Connections from an output of a function block are not allowed to a VAR_IN_OUT variable checks whether there are connections from an output of a function block to a VAR_IN_OUT variable. Such connections (= assignments) are not reported for the following ST-code.

50663

Validating the application

The rule "ST-objects must not contain more than one element on the top level" is not applied to user-defined data types.
Note: The description of the rule in the user documentation has been corrected because this rule is not applied in the case of user-defined data types.
Additional fix: The rule is now also applied in the case of vendor blocks. This has not been the case so far.
Scenario for problem: According to its description and the user documentation, the model rule ST-objects must not contain more than one element on the top level checks whether ST-objects contain more than one element on the top level of the ST-object. Such elements are e.g. POUs, data types or interfaces. However, user-defined data types are not reported.

49821

ST-editor

In case of expressions, it is possible that mathematical errors are very rarely detected and reported.
Note: The user documentation has been enhanced accordingly to list this problem and its workaround.
Scenario for problem: If you assign expressions in logi.CAD 3 , it is possible that mathematical errors are not detected and reported.

Additional information: If constant expressions are used when initializing variables, errors are no longer detected.
Workaround: Check with suitable tools whether the specified expression can be mathematically evaluated.

49494

Application navigator,
ST-objects

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.
Scenario for problem: It is possible to create several language elements, such as function blocks, in the same ST-object. When in the application navigator, you are selecting the command Delete for one of these language elements, all language elements in the ST-object are deleted because the entire ST-object is deleted. There is no information before the delete action that other elements will be affected by the delete action.
Additional information: The same problem occurs in case of a moving action. This means: If one element is moved, the other elements within the ST-object are moved as well.
Workaround: Before you delete an element, you might want to check whether there are other elements in the same object. If yes, rather delete the element in the ST-object (i.e. in the ST-editor).

49498

Application navigator

The command "Go Into" in the application navigator does not behave as expected.
Scenario for problem: The command Go into should refocus the view to the currently selected folder. However, if the command is selected in the application navigator (for example, for the folder Project blocks), the view does not display the contents of only this folder, but all projects that are currently open will be displayed in that folder as well. This behavior in the application navigator is not as expected.
Workaround: none available

49514

"Values of Variables" view

An external variable cannot be forced in the "Values of Variables" view, if the corresponding global variable is a program-global variable.
Scenario for problem: If you force an external variable for which the corresponding global variable has been declared in the program, this message is displayed in the error log: Access to the variable has been denied. (Error code: 0x10308 (66312)} – The external variable is not forced.
Workaround: Force the program-global variable instead of the external variable. However, observe that the Values of Variables view does not correctly display the force status of the corresponding external variable. The following additional force information for the external variable is missing:

• the force value in the column Prepared value

• the preceding symbol in the column Value

49535

List of declared variables

The command "New Variable..." is not using the correct entry for a data type with named values declared within a namespace.
Scenario for problem: In the list of the declared variables, when you select a variable and then the context menu command New Variable..., the dialog uses the data type of the selected variable in order to quickly create a new variable with a similar name. However, if the selected variable has been declared based on a data type with named values within a namespace, the data type of the named values is not correctly entered. Subsequently, the button OK of the dialog is disabled and the new variable cannot be created.
Example: The dialog suggests the data type Colors instead of the correct data type NS1.Colors. The variable cannot be created because the namespace NS1 is missing for the suggested data type.
Workaround: Delete the last character of the suggested data type (so delete the character s of Colors) in order to get a list with suggestions for the data type. In this list, select the correct data type, e.g. NS1.Colors. Then the button OK of the dialog will be enabled.

49539

List of declared variables

The command "New Variable..." uses a non-saved item for a data type. However, the validation is based on the saved item.
Scenario for problem: In the list of the declared variables, when you select a variable and then the context menu command New Variable..., the dialog uses the data type of the selected variable in order to quickly create a new variable with a similar name. If the name of the data type has been changed in the ST-editor, but the change has not been saved, the previous name of the data type is suggested as the data type in the dialog, but the OK button of the dialog is disabled. If you change the name of the data type in the dialog to the new name of the data type, the OK button of the dialog becomes enabled. If you save the editor with the created variable (based on the new data type name) but the changes in the ST-editor remain unsaved, the created variable will be reported as faulty because the validation is based on the saved entry (= the previous name of the datatype).
Example: The data type myINT has been corrected to myINT2 in the ST-editor but this change has not been saved yet. The dialog for the new variable (e.g. in the FBD editor) still suggests the original data type myINT but OK is disabled. Only when you correct the data type from myINT to myINT2, it is possible to create the variable based on myINT2. However, after saving the editor with the created variable, this variable is reported as faulty because the ST-editor with myINT2 is not saved yet.
Workaround: Save the changes in the ST-editor as well so that there is a consistent state that is used for the validation.

49543

List of declared variables

It might not be possible to correct a missing data type of a variable within the dialog. Or the error icon is not displayed for the variable with a missing data type.
Scenario for problem: When the data type of a variable within a graphical editor is missing, this error is highlighted in the list of the declared variables by an error icon in front of the variable name (this is mentioned within the user documentation). It is possible to fix this problem in the list of the declared variables. e.g. double-clicking the variable opens a dialog to correct the data for this variable.
However, there have been occurrences where

• the field Data type in the dialog has been disabled. In this case, it is not possible to correct the data type in the dialog.

• the variable with the missing data type has not been highlighted with the error icon .

Workaround, if the field Data type in the dialog is disabled: Use the context menu command Edit Type in order to correct the data type.
Workaround, if the error icon is missing: Check the Problems view for error messages that report the missing data type. Double-click this error message to go to the respective variable in the list of the declared variables. Correct the data type.

50847

FBD-editor

Copying/Pasting the contents on several pages does not work when one of the target pages is missing.
Scenario for problem: When you select the entire content in an FBD-editor that consists of several pages, it is possible to copy the selection to the clipboard. But it is not possible to paste the content into a different FBD-editor that consists of fewer pages. In this case, only the preview of the pasted elements is displayed but nothing is inserted. Moreover, no message informs about the possible problem cause.
Workaround: Make sure that all target pages are existing before pasting the content. Or copy and paste only the elements of one page.

50924

FBD-editor

It is not possible to create a line fork when connecting a continuation to an input of a second block.
Scenario for problem: When you point to an existing line, press and hold the primary mouse button, move the mouse pointer onto a free block input and release the primary mouse button, a line fork (incl. a connection point) is created connecting the line with the block input. However, if the existing line has been connected to a continuation and the free input is that of a second block, the line fork will not be created.
Example: Here the line fork from the continuation C1 to the input of the lower OR block cannot be created (do not mind the error icons; they are of no consequence for this problem):

Workaround: Create the line in the other direction. This means:

• Create the connection point on the existing line (by double-clicking onto the line).

• Point to the free block input

• Press and hold the primary mouse button.

• Move the mouse pointer onto the connection point.

• Release the primary mouse button.

50969

FBD-editor

It is not possible to create a new value field with a TIME_OF_DAY or DATE_AND_TIME literal.
Scenario for problem: When you use the context assist to create a new value field with a TIME_OF_DAY or DATE_AND_TIME literal, the specified value is not accepted.
Example for such values: TOD#13:33:17, DT#1999-03-12-01:20:41.500
Workaround: First create a value field with value TRUE. Then edit the value field and insert the desired value.

51230

LD-editor

The statusbar of the LD-editor does not contain information on the POU.
Scenario for problem: According to the user documentation, the statusbar of an LD-editor should contain information on the POU, such as the POU type and the POU name. However, the statusbar is empty.
Workaround: none existing

51266

Validating the application

In case of a validation relating to the instance, the rule "The usage of blocks is restricted either completely or only for defined types" is also applied to objects that are not included in the instance context.
Scenario for problem: When you validate the elements of a resource, the validation should be done for all objects that are used starting from the resource. That means, objects not in the instance context of the resource should not be validated. However, the rule The usage of blocks is restricted either completely or only for defined types is also applied to the objects that are not included in the instance context of the resource.
Additional information: This problem occurs when objects included in the instance context are located in the same ST-object as objects not included in the instance context.
Workaround: Move the objects into to different ST-objects, if this is reasonable for you.

51281

Validating the application

In case of a validation relating to the instance, the rule "Illegal elementary data types must not be used" is also applied to objects that are not included in the instance context.
Scenario for problem: When you validate the elements of a resource, the validation should be done for all objects that are used starting from the resource. That means, objects not in the instance context of the resource should not be validated. However, the rule Illegal elementary data types must not be used is also applied to the objects that are not included in the instance context of the resource.
Additional information: This problem occurs when objects included in the instance context are located in the same ST-object as objects not included in the instance context.
Workaround: Move the objects into to different ST-objects, if this is reasonable for you.

51290

Validating the application

In case of a validation relating to the instance and the activated rule "Illegal elementary data types must not be used", an exception might occur.
Scenario for problem: When you validate the elements of a resource and these elements conains a type with a recursion, the validation with the activated rule Illegal elementary data types must not be used causes an exception. In this case, the following message is displayed in a dialog and the error log:

Workaround: Avoid the usage of recursions.

51294

Creating custom library

The link to open the validation report does not work when a project is located outside the workspace.
Scenario for problem: When you generate a library, the library is automatically validated in some variants of logi.CAD 3. In the other variants of logi.CAD 3, it is possible to validate the library yourself. When such a validation is executed, the Validate view informs that this validation report has been created. When you double-click the appropriate message, the validation report is opened in logi.CAD 3. When logi.CAD 3 has been started with a workspace containing a blank, the project mus be located outside of the workspace. In this case, the validation report is not opened. Instead, the error log displays the messages Unable to create part and Cannot determine URI for 'path/library-name.lib.mrclog'.
The last message is also displayed in the component where the report should be displayed .
Workaround: Open the validation report from the project explorer.

51303

FBD-editor

It is possible to create a value field by dragging the variable with an invalid data type from the list of the declared variables.
Scenario for problem: When a variable is declared on an invalid data type, the view Problems contains a message to indicate the problem. However, it is possible to create a value field for this variable by dragging this variable from the list of the declared variables into the drawing field. As a consequence, the value field uses a faulty variable.
Additional information:

1. The data type might be invalid because the data type has been deleted since the variable has been declared.

2. The content assist does not list the variable with the invalid data type.

Workaround: none existing

51356

Validating the application

In case of the activated rule "Only identifiers conform to predefined specifications must be used for projects/folders/objects.", an exception is caused when creating a device object.
Scenario for problem: When you activate the rule Only identifiers conform to predefined specifications must be used for projects/folders/objects, it is not possible to create a new device object because an exception is caused. In this case, the dialog to create the object does not display an enabled button Finish and the error log displays the messages Unhandled event loop exception.
Workaround: none existing

51364

FBD-editor

The refactoring of a data type has no impact on variables that are declared/used in the FBD-editor.
Scenario for problem: It is possible to refactor a data type by changing its name. Variables that are declared with this data type are correctly changed to the new name of the data type - but only when the variable has been declared in the ST-editor. The refactoring is not done when the variable has been declared in the FBD-editor.
Workaround: Double-click the error message reporting the missing data type. Change the data type of the variable in the FBD-editor yourself.