Error messages in the ibaQDR event log

Peak detected of {x}s on coil ID of {ML}

This error occurs if the tracked part ID has changed twice within 2 s. This is normally an indication of a tracking error in the ID signal.

x

No time data found for {x} in entrycoil {y}

No time data available for signal x in entry product y.

Stopping QDR datastore because an error occurred in measuring location {ML}

An unexpected error occurred at the measuring location, which led to the ibaQDR data store being stopped. Check the ibaQDR and ibaPDA server log files for more information about the error.

Product file {x} already exists

A file with the name {x} already exists. ibaQDR will attempt to assign an alternative file name by appending a number.

Error creating file {x}: {y}

Generation of product file {x} failed. {y} specifies the reason. This error leads to ibaQDR being stopped.

Error creating directory {x}: {y}

The product directory {x} could not be created. {y} specifies the reason. If {x} was the base directory, ibaQDR attempts to use the backup directory to generate the product files. If {x} was the backup directory, ibaQDR is stopped.

Exception in QDR thread: {x}

Error {x} occurred during processing of ibaQDR product files. This error leads to ibaQDR being stopped.

x

There are entrycoils missing for {ML} --> this measuring location and all measuring locations in front of it are being ignored!!!

ibaQDR cannot find any data for the current product at measuring location {ML}. This can happen if ibaQDR is not yet fully synchronized or if the tracking is faulty. The product file will not contain any data for this measuring location and for all upstream measuring locations.

There is a {x}% difference between the exit length at {y} and the entry length at {z} for the product file {a}. Please check the length signals.

The difference between the exit length at measuring location n and the entry length at measuring location n+1 is more than 10 %. In theory, the two lengths should be exactly the same. This error can occur if the tracking is faulty or if the configuration of the elongation for measuring location n+1 is incorrect. ibaQDR deals with this difference by stretching the exit length from measuring location n uniformly to the entry length for measuring location n+1.

x

Processing time-based data failed: {x}

Error {x} occurred during processing of the time-based data from measuring location n. ibaQDR ignores the time-based data from measuring location n and generates a product file at measuring location n-1.

Data is missing in QDR productfile {x}. Examine the qdr log for more details.

More than 5 % of the data in product file {x} is missing. This is indicated in the info field $QDR_DataMissing. This can happen if ibaQDR is not yet fully synchronized or if the tracking is faulty (incorrect length signals). The following errors then appear in the ibaQDR log file.

x

ID={x} --> Insufficient data: needed data up to {y}m, but data only available up to {z}m

This error occurs if no data is available at {y} m of ID {x}. This can happen if ibaQDR is not yet fully synchronized or if the tracking is faulty (incorrect length signals).

ibaQDR has data up to {x} m. The missing data {y} - {z} is ignored.

ID={x} --> Data needed up to {y}m, but data only available from {z}m --> No data available for this product coil at this measuring location

This error occurs if no data is available at {y} m of ID {x}. This can happen if ibaQDR is not yet fully synchronized or if the tracking is faulty (incorrect length signals).

The product file will not contain any data for this measuring location and all upstream measuring locations.

ID={x} --> Insufficient data: needed data from {y}m, but data only available up to {z}m

This error occurs if no data is available at {y} m of ID {x}. This can happen if ibaQDR is not yet fully synchronized or if the tracking is faulty (incorrect length signals).

ibaQDR has data up to {z} m. The missing data {y} - {z} is ignored.

ID={x} --> Data needed from {y}m, but data only available from {z}m

This error occurs if no data is available at {y} m of ID {x}. This can happen if ibaQDR is not yet fully synchronized or if the tracking is faulty (incorrect length signals).

ibaQDR starts the coil at {z} m instead of {y} m. The missing data {z} - {y} is ignored.