Automated importing of the projects
Neuron Power Engineer provides a tool for the automated import of Neuron Power Engineer →projects into a workspace.
If you invoke this tool, you will be able to use the resulting workspace when invoking other automated tools afterwards (such as for the automated build of a PLC application). Hence, the following tools do not need to import the specified project anew from an empty workspace for each invocation of the tool. These combined invocations result in the increased performance of the tools.
Good to know |
---|
The tool is intended for usage by an experienced user of Neuron Power Engineer. A condition for the successful usage of the tool is the knowledge of the action to be executed as it would be executed in the graphical user interface of Neuron Power Engineer. The output of the tool is in English only. |
In this article: |
---|
Preparation
-
Make sure that Neuron Power Engineer is installed. Have the following information prepared:
-
The path to the Neuron Power Engineer installation directory
-
The path to an existing directory that will be used as the workspace
If the optional parameter-checkEmptyWorkspace
is used (see the description of this parameter below), the directory must be empty. -
The path to the project that should be imported
-
The path to the log configuration file (see below for more information)
A sample configuration file is included in the installation of Neuron Power Engineer.
-
-
Open a command line: e.g.
cmd.exe
under Windows and navigate to the Neuron Power Engineer installation directory.
Invocation
|
Invoking the tool under Linux is not officially supported. However, if you want to try invoking the tool under Linux nevertheless, replace the part NeuronPowerEngineerc --launcher.ini NeuronPowerEngineer.ini -application
of the above-mentioned invocation by NeuronPowerEngineer -application
. The remaining part of the invocation is identical to the above-mentioned invocation.
Description of parameters:
Parameter |
Description |
Example |
---|---|---|
|
absolute path to the project that should be imported |
|
|
absolute path to a workspace to which the project should be imported
|
|
|
path to the log configuration file |
|
|
Example 1 for invocation, incl. check of the empty workspace |
---|
|
Example 2 for invocation, no check of the empty workspace |
---|
|
Log configuration file
This file is needed to configure the log4j logging mechanism. The file specifies how log events are output.
Sample log configuration file |
---|
|
Troubleshooting
The file that is specified in the log configuration file contains information about the import. If the import has not been successful, fix the problem according to the following table.
Return code |
Message on STDOUT or STDERR |
Cause |
Solution |
---|---|---|---|
|
|
|
|
|
|
An argument or parameter is missing. |
Invoke the tool as specified above. |
|
|
The specified project does not exist. |
Specify an existing project. |
|
|
The code image could not be created. |
|
|
|
The project contains syntax errors. |
Open the project in Neuron Power Engineer and fix the errors displayed in the Problems view. |
|
|
The workspace already contains data (e.g. one or more Neuron Power Engineer projects). |
If you have specified the parameter |
|
|
An unexpected error has occurred. |
Contact Neuron. |