×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

problems with offline solving

  • Posts: 1119
  • Thank you received: 182
OK, so this is the problem: You are using an LX200 reflector, which is an 8"/f10 telescope and a focal length of 8"=200mm x 10 = 2000 mm.

The information in your FITS files, however, shows a focal length of 600 mm and an aperture of 80 mm. Therefore, the solver is trying to solve the image with a 3.33 x mismatched pixel resolution and a 1.33 x mismatched FOV.
No wonder it can't find anything.

Looks like you may have entered your guide scope information instead of your primary telescope information in the respective fields in the Control panel.

Go into the mount tab and enter 200 mm for aperture and 2000 mm for focal length for your primary telescope, then the solver should have no problem completing.

Image #1
SIMPLE = T / file does conform to FITS standard
BITPIX = 8 / number of bits per data pixel
NAXIS = 3 / number of data axes
NAXIS1 = 4365 / length of data axis 1
NAXIS2 = 2912 / length of data axis 2
NAXIS3 = 3 / length of data axis 3
EXTEND = T / FITS dataset may contain extensions
COMMENT FITS (Flexible Image Transport System) format is defined in 'Astronomy
COMMENT and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H
INSTRUME= 'Canon DSLR EOS 5D (normal mode)' / CCD Name
TELESCOP= 'LX200 OnStep' / Telescope name
OBSERVER= 'Unknown ' / Observer name
OBJECT = 'M_51 ' / Object name
EXPTIME = 3.000000E+01 / Total Exposure Time (s)
CCD-TEMP= 0. / CCD Temperature (Celsius)
PIXSIZE1= 8.200000E+00 / Pixel Size 1 (microns)
PIXSIZE2= 8.200000E+00 / Pixel Size 2 (microns)
XBINNING= 1 / Binning factor in width
YBINNING= 1 / Binning factor in height
XPIXSZ = 8.200000E+00 / X binned pixel size in microns
YPIXSZ = 8.200000E+00 / Y binned pixel size in microns
FRAME = 'Light ' / Frame Type
IMAGETYP= 'Light Frame' / Frame Type
FOCALLEN= 6.00E+02 / Focal Length (mm)
APTDIA = 8.00E+01 / Telescope diameter (mm)
FOCUSPOS= 0 / Focus position in steps
SCALE = 2.819433E+00 / arcsecs per pixel
SITELAT = 5.056120E+01 / Latitude of the imaging site in degrees
SITELONG= 6.255970E+00 / Longitude of the imaging site in degrees
AIRMASS = 1.013823E+00 / Airmass
OBJCTRA = '13 29 51.59' / Object J2000 RA in Hours
OBJCTDEC= '47 11 58.27' / Object J2000 DEC in Degrees
RA = 2.024650E+02 / Object J2000 RA in Degrees
3 years 10 months ago #54421

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

  • Posts: 34
  • Thank you received: 2
Hi, that seemed to be the solution... so i changed the spec as you told me... but no solution, then i changed the Fits Header Length and diameter to the LX200 spec... no solution. Then i did erase the hole Header and schwups after 10 sevc i had a positiv solution. So anything in the header is mismatched. Kstars is working with J2020.4 coordinates and fits has J2000 data... may be? where to change the J2020 data?
Matthias
3 years 10 months ago #54422

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

  • Posts: 1957
  • Thank you received: 420

Sorry, I didn’t realize that you put a screenshot there as well. It only shows one tab of the options panel, not all four. Anyway, I see that in the options you have “Use Scale” enabled. Whenever I have solver problems I always disagle that option and in fact by default switch it off now. Can you give that a try?


Wouter
3 years 10 months ago #54426

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

  • Posts: 34
  • Thank you received: 2
ok folks, seems to work now, guess it was the wrong scaling, my fault... thanks again for your pation
Matthias
3 years 10 months ago #54427

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

  • Posts: 1119
  • Thank you received: 182
Scaling would probably be fine, if you had taken the image with the correct camera settings. Just correcting the focal length in the FITS header is not going to make a difference post-hoc, since the wrong scale, i.e. arcsec/pixel, is also written into the FITS header. By deleting the FITS header you forced the solver to do a blind solve, as it has to do with a JPG, which does not contain a FITS header. If you had also changed the scale in the FITS header to the correct one, i.e. divide the arcsec/pixel value by 3.33 (2000mm/600mm), I assume the solver would have completed with the scaling selected as well.
It would be great if you could try that out, for our information. I want to make sure that I understood the problem correctly.
Best
Jo
3 years 10 months ago #54448

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

  • Posts: 34
  • Thank you received: 2
Hi, Jo, yes that works... first i deleted the scaling mark, but then recalculated and the solver did work. So in fact, your hint did its job thanks a lot!
Matthias
3 years 10 months ago #54467

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

Time to create page: 0.225 seconds