|
Re: Looking for Suggestions to Cause of Image Anomoly
On 6/30/2019 9:06 AM, mike.hambrick@... [ap-gto] wrote:
I don't think this is a guiding, periodic error, or flexure issue.Well, that pretty-much rules out the main suspects. <GRIN> It's very hard to see much in an 800px-wide image. I can't even zoom-in without the small stars becoming pixelated. Can you crop a few stars with the anomaly from one exposure, and post that for a better view of the problem? Also, the image would be easier to analyze if you'd subtract a dark frame before cropping. To me, it looks like a guiding issue -- as if the mount didn't respond to a few seconds of guider corrections during each 60-second exposure. IOW, the the guide star drifted, but the guider (a) didn't detect it and issue a correction or (b) the guider did issue a correction, but the mount didn't respond. Flexure generally results in smeared stars. A small blip indicates (to me, at least) a short period of time where the guider wasn't correcting. Here are some questions and suggestions: 1. Is the anomaly on the RA or Dec axis? If on Dec, that could indicate a Dec balance problem. Normally The Dec doesn't change as the target tracks across the sky. But maybe the autoguider issued a correction that shifted the guide star, and then the guider quickly issued a second correction to bring it back. 2. What does your guider's tracking error graph or log look like? Do you see any brief spikes and corrections that could explain the anomaly? 3. Is it possible that the main camera was still downloading a large image after it began the next exposure? If so, maybe the guide camera was prevented from downloading an image during this time. 3a. One way to check is to define a small subframe on the main camera surrounding only a few stars (including the bright one toward the left). Use the same 60s exposure, and guide normally. If the anomaly is gone, that points strongly to a USB data overload during the full image download. 3b. Or was your computer doing something that prevented the guider from responding to a guiding error? Any CPU-intensive operation could stall the guider briefly. To me, it's suspicious that the anomaly occurred on EVERY exposure. What's the computer doing immediately after downloading data from the main camera? 4. Do these anomalies occur with shorter (e.g., 15s or 30s) guided exposures? If so, see #3 above. 5. Do the anomalies occur with 60s UNGUIDED exposures? Your AP1100 should be capable of good tracking over 60 seconds if it's accurately polar-aligned. If polar alignment isn't good, stars will be smeared on the RA axis. 5a. But (AHA!) if the stars ARE smeared in the unguided exposure, that strongly points to a guider issue. Your mount is drifting but the autoguider is not always correcting for the drift. That's all I can think of at the moment. hope this helps. -- Mike Mike Dodd Louisa County, Virginia USA http://astronomy.mdodd.com
|
|
|
|
Mach1GTO bad goto's w/ SkySafari
Dan
Long story short I decided to take my Mach1 out with my C8 for an outreach event. I connected via WIFI w/ SkySafari 6 Pro in my iPhone. I did not get a perfect polar alignment. I knew Polaris was over a specific tree and lined up to it.
|
|
|
|
Looking for Suggestions to Cause of Image Anomoly
mike.hambrick@...
Hi to all I am looking for some suggestions what might be causing the blip in the stars that you can see in the attached image. This is a 60 second sub frame of M101 taken with a 180 EDT with 27TVPH reducer and a SBIG STXL16200 / FW8G-STXL camera / filter wheel on a A-P 1100 GTO mount (no encoders). I was using a piggybacked 76 mm guide scope with a ST-I camera for guiding using CCDOPS I don't think this is a guiding, periodic error, or flexure issue. The exact same thing is seen in all of the sub-frames I took (60 total) through different filters (L,R, G, and B). I have not seen this anomaly on images taken with my 100 mm scope. Also, for whatever it's worth, there is a slight rattle in the 27TVPH which I was told a while back is not uncommon. Any suggestions would be appreciated. Here is the link:
|
|
|
|
New file uploaded to ap-gto
ap-gto@...
Hello,
This email message is a notification to let you know that a file has been uploaded to the Files area of the ap-gto group. File : /mchambrick/M101 Image Anomoly.jpg Uploaded by : mchambrick <mike.hambrick@...> Description : M101 Image Anomoly You can access this file at the URL: https://groups.yahoo.com/neo/groups/ap-gto/files/mchambrick/M101%20Image%20Anomoly.jpg To learn more about file sharing for your group, please visit: https://help.yahoo.com/kb/index?page=content&y=PROD_GRPS&locale=en_US&id=SLN15398 Regards, mchambrick <mike.hambrick@...>
|
|
|
|
Counterweight shaft lengths?
Jeffc
Did AP change the 1.875” counterweight shaft lengths (over the past few years)?
I have an ~ 18.5” shaft from a 2005 AP1200 And an ~ 13” shaft from a (?) 2012 AP1100. Here’s a picture of the two shafts: https://drive.google.com/file/d/1Tml9DiiO346yie5016FyeJk069nngpXS/view?usp=drivesdk I’m planning on using the longer shaft on the AP1100 to reduce needed counterweights. Shouldn’t be a problem, correct? It seems the current (2019) AP1100 comes with a 16” shaft. Optional shafts are 9.25” and 22”. Is this correct, or am I missing something? Presumably AP has optimized the length at 16”. Which to be honest makes sense; I could use a shorter shaft on the AP1200 but 13” is I think too short for my usage. Thx -jeff
|
|
|
|
Re: ASCOM guiding
On 6/29/2019 9:49 PM, 'Yves Laroche' yves.laroche@... [ap-gto] wrote:
When connecting MaximDL directly to the telescope driver, some MaxImDLThank you for the clarification. I'm using ASCOM Direct in MaxIm only for autoguiding, and not connecting directly to the telescope driver, so I'm happy to hear that will not interfere with ACP. --- Mike
|
|
|
|
Re: ASCOM guiding
Yves Laroche
|
|
|
|
Re: ASCOM guiding
Ross Salinger <rgsalinger@...>
Two quick points. I had Bob Denny on the phone literally yesterday and we talked about NOT connecting MaximDL to the AP driver when using ACP. It's also in the "manual". Second, I am positive that he also said to use ASCOM direct when guiding THROUGH MaximDL
under ACP control and to use Telescope when not using ACP. I'm sure, though, from experience, that both settings can be made to work when operating stand alone.
That to me is the only mystery - exactly how they differ. I thought that if you used ASCOM direct, then not all of the MDL parameters are being used to calculate what gets sent to the mount driver. The MDL manual isn't very clear on this at all. It's on page 471 and I've read it ten times and I still can't suss out the exact meaning. Rgrds-Ross
On 6/29/2019 5:12 PM, 'Steven Reilly'
sreilly24590@... [ap-gto] wrote:
|
|
|
|
Re: ASCOM guiding
Steve Reilly
The connection in MaxIm isn’t the same as setting MaxIm to connect to the telescope just the same as guiding with the relays doesn’t connect to the mount. The communication with MaxIm is guider info for the mount either way just different methods.
-Steve
From: ap-gto@...
Sent: Saturday, June 29, 2019 7:59 PM To: ap-gto@... Subject: [ap-gto] Re: ASCOM guiding
On 6/29/2019 7:10 PM, Yves Laroche yves.laroche@... [ap-gto] wrote:
|
|
|
|
Re: ASCOM guiding
On 6/29/2019 7:10 PM, Yves Laroche yves.laroche@... [ap-gto] wrote:
Normally ACP uses Maxim to autoguide. Maxim is not autoguiding inLet me clarify: I set MaxIm to use ASCOM Direct to guide using "pulse guiding." I chose the "Astro Physics GTO V2 Mount" ASCOM driver. I then calibrated the guider and tested guiding standalone MaxIm. Next I launched ACP connected the telescope and camera, and started an imaging plan. ACP found a guide star and started guiding as it always does. At no time did I "connect" to the mount in MaxIm. However, Maxim somehow established a connection to the mount so it can issue guiding corrections via ASCOM. According to Bob Denny, MaxIm DOES connect to the mount. I don't know this all works, but it DOES work. --- Mike
|
|
|
|
Re: ASCOM guiding
Yves Laroche
Normally ACP uses Maxim to autoguide. Maxim is not autoguiding in standalone mode as you should do if ACP was not present. Unless something has changed in ACP v8, you should avoid connecting Maxim to the telescope when using ACP My two cents... Yves
|
|
|
|
Re: ASCOM guiding
On 6/29/2019 6:04 PM, Yves Laroche yves.laroche@... [ap-gto] wrote:
Ummm.... Two nights ago MaxIm was autoguiding using ASCOM Direct with the A-P GTO Telescope driver while ACP was connected to the mount. Bob told me just last week that MaxIm connects to the mount itself. Am I mising something? --- Mike
|
|
|
|
Re: ASCOM guiding
Yves Laroche
Of course Mike but don't connect Maxim to the telescope when using ACP . Bob Denny already mentionned this several years ago. Yves
Le 29 juin 2019 17 h 53, "Mike Dodd mike@... [ap-gto]" <ap-gto@...> a écrit :
|
|
|
|
Re: ASCOM guiding
On 6/29/2019 5:48 PM, Yves Laroche yves.laroche@... [ap-gto] wrote:
You can also connect TheSkyX directly to the AP ASCOM Driver. ThisGreat news, thanks! I assume ACP will also connect to the mount if SkyX and MaxIm are connected to it with this driver. Yes? --- Mike
|
|
|
|
Re: ASCOM guiding
Yves Laroche
Mike, You can also connect TheSkyX directly to the AP ASCOM Driver. This driver works the same as a hub. Yves
Le 29 juin 2019 17 h 38, "Mike Dodd mike@... [ap-gto]" <ap-gto@...> a écrit :
|
|
|
|
Re: ASCOM guiding
On 6/29/2019 3:08 PM, Ross Salinger rgsalinger@... [ap-gto] wrote:
Note also that there is an ACP telescope hub that you can connect theAbsolutely. I had that configuration with Sky6 before 2010 when we moved to a new house. I plan to do the same thing with SkyX soon in the new observatory. I only recently got everything playing happily together, so next I'll add SkyX connecting via the ACP telescope hub. It's really nice to SEE where ACP is imaging. :-) -- Mike Mike Dodd Louisa County, Virginia USA http://astronomy.mdodd.com
|
|
|
|
Re: ASCOM guiding
Mike Shade
Thanks for the info...I am using Sky 6, NOT SkyX...same apply?
Mike J. Shade: mshade@q.com Mike J. Shade Photography: mshadephotography.com In War: Resolution In Defeat: Defiance In Victory: Magnanimity In Peace: Goodwill Sir Winston Churchill Already, in the gathering dusk, a few of the stars are turning on their lights. Vega, the brightest one, is now dropping towards the west. Can it be half a year since I watched her April rising in the east? Low in the southwest Antares blinks a sad farwell to fall... Leslie Peltier, Starlight Nights International Dark Sky Association: <http://www.darksky.org/> www.darksky.org From: ap-gto@... [mailto:ap-gto@...] Sent: Saturday, June 29, 2019 12:08 PM To: ap-gto@... Subject: Re: [ap-gto] Re: ASCOM guiding The AP driver is the only choice that will work. That SKYX driver is used when you are connecting something in addition to the SKYX to a Paramount. When using ACP, the correct Guiding Via choice is Ascom Direct. When not using ACP the correct choice, when not using an ST4 cable is Telescope. Note also that there is an ACP telescope hub that you can connect the SKYX to. I use it along with ACP on an AP1600 that I just got access to about a week ago. That makes the SKYX a great Planetarium program while allowing you to have ACP controlling things as well. At least this works for me. Rgrds-Ross On 6/29/2019 11:40 AM, Mike Dodd mike@... [ap-gto] wrote: On 6/29/2019 1:53 PM, Mike Dodd mike@... [ap-gto] wrote: 4. Choose the appropriate ASCOM driver for your mount.I noticed after I posted my reply that you're using ACP, as do I. I did NOT select the "ACP ASCOM telescope hub" or whatever it's called. I DID choose "Astro Physics ASCOM driver" or something similar. I am told that MaxIm connects to the mount, so if you want to do that without ACP running, you can't use the ACP ASCOM hub. Once I made my selection, MaxIm found the mount and calibrated/guided correctly without ACP running. And.... Even though I have TheSkyX and have connected my AP1200 mount to it, I did NOT choose the SkyX ASCOM driver, if that even appeared in the list. The A-P driver looked like the best choice for Maxim to connect without other programs running, and that proved correct. --- Mike [Non-text portions of this message have been removed]
|
|
|
|
Re: ASCOM guiding
Ross Salinger <rgsalinger@...>
The AP driver is the only choice that will work. That SKYX driver is used when you are connecting something in addition to the SKYX to a Paramount. When using ACP, the correct Guiding Via choice is Ascom Direct. When not using ACP the correct choice, when not using an ST4 cable is Telescope. Note also that there is an ACP telescope hub that you can connect the SKYX to. I use it along with ACP on an AP1600 that I just got access to about a week ago. That makes the SKYX a great Planetarium program while allowing you to have ACP controlling things as well. At least this works for me. Rgrds-Ross
On 6/29/2019 11:40 AM, Mike Dodd
mike@... [ap-gto] wrote:
|
|
|
|
Re: ASCOM guiding
On 6/29/2019 1:53 PM, Mike Dodd mike@... [ap-gto] wrote:
4. Choose the appropriate ASCOM driver for your mount.I noticed after I posted my reply that you're using ACP, as do I. I did NOT select the "ACP ASCOM telescope hub" or whatever it's called. I DID choose "Astro Physics ASCOM driver" or something similar. I am told that MaxIm connects to the mount, so if you want to do that without ACP running, you can't use the ACP ASCOM hub. Once I made my selection, MaxIm found the mount and calibrated/guided correctly without ACP running. And.... Even though I have TheSkyX and have connected my AP1200 mount to it, I did NOT choose the SkyX ASCOM driver, if that even appeared in the list. The A-P driver looked like the best choice for Maxim to connect without other programs running, and that proved correct. --- Mike
|
|
|
|
Re: ASCOM guiding
On 6/29/2019 1:34 PM, 'Mike Shade' mshade@q.com [ap-gto] wrote:
I just did that, so I'll throw out what I learned. 1. Disconnect the ST-4 cable from your guide camera to the mount. 2. In MaxIm's Guide tab -> Settings -> Control Via, choose ASCOM Direct. 3. Below that, next to the grayed-out COM port, click the Setup button to bring up the ASCOM chooser. 4. Choose the appropriate ASCOM driver for your mount. 5. Click the Properties button to check/verify the driver's settings, then close that Dialog. 6. Click the OK button on the Chooser dialog. 7. Slew to a bright star and take a guider image to confirm it's in the FOV. 8. Enter the star's Dec in the MaxIm Guide tab. 9. Click the star's centroid and click Calibrate in MaxIm. You should get the expected L-curve. 10. Take another guider image, click the star's centroid, then click Track in MaxIm. Open the guide error graph to see how well autoguiding is working. That's it. It worked great for me. -- Mike Mike Dodd Louisa County, Virginia USA http://astronomy.mdodd.com
|
|
|