Creating a new job

To create a new job, proceed as follows:

Open the job manager in the "Manage Recorder Jobs" section.
Click "New" to open the Job editor.

The following primary UI elements are available:

Area	UI element	Description
1		General job settings: Job name and description Trigger conditions to schedule recordings Metadata
2		SINUMERIK-HF signal selection: select which of the available HF signals shall be recorded.
3		SINUMERIK-LF signal selection: select which of the available LF signals shall be recorded.
4		Advanced job settings: MQTT data streaming
5		Return to the job manager without saving the modifications of current job definition.
6		Undo the last modifications.
7		Save the job definition and return to the job manager.

In the following section all available job configuration parameters are described in detail.

Job name

You can give the job a descriptive name by which you can identify it. The permitted characters are limited to letters, numbers and "_". If you enter any restricted characters, you will get an error message, and the field will be marked with a read indicator.

Note:

If the job has recorded data, then the name of the job is read-only and cannot be changed! Delete the recorded data so that you can change the job name.

Description

A short description of the recording job can be entered.

Metadata

To provide additional context information to recorded data sets you can define up to 5 metadata labels. A label is basically a name-value pair which can hold arbitrary string-encoded information. Metadata are written into the output files.

There are two types of labels:

constant: a static name-value pair, for example: (“machine_name”:“MACHINE_A”)
variable: the address of an arbitrary LF signal can be stated which will be evaluated exactly once in the beginning of the recording. The name of the label will be the address provided and the value will be the value retrieved from the SINUMERIK Connector

The following functions are available:

Area	UI element	Description
1		Shows the type of the current metadata label.
2		Enter the name of the respective label (only available for labels of type constant).
3		Enter the value of the respective label (only available for labels of type constant).
4		Remove the label from the list.
5		Add a new label to the list by selecting the desired type (up to 5 labels can be added).

Triggers

Triggers are a way to define when a recording shall start and stop. For both, start- and stop-triggers you can specify multiple trigger conditions, which are logically linked by the AND operator. This means that the recording starts/stops if all these conditions become TRUE.

In practice, situations can occur in which the stop trigger condition are never fulfilled.

Example: an operator manually aborts the machining program. The NC code used as a stop trigger condition is never going to be processed. Consequently, data recording is not stopped, and subsequent runs of the machining operation are not recorded because only one running instance of a recording job is allowed at time.

In any case you can enforce start and stop job manually at any time.

Triggers are defined in the “General” tab of the job editor using the depicted dialog.

The following functions are available:

Area	UI element	Description
1		Add a new trigger condition to the start- or stop-trigger.
2		Select the type of the trigger condition. Refer to the detailed description of the available types below.
3		Trigger condition value (exact representation depends on the condition type).
4		Remove the trigger condition from the start-or stop-trigger.
5		Activate / deactivate auto-stop behavior.

The following trigger condition types are available:

Trigger type	Description
Channel	TRUE if the specified NC channel is active
NC Code	TRUE if the specified expression is found in the current NC block. Consider that only the first 110 characters of the NC code are considered. In addition, the system will not recognize the following lines: Most M-commands (e.g, M6) Code comments (workaround: add 0-dwell: “G4F0;START”) Program flow constructs (IF-ELSE,WHILE etc.) The string matching is case sensitive. Example: `START` will trigger on the NC block `G4F0;START_PROGRAM` Alternatively, regular expressions can be used. Note that characters that have a special meaning in regular expressions need to be escaped, e.g.: \.[]{}()<>+-=!?^$\| Example: `.X\=[1-2].`* will trigger on `G1 X=100 Y=0 Z=0 F500` but not on `G1 X=300 Y=0 Z=0 F500`
Line number	TRUE if the current line number is equal or greater than the specified line number.
Call stack level	TRUE if the specified call stack level is reached. The call stack level of the main program is 0.
Program path	TRUE if the specified program path is invoked. Only the first 51 characters of the complete path are considered. The field is not case sensitive. Do not use this condition if the NC code does not contain any sub-program calls.
Active tool	TRUE if the active tool Id matches the specified number.
Selected tool	TRUE if the selected tool Id matches the specified number.

Note:

Only one instance of each trigger condition can be added to a trigger, except for LF signals. LF signals can be added 5 times.

The triggers are dependent on the HF_EVENT signal. If the “Publish on the Databus” checkbox is not selected for the HF_EVENT signal, the triggers will not function.

SINUMERIK-HF

The tab “SINUMERIK-HF” is only displayed if the application is connected to a SINUMERIK system. Here you can select which of the configured HF signals shall be recorded.

The following functions are available:

Area	UI element	Description
1	List of elements	The list on the left side of the screen contains all signals that will be recorded as part of the current job.
2	List of elements	The list on the right side of the screen contains all signals that are generally available in the application.
3		Use these buttons to move selected signals from one list to the other. Hint: You can also use drag and drop to achieve the same goal.
4		Filter the lists based on signal name or axis.
5	Axis column	Input fields for axis names. User can enter axis name for each signal.

Note:

You must define at least one active signal that is recorded, regardless of whether it is an LF or HF signal.

SINUMERIK-LF

The tab “SINUMERIK-LF” is only displayed if the application is connected to a SINUMERIK system. Here you can select which of the configured LF signals shall be recorded.

The following functions are available:

Area	UI element	Description
1	List of elements	The list on the left side of the screen contains all signals that will be recorded as part of the current job.
2	List of elements	The list on the right side of the screen contains all signals that are configured as low frequency data via the Common Configurator.
3		Use these buttons to move selected signals from one list to the other. Hint: You can also use drag and drop to achieve the same goal.
4		Filter the list based on the signal name.

Advanced

In the tab “Advanced” the following aspects of a recording job can be configured:

MQTT data streaming: if the MQTT service is correctly configured (see section Configuring MQTT data streaming) the data streaming feature can be enabled for a particular job. In addition, it is possible to route the data to a job-specific MQTT sub-topic.

The following functions are available:

Area	UI element	Description
1		Currently not supported.
2		Currently not supported.
3		Enable or disable MQTT data streaming for the current job. As a prerequisite the data streaming service (e.g. Flow Creator) must be correctly configured.
4		In addition to the global MQTT topic defined during commissioning of the application, you can define further job-specific topics which will be treated as sub-topics of the global topic. Example: workpiece_A/operation_1
5		Specify the maximum chunk size of a single MQTT message in the range of 100 KB to 5000 KB. Smaller values will lead to messages being sent more frequently.
6		Enable or disable saving job recordings to disk. If MQTT data streaming is disabled, this option cannot be changed.