Balluff BVS ID-M1280 F1 Series, Configuration Manual

Page: 199 / 316

BVS ID-M1280xF1-xx-xxx
english 41
1.
a.
b.
2.
a.
b.
3.
a.
b.
2.4.4 Runtime optimizations of the inspection runs
The time required for an inspection run can fluctuate due to the system. This also happens even if the external
conditions do not vary noticeably from one inspection run to the next. On the one hand, this is due to changes
in the image that appear insignificant to the human eye, and on the other hand to internal activities of the
BVS
ID that are not obvious.
Some measures can be taken to reduce the average runtime and the amount of runtime fluctuations:
In the tool Inputs :
Reduce the image area of interest (AOI).
A so-called quiet zone should be maintained around the code, i.e. do not reduce the image
section directly to the edge of the code.
Select the image area of interest (AOI) in such a way that it contains only the code together with
the plain background.
Disturbing elements (text, etc.) should be outside the image section if possible.
In the tool Analysis :
Limit the time used for reading the codes.
The
Tool timeout parameter is available for this purpose. Instead of a runtime peak, NOK results
are returned with the error message "Timeout occurred while searching for code".
Reduce the code types.
The tool tries to find all chosen code types. More code types lead to a longer execution time of
the tool. Therefor it is reasonable to search only for the code types available in the image.
In the web browser:
Close the SensorApp interface in the web browser and operate the BVS ID in standalone mode
without the user interface.
If the
BVS ID is operated with the SensorApp interface open, deactivate the live image display of
the SensorApp interface.
By suitable selection of the parameter Tool timeout it can be chosen within certain limits whether a runtime peak
leads to a NOK result or a trigger error. The BVS ID is able to partially compensate for runtime fluctuations, as
long as a new image acquisition can be performed in parallel to the evaluation of the previous image. It is
therefore possible to select the trigger frequency and/or the
Tool timeout higher than the largest possible
runtime peak.
At a high trigger frequency and in the Continuous trigger mode, the runtime fluctuations are greatest because
of the high system load. The execution time displayed in the list of inspection results in the Continuous trigger
mode is therefore only a rough indicator of the execution time actually required in the Rising edge trigger mode
with low trigger frequency. It is therefore not recommended to set the maximum possible trigger frequency and
the Tool timeout based on the Continuous trigger mode. Instead, we recommend setting the trigger mode to
Rising edge , triggering with the desired frequency on a test basis and selecting a Tool timeout that matches this
frequency. If a trigger error is now reported in the Device info area or NOK results appear in the list of inspection
results with the error message "Timeout occurred while searching for code", the selected trigger frequency is
too high or the selected
Tool timeout is too low. With the above tips to reduce runtime and runtime fluctuations,
a stable application with the desired trigger frequency can be realized.