|
Re: Close up of M81 without CCDT67
Bill Long
You can still get the circle pattern while they are in stock:
From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Robert Chozick via Groups.Io <rchozick@...>
Sent: Monday, February 24, 2020 12:54 PM To: main@ap-gto.groups.io <main@ap-gto.groups.io> Subject: Re: [ap-gto] Close up of M81 without CCDT67 Wayne did you also adjust the primary? Do you have an attachment to project a grid or circle on the wall? I bought a focuser tilt adjustment ring so I could do the full laser collimation procedure -all 3 parts. My Howie Glatter laser has
the grid attachment but they no longer make the circle projection attachment. You can make the grid attachment work ok.
Robert
On Feb 24, 2020, at 2:26 PM, Wayne Hixson via Groups.Io <wayneh9026@...> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
Robert Chozick <rchozick@...>
Wayne did you also adjust the primary? Do you have an attachment to project a grid or circle on the wall? I bought a focuser tilt adjustment ring so I could do the full laser collimation procedure -all 3 parts. My Howie Glatter laser has the grid attachment but they no longer make the circle projection attachment. You can make the grid attachment work ok.
toggle quoted messageShow quoted text
Robert
On Feb 24, 2020, at 2:26 PM, Wayne Hixson via Groups.Io <wayneh9026@...> wrote:
|
|
|
|
Re: Close up of M81 without CCDT67
Bill Long
We'll see if my recent tip tilt adjustment solves my issues, once it clears here. That may have been the problem the whole time.
From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Wayne Hixson via Groups.Io <wayneh9026@...>
Sent: Monday, February 24, 2020 12:26 PM To: main@ap-gto.groups.io <main@ap-gto.groups.io> Subject: Re: [ap-gto] Close up of M81 without CCDT67 Hi Bill, I just checked my AGO 12.5” iDK with laser collimator and Tak scope yesterday. Following Dave Tandy’s collimating video, things looked good to my eye. Beam was within the center target of the secondary and beam return to the primary was overlapping
the beam source, sort of like a very close double star. Tak scope pattern looked like it was supposed to. Waiting now to check out under the stars. Wondering what issues you ran into?
|
|
|
|
Re: Close up of M81 without CCDT67
Wayne Hixson
Hi Bill, I just checked my AGO 12.5” iDK with laser collimator and Tak scope yesterday. Following Dave Tandy’s collimating video, things looked good to my eye. Beam was within the center target of the secondary and beam return to the primary was overlapping the beam source, sort of like a very close double star. Tak scope pattern looked like it was supposed to. Waiting now to check out under the stars. Wondering what issues you ran into?
|
|
|
|
Re: Apparent loss of tracking after dither command
Roland Christen
It appears that RA is oscillating quite a bit. Possible reasons:
1) wrong calibration values - highly likely
2) mount is not balanced in RA - somewhat likely
Unfortunately your graph doesn't show the guide corrections which might help determining the cause. I would run Guide Assistant, there is a lot of information generated which will help you in your settings. The RA axis should not oscillate, unless the calibration values are way wrong for that part of the sky. It's happened to me when I fed the wrong focal length and pixel scale info to the guide program and had wild oscillations that did not go away until i reduced the aggressiveness to 10%. That was the clue that I had entered something wrong.
Rolando
-----Original Message-----
From: Peter Bresler via Groups.Io <PABresler@...> To: main <main@ap-gto.groups.io> Sent: Mon, Feb 24, 2020 11:35 am Subject: Re: [ap-gto] Apparent loss of tracking after dither command There were problems with retaining the guide scar, although guiding had been working for quite a while. In any case I expect that the mount would keep tracking, but that did fail. When I turned off dither and recentered with a plate solve things were ok.
|
|
|
|
Re: Apparent loss of tracking after dither command
Dale Ghent
Assuming that the screenshot you provided was taken right after the erroneous event, the reason why guiding stopped in plainly-stated: Something external to PHD2 commanded the mount to slew while PHD2 was still guiding. In such a case, PHD2 will stop guiding and post a complaint.
toggle quoted messageShow quoted text
You mentioned that you turned dithering on in SGP. Dithering is an operation that's normally handled by PHD2 - the sequencing application pauses between exposures, and through its direct connection to PHD2, orders PHD2 to begin a dither operation using either the provided parameters or PHD2's defaults. PHD2 executes this by sending pulse guide commands to the mount to move the field of view a few pixels in a random direction, then reacquires the guide star and resumes guiding. The sequence application observes through its direct connection to PHD2 that the dither op is completed, then starts the next exposure. I don't know if this option is in SGP, but there is a "manual dither" feature that's common in sequencing apps, typically employed when there is no guide camera and no guiding app such as PHD2 operating, such as with an unguided setup. In such a case, it is the sequence application that tells the mount to move a little to effect the dither. Could it be that you have this feature on in SGP, and thus SGP is not coordinating the dithers through PHD2 at all? If this were the case, PHD2 would then see the guide star and mount move unexpectedly and produce the error you see in the screenshot you provided. This could be one possible explanation. You didn't explain if you have had previous dither operations execute and succeed during your sequence. Doing your first dither 18 shots into a sequence is pretty late in the game to start doing it as, like I said, one normally sets up dithering to happen every 1-5 shots and no less frequent than that. I would take Brian's advice and take this up on either the PHD2 or SGP forums.
On Feb 24, 2020, at 12:35 PM, Peter Bresler via Groups.Io <PABresler=aol.com@groups.io> wrote:
|
|
|
|
Re: Apparent loss of tracking after dither command
if you slew, guiding will stop. that's what it looks like happened here from your screen shot, but again you can get more details at PHD forums if you want to investigate further
On Mon, Feb 24, 2020 at 9:35 AM Peter Bresler via Groups.Io <PABresler=aol.com@groups.io> wrote: There were problems with retaining the guide scar, although guiding had been working for quite a while. In any case I expect that the mount would keep tracking, but that did fail. When I turned off dither and recentered with a plate solve things were ok. --
|
|
|
|
Re: Apparent loss of tracking after dither command
There were problems with retaining the guide scar, although guiding had been working for quite a while. In any case I expect that the mount would keep tracking, but that did fail. When I turned off dither and recentered with a plate solve things were ok.
|
|
|
|
Re: Notified!😍 #mach2gto
#Mach2GTO
https://ap-gto.groups.io/g/main/topic/upgrade_to_new_keypad_version/69318928?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,60,69318928
Must be used with GTOCP4 or GTOCP5 (CP5 is for Mach2GTO only). This is due to the more advanced command language and pointing precision that is only available in these control boxes. The software of the GTOCP4 itself will have to be updated, which can be done online. We will have more information regarding the downloadable upgrade when the time comes.
|
|
|
|
Re: Notified!😍 #mach2gto
#Mach2GTO
Wayne Hixson
I meant Marj! Darn autocorrect!!
|
|
|
|
Re: Notified!😍 #mach2gto
#Mach2GTO
Wayne Hixson
Thanks Mark! So to be sure I understand, my friend who bought my AP1100 will be able to update his GTOCP4 with all these goodies too?
toggle quoted messageShow quoted text
Thanks, Wayne
On Feb 22, 2020, at 1:10 PM, Marj Christen <marj@...> wrote:
|
|
|
|
Re: Apparent loss of tracking after dither command
Hi Peter your best bet to track this down is to head over to the PHD forums and post your guidelog there with the above explanation. That can be hunted down pretty quickly. My guess is it's unrelated to the dither, but the guidelogs will tell (FYI guidelogs are automatically captured for you)
On Sun, Feb 23, 2020 at 11:58 PM Peter Bresler via Groups.Io <PABresler=aol.com@groups.io> wrote: I was shooting with SGP and PHD2; things seemed to be going well for about 18 4 minute exposures. I had selected "dither" for PHD2. On the 19th shot after the dither signal the mount started drifting badly and I had to stop the sequence. Same thing happened again when I restarted, but after I recentered and unchecked dither things went well again with good guiding. What is going on? --
|
|
|
|
Re: Close up of M81 without CCDT67
J. Belden
Rolando,
Yes, I love my AP1600 and it just handles anything I put on it and I doubt that I will have a need to get close to weight rating because I still need to handle the OTA to setup each night. But, let me know if your plan on making any of the 17" OTA, I'd put my name in the hat/list. Joe
|
|
|
|
Re: Notified!😍 #mach2gto
#Mach2GTO
Luke Leege
Looking forward to the update when it becomes available.
|
|
|
|
Re: Apparent loss of tracking after dither command
Dale Ghent
It’s hard to say what happened with such a superficial description. Did PHD2 start complaining about the loss of lock on the guide star? It would have been flashing its UI and displaying a warning to that effect. Did prior dither operations succeed? Usually one dithers every 1 to 5, at most, exposures so there should have been a few dithers happening somewhere in between those prior shots... dithers that I presume went off without a hitch? The key and basic thing to know here is whether PHD2 lost its guide star or not, an event that it gripes loudly about.
On Feb 24, 2020, at 02:58, Peter Bresler via Groups.Io <PABresler@...> wrote:
|
|
|
|
Apparent loss of tracking after dither command
I was shooting with SGP and PHD2; things seemed to be going well for about 18 4 minute exposures. I had selected "dither" for PHD2. On the 19th shot after the dither signal the mount started drifting badly and I had to stop the sequence. Same thing happened again when I restarted, but after I recentered and unchecked dither things went well again with good guiding. What is going on?
|
|
|
|
Re: Error when running PEMPro V3
Ray Gralak
That's maybe too broad of a range for a DSLR.
toggle quoted messageShow quoted text
You should look at the brightness of stars in one of your raw images and select a range that is representative of stars that are not saturated. -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro V3: https://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
-----Original Message-----
|
|
|
|
Re: Error when running PEMPro V3
Worsel
Thanks for the help, Ray.
Canon 6D DSLR via SGPro. Min = 1000 (the default, I believe) Max = 100000 (also default) Bryan
|
|
|
|
Re: Error when running PEMPro V3
Ray Gralak
Bryan,
toggle quoted messageShow quoted text
Let's start with the basics. What camera are you using and what Min and Max star brightness values do you have configured in PEMPro? -Ray Gralak Author of APCC (Astro-Physics Command Center): http://www.astro-physics.com/index.htm?products/accessories/software/apcc/apcc Author of PEMPro V3: https://www.ccdware.com Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
-----Original Message-----
|
|
|
|
Error when running PEMPro V3
Worsel
I want to refresh my PE curve in PEMPro. The calibration wizard executes without issue (PEMPro V3 and SGP). When I Start the PEMPro run, I get the error "The brightest star is too close to the edge. Re-center the star closer to the center."
1. There are several bright stars scattered across the field. None are 'close' to the edge. 2. Regardless of what I do to re-center ANY bright star, the same errors continues. What do I need to do to execute a PEMPro run? Bryan
|
|
|