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.17.0, install and use the version 5 .15.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.

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.
Fix: The command New Variable... is using the correct entry for the following scenario.
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.

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.
Fix: In the case of the following scenario, the command New Variable... and the validation are using the non-saved item for the data type.
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.

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.
Fix: The occurrences according to the following scenario do not occur anymore.
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 .

50847

FBD-editor

Copying/Pasting the contents on several pages does not work when one of the target pages is missing.
Fix. It is still not possible to paste the contents on several pages when one of the target pages is missing. In this case, the elements are now presented with a red rectangle in order to indicate that the pasting action is not possible.
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.

50924

FBD-editor

It is not possible to create a line fork when connecting a continuation to an input of a second block.
Fix: It is possible to create the line fork according to the following scenario.
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):

50969

FBD-editor

It is not possible to create a new value field with a TIME_OF_DAY or DATE_AND_TIME literal.
Fix: It is 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

51166

FBD-editor

Aligning some FBD-elements might not create a straight line.
Fix: The FBD-elements are connected by a straight line after the alignment as described in the following scenario.
Scenario for problem: If you change the layout of a value field and a NOT block by using the context menu command Layout – Align Bottom, where the connection points of these FBD-elements are on the same horizontal position, the line between these two elements gets a slight bend after the new alignment. Thus the elements are no longer connected by a straight line.

51230

LD-editor

The statusbar of the LD-editor does not contain information on the POU.
Fix: The statusbar of the LD-editor contains the 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.

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.
Fix: In case of a validation relating to the instance, the rule is correctly applied.
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.

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.
Fix: In case of a validation relating to the instance, the rule is correctly applied.
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.

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.
Fix: The exception does not occur for the following scenario anymore.
Scenario for problem: When you validate the elements of a resource and these elements contain 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:

51294

Creating custom library

The link to open the validation report does not work when a project is located outside the workspace.
Fix: The link to open the validation report is now working for the following scenario.
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.

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.
Fix: For the following scenario, it is not possible to create the value field.
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.

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.
Fix: The problem according to the following scenario does not occur anymore.
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.

51428

Test framework,
ST-editor

The SiL-/PiL-test cannot be executed, if the block contains the pragma "{ noCodeGeneration }".
Fix: The SiL-/PiL-test can be executed for the following scenario.
Scenario for problem: If an ST-block under test contains the pragma "{ noCodeGeneration }*, it is not possible to successfully execute the SiL-/PiL-test for this block. Instead, errors are displayed in the error log, in the console for the SiL-/PiL-test and in the build log.

51505

Building/loading the application,
libraries

Exceptions are caused when an application is built but a library is missing.
Fix: The exceptions according to the following scenario are not caused anymore. Messages when building the application indicate that an unknown library is used and that the application cannot be build/loaded.
Scenario for problem: When you install a library for a project and then the library is deleted from the library provider and library cache, the installed library in the project explorer is highlighted as faulty. Otherwise, no message indicates the missing library. If you build the application, exceptions are caused. In this case, the error log displays messages, for example:

or

51549

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.
Fix: The exception does not occur for the following scenario anymore.
Scenario for problem: When you validate the elements of a resource and the ST-code according to the following example is used, the validation with the activated rule Illegal elementary data types must not be used causes an exception.

In the case of the exception, the following message is displayed in a dialog and the error log:

51693

FBD-editor,
Debugging

A carriage return by using the Enter-key can be entered in an OLT-field but it is reported as invalid.
Fix: Pressing the Enter-key in the dialog is now applying the already entered characters and closing the dialog. If you want to enter a new line within the dialog, press Shift+Enter.
Other changes in this context:

• In this dialog for a STRING variable, you can enter special characters, such as umlauts, directly by using the keyboard. It is no longer necessary to enter the appropriate three-character combination of the dollar sign ($) followed by two hexadecimal digits in this dialog when a STRING variable is affected.

• The leading/terminating quote characters for character strings are no longer displayed in the OLT field for a STRING variable. However, they are still displayed in the input field. Therefore, do not delete the leading/terminating quote characters when you change the STRING value.

Scenario for problem: In case of an OLT-field for a STRING variable, you are able to enter STRING values in the FBD-editor with instance context. In the dialog to enter the value, pressing the Enter-key is interpreted as a new line or carriage return. However, the button to accept this string becomes disabled and the message Invalid input is displayed.

51780

Building the application,
ST-editor

The application cannot be built, if an unused program contains the DMA pragma.
Fix: The application for the following scenario can be built.
Scenario for problem: If an unused program declaration contains the DMA pragma (see the following example), it is not possible to build the applications. After this has been tried, the Problems view displays the following errors:

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

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.

51763

FBD-editor,
exiting the IDE

Exceptions might be caused when exiting the IDE, if FBD-editors with instance context and force marker were open.
Scenario for problem: It is possible that the following steps are causing exceptions:

1. Load an application with force markers on the PLC.

2. Open different FBD-editors with instance context by double-clicking on the force marker items in the Force Marker view – several times each in succession.

3. Exit logi.CAD 3. Now the exceptions might be caused.
   In this case, one of the following messages might be displayed:

   com.google.common.eventbus.EventBus$LoggingHandler handleException

   SEVERE: Exception thrown by subscriber method ...

   java.lang.NullPointerException: Cannot invoke "com.logicals.iec.fbd.editor.shared.FbdEditorUiContext.getService(java.lang.Class)" because "this.editorUiContext" is null
   Exception while dispatching event com.logicals.lc3.api.events.ApplicationEvent [topic=com/logicals/events/ApplicationEvent] {} to handler com.logicals.targetproxy.ApplicationEventHandler@1ba9111b

   java.lang.ArrayIndexOutOfBoundsException: Index 32 out of bounds for length 32
   LC3EventAdmin can't send the event com/logicals/events/TargetSessionEvent: The OSGi EventAdmin has not been bound!

   com.google.common.eventbus.EventBus$LoggingHandler handleException

   SEVERE: Exception thrown by subscriber ...

Note: The problem has been observed, when starting logi.CAD 3 by using the command logiCAD3c.exe -console -consoleLog within a command prompt. The messages are displayed in this command prompt but not in logi.CAD 3 itself.
Workaround: none existing

51837

FBD-editor

If there are overlapping elements, it is possible that the instance name cannot be hidden.
Scenario for problem: It is possible that lines cannot be routed due to overlapping elements in the FBD-editor. In this case, the message Lines cannot be routed due to overlapping elements is displayed in the Problems view. If you try to hide the instance name so that the elements no longer overlap, this is not possible for some calls. The instance name remains displayed.
Workaround: Move the element so that it no longer overlaps. After that, it is also possible to hide the instance name (if this is still necessary).

51884

Values of Variables view

A prepared empty string is not loaded to the PLC. It is also possible that the connection to the PLC is lost.
Scenario for problem: If you specify an empty string as a prepared value for a STRING variable in the Values of Variables view and then you click the button Force Prepared Values, the empty string is not loaded onto the PLC. Instead, the message Invalid parameter value (error code: 0x10002 (65538) ) is displayed in the error log.
In some cases, even the connection to PLC was lost.
Workaround: none existing

52090

Migration wizard

The migration wizard does not show the expected results for "Analyze External Libraries" when logi.CAD 3 incl. the migration wizard is installed in a path with blanks.
Scenario for problem: When logi.CAD 3 incl. the migration wizard is installed in a path with blanks, the migration wizard page Analyze External Libraries does not display the expected links in the logi.CAD/32 project.
Workaround: Install logi.CAD 3 incl. the migration wizard into a path without blanks. Start the migration anews.

52111

FBD-editor

Specifying the terminating character ; in the content assist when creating an external variable causes a syntax error.
Scenario for problem: If you declare a function block instance as a resource-global variable, then declare the corresponding external variable with the terminating character ; using the content assistant in the FBD editor – that is, specifying e: instance name : function module type;, then the terminating character ; is accepted and erroneously adopted. After saving the changes, the message Unexpected character ';' appears in the Error view.
If you close the FBD-editor and try to open it again, this message is displayed: File contains syntax errors. Please fix them in the textual FBD-editor.
Workaround: Open the FBD-POU in the textual FBD-editor and delete the invalid character. Save the FBD-POU.

52196

Creating/using custom library

A snapshot library is not updated, if the installation folder contains the subfolders: libraries\addon
Fix: The snapshot library is updated for the following scenario.
Scenario for problem: If you create and deploy a snapshot library with modified content, the snapshot library is automatically updated when you open the project which is using this snapshot library. However, if the installation folder contains the subfolders libraries\addon, the snapshot library is not updated. Instead, the following message is displayed in the error log:

Additional Information: The subfolders libraries\addon were created by the system integrator to provide additional libraries for the installation there.
Workaround: none existing