Hi Davis,
Can you share your code for getting a calibration working with me? I might be able to help debug what's going on. Just to give you some confidence in the machine, the API's are all the same api's that are used with the official software. So if the actual software is working, you can rest assured that the api's are working. So this might just be a small mistake in your code.
A small correction to my previous reply: There is both a camera calibration and a turntable calibration end point in the API.
The camera calibration is used for automation and integration clients that have changed the cameras position with respect to each other. Don't use this, as the factory calibration is far more precise and done by robotic arms.
The turntable calibration on the other hand, is used for calibrating the turntable w.r.t the scanner at a specific focus length.
The pseduo code steps are:
1) Set camera focus, exposure and gain
https://matter-and-form.github.io/three-python-library/three/MF/V3/Tasks/SetCameras.html
2) Call Turntable calibration (requires calibration card on the turntable, connected to the THREE, and visible to both cameras).
https://matter-and-form.github.io/three-python-library/three/MF/V3/Tasks/CalibrateTurntable.html
3) After a success, then call scan with the turntable object (specifying steps and rotation amount) and the camera settings for the scan.
https://matter-and-form.github.io/three-python-library/three/MF/V3/Settings/Scan.html
You are correct about eliminating the floor. Scanning with the turntable will cut off any data points outside of an imaginary cylinder on the bed. So the points on the turntable itself and below will be cut off and discarded. This cylinder can be set with
Hopefully this helps a little.