Recently Browsing 0 members
No registered users viewing this page.
So I routinely have issues with guiding. Last night, I was getting some solid sub exposures of 5 minutes on the Flaming Star Nebula. When it got to about 15-20minutes of the meridian, I began getting trails on my stars. Then after the flip, I was still getting trails despite PHD reporting all's well. I moved over to the Horsehead Nebula and tried 5 minutes there, and it behaved itself. Then I tested it on the Jellyfish Nebula and it also behaved (just about - minor trails). But it just did not want to dig it with the Flaming Star Nebula, which was practically near the zenith (about 2:30am 30/11/19).
I tried recalibrating PHD (I use Pulseguide so the scope knew where it was). I then also recalibrated PHD at Alnitak so it was near the celestial equator (as the PHD best practices recommend). I even checked my Polar Alignment (done with a Polemaster), which was fine. I couldn't find anything wrong.
The guide scope was slightly off alignment with the main OTA, but that wasn't making any differences before the Meridian.
I did find the helical focuser of the Starwave 50mm guide scope I was using to have some movement in it again when I manipulated the guide camera. So that's something I need to look into. But before I start throwing money at this issue, I see the terms "flexure" and "differential flexure" coming up. Can anyone shed light on what this means please?
I tried manipulating the OTA in its tube rings, that didn't yield any movement either. The piggyback scope is secure, the g/scope is secure in its rings as well, there's no movement in the OTA focus rack and the cameras are secure in their tubes.
I do have my guide rings quite far back on the body of the telescope to assist with fitting the guide scope piggyback.
Video of g/scope play:
Flaming Star Nebula. 5 minute sub, post Meridian Flip, about 2:50am (30/11/19). Note the plate solve compass in the top left. Drift appears to be in S/W direction.
Position of tube rings (they're now at the focus end).
I think I am leaning towards needing to move my tube rings (once I remember to get the tools from work).
(brand new) Skywatcher EQ6-R Pro, SW Evostar Pro 80ED, Altair 0.8x R/F, Canon 600D, Altair Starwave 50mm Guide Scope, Altair AR130 Mono Guide Cam.
By John Lawley
Hi - I've not posted here before as only just launched into this hobby, although I've always been massively interested in astronomy.
I had first light on my rig last night, which is:
Esprit 100, HEQ 5 Pro, ZWO EAF, ZWO mini filter wheel, skywatcher 50ED guidscope with ASI120, ZWO1600mm Pro, Lynx dew controller w 2 astro zap tapes
A big endeavour to get that lot working from zero experience, but I love a challenge and have really enjoyed the computer side (I'm a grade A nerd)...
So - what went well... I got the guide scope in focus (was stressing about this), and also the main scope. Even more awesomely, the autofocus routine in SGP is working perfectly Filter wheel also working perfectly and I'm getting lovely smooth pics from the main camera (I've already done the flats and darks while I was waiting for clouds to clear). Final good thing (well, good-ish), is that I got the platesolving working eventually, and was able to get the scope to align from Park to the Soul Nebula and centre fine. For some reason the "number of attempts" in my SGP profile hadn't applied, so it was giving up after 1 go, but I got it working in the end.
So the bad...
I couldn't take any data because every time it finished the platesolving and started PHD2, PHD2 would start the calibration process and then halfway through, the sidereel tracking on the EQMOD panel would turn off. Obviously, that would lead to a "lost the star" error. Is there some reason why sidereel tracking would turn off like that? I'm generally a bit confused as to whether I should be controlling the telescope from SGP (i.e. unpark) or using the park and unpark + tracking button on the EQMOD panel. Both PHD 2 and SGP are setup to use EQMOD ASCOM HEQ5/6?
So at the moment I can't do anything, because there's no way of guiding without it turning tracking off
Also I was cold. Very Very Cold.
From AST Optics selling my mini guiding system that i used for my Redcat51 , i have used it also with my Esprit 100 and had excellent guiding results.
There is a nice review here if someone wants to read :
Lens: f=100mm F3.5 CCTV objective - made in Japan
Adjustment: by ballhead - with reliable clamping
Dovetail: compatible with most finder shoes
True field of view: 2.9° x 3.8°
Maximum guidable focal length: 1000 mm
Focusing: via lens cell
Connection to camera: C-Mount
Lens filter thread: M30.5mm P=0.5
Weight: 79 grams
Length of the objective: 44 mm
PRICE : £100 (selling the mount and the CCTV lens not the camera)
Paypal accepted buyer pays the fees
I will cover the postage expenses
Hi guys, it's my first post here, so Hello!
My synscan goto upgrade started to act like in this video of mine SynScan GOTO Skipping after being disassembled for few weeks in the closet. There were no such problems before.
When it slews at rates above x3 everything is fine and smooth but as soon as it starts tracking at x3, it skips steps or something like that.
My setup is eq3-2 on alu and SW 150/750 with Canon 700D attached.
Thanks in advance for any clues or ideas!
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.