Release notes for version 3.27.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.

If you want to use special characters (e.g., umlauts, or kanji characters) in the installation or workspace folder, Neuron recommends substituting the folder path with the command subst of the operating system.

See the troubleshooting article “Special characters in path prevent loading of application” for details.

Starting with this version, only one instance of Neuron Power Engineer can be started at the same time on the same computer. If an instance of Neuron Power Engineer is already running and a user tries to start another instance, this fails. The message Instance of Neuron Power Engineer is already running informs the user about the already locked instance.

When it should be possible to start multiple instances again, contact your administrator and ask to define the configuration variable -Dnpe.start.allow-multiple-instances and make sure that its conditions are met. See the English documentation “IDE administrator's manual” for details.

It is possible for a system integrator to use/activate profiles to hide GUI-elements. The command Show in - System Explorer has been hidden when using the profile beginner_integrated. On a request, this command and all commands in the menu Show In are provided again when this profile is activated.

Opened editors in Neuron Power Engineer detect external changes to the content of a file. When this occurs, a message is displayed, allowing the user to choose whether to update the content of the editor.

In the previous version of Neuron Power Engineer, updates were allowed even for an invalid object identity. The current version reports the change and indicates if the object identity is invalid. In such cases, the user must close the editor without saving the changes.

The safety parameter editor provides these new GUI elements:

• an input field to filter the parameter values by their names; see "Filtering the safety parameters" for details.

• the button Start the bulk editing; see "Bulk editing of safety parameters" for details.
  This button starts the bulk editing within the safety parameter editor. It can be used for bulk editing the safety parameters provided in the same safety-relevant hardware devices as well as for safety parameters provided in different safety-relevant hardware devices. So, this new button is an additional possibility to the existing bulk editing variant by the command Bulk editing safety parameters provided in the context menu of the application navigator.

1. Neuron Power Engineer now offers two different modes for global variables: the IEC mode as well as the smart mode. While the IEC mode uses the familiar behavior according to the IEC standard, the smart mode handles global variables in a simplified way. For details see "Smart mode for global variables" in the user documentation.

2. External variables can now be declared based on global variables by using a second list in the content assist of the ST editor. For details see "Content assist in the ST-editor" in the user documentation.

The test framework has been revised as follows:

1. The test framework detects when the Excel file for a test suite has been modified when the test is started for the test suite file. In this case, you can decide if you want to reimport the Excel file.

2. The product name in the generated test report has been changed to a generic name.

The safety parameter editor enables safe commissioning by allowing parameter changes at application runtime.

The GUI of the safety parameter editor includes a check box in the column Commissionable. When this box is selected, additional rows appear to configure commissioning properties, such as the default value.

The safety parameter editor highlights changes to commissioning properties in the same way as for other parameter values. See "Viewing or changing the current parameter values" for details.

The dialog Check Object Identity includes a button to reject a deviation for the selected file. In the previous version, clicking this button deleted the selected file.

In the current version, the user can choose to either revert the file to its shadow copy or delete it. In both cases, the deviation is rejected.

When developing safety-relevant applications and libraries for them, you must use a version of the Neuron Power Engineer that has been released for this purpose. The installed files of such a version must not be modified.

To make it easier to detect modifications, the installation is now verified. This means that upon startup, the Neuron Power Engineer automatically verifies the installed files. If any modifications are detected, a dialog will inform you that the MD5 validation failed. See "Verification of installation" for details.

the Neuron Power Engineer allows you to include a custom library with user blocks directly in the current project by default. Contact your system integrator to activate project-local libraries. Observe the following:

• Project-local libraries will be used in all projects created, imported, or opened in the Neuron Power Engineerr. So, when a library is installed, this library is automatically copied within a project folder that is hidden in the Neuron Power Engineer by default.

• System libraries, e.g. the library Standard (safe) will automatically copied into the project. So, the system libraries become project-local libraries as well.

• When you update to a successor version of the Neuron Power Engineer, the project-local libraries (incl. the system libraries copied into the project) are not automatically updated.

This ensures that projects are self-contained, and the libraries used are independent of the the Neuron Power Engineer version. This simplifies sharing projects with other users. See "Using project-local libraries" for details.

When the behavior for the project-local libraries is not activated, the default behavior is still valid. This default behavior is identified as legacy mode for the libraries in the IDE documentation.

Important: The activated behavior for project-local libraries should not be changed back to the legacy mode. If this is done anyway, the opened projects with the libraries are broken. To briefly test the behavior for project-local libraries, Neuron recommends using a new, empty workspace for the Neuron Power Engineer and importing/opening a project copy in this workspace. This leaves your original workspace and projects intact to continue using the projects and libraries with the legacy mode.

There is an additional system library Standard (legacy) with 9 blocks. The behavior of these blocks match the behavior of the blocks from the predecessor product of the Neuron Power Engineer. See the IDE documentation "Standard blocks (legacy)" for details on these blocks.

Observe that this system library is not provided in all variants of the Neuron Power Engineer. Contact Neuron, if you are interested in this system library.

The device topology transformer (DTT) supports the specification for IO_IMPORT within the PLC-object. Such statements are used by the system integrator to activate the IO-services on the target system.

Example for such a statement: { IO_IMPORT PROVIDER := GenericProvider, SERVICE := GPID }

A memory leak occurs when scrolling through extensive FBD-objects.
Fix: The problem according to the following scenario does not occur anymore.
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.

The keyboard shortcut Ctrl+Shift+S is not supported for the safety parameter editor.
Fix: The problem according to the following scenario does not occur anymore.
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.

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.
Fix: The problem according to the following scenario does not occur anymore. The content assist displays the message Strings with undefined length are not allowed to indicate the missing length.
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.

“Going Into” for a project in the application navigator expands the project infinitely.
Fix: The problem according to the following scenario does not occur anymore.
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.

When using at least 2 monitors with different screen scaling, some GUI elements for the FBD-editor are 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. 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).

A local variant for a library element is reported with the state “Added” by the dialog “Check Object Identity”.
Fix: The problem according to the following scenario does not occur anymore.
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.

The migration wizard does not detect export problems when the export tool is terminated unexpectedly.
Fix: The problem according to the following scenario does not occur anymore.
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.

The project explorer displays an option that is expected to be hidden.
Note: This problem has not been fixed. Usually, the users of the profile “beginner (integrated)” do not use an empty project explorer.
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.

When using a monitor with a screen scaling >= 150%, a GUI dialog is not displayed as expected and cannot be used.
Fix: The problem according to the following scenario does not occur anymore.
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.

An exception is caused when trying to create an Excel test suite for a folder in the application navigator.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When you use the wizard to create a test suite for a folder, 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)
Additional information: Actually, a folder is not supported to create a test suite at all.

The start of the IDE with a separate workspace from the command line might fail with exceptions.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: It is possible to start the IDE with a separate workspace and a specified project from the command line. An exception occurs, when this workspace and project do not exist and/or the topology parameters are insufficiently specified. In this case, the console displays one of these messages:

Exception in thread "Thread-165" org.eclipse.swt.SWTException: Device is disposed at org.eclipse.swt.SWT.error(SWT.java:4918) ..

or

at com.logicals.lc3.dev.transformer.core.internal.DeviceTopologyTransformerImpl.validate(DeviceTopologyTransformerImpl.java:384) at com.logicals.lc3.dev.transformer.core.internal.DeviceTopologyTransformerImpl.safeGeneration(DeviceTopologyTransformerImpl.java:286) …

An exception is caused when importing a project when a profile is activated.
Note: This problem has not been fixed. Usually, the users of the profile “beginner (integrated)” do not use an empty project explorer.
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

The IDE documentation does not contain sufficient or correct information on reports or a headless tool invocation.
Fix: The IDE documentation has been updated so the corresponding information is correct or provided.
Scenario for problem: The IDE documentation contains information on:

• the MRC-report for validation

  Here, the specified name object-name.iecplc.res.mrclog of the MRC-report for a resource is wrong. The correct name is: object-name.iecplc.res.resource-name.mrclog

• the tool for automated builds of PLC applications

  Here, the IDE documentation does not contain information on where the build report is generated. Also, the IDE documentation describes that the invocation is possible for a configuration and a resource whereas the invocation is possible for a configuration or a resource.

An exception occurs when trying to open an invalid object in the application navigator.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When using the feature "object identity" and you try to open an invalid object by double-clicking the object in the application navigator, the expected message is displayed that the object could not be validated because the file has been changed. But after confirming this message, an exception is caused. In this case, the following message is displayed:

An error occurred. ...

Cannot invoke "org.eclipse.xtext.ui.editor.model.IXtextDocument.tryReadOnly(org.eclipse.xtext.util.concurrent.IUnitOfWork)" because the return value of "org.eclipse.xtext.ui.editor.XtextEditor.getDocument()" is null

Additional information: An invalid object is an object that has been modified outside of Neuron Power Engineer. It is not possible to open an invalid object. The reported deviation must be approved or rejected by using the dialog Check Object Identity.

External modifications for an open editor might be approved without user information.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When using the feature "object identity", the following steps cause an unexpected behavior:

1. Open the editor for an object (eg. an ST-object). Keep this editor open.

2. Modify the object outside of Neuron Power Engineer.
   Additional information: This external modification makes the object to be invalid. This has the consequence that it is not possible to open an invalid object in Neuron Power Engineer. The reported deviation must be approved or rejected by using the dialog Check Object Identity.

3. Change back to Neuron Power Engineer where the editor of the modified object is still opened.
   There is no user information that the object has become invalid and the editor stays open.

4. Double-click the object in the application navigator to refresh the editor content.
   There is still no such user information on the invalid object. But now the opened editor contains the external modifications.

5. If you change the object in the opened editor and save the changes, the external modifications will be saved in Neuron Power Engineer as well.
   Now the external modifications are approved in Neuron Power Engineer without any user information.

The IDE is not started from the command line when the start command includes topology parameters.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: It is not possible to start the IDE from the command line when the start command contains the parameters for a project topology update -topologyPath and -topologyType. Instead of the expected IDE start, an exception occurs. In this case, the message Unhandled event loop exception is displayed. The details on this exception are:

org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException: Cannot invoke "org.eclipse.ui.IWorkbenchWindow.getShell()" because the return value of "org.eclipse.ui.IWorkbench.getActiveWorkbenchWindow()" is null)

...

Caused by: java.lang.NullPointerException: Cannot invoke "org.eclipse.ui.IWorkbenchWindow.getShell()" because the return value of "org.eclipse.ui.IWorkbench.getActiveWorkbenchWindow()" is null

Refactoring in an ST-editor might cause an exception.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When a variable declared in an ST-editor is refactored, an exception occurs. In this case, the following message is displayed: Cannot invoke "org.eclipse.ui.lWorkbench.getProgressService()" because "this.workbench" is null
Additional information: The POU contains the statement {safeSimplified} for the language characteristics. Also, the version is started by using substituted drives for the installation folder and the workspace.

Building the safety-relevant application containing a data type is not be possible for a project or its path starting with “h”.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: If the project name or a folder of the project path starts with the character h, a data type is used in the application and this application is a safety-relevant application, it is not possible to build the application. The error log and the build report reports the following messages:

Fingerprints do not match for POU "name". Expected "number" but was "number"

File <%projectpath%>\src-gen\lcdt___name.c\u0027 does not exist

The safety parameter editor might show an empty group when bulk editing is used.
Note: The problem according to the following scenario does not occur anymore.
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.

The execution order of an FBD-network might not be as expected when this FBD-network contains value fields with structure elements.
Fix: The problem according to the following scenario does not occur anymore. Additional information on the fix: Variables with different array indexes (e.g., Var1[1] and Var1[2]) or different structure elements (e.g., VarA.Elem1 and VarA.Elem2) are treated as distinct variables, just like Var1 and Var2. This information has also been added to the IDE documentation.
Scenario for problem: The execution order of networks in FBD is evaluated according to the IEC-standard. And according to the IDE-documentation, the value of variables needs to be calculated at first even if they are located on the down right side, when they will be used for calculating another value on the upper left side. But this is not true when the value fields contain structure elements.
The execution order is as follows:

But the expectation of the execution order is as follows:

An exception might occur when trying to open an invalid object in the project explorer.
Fix: The problem according to the following scenario does not occur anymore.
Scenario for problem: When using the feature "object identity" and you try to open an invalid object by double-clicking the sub-level of an ST-file (= the ST-object itself, e.g. the ST-program that is contained in the ST-file) in the project explorer, the expected message is displayed that the object could not be validated because the file has been changed. But after confirming this message, an exception is caused. In this case, the following message is displayed:

An error occurred. See error log for more details.
Cannot invoke "org.eclipse.xtext.ui.editor.model.IXtextDocument.tryReadOnly(org.eclipse.xtext.util.concurrent.IUnitOfWork)" because the return value of "org.eclipse.xtext.ui.editor.XtextEditor.getDocument()" is null

Additional information: An invalid object is an object that has been modified outside of Neuron Power Engineer. It is not possible to open an invalid object. The reported deviation must be approved or rejected by using the dialog Check Object Identity.

See ID "120822" 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.

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.

FBD-elements are highlighted as faulty in the opened FBD-editor, if the corresponding C-file has been opened while cleaning the project.
Scenario for problem: If you have opened an FBD-editor and the corresponding C-file while the project is being cleaned, the lines and the connected block calls are highlighted as faulty in the opened FBD-editor. If you move the mouse pointer onto the error icon of the call, these messages are displayed for each block and block input: Could not resolve reference to '_name_'. A variable with this name does not exist.
Additional information: Usually, C files are not displayed in the views with the resources (e.g. the project explorer). However, C files can be displayed in the project explorer, if you deactivate the src-gen folder filter for the view. In this case, it is also easy to open the editor for a C file from within the project explorer.
Workaround: Close and reopen the FBD-editor

The sort order might not be as expected, when moving multiple global variables or sections in the global-variables-editor.
Scenario for problem: When you are moving multiple global variables or sections in the global-variables-editor, the variables or section might not be sorted as expected.
Workaround: none existing

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.

Error message about invalid namespace is not sufficiently visible in the FBD-editor.
Scenario for problem: If you enter an invalid namespace (e.g. 11) in the tab “Namespace” of the FBD-editor, an appropriate error message is displayed but the message is not entirely visible.
Additional information: A namespace must be an IEC-identifier. See “→IEC-identifier” for details.
Workaround: Enter an IEC-identifier as namespace to avoid getting the error message.

It is impossible to move a global-object into a namespace folder.
Scenario for problem: When you are using namespace folders in the application navigator, it is impossible to move a global-object from a regular folder into the namespace folder.
Compare: It is possible to create a global-object in this namespace folder.
Workaround: Removing the namespace assignment so that the folder becomes a regular folder. Move the global-object into this folder. Then turn the folder into a namespace folder again.

The context menu in the “Instances” view might not be displayed for the first mouse click.
Scenario for problem: A context menu is usually displayed in the “Instances” view if you click the →secondary mouse button (= press and release) in this view. But this is not true for the first time clicking this mouse button in the view.
Workaround: Click the secondary mouse button a 2nd time to display the context menu.

The wrong timestamp might be displayed for a locked object.
Scenario for problem:The column Locked on in the list under Locked by me of the team monitor might display a wrong timestamp for a locked object.
Workaround: none existing

The opening of an FBD function block takes longer than expected.
Scenario for problem: The opening of a specific FBD function block takes up to 5 seconds. In previous versions, this opening of this block took only up to 1 second.
Workaround: none existing

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

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.

Deleting resources might take longer than expected.
Scenario for problem: When you use a team server and delete some resources in a project, deleting 10 resources might take up to 40 seconds.
Workaround: none existing

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

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.

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

It is not possible to change the value of a variable within an OLT-field for an LD-editor.
Scenario for problem: When you debug the logic element within an LD-editor, the OLT-fields displays the values of the variables. It is not possible to change the values in the LD-editor because the expected dialog is not opened.
Workaround: Change the values in the Values of Variables view.

Information under “Blocks for safe logic” in the IDE documentation is wrong.
Scenario for problem: The topic “Blocks for safe logic” in the IDE documentation contains a list of blocks that can be used to develop safety-relevant applications. This list contains the following blocks that cannot be used in safety-relevant applications:

• BCD_TO_DINT

• BCD_TO_INT

• BCD_TO_LINT

• BCD_TO_SINT

• BCD_TO_UDINT

• BCD_TO_UINT

• BCD_TO_ULINT

• BCD_TO_USINT

• CONCAT_DT

• DT_TO_DATE

• FROM_BIG_ENDIAN

• FROM_LITTLE_ENDIAN

• IS_VALID

• TO_BCD_BYTE

• TO_BCD_DWORD

• TO_BCD_LWORD

• TO_BCD_WORD

• TO_BIG_ENDIAN

• TO_LITTLE_ENDIAN

Additional information:

• When these blocks are used in an FBD-editor, they are highlighted as safe logic. Still, it is not possible to build the application.

• All these blocks are part of the library Standard (non-safe).

Workaround: Do not use these blocks for safety-relevant applications. For details on which blocks are unsupported for safety-relevant applications, see the documentation "Safety instructions on working with the IDE" (= the safety manual), “Appendix: List of unsupported and restricted elements”. Contact your system integrator or Neuron to obtain this documentation.

not released yet

not released yet

V3.0