Brille The last sentence in my post clearly makes the point about reduced processing time. And, yes, fewer frames means less data to take up storage but I hope that would be clear on its own.

I apologize for accidentally deleting the last comment due to my mistake. I'll explain here about the S30 gain of 80.
The S30 is fixed on HCG mode and normally has a gain of 200, it is the S50 that has a fixed gain of 80, so if your S30 has a gain of 80 in the fit header file, then something is wrong.

starnet59 In Android. if you need to revert , you can reset the SS. You can then delete the app from the Android device and side load the version you want. A side loaded version will not auto update.

S50 GAIN of 80, S30 GAIN of 200...I made a mistake in my initial post. Apologies for the confusion caused....

21Hk60qO

@support@Seestar

Hello Seestar team,

I am re-upping my previous comment to see if there are any thoughts on a resolution for the sky atlas in EQ mode and planning functions. Thanks! 😊

    21Hk60qO Yes, this is a very reasonable suggestion. I will contact you after confirming the situation with the team.

    Since the new version, there is no longer a message indicating that there are not enough stars for stacking.
    Is this normal?
    Thank you.

    Hi Balcony Astrophotographers,

    I have been able to get polar alignement by offsetting the start position in a way that, as the Seestar turns 270 degrees counter clockwise, it will point to some area that is not my upper neighboor balcony. It will need three points around the RA axis, I guess 60 degrees total like for the horizontal calibration, so account for that also. Once you adjusted your azimuth and altitude, you are ready to go.

    The tricky part is the first go to, as it is completely offset. So you need to find an object that the seestar will mistakenly point in a visible sky area.

    It will go there and do a first solve, and then will try to get to the real position.

    It will adjust (a lot) and potentially point a wall or whatever obstacle.

    At this point you SYNCHRONIZE MANUALLY EVEN IF POINTING AN OBSTACLE, and do a new go to this time to your desired object. Now it will approach correctly the object, solve, and eventually center the object.

    I had many clouds so couldn’t really do a meaningful efficiency test, but it seems to work.

    This is the awkward initial position, that in my situation will allow to get the polar alignement deviation not pointing at zenith (upper balcony in my case).

    And the dovetail bar offset…

    Stevan

    9qTXgfu8

    Thanks for the hint !

    Just tried that tonight, it seems to work, you need to offset your dovetail bar, so that is starts at a different angle than leds pointing upwards. It will depend on the obstacles. But the scope will scan three points like in the horizontal alignement, so some leeway must be accounted for.

    裕 沼尻 I have this same issue that I noted in another comment. They didn’t see it as a problem but they will after more people experience the inconsistency with the framing in EQ mode.

      Seestar app doesn't close when finished, has to be Forced Closed to exit since update.

      Any idea on a time line of the larger aperture seestar model release date and also on the release of the 60 second exposure time

      Hello. After the last version of the APP, I have unfortunately had to notice that there are satellite tracks on all the recordings from my S30, it is as :the function to delete images with satellite tracks no longer works.

        Thx Jon for the tip, it works for me too, although I had to point the S50 with the logo and the on/off head away from me, so the other way around than in your photo. I live in the northern hemisphere and only have a clear view of the west.
        Although it remains a bit awkward, hopefully there will be an update so that the S50 can easily be set to equatorial mode even without a clear view of the zenith.

          There are lots of posts in the official ZWO Facebook group about “banding” effects showing up in EQ mode. Some call this thermal noise, some attribute it to light pollution effects, and some say that dithering is not being used in EQ mode or at least more dithering is needed. Some also say that flat frame calibration is needed (and an old post before EQ where ZWO support even mentioned that flat frames are coming).

          It would help to have an official statement from ZWO on what is going on, what users can do to help compensate, and what ZWO is working on to address this. Thanks!