Please disable Synchronous Pulse Guide in ASCOM Driver warning vs APCC
Peter Gottstein
Bruce Waddington
Hi Peter. I’ll be happy to work through this with you but we need to go about it systematically and focus on your specific results. I’m currently on a driving trip for several days so I will only be able to respond to things at night when I’m in a hotel.
The advisory message you’ve seen (once per night at most) is probably irrelevant to your setup and should be ignored. The message should probably be reworded to say “if you are using synchronous pulse-guiding, you should disable it…”. If you know that doesn’t apply to you, just click on the ‘don’t show this message again’ option and forget about it. This isn’t having any effect on the guiding in the two logs you sent, so let’s set that topic aside and move on.
In the two logs you sent – one for 01/26 and one for 01/28 – I can’t find any cases where “the guiding went crazy”. In fact, the guiding sequences are quite consistent with only a single anomaly and you should have been getting round stars in your images with only this single exception. That anomaly occurred at 20:28 on 01/28 and looked like this:
Red is RA, green is Dec. This was not caused by guiding, there were no guide pulses issued at the start of this large excursion. The only guide pulses occurred after the fact in order to restore the guide star to the lock position. This is also unlikely to have come from the mount itself. This happened only a few minutes before the scope reached the central meridian so there’s a good possibility it was caused by a cable snag of some kind. Are you using an off-axis-guider with your setup or a separate guide scope? Even with through-the-mount cabling, you aren’t immune to cable routing problems and these sorts of things are pretty common. It’s also possible you encountered a wind gust or something else that jostled the scope around, there’s no way to tell – but it wasn’t guiding. And as I said, this was the only tracking or guiding anomaly I could see in the two nights of imaging. So if you think that something is more seriously wrong than this, you will need to be specific about the time and date when the problems occurred and be sure you are uploading log files that cover those periods. I don’t know if you’re judging things by looking at the real-time graph or by analyzing the log after the fact. But don’t get confused by large guide star excursions that are the result of dithering, those are entirely normal and are identified as such in either the real-time graph or the PHD2 Log Viewer.
Regards,
Bruce
--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/68536dc7-4ab6-4443-b11a-4742bffd08b8n%40googlegroups.com.
Peter Gottstein
Hi Peter. I’ll be happy to work through this with you but we need to go about it systematically and focus on your specific results. I’m currently on a driving trip for several days so I will only be able to respond to things at night when I’m in a hotel.
The advisory message you’ve seen (once per night at most) is probably irrelevant to your setup and should be ignored. The message should probably be reworded to say “if you are using synchronous pulse-guiding, you should disable it…”. If you know that doesn’t apply to you, just click on the ‘don’t show this message again’ option and forget about it. This isn’t having any effect on the guiding in the two logs you sent, so let’s set that topic aside and move on.
In the two logs you sent – one for 01/26 and one for 01/28 – I can’t find any cases where “the guiding went crazy”. In fact, the guiding sequences are quite consistent with only a single anomaly and you should have been getting round stars in your images with only this single exception. That anomaly occurred at 20:28 on 01/28 and looked like this:
<image002.jpg>
Red is RA, green is Dec. This was not caused by guiding, there were no guide pulses issued at the start of this large excursion. The only guide pulses occurred after the fact in order to restore the guide star to the lock position. This is also unlikely to have come from the mount itself. This happened only a few minutes before the scope reached the central meridian so there’s a good possibility it was caused by a cable snag of some kind. Are you using an off-axis-guider with your setup or a separate guide scope? Even with through-the-mount cabling, you aren’t immune to cable routing problems and these sorts of things are pretty common. It’s also possible you encountered a wind gust or something else that jostled the scope around, there’s no way to tell – but it wasn’t guiding. And as I said, this was the only tracking or guiding anomaly I could see in the two nights of imaging. So if you think that something is more seriously wrong than this, you will need to be specific about the time and date when the problems occurred and be sure you are uploading log files that cover those periods. I don’t know if you’re judging things by looking at the real-time graph or by analyzing the log after the fact. But don’t get confused by large guide star excursions that are the result of dithering, those are entirely normal and are identified as such in either the real-time graph or the PHD2 Log Viewer.
Regards,
Bruce
From: open-phd...@googlegroups.com [mailto:open-phd...@googlegroups.com] On Behalf Of Peter Gottstein
Sent: Sunday, January 29, 2023 4:51 AM
To: Open PHD Guiding <open-phd...@googlegroups.com>
Subject: [open-phd-guiding] Please disable Synchronous Pulse Guide in ASCOM Driver warning vs APCC
I currently run the the latest ASCOM driver version with my- AP Mach 2 mount while running APCC software. Every-time I run I get the following PHD2 warning. Please disable the synchronous Pulse guide option in6 mounts ASCOM.driver settings. I have done this and to no avail. I also will have situations where guiding will go crazy 2 hours in. The developer of APCC claims this a serious PHD2 bug and not a ASCOM or APCC issue. Can you please advise. Thank you in advance. my- logs are included.
Best
-
Peter
--
You received this message because you are subscribed to the Google Groups "Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/68536dc7-4ab6-4443-b11a-4742bffd08b8n%40googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Open PHD Guiding" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/open-phd-guiding/h8Ekv_Y7No0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/004a01d93453%244c919700%24e5b4c500%24%40earthlink.net.
Bruce Waddington
Your guiding settings look fine. The PHD2 setup procedure has become pretty good at setting guider properties to work well for a particular setup. Your use of the variable delay exposure feature is definitely the right thing to do for the Mach2. I would still like to know if you’re using an OAG or a separate guide scope, can you help me with that? We don’t recommend changing settings until we can identify a specific shortcoming in the mount’s native tracking and I don’t see that here.
I think the real issue is your claim that your guiding “goes crazy” on a repeated basis. I need to see some clear examples of that in order to help you further. If the single anomaly I pointed out is indeed rather unique, then we can probably ignore it. For now, I can’t really see what problem it is that you’re having.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/5E9D765F-95B0-43B4-A921-ACC1BB7D3A2A%40gmail.com.
Peter Gottstein
On Jan 29, 2023, at 9:59 PM, Bruce Waddington <bw_m...@earthlink.net> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/007001d93467%24ad0b3910%240721ab30%24%40earthlink.net.
Peter Gottstein
On Jan 29, 2023, at 9:59 PM, Bruce Waddington <bw_m...@earthlink.net> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/007001d93467%24ad0b3910%240721ab30%24%40earthlink.net.
Bruce Waddington
Ok. Figuring out the disabled tracking problem may be the key. If tracking is disabled – for example because of a meridian limit you’ve configured – guiding will indeed “go crazy.”
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/A8C066B4-854E-4DC4-9908-C0C3885206A5%40gmail.com.
Peter Gottstein
On Jan 30, 2023, at 6:24 PM, Bruce Waddington <bw_m...@earthlink.net> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/004501d93512%24c9848910%245c8d9b30%24%40earthlink.net.
Bruce Waddington
No, I think the thing to do is look at the various log files and be sure we know what’s happening. Right now, I’m just speculating that meridian limits might be a possible factor. I’d like to see a log where you think the guiding has gone very bad, then trace that time period back to what’s going on with the various other pieces of software – NINA, ASCOM driver, etc. If we’re systematic about tracking this down, we won’t fall into the common trap of flailing around and chasing smoke. J
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/22AFE9AA-9C0E-441E-9538-22F7E5CAFC70%40gmail.com.
Peter Gottstein
On Jan 30, 2023, at 7:07 PM, Bruce Waddington <bw_m...@earthlink.net> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/006101d93518%24cbd484d0%24637d8e70%24%40earthlink.net.
hugh...@gmail.com
Here are my log files.
Bruce Waddington
Can you tell me what kind of PC this is running on and is it only a dual-core CPU? In any case, if you know that the synchronous pulse-guide option is disabled, just disable the alert message by clicking on the “don’t show again” box. We plan to change how this is handled in the next dev release. In your case, the guiding was fine, so no issues.
Regards,
Bruce
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/ce7e1c21-7c89-49f2-90af-9559212f9abbn%40googlegroups.com.
Matt H
MeLE Mini PC Fanless QuieterHD3 N5105 Windows 11 Pro 16GB RAM 512GB ROM Mini Desktop Computer with VESA Mount, WiFi 6 BT5.2 Gigabit Ethernet, Support 4K Triple Display, M.2 NVMe SSD, 2.5" SATA HDD/SSD
On 19 Feb 2023, at 13:22, Bruce Waddington <bw_m...@earthlink.net> wrote:
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/005f01d94409%2407bd4820%241737d860%24%40earthlink.net.