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.

Search the Community

Showing results for tags 'phd2'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Welcome
    • Welcome
  • Beginners
    • Getting Started General Help and Advice
    • Getting Started Equipment Help and Advice
    • Getting Started With Observing
    • Getting Started With Imaging
  • Community
    • Official SGL Announcements and Events
    • SGL Challenges and Competitions
    • SGL Star Parties
    • Star Parties & Astro Events
    • Celestial Events Heads Up
    • The Astro Lounge
  • Retailers
    • Sponsor Announcements and Offers
    • FLO Clearance Offers
    • IKI Observatory
    • Supplier Reviews
  • Astro Classifieds
    • For Sale / Swap
    • Wanted
  • Equipment
  • Observing
  • EEVA (Electronically Enhanced Visual Astronomy)
  • Imaging
  • Science
  • WADAS's WADAS Discussion Forum
  • Beaufort Club's Topics
  • Swindon Stargazers Club's Topics
  • East Midlands Stargazers''s Topics
  • Central Scotland Astro's Topics
  • SGL Cumbrian Skies's Topics
  • Herts, Beds and Bucks Group's Topics
  • SGL East Anglian Group's Topics
  • South Leicester Observers's Topics
  • South Wales Group's Topics
  • SGL Surrey Observers's Topics
  • South Yorkshire Stargazers's Topics
  • Yorkshire Astronomers's Topics
  • Devon and Cornwall's Topics
  • West Midlands's Topics
  • Essex Cloud Dodgers's Topics
  • Essex Cloud Dodgers's New equipment
  • NLO and Planetarium's Topics
  • Astronomical Society of Edinburgh's Discussion
  • Dorset Stargazers's Topics
  • Hairy Stars Club (Comets)'s Tutorials and Guides
  • Hairy Stars Club (Comets)'s General Discussion
  • Hairy Stars Club (Comets)'s Observing Campaigns
  • Hairy Stars Club (Comets)'s Analysis results
  • Hairy Stars Club (Comets)'s Useful Links
  • Pixinsight Users Club's Pixinsight Discussion Forum


  • Astro TV
  • Celestial Events
  • SGL Calendar
  • Astro Society Events
  • Star Parties
  • WADAS's Events
  • Beaufort Club's Events
  • Astronomical Society of Edinburgh's Events
  • Dorset Stargazers's Events


There are no results to display.

There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 42 results

  1. Hi All! I have guiding problem with the following guider setup: 9x50 finder + ZWO ASI 120mm mini + PHD2. The imaging scope is a 6' newtonian + canon dslr on a HEQ5, driven by a laptop via diy EQDIR cable. When the mount is set up and running correctly, polar aligned and all... I connect the guider camera and mount with phd2. All nice and easy, I run a calibration, then it starts to guide. All seems ok. Then I am starting to take pictures. The first seems OK, then the second have the star trails... I check phd2 and there is a message: the camera (ASI) did not take a picture for "xy" seconds so it is disconnected. Grrr.... I reconnect try to set up a longer period for "xy" in the settings as mentioned in the message. And all the same again and again. Whatever I add for connection timeout for the camera, it just reaches that and disconnect the camera. PHD + philips toucam has worked for me flowlessly. I changed to PHD2 because I gave myself a birthday present, the little ZWO camera. (and PHD did not recognize it) Do you have any idea what can be the problem? I will contact PHD2 help also, but maybe somebody had already the same problem and figured out how to overcome. I am almost sure I make some dumb mistake in the PHD2 software settings, however I tried to change only what was needed.
  2. Can Nebulosity and Ph.D operate simultaneously and share a single camera. Running Win 10.
  3. Ok, so this is a really annoying bug / problem that I have with my setup: From time to time, in non regular intervals the image my guiding cam (ZWO ASI120) send seems to get flipped / mirrored or looks like it's from a completely different patch of sky. When I'm paying attention to the guide images I can clearly see that the image seems to be flipped in some way. It only happens for 1 frame PHD send a warning ( No star found / Star lost Mass changed) and after that everything is fine again. My gear is all connected to a single USB3 Hub which then runs via powered USB3 cable to my Pc. I'm not binning and have the noise reduction off (though PHD might got hickups while processing) but it still happens. Sometimes there are minutes between two events sometimes it happens 5 times in a row. It also seems like it's only happening during guiding, I haven't seen it happen during calibration yet... I'm completely clueless what's happening or how to get rid of it, any help / idea is greatly appreciated.
  4. Hi Guys, hoping someone can help me with the guiding issues Iv'e been having. First of all my setup is: Explore Scientific ED80 Triplet Skywatcher EQ5 mount with synscan Orion mini 50mm guide scope Altair GPCAM2 AR0130 Mono (as the guide camera) I did my polar alignment and 3-star alignment, which was spot on. So I set up the GPCAM2 and opened PHD2 where I selected "Altair Camera" and "On-Camera". It was all in focus, kept it on the default settings and I selected "auto select star", then it said I was guiding (I can hear the mount making small adjustments). A message popped up saying I needed to increase the max RA duration, then I needed to increase the max DEC duration, which I did gradually by 1000ms each time the message appeared. Still no progress. So I restarted the process with the max RA and DEC duration as 8000ms and it said I needed to eliminate the source of the problems. (I HAVE ATTACHED IMAGES OF THIS) I'm not sure why it not working and if I'm doing something wrong. But if someone knows where I'm going wrong, or has any advise it will be greatly appreciated! Oh and just let me know if you need any more info, because Iv'e probably missed something out. Thanks again ?
  5. I've picked up a second hand Lightrack II recently, so was keen to test it. My plan was to use the guiding assistant in PHD to get a graph of the tracking performance, but initially the mount wouldn't move. After a search, I had to modify the guiding cable that came with the mount, as it was wired up 'the other way' to the one required for QHY5L. After that it calibrated fine and could run the test. Below is a 22min graph of the unguided performance, while it's not within the 2" peak-to-peak quoted, it's still pretty good. Next I've tried it with a canon 300mm lens (unguided again), the picture is a crop of a 10min exposure, slightly eggy, but again pretty happy with that.
  6. 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
  7. I connect my mount to PHD2 using ASCOM and most nights I have the error "Star did not move enough" as well as "Suspicious blah blah, axis may not be perpendicular". This does not happen when I connect the mount via ST4 cable. I read somewhere that I can do a Calibration Sanity Check in PHD2. I am however unable to find that function in the software. Is it some pop up feature or does it have a location in the settings/brain icon? Any help will be highly appreciated.
  8. Hi Guys, I recently went NB and face new challenges, - guiding in particular. My house blocks Polaris, so I use PHD2 drift alignment and usually cannot achieve better results than 8 arc-min PA Error. My guiding at the moment is quite good, but I noticed that Star Diffraction Spikes become blurry after 8min exposures and I want to improve if it's possible. Some PHD2 images with data below. My usual guiding exposure time 1sec., but I also enabled the timelapse option for 1s, so 2sec in total (camera Gain 60) The graph below is probably my best one and I afraid to touch anything but it's not enough :( Also, I noticed my PHD2 autoselects very low SNR stars, around 20-35 (adjusted as per youtube tutorial) I saw other posts with SNR 100 and even higher... I use 130PDS and ASI1600MM PRO for imaging and Evoguide50 + ASI22MC for guiding. All on NEQ6 Mount. Every Little advice will Help. Thank you PHD2_GuideLog_2018-07-02_223203.txt
  9. hello all.. i'm hoping someone can help me here. i'm trying to hook up my SW EQ3 Pro SynScan mount and ZWO ASI120MC guide camera with PHD2. I haven't done any auto guiding before, so forgive me if my questions are a bit dumb.. I've read quite a few bits online, but get confused with the terminology half the time. I've got my guide camera connected to my laptop via USB, and the SynScan connected via ST4 to USB too. I've downloaded and installed all the mount drivers I need (I think?), but nothing seems to happen when i try to control the mount with PHD2. Any thoughts or advice would be gratefully received and acted upon immediately - it's clear out tonight! If you can, please help.. you're my only hope. Thank you.. RAWz. ps: I have posted this question in another thread, but feared it may get buried. My setup: Skywatcher ED80 Pro Telescope + Skywatcher EQ3 Pro SynScan Mount and Tripod + ZWO ASI120MC Guide Camera + Canon EOS 550D + Microsoft LifeCam Polar Cam + PC or MAC.
  10. Hi I have just started to use Phd2 guiding, i need to upload the image of the guiding camera to astrometry so that i can determine the name of a particular star. I am unable to do that as I got the error message below, please can any one help. Here is link http://nova.astrometry.net/upload winnie
  11. Setting up all the software on my win10 laptop and getting things to talk to one another is a nightmare. I'm starting a new thread, so I can post all the problems I am having, one at a time, so issues don't get confused. This will also hopefully help anyone coming to similar situations later, as the problems and answers will not be interlaced. First issue: APT does not detect ZWO camera. I have got the camera (ZWO) drivers installed and sharpcap can see it and will connect to it properly. However, when I try to connect the camera in APT, the only CCD options it gives me are SBIG (which it isn't), QSI (which it isn't) and ASCOM. Now it shouldn't need to use an ascom driver, because the proper driver is installed, but I give it a go anyway, and this just offers me 2 simulators and 3 QHY cameras (I have one qhy driver installed for the guidecam .... I'll get to that later!). I have disconnected both the filterwheel and guide camera from the camera hub, so they cannot be interefering with the process. I am at a total loss ... any suggestions? Thanks.
  12. As a rookie astrophotographer, I have recently acquired a star adventurer mount. Seeing the port marked "Auto Guider" it sure seems to me that the manufacturer intended the mount to be used this way. But the documentation on this capability or connection is non existent. I bumped into something called phd2..it seems there is hope. Do I need a guide scope or can the mount take direction directly from phd2? Obviously i am somewhat confused. Any guidance out there? Thanks in advance.
  13. Hi, I am using the SA with a Canon 650D and a 300/4.0 L USM for some months now. In order to get longer exposure times (>30 sec) I just got a little guiding cam (TSGM120M: https://www.teleskop-express.de/shop/product_info.php/language/en/info/p8963_TS-Optics-Mono-Planetenkamera-und-Guidingkamera-mit-Aptina-CMOS-Chip.html). Stand alone guiding like the M-GEN II is way to expensive from my point of view, so I decided to use PHD(2) on a laptop to do the guiding. I use the Orion 50 mm Guide-Scope mounted on the second port of the L-Mount. But I don't know how to set up PHD2 to work with the SA. The guider-cam will be connected over USB to the laptop and over the ST-4 cable to the ST-4 port of the SA - now question about that. There are some users in the forum, who already work with PHD and the SA as far, as I have seen. So maybe someone could help me about what "Mount" and "Aux Mount" do I have to choose in the connection dialogue of PHD? How do I switch off DEC-guiding, as the SA doesn't provide it? Any experience with the dither function BackyardEOS provides with PHD2 connectivity? Many thanks in advance! Chris
  14. Starting doing guiding to assist with Astro-Photography rather than my usual "up to 30 second exposure". When I got the guiding going correctly you can see from the image that PHD2 was constantly correcting large errors. Could this be from wind? Although I i was sheltered, it still felt a little breezey at times so I'm wondering if that was possibly it. Thanks all My setup is Skywatcher 200p Skywatcher HEQ-5 Pro SynScan QHY5L-II Mono ST-4 on 9x50 Finderscope PHD2 in On-Camera configuration (I know that EQMOD is the more common way but I'm not quite there too ditch the SynScan yet and at some point I'll have to purchase a guide scope rather than using the Finderscope but I'm at the limit of the HEQ5 mount with the 2 counter weights)
  15. Does anyone know what the cyan bullseye targets are in PHD2? I accidentally discovered these, but can't work out what they're for. I've looked through the manual and done a few web searches but can't find any info. I just wondered if anyone know? If you press ctrl and then left click over the guide screen these appear. Is it anything I should know about? Am I missing something? Thanks
  16. Hi, Bit of a strange one. I have a NEQ6 which I control with EQASOM for imaging using SGP and PHD2 for guiding and have recently replaced the HC connection to the pc with an Lynx Astro FTDI EQdir cable. First time I used it it worked perfectly, it connected straight away, the guiding was good and SGP found the target without any issues. But I tried it again last night and whilst SGP worked perfectly, plate solved the image and moved directly to the target, PHD2 wouldn't connect to the scope. I selected the correct ASCOM mount from phd2 dropdown list but the EQASCOM connected briefly then disconnected with a display saying that it had failed to find the correct port. I tried adjusting the settings next to the mount selection tab and ensured it had pulse guiding selected but still no joy. As a result the phd2 software is not sending guide commands to the mount. The funny thing is that PHD2 will connect to EQASCOM if done so before SGP is connected but then the subsequent connection to SGP fails. But with PHD2 connected on its own its still not sending signals to the mount. Is this a faulty cable or is it a EQDIR driver problem or even an issue with PHD2 or EQASCOM? Any help would be appreciated as I am a loss as to how to rectify the situation. Thanks Dec
  17. Hi, I just got my new ASI174 MM Mini. I installed all the drivers from the CD and it worked right off in Sharpcap and Amcap. But then, when I tried to use it with PHD2, I was not able to connect to it. There are 3 options in PHD2's camera menu: ASI (ASCOM) 1 and 2 and, at the end of the list, ZWO ASI camera. None of them works. PHD2 just cannot find the camera. Anybody who can help? Thanks and cs, Pat
  18. Has anyone upgraded on Mac to "High Sierra" (OS 10.13) and had any issues with PHD2 or using Wine to run DSS, or any camera control software? I'm getting the notifications for the upgrade, but I'm worried some of my AP software (currently running on 10.12) won't work right before a big trip to a dark sky site in 2 weeks.
  19. Hey all, finally got some guiding going last night, but at the bottom right of PHD2, the word "CAL" is yellow (as opposed to green) and says "Calibration: Completed, but scope pointing info not available/not in-use" Does this mean PHD2/SSAG isn't sending data to the mount, or the mount isn't accepting the pushes? It's an AVX mount, and my PHD2 graph isn't great, but RA and Dec stay within about 3" either way. But I can't tell if guiding is doing anything to the mount, or if my images are turning out ok simply because of decent polar alignment and just tracking. Any ideas what the above text means? - Josh
  20. Hey all, after a massive guiding failure last night, I thought it was time to reach out! Last night was only the 2nd time I tried to guide with the new SSAG. The first time a few weeks back, I got the SSAG and PHD2 to "work" but the guiding was just ridiculously off. However, last night made me think something might be wrong. So... I realized that my SSAG has either a ton (dozens) of hot pixels or bad pixels, and nothing I did could get it to actually see any real stars, but those dozens of white dots remain whether the guide scope camera cap was on or off (see pic below, those aren't stars!). I actually had to detach the SSAG and just point it up at the moon to make sure the sensor was getting any light at all! It was! So, I tried all the fixes I've read on this and other forums, with no success. Even tried a bad pixel map calculation, which failed (also see pic). And I tried using dark library, which only created intense noise in the frame. PHD2 would allow me to select "begin looping" as well as "begin guiding", but I would get no RA or DEC lines on the graph, and all 0.00 on the history window (also see pic). PHD2 acknowledged that the camera and mount were connected, but "CAL" never turned from red to green. So I'm at a loss at the moment. Any chance this is faulty equipment? Normally I assume it's just me. Any help would be greatly appreciated! - Josh P.S. I finally nailed my polar alignment last night! So I don't think that was the source of my problems. AVX mount, Celestron C8N, 50mm guide scope
  21. Hi, So, I have a minor setup issue for my automation setup. Here is a brief overview of my setup: Raspberrypi on the scope connected to a powered usb hub. Connected to the hub are a external wifi card (raspberry pi3 wifi is weak), an astromodified Canon 550D, a QHY5L-II for guiding and an EQ6 pro mount. The camera and QHY are connected to an OAG. The QHY5 is also connected to the mounts ST4 port. On the Rasperry Pi 3 I am running xubuntu with INDI server and PHD2 installed. Using realvnc to view phd2. indi server + webserver starts on boot, static ip on external wifi card starts on boot. On my laptop I have EKOS to connect to indi server and phd2 for guiding. I am running phd2 on the raspberrypi to hopefully this will let PHD2 have a more direct (faster) connection to the guide camera. My issue: Their appears to be a disabled install of ufw which has some groups under iptables. I enabled the ufw and enbled the ports 4400, 7642 (PHD2), 8624 (indiweb), 7624(indi) however the guiding suite of Ekos would not connect to PHD2. I disabled ufw and flushed the iptables and tried again with the above ports however the same result. In the end I have opened all the ports to allow the connection to proceed, which is ok for short term but ideally I would want some security. Does anyone know which ports I should open to get indi, indiweb and phd2 to talk nicely to my laptop EKOS version? Anyone else running a similar setup successfully? Can you give me any indications of what pitfalls to avoid? Thanks
  22. Hello All Im using a eq6 and I'm having all sorts of problems with my guiding. I used to be without guider to get 2 minutes easily but now I'm struggling to get good shots whatever I choose. So first of all EQMOD what do people use for the RA settings for the autoguider in EQMOD? I have fiddled about with every one of them but no real improvement. What do others use? In PHD2 I have done the settings for my guide camera which is a asi120mm and the focal length of the scope is done along with the sensor size. On the PHD I've moved just about everything and nothing seems to work well enough. Can anyone give me their basic settings to see if that helps. The only thing I've changed is my way to do polar alignment I'm now using the EQMOD polar align process which might have affected it but I'm still getting objects on my gotos so I was wondering if cone error would do it also? Is drift alignment essential? I don't think so. I did do it on the south meridian as I've got views that way but not so much on the north. Help! Please guys and girls I wasted a whole session just fiddling and ended up with 8 exposures of M20 which you can see below.
  23. I'm a newbie in this hobby and last week end I had the opportunity to start testing my setup with guiding. I read a couple PHD2 tutorials and went on with it, I was successful taking 480sec exposures with round stars, so I pretty happy with my first attempt. My question is related with the Calibration data produced by PHD2, please check bellow my data: I'm not fully understanding the data.. 1) I assume a perfect tuned mount RA and DEC should align with the 90º graph scale. 1.a) Is this the orthogonality error ? 2) If my assumption is right, how do I correct the deviation ? 3) What are the white dots ? 4) Why the read and green lines do not align with the dots ? 5) What should I conclude concerning the performance of my mount by looking at the data ? I know.. a lot of questions.. Just a bit of context, my setup is a NEQ6 with an ED80 (0x85 reducer), for guiding I have a TSL80 (328mm) with an ASI120, btw the NEQ6 is fully stock. Thanks, -jb
  24. Hi All, i have recently purchased a star tech powered USB hub and 25m of CAT6e cable and connected it up to my NEQ6 mount, Canon 700d, and Star shoot autoguider (through PHD2). The problem is that everything works fine apart from the autoguider. PHD2 connects ok to the mount and camera but won't loop exposures. I keep getting Error 31 connection to device has failed. Any suggestions on what the problem could be? Thanks
  25. Tarantula Nebula ( NGC 2070 ) in the Large Magellanic Cloud ( LMC ) Re-processed to tweak colour balance and bring out a little more faint detail: New version: Original: ( click/tap on image to see full size - the above compressed version looks a little soft; the full size version is sharper ) The Tarantula Nebula ( NGC 2070 ) is the largest and brightest emission nebula in the nearby irregular galaxy, the Large Magellanic Cloud ( LMC ). At a distance of 160,000 light years away from us, the Tarantula Nebula is so bright that it would cast shadows on the Earth if were as close to us as the Orion Nebula in our galaxy. First image with new telescope and autoguider/setup. Links: 500px.com/MikeODay photo.net/photos/MikeODay Details: Nebulae: NGC 2070 Tarantula Nebula NGC 2048 NGC 2060 NGC 2077. Open clusters: NGC 2042 NGC 2044 NGC 2050 NGC 2055 NGC 2091 NGC 2093 NGC 2100 Image centre RA 5h 38m 57.3s, Dec -69deg 20' 36.6" (nova.astrometry.net) Field of view (arcmin): 58.7 x 39.2 Scale (full size image) 0.585 arcsec/pixel. Telescope: Orion Optics CT12 Newtonian ( mirror 300mm, FL1200mm, f4 ) Corrector: ASA 2" Coma Corrector Quattro 1.175x Effective Focal Length / Aperture ): 1410mm f4.7. Mount: Skywatcher AZ Eq6 GT Guiding: TSOAG9 Off-Axis-Guider, Starlight Xpress Lodestar X2, PHD2 Camera: Nikon D5300 (unmodified) (sensor 23.5 x 15.6mm, 6016x4016 3.9um pixels) Filter: none Exposures: 14 x 240 sec ISO400 12 x 120 sec ISO400 10 x 60 sec ISO400 11 x 60 sec ISO200 10 x 60 sec ISO100 10 x 30 sec ISO100 Pixinsight & Photoshop 20 December 2016
  • Create New...

Important Information

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