Recently Browsing 0 members
No registered users viewing this page.
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.
I have recently bought a Orion Starshoot Autoguider. I downloaded phd 2, eqmod and ascom stuff. After a small research I found out my mount (exos 2 gt) doesn't support computer acces without firmware upgrade and fancy cables but I have the st4 port so it shouldn't be a problem. In phd I choose camera as Starshoot Autoguider and mount On-Camera. Aux mount and AO are both none. My wiring is one cable to pc from camera and another to st4 port from camera. When I started looping I selected the star with no problem. I choosed the one star alignment option from my hand controller and after centering the Archturus in the middle of view I pressed ok and it was successfull. I started guiding and after a while I get the error: RA calibration failed star didn't move enough.
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.
Has anybody else had this problem?
I use a single, ageing laptop (HP620 8Gb RAM) running Windows 7 Pro 64bit to control my imaging setup using the following software;
Cartes du Ciel and EQMOD to control EQ5 Pro mount via EQDIRECT cable connected via powered USB Hub
BackyardEOS to capture images from Canon 450D via same USB powered hub
PHD2 for guiding using GP-CAM 130C and EQMOD pulse guiding
What confuses me is that some evenings everything works absolutely fine. Another evening, using exactly the same hardware, software and even connections (ie I always plug the leads into the same ports) the system will be working fine but then suddenly fail. The failure affects EQMOD indicating a timeout or port not available issue and the Canon 450D also 'locks' requiring a restart of the camera and BackyardEOS.
I have run USBTree during such a failure and it is showing that the EQDIRECT cable (ie serial converter) is still connected to COM4 (which is correct) and the Canon 450D is also still connected. I basically have to ensure that all the software is closed and any associated services also stopped. Of course, the scope is now pointing away from its home position so I have to move it manually back to 'home' before starting again.
My thoughts are that there could be a number of issues;
1. Use of a USB hub
2. A dodgy EQDIRECT cable
3. USB cables too long (ie about 5m)
4. Windows is turning off a connection (I have set the power management for each USB port to 'off')
5. Canon 450D somehow 'freezing'
When using this laptop, I turn off the Wifi and Anti Virus and Automatic Updates are also off.
It just baffles me that sometimes this system works flawlessly for hours and yet other nights it keeps failing.
Any suggestions gratefully received.
Thanks for looking.