Jump to content

Stargazers Lounge Uses Cookies

Like most websites, SGL uses cookies in order to deliver a secure, personalised service, to provide social media functions and to analyse our traffic. Continued use of SGL indicates your acceptance of our cookie policy.

joecoyle

Anyone able to help analyse my PHD2 log? Regular dec dips...

Recommended Posts

Hi

I've set my scope up on it's pier in my ROR observatory, done a few drift aligns and started to take some images. 

I've noticed a 'quite' regular dip in my DEC line on several nights. 

Would anyone be able to have a quick scan of my log and offer any insight?

Could it be backlash? Could it be something with each rotation of the gears? Faulty tooth? 

It is quite regular, although not always, and always in the same direction.

It doesn't seem to be adversely affecting imaging yet, but I've not tried anything too taxing.

Thanks

Joe

 

PHD2_GuideLog_2018-09-23_200940.txt

Share this post


Link to post
Share on other sites

Hi Joe

I would send the guidelog and the debuglog to the Open PHD Guiding forum, where the PHD developers will give you an expert opinion.

https://groups.google.com/forum/?fromgroups=#!forum/open-phd-guiding

I'd guess you have a lot of Dec backlash - have you measured it with the Guiding Assistant?

If your mount has Backlash Compensation you should disable this as it fights PHD

The dec excursions aren't always in the same direction, the events at 20:44 onwards, where Dec is yoyo-ing back and forth, they could be due to stiction - corrections are sent until the dec unsticks, then it flies over to the other side, and repeats.

Or just large backlash causing over-corrections.

Your PA might be too good !! If you had a gentle PA trend and unbalanced slightly the same way, then Dec correction would only need to be in that direction, avoiding the overshoots and lengthy time correcting.

But like I say, ask the experts !

Michael

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By knobby
      Hi All, wondered if you could help me make sense of this ... new HEQ5 - belt modded by FLO, all feels good, minuscule backlash but strange guiding.
      Admittedly first time using it but baffled.
      Failed calibration see image below and guiding seemed to be Ra and Dec following each other.
      Stars look ok ish (@ 1500 mm )
      Needle galaxy is poor as only about 10 mins each in RGB
      note - it was hazy and did keep losing star in OAG
       
      Thanks for looking
      PHD2_DebugLog_2020-05-19_221608.txt
       



    • By Odiug
      Dear Avalon Enthusiasts,
       
      Do you have PHD2 Guiding Logs that you could share? Preferably at least 30 minutes long.
      I am curious about the contribution to the overall error from the individual parts of the belt reduction gear. PHD2 Log Viewer provides nice analysis capabilities for that. I am especially interested in the frequency analysis.
      Background is that I have built a motion module that uses a timing belt gear reduction quite similar to the Avalon mounts. Performance is quite good already, but I would like to compare it to the "real thing". 😃
       
      CS
      Guido
    • By Astronome
      Hello all,
      I have had a real problem with my AZ EQ6 GT:
      I have found that the MOUNT guide rate in RA is 1/3 the guide rate in DEC.  EQMOD is set to 0.9 in both axis??  This seems to have happened when I tried guiding with AA& instead of the normal PHD2?
      Is there a mount direct command to alter the RA guide rate.  Bit like the mount commands to dim the polar scope and set park position.
      You know one of these serial commands the no one ever uses??
      All the best
      John
       
    • By AstroRuz
      Hello all,
      So I routinely have issues with guiding. Last night, I was getting some solid sub exposures of 5 minutes on the Flaming Star Nebula. When it got to about 15-20minutes of the meridian, I began getting trails on my stars. Then after the flip, I was still getting trails despite PHD reporting all's well.  I moved over to the Horsehead Nebula and tried 5 minutes there, and it behaved itself. Then I tested it on the Jellyfish Nebula and it also behaved (just about - minor trails). But it just did not want to dig it with the Flaming Star Nebula, which was practically near the zenith (about 2:30am 30/11/19).
      I tried recalibrating PHD (I use Pulseguide so the scope knew where it was). I then also recalibrated PHD at Alnitak so it was near the celestial equator (as the PHD best practices recommend). I even checked my Polar Alignment (done with a Polemaster), which was fine. I couldn't find anything wrong. 
      The guide scope was slightly off alignment with the main OTA, but that wasn't making any differences before the Meridian. 
       
      I did find the helical focuser of the Starwave 50mm guide scope I was using to have some movement in it again when I manipulated the guide camera. So that's something I need to look into. But before I start throwing money at this issue, I see the terms "flexure" and "differential flexure" coming up. Can anyone shed light on what this means please?
      I tried manipulating the OTA in its tube rings, that didn't yield any movement either. The piggyback scope is secure, the g/scope is secure in its rings as well, there's no movement in the OTA focus rack and the cameras are secure in their tubes. 
      I do have my guide rings quite far back on the body of the telescope to assist with fitting the guide scope piggyback. 
      Video of g/scope play: 
       

      Flaming Star Nebula. 5 minute sub, post Meridian Flip, about 2:50am (30/11/19). Note the plate solve compass in the top left. Drift appears to be in S/W direction.

      Position of tube rings (they're now at the focus end).
      I think I am leaning towards needing to move my tube rings (once I remember to get the tools from work). 
       
       
      Equipment:
      (brand new) Skywatcher EQ6-R Pro, SW Evostar Pro 80ED, Altair 0.8x R/F, Canon 600D, Altair Starwave 50mm Guide Scope, Altair AR130 Mono Guide Cam. 
       
       
    • By John Lawley
      Hi - I've not posted here before as only just launched into this hobby, although I've always been massively interested in astronomy.
      I had first light on my rig last night, which is:
      Esprit 100, HEQ 5 Pro, ZWO EAF, ZWO mini filter wheel, skywatcher 50ED guidscope with ASI120, ZWO1600mm Pro, Lynx dew controller w 2 astro zap tapes
      A big endeavour to get that lot working from zero experience, but I love a challenge and have really enjoyed the computer side (I'm a grade A nerd)...
       
      So - what went well... I got the guide scope in focus (was stressing about this), and also the main scope. Even more awesomely, the autofocus routine in SGP is working perfectly Filter wheel also working perfectly and I'm getting lovely smooth pics from the main camera (I've already done the flats and darks while I was waiting for clouds to clear). Final good thing (well, good-ish), is that I got the platesolving working eventually, and was able to get the scope to align from Park to the Soul Nebula and centre fine. For some reason the "number of attempts" in my SGP profile hadn't applied, so it was giving up after 1 go, but I got it working in the end.
       
      So the bad...
      I couldn't take any data because every time it finished the platesolving and started PHD2, PHD2 would start the calibration process and then halfway through, the sidereel tracking on the EQMOD panel would turn off. Obviously, that would lead to a "lost the star" error. Is there some reason why sidereel tracking would turn off like that? I'm generally a bit confused as to whether I should be controlling the telescope from SGP (i.e. unpark) or using the park and unpark + tracking button on the EQMOD panel. Both PHD 2 and SGP are setup to use EQMOD ASCOM HEQ5/6?
      So at the moment I can't do anything, because there's no way of guiding without it turning tracking off
       
      Also I was cold. Very Very Cold.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.