I tried the new promising and exciting new feature "Recenter..." and there are problems with it. I tried it repeatedly in several processes and each time it showed the same behavior and problem.
Initial situation:
- Skywatcher AZ-EQ5 with Celestron Starsense auto-alignment in AltAZ mode. This means that the Celestron Starsense hand controller is connected to the Skywatcher AZ-EQ5. The Celestron Starsense hand controller is connected to the Windows 10PRO computer (8GB RAM) via a USB cable (50 cm) via an active USB HUB from the PC to the hand controller by the Celestron ASCOM driver
- Camera: ASI183MC Uncooled.
- Telescope: Skywatcher 200PDS with
- Pegasus Falcon rotator running in “derotation mode”.
- All active components are connected via ASCOM driver and are visible from the side in Sharpcap.
Yesterday I viewed M39 in the telescope. Positioning mount to M39 was done by Steallarium. In a second run I used Sharpcap to postioning M39. When M39 was succesfully found I carried out platesolving, then aligned the rotator to 0° / north, started Derotations mode in Falcon Software, performed platesolving again and then selected M39 in the DeepSky Annotation-Results window, adopted the name for the stack and then pressed the "Center in View" button and waited until Sharpcap M39 was perfectly centred in the sensor.
I then started LiveStacking in the Guiding TAB. I initially had a "recenter drift value" of 60, but I changed it to 35 during stacking.
sharpcap-41_10.jpg
After about 210 s, 35 was obviously exceeded and Sharpcap started a new plate solving. Everything was executed without an error message.
Time: 00:34 - 104 stacked
sharpcap-41_20.jpg
After completing the first recenter, the observed drift in the Guidind graph window increased dramatically faster. In the stack image you could also see a black bar on the right edge that grew very quickly
Time: 00:36 - 106 stacked
sharpcap-41_21.jpg
Time: 00:37 - 110 stacked
sharpcap-41_22.jpg
From this point on, Sharpcap performed a new recenter after only, one, two, three or four additional sub frames that were successfully added to the stack. After each recenter, the swings in the guiding graph became larger and the black bar became wider and clearer.
Time: 00:38 - 114 stacked
sharpcap-41_23.jpg
Time: 00:41 - 125 stacked
sharpcap-41_25.jpg
I was able to reproduce this behaviour repeatedly in a row. Started from a new starting position each time. At first there was a very quiet, barely increasing guiding graph for several minutes. From the first "automated" Sharpcap recenter procedure, everything got worse and worse, faster and faster.
Here are the links to the last four LOG files from Sharpcap.
Log_2023-09-28T23_19_49-9000.log
Log_2023-09-28T23_35_10-6436.log
Log_2023-09-29T00_08_39-6052.log
Log_2023-09-29T00_17_26-12124.log
I hope my description has all the necessary facts and data so that you can understand the problem. If anything is missing or further details are needed, I will be happy to help. If I should carry out other tests or examinations, I am happy to be able to support you.
Ouch!
![Surprised :o](./images/smilies/icon_e_surprised.gif)
![Cool 8-)](./images/smilies/icon_cool.gif)
https://f2m.org/sharpcap/sharpcap-41_22.zip
Servus - MunichAtNight - Ewald