Recently Browsing 0 members
No registered users viewing this page.
As my GoTo is successfully finished (some cosmetic issues remain) I shoud focus my attention on planets' positions. I have proper source of information: fantastic book "Astronomical Algorithms" by Jean Meeus, thus I will sort the planets soon. But planets are not a challenge for me at this moment, they are just something obvious to do in my list.
I have another idea and ambitious plan for next project within the year: locating and tracking the ISS to be able to make a video of its fly, not only transition.
Similarly to other objects, I need some equations. I'm pretty sure they are available somewhere, because plenty websites or apps offer showing current position of the ISS.
I will use this topic for sharing a progress ot the project.
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 am only a few weeks into astronomy and started off with a Celestron 9.25" Evo on the standard AZ mount. I guess with hindsight this wasn't the best place to start and also with hindsight I would have done better to have bought a GEM mount. Anyway, lesson learned and at 71 years old I have to speed up the learning process compared to younger enthusiasts I have 2 issues. 1/ Its a pain dragging the scope out into the garden and setting it up every time I think the fickled weather might be obliging. 2/ I now know that the mount I have is useless for long exposures and a wedge is fiddly to get polar aligned.
My question is, though I gather wedges are a PITA to setup etc is if I was to build or buy a pier for the backyard and use my existing mount + a wedge is this a reasonable way to go? Though it's fiddly to set the thing up once set I could leave the mount, wedge, etc covered up and would just need to drop the OTA on when I wanted to use it. Is this reasonable or am I missing something fundamental down near the bottom end of my learning curve
Any advice much appreciated and don't feel you have to spare my feelings
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.