Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Losmandy_users
- Messages
Search
Mount takes off when guiding is turned on
All of a sudden my G11 has decided to take off when I activate software guiding.
It tracks fine and I get 30 second images with not star trailing but as soon as start guiding in PHD2 or Metaguide the mount starts drifting off. A 30 second image with guiding turned on shows LARGE star trails. This is with a Gemini 1. I tried parking then turning the electronics off and cold stating it but the same issue is there. Any ideas? Last night it worked fine. Jim P |
Re: Spikes!
What calibration problems are you having?I want to get to 0.5" RMS total but 1.2 is the closest I got, with the 12".? I'm looking at mechanical problems first.? The DIY spring loaded worms seem to work but I will check again, need to check the effect of tightening the clutches too.? I have equal errors in DEC and RA so it could just be poor seeing.? I will find out more tonight with the 6", just guiding no imaging.? Until it works. |
Re: Scope Location and NINA
Russ Is it possible you have Set Gemini time and location on connect in your Gemini application? On Fri, Apr 2, 2021 at 5:48 PM Russ via <njrusty=[email protected]> wrote: Constantly having the same issue when connecting scope to NINA, MAXIM and any other software.? Tonight for example, the G11 HC (physical device) shows my location (LAT/LONG/TIME) correctly.? However, when connecting to any software package (like NINA) and I look at the virtual Gemini HC on screen, shows my location as Hollywood with everything zeroed out.? When I then try to slew to a star it is way off.? Also, the Gemini Virtual HC will not let me enter a new LAT/LONG/TIME. --
Brian? Brian Valente portfolio |
Scope Location and NINA
Constantly having the same issue when connecting scope to NINA, MAXIM and any other software.? Tonight for example, the G11 HC (physical device) shows my location (LAT/LONG/TIME) correctly.? However, when connecting to any software package (like NINA) and I look at the virtual Gemini HC on screen, shows my location as Hollywood with everything zeroed out.? When I then try to slew to a star it is way off.? Also, the Gemini Virtual HC will not let me enter a new LAT/LONG/TIME.
Anyone else come across this issue???? |
Re: Spikes!
haha well i'll say it one more time? "this doesn't directly address your question, but i think having a solid foundation is an important first step here" Fixing symptoms with unknown?causes is always a process of elimination right? if we knew what it was, we'd just jump to the fix. But 99% of the effort is isolating the cause. So it makes sense to me that we want to make sure everything else is operating correctly, and eliminate one thing at a time that's also why I mentioned the previous steps of doing an unguided run. if it shows up in the unguided results, we know it's the mount. if it's not we know it's not the mount, or at least not the mount by itself i like your idea of testing without the SCT On Fri, Apr 2, 2021 at 2:12 PM Jamie Amendolagine <jamie.amendolagine@...> wrote: I made a habit of making large steps for calibration sometime ago, and I honestly can't remember exactly why I did that... I think that PHD was complaining that my steps were too small, so I just increased them. I'll try and dial it in better tonight, but honestly I don't see how the calibration can account for the spikes, and that's my biggest issue.? --
Brian? Brian Valente portfolio |
Re: Spikes!
?hmmm well the prior one i showed was pretty much the same, but maybe you didn't see the second image on that post What calibration problems are you having? On Fri, Apr 2, 2021 at 2:13 PM Henk Aling <haling@...> wrote: Hi Brian, that's not the same graph that you showed earlier.? Never mind though, I am just a disturbance trying to learn how to debug calibration problems. --
Brian? Brian Valente portfolio |
Re: Spikes!
I made a habit of making large steps for calibration sometime ago, and I honestly can't remember exactly why I did that... I think that PHD was complaining that my steps were too small, so I just increased them. I'll try and dial it in better tonight, but honestly I don't see how the calibration can account for the spikes, and that's my biggest issue.?
Jamie |
Re: Still working out polar alignment on my mount
Hi Jeff Are you referring to a reset to default values? from your hand controller main screen MENU->SYSTEM->RESET HGM DEFAULTS then power cycle the Gemini After that I recommend doing a Quick Start and walking through the setup info If you change your mount type (and I think you?will: you have a G11T correct?) you will want to power cycle your mount again after that On Fri, Apr 2, 2021 at 1:15 PM jeff marston <jeffmarston@...> wrote: How do you do default setting for anything on Gemini 2. I haven¡¯t found a video that shows that yet. I have looked through the menu and I haven¡¯t seen it. It has to be something obvious I just missed. --
Brian? Brian Valente portfolio |
Re: Still working out polar alignment on my mount
Jeff are you imaging or observing? On Fri, Apr 2, 2021 at 1:12 PM jeff marston <jeffmarston@...> wrote: I have not tried those. I was thinking of getting a polemaster. On other mounts, I have used a polar alignment scope and it was usually close enough. I don¡¯t even know if there is such a thing for my G11T.? --
Brian? Brian Valente portfolio |
Re: Spikes!
Sorry i should?have said The DEC axis calibration?looks fine? On Fri, Apr 2, 2021 at 12:57 PM Brian Valente via <bvalente=[email protected]> wrote:
--
Brian? Brian Valente portfolio |
Re: Spikes!
Henk the backlash calibration looks fine to me? southern movement is not part of the calibration you're right they are both too big On Fri, Apr 2, 2021 at 12:53 PM Henk Aling <haling@...> wrote: From the calibration graphs, it's not just the RA that has steps that are too large but the DEC calibration steps are almost all backlash clearance (the ones labeled B).? There are just a few small steps South, then North finally acts half way normal. --
Brian? Brian Valente portfolio |
Re: Spikes!
From the calibration graphs, it's not just the RA that has steps that are too large but the DEC calibration steps are almost all backlash clearance (the ones labeled B).? There are just a few small steps South, then North finally acts half way normal.
So, major DEC backlash problems during the calibration at least.? The large RA steps indicate there's something wrong in the settings, and PHD2 will therefore use a gain that's way off.? That could explain it. Now, if I could only fix my own guiding problems... |
Re: Spikes!
Yes, as I mentioned this doesn't directly address your bumps, but I think it's important to make sure everything else is working correctly Another thing that would help is a longer unguided run like 30-45 min (guiding assistant or disable guide output) If there's a problem in the mount, it will show there as well might also doublecheck?PEC status and and TVC values On Fri, Apr 2, 2021 at 11:44 AM Jamie Amendolagine <jamie.amendolagine@...> wrote: Thanks, you're right, I don't have very good calibration. I'll do that next time I'm out. But I don't think that it's related to the issue that I'm seeing. I generally use similar settings for the calibration, and I've very reliable, and good guiding in the past. This spike is new, I don't think that I've ever seen it before. Tonight I'll be trying things out using the guide scope instead of the OAG. If the issue is still there, then I can eliminate possible issues with the SCT like mirror flop or some sort of looseness. If that fixes it, then there might be something going on with the SCT, or image train on the SCT.? --
Brian? Brian Valente portfolio |
Re: Spikes!
Thanks, you're right, I don't have very good calibration. I'll do that next time I'm out. But I don't think that it's related to the issue that I'm seeing. I generally use similar settings for the calibration, and I've had very reliable, and good guiding in the past. This spike is new, I don't think that I've ever seen it before. Tonight I'll be trying things out using the guide scope instead of the OAG. If the issue is still there, then I can eliminate possible issues with the SCT like mirror flop or some sort of looseness. If that fixes it, then there might be something going on with the SCT, or image train on the SCT.?
Jamie |
to navigate to use esc to dismiss