Automated building of PLC applications
Neuron Power Engineer provides a tool for automated builds of PLC applications.
Condition for using this tool: You have already installed the required license (see "Preparation", step 2).
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 a directory that will be used as the workspace
In case the directory does not exist, the tool creates it. 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 built
The project must not contain any syntax errors. All settings (e.g. required compiler settings) must exist for the target system (as it is required when the application is built within the graphical user interface of Neuron Power Engineer). -
The name of the →configuration to be used for the build (can be found in the PLC-object of the project)
-
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.
-
-
Make sure that you have a license that is suited for the automated builds of PLC applications. Details: See "Requesting and installing license".
-
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 NeuronPowerEngineer3 -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 |
|
|
name of the configuration |
|
|
absolute path to a workspace to which the project should be imported
|
|
|
path to the log configuration file |
|
|
Example 1 for invocation, with the check whether the workspace is empty |
---|
|
Example 2 for invocation, just specifying the project name because the project has already been imported into the 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 build. If the build 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. Or invoke the tool with the absolute path for the project. |
|
|
The specified configuration does not exist. |
Specify an existing configuration. |
|
|
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). |
Use an empty workspace or remove all existing data from the current one. |
|
|
An unexpected error has occurred. |
Contact Neuron. |
|
|
No license available. |
Make sure that there is a license for the tool and/or that the current computer has been set up correspondingly. Invoke the tool again. |