×

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

Bi-monthly release with minor bug fixes and improvements

Alignment mystery

  • Posts: 643
  • Thank you received: 62
Hi!

Tonight, I hade a strange problem with the alignment module - first time ever. I was trying to center M81, and repeatedy ordered the mount to slew to it, and the capture, solve and slew to target. However, repeatedy it ended with M81 low in the field. I tried using WCS, clicking on the galaxy core, saying yes to slewing to those coordinates. And still, M81 in the lower part of the image. Finally, I manually, with the handcontrol of the mount, centred M81. And then, doing a capture and sync, and the click on "Show objects in image" I get the green square indicating M81. In the lower part of the image, NOT where it actually is. See attached screendump. Any ideas as to what is going on here? Any settings beeing off, or what might this be?

Magnus
Last edit: 7 years 1 day ago by Magnus Larsson.
7 years 1 day ago #15719
Attachments:

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

  • Posts: 298
  • Thank you received: 46

Replied by Markku on topic Alignment mystery

Hi there..
I've had it like that for a long time now but I never really cared about it but of course it would be nice to have it corrected.
Br
/Markku
7 years 1 day ago #15727
Attachments:

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

  • Posts: 643
  • Thank you received: 62

Replied by Magnus Larsson on topic Alignment mystery

Hi!

Good to hear that it is not just me...:) So how do you cope with it? My main problem with it is that it is that I cannot depend on the scheduler to slew to a specific object and center on it. This situation demands manual intervention...right?

Magnus
7 years 1 day ago #15728

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

Replied by Jasem Mutlaq on topic Alignment mystery

1. Can you provide a link to the FITS image captured above for M81?
2. Are both of you using LX200Gemini? or different mounts? With LX200Gemini, I asked you recently to change the sensativity so that it reports slew is complete. I believe this has an effect here. At any rate, I need to know if we can use the command set here: www.gemini-2.com/web/serial_commands.html
7 years 1 day ago #15738

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

  • Posts: 643
  • Thank you received: 62

Replied by Magnus Larsson on topic Alignment mystery

Hi!

The fits image:
www.dropbox.com/sh/fs744ujp8oed79d/AACfn...E98N8km8Tv2dUBa?dl=0

Yes, LX200Gemini driver.

And yes, the "slew complete" settings are at play here. Based on your advice two days ago, I set it to 11, and that worked nicely. Howevr, yesterday, imaging M81, it didn't work. I had to increase it to 20 or even more to be able to complete a slew. I don't have the logfile, though.

(I hope the driver information answers your question about the command set?)

Magnus
7 years 1 day ago #15739

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

Replied by Jasem Mutlaq on topic Alignment mystery

Please check Google chat, it's faster than here.
7 years 1 day ago #15740

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

  • Posts: 298
  • Thank you received: 46

Replied by Markku on topic Alignment mystery

I just checked the fitsheader and it seems like the green square is at correct place, and I also checked with Stellarium and it is indeed correct.
I'm using a EQ8.
************
Image #1
SIMPLE = T / file does conform to FITS standard
BITPIX = 16 / number of bits per data pixel
NAXIS = 2 / number of data axes
NAXIS1 = 1392 / length of data axis 1
NAXIS2 = 1040 / length of data axis 2
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
BZERO = 32768 / offset data range to that of unsigned short
BSCALE = 1 / default scaling factor
INSTRUME= 'SX CCD SXVR-H9' / CCD Name
TELESCOP= 'EQMod Mount' / Telescope name
OBSERVER= 'Markku Siitonen' / Observer name
OBJECT = 'Unknown ' / Object name
EXPTIME = 60. / Total Exposure Time (s)
CCD-TEMP= 8.3 / CCD Temperature (Celcius)
PIXSIZE1= 6.44921875 / Pixel Size 1 (microns)
PIXSIZE2= 6.44921875 / Pixel Size 2 (microns)
XBINNING= 1 / Binning factor in width
YBINNING= 1 / Binning factor in height
FRAME = 'Light ' / Frame Type
FILTER = 'UVIR ' / Filter name
FOCALLEN= 1507. / Focal Length (mm)
OBJCTRA = '14 16 15.65' / Object RA
OBJCTDEC= '19 06 31.19' / Object DEC
EQUINOX = 2000 / Equinox
CRVAL1 = 214.065215632326 / CRVAL1
CRVAL2 = 19.1086629455481 / CRVAL1
RADECSYS= 'FK5 ' / RADECSYS
CTYPE1 = 'RA---TAN' / CTYPE1
CTYPE2 = 'DEC--TAN' / CTYPE2
CRPIX1 = 696. / CRPIX1
CRPIX2 = 520. / CRPIX2
SECPIX1 = 0.882862526957532 / SECPIX1
SECPIX2 = 0.882862526957532 / SECPIX2
CDELT1 = 0.000245239590821537 / CDELT1
CDELT2 = 0.000245239590821537 / CDELT2
CROTA1 = 183.3 / CROTA1
CROTA2 = 183.3 / CROTA2
DATE-OBS= '2017-03-27T19:57:17.278' / UTC start date of observation
COMMENT Generated by INDI
DATAMIN = 1460. / Minimum value
DATAMAX = 65535. / Maximum value
DATE = '2017-03-27T19:58:55' / file creation date (YYYY-MM-DDThh:mm:ss UT)
HISTORY Modified by KStars on 2017-03-27T21:58:55
***************

I did a platesolving near Arcturus so I don't know why it is off by so much.
Just remove the .txt extension to get a .fits
7 years 1 day ago #15742
Attachments:

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

Time to create page: 0.427 seconds