×

INDI Library v1.9.1 Released (26 Jun 2021)

Bi-monthly INDI Library v1.9.1 is released bringing a few new drivers and improvements to existing drivers.

Dither messes up guide exposure

  • Posts: 745
  • Thank you received: 96
Alfred,
this indeed matches my experience: There is a continuous stream of exposures from guiding at the requested exposure time exactly up to the point when, after dither, guiding is resumed. This resume triggers a new exposure, which aborts the currently ongoing one:
[2021-06-11T00:19:01.290 CEST INFO ][     org.kde.kstars.ekos.guide] - "Guiding resumed."
[2021-06-11T00:19:01.291 CEST DEBG ][     org.kde.kstars.ekos.guide] - Capturing frame...
[2021-06-11T00:19:01.293 CEST DEBG ][           org.kde.kstars.indi] - ZWO CCD ASI294MC : "[DEBUG] Aborting exposure... "
and the guide module gets that aborted frame, which has only been exposed for a second or so, instead of the requested 4.5s. The time between readouts is basically given by readout time ad processing time. You can see that, e.g., the flux of the brightest star went down from 27902 before the dither to 9532 after dither.

As I mentioned in post #72049, that abort also happened in the 'old' version, but there only once, and after that only one stream of exposure/readouts continues with proper exposure times, whereas now both seem to continue.

Thinking about it, my guess is that the main error is that when an exposure is already going on at the time when a frame capture is requested, the ongoing exposure is aborted, but read out, and then returned as the requested frame, instead of completely dumping it and waiting until the newly triggered frame exposure ends.
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
1 month 2 weeks ago #72256

Please Log in or Create an account to join the conversation.

I believe I found one issue that could contribute to this. Fix pushed to GIT: invent.kde.org/education/kstars/commit/7...a7c317b252fdec560fa9
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
The following user(s) said Thank You: Peter Sütterlin
1 month 2 weeks ago #72258

Please Log in or Create an account to join the conversation.

  • Posts: 745
  • Thank you received: 96
Will compile & test ASAP!
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
1 month 2 weeks ago #72261

Please Log in or Create an account to join the conversation.

  • Posts: 731
  • Thank you received: 114
I spent the night with the intention to test the latest guide module changes but ran into a wall of obstacles that prevented me from guiding. The two most important ones:

1. Star extraction/plate solving did not work as expected

No matter what parameters I entered, plate solving failed complaining there were too few stars in the field while in fact the frames were of good quality and did show many stars you could easily guide on. After a while of unsuccessful attempts to get it working, I changed guide/main camera and used the guide cam for solving. This time it did solve in a second! It did show the same FOV as the main cam before. The quality was not quite as perfect as with the main cam (still good though!) yet plate solving did work flawlessly and quickly. I then reverted to the main cam which again delivered an even better frame but Ekos still complained it was unable to solve.

I then shut down server and client, checked the mount, cams, etc. and started over. This time it was the other way round. The main cam did solve reliably and in no time but the guide cam did not solve, despite same settings, FOV was set correctly for both scopes.

2. Calibration was going nuts and I was unable to rectify the problem all night. It started out as usual, RA drifting forward nicely. The RA backward drift however was exactly in a 90 degrees angle against the forward drift. Of course I checked the usual suspects like RA axis latch, cables, etc. but everything was 100% OK. I tried over and over again but the result remained the same.

 

According to the logfile <:Mgw0500 and <:Mge0500 commands were sent. As you can see in the calibration plot the result was much different from what one would expect. Since I didn't get calibration done, I was unable to test the new guiding code. I'd be glad if someone with a better understanding of the calibration log had a look at the logfile. I'd really like to get a hint as to what went ẃrong since I am afraid I could run into exactly the same problem again. I'll try again tonight but am not too optimistic.

 
Last edit: 1 month 2 weeks ago by Alfred.
1 month 2 weeks ago #72286
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 585
  • Thank you received: 279
Alfred,

Sorry about all the issues. 

Re the plate solving: I see you are using ASTAP. I reported an issue a while back with stellarsolver/ekos & ASTAP where ASTAP expects FOV degrees for the image height, but is being sent the width degrees. This can be worked around by unsetting "Use Scale" or perhaps both unchecking "Use Scale" and "Use Position" in the align options  Scale & Position menu when using ASTAP. You can test on your own as well by using the offline astap program. For instance, on my system astap is installed as /opt/astap/astap. So you can run "/opt/astap/astap -help" to see its options, and, for instance, capture a fits you're having trouble with, and running "/opt/astap/astap -f FILE.fits" to solve it "blind" without scale nor position. You can see the args stellarsolver is sending astap from your log--where it's adding in the scale (that's the -fov 1.36103 in your log) and the position (-ra 19.1981 -spd 75.0158).

Re the calibration: Sorry, no idea. That's the first time I've seen something like that. I'll try and look a little more later. :(

Hy
 
Orion Atlas Pro, William Optics ZS105, Moonlight V2 focuser
ZWO ASI1600, OAG & Filterwheel, Astronomik Filters, QHY 5L-IIm guidecam.
KStars/Ekos/Indi on RPi4 w/SSD
Ekos Projects: Terrain Backgrounds, Polar Alignment, Analyze, Linear Focuser, SEP MultiStar & GPG Guiding, FITS autostretch.
1 month 2 weeks ago #72295

Please Log in or Create an account to join the conversation.

  • Posts: 731
  • Thank you received: 114
Thank you so much for looking into it, Hy! That's good to know. Should I experience problems again tonight, I'll save a couple pictures that fail to solve so I can experiment and sort things out later. Looks like weather will be good so I'll definitely have another try tonight.

I am much better prepared now as I have several KStars/Ekos versions and also two indi servers ready for testing tonight. Hopefully I'll be able to actually guide.
1 month 2 weeks ago #72300

Please Log in or Create an account to join the conversation.

  • Posts: 731
  • Thank you received: 114
Finally I got to guide a few  sequences so I'll leave the logfile for everybody to inspect. I got the solver working with ASTAP and astrometry as well. But calibration was a mess again. I'll write more about it later.
The following user(s) said Thank You: Peter Sütterlin
1 month 2 weeks ago #72320
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 745
  • Thank you received: 96
This looks very promising - at least the "double" captured/aborted frames of the guide cam are gone.

So this is latest git of INDI and kstars?
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
1 month 2 weeks ago #72321

Please Log in or Create an account to join the conversation.

  • Posts: 731
  • Thank you received: 114
Yes, it is.
1 month 2 weeks ago #72327

Please Log in or Create an account to join the conversation.

  • Posts: 745
  • Thank you received: 96
So I finally get a night without clouds and wind, so I tried todays git (both INDI and kstars).

As already expected from Alfreds log, indeed the issue is fixed, i.e., the guiding continues normal after a dither, with correct exposure time.

However, I got already two crashes of kstars which was doing nothing except guiding.  Both times it seems to have started with an exposure timeout:
[2021-06-19T22:11:18.149 WEST INFO ][           org.kde.kstars.indi] - ZWO CCD ASI1600MM Pro :  "[INFO] Taking a 4.5 seconds frame... "
[2021-06-19T22:11:53.013 WEST INFO ][     org.kde.kstars.ekos.guide] - "Exposure timeout. Restarting exposure..."
[2021-06-19T22:11:53.021 WEST WARN ][                       default] - QSqlDatabasePrivate::removeDatabase: connection 'filter_db' is still in use, all queries will cease to work.
[2021-06-19T22:11:53.022 WEST WARN ][                       default] - QSqlDatabasePrivate::addDatabase: duplicate connection name 'filter_db', old connection removed.
[2021-06-19T22:11:53.083 WEST INFO ][           org.kde.kstars.ekos] - "INDI services stopped."
[2021-06-19T22:12:53.024 WEST WARN ][                       default] - QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
[2021-06-19T22:12:53.025 WEST WARN ][                       default] - QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
[2021-06-19T22:12:53.025 WEST WARN ][                       default] - QSocketNotifier: Invalid socket 25 and type 'Read', disabling...
second crash:
[2021-06-19T22:17:01.995 WEST INFO ][           org.kde.kstars.indi] - ZWO CCD ASI1600MM Pro :  "[INFO] Taking a 4.5 seconds frame... "
[2021-06-19T22:17:37.013 WEST INFO ][     org.kde.kstars.ekos.guide] - "Exposure timeout. Restarting exposure..."
[2021-06-19T22:18:37.029 WEST WARN ][                       default] - QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
[2021-06-19T22:18:37.029 WEST WARN ][                       default] - QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
[2021-06-19T22:18:37.030 WEST WARN ][                       default] - QSocketNotifier: Invalid socket 25 and type 'Read', disabling...
Guess I'll revert to an older version for now.
 
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
1 month 1 week ago #72482

Please Log in or Create an account to join the conversation.

Is this on Raspberry PI? If yes, go to Settings --> Configure Notifications and disable all sounds.
Jasem Mutlaq
Support INDI & Ekos; Get StellarMate Astrophotography Gadget.
How to Submit Logs when you have problems?
Add your observatory info
1 month 1 week ago #72485

Please Log in or Create an account to join the conversation.

  • Posts: 745
  • Thank you received: 96
No Pi, a Celeron-based ASUS PN40 for INDI, and a Lenovo i7 Thinkpad for kstars.
Sound notifications in kstars (e.g., align success) do work fine.
openSUSE Tumbleweed KStars git INDI git
GPDX+EQMOD, CEM60EC, ASI2600/1600/290mini+EFW+EAF
1 month 1 week ago #72489

Please Log in or Create an account to join the conversation.

Time to create page: 1.001 seconds