Release notes for version 3.24.0
This article contains the release notes for Neuron Power Engineer version 3.24.0.
Up-to-date information within online-version Please check the online-version (provided under https://help.neuron-automation.eu) whether new pieces of information have been added since this user manual (as PDF/HTML/Word) has been published; e.g. the release notes quote new problems or there are new articles in the troubleshooting- or FAQ-section. |
Release-Notes for previous versions of Neuron Power Engineer are provided in the online-version under https://help.neuron-automation.eu only.
In this article: |
---|
General information
About compatibility: |
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.
|
|
On the Log4j security vulnerability: |
See "Is the IDE affected by the Log4j security vulnerability (December 2021, CVE-2021-44228, Log4Shell)". |
|
About system libraries: |
||
About the illustrations in the IDE documentation: |
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. |
General information for runtime system and target systems
About the →runtime system : |
If you are using Neuron Power Engineer version 3.24.0, install and use the version 5.19.0 of the runtime system.
If you are using an older version of the runtime system, it might not be possible to successfully connect to the target system from within Neuron Power Engineer (see troubleshooting article "No connection to the target system, but there are error messages)". |
About →Raspberry Pi : |
See the tutorial "Putting Raspberry Pi into operation" which version is recommended by Neuron for usage. |
About the runtime system for safety projects: |
If you are using logi.µSRTS version V1.0.0 (with a logi.µSRTS Core version ≥ 1.17.0) or V2.0.1 (with a logi.µsRTS Core version V2.0.0) together with the current version of Neuron Power Engineer, observe that the alarm messages of these logi.µSRTS versions are still containing the previous product name of the development environment. This previous product name is "logi.CAD 3" whereas the current product name is "Neuron Power Engineer". In spite of the previous product name, the alarm messages apply to Neuron Power Engineer as well. |
New features in Neuron Power Engineer version 3.24.0
This section informs you about the latest new features for this version.
ID |
Component |
New feature |
|
---|---|---|---|
59503 | IDE, workspace, libraries |
With the positioning of the Neuron brand, there is a breaking change in this version:
As a consequence, the following changes have been made:
The IDE documentation reflects all these changes. As a short name for the company, “Neuron” is used in the IDE documentation.
Observe that the alarm messages of some logi.µSRTS versions have not been changed regarding the product name. They still contain the previous product name “logi.CAD 3” but they apply to Neuron Power Engineer as well. See the section “General information for runtime systems and target systems” for the affected logi.µSRTS versions. |
|
59605 | Declaring variables |
When you declare a variable by using the command New Variable... in the list of declared variables visible, the behavior of the opened dialog has been changed as follows: In case of missing or incorrect data for the variable, the respective field in the dialog is now highlighted with a red border and an error icon. When you move the mouse pointer over this error icon, a message details the error. In previous versions, the button OK has been highlighted with an error icon and only a generic message has been displayed. The new error highlighting makes it easier for you to fix the error for the variable declaration. |
|
62386 |
Safety-relevant applications, FBD-editor |
If you are creating safety-relevant applications, keep in mind that calls of blocks are no longer automatically updated when you open the FBD-editor if the interface for the blocks has changed in the interface editor. However, you remain able to update a changed interface yourself by selecting the call and pressing Ctrl+1 or the F5-key. You can find more details on the update under "Updating existing calls for changed interfaces". |
|
62479 | List of declared variables, FBD-editor | Now the list of the declared variables in the FBD-editor allows you to copy and paste existing variables and/or instances with a unique name. The data of the copied variables/instances (e.g. data type, initial value) are automatically entered in the pasted variables/instances. See "Copying and pasting variables/instances" for details. |
|
62506 | "Instances" view, FBD-editor with/without instance context |
When editing or debugging POUs in the FBD-editor, the IDE can open two different tabs of editing mode and debugging mode at the same time. This is the default behavior:
Now it is possible to change the default behavior so that just one tab is opened for editing and debugging POUs in the FBD-editor. If you are interested in this behavior, ask the system integrator to activate the new configuration variable This possibility helps to avoid any synchronization issues between editing and debugging tabs. But mind that the closing and opening of the tabs might change the tab order. |
|
62558 |
Safety-relevant applications, Building the application |
The HTML-report that is generated when the application is built (also called build report) does now contain the information whether a task is defined as IO task. This information is displayed along with the other data for the program structure. This new information is of particular interest when building safety-related applications. |
|
108422 | Validating an application | When validating an application, you can configure the rules to be applied for a resource in the Configure Validation for resource name dialog. Now you can resize this dialog and change the arrangement of the areas in the dialog so that there is more space for the list of rules, for example. | |
108515 | FBD-editor |
The FBD-editor can now be used with 2 different stylings:
See “Smart styling for the FBD-editor” for details and illustrations of how the FBD elements are displayed. All other illustrations with FBD elements in the user documentation use the legacy styling.
If the styling is changed, observe that the new styling is applied only to the newly created project. Already existing projects will not be affected by a changed styling. The chosen styling applies to all FBD-POUs in the project. It is not possible to mix legacy and smart styling within the same project. Moreover, 2 new properties are provided for implementing vendor blocks. These properties are applied for the smart styling only. These properties are:
See “Properties for implementing vendor blocks” for details on the properties for implementing vendor blocks. |
|
108552 | ST-editor, classes |
You can create ST-classes, also identified just as “classes”. A class is a program organization unit (POU) consisting of:
A class is similar to a function block. See “Declaration of a class in ST“ on the ST-syntax of a class and the differences to a function block. Observe that:
Also, It is possible to deploy a function block with methods by using the value “ |
|
108625 | ST-editor, reference variables | You can use a function block as the type when you declare reference variables. In previous versions, this has not been possible. See “Declaration of reference variables (incl. assignments to them)“ on the ST-syntax of a reference variable. | |
108648 | ST-editor, reference variables | You can use a classe as the type when you declare reference variables. See “Declaration of reference variables (incl. assignments to them)“ on the ST-syntax of a reference variable. | |
108877 | Java, JRE |
The Java Runtime used by Neuron Power Engineer has been updated to version 17.0.9 to fix a memory leak. See “Why do I need JRE?” for more information why JRE is needed for Neuron Power Engineer. |
|
110995 | ST-editor |
The attribute Here the attribute See the syntax under topic “Declaration of a structured data type with partial address in ST“ and “Declaration of a language element with partial address in ST“. |
|
111007 | ST-editor |
When you declare a structured data type in the ST-editor and specify the optional attribute Here is an example to illustrate the calculation using
More examples can be found in the topic “Declaration of a language element with partial address in ST“. |
|
111149 | Safety parameter editor |
Now you open the safety parameter editor as follows:
In previous versions, the command was provided in the context menu for the configuration itself. In the current version, the configuration contains the new folder Moreover, observe that the button Save all in the safety parameter editor is not provided anymore. Just use the button Save group that is still provided at the end of the group with the safety parameter editor. |
|
111198 | Validating an application |
The standard package of the IDE provides the new rule Limited variability languages (LVL) must be used only. Use this rule to check whether the application uses elements that do not follow the guidelines for limited variability languages (→LVL). As usual for rules, you can change the configuration of this rule. |
|
111209 | Application navigator |
Now, the application navigator displays the project blocks and global variables of the entire project. Observe that these elements are displayed under the folder Compare the behavior in previous versions:
|
|
111245 | Target system, accessing IOs |
For accessing IOs, mind that specified warnings/notes apply. See Properties and restrictions specific to the target system“, section Accessing IOs“ for details. These warnings/notes are also included in the document “Safety instructions on working with the IDE” under “Warnings/notes for accessing IOs“ because they are relevant when you are developing a safety-related application. |
|
111598 | Interface editor |
The tab Properties of the interface editor provides the new setting Safe style. Neuron recommends to use this safe style only if a block tracks safe signals when developing safety-related applications. Do not misuse this setting for other blocks. See “Defining background color for the interface” for more information on the impact of this setting. |
|
111977 | PLCopen blocks, IDE documentation |
In the current IDE version, the PLCopen blocks are now based on the technical specification "TC5 - Safety, Version 2.10 – Official Release, Part 1 - Concepts and Function blocks" (© PLCopen). In the previous IDE version, the blocks were based on the version 2.01 of the technical specification. Please observe that the description in the IDE documentation has not been updated to reflect this implementation change. The description will be updated in future versions. In the meantime, if you need information on the changed behavior of the PLCopen blocks, please contact Neuron. |
|
111979 | IDE documentation |
Starting with version 3.24.0, there are some changes for the online documentation:
Observe that there are some restrictions:
|
New features relating to the runtime system and target systems
ID |
Component |
New feature |
---|---|---|
|
|
none |
Fixed problems in Neuron Power Engineer version 3.24.0
If not otherwise stated, this sections informs you about problems that have occurred in version 3.23.2 and have been fixed for the current version 3.24.0.
ID |
Component |
Fixed problem |
||||
---|---|---|---|---|---|---|
54528 | FBD-editor, namespaces |
Declaring a namespace in the FBD-editor might cause errors in the FBD-editor.
If you save the changes, the Problems view also displays this message and similar messages. |
||||
58528 |
PLC-object, building the application |
Formatting the PLC object might cause an error in the specifications for PARAMS. As a result, it is not possible to load the application onto the PLC.
If you format the code in the PLC object using the context menu command Source, Format or the keyboard shortcut Ctrl+Shift+F, the path specification after |
||||
59213 |
"Instances" view, vendor blocks |
The fingerprint of the application is not updated in the "Instances" view when changing C-sources.
|
||||
59774 |
Building the application |
Changed applications for PTK GCC 10.2.x may fail to build.
Additional information: The problem occurs only if the platform toolkit does not contain the |
||||
60255 |
FBD-editor, "Problems" view |
The quick fix to resolve errors in the "Problems" view may not work.
|
||||
60268 |
Test framework |
A test suite with a name that is too long cannot be exported to Excel.
|
||||
60476 |
IDE documentation |
The order of 2 illustrations in an article of the IDE documentation is wrong.
|
||||
60771 |
Migration |
The migration of constants may cause an error in the target project.
|
||||
60783 |
Access rights |
A dialog for saving the changes is displayed by mistake.
|
||||
60825 |
Interface editor |
The preview of the interface editor is not updated correctly when undoing the creation of a value field.
|
||||
60829 |
Interface editor |
It may not be possible to undo the creation of a comment field within the interface editor.
|
||||
60833 |
Interface editor |
The deletion of elements within the interface editor may need to be undone twice.
|
||||
61061 | Instance data |
An exception occurs when instance parameter are copied in a dialog.
Additional information:
|
||||
62735 |
List of declared variables |
A STRING variable cannot be changed in the dialog.
|
||||
62839 |
OLT-field |
Special characters within OLT fields are not evaluated as expected when debugging an application.
Scenario for problem: When debugging an application, if you enter special characters, such as umlauts or texts with several lines, using the three-character combination (starting with the dollar sign ($) and followed by 2 hexadecimal digits), the entry is not evaluated as the expected character. |
||||
106944 |
List of the declared variables |
The initial value of declared variables might not be changed.
|
||||
106952 |
Properties field, FBD-editor |
The application cannot be built if the characters * / are contained in a property field in FBD.
|
||||
106958 |
ST-editor |
The application cannot be built if the characters */ are contained in a property field in ST.
|
||||
107041 |
Application navigator, global-object |
A global-object can be renamed to an invalid name in the application navigator.
|
||||
107075 |
FBD-editor |
The call of a block can be enlarged, although this should not be possible.
|
||||
107259 | IDE, device topology transformer (DTT) |
Unexpected behavior of features in the case of the missing configuration variable -Dlc3.serverport=50055.
|
||||
107327 |
Global-variables-editor |
The global-variables-editor might not display the expected icon for some variables.
This means that the icon or is displayed for such variables in the global-variables-editor. But only the icon should be used for this. |
||||
107391 |
ST-Editor, building the application |
It might not be possible to build the application due to a called method.
After the attempt to build the application, the messages are displayed in the Problems view. Here are the messages for the customer scenario in which the problem occurred:
|
||||
107403 | Application navigator, namespaces | Moving/copying a subfolder into a namespace folder does not update the namespace for the included objects. Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: If you use a namespace folder, the IDE is updating the namespace during actions in the application navigator. This update takes place when moving/copying objects into a namespace folder, but not when moving/copying a subfolder with objects into a namespace folder. After the move/copy action for the subfolder, deviations are reported because the namespace in the objects of the subfolder and the namespace folder do not match. Workaround: Only move or copy objects into a namespace folder, but not subfolders. |
||||
107430 |
Global-variables-editor |
Undoing/Redoing the delete action for all sections does not work as expected.
|
||||
107517 |
Building the application, ST-editor, FBD-editor |
It is not possible to build the application, if a function block variable is assigned to the ANY input of a function block.
In this case, the following messages are displayed:
Additional information: The problem also occurs in the FBD-editor. There, the line between the value field containing the function block variable and the
|
||||
107563 | FBD-editor |
An exception is caused by a wrong array initialization when creating a new structured variable via the content assist.
|
||||
107568 |
List of the delared variables |
An exception is caused when initializating structure elements while creating a new structured variable in the list of the declared variables.
|
||||
107681, 107686 |
FBD-editor | When using the content assist to create new variables, a possible conflict to existing variables of another variable section is not reported. The existing variable is automatically used.
Note: The IDE documentation has been updated in the current version to inform about the behavior for the following scenario. Observe that the implementation has not been changed in the current version. Scenario for problem: It is possible to create values fields with new variables by using the content assist. For instance, the input L, C : var5 : BOOL := TRUE means that one value field will be created and it is to contain the internal variable (due to the prefix L for the section of the local variables, also known as internal variables) with the name var5 of data type BOOL and the initial value TRUE . Due to the prefix C , the variable is also declared with the keyword CONSTANT .But in the case that there is already a variable with the same name and data type but this variable has been declared in a different section, this existing variable is automatically entered in the value field. So for instance, if there is an external variable var5 of data type BOOL but no initial value, this external variable is entered in the value field. During the input, there is no message reporting this conflict. Moreover, there is no information that the existing variable has been entered instead of the internal, constant variable var5 (with the specified data type and initial value) and that this new variable has not been created at all.Additional information 1: The IDE documentation does not specify the behavior for the above problem Additional information 2: In the case that there is already a variable with the same name but a different data type, this conflict is reported and it is not possible to declare the new variable. A similar behavior has been expected for the above problem, even if the IDE documentation does not specify the behavior. |
||||
108015 | Safety parameter editor, IDE documentation |
The IDE documentation on the safety parameter editor does not contain information on the valid range for floating point value.
Moreover, if a specified value cannot be precisely interpreted as a floating-point number, the safety parameter editor corrects the value to the corresponding floating-point number.
Example: The value
|
||||
108037 | Test framework |
An exception occurs during the SiL/PiL test for a library block.
|
||||
108083 | Creating custom library with user blocks | The IDE documentation does not specify clearly that the preferences for the library providers are just for the configuration of the library providers.
Fix: Now the IDE documentation makes it clear that the preferences for the library providers are just for their configuration and that a selection does not change the library provider to be applied for the projects. Scenario for problem: The IDE documentation contains information about the library providers “Local file system” and “Current project”. The IDE documentation also specifies that the options for the library providers can be inspected and changed in the preferences (menu “Window”, “Preferences”, group “Library Provider”, “Library Provider”). However, it does not specify that the changes for a library provider are just applied to the configuration of the library providers. Observe that the selection of the library provider does not change the library provider to be applied for the projects. |
||||
108088 | List of the declared variables | The initial value of declared variables might not be changed. Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: If a reference variable is declared or a variable is declared based on a function block, it is not possible to enter or change the initial value for this variable by clicking on the Initial value field in the list of the declared variables. It is also not possible to enter or change the initial value by using the command Edit Initial Value or Ctrl+I. |
||||
108117 | "Build Log" view, vendor blocks |
The fingerprint of the built application might not be updated in the "Build Log" view when the C-sources are changed.
|
||||
108128 | Test framework |
Specific notations for duration literals, date and time literals and time of day literals are not supported when defining intial values for outputs in the test case.
If you use this notations, the tests will be failing because the intial values are not considered as expected. |
||||
108217 | FBD-editor |
Changing the instance name does not update the referenced instance name.
|
||||
108344 | "Instances" view | The version specification under "Recommended version" for the runtime system in a customer version is not displayed as expected.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: The Instances view displays the item Runtime system below PLC information. The sub-items list information on the used runtime system on the PLC (type and version) as well as a recommendation which version should be used for the application. In a customer version, however, the item Recommended version does not display the expected version specification for the runtime system. Instead of this, the version specification is displayed with the suffix SNAPSHOT . |
||||
108389 | Application navigator | A closed project can still be expanded in the application navigator.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: If you close a project, the project can still be expanded in the application navigator. In this case, the application navigator only shows the folder Project blocks for the closed project. |
||||
108394 | Application navigator | The name of a created project might not be displayed in the application navigator.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: If you create a project in the project explorer and then switch to the application navigator, it is possible that the name of the created project is not displayed in the application navigator. |
||||
108513 | ST-editor |
When using ST data types with the SIZE/OFFSET pragma, mapping variables to IEC hardware addresses might produce wrong copy sizes and bit offsets.
|
||||
108609 | IDE documentation, data types |
The IDE documentation contains wrong information: The lower and upper limit is not correctly specified for the data type BOOL.
|
||||
108741 | Building the application | The same error text is displayed twice for the same exception.
Fix: The dialog displays the heading “Error in platform toolkit” for such customer-specific errors in the platform toolkit. Scenario for problem: In a customer-specified version, customer-specific errors might be reported when an exception occurs while building the application. The dialog reporting this exception displays the same error twice. Additional problem: The customer-specific error has been realized in the platform toolkit. The same error text is used for the heading as well as the details of the dialog. |
||||
109272 | ST-editor, reference variable |
The assignment to a reference variable is reported as an error by mistake.
The following error message is reported: |
||||
109920 | Command line interfaces, headless tools | Exceptions are caused in the command line when building or deploying libraries by using the headless tool. The libraries are built/deployed anyway. Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: When you are using the headless tool for the automated building (=generation) and deployment of libraries, an exception might be caused in the command line where the headless tool is invoked. |
||||
110255 | Safety-relevant applications | Wrong customized files for starting the IDE might be included in the file configuration\com.logicals\configuration.idx. Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: Before starting the IDE to build safety-relevant applications and/or libraries for these applications, you must verify that the IDE has not been modified. This is done by checking the md5sum of the file configuration\com.logicals\configuration.idx .
However, the file might contain the wrong files. Hence, the verification is not possible as the safety manual instructs.Additional information: This problem only applies to a customer version for which the files have been customized regarding its file name. |
||||
110566 | Opening the help | An exception is caused by opening the help for an data type.
Fix: The problem according to the following scenario does not occur anymore. Scenario for problem: If you select the command Show Help for a data type, the help is not opened. Instead, an exception is caused. In this case, the error log displays this message: Unhandled event loop exception |
||||
111403 | FBD-editor |
A wrong error about a safety conflict is reported when a function block instance is connected to the input of a SEL block.
|
||||
111453 | ST-editor |
The application cannot be built using an external variable declared in the ST code and an input variable declared in a function block. Both variables have the same name.
|
||||
111873 | System blocks, PLCopen blocks |
Missing information about the behavior of output “ENO” for the PLCopen blocks.
|
Changes affecting the code generation
The following changes in Neuron Power Engineer version 3.24.0 affect the automatically generated C-code (and thus the built application), even if you do not make any changes in the application yourself. Observe that when you load the application, the changed code will be loaded onto the PLC.
Change |
Starting with version |
More information on the change |
---|---|---|
none |
|
|
Note: The flag SAFETY means that the change must be taken into account in particular when developing safety-relevant applications. A change without this flag applies to a functionality/configuration which is not supported for the development of safety-relevant applications. |
Known problems in Neuron Power Engineer version 3.24.0
ID |
Component |
Known problem |
|
---|---|---|---|
49494 |
Application navigator, |
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.
|
|
49498 |
Application navigator |
The command "Go Into" in the application navigator does not behave as expected.
|
|
59175 |
Teaming up to create applications, vendor blocks |
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.
|
|
60703 |
Validating the application |
Syntax errors might be caused when using the content assist to suppress warnings for rule violations.
Workaround: none existing |
|
60726 |
IDE |
The changed file association is ignored for opening a data type from a library configuration.
|
|
60776 |
LD-editor |
No emphasis is displayed when reconnecting existing link elements within the LD-editor.
|
|
61171 |
Teaming up to create applications |
The "Team Monitor" view does not determine the status changes on the team server at the expected interval.
|
|
61175 |
Access control |
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.
Workaround: none existing |
|
61183 |
Access control |
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.
Workaround: none existing |
|
61187 |
Artifact identity |
The artifact identity is not created/updated when turning a folder into a namespace folder or assigning a USING instruction for accessing a namespace folder.
|
|
107348 |
Building the application |
Building an application might lead to linker warnings.
|
|
107379 |
FBD-editor |
The IDE documentation differs from the implementation in a special case for replacing a block call.
Here is the illustration from the IDE documentation in which the value field with the access
|
|
107419 |
Application navigator, namespaces |
Objects in nested namespace folders do not have a nested namespace.
|
|
107558 |
FBD-editor |
The initialization of structure elements is not possible when creating a new structured variable via the content assist.
|
|
107713 |
Access control |
An exception might be caused when importing an existing access rights configuration.
|
|
107764 | FBD-editor, Cleaning the 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 |
|
107789 | Global-variables-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 |
|
108722 | PLCs, Connecting to the PLC |
After a failed loading of the application, GUI elements in the “Instances“ view might not be in sync.
Workaround: Click the button Connect to PLC again to update the state. Subsequently, the line Connection state displays Online with the execution state Error. |
|
109235 | Safety-relevant applications |
The integration acceptance tests cannot be executed because of missing files.
|
|
109982 | Safety-relevant applications |
The build report might contain error messages about unverified data types.
Workaround: In an ST program or an ST function block, declare an internal variable ( |
|
110582 | Text files |
A message is displayed when entering “**” at the beginning of a text file.
|
|
111534 | Building the application |
The application cannot be built when a function block instance is assigned/connected to the input of a SEL block. The application for the PLC (resource "name1", platform toolkit "name2") cannot be created/loaded. Check the views "Error Log" and "Problems" for more information. An error occurred during compiling or linking the code image (error code: 1).After the attempt to build the application, messages are displayed in the Problems view. Here are the messages for the described scenario: implicit declaration of function 'LC_INIT_DataType_SR'; did you mean 'LC_INIT_DataType_SAFEBOOL'? [-Werror=implicit-function-declaration] in expansion of macro 'LC_INIT_Function_SEL__DERIVED_SR' in expansion of macro 'LC_INIT_IMPL__SEL__DERIVED'
Additional information 1: The same problem also applies to other blocks, e.g. |
If your problem is not listed in this list, check these sections: Troubleshooting and FAQ
Addendum: Known issues after the release of Neuron Power Engineer version 3.24.0
This section was last updated on: 2024-04-12
For issues discovered after the release of Neuron Power Engineer version 3.24.0, please refer to the release notes of the successor versions. Both the list of known problems and the list of fixed problems might contain descriptions of problems that are relevant for Neuron Power Engineer version 3.24.0.
Issues that have been reported before the successor version has been released are listed below. This list is updated at regular intervals (see the date after the section heading). If you need more up-to-date information, please contact Neuron .
ID |
Known problem |
---|---|
59779 | 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. |
112265 |
Deviation in the technical specification for PLCopen blocks, current version 2.10 to previous version 2.01.
|
112370 | The “Application” folder might not display any additional decorators, such as the decorator for errors/warnings.
Scenario for problem: Additional decorators within an object icon inform about the state of the object (e.g. that it is faulty or that there is a warning for this object). These decorators are also provided within a folder icon to inform about the states of the objects that are included in the folder. However, these decorators are missing for the Application folder.Workaround: Expand the Application folder to view the states of the included objects. |
112386 | Renaming a configuration or resource in the application navigator does not update the associated items there.
Scenario for problem: When you rename a configuration or resource in the application navigator (e.g. by using the command Rename), the folders Sources for configuration and Sources for resources are not updated appropriately. Instead, these folders do not contain any objects anymore. This is because the associated folders for the configuration/resource have not been renamed as well. The project structure still displays the folders with the previous names whereas the Sources for configuration and Sources for resources folders are already looking for the objects in the folders with the new names. Workaround: Change to the project explorer. There, rename the folders with the previous names for the configuration/resource. Then change to the application navigator and refresh the view. |
112411 | 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. |
112437 | An empty folder is displayed under the project, when a new folder is created under the “Application” folder.
Scenario for problem: When you create a new folder under the Application folder in the application navigator, an item without any name is displayed under the project folder. This empty item is automatically selected. Workaround: Refresh the view so that the empty item disappears. Do not delete this empty item. If you do anyway, the new folder will be deleted as well. In this case, just press Ctrl+Z to undo the deleting. |
112463 | The renaming of the in-/outputs in the interface editor might not update the dirty flag as expected.
Scenario for problem: If you rename an in-/output in the interface editor by using the command Edit Name or the F2-key, the name of the in-/output is changed in this editor but the dirty flag might not be displayed for the interface editor. Additional information: The problem has been detected for some workstations only. On other workstations, the problem did not occur (so the dirty flag has been displayed as expected). At present, there are no details on any differences between the workstations or for the deviations on the scenario performed on the workstations. Workaround: none existing |
112473 | Unexpected message on a failed resizing of a block with a fixed size.
Scenario for problem: If the setting Fixed Size is checked within the interface editor, it is impossible to make a call of the block larger or smaller. When you try to enlarge such a call to adjust the size of several FBD-elements in one by using the commands Layout and Same Size, this unexpected message is displayed: A selected block cannot be made smaller because of a minimum height or width for the block. Workaround: none existing |
112484 | 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. |
112503 | 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. |
112508 | The “Application” folder does not display the expected content for a library configuration.
Scenario for problem: When you create a library configuration in the Application folder, 2 items are displayed instead of the expected object for the library configuration:
Workaround: none existing |
112523 | The IO code is not synchronized/updated after some changes in the VAR_CONFIG hardware addresses.
Scenario for problem: When you change hardware addresses in the section VAR_CONFIG … END_VAR (inside a section RES_VARCFG … END_RES_VARCFG ), save the changes and you rebuild the application, the IO code is not updated as expected. Instead, the original hardware address is still being considered.Additional information: The file IOAccess.c is not generated anew.Workaround: Clean the project after the changes and before the building. Then the IO code is updated as expected. |
112570 | Duplicate global variables are possible in the global-variables-editor.
Scenario for problem: When you sort the existing global variables and then you change the section of the global variable that is the last item in the editor, the global-variables-editor displays a duplicate for the global variable just modified. Workaround: Save the changes in the editor, close and reopen the editor. Then the editor does not display the duplicate variable anymore. |
112666 | The wrong timestamp is displayed for a locked object.
Scenario for problem: The column “Locked on” in the list under “Locked by me” of the team monitor displays a wrong timestamp for a locked object. Workaround: none existing |
112671 | The context menu for the team monitor might not be opened at the current mouse position. Scenario for problem: If you use a different screen scaling than 100%, the context menu for the team monitor is opened at a different position than the current mouse position. Workaround, if this is sensible: Use a screen scaling of 100%. Or use the keyboard shortcut, if such a shortcut is provided for the command provided in the context menu. |
112676 | 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 |
112681 | The command “Add Variable to Values of Variables” might create a duplicate of the view.
Scenario for problem: When you perform the following steps, a duplicate view of Values of Variables is displayed (instead of bringing the existing view to the front):
Workaround: none existing |
112715 | When using a different screen scaling that 100%, the FBD-editor might not behave as expected.
Scenario for problem: If you use a different screen scaling than 100% and you open the context menu in the FBD-editor, the following issues have been observed:
Additional information: The changed scaling seems to cause this problem. For both issues, the context text appears to be opened for a wrong FBD-element whereas the context menu is opened at the position of the current mouse cursor. Regarding example 1, the command to create the OLT-field appears to be disabled because the drawing field is incorrectly considered to be the valid context. |
Checksum for components of Neuron Power Engineer version 3.24.0
This section is not relevant for Neuron Power Engineer version 3.24.0.
Component |
Version |
Checksum |
Description |
---|---|---|---|
Neuron Power Engineer IDE |
version3.24.0 |
|
|
system library |
version 3.7.0 |
|
|
system library |
Version 1.2.0 |
|
|