Hey there,
I've lately run into the problem, that I can't issue a new calibration if the calibration progress fails (empty calibration results or too many attempts at resampling).
Before starting a calibration, I always check whether a calibration is running, and if yes, I call abortCalibration(). Even if I call it multiple times and wait a few seconds before trying again, the tracker doesn't seem to react to the abortion request. If I try to start a new calibration, it fails because a calibration is already running. In this state, the calibration from the tet ui also gets stuck at the first point or displays an error message (I think this depends on whether it has been running before or was started after the problem occurred).
I use the latest version of the sdk and have firmware reversion 293.
I experienced this problem yesterday for the first time, but I can't really tell if this is because something changed (I didn't change my code, but there was a windows update) or if I've just not had a calibration fail since the last sdk update.
I'd be extremely grateful for fast help,
best,
alina
