Jump to content

sgl_imaging_challenge_2021_annual.thumb.jpg.3fc34f695a81b16210333189a3162ac7.jpg

Recommended Posts

Hi all PHD2 seems to be playing up again and Iost a clear night again¬†ūü§¨¬†Everything appeared to be fine and after polar aligning¬†(separate camera to guide scope) I set up a new sequence.¬† That started up and focused, plate solved¬†and then guiding started but after a few seconds of perfect looking guiding the RA and Dec went off the scale massively ending up with a PHD error along the lines of "PHD2 is unable to make sufficient corrections in RA, check for cable snags, redo calibration...." Images obviously come out trailed. I have an RDP connection to the laptop at the mount so after happening a few times I went to check for snags etc but it all seemed fine. I set up the sequence again at the mount and the same thing happened. Restarting the apps, power cycling the kit and choosing different targets all resulted in the same issue so I packed it all away. It was also the same if I used PHD2 via NINA or if I just started PHD2 on its own and tried guiding separately.

I'm using an AZ-EQ6 with a WO guide scope and 120mm if it's relevant.

I checked everything was tight and have not looked at any logs yet but does anyone have any bright ideas what might be happening please?

Thanks in advance...

Link to post
Share on other sites
  • Replies 33
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Posts

Did you do a calibration in PHD?

Are you sure it started a calibration? PHD has the option to reuse previous calibrations as it saves time if you haven't moved your guide scope or camera. Dont assume NINA will take care of everything

I didnt know it did the calibration first, how did you get it to do that?  If nothing has changed with the setup hardware since the last calibration then a new calibration shouldn't be needed for

Were you clutches tight? I've had this behaviour in PHD2 recently and the clutches weren't quite done up after I'd done the PA. 

Also I'd reiterate the advice above and redo a calibration (and guiding assistant for good measure) 

 

 

 

Link to post
Share on other sites

 

19 minutes ago, david_taurus83 said:

Did you do a calibration in PHD?

Thanks and searching around suggest this too but no I didn't do anything other than start the sequence which does a calibration before it starts guiding.

I'm assuming there is a separate step somewhere so if so nope didn't do it or know about it....

Link to post
Share on other sites
Just now, CraigT82 said:

Were you clutches tight? I've had this behaviour in PHD2 recently and the clutches weren't quite done up after I'd done the PA. 

I was about to post this same issue: A few days ago I forgot to fully close the DEC clutch and got the same error.

Link to post
Share on other sites
2 minutes ago, CraigT82 said:

Were you clutches tight? I've had this behaviour in PHD2 recently and the clutches weren't quite done up after I'd done the PA. 

Also I'd reiterate the advice above and redo a calibration (and guiding assistant for good measure) 

 

 

 

Yep thanks, I'd checked that and seemed fine.

Link to post
Share on other sites
18 minutes ago, scotty38 said:

 

Thanks and searching around suggest this too but no I didn't do anything other than start the sequence which does a calibration before it starts guiding.

I'm assuming there is a separate step somewhere so if so nope didn't do it or know about it....

Are you sure it started a calibration? PHD has the option to reuse previous calibrations as it saves time if you haven't moved your guide scope or camera. Dont assume NINA will take care of everything for you. All it does is send a command to PHD to start guiding. Do you strip down all your gear after a session and put it back together again for the next? If so, you will need to do a fresh calibration each time. It's also recommended you slew to near the celestial equator to perform the calibration as it gives better results.

There should be a folder in Documents titled PHD2 and it automatically stores guide logs in there. You can review the latest ones with the PHD log viewer.

https://openphdguiding.org/phd2-log-viewer/

  • Like 1
Link to post
Share on other sites
32 minutes ago, scotty38 said:

I didn't do anything other than start the sequence which does a calibration before it starts guiding.

I didnt know it did the calibration first, how did you get it to do that? 

If nothing has changed with the setup hardware since the last calibration then a new calibration shouldn't be needed for each session, just a guiding assistant run. I think if you rotate your guide cam in the guide scope you would need a new calibration.  You didn't have any windows updates or any other software changes that might have affected phd2 at all before that session? 

Edited by CraigT82
  • Like 1
Link to post
Share on other sites

I had this same issue a few nights ago. Doing another calibration seemed to fix it but I have no idea what caused the problem. I had been guiding fine earlier in the evening and it only started happening after I slewed closer to the pole and tried to guide there.

I have a suspicion that it may be related to the fact that I cleared all my alignment points at one point while trying to frame my target. I wonder if the mount had 'forgotten' where it was at the point when I started guiding in PHD.

  • Like 1
Link to post
Share on other sites

Hi Scotty

Sounds like it was using a previous Cal, and something was different from your last Cal, so carry out a new one.

If you hover the pointer over any of the PHD2 buttons, you get some Help text.

In the case of the "Guide" button, it says something like "Shift-Click to start a new Calibration"

In case there's a different problem, post your PHD2 GuideLog (they're in the PHD2 Folder)

Michael

  • Like 1
Link to post
Share on other sites
22 minutes ago, CraigT82 said:

I didnt know it did the calibration first, how did you get it to do that? 

If nothing has changed with the setup hardware since the last calibration then a new calibration shouldn't be needed for each session, just a guiding assistant run. I think if you rotate your guide cam in the guide scope you would need a new calibration.  You didn't have any windows updates or any other software changes that might have affected phd2 at all before that session? 

To be honest nothing... I just see the word "calibrating", "looping" etc at the bottom of the screen in NINA or PHD. It may well not be the same thing as an initial or full calibration though....

Link to post
Share on other sites
1 minute ago, michael8554 said:

Hi Scotty

Sounds like it was using a previous Cal, and something was different from your last Cal, so carry out a new one.

If you hover the pointer over any of the PHD2 buttons, you get some Help text.

In the case of the "Guide" button, it says something like "Shift-Click to start a new Calibration"

In case there's a different problem, post your PHD2 GuideLog (they're in the PHD2 Folder)

Michael

Thanks and I'll try this and see what happens. I did try the shift-click thing and being honest didn't see it do much different at all, unless it was doing it anyway, if that makes sense. I'll grab the logs of my other machine and see what they say.

Link to post
Share on other sites
5 minutes ago, scotty38 said:

To be honest nothing... I just see the word "calibrating", "looping" etc at the bottom of the screen in NINA or PHD. It may well not be the same thing as an initial or full calibration though....

OK. The full calibration normally take a couple of minutes. Definitely worth doing it next time you set up. 

When you shift click the green guide icon you should get a dialogue box asking you if you're sure you want to redo the calibration

Edited by CraigT82
  • Like 1
Link to post
Share on other sites
27 minutes ago, CraigT82 said:

I didnt know it did the calibration first, how did you get it to do that? 

If nothing has changed with the setup hardware since the last calibration then a new calibration shouldn't be needed for each session, just a guiding assistant run. I think if you rotate your guide cam in the guide scope you would need a new calibration.  You didn't have any windows updates or any other software changes that might have affected phd2 at all before that session? 

Sorry, I didn't answer your other questions. I have added an EAF which updated an ASCOM driver but nothing else has changed. I set up the focuser the other evening but after that was done the clouds rolled in so maybe that's affected something....

Link to post
Share on other sites
3 minutes ago, CraigT82 said:

OK. The full calibration normally take a couple of minutes. Definitely worth doing it next time you set up. 

When you shift click the green guide icon you should get a dialogue box asking you if you're sure you want to redo the calibration

ok thanks, in that case it wasn't done as I saw no dialogue box. It all seems to be pointing towards doing that although I don't recall doing it previously and it has worked before so maybe just lucky that time....

Link to post
Share on other sites

Hi Scotty

The difference between when PHD2 is Calibrating and when it's Guiding is pretty obvious.

Sounds like you need to read and apply some of the PHD2 Help Guides you can find via the Help menu.

Michael

  • Like 1
Link to post
Share on other sites

If you have PHD open during the calibration, it will give you information about the process in the bottom left hand corner. It should take about 10-30 steps and you can see the star being brought back to the centre when it moves in the opposite direction. 
Given the problem you had I would definitely recommend you do a calibration at the start of the session, if it successfully calibrates that rules out any initial set up problems.

  • Like 1
Link to post
Share on other sites
36 minutes ago, david_taurus83 said:

Are you sure it started a calibration? PHD has the option to reuse previous calibrations as it saves time if you haven't moved your guide scope or camera. Dont assume NINA will take care of everything for you. All it does is send a command to PHD to start guiding. Do you strip down all your gear after a session and put it back together again for the next? If so, you will need to do a fresh calibration each time. It's also recommended you slew to near the celestial equator to perform the calibration as it gives better results.

There should be a folder in Documents titled PHD2 and it automatically stores guide logs in there. You can review the latest ones with the PHD log viewer.

https://openphdguiding.org/phd2-log-viewer/

No I'm not sure to be fair. I take the scope, guide scope and cameras etc off the mount as one each time but they all stay connected relative to each other and all I do when it's remounted and after a PA is have NINA tell PHD to start guiding. Sounds like I've missed/missing some initial calibration at least....

Link to post
Share on other sites
2 minutes ago, michael8554 said:

Hi Scotty

The difference between when PHD2 is Calibrating and when it's Guiding is pretty obvious.

Sounds like you need to read and apply some of the PHD2 Help Guides you can find via the Help menu.

Michael

Yep agreed!

Link to post
Share on other sites
1 minute ago, tomato said:

If you have PHD open during the calibration, it will give you information about the process in the bottom left hand corner. It should take about 10-30 steps and you can see the star being brought back to the centre when it moves in the opposite direction. 
Given the problem you had I would definitely recommend you do a calibration at the start of the session, if it successfully calibrates that rules out any initial set up problems.

Yes I see all that and I'll do a full calibration next chance I get. Thanks

Link to post
Share on other sites
1 minute ago, scotty38 said:

I take the scope, guide scope and cameras etc off the mount as one each time but they all stay connected relative to each other

Then a different problem to Calibration, you need to post that Log !

Michael

Link to post
Share on other sites
Posted (edited)

Hi at first I was looking at the California Nebula then I tried M51 so pointing the other wayish. I've attached the PHD2 debug log too, there's a lot in there but you can probably ignore the latter half as I was messing at that stage with focus on the guide scope to see if that was the issue.

PHD2_DebugLog_2021-03-20_195954.txt

Edited by scotty38
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 Sajjad
      Hello, 
      I'm using phd2 guiding with an asi 120mm mini connected to my laptop via USB.. I have eq6r mount which is also connected via USB.. When I connect everything the mount can be controlled via the eqmod interface.. It slews in all directions.. However, when I connect to phd2 and try manual guiding to check if commands are going to the mount nothing happens in any direction.. I have the setting at 5000ms..i don't hear any movement from the mount and have had a look at the motors but they do not turn even when holding the direction button for minutes!! What am I doing wrong here? 
      Please help as this is driving me crazy.. Thanks in advance 
    • By NigelHt
      I've recently started astrophotography, and after beginning with a DSLR and rotator haveprogressed to an EQM-35 GoTo mount and Zenithstar 73 telescope, with Ascom control and guiding with PHD2. While I've got some decent results, I've consistently had problems with guiding, even though I've tried adjusting the mount as described in online videos to remove backlash, and unbalancing the telescope. Initially there was obvious backlash that I could feel; I've now eliminated that, although I notice that the stiffness varies with declination (something I've seen reported by others), and it's almost impossible to avoid backlash at some declination angles without making the mount far too stiff at others.
      While I'm aware that this type of mount is always prone to backlash issues, what I'm seeing is still different to what I'd expect. If I drive the mount, say, North (either manually or as part of calibration or guiding), stop so that everything comes completely to rest, and then drive the mount South, what I see is that it continues to move North for a while before beginning to move South as expected; the behaviour is exactly the same if I start moving South then switch to moving North. The attached image is part of a typical calibration from PHD2 Log Viewer to show what I mean. As you can imagine, this completely messes up guiding unless I offset the polar alignment and guide in one direction only, or align very accurately and switch off declination guiding altogether.
      If this was simply backlash, I'd expect the mount not to move at all initially after switching direction rather than to move the wrong way, and I can't think of a mechanism to cause this behaviour. I'd be grateful if anyone can explain this, please, and give me some advice on how to cure it.

    • By blameTECHIE
      I don't expect any replies - think I'm just braindumping for the mental wellbeing aspect of a frustrating night.
      ---
      Having been ill through the week, Saturday found me feeling well enough to get outside and see if I could hook some things together and try to get FirstLight through some of my recent purchases.  I've been using my Star Adventurer mini-rig [SA non-wifi, Canon 200D (unmodified), >30yr old Tamron 200mm f3.5] but knew things were going to be very different, and was keen to get going.
      So the kit was all lined up:
      > Laptop (Win10), Raspberry Pi4 with Astroberry
      > EQ6-R Pro
      > SW 80ED-DS Pro (Kit), SVBony SV106 190mm/50mm Guide Scope
      > ZWO ASI 224MC, Canon 200D, SVBony SV205, 7TC ASI 120MC clone
      > USB GPS Dongle (G72 G-Mouse Glonass Beidou GNSS) for location
      and mains power for all via various PSUs with enough USB cables to circle the planet
      ---
      Didn't take too long to get both Win10 (ASCOM) or Astroberry (INDI) talking to the mount and progress was being made - RA/DEC all seemed fine so onto the cameras.  Found a distant object and SharpCap gave me images for all three USB devices once I had the SVBony as a Windows WebCam (RESULT!) and the same through INDI on the Astroberry, all three displayed images when enabling Streaming.
      Settled on EQ6-R, SW 80ED, ASI224MC for imaging, SV106/SV205 for guiding
      That's it (I thought!) and I broke down the rig and moved it to the lawn - I say lawn, more like a mossy bank but serves the purpose - and wait until dusk where a simple Polar Align and I'll be grabbing images of M51 Whirlpool in no time ...............

      (I must cut the lawn, even if just to get rid of the blue from spray-painting a new table a couple of weekends ago)

      (please ignore the middle dew heater, was there to remind me to put it on the guide scope later)
      ---
      PA on the Star Adventurer, 30mins (5mins for the alignment, 5mins for remembering which phone app has a PA Clock and the obligatory 20mins to find the flamin' polar illuminator!) - this has been giving me consistent 5min exposures with no trailing.
      PA on the EQ6-R is 'interesting' - I have a QHY PoleMaster but am waiting on the adapter from FLO (stock issues) so it was SharpCap alignment.
      Wait for it to get dark enough, then get focus, then wait for platesolving in a "change exposure, gain, star threshold, black threshold, platesolve again" loop for over an hour.  Woohoo, plate solved ..... oh, rotate around RA ..... and perform the same operation again ..... ARGHHH!
      Over two hours later (probably more like 3hrs+) I've got polar alignment to within 12 seconds (wishing I'd screengrabbed that now).  I really don't like the adjustment mechanism, the thread pitch is far too high for minute adjustments of alignment!
      ---
      And onto guiding ........................ or maybe not.
      PHD2, Nothing through it at all .... then remembered I'd not refocused the guide scope, then it was taking the Darks library.  Still nothing.  Opened the SV205 via SharpCap and got focus, switched back to PHD2, still nothing ...... hmm, is this just an unsupported camera (windows 'webcam').  So switched out for the 120MC copy - Amazon 7TC special.
      Repeated the SharpCap for focus, then PHD2 Darks library and BOOM I have stars showing up in PHD2 - RESULT ...... I'll leave it at that for a moment and try looking at something, see what I get from the 224MC main camera and what PHD2 gives me in the guide scope.
      So onto the next 'learning opportunity' - target selection
      ---
      Erm, how do I select a target for goto with just two camera apps .... aha, Stellarium
      No Telescope selected, easy - it went something like this:
      "Open Stellarium, select telescope, select ASCOM ... there we go ... nope, it won't connect ... restart everything (twice) ... redo settings (twice) ... check ASCOM diagnostics (all passed) ... quick google search, aha I'm not the only one, you have to select the scope within the options pane ... what options pane .... oh, scroll down ..."
      And I now have Stellarium control of the scope - again a RESULT - it's taking time but I think I'm making progress here .... hmm, it's getting bloody cold, wow, it's midnight!
      ---
      So I now have an in focus 224MC, an in focus guide scope and control over the mount, here we go ... I'll be stacking images in the morning and making millions from selling prints online
      NOPE!
      Easy targets for testing were below the horizon (basically M42) so I'll just pick Vega and make sure slewing works, imaging works and can see how guiding works.
      Nothing, no bright star at all - okay, bigger target - the moon.
      Again nothing, no bright screen - so switched out the camera for a 26mm LER EP and a diagonal and manually aligned the moon - then, and here comes stupid, refocused (!) for the moon.
      ---
      Stellarium wasn't syncing with the mount - I was 'off' on any selected target and by a lot
      Quick google search and I'm no the only one - no sync points on my clean build so wasn't that, but use of the GPS dongle for location and TIME might be the problem.
      ---
      And at this point it as 2:30am - prime viewing time last night with the moon disappearing in the West behind me - the garden slopes due-West to due-East so I only get Partial-North>East>Partial-South viewing.
      Time to give up, have a small glass of Red and look for more things to buy on SGL/Astro B&S.
      ---
      Today - well I had to break everything down to get it into the garage (too heavy to carry as one with current health) - I'll try to get the ASCOM/GPS element sorted out and maybe this evening try some targeting/lunar rate tracking so see if that major element is resolved.
      And, if you've made it this far, please accept this for your perseveranceūüéĖÔłŹ, you've earned it.
    • By Quetzalcoatl72
      Below are consecutive raw pictures if the ring nebula I took with my canon 600da and RCT 8" with neq6 pro guided with sharpcaps polar alignment procedure on the 15th of this month at 1am. I have 20 of these all 1600 iso auto wb 2 minute exposures. The problem will become apparent when you closely examine them, tracking is almost completely broken. I only stacked about 8 of them as most of the frames are unusable, some are star trails, some are commas and some are double exposures. This has become standard and getting worse since I tampered with my mounts gears and backlash adjustment. I have never been able to get consecutive 3min exposures on this mount, and I got it new 6 years ago, and only used it less than 30 times. I have spent roughly 20 hours trying to get rid of the backlash, coffee grinding noise and knocking when I press the directional keys to no avail, when the keys are pressed I notice the image wobbles violently. The go-to is also not working to 100% efficiently, I have to do guess work if I want my image centred.
       










    • By jacko61
      After some trial and error I'm getting some very good guiding results with PHD2 now. 60mm guidescope and ASI290MM mini camera. The M42 image taken late March was 12 x 15 second exposures taken manually with my dslr / C8 and a stopwatch. Stacked in DSS and played with a bit in GIMP. On the night I couldn't get APT to register the camera - turned out to be the mini USB cable (although later trials point to the socket in the camera being a bit loose too). 
      Bought an iOPTRON iPOLAR that arrived on Friday and had a play with that which has resulted in near perfect polar alignment. 2 star alignment and an additional 2 calibration stars on my Advanced GT mount means I'm getting very accurate GOTOs now and PHD2 (through the ST4 port on the ASI camera) seems to be guiding very well.  Last night after more cable faffing I managed to get everything working together to the point where I felt confident enough to leave it running by itself for an hour and a half (45 minutes of 180 second exposures plus 3 minutes each exposure to save the file - I've since found out I shouldn't have noise reduction switched on in the camera - DOH!) so M51 is 15 x 180 second @ ISO 800 lights and 5 x 180 second darks.  A little manipulation in GIMP and I think it's come out very well. Obviously still have a lot to learn and I'm going to have to start taking much longer exposures  but I'm quite pleased with these 2 pictures. 
      Graeme.
       

       

√ó
√ó
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.