Recently Browsing 0 members
No registered users viewing this page.
First of all mine english is not so good so sorry for that.
I am a new to astrophotography. And my setup is
Mount : Skywatcher EQM 35 PRO
Tube : Skywatcher Explorer 150PDS (newtonian)
Camera : Canon 550D
Guide scope : Svbony 60mm compact guide scope
Guide cam : Svbony SV105
I know my setup is weak and cheap but for now I have them (budged problem )
I started the hobby at May and I took some photos that not bad for beggining. I reached 60-90 seconds without guiding.
After that I thought that the time for starting improve the guiding and I bought guiding scope and cam. I know the cam is not for guiding but it was cheap, and I am planing to change it with mono guide cam (like zwo asi120 mono) at next months.
But my first experience for PHD2 was terrible.
I've detected some errors and tried to fix them.
First thing there was a unbalancing. I mounted the guide scope on the position of finder scope which is very close to edge of the main scope.
So I fixed it (after the night I tried to guide with PHD2) and put it on the bracelet (over and middle of the main tube)
And second thing was that there is a backlash and I tried to fix it too. I opened to gear of dec and adjusted to gear mesh.
Except them the alignment was not so good because location was in the city (bortle scale 9) and I haven't got finder scope as you know. So I am not sure that if the stars (3 star alignment method) are correct because with nacked eye I could't see them. Next time I will do better alignment with finder for sure.
After them I am planing to try next weekend again. But before that I need your advises to eliminate the problems which I couldn't detect or I don't how to fix them.
For example I can not see any pulse for RA on the graph what does it mean and how can I fix it.
And also I am not sure if there is any problem with ascom. There is no option in the drop list for EQM 35 PRO. So I choose ASCOM.SkyWatcher.Telescope and I downloaded/installed ascom driver from webpage of skywatcher.
Hi All, wondered if you could help me make sense of this ... new HEQ5 - belt modded by FLO, all feels good, minuscule backlash but strange guiding.
Admittedly first time using it but baffled.
Failed calibration see image below and guiding seemed to be Ra and Dec following each other.
Stars look ok ish (@ 1500 mm )
Needle galaxy is poor as only about 10 mins each in RGB
note - it was hazy and did keep losing star in OAG
Thanks for looking
Dear Avalon Enthusiasts,
Do you have PHD2 Guiding Logs that you could share? Preferably at least 30 minutes long.
I am curious about the contribution to the overall error from the individual parts of the belt reduction gear. PHD2 Log Viewer provides nice analysis capabilities for that. I am especially interested in the frequency analysis.
Background is that I have built a motion module that uses a timing belt gear reduction quite similar to the Avalon mounts. Performance is quite good already, but I would like to compare it to the "real thing". 😃
I have had a real problem with my AZ EQ6 GT:
I have found that the MOUNT guide rate in RA is 1/3 the guide rate in DEC. EQMOD is set to 0.9 in both axis?? This seems to have happened when I tried guiding with AA& instead of the normal PHD2?
Is there a mount direct command to alter the RA guide rate. Bit like the mount commands to dim the polar scope and set park position.
You know one of these serial commands the no one ever uses??
All the best
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.