forum.heinrichsweikamp.com

Reading through the videos and replies, it honestly sounds less like a calibration technique issue and more like the sensor is struggling to register the full motion range consistently. The fact that it always stalls around the same point after so many attempts is what stands out to me.
One thing ...

In my experience, when something looks off with the readings, it's always worth double-checking sensor calibration and battery condition first, as they can sometimes cause surprisingly inconsistent behavior. Curious to hear what the final cause turns out to be.

I had a similar headache trying to get the connection to stable up. If it's dropping mid-sync, try completely unpairing the OSTC from your device's native Bluetooth settings first, restart the device, and then try pairing it directly through the companion app instead. Also, making sure no other ...

It’s always helpful when someone comes back with the actual fix instead of leaving the thread hanging. This will probably save a few other people a lot of troubleshooting time.

I had something similar happen after a firmware update once. Rechecking the battery contacts and doing a full reset/calibration fixed it for me. Sometimes the issue seems more related to power stability than the sensor itself.

I’d probably start by checking the battery contacts and doing a full reset/calibration cycle first. A lot of odd dive computer behavior seems to come from power or sensor initialization glitches after updates or battery changes. Hopefully it’s something simple and not a hardware fault.

Ugh, compass calibration is always the worst part of a new dive computer setup. 😖
Matthias is spot-on—it totally looks like you're trying to roll it instead of pitching it during that part of the sequence.
The easiest way to visualize the pitch rotation is to hold the OSTC flat like you're reading ...