Known limitations

Red Screen

On a system overload caused by IED platform, the application might render a red screen fatal error. In this case, if a page refresh does not solve the issue, a restart/reboot might be needed to recover from this state.

Some dummy values in output file format

Fields "samplingPeriod" and "label" are kept with dummy values to keep backward compatibility. Field "value_type" in LF data output is kept as "String" to keep backward compatibility.

Unavailable LF data points

If there is any unavailable LF data point address defined, this may also affect correctly defined data points in the same job configuration, and job recording may not read data properly.

Downloading corrupted files

If there is a corrupted recording file, you may not be able download it via recording list. You need to go into the recording and download via corresponding entry.

Frequent start/stop triggers

When start and stop triggers are set up to be very frequent, the application tries to write high number of small files depending on how frequent start/stop triggers are. Due to that reason application may crash. Please avoid frequent start stop triggers.

Empty recording file

When not selecting any data point in the recording job, the resulting recording file may be empty.

Same start/stop triggers

The system behavior is undefined in case of same start and stop triggers are configured.

Download progress percentage indicator

Consider that in rare cases the displayed recording job download progress percentage indicator may be inaccurate when switching the page.

Downloading a recording of a running job

When trying to download a recording while the recording job is still running, you may get an empty zip file.

Empty error section at the footer of the output file

Error section at the footer of the output files might be empty, do not assume the system does not have any error if this field is empty. Refer to the application logs to observe application errors.

Header’s Initial section

The values in the header's Initial section (like HFProbeCounter and others) may be inaccurate.

Metadata variables in job editor

Custom defined metadata variables in job editor, which are normally recorded in "Metadata" field of output file, are not recorded

Creating copy of a job

If some of the available data points by SINUMERIK Connector are removed, this will have an effect on cloning of a job. This happens when data points are removed and subsequently SINUMERIK Data Recorder is restarted. In this case, a success message will be shown but the job copy operation will actually fail.