Experiences and new bugs for version 2.1.0

FZS

Hi, here are some experiences and possibly new bugs for the latest version.

I think the Polaris issue was corrected in some way, it is almost in the center after GoTo starting from default position (with arm closed), however, when I hit GoTo after another object observed, it still gets out of the frame.
Images look brighter and therefore much noisier than in previous versions. I don't know if it is a bug or an intentional modification.
Less frames are discarded, even in very cloudy sky. That's good!
Guest mode pop-up message in the bottom of the screen can't be closed and it's confusing: if I hit "Exit", it disconnects the device and won't connect again in Station Mode unless I connect the phone/tablet directly to the Seestar's WiFi with Bluetooth enabled. Please, add a "Close" or "X" button.
After the update it fails finding the Sun. Maybe it's just a temporary issue as for today (many users told me the same).
I like that the amimated circle disappeared during the finding process, because it was confusing.
Framing feature is good, I recommend to set an 1.1-1.2× magnification without rotating, if you don't have hours for shooting. Works perfectly for objects that almost don't fit in the default frame, e.g. M45.

tom-dd

Finding the sun: The sun was also found immediately after the update (very clear sky).
BTW, since I used the Seestar for the first time, I have never calibrated the compass again.

FZS

tom-dd For me the opposite. Before the update I had never had any problem finding the Sun, and now it stopped finding it automatically.

Kommuna

У меня после обновления обрывы соединения с телефоном по Wi-Fi в процессе съемки (

Tech@ZWO

Kommuna Thank you for your feedback, we will optimize the guest mode in the next version.

For point 6, do you mean particle animation?

FZS

Tech@ZWO I ment there was something like an animated circle in the center of the screen (below the "Finding object...." message), so not those flying dots, that's ok. 🙂

Tech@ZWO

FZS Got it, Thanks.
Regard of the problem finding the Sun, Seestar relies on both compass and leveling data to accurately position itself and find celestial objects like the Sun and Moon. If the device fails to find them, it's usually because one of these calibrations is off.
Step-by-Step Troubleshooting

Identify the Problem: Compass or Leveling?
○ Observe the direction of the Seestar's lens during the search process.
○ If the direction is completely off, it's likely a compass calibration issue.
■ Solution: Recalibrate the compass.
○ If the direction seems correct but the device cannot locate the Moon, the issue is likely with the leveling.
■ Solution: Recalibrate the leveling system.

Gulyas K

Tech@ZWO A lot of people complain about this Sun and Moon finding issue since the new firmware.
I have to find the Sun manually, because Seestar always aims above the Sun about 1-1,5 degree during the finding process. I have a granite table at work, it is perfectly leveled, because of the high precision work we do. The quality guys check it every week. I did the level calibraton of my Seestar on this granite table, so it can't be a level issue. I did the compass calibration in the field, at least 30 meters from every iron or other metal things. I checked it with a classic compass and it looked good. I adjusted my Seestar with 0,2 degrees level issue, hit Goto Sun, and aimed over the Sun about 1,5 degrees while finding it. I saw the brightness of the Sun at the bottom of the field of view, when automaticly slew to find, but never found it. Then I switched Seestar off and back on, adjusted the tripod level with 1,5 degree issue to aim a bit below the Sun. When I looked at my Seestar, it was clearly seen it was not leveled and leaned towards to the Sun. Hit Goto Sun and found it immediately!
As you can see this should be something else, not a calibration issue.

Tech@ZWO

Gulyas K Could you please perform this test?
First, adjust the Seestar to a horizontal level and record the value. Use the arrow keys to rotate Seestar 90 degrees in azimuth axis, then check and record the level error value in the settings. After that, rotate it another 90 degrees, check the level value again. Repeat the process once more. Finally, compare the differences in level value from all four measurements. If the deviation exceeds 2 degrees, it indicates a significant level calibration data error. We recommend recalibrating according to this guide.
https://h5.seestar.com/course/8744

fedorauser

May I join this problem, because since the update I also have the problem that the sun searches with 90° deviation and compass and leveling (0.1) was recalibrated. The sun is in the SW and the Seestar moves NW. Three hours later after OFF/ON, the Seestar moves to the moon, Saturn and Neptune in solar mode without any problems.

Tech@ZWO

fedorauser According to your description, the compass data is wrong, need to recalibrate the compass again, and make sure there is no iron and magnet around the Seestar.

Gulyas K

Tech@ZWO Thank you for the answer! Yes I've done this 90 degree rotation test before. The values were between 0,3 degrees.
Sorry to say that, but as for this level calibration method in the video, well, whoever found this out, maybe he/she has never used a bubble level before. To read the bubble level accurately, you have to take a look at it directly from the top. Which is impossible in our case because of the Seestar's arm.

fedorauser

Tech@ZWO Thanks for the answer, but it doesn't work with the sun, but it does in stellar mode and the moon was also found. The weather is not playing along at the moment and I will test it again, but the problem with the crashes after the first mosaic stack certainly has nothing to do with it.
LG