This functionality is only available for certain module packages.

Release Notes

Area Feature Version
Job Server

Hostnames with underscore are allowed for Job Server Worker

Starting with version 2.9 SP1 Update 5, Job Server Workers whose host names contain an underscore can also be registered on the Job Server (e.g. DE_345).

2.9.SP1 Update 5
Form-UI

If any editor in which a change is made is opened in parallel to the Form-UI view, the Form-UI view will no longer assume the "dirty" state.

2.9.SP1 Update 5
Basic workflow

If parameters are inserted into the Parameters editor between existing parameters by drag & drop, the the order of the inserted parameters is preserved. If a sorting ist set for the Parameters editor, the inserted parameters are sorted accordingly.

2.9.SP1 Update 5
Basic workflow

The Navigator view is always synchronized with the referenced Windows folder when it is opened, so that only existing project files can be opened and no exception is thrown.

2.9.SP1 Update 5
Basic workflow

A project can be exported without errors even without a mechatronic structure.

2.9.SP1 Update 5
Commands

When a sequence of commands containing a command that executes a file selection dialog (for example, importing a PX file) is called in a fileSelectionForm, the SaveActiveEditor command can then save any changes that have occurred.

2.9.SP1 Update 5
PLC/CoDeSys

If actions are called multiple times, including on a network socket on which the reference is placed, an improved message is issued.

2.9.SP1 Update 4
PLC/CoDeSys

The order in which the PLC code is generated has been improved. Prior to generation, all existing actions and methods are removed from the program module and only added at the end of the generation. This prevents interactions of the block code with the code of the actions and methods.

2.9.SP1 Update 4
PLC/CoDeSys

In order to mark the inputs and outputs of logic blocks as a socket, it is no longer necessary to repeat them elsewhere in the resource and mark them there as type Socket. It is sufficient if the corresponding EEC parameter has the type Socket and the VarType REPLACE.

2.9.SP1 Update 4
Basic workflow

Built-in components can be moved error-free within the Component Editor using drag-and-drop.

2.9.SP1 Update 4
Basic workflow

An EOX model with a modified formula can be imported into an existing model without error, even if an editor is still open for resolving a conflict. This applies to both 2-way mixing and 3-way mixing.

2.9.SP1 Update 4
Basic workflow

A formula can be copied to the Value field in the Parameter editor of a project component while the formula inspector is active.

2.9.SP1 Update 4
ECAD

If the optional Remote API feature is installed, the P8 communication runs without errors.

2.9.SP1 Update 3
Web EEC

For the Web EEC, parameters can be transferred error-free using the URL.

2.9.SP1 Update 3
Form-UI

Neue Java VM-Argumente für Form-UI

To start EEC directly with a Form-UI page, it is now also possible to specify separately the project component containing the Form-UI page and the ID of the Form-UI page:

-Dcom.mind8.formui.perspective.object=<absolute path to object holding the Form-UI>

-Dcom.mind8.formui.perspective.form-id=<ID of Form-UI page to open at start>

2.9.SP1 Update 3
Form-UI

If there is an entry in the initialization file (ec.ini) to start EEC with the Form-UI perspective and directly display a Form-UI, this does not lead to an exception error at the first start due to lack of a workspace. Instead, EEC is started with the Engineering perspective.

2.9.SP1 Update 3
ECAD

The type of an EPLAN Electric P8 project can be switched without errors by calling a C# script. This requires the use of EPLAN Platform Version 2.9 SP1 Update 3.

2.9.SP1 Update 2
ECAD

Before copying and pasting ECAD components, a check for dependencies to other libraries is now performed. If there are only dependencies to visible libraries, the ECAD components are duplicated directly. If there are dependencies on libraries that are not visible, these are first imported and then the insertion process for the ECAD components is executed.

2.9.SP1 Update 2
Basis Arbeitsablauf

If the Content Assistant is started in a value field of a project, pressing the [Tab] key no longer quits the application, but exits the Content Assistant.

2.9.SP1 Update 2
Basis Arbeitsablauf

The UNC path to the EOX file as backend is displayed correctly in the title bar.

2.9.SP1 Update 2
Form-UI

The Form-UI editor supports comments features

In the Form UI Editor, selected lines can be marked individually as comments using Source > Toggle Comment. Conversely, comment lines can be returned to normal code lines. With Source > Add Block Comment several marked lines can be marked as block comments and with Source > Remove Block Comment they can be undone.

2.9.SP1 Update 2
Form-UI

The <open> tag supports links to secure internet connections

The ref attribute of the <open> tag permits secure connections, for example <open ref="https://www.eplan.help/de-de/Infoportal/Content/htm/portal_home.htm" >EPLAN Information Portal</open>.

2.9.SP1 Update 2
Form-UI

Formula language for numberRangeValidator attributes startValue and endValue

For the check of input values any formulas can be specified instead of fixed values for the attributes startValue and endValue. The evaluation of the formulas takes place when loading the Form-UI page.

Read more...

2.9.SP1 Update 2
Administration

If an error occurs with an SQL query, it is no longer necessary to manually append the database query to the EPLAN support request. The database request is automatically included in the EPLAN support request, only the contents of the results folder should still be added manually.

2.9.SP1 Update 1
Administration

When EEC and P8 are started together, the HTTP error 503 no longer occurs.

2.9.SP1 Update 1
Basic workflow

Navigation to object in Formula Inspector improved

In the Formula Inspector it is still possible to navigate to an object, even if the view or the editor has been switched in between.

2.9.SP1 Update 1
Form-UI Input fields of the combo type, whose contents are generated by generic methods, no longer cause the user interface to terminate. 2.9.SP1 Update 1
Pro Panel The device tag (DT) is completely transferred from EEC to Pro Panel again. 2.9.SP1 Update 1
Job Server Example HTML file for Job Server

The folder <Installation path>\install\htmlTemplates\JobMonitorTemplate provides the example HTML file JobMonitor.html. This HTML file is written in AngularJS. The page delivers a listing of all Jobs and contains the columns Status, Job Name, Job Definition and Worker. The table displays 20 jobs per page, a pagination is not supported. Navigation between the pages is provided. The data is polled cyclically.

2.9.SP1
Basic workflow Search and replace in selection formulas

When searching for a particular expression in formulas, selection formulas are also considered. This provides the option of searching for an expression in selection formulas as well and to replace it therein by using Search/Replace....

2.9.SP1
Basic workflow Searching for formulas finds disabler- and selection formulas of placeholders and extension points

The search for certain expressions in formulas additionally provides the disabler and selection formulas of placeholders and extension points.

2.9.SP1
Basic workflow By selecting the Extension point option the Disabled input field is no longer switched to inactive, so that a disabler formula can be specified. 2.9.SP1
Basic workflow New search for failed formula results

The search is extended by Search failed formula results. The search for failed formula results can be further limited by means of the options Parameter, Disabler and Extension points. No deactivated project components are taken into account and no extension points are updated. The formula cache is activated during the calculation of the formulas. All faulty formulas are listed as search results. The list of search results for formulas with errors has been extended by the column Original error message.

Read more...

2.9.SP1
Basic workflow Formula inspector lists times with units

In the formula inspector, both the execution times and the computation times are specified with units (ms/s/min/h/d).

2.9.SP1
Basic workflow Expanding the error path in the formula inspector

When searching for an error in a formula, the error path can be expanded in the formula inspector.

Read more...

2.9.SP1
Administration New preference for the maximum depth of expandable levels for formulas in the formula inspector

In the preferences under Formulas > Formula Inspector, it is possible to specify an integer value for Maximum depth of expandable levels for a formula in the Formula Inspector. The specified value is used both for expanding the entire formula and for expanding the error path.

Read more...

2.9.SP1
Job Server Pre-defined job names in Jobs list

By means of the defaultJobName parameter within the POST Request a job name is sent in advance. As long als the job is queued, it can be identified in the list of jobs by this name. After commissioning the job it is checked whether the name can last or has to be replaced by a job name which is probably generated by a formula.

2.9.SP1
Basic workflow Alphabetical order in Create new library object dialog

The Create new library object dialog now contains all objects in alphabetical order.

2.9.SP1
Pro Panel

Parts with locked areas don't lead to error messages anymore while generating Pro Panel data.

2.9.1
Job Server Error logging for Job Server improved

Errors which occur while moving generated data are now logged in detail.

2.9.1
Job Server

Different upper/lower case writing of the file extension does no longer lead to an error message while importing CSV files.

2.9.1
Administration

The logging is no longer interrupted if the preferences for logging are opened.

2.9.1
Administration Java VM runtime option -clean removed from initialization file

The entry for the Java runtime option -clean no longer exists in the standard initialization file (ec.ini).

The option can still be used normally.

2.9.1
Basic workflow Formula inspector throws error message for recursion

If the formula inspector detects a recursion within a formula, an error message is thrown.

2.9.0
Administration License package for 4 Job Server Worker each

Job Server Workers are offered in packages of 4 licenses. This allows the number of available Job Server Workers to be increased by 4 additional instances. A maximum of 40 Job Server Workers can be managed by one Job Server.

2.9.0
Administration Java VM switched to OpenJDK

The whole application was migrated to use the Java VM implementation of OpenJDK.

2.9.0
Administration Installation of EEC variants changed

For the installation of EEC variants it is no longer necessary to unpack certain plugins and copy them into the /dropins folder. Instead, after the stand-alone installation you have to install optional features via Help > Install New Software....

Read more...

2.9.0
Administration Installation of optional feature Remote API Feature separately possible

The optional Remote API Feature function no longer has references to other plug-ins. This means that this option can now be installed independently of other optional functions. In addition, a separate port can be agreed for this function so that simultaneous use of the Web EEC installation variant is possible.

2.9.0
Administration Listing of all installed third-party libraries

The Info dialog now also lists all installed third-party libraries.

2.9.0
Basic workflow Changed context menu for creating a new object

To speed up the creation of a new engineering object, the New context menu in a mechatronic library has been changed. The change gives the modular system developer faster access to the engineering objects MechatronicComponent, DisciplineComponent, Unit, Parameter, Interface, Placeholder, SelectionAction, SequenceSelectionAction, and Category.

2.9.0
Basic workflow Dialog prevents data loss when closing EEC or changing the back end

If a write-protected EOX file is specified as back end, the changes made up to that point are not saved when EEC is closed or the back end is changed. In order not to lose the changes, the model must first be exported to a (new) EOX file. In order to inform the user of the possible loss of data when closing EEC or changing the back end, a dialog is now available.

2.9.0
Basic workflow Changed wizard for exporting EOX files

The wizard for importing EOX files is now more logical and easier to understand.

Read more...

2.9.0
Basic workflow Changed wizard for importing EOX files

The wizard for importing EOX files is now more logical and easier to understand.

Read more...

2.9.0
Basic workflow Fixed: Once the resource has been internalized, it cannot be reassigned to a disciplinary component

If the resource of a discipline component is internalized, another (changed) resource can only be reassigned if the existing resource was previously externalized. Only external resources can be synchronized.

Read more...

2.9.0
Form-UI Only MS Internet Explorer is still supported for the display of web pages

Since in Form-UIs with the tag <browser> only the browser MS Internet Explorer is supported, the attribute type is omitted.

Read more...

2.9.0
Job Server New license model for Job Server/Job Server Worker

With the introduction of a new license model for Job Server/Job Server Worker, the number of existing and in use Worker licenses is displayed in the List of Workers of the Job Server Monitor.

2.9.0
Job Server Parallel start of several Job Server Workers

With the help of a batch file, several Job Server Workers can be started in parallel. Each Job Server Worker uses its own web service for communication with EPLAN Electric P8 to generate schematics.

2.9.0
Job Server Parallel use of one Job Server

Several users can use the same Job Server in parallel to simultaneously generate schematics with EPLAN Electric P8.

2.9.0
Job Server Parallel use of several Job Server Workers

Several Job Server Workers can be operated on one Job Server, who generate schematics in parallel with EPLAN Electric P8.

2.9.0
Job Server Filter for "Status" column in Job Server monitor

The list of jobs can be filtered for the following categories in the Status column:

  • Show all jobs
  • Show queued jobs
  • Show running jobs
  • Show finished jobs
  • Show jobs with error

Read more...

2.9.0
Job Server Filter options for columns in Job Server Monitor

The new job table display now offers the possibility to enter a filter term for the Job Name, Job Definition and Worker columns. The list of jobs is then restricted to those jobs that correspond to the filter characteristics entered.

Read more...

2.9.0
Job Server Time filter for Job Server Monitor removed

With the new table view of jobs, the filter criteria Today's jobs and All jobs are omitted.

Read more...

2.9.0
Job Server Job Server Monitor with new table view

As of version 2.9, the list of jobs is displayed in a new table view. The jobs are also listed with a number, their current status, the job name, the job definition, the executing worker and possible actions.

Read more...

2.9.0
Job Server Deletion of Job Server log entries is adjustable

The EEC runtime option de.eplan.eec.jobserver.cleanup.days can be used to define the number of days after which log entries are deleted. Possible values range from 1 to 99 days. If this runtime option is not specified, log entries are removed after 30 days.

Read more...

2.9.0
Job Server The Job Server removes the file trigger file of a deleted job

Deleting a file trigger job from the list of jobs also deletes the trigger file.

2.9.0
PLC/CoDeSys Calls of methods without parameters are allowed

For method calls, it is no longer necessary to pass input/output variables as parameters.

2.9.0
PLC/CoDeSys Editor page PLC methods of POU-Editor lists contained methods

The editor for POUs now contains the new editor page PLC Methods. The new editor page lists all methods contained in the POU.

2.9.0
PLC/CoDeSys Synchronizing actions and methods creates contained parameters

If the result contains new actions or methods when synchronizing CoDeSys components, these and their parameters are created.

2.9.0
PLC/CoDeSys Methods support code insertion

Code snippets can be inserted into the code of methods using the plug socket strategy and control structures. The variables are synchronized automatically.

2.9.0
PLC/CoDeSys Implementing methods in programs (PRG) and function blocks (FB)

Discipline components of type Method can be implemented both in programs and in function blocks.

2.9.0
PLC/CoDeSys Discipline components of type Method support replace parameters

Replace parameters can also be used in discipline components of type method.

2.9.0
PLC/CoDeSys Method components are created for the methods contained in POU

For each method contained in a POU, a corresponding disciplinary component of type Method is automatically created when the POU is imported.

2.9.0
PLC/CoDeSys System library CoDeSys extended by 'Method'

The system library CoDeSys has been extended by the Engineering Object Method. The extension of the system library requires a model update. The update is performed automatically when the model is opened with the new version. After the model update, the model can no longer be edited with an earlier version of EEC.

Read more...

2.9.0
Pro Panel Menu structure for new discipline components changed

New disciplinary components for Pro Panel are now created via New > ECAD > ECAD3D instead of via New > ECAD3D.

2.9.0
ECAD Preferences for discipline ECAD extended by info on communication server

If the optional function P8 Integration Service Feature is installed, information on the status of the communication server for the connection between EEC and P8 appears in the user settings under Disciplines > ECAD > EPLAN Electric P8.

2.9.0
Administration Removed dependencies from plugin com.mind8.remote.api to other plugins

By removing the dependencies of the plugin com.mind8.remote.api to other plugins, it is now possible to use the com.mind8.remote.api feature independently of the Web EEC service.

2.9.0
Administration Initialization file contains only absolutely necessary entries

The initialization file (ec.ini) no longer contains any entries that are necessary for the standard execution of EEC, for example -Dde.eplan.eec.headless=false.

2.9.0
Administration Initialization file contains examples for using EOX files as comments

By default, the initialization file (ec.ini) contains examples for using EOX files for data storage as comments. In this way, the initialization file can be converted to a different type of data storage without having to look at the documentation.

2.9.0
Administration Show the current back-end in title

y default, the title bar of the EEC window displays the access mode followed by the absolute path to the back-end file. The display is controlled by the Show used back-end in window title preference option.

Read more...

2.9.0
Administration Resource folders of disciplines are created whilst installation

During the installation procedure the default resource folders for each discipline are created.

ECAD = <EEC installation folder>\resources\ECAD

Data sources = <EEC installation folder>\resources\DataSources

Media sources = <EEC installation folder>\resources\MediaSources

Office Word = <EEC installation folder>\resources\Office\Word

PLC-AutomationWorX = <EEC installation folder>\resources\PLC

PLC-CoDeSys = <EEC installation folder>\resources\PLC

PLC-Step7 = <EEC installation folder>\resources\PLC

2.9.0
Administration Preferences for resource folders of the disciplines are displayed as absolute paths

The resource folders of the disciplines are adjusted in the preferences. Underneath the input field the absolute path to the resource folder is displayed.

2.9.0
Administration Runtime option org.foederal.sn.connectionURL allows relative path specification to EOX file

In the initialization file (ec.ini) it is now possible to specify a relative path to an EOX file for the runtime option org.foederal.sn.connectionURL.

2.9.0
Formula language The method ifError(Block block), applied to NULL does not generate an error

If the result of a formula is to be checked with .ifError('...'), no error message is generated if the result is NULL.

Example:

Formula Result
=List{null,1,2}.first.ifError('An error occurred!') <<null>>

Read more...

2.9.0
Formula language New method for determining the next-larger integer of a double value

The method ceil() can be used to determine the next-larger integer of a double value.

Read more...

2.9.0
Formula language New method for determining the smallest value from a collection

You can use the min() method to determine the smallest value from a collection.

Read more...

2.9.0
Formula language New method for determining the largest value from a collection

You can use the max() method to determine the largest value from a collection.

Read more...

2.9.0
Formula language In formulas, you can access the name of the parameter in which the formula is contained

The parameter.name method can now be used to access the name of the parameter containing the formula within a formula.

Read more...

2.9.0
Formula language Navigation methods for discipline components without discipline structure do not throw error message

Formulas, which should navigate over a discipline structure, which actually does not exist, will no longer produce error logs. In these cases instead of the determined parameter value still a message is displayed in front of a yellowish background color.

Read more...

2.9.0
Formula language Fixed: The methods first() and last() react in the same way

The first() and last() methods now both return <<null>> for empty lists.

2.9.0
Formula language No error message for formulas that can only be calculated in the discipline structure

Formulas that perform calculations on the discipline structure no longer lead to an error message. Instead, a note text is displayed in the result field.

2.9.0
Formula language Formula result of extension point

As of version 2.9.0, you can use the Formula Inspector to examine the formula result of enhancement points. The Formula Inspector is called from the context menu of the input field.

2.9.0
ECAD Navigating from P8 macro to corresponding discipline component in EEC

By means of a P8 action you can move from a marked macro within a generated schematic to the corresponding disciplin component in EEC.

2.9.0
PLC/CoDeSys CoDeSys V2 is no longer supported

EEC no longer supports the generation of PLC code for CoDeSys V2.

2.9.0
OFFICE System library contains UpdateWordFieldsCommand

The Command UpdateWordFieldsCommand is included in the WORD system library as of version 2.9. To use the command, it is no longer necessary to import the file <EEC installation folder>/install/Tutorial/Word/Word_Ui.EOX.

Read more...

2.9.0
Job Server The private alias URL should always be used for communication between the Job Server and the Job Server Worker

To set up the communication between Job Server and Job Server Worker, only the runtime option de.eplan.eec.jobserver.private.aliasurl has to be specified in the initialization file.

Read more...

2.8.3
Pro Panel Rotation of 3D macros around x-, y- and z-axis

When placing 3D macros of the EnclosurePart, MountingPanel and Device types, rotation around the x-, y- and z-axis is supported.

2.8.3
Pro Panel Automated 3D assembly setup considers the orientation to the mounting point

When creating a 3D assembly setup, the orientation of an article or 3D macro to the mounting point is identical to manual placement.

2.8.3
Job Server Fixed: Job list for Today´s Jobs now only shows jobs of the same day

If the job list in the browser is open for longer than one day and the filter is set to Today´s jobs, it is no longer necessary to update the browser content (e.g. by [F5]).

2.8.2
Pro Panel Rotation of parts around the x-, y- and z-axis

When placing parts of the EnclosurePart, MountingPanel and Device types, rotation around the x-, y- and z-axis is supported.

2.8.2
ECAD Fixed: P8 macros may have file names with a length < 3 characters

EEC also accepts P8 macros with very short file names (length< 3 characters) while creating schematics.

2.8.2
Basic workflow Fixed: Paste any content from the clipboard

When pasting contents from the clipboard, only allowed contents are accepted and not allowed contents are ignored.

2.8.2
Basic workflow Fixed: Export of model data for support request

For a support request, the selected data is exported even if a support request of the same name already exists. This ensures that the data stored in the workspace directory is not exported if it is stored below the global resource folder.

Read more...

2.8.2
Documentation Fixed: Passing parameters to line-up devices with mounting parts

To line-up devices with mounting parts the list of parameters has the following syntax: =List{'M4','M2',<dx>}.

2.8.1
PLC/CoDeSys Variables declarations with comment are overtaken

Variables declarations with comments in the same line are completely copied into the code of the inserting component. This also applies to block comments that begin in the same line of the variable declaration.

Read more...

2.8.1
Job Server Improved message, if preferences for a running Worker are changed

The preferences for a worker cannot be changed during operation. All running jobs must first be completed and the worker stopped. An improved message now informs the user of these conditions.

2.8.1
Web EEC Fixed: Session models are stored in the predefined folder

The EOX files generated during a Web EEC session are stored in a specified folder. The folder for storing the session models is specified in the initialization file (e.g. ec.ini) by the following entry:

-Dcom.mind8.remote.server.repository.file=<absolute path to session models folder>.

Read more...

2.8.1
Tutorial Parts data for Pro Panel tutorial are available as MDB or EDZ files

The Pro Panel tutorial uses parts data that may not be available in the user's parts database. In order to be able to compile the tutorial nevertheless, both the exchange of the (MDB) parts database and the import of EDZ files are described. The required files are provided in the folder /install/Tutorial/ProPanel.

2.8.1
Administration New license management

As of Version 2.8.0 a new license management is used. This means that in addition to the EEC installation a new license client is installed as well. There is no need for the user to act.

2.8.0
Documentation New EPLAN Information Portal

As of Version 2.8 of the EPLAN platform, we are providing the new EPLAN Information Portal on the Internet that has all the technical information on all EPLAN products. The web-based full text search positioned in the upper area of the Portal page allows you to specifically search information and find it quickly. During the search all EPLAN help systems as well as stored technical publications are considered.

You can reach the EPLAN Information Portal in the following ways:

2.8.0
Administration Fixed: Correct application of the "PartsFromSystemToProject" argument for the Java VM.

The PartsFromSystemToProject argument for the Java VM is only applied if it is entered in the initialization file (for example ec.ini). If the argument is not entered in the initialization file, no synchronization is performed with the parts database during the parts placement.

2.8.0
Administration Name of the installation file shows a three-digit version number.

The file name of the installation file has now been extended by the third position of the version identification. This way setup_EEC_2_8_20181101-0905.exe becomes the new name setup_EEC_2_8_0_20181101-0905.exe.

2.8.0
Administration Only 64-bit installation variants are possible

All installation variants of the EEC are only performed as 64-bit applications. The variants of the 32-64-bit hybrid installations are no longer required.

2.8.0
Administration EEC requires Java Runtime Environment of Version 8

As of Version 2.8 EEC requires the Java Runtime Environment (JRE) in Version 8. The current JRE installation file is part of all installation variants.

2.8.0
Administration Model variables standardized

The names of the model variables have been standardized in a way that makes it immediately clear whether a value or the name of a parameter has to be entered or selected for the model variable. The descriptions have been standardized or corrected accordingly. A description is now available in the help for all model variables only.

2.8.0
Administration The option “Enable inspection of non-evaluated conditional branches" in the formula inspector is not active by default.

The Enable inspection of non-evaluated conditional branches in the formula inspector option is now no longer activated by default in the user specifications. If non-evaluated conditional branches are to be calculated, the option must be consciously activated.

2.8.0
Administration Changed maximum values for memories of the VM in the initialization file.

The entries in the initialization file (for example ec.ini) for the maximum memory value of the VM have been increased to the following values:

  • For Stand-Alone and Worker installation: -Xmx1536m
  • For Job Server installation: -Xmx1792m
2.8.0
PLC/CoDeSys CoDeSys V2 is no longer supported as of Version 2.9

As of Version 2.9 EEC no longer supports the generation of PLC code for CoDeSys V2.

2.8.0
Job Server Job Server 2.8 is no longer compatible with Job Server 2.7.

After updating to Job Server of the Version 2.8, the Job Server files cannot be used with the Job Server Version 2.7 anymore.

2.8.0
Basic workflow Support request with larger entry field

The entry of a problem description has now been significantly improved with a larger entry field.

2.8.0
Basic workflow Enriching support request with own plugins

All plugins that are located in the <EEC-Installation folder>/dropins folder can now be attached to a support request as well. To do this, the new option has to be marked after launching the assistant for an EPLAN Support request. The files are added with the ZIP file after finishing the wizard with [Finish].

2.8.0
Basic workflow Enriching support request with resources

The required resource files can now be attached for a support request. To do this, the new Add resources option has to be marked after launching the wizard for an EPLAN Support request. The files are added with the ZIP file after finishing the wizard with [Finish].

2.8.0
Basic workflow Creation of support request made simpler

To create a support request you can now use the new Create EPLAN support request... menu item in the Help menu. This starts the same assistant as in the past to formulate the support request and enrich it with data.

2.8.0
Basic workflow Changed category for support request in expert dialog

Instead of Other/Quality Feedback Report, the assistant for the export of a support request is now started under EPLAN Support/EPLAN Support request in the Export dialog.

2.8.0
Basic workflow Formula inspector indicates error source if calculation of rmos() fails.

Through an improved error handing the formula inspector can now show the error source, if the calculation of a formula fails that uses rmos() to determine all components (of a certain type) below the root node.

2.8.0
Basic workflow Fixed: EEC crashes by clicking the header of the model variable table

In the model variable view the clicking of the header of the model variable table does not lead to an exception error and with that a crash of the application anymore.

2.8.0
Job Server Simultaneous operation of four EPLAN instances on one computer

Four EPLAN instances for generating schematics or 3D graphics can be used on one computer with one Job Server and four Workers. One license is required per EPLAN instance.

Read more...

2.8.0
Job Server Description of the installation variants extended

The installation variants Job Server with Worker and Worker are now documented in separate sections.

Read more...

2.8.0
ECAD Fixed: Representation type macro of window macro causes error

EEC as of Version 2.8 supports all representation types of window macros:

  • MultiLine(1)
  • SingleLine(2)
  • PairCrossReference(3)
  • Overview(4)
  • Graphics(5)
  • Panel layout(6)
  • P&I diagram(7)
  • MultiLine_Fluid(8)
  • Topology(9)
  • Functional(11)
  • Pre-planning(12)
  • FunctionOverview_fluid_power(13);
2.8.0
ECAD Fixed: Plug-Socket error while simultaneously generating schematic with 2 P8 instances

Plug-Socket errors do not occur anymore when EEC initiates two P8 instances on a machine at the same time to generate schematics.

2.8.0
ECAD Fixed: EEC starts and stops P8 immediately before the shutdown

If an EEC is terminated immediately after the execution of the command this does not lead to another start and finish of EPLAN Electric P8 anymore.

2.8.0
ECAD Error while C# scripts are being executed are reported by EEC

After a schematic has been generated, a C# script can be executed in P8. If an error occurs in the process, this can also be reported to the EEC and logged.

2.8.0
Job Server Database updated

The database required to operate the Job Server has been updated. There is no need for the user to act.

2.8.0
Job Server Updating of Job Server and Worker required

The modified concept for the Worker registration requires that both the Job Server and the Worker have to be updated to Version 2.8. Mixed operation of different versions is not possible.

2.8.0
Job Server Workers connect automatically after failure of the Job Server

If Job Server temporarily fails during operation or cannot be reached anymore, the active Worker can immediately log on the Job Server as soon as it can be reached again. The execution of existing Jobs is not influenced by this.

2.8.0
Job Server Button for adding a Worker removed

Through the mandatory specification of de.eplan.jobserver.private.aliasurl in the initialization file of each Worker this is registered automatically at the Job Server. This means that the button for adding a Worker is no longer required.

2.8.0
Job Server Initialization file of the Worker must contain specification for de.eplan.jobserver.private.aliasurl

It is now mandatory that the initialization file set the value for the argument of the Java VM de.eplan.jobserver.private.aliasurl.

This entry is required so that the Worker can sample the Job Server actively for pending Jobs.

2.8.0
Pro Panel Fixed: Error when placing devices on a busbar system

Any devices can be placed on a busbar system.

2.8.0
Administration Plugin entries removed from initialization file

The initialization file no longer requires the following entries:

-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_64_1.1.200.v20120913-144807
-product
de.eplan.engineeringcenter.product

These entries are no longer part of the default initialization file (ec.ini).

2.8.0
Job Server Log tells file locked by another process

If access to a file is blocked during job processing, a log entry is created. The log entry contains both the name of the locked file and the name of the process that prevented access.

2.8.0
Job Server Error during restart of Worker is logged

If a Worker is able to log on to the Job Server after the restart but is not able to perform the pending Job, this is now logged into a log file.

2.8.0
Basic workflow The Parameter editor page of Pro Panel components offers all functions

The functions Categories, Add interface parameters and automatic column width setting are now also available for the editor page Parameter of Pro Panel components.

2.8.0
Basic workflow Behavior during deletion of configuration is improved

Since storage procedures have an effect on an existing configuration, a deletion procedure for a configuration always has to wait for the completion of the storing procedure.

2.8.0
Documentation Release Notes can be filtered

The Release Notes can be filtered as of Version 2.8. Filter values can be selected from a dropdown list for the range and the validity. In the "Feature" column the content can be filtered for any term. The filters of all the columns are combined (AND operation). Columns for which a filter is set are identified by a red background color in the header.

All the filters can be reset together by using the icon.

2.7.4
Documentation Required specification of a license default setting file for operation without a user interface

For operation without user interface, for example as a Windows service, the specification of a license default setting file is mandatory. This specification is entered as a VM argument in the initialization file.

Read more...

2.7.4
Basic workflow Fixed: Logging does not result in a standstill of a Worker while actions are being executed

The logging function can emit a message itself during logging without this resulting in a standstill of a Worker.

2.7.4
Pro Panel Fixed: Complete DTs transferred to Pro Panel

When the Pro Panel data is generated, the complete DTs are also transferred for mounting panels, enclosure parts and subordinate parts of busbar systems (for example holders).

2.7.4
Pro Panel Only devices are placed on a busbar system

Only permissible devices are still placed on a busbar system. The placement of components of a different type on a busbar system results in an error message during the generation of the discipline structure.

Read more...

2.7.4
Pro Panel Fixed: Placement of a mounting panel with specification of the macro possible

A mounting panel can be placed both with specification of the part numbers and with specification of the 3D macro.

2.7.4
Licensing The MCAD Inventor module is no longer part of the EEC as of Version 2.7.3

As of Version 2.7.3 the MCAD Inventor discipline is no longer available.

2.7.3
Pro Panel Fixed: Placement of a 3D macro only possible without rotation

A part that is referenced as a 3D macro can now be rotated simultaneously during placement.

2.7.3
Job Server Fixed: Error message when host name was not found

If the host name for a connection cannot be resolved, only a helpful error message is output.

2.7.3
ECAD Fixed: Despite an error during the creation of a schematic a C# script is executed

If an error occurs during the generation of a schematic, this normally leads to the cancellation of the process and an error is written into the log file. To find all errors and have a C# script executed during the generation of a schematic, the cancellation can be prevented with the Continue P8 creation in case of an error preference.

Read more...

2.7.3
Organization of models Fixed: Filter in Imported libraries view also filters the connection lines

If the filter Hiding all assemblies which were not directly imported is activated, both the indirectly imported assemblies as well as their connection lines are hidden.

2.7.3
Documentation Pro Panel Tutorial with change of parts database instead of EDZ import

The Pro Panel Tutorial requires parts data that are not necessarily available in the installed EPLAN version. These parts data are provided in a parts database. In the preparatory steps the system now switches to this parts database, instead of importing the missing parts as EDZ files.

Read more...

2.7.3
Documentation Behavior of directory settings for ResourcePath and disciplines

The paths to the resources of the individual disciplines can be indicated as absolute paths or they are compiled from two components:

  1. Runtime option for the resource path.
  2. Preferences for the respective discipline.

The descriptions of the preferences are enriched with examples for every single discipline, which illustrate the behavior.

Read more...

2.7.3
Basic workflow Accelerated importing of project modifications

The import of project modifications (PX files) has been optimized. The optimization has an effect both on the selection of the project modifications to be imported and on the importing of the project modifications.

2.7.3
Basic workflow Fixed: After undocking from the library or project catalog the navigation targets are not available anymore

After undocking from the library and project catalog you can once again select the Show in... menu item in the popup menu.

2.7.2
Job Server Fixed: Status display of Worker contains errors

Instead of displaying the state of a process, the status of the Worker is now displayed correctly.

2.7.2
Basic workflow Renaming level components is not allowed

Level components that allow themselves as subordinate components may not be renamed or used as soon as they are installed library components. In this case the entry field for the name has a red background.

2.7.2
Form-UI Fixed: Documentation of <label> adapted to actual possibilities

In Form UIs not all documented attributes and their combinations could be used anymore. The documentation now only describes the attributes actually possible and their components.

Read more...

2.7.2
Documentation Pro Panel Tutorial extended with EDZ Import

The Pro Panel Tutorial requires parts data that are not necessarily available in the installed EPLAN version. These parts data are provided as EDZ files and imported into the parts database in advance.

Read more...

2.7.2
Pro Panel Rotating parts around every axis

The placement of a part on a mounting surface can now be determined with additional parameters on the Y- and Z-axis. The placement is either defined with a Type Mate parameter or MateMap.

Read more...

2.7.2
Basic workflow Fixed: Version identification for PX update

Because of an error the names for the PX updates had to begin with a number instead of the letter V. Now the behavior follows the rules as before.

Read more...

2.7.2
Web EEC Fixed: Web EEC generates incorrect URLs for file download

The URLs for the download of generated files now does not include invalid characters anymore.

2.7.2
Web EEC List of the Apache Tomcat Server versions

A list of the recommended Apache Tomcat Server is provided in the installation chapter. The IT requirements are expanded by a list of currently required Apache Tomcat Server versions.

Read more...

2.7.2
ECAD Note on the update of the project template when the P8 version changes

If the user switches to another P8 version a note on the update of the project template is displayed. The user always has to provide the project template corresponding to the currently used P8 version.

2.7.2
ECAD Generation of non-visible parameters in macros

If parameter values are required in macros, for example for calculations, the parameter name at the beginning must be expanded by "hidden_" (for example hidden_Order).

Read more...

2.7.1
ECAD Deleting placeholders after generation

The user preferences now include the option Delete placeholders after generation. If this option is selected, all placeholders that include ECC parameters in the generated schematics are removed. To do this the placeholder must include at least one parameter, even if this is a non-visible parameter.

Read more...

2.7.1
ECAD Error messages if user preferences for P8 are not correct

If user preferences for P8 are not set correctly, this is displayed by messages that include a note on troubleshooting.

2.7.1
Documentation Copy URL to Clipboard

The URL of the help topic can be copied simply to the Clipboard with the button interface that can be found in the help toolbar next to the language switching function. To this purpose the URL is shortened to the part actually required.

2.7.1
ECAD Fixed: Line break between "mounting location" and "device tag" shows quotation marks instead of a line break

Inserting a line break between the mounting location and device tag in the Displayed DT field (for example +EC¶-X1865XB) does not show any quotation marks in the results of the test run anymore.

2.7.1
ECAD Fixed: Opening of a macro preview with an invalid path to the macro throws an exception error

If the path of an ECAD macro is not valid anymore, an error message instead of a macro preview is shown and the path to the resource is displayed with a yellow background to mark it as invalid.

2.7.1
ECAD Fixed: No warning is to be shown at pages without a plug parameter if only a WiringDiagram exists

If the ECAD structure only includes a component of the WiringDiagram type, it is not necessary to provide the pages with plug parameters since they cannot be installed anywhere else in the schematic. This application case does not result in a warning message anymore while the schematic is being generated.

2.7.1
Job Server Fixed: Exception error appears during the Worker start, after the restore folder has been renamed

Renaming or deleting of the folder for restore files does not lead to an exception error anymore. This can happen either during the operation of the Worker as well as at the stopped Worker.

2.7.1
Office Fixed: Blanks are missing in generated Word documents

Blanks which are included in parameter values are no longer lost in the generated Word documents.

2.7.1
GRAPH2D Fixed: Review during the removal of the GRAPH2D library is impossible

If a project already includes an instance of a GRAPH2D discipline component, it is not possible anymore to remove the GRAPH2D library from the modular system. This prevents assemblies from becoming invalid.

2.7.1
Job Server Fixed: Numbering of Jobs in the interface of the Jobs

The numbering of Jobs now always starts with 1 and runs without any gaps to the highest number. This behavior is always the same, regardless of whether a filter is set or which filter is set.

2.7
PX update Method deleteInstance with five arguments

The deleteInstance method for PX updates has been expanded by the additional argument deleteAllInstances. If the Boolean argument is set to true, all project components of a given name are deleted. If the argument is set to false, only the specified project components are deleted.

2.7
Administration As of version 2.8 ECC will not be available anymore as a 32-bit application

As of version 2.8 only the installation of 64-bit applications is supported. The installation of a 32-bit application through the 32-/64-bit hybrid version is no longer supported.

2.7
Administration Starting the ECC via the command line is no longer supported

Starting the ECC via the command line is no longer supported. The arguments for the Eclipse and the Java VM are only passed by the initialization file, for example ec.ini.

2.7
Job Server Show log for Job separately

The Job Server includes a new symbol that includes a link to a Job-specific record page. Therefore the previous record page only includes general information. This is in contrast to the Job-specific record page which only includes information on specific Jobs.

2.7
Pro Panel Support of drilling patterns

EEC now supports the placement of drilling patterns. The placement of drilling patterns is specified by a Coordinate parameter of the List type and additional information by a parameter of the SupplementaryMap type.

Read more...

2.7
Pro Panel Parameters for drilling pattern variants

Pro Panel parts can include drilling pattern variants, which are identifiable by their name. To state the variant a parameter of the DrillingPatternVariant needs to be created. A discipline component which includes a part with drilling pattern variants also has to include this parameter. The value of the parameter specifies the name of the drilling pattern variant.

Read more...

2.7
Pro Panel Model variable for angle

The placement of Pro Panel components can be specified with angles in the units degrees or radians. The unit is specified with the model variable Unit for angle. The new model variable is located in the new path Disciplines > ECAD > EPLAN Pro Panel. The unit is selected via a Dropdown list.

2.7
Documentation Switching the language of the help

Switching the language is now facilitated by a dropdown list in the help toolbar.

2.7
Documentation Restricting the search results to one area

Search results are limited to a certain area by clicking Search in... on the right-hand side of the search field. This opens the dropdown list with available areas to reduce the search results.

2.7
Documentation Help on the installation of EEC only still online

For the installation of EEC a Help system can be called up. This can be accessed as part of the complete Help online.

Read more...

2.7
Documentation EEC-Help still only online

As of Version 2.7 the Help for EEC is only still accessible online. The Help is available under the URL http://www.eplan.help/2.7/en-US/EPLAN_help.htm.

2.7
Administration Configuration of existing DatabaseDataSource in initialization file

Existing DatabaseDataSource configurations can be overwritten through entries in the initialization file.

Read more...

2.6.3
Documentation Fixed: Spelling errors in the values of the model variable "Name of the parameter for the I/O assignment"

The correct values for the 'correct values' model variable for the model variable Name of the parameter for the I/O assignment are free, IO combined and IO separate.

2.6.3
Administration Discontinuation: Command line parameters are no longer supported as of version 2.7

With version 2.7 command line parameters are no longer supported.

2.6.2
Web EEC Fixed: Web EEC is not terminated

After an EEC Server has been terminated, no background process remains. This means that an error message due to an occupied port is no longer generated after a restart.

2.6.2
Web EEC Fixed: Closing of a tab results in an error in all other open tabs

If the same Web EEC page was opened in several tabs of a browser and the first tab was closed, several error messages were shown. This behavior could be traced back to an old version of RAP as target. Since RAP 2.3 used by Web EEC, tabs can be closed without error messages.

2.6.1
Administration Fixed: Parameter data shall be supported in the command line call of the ec.exe

If ec.exe is started via a command line call, the parameter -data can be used to transfer the specification of the workspace folder.

2.6.1
SAP interface Fixed: SAP plugins are not compatible

The plugins of the SAP interfaces are up-to-date to suit version 2.6.

2.6.1
Form-UI Fixed: Form-UI-Dialog yes/no is not translated

The [Yes] and [No] buttons of Form-UI dialogs are always displayed in German. By switching the language to en-US, the texts of the buttons are also shown in English.

2.6.1
Job Server Fixed: Automatic registration of Workers does not function

The automatic registration of Worker at a Job Server functions again.

2.6.1
Job Server Fixed: Jobs and records that are older than 30 days are not deleted

Jobs and records are removed after 30 days.

2.6.1
ECAD Fixed: Value of "Macro folder" model variables is not transferred to P8

The Macro Folder model variable is now transferred to P8. A new version of P8 is also required.

2.6.1
ECAD Fixed: No automatic restart after change of user preferences

If user preferences that require a restart of EEC are changed, this is automatically carried out.

2.6.1
ECAD Fixed: P8 is automatically restarted if the connection is lost

It can happen that the connection to P8 is lost. In this case EEC tries to start P8 again.

2.6.1
ECAD Fixed: EEC does not close all P8 instances when EEC is terminated

If EEC is terminated, all P8 instances that were started by this EEC instance are now closed again.

2.6.1
ECAD Model variables for the generation of EDZ files adapted

Only those model variables that are necessary for the EDZ generation should be displayed in the table of the model variables. Therefore the model variables EEC_RES and EEC_MASTERDATA have been removed.

2.6.1
ECAD/Pro Panel Continuing generation of ECAD/ECAD3D in case of an error

In case errors appear during the generation of P8 schematics or Pro Panel, these are recorded and generation is continued. In case of an error P8 or Pro Panel are not opened. If the generation of P8 schematics or Pro Panel was called by a Job Server, in case of an error the Job is marked with "failed".

2.6.1
Basic workflow Fixed: Search and replace cannot change formulas in parameter objects

Formulas that are saved in parameters, are now also taken into consideration for Search And Replace.

2.6
Documentation Fixed: Names of handles for enclosures have been changed since Pro Panel version 2.5

The standard names of handles for enclosures have changed. In the past the handles had the names CUB1, CUB2 etc. The new default names have been expanded by "C_" in the beginning, so that the names are now C_CUB1, C_CUB2, etc. All occurrences in the documentation have been changed accordingly.

2.6
Documentation Fixed: Comments of the model variables for P8 folders are incorrect

The comments for the P8 model variables Image_Folder and Macro_Folder result in incorrect specifications. The comments and the documentation for these model variables have been corrected.

2.6
Job Server Fixed: Displays an error message if Browser Scripting is not allowed

The LOB Server user interface is displayed by every browser. To this purpose scripting has to be allowed by the browser. If the browser rejects scripting, a corresponding error message is displayed.

2.6
ECAD Fixed: DT contains invalid characters

Device tags that contain a line feed do not generate an error message during the generation of the EPLAN Electric P8 schematics.

2.6
ECAD Fixed: Names of shields are not transferred

The names of shields are now transferred during the generation to EPLAN Electric P8.

2.6
Job Server Fixed: Job Servers / Workers sometimes show an incorrect status

The status display for Jobs has been improved so that incorrect states are no longer displayed.

2.6
Basic workflow Fixed: Parameter data are to be supported in the command line call of the initialization file (for example ec.exe)

A command line call for the ec.ini now supports the -data parameter to transfer the workspace folder. A corresponding entry in the initialization file (for example ec.ini) is overridden by the command line parameter.

Read more...

2.6
GRAPH2D Fixed: Error message during the deleting and renewed creation of a new GRAPH2D diagram

If a customer-specific sequenceSelectionAction is used to delete a GRAPH2D diagram and to create a new one with the same name in the same editor, this no longer returns an exception error message.

2.6
Job Server Fixed: Job Server does not delete files that are older than 30 days

Generated files that are older than 30 days are now deleted in accordance with the specification.

2.6
Basic workflow Fixed: Inconsistent model after objects have been deleted

Every action has to ensure that its result is consistent. When objects are deleted, a renewed validation checks that no references to the deleted objects exist. Otherwise the deleting process is aborted and an error message is displayed.

2.6
MCAD Documentation for MCAD

A documentation for the MCAD discipline is available.

2.6
Discipline During the generation of the discipline structure Sockets are favored against Names

In order to structure discipline components Sockets are now favored against the Names of the discipline components. If both the Socket as well as the Name of a discipline component are valid, the Socket is always used.

Note: In rare cases this can result in other discipline structures than before if both Sockets and Names come into question as possible higher-level components for placement.

2.6
Pro Panel Fixed: Components of the EnclosurePart and MountingRail types do not support placement in the direction of the Z-axis

Components of the EnclosurePart and MountingRail types can now also be placed in the direction of the Z-axis. In the past the value for the Z-axis was ignored.

2.6
Pro Panel Setting macro variants and part variants for a macro

Now both macro variants and part variants for a 3D graphical macro can also be set by means of a parameter for all the Pro Panel components.

2.6
Pro Panel Components of the CutOut type support the specification of an angle

An angle can now also be specified in the parameter of the Dimension type for cut-outs.

2.6
Pro Panel Fixed: The use of a 3D graphical macro for a mounting surface now generates an error message

In addition to the part for a component of the Plane type, a 3D graphical macro can also be used via the macroName parameter.

2.6
Administration ec.exe is now the 64-bit version

The new EEC installation routine supports 64-bit Windows systems and can no longer be executed in 32-bit Windows environments. The 64-bit version of EEC is now started with the ec.exe. Installation of a 32-bit version of EEC is made possible by the 32/64-bit hybrid version. In this case the 32-bit version is started with ec32.exe. Take into account that the folder for the configurations was renamed to /configuration for the 64-bit version or respectively /conf32 for the 32-bit version.

2.6
Job Server Calling of any class methods from the JMX Action Tag

Within a Job definition the <action> tag can point to a static class method with the following syntax:

<action name="<class name>:<static method name>" 
arguments="List{<argument1>, <argument2>}" />

Read more...

2.6
General Preparation for version 2.5

The help system has been changed to a HTML5 authoring system.

2.5
Job Server Scalable Job Server (multiple worker instances)

EEC as Job Server can be started with a Worker or only as a Worker. Multiple Workers can register at a Job Server to be able to edit multiple or different job definitions.

2.5
Job Server Job progress display and monitoring

A progress monitoring service and a web user interface is provided for every performed job of the Job Server.

2.5
Job Server File and WebService Triggers for Job definitions

Job definitions can define a File or WebService Trigger. File triggers monitor a central input folder. In contrast to this, WebService Triggers listen at a port and can be requested by other services or web applications.

2.5
Job Server Cleaning of job data

To minimize memory usage, the Job Server deletes job data (files, records, meta data) after a certain amount of time (by default 30 days).

2.5
Job Server Job Server web user interface

The Job Server user interface has been improved when it comes to scalability and user-friendliness. The user interface can now be reached both with any web browser as well as within the EEC. Filter options help reduce the long list of relevant entries.

2.5
Job Server Automatic registration of Workers

After the installation and the first start of the Job Server, the local Worker automatically registers with the Job Server. Workers can register themselves after the start automatically at the Job Server in order to reduce the administrative work. Additional Workers can also be registered manually.

2.5
Job Server Scalable use of the Job Server (separation of Job Server and Worker)

The installation routine has been changed. The Job Server is now always installed with a Worker, but a Worker can also be installed without Job Server.

2.5
Job Server Central record for Job Server

The user interface of Job Server through a central log now offers a central overview of the activities of the Job Server and the Worker. Log messages are grouped according to date (today, last 7 days and older) and sorted by time (newest on top). Log messages can have different severity levels. Additional filter options can restrict information, warnings, errors and any combination from the list.

2.5
Job Server Customer-specific results data can be added to a Job process

Additional information on Job monitoring, for example customer-specific results data such as texts, can be added with EEC Commands. Temporary results are displayed during the execution of the Job. This is helpful if customer-specific results are to be displayed as a final result during or at the end of the execution.

2.5
Documentation Improvements in the Pro Panel Tutorial

The Pro Panel Tutorial shows how formulas for the determination of device tags in the mechatronic structure avoid error messages.

The EEC preferences are adapted to a different project template file IEC_bas001.zw9.

The EOX file with the sample solution has been improved through the changes mentioned above.

2.5
Documentation How do you switch from FastObects data back end to EOX file?

The administration chapter describes how the data back end is switched from FastObjects to EOX file.

Read more...

2.5
Job Server Formulas determine values for arguments of actions

Formulas can be used for the values of arguments for actions. For example the name of a project component can be determined though the formula absRef('<absolute name of component>').name.

Read more...

2.4.5
Commands ForcefulEOXImportCommand added to Customizing_Engineering.eox

The new command ForcefulEOXImportCommand imports an EOX file and in the process overwrites all the components existing in the existing project. The command is made available with the EOX file Customizing_Engineering.EOX in the folder <Installation directory>\install\other\model. After the EOX file has been imported, the command is contained in the Customizing_Engineering library.

2.4.4
Pro Panel Placing devices not only on the surface of mounting panels but also on surfaces of the enclosure

Devices may be placed on all surfaces within the layout space. The configuration is not restricted to placements on mounting panels or enclosures anymore.

Read more...

2.4.4
Pro Panel Fixed: Placing mounting rail on the mounting panel

Mounting rails can be placed either by using coordinates on a component of the Plane type or via the mounting point on a component of the MountingPanel type.

2.4.4
Pro Panel Fixed: Pro Panel structure allows additional EnclosureParts directly below the layout space

Discipline components of the EnclosurePart type might be placed directly below discipline components of the LayoutSpace type.

2.4.4
Form-UI RAP/RCP display faults: Standard font size, cell height, cell height in pureTable

The cells of tables and the texts contained in them are no longer displayed in different sizes in Web EEC and Desktop EEC. If deviations nevertheless occur, the Form-UI can be adapted as follows:

  • In the <table> element specify fixed values for cellSpacing and cellPadding.

  • For <pureTable> in the <column> element specify fixed values for hSizeMinPx and hSizeMaxPx.

2.4.4
Form-UI Fixed: Clicking into an empty cell of a table of the pureTable type throws exception errors

Clicking empty cells in a table of the pureTable type does not cause exception errors anymore.

2.4.4
Job Server Fixed: Hidden/locked files in input folder let job fail

Hidden and locked files in the incoming folder of the Job Server are ignored and not processed. Locked files are for example DOCX files that are currently opened in Word. The file is processed as soon as locking is rescinded.

2.4.4
Job Server Mroot specified in IMX file

In IMX format the mroot attribute has been added to the <project> tag so that any name can be specified for the mechatronic root node.

Read more...

2.4.4
Job Server Importing parameter values via IMX file

By means of IMX files you can import several parameter values into a mechatronic object. The project or object into which the parameter values are imported do not have to be part of the IMX file and can be specified for the Command or the Action.

Read more...

2.4.4
PLC/CoDeSys Parameter for action components

During automatic creation of Action components the parameters existing in the Action code are created. If no value exists for the created parameters within the Action, the default value references the parameter of the superordinate component in the discipline structure. During the generation of the code the parameters of the Action itself are used and not, as in the past, the parameters of the superordinate component.

2.4.4
General New symbols

The following symbols have been added to the icon collection in the install/icon_collection folder: arrow_down.png, arrow_up.png, icon_delete.png, icon _ok.png, square_blue.png, square_brown.png, square_green.png, square_grey.png, square_lightblue.png, square_lightgreen.png, square_orange.png, square_purple.png, square_red.png

2.4.3
Commands Inserting appendixes with SendMailCommand

Emails which are sent via SendMailCommand, can now have any number of attachments.

2.4.3
ECAD Fixed: DT with line break does not work in version 2.4

Displayed device tags with line breaks no longer lead to errors in error checking of EPLAN Electric P8.

2.4.3
Form-UI Fixed: Font size in Web EEC is different to Desktop EEC

The assigned font size is processed in the same manner for Web EEC and Desktop EEC. It is recommended to always assign the font, style and size, to avoid different displaying.

2.4.3
Job Server Fixed: Memory overflow in message record when filtering

Activating the message record filter no longer leads to memory overflow.

2.4.3
Job Server Excel import wizard also accepts xlsm files

The file filter for importing Excel files is expanded by the *.xlsm file extension, to make it possible to import Excel files with macro functions.

2.4.3
Job Server CSV import via XML import adapter

By means of the ImportCSVCommand command the content of any csv file is imported to generate project content.

2.4.3
Job Server Specifying absolute and relative paths in IMX file via xi:include

Within an IMX file the <xi:include> tag is used to assign e.g., a mapping file as a relative or absolute URI.

Read more...

2.4.3
Job Server Access to job results via scripting

To get access to the data folder in case of success and in case of error as well as the name of the current job, the job-definition-file can contain the trigger variables outputFolder, failedFolder and jobName.

Read more...

2.4.3
Job Server Job administration via REST service

A Web UI is available for the Job control and administration of the Job Server.

Read more...

2.4.3
Job Server Webservice Trigger for Jobs

A job definition can define a trigger with the <webserviceTrigger> tag to start a job via the webservice interface.

Read more...

2.4.3
PLC/CoDeSys Fixed: Synchronization of CoDeSys resources does not compare standard values correctly anymore

During the synchronization of CoDeSys resources the values of pool parameters are no longer taken into consideration. This means that the differing standard values of pool parameters and resource parameters are no longer displayed during synchronization.

2.4.3
PLC/CoDeSys Fixed: Standard values are not set when a POU is changed through CoDeSys synchronization

While synchronizing CoDeSys resources the default value is taken into account.

2.4.3
PLC/CoDeSys Parameter for action components

In order to build actions into any components without having to insert the required parameters into the components, the actions contain the required parameters themselves.

2.4.3
Scripting Getter for parameter and parameter value

Groovy scripts now provide the methods getParameter(String parameterName) and getCalculatedValue() in order to get access to parameters and their values.

Read more...

2.4.3
Scripting Methods return the path or name of the output folder

The library Customizing_Engineering contains the class UtilAPI with the methods getOutputDirectoryForProjectName and getOutputDirectoryForProject. They calculate the absolute path to the output folder of the given project name, resp. of the given project.

2.4.3
Commands ImportEOXCommand overwrites all the components with the imported EOX file

An EOX file which overwrites the already existing assemblies can be imported by means of the new Customizing_Engineering.ForcefulEOXImportCommand command.

2.4.2
Documentation Update for the STEP7 tutorial

The Tutorial STEP 7 shows the use of the IO generator to assign the input and output addresses. Another section shows how a symbol table is generated from the mechatronic configuration. The last section shows how interrupt messages are inserted into mechatronic configurations and considered in the generation of STEP 7 code.

Read more...

2.4.2
Formulas Fixed: isAvailable() on DatabaseDataSource never deallocates the database connection

A bug-fix prevents that using the isAvailable() method suspends a database connection.

2.4.2
Form-UI Fixed: Focus in the Form-UI popup on Cancel instead of OK

A bug-fix focuses the [Cancel] button instead of the [OK] button in popup windows to prevent unintentional confirmation.

2.4.2
Job Server Fixed: XML import is to support xi:include in the file result imx

A bug-fix enables the import of an IMX file including the <xi:include> tag.

2.4.2
Job Server Input files for Job Server in FIFO order

The input files for the Job Server are processed in chronological order. The point of time when the file is inserted into the input folder applies.

Read more...

2.4.2
OFFICE Headless PDF generation in Word discipline

PDF files are generated by the WORD discipline without displaying any user interface. Additionally, Word-tasks will be closed correctly.

2.4.2
PLC/CoDeSys RefLocalId attribute is not set correctly when networkId > 10

A bug-fix fits the networks of child components on a Socket and updates the IDs of all referenced Elements correctly.

2.4.2
PLC/CoDeSys Declarations with CONSTANT result in double declaration in the generated code

An already declared variable is not written again, independently of the declaration section (e.g. VAR_INPUT) in which it is situated or of which data type the variable in both components is.

Read more...

2.4.2
Scripting The scripting method perform() is not available in instance methods

The perform() method can also be used in scripts of instances.

2.4.2
Web EEC Fixed: Access denied occurs when using MailTo in Form UIs for Web EEC applications

A bug-fix enables the use of the <mailTo> tag in Form-UIs for Web EEC applications.

2.4.2
Web EEC Web EEC file upload and Command call

The <fileSelectionForm> tag creates a new type of window to support uploading of the selected file.

Read more...

2.4.2
Documentation Changing all OLE objects for simple pictures

Any figures which have been embedded as OLE objects are inserted into the documentation as PNG image references.

2.4.1
Documentation Changing of all occurrences of 'mechatronic engineering' and 'functional engineering'

The words mechatronic engineering and functional engineering are replaced by mechatronic configuration and functional configuration.

2.4.1
Documentation Change of “Engineering Center” in English documentation

The product name Engineering Center is switched to Engineering Configuration.

2.4.1
Documentation Menu 'Model/...' without German translation

The translation of the Model menu in the GUI is corrected.

2.4.1
Documentation Documentation of OpenCommand in Web EEC environment

The documentation describes the application of the OpenCommand command in the Web EEC context.

Read more...

2.4.1
Documentation Documentation of CopyFileCommand

The CopyFileCommand command copies a file or a folder to the assigned destination.

Read more...

2.4.1
Job Server Method getOutputDirectory does not return correct work folder

The path to the generated data of the Job Server is determined by means of the getOutputDirectory() method directly.

Read more...

2.4.1
Job Server Job Server default settings

The settings for the Job Server can be set in user preferences.

Read more...

2.4.1
PLC/CoDeSys Change of default values for Replace parameters

As of version 2.4.1, the specification of the value is no longer interpreted as a value, but as a default value.

Read more...

2.4.1
PLC/CoDeSys Struct-nodes in UserDefindedDataTypes are optional

A bug-fix allows the optional use of struct nodes for user-defined data types.

2.4.1
PLC/CoDeSys UDT fragments, loops, and replace parameter

By means of the Plug-Socket concept fragments are placed as subcomponents of components of the User-defined data type type.

Read more...

2.4.1
PLC/CoDeSys References also function with actions

Reference components are created which are used as references to actions.

Read more...

2.4.1
PLC/CoDeSys Fixed: Negation of OutputSockets does not function correctly

The negation of output signals is executed correctly.

2.4.1
PLC/CoDeSys Control structures ("commands") also function in actions

Actions in resources are created as discrete subcomponents and are a reference to the action, which is situated in the resource of the parent discipline-component.

Read more...

2.4.1
PLC/CoDeSys Creation of reference components

Reference components are created which are used as references to POUs.

Read more...

2.4.1
PLC/CoDeSys Code creation of SourceUserDefinedDataType 2.4.1
PLC/CoDeSys Call concept for the language ST is based on Sockets including references 2.4.1
PLC/CoDeSys Abstract POUs do not need resources

Abstract POUs are created without assigning a resource. A corollary is that any subsequent change to abstract or from abstract back to non-abstract is no longer possible.

Read more...

2.4.1
PLC/CoDeSys Fixed: The code creation for global variables does not work correctly sometimes 2.4.1