level sensor calibration does not complete

dqsbRAvH

Hi,
I recently purchased an S50 and ran through the calibration steps, however the level sensor calibration never finishes (it is currently still running after 15 minutes...).
I have recalibrated the compass multiple times, tried in wifi mode, tried in station mode yet it never completes.
Is there something else I can try? (I have the latest firmware and app installed).
regards
Jon

Support@Seestar

dqsbRAvH Could you send me the operation video or the problem photos?

gofraro

For level calibration, you have to put the Seestar directly on a flat surface, that is accurately leveled (check your countertop in the kitchen with the good old spirit level (in all directions). Make sure, all rubber pads of the Seestar are in place. Press "Calibrate" and done.

Steven Fox

I was getting weird level "incorrect" messages during a nights session since last firmware upgrade. Decided to try a recalibrate but like you it never ends.

CAZ3650

Steven Fox I’m getting this issue too. But only since the software update. I start the session at 0.0-0.3 but 20 minutes into the imaging, it’s asking me to level and is showing white circles between +3 to +7.

dqsbRAvH

Support@Seestar

On the app I don't get any any error, it just never finishes.
I've tried on a desk and on the leveled tripod.

Are there not logs I can send through as well?

Support@Seestar

dqsbRAvH
After reproducing this problem, please do not shut down your device. You can log in to your Seestar APP account and submit the log according to this tutorial. https://h5.seestar.com/course/79221
Remember to check "Add log".

dqsbRAvH

Support@Seestar tx, submitted (BT20250522691160S)

Is there a way for me to view the logs?

Support@Seestar

dqsbRAvH You can see your log here. We will reply to you in the log if there is any relevant progress.

dqsbRAvH

Support@Seestar I was referring to actual system log that was sent through - not the log of me creating the ticket

dqsbRAvH

fyi, I've received confirmation this is a bug and will be fixed in next release

Steven Fox

CAZ3650 I have now received a reply from ZWO saying it is a bug and will be fixed in the next firmware upgrade.