Release notes

Area

Functionality

Valid as of

Project Builder

Solved: Visibility rules for configuration variables in Macro-Typicals were lost as soon as you used Macro-Typicals in instantiated Typical-Groups.

  • Visibility rules defined for configuration variables in Macro-Typicals are now retained for instantiated Typical-Groups.
V2.9 Update 1
Project Builder

Creating a new target project

Instead of selecting a target project in Designer, you now have the possibility to create a new project. To do so, click the selection box in the header. After you have clicked the selection box, three input fields appear in which you can enter the project template, the storage location and the new project name.

You can also choose to overwrite an existing project using the selection switch.

V2.9
Project Builder

XML import

You can now import an XML file even if values for a configuration variable marked as "Mandatory" are missing. Values for configuration variables in the Project Builder that do not exist in the XML file are retained during import.

If you use configuration variables and instances in the XML file that do not exist in the Typical, an error message is displayed.

V2.9
Project Builder

Overwriting a project in silent mode

The default value for the "Overwrite" function has been changed from 1 to 0. If you do not enter anything in the command line, an existing project is not overwritten.

V2.9
Project Builder

XML import

It is no longer necessary to set values in the XML file to be imported for all configuration variables. The XML import also functions when configuration variables in the XML file do not contain any values.

The contents of the XML file are also combined with the existing configurators, provided that the variable values do not overlap.

V2.9
Project Builder

Silent mode

You can also generate a project documentation in Project Builder by using the command line. An interaction with the software user interface of the Project Builder is not required in that case. It is possible to select a library, a target project, a configurator, Macro-Typicals or Typical-Groups and import a XML file.

To this purpose start your EPLAN platform with the command line. By entering the parameters you specify which elements are to be used for the generation of the project documentation.

V2.9
Designer

Solved: Problems with renaming variables when Ladder logic is enabled.

  • Renaming is now possible.
V2.8 HF4
Designer

Replacing a macro

You can replace a macro in a Macro-Typical with another macro. Existing variables and formulas will be retained. Differences between the original macro and the new macro are displayed in a dialog window. Subsequently you have the possibility to decide whether to replace the macro or not.

To replace a macro, select a new macro in the EPLAN platform and click .

V2.8 HF3
Designer

Displaying existing references

Click the button in the element list to display all references that exist in a macro. The list of references can be copied into the clipboard.

V2.8 HF3
Designer

New variable _elementindex_

The variable _elementindex_ refers to the numbering of a Macro-Typical or a Typical-Group in the element list. The variable can be entered in all formula windows (except in the formula window for the visibility of configuration variables) and adopts the respective value of the numbering. When you change the order, the value is adjusted automatically.

V2.8 HF3
Designer

Solved: Elements could not be deleted from a Typical-Group with a Cogineer Basic license. An error message was displayed.

  • The error message is no longer displayed.
V2.8 HF2
All

Solved: It is not possible to set the configuration variable Double if the operating system is set to Polish or Czech and if the value is entered with a comma. An error message is displayed.

If the value of the configuration variable is entered with a period, an error message is displayed during generation.

  • The error message is no longer displayed.
V2.8 HF2
All

The export of records

All records available in the library can be exported as an archive. The archive contains an own XML file for each record. The records are sorted according to the names of the configurators and the Macro-Typicals. The individual variables of the records are exported without the associated values. You can find the values as a comment in the corresponding section of the XML file. You can reimport the individual XML files in the Project Builder.

To do this open the corresponding library in Designer. Then open the Settings dialog and click the Export all records button.

The button is only displayed if the opened library actually contains records that can be exported.

Read more

V2.8 HF1
Designer

Numbered elements

The list of elements within Macro-Typicals and Typical-Groups is numbered. If you delete or add elements, the numbering is modified automatically.

V2.8 HF1
All

New license model

The license model for EPLAN Cogineer has changed. Depending on your license a different functional scope is available to you in the different ranges of the software.

Read more

V2.8
All

Solved: If the Designer and the Project Builder are executed at the same time and they work in both ranges at a library with the same name, error messages are displayed that are not applicable.

  • The error messages are not displayed anymore.
V2.8
Project Builder

Performance enhancement: During the generation of the product documentation, specific elements are generated multiple times and overwritten. The process is slowed down by this.

  • Before an element is generated, a check is carried out whether it already exists. This way all elements are only generated once. The process is accelerated significantly.
V2.8
Designer

Solved: If the window in which Designer is executed is very narrow, the buttons Save and Close are not displayed in the Extended Formula Input dialog.

  • A minimal width is defined for the Extended Formula Input dialog. This way the buttons are always displayed. If the dialog is not fully visible, enlarge the window in which Designer is executed.
V2.8
Designer

Solved: Adding faulty macros to a Macro-Typical leads to a system crash of the EPLAN platform.

  • If faulty macros are added to a Macro-Typical, a corresponding error message is displayed. The EPLAN Platform continues to be executed.
V2.8
Designer

Solved: The entry fields in the Multilingual input dialog are aligned differently.

  • All entry fields are correctly aligned.
V2.8
Designer

Solved: Some designations in the software user interface and some error messages are not translated.

  • All designations and error messages are translated.
V2.8
Designer

Solved: If you do not specify the Display name of a configuration variable, an error message is displayed that the Macro-Typical or the Typical-Group is a duplicate.

  • A message is displayed that you have to enter a Display name in at least one language.
V2.8
Designer

Copying of configuration variables

Configuration variables that you have defined in a Macro-Typical can be copied to a Typical-Group if the Macro-Typical is part of the Typical-Group. In the past only the configuration variable and the list of predefined values were copied. Now the Display name and the Mandatory status of the configuration variable are copied additionally.

V2.8
Designer

Solved: In some cases the current formula was not displayed in the Extended Formula Input dialog. Instead an older version of the formula was displayed.

  • The current formula is always displayed.
V2.8
Designer

Solved: For macro projects that are not saved in the default folder for projects of the EPLAN platform, the synchronization between the macro project in the EPLAN platform and the Cogineer does not function.

  • When the synchronization is started, a check is first carried out whether the corresponding macro project is opened in the EPLAN platform. Only if the macro project is not open, is a check carried out whether the macro project is located in the default folder for projects.
V2.8
Designer

Solved: For macro projects whose name contains a dot, the synchronization between the macro project in the EPLAN platform and the Cogineer does not function correctly.

  • The synchronization of the macro functions correctly even if the name of the macro project contains a dot.
V2.8
Designer

Extension of the formula editor

During the creation of formulas for controlling the status of a macro and for controlling the visibility of configuration variables you now have an alternative editing possibility in the formula editor. The elements that you can use for the creation of a formula are displayed in lists. You select the required elements and establish a relation between them. The resulting formula is generated automatically. A manual entry of the formula is not required in this case.

Read more

V2.8
Designer

XML export

You can carry out an export as an XML file for all elements of a configurator. To do this open the configurators tab. In the list of the elements you find the button for each element to start the export.

The XML file contains all configuration variables but without the corresponding values. The name, type and, if existing, predefined values of the configuration variables are shown as a comment in the XML file. Specify values for the configuration variables in order to use the file for configuration in the Project Builder.

Read more

V2.8
Project Builder

XML import

Instead of carrying out a configuration manually, you can also import from an XML file. The XML file must contain a certain structure so that it can be imported.

Read more

V2.8
All

Working with instances

The usage of instances allows you to define the functions of your product, which may occur several times, within one Typical-Group. At the definition of Typical-Groups you have the possibility to allow the generation of several instances of an element of the Typical-Group. The designer in Project Builder then has the possibility to flexibly extend the functional scope of your product.

Read more (Designer)

Read more (Project Builder)

V2.8
Designer

Formula editor

The button is located at all points at which you can work with formulas. Click the button to open a formula editor for the corresponding input box. The formula editor offers you many additional editing options:

  • Multi-line input with more overview
  • Automatic completion
  • Highlighting in color of specific elements
  • Find and replace

Read more

V2.8
Designer

Adding macros on a specific position to Macro-Typicals

The button is located at all elements of a Macro-Typical. If you click the button, the macros that have been selected in the macro navigator of the EPLAN platform are added below the element. All following elements are moved downward accordingly.

Read more

V2.8
Project Builder

Performance enhancement: The Typical.xml configuration file contains all instructions that are required for the generation of a project documentation. Macros that are available in a configurator but are not required for the generation of the project documentation due to a configuration in Project Builder were previously all entered individually in the configuration file. Now they are only entered once. This allows the configuration file to be processed more rapidly and the project documentation to be generated more rapidly.

V2.8
Designer

Solved: The pre-defined type of a configuration variable is not available anymore if you are switching between the Macro-Typicals, Typical-Groups and Configurators tabs.

  • The pre-defined type now remains.
V2.8
Project Builder

Solved: Since EPLAN platform Version 2.8 you have the possibility to specify in the project settings whether a macro can be inserted with or without a macro box. In the past this did not have any effect in EPLAN Cogineer.

  • This setting is now also taken into consideration for the generation of the project documentation in EPLAN Cogineer.
V2.8
Designer

Solved: The error message 'The configuration variable "xxx" cannot be deleted, because it is still referenced' is displayed even if references do not exist anymore.

  • The error message is only indicated if references actually exist.
V2.8
Designer

Solved: Moving a configuration variable via the button does not function correctly if the Visibility entry field of the configuration variable is displayed.

  • Moving a configuration variable functions as expected.
V2.8
Designer

Solved: The automatic completion for formulas is activated if the view of a macro is extended.

  • The automatic completion for formulas is activated when you enter a formula in an entry field.
V2.8
Designer

Definition of dynamic configuration user interfaces

In Designer you now have the possibility to define dynamic user interfaces for configurators in Project Builder. The user interface of a configurator is assembled from the Display name of all configuration variables, for which no fixed values were defined in Designer. You can now make the Visibility of these configuration variables dependent on conditions. To do so insert a corresponding formula as usual. This way you can for example make the display of the 'Enclosure light' option dependent on whether the '24 V enclosure light' option was selected beforehand.

V2.7 HF2
Project Builder

Automatic display of newly generated project pages in the graphical editor

If you are re-generating an existing project documentation after a change in the configurator, the project page in the target project which was shown in the graphical editor of the EPLAN platform before the generation is now automatically displayed. This means that you do not have to manually navigate to the page anymore. The Workflow which you follow for testing a change, is considerably reduced this way.

V2.7 HF2
Designer

Localized identifier blocks

In Designer the individual identifier blocks are now also displayed localized. They are always displayed in the language that you have currently set as the dialog language in the EPLAN platform. This affects the Settings dialog and the Structure section in the extended view of a macro.

V2.7 HF2
Designer

Extension of the Copy & Paste functionality

As of now you can also copy and paste contents in Designer in the Multilingual input dialog.

V2.7 HF2
Designer

Solved: Faulty representation of the content of a library

  • Regardless of whether you have opened one or several libraries in the page navigator of the EPLAN platform the content of the selected library is always displayed in Designer.
V2.7 HF2
Designer

Overview of all existing references to a configuration variable

In Cogineer Designer you can display all existing references to a configuration variable in an overview. This overview appears for different actions:

  • When changing the name of a configuration variable
  • When deleting the name of a configuration variable
  • After clicking on the button
V2.7 HF1
Designer

Duplication of macros in a Macro-Typical

In Designer you can duplicate macros within a Macro-Typical. The name of the macro is not changed in the process. All data that you have entered in the extended view of a macro are adopted.

V2.7 HF1
Designer

Adding several macros in one step

In Designer you can add several macros to a Macro-Typical in one step. To this purpose select the relevant macros or directories in the macro navigator of the EPLAN platform and then click the button Add macro in the workspace.

V2.7 HF1
Designer

Macros are automatically active after being added

In Designer there is a new default behavior. After you add macros to a Macro-Typical, their status is set to Active.

V2.7 HF1
Designer

Formulas remain unchanged when the status of a macro is changed

Formulas that you use to reference the status of a macro with a configuration variable also remain unchanged. You do not have to re-enter the formula after you have reset the status.

V2.7 HF1
Project Builder

Reuse of configurations in Project Builder

In Project Builder you can later reuse the data that you have entered in a configurator. To do so save the configuration in a record. When you subsequently open the configurator again you can select the saved configuration from a drop-down list instead of entering all the data once more. If the configurator has already been used before for the specified target project, the most recently used configuration from the target project is loaded.

V2.7 HF1