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.

stargazine_ep20_banner.thumb.jpg.c34e90166f1f5aa93f5211765a962cda.jpg

Search the Community

Showing results for tags 'phd2'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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
    • StarGaZine
    • 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

Calendars

  • 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

Blogs

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Interests


Location

Found 44 results

  1. From the album: CCD venture

    A h-alpha shot of the pelican nebula in Cygnus. 2 x panel mosaic. 10 min subs. 9 x 10m + 9x10m stacks stitched together in ms ICE. ED80 - ATK16HR - Ha clip filter - EQ6 - finderguider 9x50mm PhD2 - photoshop - DSS.
  2. 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.
  3. 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
  4. 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.
  5. 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
  6. 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.
  7. 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)
  8. 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
  9. 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
  10. 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.
  11. 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
  12. 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
  13. Guys and girls, I desperately need your help! Last night I spent hours trying to get PhD2 to track. I must admit that I not know what to do. The problem: the guiding cam's picture continuously moves to the south, fast (about 5 microns evry 3-5 seconds) - i suspect a PA eror - BUT astrotortilla claims that my pa error is only 8 minutes- according to a pa error calculation site, this is insane- maybe astrotortilla is computing the pa error incorrectly? Which errors did i check? I do know that PhD two is connected correctly to the mount. I can hear the motors running when i manually correct the position. According to Astrotortilla, my PA error is approx. 8 minutes. The mount is connected via ASCOM drivers. The guiding rate was too low at first (0.1x the sidereal rate; corrected that to 0.9x the sidereal rate) The focal length of the guide scope is correctly set up (162 mm) PHD2 is set up to immediately correct. Target was NGC 6992 yesterday night at around 0130CEST. When the problem was most critical, 6992 was at max. 72 deg altitude. ===> From my limited knowledge, it looks like the PA is so far off that PHD2 cant correct it... but with 8 min PA error??? I am pasting my settings: Plus two iterations of my log?! 01:28:10.645 00.000 3856 Worker thread wakes up 01:28:10.645 00.000 3856 worker thread servicing REQUEST_EXPOSE 1500 01:28:10.645 00.000 3856 Handling exposure in thread 01:28:10.661 00.016 4044 IsSlewing returns 0 01:28:10.661 00.000 4044 IsGuiding returns 0 01:28:10.661 00.000 4044 Movement stopped - continuing 01:28:10.692 00.031 4044 PulseGuide returned control before completion, sleep 483 01:28:11.177 00.485 4044 IsGuiding returns 1 01:28:11.177 00.000 4044 scope still moving after pulse duration time elapsed 01:28:11.192 00.015 4044 IsSlewing returns 0 01:28:11.192 00.000 4044 IsGuiding returns 1 01:28:11.208 00.016 4044 IsSlewing returns 0 01:28:11.208 00.000 4044 IsGuiding returns 1 01:28:11.239 00.031 4044 IsSlewing returns 0 01:28:11.239 00.000 4044 IsGuiding returns 1 01:28:11.255 00.016 4044 IsSlewing returns 0 01:28:11.255 00.000 4044 IsGuiding returns 1 01:28:11.270 00.015 4044 IsSlewing returns 0 01:28:11.270 00.000 4044 IsGuiding returns 1 01:28:11.302 00.032 4044 IsSlewing returns 0 01:28:11.364 00.062 4044 IsGuiding returns 1 01:28:11.380 00.016 4044 IsSlewing returns 0 01:28:11.380 00.000 4044 IsGuiding returns 1 01:28:11.395 00.015 4044 IsSlewing returns 0 01:28:11.395 00.000 4044 IsGuiding returns 1 01:28:11.427 00.032 4044 IsSlewing returns 0 01:28:11.427 00.000 4044 IsGuiding returns 1 01:28:11.442 00.015 4044 IsSlewing returns 0 01:28:11.442 00.000 4044 IsGuiding returns 1 01:28:11.458 00.016 4044 IsSlewing returns 0 01:28:11.458 00.000 4044 IsGuiding returns 1 01:28:11.489 00.031 4044 IsSlewing returns 0 01:28:11.489 00.000 4044 IsGuiding returns 1 01:28:11.505 00.016 4044 IsSlewing returns 0 01:28:11.505 00.000 4044 IsGuiding returns 1 01:28:11.520 00.015 4044 IsSlewing returns 0 01:28:11.520 00.000 4044 IsGuiding returns 1 01:28:11.552 00.032 4044 IsSlewing returns 0 01:28:11.552 00.000 4044 IsGuiding returns 1 01:28:11.614 00.062 4044 IsSlewing returns 0 01:28:11.645 00.031 4044 IsGuiding returns 0 01:28:11.645 00.000 4044 scope move finished after 500 + 486 ms 01:28:11.645 00.000 4044 Move returns status 0, amount 500 01:28:11.645 00.000 4044 scope calibration move dir= 2 dur= 500 01:28:11.645 00.000 4044 Move(2, 500, 0) 01:28:11.645 00.000 4044 Guiding Dir = 2, Dur = 500 01:28:11.645 00.000 4044 IsSlewing returns 0 01:28:11.645 00.000 4044 IsGuiding returns 0 01:28:11.677 00.032 4044 PulseGuide returned control before completion, sleep 480 01:28:12.161 00.484 4044 IsGuiding returns 1 01:28:12.161 00.000 4044 scope still moving after pulse duration time elapsed 01:28:12.177 00.016 4044 IsSlewing returns 0 01:28:12.177 00.000 4044 IsGuiding returns 1 01:28:12.208 00.031 4044 IsSlewing returns 0 01:28:12.208 00.000 4044 IsGuiding returns 1 01:28:12.223 00.015 4044 IsSlewing returns 0 01:28:12.223 00.000 4044 IsGuiding returns 1 01:28:12.239 00.016 4044 IsSlewing returns 0 01:28:12.239 00.000 4044 IsGuiding returns 1 01:28:12.270 00.031 4044 IsSlewing returns 0 01:28:12.270 00.000 4044 IsGuiding returns 1 01:28:12.286 00.016 4044 IsSlewing returns 0 01:28:12.286 00.000 4044 IsGuiding returns 1 01:28:12.317 00.031 4044 IsSlewing returns 0 01:28:12.317 00.000 4044 IsGuiding returns 1 01:28:12.395 00.078 4044 IsSlewing returns 0 01:28:12.395 00.000 4044 IsGuiding returns 1 01:28:12.427 00.032 4044 IsSlewing returns 0 01:28:12.427 00.000 4044 IsGuiding returns 1 01:28:12.442 00.015 4044 IsSlewing returns 0 01:28:12.442 00.000 4044 IsGuiding returns 1 01:28:12.458 00.016 4044 IsSlewing returns 0 01:28:12.473 00.015 4044 IsGuiding returns 1 01:28:12.489 00.016 4044 IsSlewing returns 0 01:28:12.489 00.000 4044 IsGuiding returns 1 01:28:12.505 00.016 4044 IsSlewing returns 0 01:28:12.505 00.000 4044 IsGuiding returns 1 01:28:12.536 00.031 4044 IsSlewing returns 0 01:28:12.536 00.000 4044 IsGuiding returns 1 01:28:12.552 00.016 4044 IsSlewing returns 0 01:28:12.552 00.000 4044 IsGuiding returns 1 01:28:12.567 00.015 4044 IsSlewing returns 0 01:28:12.567 00.000 4044 IsGuiding returns 1 01:28:12.598 00.031 3856 Exposure complete 01:28:12.598 00.000 4044 IsSlewing returns 0 01:28:12.630 00.032 3856 worker thread done servicing request 01:28:12.677 00.047 4044 IsGuiding returns 0 01:28:12.677 00.000 4044 scope move finished after 500 + 522 ms 01:28:12.677 00.000 4044 Move returns status 0, amount 500 01:28:12.677 00.000 4044 Processing an image 01:28:12.677 00.000 4044 UpdateGuideState(): m_state=6 01:28:12.677 00.000 4044 Star::Find(0x017E0E08, 50, 940, 495) 01:28:12.677 00.000 4044 Star::Find returns 1, X=940.39, Y=496.62 01:28:12.677 00.000 4044 SchedulePrimaryMove(001E2608, x=-2.97, y=7.30, normal=1) 01:28:12.677 00.000 4044 Enqueuing Move request for scope (-2.97, 7.30) 01:28:12.677 00.000 4044 Status Line 0: m=260605 SNR=56.4 01:28:12.677 00.000 3856 Worker thread wakes up 01:28:12.677 00.000 3856 worker thread servicing REQUEST_MOVE scope dir 0 (-2.97, 7.30) 01:28:12.677 00.000 3856 Handling move in thread for scope dir=0 01:28:12.677 00.000 4044 UpdateImageDisplay: Size=(1280,1024) min=0, max=63744, FiltMin=640, FiltMax=31232 01:28:12.677 00.000 3856 endpoint = (-2.97, 7.30) 01:28:12.677 00.000 3856 CameraToMount -- cameraTheta (1.96) - m_xAngle (-0.52) = xAngle (2.48 = 2.48) 01:28:12.677 00.000 3856 CameraToMount -- cameraTheta (1.96) - (m_xAngle (-0.52) + m_yAngleError (-1.06)) = yAngle (3.54 = -2.74) 01:28:12.677 00.000 3856 CameraToMount -- cameraX=-2.97 cameraY=7.30 hyp=7.88 cameraTheta=1.96 mountX=-6.22 mountY=-3.05, mountTheta=-2.69 01:28:12.677 00.000 3856 Moving (-2.97, 7.30) raw xDistance=-6.22 yDistance=-3.05 01:28:12.677 00.000 3856 GuideAlgorithmHysteresis::Result() returns -6.22 from input -6.22 01:28:12.677 00.000 3856 GuideAlgorithmResistSwitch::Result() returns -3.05 from input -3.05 01:28:12.677 00.000 3856 Move(2, 279, 1) 01:28:12.677 00.000 3856 Guiding Dir = 2, Dur = 279 01:28:12.677 00.000 3856 IsSlewing returns 0 01:28:12.677 00.000 3856 IsGuiding returns 0 01:28:12.708 00.031 3856 PulseGuide returned control before completion, sleep 262 01:28:12.723 00.015 4044 Resizing image to 506,405 01:28:12.739 00.016 4044 UpdateGuideState exits:m=260605 SNR=56.4 01:28:12.739 00.000 4044 OnExposeCompete: CaptureActive=1 m_continueCapturing=1 01:28:12.739 00.000 4044 ScheduleExposure(1500) 01:28:12.739 00.000 4044 Enqueuing Expose request 01:28:12.739 00.000 4044 scope calibration move dir= 2 dur= 500 01:28:12.739 00.000 4044 Move(2, 500, 0) 01:28:12.739 00.000 4044 Guiding Dir = 2, Dur = 500 01:28:12.739 00.000 4044 IsSlewing returns 0 01:28:12.739 00.000 4044 IsGuiding returns 1 01:28:12.739 00.000 4044 Entered PulseGuideScope while moving 01:28:12.786 00.047 4044 IsSlewing returns 0 01:28:12.786 00.000 4044 IsGuiding returns 1 01:28:12.786 00.000 4044 Still moving 01:28:12.848 00.062 4044 IsSlewing returns 0 01:28:12.848 00.000 4044 IsGuiding returns 1 01:28:12.848 00.000 4044 Still moving 01:28:12.927 00.079 4044 IsSlewing returns 0 01:28:12.927 00.000 4044 IsGuiding returns 1 01:28:12.927 00.000 4044 Still moving 01:28:12.958 00.031 3856 IsGuiding returns 1 01:28:12.958 00.000 3856 scope still moving after pulse duration time elapsed 01:28:12.973 00.015 4044 IsSlewing returns 0 01:28:12.973 00.000 4044 IsGuiding returns 1 01:28:12.973 00.000 4044 Still moving 01:28:12.989 00.016 3856 IsSlewing returns 0 01:28:12.989 00.000 3856 IsGuiding returns 1 01:28:13.005 00.016 3856 IsSlewing returns 0 01:28:13.005 00.000 3856 IsGuiding returns 1 01:28:13.036 00.031 3856 IsSlewing returns 0 01:28:13.036 00.000 4044 IsSlewing returns 0 01:28:13.036 00.000 3856 IsGuiding returns 1 01:28:13.036 00.000 4044 IsGuiding returns 1 01:28:13.036 00.000 4044 Still moving 01:28:13.052 00.016 3856 IsSlewing returns 0 01:28:13.052 00.000 3856 IsGuiding returns 1 01:28:13.067 00.015 3856 IsSlewing returns 0 01:28:13.067 00.000 3856 IsGuiding returns 1 01:28:13.083 00.016 4044 IsSlewing returns 0 01:28:13.083 00.000 4044 IsGuiding returns 1 01:28:13.083 00.000 4044 Still moving 01:28:13.098 00.015 3856 IsSlewing returns 0 01:28:13.098 00.000 3856 IsGuiding returns 1 01:28:13.114 00.016 3856 IsSlewing returns 0 01:28:13.114 00.000 3856 IsGuiding returns 1 01:28:13.177 00.063 4044 IsSlewing returns 0 01:28:13.177 00.000 4044 IsGuiding returns 1 01:28:13.177 00.000 4044 Still moving 01:28:13.177 00.000 3856 IsSlewing returns 0 01:28:13.177 00.000 3856 IsGuiding returns 1 01:28:13.223 00.046 3856 IsSlewing returns 0 01:28:13.223 00.000 3856 IsGuiding returns 0 01:28:13.223 00.000 3856 scope move finished after 279 + 277 ms 01:28:13.223 00.000 3856 Move returns status 0, amount 279 01:28:13.223 00.000 3856 Move(0, 500, 1) 01:28:13.223 00.000 3856 Guiding Dir = 0, Dur = 500 01:28:13.223 00.000 3856 IsSlewing returns 0 01:28:13.239 00.016 3856 IsGuiding returns 0 01:28:13.302 00.063 4044 IsSlewing returns 0 01:28:13.302 00.000 3856 PulseGuide returned control before completion, sleep 434 01:28:13.302 00.000 4044 IsGuiding returns 1 01:28:13.317 00.015 4044 Still moving 01:28:13.364 00.047 4044 IsSlewing returns 0 01:28:13.364 00.000 4044 IsGuiding returns 1 01:28:13.364 00.000 4044 Still moving 01:28:13.442 00.078 4044 IsSlewing returns 0 01:28:13.442 00.000 4044 IsGuiding returns 1 01:28:13.442 00.000 4044 Still moving 01:28:13.489 00.047 4044 IsSlewing returns 0 01:28:13.489 00.000 4044 IsGuiding returns 1 01:28:13.489 00.000 4044 Still moving 01:28:13.536 00.047 4044 IsSlewing returns 0 01:28:13.536 00.000 4044 IsGuiding returns 1 01:28:13.536 00.000 4044 Still moving 01:28:13.598 00.062 4044 IsSlewing returns 0 01:28:13.598 00.000 4044 IsGuiding returns 1 01:28:13.598 00.000 4044 Still moving 01:28:13.708 00.110 4044 IsSlewing returns 0 01:28:13.708 00.000 4044 IsGuiding returns 1 01:28:13.708 00.000 4044 Still moving 01:28:13.739 00.031 3856 IsGuiding returns 1 01:28:13.739 00.000 3856 scope still moving after pulse duration time elapsed 01:28:13.755 00.016 4044 IsSlewing returns 0 01:28:13.755 00.000 4044 IsGuiding returns 1 01:28:13.755 00.000 4044 Still moving 01:28:13.770 00.015 3856 IsSlewing returns 0 01:28:13.770 00.000 3856 IsGuiding returns 1 01:28:13.786 00.016 3856 IsSlewing returns 0 01:28:13.786 00.000 3856 IsGuiding returns 1 01:28:13.801 00.015 3856 IsSlewing returns 0 01:28:13.801 00.000 3856 IsGuiding returns 1 01:28:13.817 00.016 4044 IsSlewing returns 0 01:28:13.817 00.000 4044 IsGuiding returns 1 01:28:13.817 00.000 4044 Still moving 01:28:13.833 00.016 3856 IsSlewing returns 0 01:28:13.833 00.000 3856 IsGuiding returns 1 01:28:13.848 00.015 3856 IsSlewing returns 0 01:28:13.848 00.000 3856 IsGuiding returns 1 01:28:13.864 00.016 4044 IsSlewing returns 0 01:28:13.864 00.000 4044 IsGuiding returns 1 01:28:13.864 00.000 4044 Still moving 01:28:13.864 00.000 3856 IsSlewing returns 0 01:28:13.880 00.016 3856 IsGuiding returns 1 01:28:13.895 00.015 3856 IsSlewing returns 0 01:28:13.895 00.000 3856 IsGuiding returns 1 01:28:13.958 00.063 4044 IsSlewing returns 0 01:28:13.958 00.000 3856 IsSlewing returns 0 01:28:13.958 00.000 4044 IsGuiding returns 1 01:28:13.958 00.000 4044 Still moving 01:28:13.958 00.000 3856 IsGuiding returns 1 01:28:13.989 00.031 3856 IsSlewing returns 0 01:28:13.989 00.000 3856 IsGuiding returns 1 01:28:14.005 00.016 3856 IsSlewing returns 0 01:28:14.005 00.000 3856 IsGuiding returns 1 01:28:14.020 00.015 4044 IsSlewing returns 0 01:28:14.020 00.000 4044 IsGuiding returns 1 01:28:14.020 00.000 4044 Still moving 01:28:14.036 00.016 3856 IsSlewing returns 0 01:28:14.036 00.000 3856 IsGuiding returns 1 01:28:14.051 00.015 3856 IsSlewing returns 0 01:28:14.051 00.000 3856 IsGuiding returns 1 01:28:14.067 00.016 4044 IsSlewing returns 0 01:28:14.067 00.000 4044 IsGuiding returns 1 01:28:14.067 00.000 4044 Still moving 01:28:14.067 00.000 4044 Still moving after 1s - aborting 01:28:14.067 00.000 4044 Error thrown from scope_ascom.cpp:568->ASCOM Scope: scope is still moving after 1 second 01:28:14.067 00.000 4044 Error thrown from scope.cpp:544->guide failed 01:28:14.067 00.000 4044 Move returns status 1, amount 0 01:28:14.067 00.000 4044 Throw from scope.cpp:464->Move failed 01:28:14.067 00.000 3856 IsSlewing returns 0 01:28:14.067 00.000 3856 IsGuiding returns 1 01:28:14.098 00.031 3856 IsSlewing returns 0 01:28:14.098 00.000 3856 IsGuiding returns 1 01:28:14.114 00.016 3856 IsSlewing returns 0 01:28:14.114 00.000 3856 IsGuiding returns 1 01:28:14.130 00.016 3856 IsSlewing returns 0 01:28:14.130 00.000 3856 IsGuiding returns 1 01:28:14.145 00.015 4044 Resizing image to 506,405 01:28:14.208 00.063 3856 IsSlewing returns 0 01:28:14.208 00.000 3856 IsGuiding returns 1 01:28:14.223 00.015 3856 IsSlewing returns 0 01:28:14.223 00.000 3856 IsGuiding returns 1 01:28:14.255 00.032 3856 IsSlewing returns 0 01:28:14.255 00.000 3856 IsGuiding returns 0 01:28:14.255 00.000 3856 scope move finished after 500 + 520 ms 01:28:14.255 00.000 3856 Move returns status 0, amount 500 01:28:14.255 00.000 3856 Status Line 1: Ost 6.22 px 279 ms Norden 3.05 px 500 ms 01:28:14.255 00.000 3856 Ost 6.22 px 279 ms Norden 3.05 px 500 ms 01:28:14.255 00.000 3856 move complete, result=0 01:28:14.255 00.000 3856 worker thread done servicing request 01:28:14.255 00.000 3856 Worker thread wakes up
  14. I have been reading the PHD2 manual and have noted the statement: "The settings for 'Use Dark Library' and 'Use Bad-pixel Map' are mutually exclusive - you can use one or neither, but not both at the same time". So, in order not to reinvent the wheel, a question for those of you who use PHD2. Which, if either, do you find works best? Or. if it isn't that simple (and when is it ever?), what are the main things I should consider in making the decision? Thanks.
  15. 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
  16. 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.
  17. Hi can anyone help me with some basic settings in the software for PHD2, ive used it for some time now, but I dont think my settings are right. And on top of that im still trying to get better polar alignment. Im guiding long focal length, (piggy backing my w/o zenithstar to my mak newt, to aliviate the issues on my images), ive been trying to use the drift alignment tool, but im finding that my trendlines are to erratic (another reason I feel my settings are wrong). So the mak is at the moment my guidescope which is 1000mm, and im imaging through a much shorter focal length zenithstar. My settings at the mo are (on PHD2)............. "Guiding".........search region pixels...15, enable mass star detection with a tolerance of 50.0, focal length 1000mm, once in calibration its... pixel size micron 7.40 (guide camera is atik 16IC mono), calibration steps 15, calibration declination, degrees 14, calibration steps, ms 350, then in algorithym tab.........RA...hysteresis 10, aggressiveness 20, minimum move 0.40, max RA duration is 2645, and then DEC hysteresis 10, aggressiveness 20, minimum move 0.90, backlash comp 0, max dec duration is 2500, dec guide mode is auto. My mount is a losmandy G11, (standard not go-to Gemini), and my guiding rate is 0.5.....which I put in the PHD2 settings. my camera exposure durations are set to 1.5 sec as well. If anyone can help me to get at lease some of my settings better then I would be very grateful. If I can get my settings right then I can maybe go back to the drift alignment tool and go from there to get better PA. Many thanks.............
  18. In the past my PHD2 guiding has been fine for months then it goes funny. It's gone funny again. It is windy out but Im in a sheltered observatory (roll off roof shed). The screen is changing from black, to grey, maybe light grey then grey again. And check out the graphs - the blue line keeps rising, might sort itself out, then started rising again?! Help! IMG_7205.MOV Once I have saved up for my ATIK460EX I am seriosuly considering an OAG or something to never have to struggle with PHD again!
  19. Dear all, please can you help out a beginner to the software PHD2. I am attempting to guide an ED80 scope on an EQ5 Synscan mount with an ASI 120MC camera on a 9x50 finderscope. I have connected an ST4 cable from the mount to the camera and I can see that the mount does converse with the camera and corrections are given succesfully. The problem I having is seen at the end of the calibration step. I keep getting an orthagonality error which is always massive - usually around 50-60 degrees when it should be less than 10. If I accept the calibration then guiding performance is absolute rubbish. I have on one of the 5 occasions I have tried to guide managed to get a calibration where the orthagonality error value was about 20 and the guiding performance was pretty good leading to 8minute subs. I ensure that my polar alignment is as good as possible and I can't see any obvious scope balancing problems. Please suggest remedies or can it be only due to poor scope balance? thanks in advance
×
×
  • Create New...

Important Information

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