Display difference in rotation between solved image and current FOV #45449
I think rotation with regards to (re-)framing could be improved upon. What I am currently doing:
- Solve an image in the alignment module
- Watch for the resulting angle to appear in the rot field
- Quickly take note before it gets overwritten by the solution of the next capture
- Subtract the values and rotate my imaging train/cmaera by the resulting amount
Sequence Generator Pro and N.I.N.A. both offer a manual focuser, which upon solving and determining the current FOV, prompts the user to rotate the camera by the correct amount. So basically what I am doing manually.
I could do without the prompt , but having the difference in rotation of a solved image and the current FOV in a more permanent fashion would be very nice. I am sitting in front of the screen like a hawk, waiting for the solution before it gets overwritten by the next capture
The same goes for the KStars windows where the solved FOV is only displayed until a new capture is solved. Being able to have a permanent FOV indicator for the manually loaded and solved image woudl be nice, too.
Display difference in rotation between solved image and current FOV #45455
So is your goal here :
1. To use the "load and slew"functionality of Ekos to tell it to load an image, go to that image, and tell the user how far to rotate the camera as a goal and then provide feedback as to how far right and left they have to rotate it until it matches.
2. To have an algorithm to set a target orientation for the Camera to be in and then to plate solve and manually make adjustments until it matches the target orientation..
3. To just display the difference between which way it thought the camera was oriented compared to how it is really oriented based on a plate solve?
Display difference in rotation between solved image and current FOV #45456
It is 1.
Or even simpler: add another edit box which displays the difference in degrees between the last image that had been solved using "load and slew" and the last image that has been taken by the alignment module (as there is no way to prevent another image taken anyway when using "load and slew").
The other way would be to add a radiobox "solve only" so the user can just load and solve, without ekos trying to actually get there. That at least would remove the timing component out of reading the rotation.
I have just been looking at the alignment module code, it seems there is support for rotators, so I guess it would also possible just to have an INDI-driver implementing a manual focuser, prompting the user to rotate?
Display difference in rotation between solved image and current FOV #45462
So Ekos supports both in a way. The requirement is to first solve an image before any of this can be set. I just tried this live with my home observatory. I had to fix a couple of minor issues that will be in KStars v3.3.7 due very soon (tomorrow or Thursday).
In the first part of the video, you can see I set rotation to 20 degrees E of N (it was 4.7). Then after solving the image, you can see the orientation reported by astrometry matches what we requested.
In the second part, I am currently at 20 E of N, and I "Load & Slew" an image I captured while the rotator was at 4.7 E of N.. so it solved the image, and then it rotated to 4.7 as expected, and it solved again to make sure we are indeed there at that location and orientation.
Display difference in rotation between solved image and current FOV #45479
I do not know how to apply that routine for my use case. I understand that you use a motorized rotator? I have to rotate manually, i.e. loosen the clamping of drawtube or camera, rotate and tighten again.
Ekos ideally should prompt me how to rotate, let me acknowledge when finished, check against a new capture and reiterate until within a given deviation.
Display difference in rotation between solved image and current FOV #45517
This got me thinking it would be neat if the align module displayed a refreshable overlay of a few star positions that correspond to a position and rotation to match a solved image or desired orientation in degrees.
I'm thinking manually matching 3 or 4 stars within small targets would get you pretty close.
INDI/KStars on Raspberry Pi 4, 4gb
Raspbian Buster with AstroPi3 script configuration
Skywatcher HEQ5 Pro Mount
Canon 600D Camera
Orion SSAG/ASI120mm @280mm Guide Scope
Adafruit Motor Hat shield
Adafruit GPS Module
Generic Bluetooth Joystick.
Startech 7 port powered USB Hub.