Initial goto offset by 30 degrees since the last fw update: Page 2

Initial goto offset by 30 degrees since the last fw update

Support@Seestar

@"pscharff"#p98301You are right, in fact we are also optimizing it, you can download V2.6.1 now to try it out.

pscharff

It seems like this problem hasn't solved with the latest firmware update.

On today I have made the folowing test:
I have switched on the Seestar, and then I have noted the coordinates of the Seestar, you can see in "Advanced features" -> "Compass Calibration". There was displayed an azimuth value of 98°. So, there Seestar "thought", that it was pointed to an azimuth value of 98°. But in fact the arm of the Seestar was pointed to an azimuth value of about 20°.

In the Seestar app I have choosen T CrB as target again. At this time the azimuth of T CrB was 196°. After I have selected "Goto" to T CrB, the Seestar began to move and it stoped at an azimuth of 120° (value from the app), which corresponded with the real direction. Thats a difference of 76° to the target.

Lets go to the beginning.
As I wrote, the Seestar "thought", it was pointed to an azimuth of 98°. The target's azimuth was 196°. So, it had to move about 100° to the target. But in fact it was pointed to an azimuth of 20°. The Seestar has moved the 100° and it stoped at an azimuth of 120°, which corresponds to the value of the app.

I would say that there still exists a compass calibration problem of the Seestar.

Patric

pscharff

Here comes a small update regarding this problem.

On yestarday I have made a Seestar session under an open sky. Nevertheless the Seestar app has displayed a wrong azimuth value. Then I have switched of the Seestar. Afterwards I have switched it on again, and then I have recalibrated the compass. Then the Seestar app has shown the correct azimuth value, and the GoTo to T CrB worked perfectly.

So perhaps one can conclude the following:
On obstructed views (e.g. balcony) it is essential, that the Seestar is calibrated correctly. It could be necessary, to need to recalibrate the compass of the Seestar before every seesion, like you need to do it for sun and moon observations. Then it is likely ensured, that the Seestar will stop for plate solving near the target.

Under an open sky with unobstructed views the calibration is not so important, and it is not necessary, to do it on every session, because the Seestar will find the target by using plate solving, even if the the Seestar stops at a large deviation to the target.

Patric

Lilo

pscharff
On a balcony there are a lot of magnetic parts around. So, compass becomes unusable even if you recalibrate it even several times.
So, just select any object in atlas, probably it requires several attempts for seestar to see open sky. After that it plate solves, syncs to the sky and everything works.

pscharff

Lilo
Thanks for the info.

I was half afraid, that the usage of the Seestar on a balcony could be attended with problems. But I was very optimistic after the yesterday's session. And the first three "plan" sessions on the balcony in June/July were finished without problems.

Patric

Misam

Just thinking out loud: I guess the Seestar can get some readings/figures/whatever from its gears...? If I level the Seestar manually and set e.g. the power button side facing south (again manually), why couldn't I now just tell Seestar that now you are levelled and facing at certain direction. It could then use those setup readings from the gears to find the sun/moon or go to some open sky area to do plate solving (I could even tell the Seestar at what direction the open sky area is).
The Seestar should be plug'n'play but obviously needs some workarounds even in a basic startup situation...

A GoTo Dobsonian is much easier with its home position procedure...!

Balrog

Support@Seestar
Three months later, after updating to the latest firmware and calibrating the compass before using the Seestar S30, the problem persists, the initial GoTo position is offset by 30 degrees. When are you going to fix this? This is unacceptable, it used to work perfectly, and you seem incapable of resolving this issue.

Support@Seestar

Balrog Did you submit any logs? We need to analyze the logs to confirm the problem and provide a solution. Currently, this issue shouldn't exist. Could you reproduce the problem and then submit the logs? Thx

Balrog

Support@Seestar
I've already sent the log. I hope you can fix it.

« Previous Page