Setting Blob NumberToFind to 0 causes wrong camera and robot world coordinates

> Service & Support > FAQ > Setting Blob NumberToFind to 0 causes wrong camera and robot world coordinates

Setting Blob NumberToFind to 0 causes wrong camera and robot world coordinates

Symptoms
If NumberToFind is set to 0 for a Blob object (to find all occurrences), then Camera X, Y, U and Robot X, Y, U values will be zero if the object is used in a sequence with calibration. :p>

Causes
This is caused by a bug in EPSON RC+.

Remedy
:p> To workaround, set NumberToFind to a value greater than 0.

Status
This problem was fixed in version 3.6.0.

General Terms of Business | Contact | Provider identification | General Terms