This article is for V2 and V1 3D scanners.
If calibration fails in MFStudio it's usually for one of two reasons. Either the camera can't see the check board pattern on the calibration box/card, or the ambient light is too bright.
Calibration Check board Pattern out of Camera Frame
Sometimes calibration in MFStudio will rotate the calibration card/box on the scan bed in a full circle, and/or never turn on the lasers, and ultimately report that calibration failed.
The most common reason for this is the calibration card/box is too close to the camera and is out of its frame-of-view. This is particularly likely to happen when using the calibration box, on step 2, when the box is moved towards the camera. It is very easy to move the box too close.
To address this problem for the box, on the first step, place the box on the scan bed so that the side with the check board pattern is over the center of the scan bed, with the rest of the box sitting behind the center. Then, on step 2, move the box forward only 1 cm/half an inch. At no point will the whole box sit directly over the center of the scan bed.
To address this problem for the calibration card, for the first step of calibration, place the card on the center of the scan bed. On the second step of calibration, move the card forward 1 cm/half an inch.
Ambient Light is Too Bright
If you have followed the card/box placement instructions above and the scanner is still not calibrating, it may be that the lighting in the room is too bright.
In very bright rooms, with lots of sunlight and/or fluorescent lighting, the camera may not be able see the check board pattern. If "very bright" describes your room, try blocking out some of the light from the scanner before calibrating. You can turn off the overhead lights, or just use cardboard, books, file folders or similar objects to wall off the area around the scan bed.
Still Not Working?
If after trying these suggestions your scanner will still not calibrate, please submit a request or contact us at support@matterandform.net with your MFStudio log file and we will investigate the problem for you.