Release notes for version 3.26.0

If you have used a previous version of Neuron Power Engineer and you want to use the current version, see "Are my projects upwards and downwards compatible?" for important information. Recommended, if you are using projects that have been created in a previous version of Neuron Power Engineer: Clean the imported projects.

See "Is the IDE affected by the Log4j security vulnerability (December 2021, CVE-2021-44228, Log4Shell)".

See "Release notes for system libraries".

Depending on the configuration of your Neuron Power Engineer version, the FBD-editor and its elements might be displayed differently in your Neuron Power Engineer version than illustrated in the IDE documentation. This is the case, if Neuron  or the system integrator has activated the smart styling or one of them has changed the styles for the FBD-editor. Subsequently, the illustration in the IDE documentation are symbolic images and the representation in your Neuron Power Engineer version takes precedence for the valid representation. In case of doubts, please contact Neuron or your system integrator.

See "Color and style for FBD-elements determined by data type" for details.

The feature "object identity" allows you to check all relevant objects for their identity and integrity. To make this check easier, the project context menu within the project explorer and the application navigator provide the new command Check Object Identity. This command opens a dialog reporting modifications of individual objects outside the qualified editors of Neuron Power Engineer. This dialog allows you to approve or reject the deviations if the appropriate features for access control are provided. After approving or rejecting each deviation individually, the best procedure is to recalculate the object identity in the dialog to confirm that the state Valid is reported for the project object.

When building the application and creating a library, the dialog is automatically displayed to inform about the non-matching object identities. In the case of a valid project object, the dialog is not opened when building the application and creating a library.

These changes were already included in version 3.25.0 of Neuron Power Engineer but they were not documented in the IDE documentation of version 3.25.0.

There is a new restriction for the library configuration: The declaration of several libraries within the same library configuration is not allowed anymore.
If you want to create different libraries, create different library configurations - one library configuration per library. See “Syntax for library configuration” and its subtopics, if you need details on the syntax.

The →library reference syntax has been enhanced by a statement to include an MD5 hash value.
Observe that you do not need to edit the library reference of a project yourself. The content of the library reference is automatically adapted, if you are installing or removing libraries within the properties of the project. The library reference syntax including the new statement is just documented for reasons of completeness within the IDE documentation.

Both changes were already included in version 3.25.0 of Neuron Power Engineer but they were not documented in the IDE documentation of version 3.25.0.

If you want to bulk edit safety parameters, use the new command Bulk editing safety parameters that is provided in the context menu when several subfolders containing the safety-relevant hardware devices are selected in the application navigator.

See “Bulk editing of safety parameters” for details.

The application navigator has already provided the possibility to create new →instances of a program. This is also known as assigning more program types. Similar to this possibility, the application navigator makes it now possible to:

• unassign a program instance from a task

  Select the program instance listed under the task and press the Del-key or select the context menu command Delete.

• reordering the program instances to change the execution of the program instances

  Drag the program to the requested position within the task or select the context menu commands Move up and Move down for the program listed under the task.

• disabling and enabling a program instance

  Select the program instance listed under the task and select the context menu commands Enable or Disable. The icon in the application navigator is updated to reflect the enabled/disabled status.

Follow the links under “Actions in application navigator”, if you need details on these user actions.

Observe that all these possibilities have already been possible in previous versions. But you had to change the content of a PLC-object in an editor and know its correct syntax. Now, when you use the application navigator, you do not need to change the PLC-object in these respects anymore.

You can create ST code for safety-related applications and non-safe applications in the same project. Now the IDE helps you to use only the appropriate language elements. When unsupported language elements (e.g. SFC elements) are used in safety-related applications, the IDE can report these language elements.

The IDE provides the following new features to help guide the user regarding the allowed ST code in the context of the application:

• the language characteristics to be selected when creating an ST program, ST function block or ST function
  There are 3 language characteristics: standard, safe and safeSimplified - See “Language characteristics for ST” for details.
  The system integrator can determine the default setting and disallow the language characteristic from being changed.

• the new ST pragmas { Standard } , { Safe } and { SafeSimplified }
  These ST pragmas correspond to the above-mentioned language characteristics. One of these ST pragmas is automatically set when you create the application in ST. See “Statements for language characteristics in ST” for details.

• the rule The language characteristics "SafeSimplified" and "Safe" must be used only
  Activate this rule to check whether unsupported language elements are used. The scope of the checks depends on the chosen language characteristic. For instance, the language characteristic safeSimplified makes the rule to check the complexity of ST-code. See “Rules for the validation of an application” for details.
  When a safety-related application is built, the activated rule is automatically checked. See the release notes for ID “117948” for details.

The standard package of the IDE provides the new rule Global function block instances must only be used in one task.

This model rule checks whether function block instances declared as global variables are only used in one task at most.

By default, this rule is not activated so you will not get any messages about violations of this rule when the application is validated. But as for other rules, you can change the configuration of the rule.

In previous versions, a Boolean line connected to a →step output has been displayed as "dashed in black and red". Now, such lines are displayed as expected with a red line or dark-blue line. See “Animation of Boolean lines in the FBD-editor” for details on this animation.

Important: This feature is only provided in the new version after the existing projects have been cleaned in the new version. Observe that different C-code will be generated, even if you did not make any changes in the application yourself. See “Changes affecting the code generation” on the consequences.

Also, the step marker X, the step time T and the time of activation S of the initial steps and steps can now be used/monitored as other variables. This applies to the following components:

• Instances view

• Values of Variables view

• FBD-editor and ST-viewer when they are used for monitoring values

Observe that Neuronadvises you to not change the values for these step variables X, T and S. Otherwise, broken SFC networks or a different evaluation of the SFC elements (as it is described under the topic “Evaluating SFC elements”) might be the result.

If you want to monitor the values of array variables when the index is not a literal but a variable, ask your system integrator to activate this feature for FBD by using the start option lc3.fbdDebugMemory.valuefields.expression. As a consequence, the →OLT-field for the value field will display the value.

Observe that the activated feature consumes a little bit of memory regarding value fields that use indexed access to variables and that you cannot change these values in the OLT-fields.

By default, the Instances view displays a hierarchical view onto the instances and variables of the projects. If you are only interested in the instances of the projects, ask your system integrator to filter the elements in the view so that only the instances are visible. This filtering is possible by using the start option lc3.view.instances.defaultmode with the value ShowOnlyFBInstances.

To apply the default behavior again, set this start option to the value ShowAllElements or delete this start option.

The FBD-editor provides the following possibilities to open the parent (that is the calling POU) if this FBD-editor has been opened with a set instance context:

• Click in the status bar of the editor.

• Open the context menu, select Navigate and Open Parent.

• Press Ctrl+P when the editor has the focus.

When building a safety-relevant application, the application is automatically validated. Regardless of the selected types of the rules, the objects starting from the resource are examined based on the activated rules. If there are rule violations, the safety-relevant application is not built.

Observe that this automatic validation is not done when building applications that are not safety-relevant. For such applications, you are able to validate the application yourself. See “Validating objects” for details.

When invoking the tool for automated builds com.logicals.builder.lc3builder.application in the context of a safety-relevant application, the tool for the automated rule checking com.logicals.mrc.application is also invoked. Regardless of the selected types of the rules, the objects are examined based on the activated rules. If there are rule violations, the safety-relevant application is not built.

This behavior is similar to the behavior of the GUI elements: When a safety-related application is built, the activated rule is automatically checked. See the release notes for ID “117948” for details.

As in the GUI, the automatic rule checking is not done when invoking the tool for applications that are not safety-relevant. For such applications, you must invoke the tool for the automated rule checking yourself.

The dialog Check Object Identity (see under "Checking the identity and integrity of objects") allows you to compare files with the status Invalid or Not found with an automatically created copy. Hence, you can view the differences for the reported deviations before you decide whether to approve or reject the deviations.

When the dialog reports such a deviation for a file, select this deviation and click in the toolbar. Then the dialog lists the differences between the current content and a so-called shadow copy. The IDE has automatically created this shadow copy for the file when the file has been saved in a qualified editor of the IDE.

Observe:

• The differences are displayed based on the textual content.

• The system integrator can register a custom diff viewer to compare the textual content.

Important note on the downwards compatibility: Neuron recommends to not import projects using the shadow copy enhancement of the object identity in predecessor versions.
This is the reason:

1. You create/import a project in a Neuron Power Engineer version using the shadow copy enhancement of the object identity.
   In such a project, Neuron Power Engineer creates duplicate files in a hidden project folder .shadowcopy so that the compare feature can be used. This Neuron Power Engineer version does not report the duplicate files which is the intended behavior.

2. You import such a project in a predecessor version but this version does not contain the shadow copy enhancement of the object identity.
   As a consequence: Neuron Power Engineer reports errors due to the duplicate files because the predecessor version does not provided the compare feature as part of the object identity.

If the configuration of the safety-relevant hardware devices is modified outside of Neuron Power Engineer and you are using the feature "object identity", the safety parameter editor recognizes these external changes when the editor is started. In this case, an appropriate message is displayed that you need to accept the external changes. If you do not, the safety parameter editor shows the last loaded parameterization (not the actual content of the files). In this case, it is not possible to save any changes in the safety parameter editor.

Use the dialog Check Object Identity (see under "Checking the identity and integrity of objects") to view and approve the external changes for the hardware parameterization. When you approve a deviation for any file regarding the hardware parameterization, all deviations reported for the other files in the same folder will be approved as well. Subsequently, the safety parameter editor will reload all parameter data and discard any unsaved changes.

Now the ST-editor reports a safety conflict when you are trying to assign an unsafe expression to a safe variable. In the previous versions, such a conflict has been reported in the FBD-editor only.

This is a safety conflict because the implicit conversion of a non-safe data type to a safe data type is an illegal construct.

Now the safety parameter editor can validate the hardware parameters depending on another parameter and its value range. Also, the visibility of a parameter might depend on another parameter and its value range as well. This rule-based validation and activation of the hardware parameters is provided, if the system integrator has configured the hardware parameterization accordingly.

Moreover, observe that the safety parameter editor does not correct values anymore that have been incorrectly specified by the user. In previous versions, the safety parameter editor might have corrected an incorrect value. This change was indicated by the kept yellow background color and by a message (a warning) in the line below the changed parameter. Subsequently, the user had to confirm this suggested change or to restore the original value (e.g. by pressing the ESC-key).
In this version, the safety parameter does not change the value but enters the incorrect user value. The incorrect value is indicated by the red background color and by a message (an error) in the line below the changed parameter. The user is responsible to change the value to the correct value. The best practice is to enter the value that is suggested/reported in the error message. Now there is no possibility to restore the original value (pressing the ESC-key has no effect on the incorrect value). This behavior is applied to floating point values using the exponent notation, to floating point values that are too long and to floating point values that do not have the expected digit fraction.

Finally, observe the following: If the safety parameter contains incorrect values, it is not possible to save the changed safety parameter editor.

The integration manual does not contain information that some time tests depend on the timer frequency of the target system and how to proceed if the target system uses a different timer frequency than 1 kHz or 10 kHz.
Fix: The integration manual contains the appropriate information on how to execute tests that depend on the timer frequency.
Scenario for problem: The integration manual contains information on the qualification of a compiler. For this qualification of a compiler, integration acceptance tests must be executed with the compiler that has to be qualified. These integrations acceptance tests are provided in the file com.logicals.product.lc3.testprojects-IntegrationAcceptanceTestCompilerQualification_3.23.1.zip that is included in the delivery package of the qualified version 3.23.1. The subfolder Time of the folder tests_compilerqualification contains 2 folders with tests that depend on the timer frequency of the target system:

• tests for a target system with 1 kHz

• tests for a target system with 10 kHz

As the expected values of the tests depend on the timer frequency of the target system, these tests might fail, if the target system uses a different timer frequency than 1 kHz or 10 kHz.
Additional information: See "Properties and restrictions specific to the target system", if you need general infomation how the used target system influence the usage of the IDE. In particular, the section about duration and time literals are of relevance for the timer frequency.

• an item for a ZIP-file

• an item named folderName

1. Have the “Values of Variables” view displayed.

2. Move the view to the right of the error logger.

3. Bring the error logger to the front.

4. Close and restart the IDE with the same workspace.
   Result: The “Values of Variables” view is still provided right of the error logger.

5. Switch to the “Instances” view, expand the tree until a variable is displayed, open the context menu for this variable and select “Add Variable to Values of Variables”.

A temporary size for a value field makes it impossible to position the value field onto the grid. As a consequence, the connection line to a block input is not a straight line.
Note: This behavior has been added as a known restriction to the description of the smart styling in the IDE documentation. This description also contains a detected workaround for the problem: The line will become a straight line if you resize the value field by pointing to the lower edge of the value field and by minimally dragging the lower edge.
Scenario for problem: When using the smart styling, it might not be possible to connect a value field with block inputs by a straight line. This happens when the value field has been resized (to make it bigger) and then the value field has been resized back to its original size. After both resizing actions, any connection line to a block input is created with a “corner” because it is not possible to align the value field so that the connection nodes of the value field and of the block input are on the same grid. The connection line looks like this:

Cannot invoke "com.logicals.lc3.api.model.st.pou.Variable.getName()" because "currentVariable" is null

com.logicals.lc3.api.model.st.impl.InitializationInspector.visitInitializationForStructure(InitializationInspector.java:75)

at com.logicals.lc3.api.model.st.impl.InitializationInspector.visitInitializationRecursive(InitializationInspector.java:53)

Additional information:

• Instance parameters are a part of instance data that are additional data elements for the function block.

• Usually, instance data elements exist only for function blocks within a library provided by a system integrator. If you want to display and/or enter instance data elements for a block within the graphical user interface of the IDE, you require an IDE variant that has been enhanced by a system integrator.

• Hexadecimal literals for the initial values, such as 16#FFFF, are interpreted as variables when the instance parameter are modified. Reason: The hexadecimal value starts with a character, here F, instead of an expected value.

The application navigator might not display the project name.
Fix: The problem according to the following scenario does not occur anymore.
Scenario 1 for problem: When you create 2 projects in the IDE, the application navigator does not display the 2nd project name.
Scenario 2 for problem: When you close and open a project via the gRPC interface, the application navigator does not display the project name.
Additional information: By using the gRPC interface, it is possible to automate specific user actions in the IDE.

Debugging is not possible. Reason: The call hierarchy in the Debug view is not automatically expanded and a hit breakpoint is not highlighted.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem:To set breakpoints for an application, at first you need to select the element for which the execution has been suspended. Usually, this element is visible at once because the call hierarchy in the Debug view is expanded. However, the call hierarchy is not expanded. Also, when the application is suspended because of a hit breakpoint, this breakpoint is not highlighted in the ST-/FBD-editor.

It is not possible to use the gRPC interface for different instances of the IDE.
Fix: The problem according to the following scenario does not occur anymore, if the configuration variables -Dosgi.configuration.area and -Dlc3.serverport is specified with different values for the called instances of the IDE. The value for -Dosgi.configuration.area is a path and the value for -Dlc3.serverport is a port.
Scenario for problem:When you try to use the gRPC interface for different instances of the IDE, the following error is displayed for the gRPC interface:

Status(StatusCode="Unknown", Detail="", DebugException="Grpc.Core.Internal.CoreErrorDetailException:

{"created":"@1716819922.803000000","description":"Error received from peer ipv6:

[::1]:50055","file":"..\..\..\src\core\lib\surface\call.cc","file_line":953,"grpc_message":"","grpc_status":2}")

Also, the error log of the IDE displays errors that indicate exceptions. Here are some examples for these errors:

Exception in opening zip file: <path>\configuration\org.eclipse.osgi\780\0\bundleFile

Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench".

java.nio.file.NoSuchFileException: <path>\configuration\org.eclipse.osgi\780\0\bundleFile

Proxy could not create EMF Demo1 from provider org.eclipse.gemini.jpa.ProviderWrapper@70f6f135

Additional information: By using the gRPC interface, it is possible to automate specific user actions in the IDE.

When using at least 2 monitors with different screen scaling, the context menu for the FBD-editor is displayed in the wrong position.
Fix: The problem according to the following scenario does not occur anymore if a scaling ≤ 150% is used and the computer has been restarted after the scaling has been changed. Do not use a scaling > 150% to avoid the problem of a misplaced context menu.
Scenario for problem: If you use at least 2 monitors with different screen scaling (e.g. 125% scaling on the primary monitor and 100% scaling on the secondary monitor) and you open the context menu in the FBD-editor, the context menu is opened in the wrong position.
Additional information: This wrong position of the context menu might cause unexpected behavior in the FBD-editor as listed in the release notes for the ID “112715“.

A specific library cannot be created by using “DEPLOY=:OBJECT” when “DEPLOY=:SOURCE” is working.
Note: After the scenario has been analyzed, the customer platform toolkit has been identified to be the cause of the problem, as it is reported by the error part com.logicals.lc3.api.ptk.BuildContext.getResource(). The problem does not occur when considering the SDK API documentation about the interface BuildContext.
Scenario for problem: A customer library can be created with the value DEPLOY=:SOURCE. When the same library is created with DEPLOY=:OBJECT, the following error is reporting:

Cannot invoke "com.logicals.lc3.api.model.Resource.getConfiguration()" because the return value of "com.logicals.lc3.api.ptk.BuildContext.getResource()" is null

Additional information: The keyword DEPLOY defines the format for the element how to copy the statements of the element into the library. 3 values are supported: SOURCE, INTERFACE and OBJECT
At present, there are no details on the actual cause of the problem.

When expanding a library, the application navigator might display the wrong content. Also, the expanding of the library takes longer than expected.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem:When a custom library is expanded in the application navigator, the content of the library is not displayed as expected. An example of the wrong display is that the same folders are displayed repeatedly. As a consequence, too many files are displayed and the expanding of the library takes up to 10 seconds. This expanding is longer than expected.

It is not possible to copy and paste a value field containing an ARRAY variable as expected.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem:It is possible copy and paste a value field containing a variable from one POU to a different POU. But if the value field contains an ARRAY variable, the value field is pasted but it is highlighted as faulty. The reason for this error is that the ARRAY variable is not added in the list of the declared variables.

An insufficient warning might be displayed when using the tool for the automated generation and deployment of a library.
Fix: Add the new configuration variable lc3.router.warning.logging in the new IDE version. Start the command line interface of the new IDE version. Check the added logging information in the standard console to determine the concerned elements that are specified in the insufficient warning.
Scenario for problem:The tool for the automated generation and deployment of a specific library that is invoked with -application com.logicals.library.lc3lib.application reports a warning but its cause and/or fix are not clear. This warning is:

Warning: In ConnEnd::assignPinVisibilityTo(): ConnEnd for connector <number> can't connect to shape <number> since it has no pins with class id of <number>.

Additional information: At present, there are no details on the actual cause of the problem.

Parts of the German IDE documentation for the current version are still provided in English.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: The German IDE documentation for the current version contains some German descriptions but also a lot of English descriptions.
Additional information:Neuron is working on providing the entire German user documentation. Neuron will periodically update the online version of the German documentation that will be provided here: https://help.neuron-automation.eu/Documents/NPE/latest/de.

The IDE documentation does not contain sufficient information about the flags of the TCP_send and TCP_read blocks.
Fix: The IDE documentation has been enhanced by the appropriate information.
Scenario for problem: The TCP_send and TCP_read block provide an input flags. The IDE documentation does not contain sufficient information on how to use this input.

The IDE documentation does not contain an example for the System_write block.
Fix: The IDE documentation has been enhanced by an appropriate example. This example also demonstrates the usage of other blocks for calling system functions.
Scenario for problem: The IDE documentation does not contain an example for the System_write block that demonstrates its usage.

The IDE documentation for the PLCopen blocks contains wrong information about the values for the data type SAFEBOOL.
Fix: The IDE documentation has been corrected so that it contains the correct information.
Scenario for problem:The descriptions of the PLCopen blocks contain the information that the values SAFETRUE and SAFEFALSE are possible for variables of data type SAFEBOOL. However, the actual implementation of the PLCopen blocks is using TRUE instead of SAFETRUE and FALSE instead of SAFEFALSE.

A project folder that is renamed outside the IDE results in duplicated folders/files.
Fix: The problem according to the following scenario does not occur anymore. Also, the following prompt is displayed now when the changed object has been opened in an editor before the project folder is renamed outside the IDE and you are trying to save the opened editor contents after the rename action: The file you want to save does not exist anymore (maybe due to a folder rename outside of the tool). Do you want to recreate the file?
Scenario for problem:When you rename a project folder outside the IDE and you change an object inside this folder within the IDE, the project view displays the original project folder and the renamed project folder. The changed object is displayed under both folders.
Example: You rename the project folder src outside the IDE to src-new. Inside the IDE, you add a call into the opened FBD-object Counter that is located in the folder src and you save the change. Result: The project view displays the original project folder src and the renamed project folder src-new. The FBD-object Counter is displayed under src and src-new.

The application cannot be built if an external variable is declared within a method and this method is declared within a class.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem:If you declare an external variable within a method and this method is declared within a class, it is not possible to build the application using this class.

Missing VarCfg-objects in the project might cause an exception when the DTT has been used to generate these project elements.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When the device topology transformer (DTT) is used to generate project elements or you create some VarCfg-objects yourself and reference them in the PLC-object by the INCLUDE_VARCFG statement, but then the VarCfg-objects are deleted from the project, an exception is caused. In this case, the error logger displays the following message:

Cannot invoke “org.eclipse.emf.ecore.resource.Resource.getURI()” because the return value of “com.logicals.lc3.api.model.st.configuration.VarCfg.Resource()” is null

Additional information:

1. Usually, the DTT is used by a system integrator to generate some project elements based on external data.

2. The missing VarCfg-objects are correctly reported by the error message Could not resolve reference to "VarCfg-object-name".

An invalid object identity is caused when a program instance is disabled in the application navigator.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem:It is possible to disable a program instance in the application navigator. This disabling causes an invalid object identity because the PLC-object is automatically updated when the program instance is disabled but the object identity of the PLC-object is not updated accordingly. The invalid object identity becomes obvious, when you check the object identity and you build the application. In both cases, a dialog about the object identities reports the state “Invalid”. The additional description informs that the file of the PLC-object has been changed.

The version number of the system library is missing in the German message about updating this system library.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When a system library is updated, a message is displayed to inform you about this update. The message in German does not contain the new version number of the system library. Instead of the version number, the message displays: missing argument

An invalid object identity is caused when all variables are removed from the “Values of Variables” view.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When you remove all variables from the Values of Variables view, an invalid object identity is caused for the file testvariables.xml.
The invalid object identity becomes obvious, when you check the object identity and you build the application. In both cases, a dialog about the object identities reports the state “Removed”. The additional description informs that the file has been removed.

Opening of the POU from the “Instances” view might take longer than expected. Scrolling in this POU also might take longer than expected.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When using the smart styling, opening a POU by double-clicking its instance in the Instances view takes up to 90 seconds.
Compare: When using the legacy styling, the opening takes up to 10 seconds.
Additional information: Scrolling in the same POU with smart styling also takes longer than scrolling in a POU with legacy styling.

Removing an object with an invalid object identity might not refresh the project content as expected.
Fix: The problems according to the following scenarios do not occur anymore.
Scenario for problem 1: When the dialog about the object identities reports some objects, it is possible to delete this object by clicking the appropriate button in the dialog. However, after closing the dialog, the object is still displayed in the project explorer.
Scenario for problem 2: When you check the object identity again after the workaround for problem 1, the dialog again reports the object although this object and its object have been removed from the project.

An exception is caused when a global variable is dropped onto a program instance.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: It is possible to drag and drop a global variable onto a POU. This global variable has been declared in a global-object and the drag-and-drop action is taking place in the application navigator. If the target of the drag-and-drop action is a program instance (displayed under the a resource folder), an exception is caused. In this case, the error log displays the message Unhandled event loop exception.

An invalid object identity is caused when a namespace folder is renamed.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When you rename a namespace folder that contains POUs, an invalid object identity is reported.
The invalid object identity becomes obvious, when you check the object identity and you build the application. In both cases, a dialog about the object identities reports the state “Removed” for a file. This file is in context to the namespace folder. The additional description informs that the file has been removed.

Inaccurate validations of the object identity might be caused when an ST-object is deleted outside of the IDE but its ST-editor has been opened inside the IDE.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: There are some unexpected validations of the object identity when performing the following steps:

1. You open the ST-editor for an ST-object.

2. You close the IDE without closing the ST-editor.

3. Outside the IDE, you delete the file for this ST-object.

4. You start the IDE again.
   Result: A message reporting the failed validation of the object identity is displayed. However, this message contains the information that the file has been modified when it has been deleted.

Additional information: When you check the object identity or you build the application, a dialog about the object identities reports the state of H-/C-files to be “Removed”. The additional description informs that the files have been removed. However, these files have not been deleted outside the IDE.

PiL-tests are failing on a specific customer hardware platform.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When running PiL-tests on a specific customer hardware platform, the PiL-tests are failing after some time and the target system is not reachable anymore. A ping neither reproduces a response from the target system.
Additional information: The reason for the problem is the missing keyword Set Defaults in the test suite.

An exception might occur when pasting a copied POU with a specific instance name.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When copying and pasting a POU with a shown instance name that ends with more than ten digits (for example, the instance name is a12345678901 or abcdefghiljklmnopqrstuvwxyz12345678901), an exception occurs. In this case, the error log displays the following messages:

Cannot invoke "java.util.Map.values()" because "this.createdGraphicElements" is For input string: “name”

An exception was ignored during command execution

Missing information about the calling of references to function blocks.
Fix: The IDE documentation has been enhanced accordingly.
Scenario for problem: In the ST-editor, it is possible to call references to function blocks. However, the documentation on this is missing.

The texts “Loaded by” and “Loaded on/at” in the “Instances” view are not accurate.
Fix: The texts have been changed to Built by and Build on/at to reflect that these lines inform who and when the application has been built.
Scenario for problem: The Instances view contains the following pieces of PLC information: Loaded by and Loaded on/at. These pieces of information are displayed when the application is loaded onto the PLC but the information is actually about which user has built the application and when the application has been built.

The access right “Build application” does not prevent the building of the applications for all resources of the configuration.
Fix: There is the new access right Build applications (based on configuration). Uncheck this access right to deactivate the building of the applications for all resources of the configuration.
Scenario for problem: The unchecked access right Build application prevents the building of the application for a resource. But it is still possible to build the applications for all resources when the building is started for a configuration.

The current storing of the team server settings makes it necessary to define the team server data for each installed IDE version.
Fix: The team server data is stored in the workspace. Consequently, it is only necessary to define the data for the team server again when you switch the workspace. This will make the team collaboration easier because the same workspace can be used for newly deployed IDE versions.
Scenario for problem: If you want to work in teams by using a team server, the IDE requires you to define the data for the team server in each IDE version that should be used for working in the team. This makes team collaboration difficult when a new IDE version is deployed.
Additional information: The technical reason for the current procedure is that the team server data is stored in the installation folder of the IDE.

Importing a test suite from Excel might remove the keyword "Set Defaults" in the created test suite file. Subsequently, the tests might fail.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When no initial values are specified for the variables (as these variables are only written as outputs) in an Excel test suite and this Excel test suite is imported, the keyword Set Defaults is missing in the created test suite. When the tests are executed, the tests might fail after some time (see ID “114811” for this problem).

The IDE documentation for com.logicals.builder.lc3builder.application does not mention the option -resourceName.
Fix: The IDE documentation contains the description of the missing option.
Scenario for problem: The IDE documentation for the command line interface for automated builds of PLC applications mentions the option -configurationName but the similar option -resourceName is not described.

A missing file for the invocation of the command line interfaces is not reported.
Fix: The problem according to the following scenario does not occur anymore. Now the command line interfaces com.logicals.builder.lc3builder.application, com.logicals.uploader.lc3uploader.application, com.logicals.library.lc3lib.application and com.logicals.mrc.application return this error: invalid launcher.ini setting, either remove the --launcher.ini setting or specify a valid path
Note: The IDE documentation for all command line interfaces have been updated to emphasize the fact how to correctly invoke the the command line interface.
Scenario for problem: The command line interfaces do not report an error when the command line interface is invoked with the option --lauchner.ini but its specified file is not found.

The Values of Variables view might not display values in case of a longer instance path.
Fix: The view displays the values as long as the instance path is shorter than 1.024 characters.
Scenario for problem: The Values of Variables view does not display values for variables when instance path (with the hierarchical levels including characters, such as . and []) is longer than 128 characters and the Gateway is used for the communication between the IDE and the target system.
Examples for affected target system are the Controllinos.

An error is caused when the tool for automated rule checking is invoked for a project and the report is created outside the project.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When you invoke the command line interface com.logicals.mrc.application for automated rule checking of a project, you specify a location for the report file outside the project (using the options -outputPath and -outputFile), an error is caused. In this case, the following error is output: An internal error occurred during "Object is validated".

Exceptions are caused when the tool for automated rule checking is invoked for a project outside the workspace and the option -checkEmptyWorkspace.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When you invoke the command line interface com.logicals.mrc.application for automated rule checking of a project with the option -checkEmptyWorkspace but the project is located outside the workspace, an exception is caused. In this case, the following messages are output:

2024-08-21 19:22:33 ERROR: Check failed (-6): Workspace not empty

Exception in thread "DB - load project" java.lang.IllegalStateException: Attempting to execute an operation on a closed EntityManager.

at org.eclipse.persistence.internal.jpa.EntityManagerImpl.verifyOpen(EntityManagerImpl.java:2067)

at org.eclipse.persistence.internal.jpa.EntityManagerImpl.close(EntityManagerImpl.java:1908)

at com.logicals.projectindex.Lc3ProjectDatabaseManager.initDbCache(Lc3ProjectDatabaseManager.java:117)

at com.logicals.projectindex.Lc3ProjectDatabaseManager.lambda$0(Lc3ProjectDatabaseManager.java:91)

at java.base/java.lang.Thread.run(Thread.java:840)

2024-08-21 19:22:33 WARN : The workspace will exit with unsaved changes in this session.

A renamed object might be reported as a removed object.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: After an object has been renamed in the application navigator, the dialog Check Object Identity reports this object as a removed object.

The dialog “Object validation failed” is displayed when opening the IDE with automatically opened editors with an invalid object.
Fix: The behavior for the following scenario has been changed as follows: The appropriate editor is not automatically opened. Instead, the following message is displayed: Object "name" cannot be opened due to a mismatch regarding its object identity.
Additional note: The dialog Artifact validation failed has been renamed to Validation failed. This change has been done due to the ID “118674“.
Scenario for problem: When you close the IDE with opened editors and restart the IDE with the same workspace, the IDE automatically opens the same editors. If the editor content has changed outside the IDE, the appropriate editor is still opened and the dialog Artifact validation failed is displayed with the following message: The artifact could not be validated successfully because the file "name" has been changed.
This behavior does not meet the user’s expectations.

The context menu for a configuration in the application navigator contains a duplicate command.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When you open the context menu for a configuration in the application navigator, the context menu provides the command Open and a duplicate of this command. Example: The problem occurs for the object LocalConfiguration in the application navigator.

An exception is caused when an Excel test suite with an invalid value for a variable is imported.
Fix: The problem according to the following scenario does not occur anymore. Instead of the exception, the following message is displayed: The Excel worksheet "name" contains the invalid value "character" in column "name" and row "number"
Scenario for problem: If an Excel test suite contains an invalid value for a variable and this Excel test suite is imported, an exception is caused. In this cause, the following message is displayed: Cannot invoke "org.osgi.framework.BundleContext.getBundle()" because the return value of "com.logicals.lc3.api.common.BundleInformation.getBundleContext()" is null

The object identity might report invalid files when the DTT input topology is changed by deleting some elements that the user expects DTT to remove some files and regenerate.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: The device topology transformer (DTT) generates files but then the user modifies the input topology to have DTT remove some files. Now when the user regenerates the files again via DTT, the dialog Check Object Identity reports modifications for the deleted files. These files are reported with the state Removed.

A project cannot be imported when using a new workspace and an untested team server.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: A project cannot be imported into a new workspace when you are using a team server but you did not test the access to the defined team server.

See ID "114747" in the release notes of the specified version

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).

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

The automatically generated H-/C-files for vendor blocks are not automatically locked. The editor for them is not opened in a read-only mode.
Scenario for problem: If you open an existing object from within the view Team Monitor, the IDE automatically locks this object. If the IDE cannot lock the object, the editor is opened in read-only mode. This is true for a vendor block itself but not for the H-/C-files that are automatically generated for the vendor block.
Workaround: Lock the H-/C-files yourself by opening the context menu for these files within the project explorer and selecting the command Lock selected files.

A memory leak occurs when scrolling through extensive FBD-objects.
Scenario for problem: If an FBD-editor with many pages/objects is opened for a longer period of time and the view onto to the contained pages/objects is changed (= you are scrolling through the FBD-editor), the memory consumption might increase considerably. As a result, it is no longer possible to operate the FBD-editor.
Additional information: The display of the FBD-elements occupies memory. This memory is not freed if these FBD-elements are no longer displayed. The more FBD-elements are displayed by scrolling, the more memory is used.
The problem might occur even earlier, if the FBD-editor contains many OLT-fields and data is displayed in these OLT-fields while testing/debugging.
Workaround to free the memory: Close the FBD-editor and reopen it. Or close the IDE itself and restart it.

Syntax errors might be caused when using the content assist to suppress warnings for rule violations.
Scenario for problem: The IDE documentation contains information to use the content assist when trying to suppress the warning for a rule violation (based on a specified example in the documentation). But when doing this, an error about an unexpected character is caused for the following 2 rules:

• Namespaces of language elements must match the identifier of the parent namespace folder.

• Namespace folders need a unique identifier.

Workaround: none existing

The changed file association is ignored for opening a data type from a library configuration.
Scenario for problem: The user preferences allow to change file associations for data types. However, if you delete the Editor for data types association assigned to the data type .iecst, the graphical enum-editor continues to be opened when opening a data type from a library configuration.
Workaround: none available

No emphasis is displayed when reconnecting existing link elements within the LD-editor.
Scenario for problem: The possible logic elements (e.g. contacts and coils) should be emphasized when reconnecting existing link elements to indicate that you can reconnect the link element to one of these logic elements. However, this emphasis is not displayed within the LD-editor.
Workaround: none existing

The "Team Monitor" view does not determine the status changes on the team server at the expected interval.
Scenario for problem: The upper list under Changed on master of the Team Monitor view shows which changes of the project are available on the team server. If the local files differ from the status of the master, this view should be updated automatically every 30 seconds. However, the list is not updated but it remains empty.
Workaround: Refresh the list yourself by selecting Refresh in the context menu for the list or by pressing the F5-key.

It is possible to turn a folder into a namespace folder and vice versa without the appropriate access control rights to edit the application logic.
Scenario for problem: Without the access right Edit application logic, it is not possible to edit the application logic. However, it is possible to:

• turn a folder into a namespace folder by selecting Assign Namespace in the context menu for a folder within the application navigator.

• remove the namespace assignment and namespaces for objects by selecting Unassign Namespace in the context menu for a namespace folder within the application navigator.

Workaround: none existing

It is possible to assign a USING instruction for accessing a namespace folder and delete this instruction without the appropriate access control rights to edit the application logic.
Scenario for problem: Without the access right Edit application logic, it is not possible to edit the application logic. However, it is possible to:

• assign a USING instruction for accessing the objects of a different namespace folder existing in the application navigator.

• delete such a USING instruction in the application navigator.

Workaround: none existing

The object identity is not created/updated when turning a folder into a namespace folder or assigning a USING instruction for accessing a namespace folder.
Scenario 1 for problem: The file with the object identity is not created, if you turn a folder into a namespace folder by selecting Assign Namespace in the context menu for a folder within the application navigator.
Scenario 2 for problem: If there is a file with the object identity (see "Workaround") and you assign a USING instruction for accessing a different namespace folder, the file with the object identity is not updated.
Additional information: The problems only occur, if you are using the feature "object identity". The missing/outdated file with the object identity is not reported to the user. The problems become only obvious if the user tries to execute an actions with the namespace folder (e.g. moving the namespace folder is not possible).
Workaround after any action regarding a namespace folder: Locate the file .iecproperties in the namespace folder. Observe that this file is hidden in the project explorer and application navigator by default. Therefore, uncheck the filter for .* resource to display the file in the project explorer. Then open the file .iecproperties in a text editor of the IDE, make a minimal change (e.g. add a blank) and save the change in order to create/update the object identity.

Building an application might lead to linker warnings.
Scenario for problem: Depending on the used toolchain, linker warnings might occur when building an application. The warnings are caused by a discrepancy between extern declarations and the definition of symbols in the C-code. The problem has been observed when using external variables in the ST-code or in the FBD-logic.
Workaround: Ignore the warnings.

Objects in nested namespace folders do not have a nested namespace.
Scenario for problem: If you create a namespace folder as a subfolder in an existing namespace folder, the objects in the subfolder are only declared in the namespace of this subfolder. However, the expectation is that the objects are declared in a nested namespace, as nested namespaces for ST-objects and FBD-objects are possible according to the IDE documentation and the IDE-documentation for the namespace folders does not contain any information whether nested namespaces are possible for nested folders.
Example: The namespace folder NS1 contains the subfolder NS2 that is also a namespace folder. The objects in the namespace folder NS2 are declared in the namespace NS2. However, the expectation is that the objects are declared in the nested namespace NS1.NS2.
Workaround: none existing

The initialization of structure elements is not possible when creating a new structured variable via the content assist.
Scenario for problem: When creating a value field with a new variable via the content assist, it is not possible to enter an initial value for a variable that is declared based on a structured data type. For instance, if you enter Var1: myStruct := (Elem1 := true) (where myStruct is the structured data type and Elem1 one of its structure elements), the message Invalid expression is displayed.
Workaround: Create the variable without the intial value. For instance, enter Var1: myStruct in the content assist. Afterwards go the the list of the delared variables, double-click the created variable to open the dialog to modify its data. In the field Initial value, enter the initial value, e.g. (Elem1 := true) for the above example.

An exception might be caused when importing an existing access rights configuration.
Scenario for problem: If an existing access rights configuration is imported into a closed project, an exception is caused. In this case, the text java.util.NoSuchElementException: No value present is displayed in the error log.
Workaround: Import the access rights configuration into the opened project.

After a failed loading of the application, GUI elements in the “Instances“ view might not be in sync.
Scenario for problem: When using a microcontroller system without a separation between firmware and application (e.g. when using Controllinos as PLCs), it is possible that some of the GUI elements in the Instances view are not correctly synchronized. The problem has been observed after an application could not be loaded onto the PLC because the application used too much RAM. The following happened after the Gateway closed the connection:

• The button Connect to PLC was enabled but the line Connection state displayed Online.

• All other information about the PLC displayed Unknown”.

Workaround: Click the button Connect to PLC again to update the state. Subsequently, the line Connection state displays Online with the execution state Error.

A FORCEMRK block with a connected RS block causes errors when building the application.
Scenario for problem: When you connect the input of the FORCEMRK block to the RS block (see the following example for ST-code) and build the application, the following errors are reported:

from <project_path>\src-gen\localconfiguration\local.builtinplc\rismd\allmd.sys-gen.c:6:

<project_path>/target/localconfiguration/local.builtinplc/sys-gen/rismd/mdfu___forcemrk.rs.c:7:88: error: unknown type name 'LC_TD_FunctionBlock_FORCEMRK__RS'

FUNCTION_BLOCK TestSTErr

VAR

iFM1 : FORCEMRK;

iRS, iRS_O : RS;

END_VAR

iFM1(IN:=iRS, OUT=>iRS_O);

END_FUNCTION_BLOCK

As a consequence, it is not possible to build the application.
Workaround: none existing

The keyboard shortcut Ctrl+Shift+S is not supported for the safety parameter editor.
Scenario for problem: When different editors contain unsaved changes, it is possible to save all changed as follows: In menu File, select Save All. But the appropriated keyboard shortcut Ctrl+Shift+S is not supported, when the safety parameter editor is active.
Workaround: Use the command Save All.

Double-click onto an OLT-field does not open the dialog to change the value.
Scenario for problem: You are not able to change the value of a variable within an OLT-field which is displayed in the LD-editor. The reason for this: Double-click onto the OLT-field does not open the dialog.
Workaround: none existing

After inserting several FBD-elements, an exception might be caused and the connection lines might not be displayed as expected.
Scenario for problem: If you copy several networks consisting of a few value fields, blocks, and line connections and you paste them onto a different page, an exception might be caused and some connection lines between the value fields might not be displayed as expected. In this case, some lines even seem to be missing and the error log displays this message:

org.adaptagrams.ColaException: ERROR: Critical assertion failed. expression: find(actionList.begin(), actionList.end(), ActionInfo(ShapeAdd, shape)) == actionList.end() at line 287 of router.cpp

Workaround: Save, close and reopen the FBD-editor.

Pasting resources might not lock the pasted resource.
Scenario for problem: When you use a team server, created resources are automatically locked. This applies to pasted resources as well but not when copying and pasting is done by the commands Copy and Paste.
Workaround: Copy and paste the resources by holding the Ctrl-key while dragging the resources from the original location to the new location. At the new location, you must release the Ctrl-key.

The content assist allows to create an array variable of the data type STRING but without a length. Such value fields are not highlighted as faulty.
Scenario for problem: It is possible to use the content assist to create an array variable of the data type STRING but without a length. Example: Var1: ARRAY[0..1] OF STRING
Subsequently, the FBD-editor does not highlight the value field as faulty. However, the Problems view reports an appropriate message.
Workaround:Edit the variable in the list of declared variables so that the length is declared. Example: ARRAY[0..1] OF STRING[10]

Automated building, deploying and/or verifying of libraries takes longer than the appropriate GUI action.
Scenario for problem: When you use the tool com.logicals.library.lc3lib.application for the automated building (=generation) and deployment of a library, this action takes longer than the appropriate action that is triggered in the GUI.
Workaround: none existing

“Going Into” for a project in the application navigator expands the project infinitely.
Scenario for problem: When you select the command Go Into from the context menu of a project within the application navigator, the refocus on the project is not as expected. Instead of the refocus, the project folder is displayed as 2nd subfolder, as 3rd subfolder, as 4th subfolder etc.
Workaround: none existing

The validation reports are overwritten when building the safety-related application for all resources of the configuration.
Scenario for problem: It is possible to build the application for all resources of the configuration by selecting the configuration in the Instances view and clicking the button Build Application. When this building is done for a safety-related application, the applications (meaning all resources included in the configuration) are automatically validated. During the validation, one report is generated for each resource. But for the configuration-based building, the previously generated report gets overwritten by the next report. Subsequently, only one validation report is generated - this report is the one for the last included resource.
Workaround: Select the resource in the Instances view and click the button Build Application. Repeat this action for each resource.

When using at least 2 monitors with different screen scaling, some GUI elements for the FBD-editor are displayed in the wrong position.
Scenario for problem: If you use at least 2 monitors with different screen scaling (e.g. 150% scaling on the primary monitor and 125% scaling on the secondary monitor), the following GUI-elements are opened in the wrong position:

• the tooltip for an FBD-element, for example the name of the SEL block
  The tooltip is displayed outside of the IDE window whereas the tooltip should be displayed directly over the FBD-element.

• the content assist to create new FBD-elements
  The content assist is displayed outside of the IDE window whereas the content assist should be displayed over the current mouse position.

Additional information: The context menu for the FBD-editor is displayed in the correct position if a scaling ≤ 150% is used (see the release notes for the ID “112715“ for details).
Workaround, if this is sensible: Use the same screen scaling for all monitors.

When using at least 2 monitors with different screen scaling, a GUI element for the team monitor is displayed in the wrong position.
Scenario for problem: The Team Monitor view provides a list of the currently opened team projects. If you use at least 2 monitors with different screen scaling (e.g. 150% scaling on the primary monitor and 125% scaling on the secondary monitor), this list is opened in the wrong position. Instead of under Select project, the list is displayed outside of the IDE window.
Workaround, if this is sensible: Use the same screen scaling for all monitors.

A local variant for a library element is reported with the state “Added” by the dialog “Check Object Identity”.
Scenario for problem: When you create a local variant of a library element in a project, the dialog Check Object Identity is reporting this local variant with the state Added. This behavior is not as expected because the local variant has been created inside the IDE.
Workaround: Click the button Reevaluate the object identity of the project in the dialog.

The content assist lists function blocks although they cannot be used in the FBD-editor.
Scenario for problem: You can use the content assist to create calls of function blocks in the FBD-editor. This content assist even lists function blocks when they contain unsupported language elements for the FBD-editor. For example, methods cannot be used in the FBD-editor. When you select a function block containing a method in the content assist list, the call is inserted. Subsequently, the Problems view reports the created call by an appropriate error message.
Workaround: none existing

An exception is caused when an LD-editor with changes is closed and you choose to save the changes.
Scenario for problem: When an LD-editor contains unsaved changes and you close this editor, a question appears whether to save the changes. If you choose to save the changes, an exception is caused. In this case, the following message is displayed: java.lang.UnsupportedOperationException at com.logicals.iec.model.generator.expression.VoidExpressionGenerator.getExpression(VoidExpressionGenerator.java: ...
Workaround: none existing

The migration wizard does not detect export problems when the export tool is terminated unexpectedly.
Scenario for problem: The migration wizard migrating a predecessor project to a Neuron Power Engineer project contains an export test. This export test checks whether the project can be successfully exported/migrated. The export test fails to discover problems when the export tool is terminated unexpectedly.
Workaround: none existing

The project explorer displays an option that is expected to be hidden.
Scenario for problem: When the system integrator has activated a profile, specific GUI elements are hidden. For instance, the commands to import a project are hidden. However, the empty project explorer still provides the option to import a project.
Workaround: none existing

The safety parameter editor might show an empty group when bulk editing is used.
Scenario for problem: When safety parameter data is changed in the bulk editing mode and only one subfolder containing the safety-relevant hardware devices has been selected, the safety parameter editor shows an empty group.
Workaround:Select different subfolders before invoking the bulk editing mode.

When using a monitor with a screen scaling >= 150%, a GUI dialog is not displayed as expected and cannot be used.
Scenario for problem: If you use a screen scaling >= 150%, the dialog to rename an element is not displayed as expected. The input field to enter the new name is truncated and cannot be used.
Workaround, if this is sensible: Use a screen calling less than 150%.

Overlapping names for block inputs and outputs are actually displayed as overlapping names.
Scenario for problem: When you are using the smart styling for the FBD-editor, the interface editor uses this smart styling as well. When there are are longer names for an input and the opposite output in the block interface that is too small, these names are overlapping instead of the expected truncation of the names.
Workaround: none existing

The German IDE displays the wrong characters for messages with umlauts, if these messages are reported by the safety parameter editor.
Scenario for problem: When the IDE displays German messages reported by the safety parameter editor, the umlauts in those messages are not displayed as expected.
Workaround: none existing

The search view due to command “Find References” is not provided when a profile is activated.
Scenario for problem: When GUI-elements have been deactivated in the IDE due to a profile, the command Find References in the list of the declared variables does not work. The following message is displayed: The search result view could not be activated.
Workaround: Use the default profile to provide all GUI elements.

An exception is caused when importing a project when a profile is activated.
Scenario for problem: When GUI-elements have been deactivated in the IDE due to a profile, an exception is caused when selecting the command Import projects in the project explorer list. In this case, the dialog to import the project is not opened and the error log displays this message: Exception in org.eclipse.ui.internal.views.helper.EmptyWorkspacHelperImport.Action.run: ...
Workaround: none existing

An exception is caused when creating an Excel test suite in the application navigator
Scenario for problem: When you use the wizard to create a test suite and then export it to Excel, an exception is caused. The dialog for the wizard is not closed and the error log displays this message: java.lang.UnsupportedOperationException: Not possible to create test suite for <folder> at com.logicals.lc3.testframework.testsuite.ui.internal.NewTestSuiteWizard.init(NewTestSuiteWizard.java:54)
Workaround: none existing