Hello,
Yesterday the night was clear, so this was my 4th night of imaging in a week.
As I was with some friends on the field doing shots and observing with our dobsons I did not try a complicated target.
So I imaged the double cluster of Perseus.
After polar alignment that was hard to do due to the problem I met with unsynchronised mount stop and capture I targeted to the bigger of the two clusters.
I shot an image and using the fitswiewer I clicked and moved the telescope to the middle of the two clusters.
I started a session of 50 captures. After a while for some unexpected reasons, the capture session stopped.
I decided to resume the session. So to clear the system, I stopped INDI and kstars and rerun them.
In between the target has moved. After an astrometry sync and pointing the telescope roughly to the place it was pointing previously I decided to make a load and slew to the target with a previous capture.
All the attempts failed. I decided to do it by myself entering the RA and Dec coordinates that I can find in the fit header of a previous capture.
I have done that with the virtual handpad. Follows a goto to the required place. To my surprise, on the map the telescope pointed close to the biggest cluster and not between the two ones.
I was thinking that it could be just a problem of display. I shot one image and... yes the telescope pointed in the wrong place.
I adjusted the place by iterating between captures and move of the scope to have an approximative equivalent framing as first session's part.
An hypothesis : after a click and move on the fitsviewer, it looks like the new position is not written in the header of the image .
Joined the logs of the whole night.
Is it normal ?
I've had the load and slew problem for a while now. My workaround is to add a flag in kstars and use that as the target for the scheduler. Its quick and easy. You can return night after night to those flags. Also, I tend to enjoy using the "DSS Colored" HiPS overlay. It really helps framing an object.
I guess that the coordinates recorded in the center of the fits image and the image used for astrometry are inconsistent and may produce those astrometry problems in some conditions. However what you mean with "flag in kstars" ?
Right clicking anywhere on the planetarium display in kstars will give you an option to add a flag. Label it and then anytime you want to reference the RA and DEC, you will have it. Clicking under "tools" will give you a way to access all your flags organized. Copy-paste the RA and DEC coordinates into the scheduler or into the alignment tab should give you repeatable results.
Do you have the WCS enabled for your main imaging camera in its driver tab in the indi control panel?
I realize this is an older thread, but I just started having a similar issue. What I've realized, in my case, that the solver fails both via the CLI and via ekos when there is a parenthesis in the filename or path. Perhaps you all are having a similar issue?
Some logs here:
CLI:
/usr/bin/solve-field -O --no-plots --no-verify --resort --downsample 2 -397.9257 -44.95925 -515 -L 1.07396 -H 1.31261 -u app --config /home/mike/.local/share/kstars/astrometry/astrometry.cfg -W /tmp/solution.wcs '/media/Storage/Astrophotography/Incoming/NGC 2238(Rosette Nebula)/Light/OIII/NGC 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits'
Reading input file 1 of 1: "/media/Storage/Astrophotography/Incoming/NGC 2238(Rosette Nebula)/Light/OIII/NGC 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits"...
Extracting sources...
augment-xylist.c:941:augment_xylist Source extraction failed
image2xy-files.c:47:image2xy_files Failed to open FITS input file /media/Storage/Astrophotography/Incoming/NGC 2238(Rosette Nebula)/Light/OIII/NGC 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits
../util/cfitsutils.h:26:cfitserr could not open the named file
../util/cfitsutils.h:26:cfitserr failed to find or open the following file: (ffopen)
../util/cfitsutils.h:26:cfitserr /media/Storage/Astrophotography/Incoming/NGC 2238(Rosette Nebula)/Light/OIII/NG
../util/cfitsutils.h:26:cfitserr C 2239_Light_OIII_600_secs_2019-03-22T00-28-26_001.fits
I believe astrometry.net does not like either spaces or parenthesis in file names. Can you try it with a simple file name? /home/mike/Desktop/foo.fits ?
I can confirm it works fine without the parenthesis. Spaces seem to be OK in the path as well. I was posting more as an informational post to the original poster rather than looking for a big fix.
Also, thanks to you and the team for a great product!