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

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.
Fix: The external variable can also be forced for the following scenario.
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.

49821

ST-expressions

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.

51364

FBD-editor

The refactoring of a data type has no impact on variables that are declared/used in the FBD-editor.
Fix: The refactoring of a data type is also done for variables 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.

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.
Fix: The exceptions are not caused for the following scenario anymore.
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.

51837

FBD-editor

If there are overlapping elements, it is possible that the instance name cannot be hidden.
Fix: The instance name can be hidden in case of the overlapping elements.
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.

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.
Fix: The prepared empty string is loaded to the PLC. The connection to the PLC is not 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.

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.
Fix: Now the migration wizard can also be used when logi.CAD 3 incl. the migration wizard is installed in a path with blanks.
Scenario for problem: When logi.CAD 33 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.

52111

FBD-editor

Specifying the terminating character ; in the content assist when creating an external variable causes a syntax error.
Fix: When specifying the terminating character ; in the content assist, the message Unexpected character ";" is now indicating that the external variable cannot be declared correctly.
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.

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.

52249

Application navigator

Renaming a variable in a read-only global-object might cause an exception.
Fix: It is not possible to rename a variable in a read-only global-object. The exception is not caused.
Scenario for problem: When you try to rename a variable located in a read-only global-object from within the application navigator, the renaming is not executed. This is as expected due to the read-only statement that is included in the global-object. However, an exception is caused. In this case, the error log displays the following message: Unhandled event loop exception

52282

FBD-editor

A named value of a STRING data type is not entered correctly when declaring a variable using this named value. When saving and reopening the FBD-editor, the named value is gone.
Fix: Now the named value of a STRING data type is entered correctly for the following scenario and it is kept.
Scenario for problem: When you enter a named value of a STRING data type when declaring a STRING variable in the FBD-editor (e.g. you declare the variable Var1 with the data type STRING[StrLEN#LEN] where StrLEN is the data type and LEN is the named value with an assigned value of 10), the variable is declared with the data type STRING[10]. This data type STRING[10] is kept for the variable when you are saving and reopening the FBD-editor.

52289

Application navigator

It is not instantly possible to create a subfolder under Templates.
Fix: After creating the project, it is instantly possible to create a subfolder under Templates.
Scenario for problem: After creating a project, it is not possible to create a subfolder under Templates in the application navigator. In the dialog where you have to select the root folder of the subfolder, Templates is not provided.

52329

Creating/using custom library

When installing a library, an error is reported related to a STRING/CHAR literal, if the STRING literal contains a special character.
Fix: After the library has been built and deployed by using the new logi.CAD 3 version again (preferably as a new library version), the error according to the following scenario is not displayed when installing this new library version anymore.
Scenario for problem: The following steps will result in an error:

1. Create an FBD library element that uses a STRING literal with a special character. Example: '°C'
   In this case, logi.CAD 3 does not report any errors for the FBD library element.

2. Create and deploy the library with this FBD library element.
   logi.CAD 3 does not report any errors either.

3. Install the library in another project.
   Result: The following message is displayed in the Problems view: Invalid STRING or CHAR literal

52355

FBD-editor

It might not be possible to paste a copied value field containing an ARRAY variable using a different variable as array limit into a different FBD-editor.
Fix: It is possible to paste the copied value field containing an ARRAY variable using a different variable as array limit into a different FBD-editor.
Scenario for problem: The following steps cause an error:

1. Create a variable based on an integer data type. Example: Var1 of data type INT

2. Create an ARRAY variable. Example: ArrayVar1 of data type ARRAY[1..10] OF INT

3. Create a value field containing the ARRAY variable. that uses the INT variable as array limit. Example: ArrayVar1[Var]

4. Copy this value field to the clipboard.

5. Go to another editor and paste the value field.
   Result: An error icon is displayed for the preview of the value field. The value field is not inserted because the INT variable is missing.

52403

Application navigator

The dialog for renaming the program instance allows non-IEC-conform identifiers.
Fix: Now the dialog for renaming the program instance indicates the problem when non-IEC-conform identifiers have been entered.
Scenario for problem: When you rename a program instance in the application navigator, the dialog accepts an identifier that is not an IEC-identifier. Example for a non-IEC-conform identifier: Motor-On
This non-IEC-conform identifier is entered in the PLC-object and only then highlighted as faulty. The message Unexpected character '-' indicates the non-IEC-conform identifier - in the name of the program instance.

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

52170

Importing projects

An exception might occur when importing several projects from an archive.
Scenario for problem: If you import several projects from an archive file together when using a logi.CAD 3 version with the test framework, an exception might occur. In this case, the error message shows this message twice: Error while configuring test project
Workaround: Import the projects one after another from the archive file. To do this, select just one project at a time in the import wizard. The exception does not occur during the import action of one project.

52309

Application navigator

The content of Templates is not updated correctly after deleting/renaming objects.
Scenario for problem: If you delete or rename an object under Templates in the application navigator, the object remains like this after the action:

• When deleting, the object is still visible.

• When renaming, the renamed object and the original object are displayed.

Workaround: Select Templates in the application navigator and press the F5-key to update the contents of Templates.

52402

Application navigator

The dialog to rename the program instance displays a wrong name.
Scenario for problem: When trying to rename the program instance within the application navigator, the dialog displays a wrong name. Instead of the program instance name, the dialog displays the name of the PLC-object.
However, when entering a new name in the dialog, the program instance is correctly renamed.
Workaround: none existing

52489

ST-editor,
FORCEMRK block,
building the application

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.
Scenario for problem: If you assign a variable based on a structured data type to the input of a FORCEMRK block and you do not call the FORCEMRK block itself (see the following example), it is not possible to build the application and/or load it onto the PLC. These errors are displayed:

Workaround: Insert the call of the FORCEMRK block: iFM();

52502

FBD-editor,
namespace

It might not be possible to use a named element from a namespace as an initial value.
Scenario for problem: If an FBD-object uses a namespace (internally, a used namespace corresponds to a USING namespace directive from an ST code) and a named element is declared in this namespace, it is still not possible to use this named element as initial value for a variable. The FBD-editor highlights the named element as an invalid initial value. Example: TrafficLight#Green from the used namespace NS1
Workaround: Enter the fully qualified name of the named element in the initial value field. Example: NS1.TrafficLight#Green

52526

FBD-editor,
namespace

The information regarding the fully qualified names of function block instances might differ between the graphical and textual FBD-editor.
Scenario for problem: When a call of a function block (located outside of the current namespace) is inserted in the FBD-editor, logi.CAD 3 automatically inserts the namespace as used namespace in the graphical FBD-editor. This corresponds to the USING-directive in the textual FBD-editor. In the graphical FBD-editor, the column Namespace in the list with the variables displays the name of the used namespace for the function block instance. When you toggle the fully qualified name for the function block instance, logi.CAD 3 changes the used namespace to the fully qualified name by removing the USING-directive in the textual FBD-editor and using the fully qualified name as function block type. At the same time, the graphical FBD-editor displays the fully qualified name within the column Data type in the list with the variables (instead of the namespace name within the column Namespace). So far, the information in the graphical and textual FBD-editor are matching.
However, if you insert a new call of a function block from the namespace in the FBD-editor, the column Namespace in the graphical FBD-editor displays the name of the used namespace for both function block instance whereas the textual FBD-editor contains the USING-directive for one function block instance and the fully qualified name for the other function block type. In this case, the information in the graphical and textual FBD-editor are not matching.
Workaround 1: Avoid toggling the fully qualified name for the function block instances in the graphical FBD-editor. Rather let logi.CAD 3 handle the required data (e.g. used namespace). The differences in the editors have only occurred after the first toggling.
Workaround 2: After inserting new calls for a namespace, toggle the fully qualified name for the function block instances in the graphical FBD-editor again and save the changes. This new toggling updates the content of the textual FBD-editor to be the same as in the graphical FBD-editor.

52538

FBD-editor

The refactored data type is not updated in an opened 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. However, when the refactoring is done while an FBD-editor is open, the display of this FBD-editor is not updated. This means that the list of the declared variables is still displaying the previous name of the data type for the variable.
Workaround: Close and reopen the FBD-editor so that the new name of the data type is displayed for the variable.

52613

Project explorer

The context menu for the last selected object is opened for the empty area of the project explorer.
Scenario for problem: If you select an object in the project explorer (e.g. a function block in a library) and then open the context menu for an empty area of the project explorer, this context menu contains the commands for the selected object instead of the commands for the project.
Workaround: Deselect the object before opening the context menu for the empty area of the project explorer.

52617

IDE,
context menu

The menu key to open the context menu is only supported for some components of the IDE.
Scenario for problem: The menu key on a computer keyboard is used to invoke the so-called context menu which contains a function selection relevant to the cursor position. This menu key is not supported in all components, e.g. in the FBD-editor and in the Instances view.
Workaround: Open the context menu for such components by clicking the secondary mouse button.

52637

LD-editor

The IDE is terminated, if an LD-editor is closed with the keyboard shortcut Ctrl+W.
Scenario for problem: If you close an opened LD-editor with the keyboard shortcut Ctrl+W, logi.CAD 3 will be closed in addition to the LD-editor. In this case a LOG-file is created in the installation folder of logi.CAD 3. The file contains a EXCEPTION_ACCESS_VIOLATION note.
Workaround: Close the LD-editor by using the command Close.

52644

Refactoring,
FBD-editor

Refactoring a data type might take longer than expected, if an affected FBD-editor is open.
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. However, when the refactoring is done while an FBD-editor with several logic pages is open, it might take several minutes until the action is performed successfully. During this time logi.CAD 3 does not respond to user actions anymore.
Workaround: Best practice is to close all editors before you execute a refactoring action. For the FBD editor with the multiple pages, the refactoring action was correctly completed within a few seconds.

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.
Scenario for problem: When logi.CAD 3 incl. the migration wizard is installed in a path with blanks, the POUs are missing in the migrated logi.CAD 3 project. The migration wizard is not able to execute the required Perl tool.
Workaround: Install logi.CAD 3 incl. the migration wizard into a path without blanks. Start the migration anew.

52702

FBD-editor

An error message may contain UNTYPED instead of the concrete data type.
Scenario for problem: If you connect a block with variables where a type conflict occurs, the error message informs about the concrete data type because of which the type conflict occurs. If you connect the inputs of e.g. the DIV block with variables of data type INT, but the output with a variable of data type TIME, the error messages contain the specification UNTYPED instead of the concrete data type.
The messages are per input/output:

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.
Workaround: none existing

52709

Namespace,
application navigator

A confusing message is displayed for a missing namespace of a language element.
Scenario for problem: If you create a language element without a namespace in a namespace folder, this message is displayed: The namespace "<--->" of the language element does not match the identifier "name" of the parent namespace folder.
Additional information: The specification "<--->" indicates that no namespace has been entered for the language element. However, the namespace folder name is expected as the namespace.
Workaround: Enter a namespace. Or move the object with the language element to a folder for which no namespace is expected.

52714

Namespace,
application navigator

The dialog for "Assign Using..." does not contain all existing namespaces.
Scenario for problem: If you call the command Assign Using... for a namespace folder in the application navigator, a dialog opens to create a USING statement for the namespace folder. However, the dialog does not list any of the namespaces that were previously declared in an ST-object itself.
Workaround: Enter the namespace name itself in the list of the dialog and press OK.

52718

Enum-editor

The enum-editor displays an error icon for an incorrect namespace.
Scenario for problem: If you create a data type with named values (= enums) in a namespace folder and the namespace of the data type does not match the namespace folder name, a corresponding warning is displayed in the Problems view. When you double-click this message, the enum-editor opens. In this enum-editor, an error icon is displayed instead of the warning icon.
Additional information: See ID "52723" for the problem due to the symbol in an unexpected place.
Workaround: none existing

52723

Enum-editor

The enum editor indicates a warning about the wrong namespace in the "Value" column.
Scenario for problem: If you create a data type with named values (= enums) in a namespace folder and the namespace of the data type does not match the namespace folder name, a corresponding warning is displayed in the Problems view. When you double-click this message, the enum-editor opens. In this enum editor, the problem is indicated by an icon in the Value column. However, the problem does not apply to a single value, but to the entire enum.
Additional information: See ID "52718" for the problem due to the wrong symbol.
Workaround: none existing

52761

The building of an application for a specific customer platform seems to fail.
Scenario for problem: When building the application under specific circumstances, an exception is caused which seems to prevent the building of the application. Nevertheless, all binary files are generated correctly while the HTML report for the Build Log view is not generated in fact. This missing generation is the cause of the exeception.
The circumstances for this problem are:

1. The features are activated so that logilogi.CAD 3 can be used to create a safety-relevant application.

2. A specific customer platform is used. This platform is using a special compiler.

You will notice the following messages in the error log, if the building of your applicatiion is affected by the exception:

Workaround: none existing