Mosaic mode rotation

Garin

I'm having an issue with mosaic mode on my S50, maybe it's just a misunderstanding on my part. I'm trying to image the prawn nebula but want a final image that has the prawn part vertically in the image, so I selected the frame rotated it to the orientation I want and started the mosaic, it's building the image up fine but the live view is not the selected frame view ? its the same as if I hadn't rotated the frame. I've added a pic of the frame I set and a pic of what the seestar actually imaged, the image was definitely a mosaic just not it the selected orientation, looks like it centred the frame but didn't rotate it. Has anyone else experienced this or found a work around ?

裕沼尻

Garin
Garin, have you used the Seestar S50 in EQ mode?

I've pointed out the problem that the rotation direction does not match Atlas when framing in EQ mode, but the support staff did not understand and have not yet fixed it.

In EQ mode, the rotation direction should be based on the equator, but it seems to be calculated based on the horizon.

For example, if you want to align the long side with east-west, you can shoot with the intended composition by specifying a composition rotated 90 degrees to the Zenith.

This problem occurs when shooting a position away from the meridian.

Garin

裕沼尻 yes it’s occurring in eq mode, I don’t recall it happening in az mode.

BigJRocksIt

Great catch on this... I am currently using EQ mode on Markarian's Chain and noticed that the framing didn't work as I had configured in the plan. From the framing assistant it looks like I could fit the whole chain in one shot without using mosaic mode, due to this problem you've found it has to use mosaic to fit the entire object in.

ZWO needs to address this as this adds long delays trying to build the mosaic to fit the entire object in view.

Support@Seestar

Actually, the rotation of the mosaic area can be adjusted manually in the current Seestar App. After entering Mosaic Mode, you can tap and drag to rotate the frame to match the desired orientation — including 0°, 90°, or any custom angle. This helps optimize coverage for elongated targets like the North America Nebula or the Cygnus Loop.

Hope that helps!

裕沼尻

Support@Seestar
Of course, I understand that it is possible to rotate with Framing, but I am pointing out that there is a bug.
In EQ Mode, the rotation of the field of view displayed on Atlas and the actual field of view are not aligned.
In AZ Mode, it is normal.

BigJRocksIt

Support@Seestar You are misunderstanding the problem, let me try to explain again.

When you configure a plan for a target that does not require mosaic and rotate the target frame as you want in the plan, the framing that was set in the plan does not apply to when the plan is executed. My steps to repro this are below:

I set the target as M86 Markarian's Chain
I rotate the frame to allow the target to be captured without the use of mosaic and save the plan
When I execute the plan the S30 ignores the framing that was set in the plan and only captures the object AND uses mosaic to capture the entire object

To simplify the explanation, I would say that the plan is ignoring any framing that is being set.

裕沼尻

Support@Seestar
I explained this in V2.4.0, but I'll explain the framing bug in EQ Mode again.
I'm not a native English speaker, so I might not be able to explain it well, but I'll start from the basics. Do you understand horizontal coordinates and equatorial coordinates?

Horizontal coordinates: A coordinate system in which the horizon is at an altitude of 0 degrees and the zenith is at an altitude of 90 degrees.

Equatorial coordinates: A coordinate system in which the celestial equator is at a declination of 0 degrees and the celestial north pole is at a declination of +90 degrees.

In EQ Mode, equatorial coordinates are the basis.
When setting framing in SkyAtlas, the display and settings are done in equatorial coordinates.
However, there is a bug where when you start shooting, the image is taken with a rotation angle in horizontal coordinates, resulting in a different composition than in SkyAtlas.
I'm sorry, but I would like this bug to be fixed.

P1x26Yb4

BigJRocksIt ditto here. I have created mosaic plan using multiple 1x/1degree overlapping objects. Open the plan & all you see is a default, square to the grid plan for each step. Mosaic rejections seem to have increased since last update.. Before, it was take 4 reject 1 image. Now it is reject 50% in 10s/image. Reject 60+% in 20s/image. Same s30, same position. Seems rush to production with little documentation or calibration to no spec. (You get what you get because there is no calibration spec). But, I must say, for $400 I got my money worth.

BigJRocksIt

@[deleted] has the visual of the problem captured correctly above, or at least for my issue.

While creating the plan I can rotate the scope "blue" frame to match the rotation of the target "red" frame, but when I go to run the plan the framing and rotation are completely ignored.

Markarian's Chain should fit neatly in one frame, not 4.

Daemon42

BigJRocksIt I tested this last night, and it worked as expected. Resultant mosaic image matched the selected rotation of the frame. I didn't do it as a plan though. I just set the frame and started it. Maybe try that, and see if there's a difference between direct and plan.

BigJRocksIt

Daemon42 This is my test for tonight, skies permitting.

Coming from using an ASIAir with my main rig I somewhat expected the same functionality with My S30. Seems like the experience should be the same across the platforms. When I think of "plan" mode, I think of not having to interact with the system at all to capture what I want. Having to "pre-frame" everything is not optimal.

marvindj

裕沼尻 Your English is very good. You have just explained this issue in a manner that my brain can understand.