Jump to content

Banner.jpg.b83b14cd4142fe10848741bb2a14c66b.jpg

Miguel1983

Members
  • Posts

    689
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Miguel1983

  1. Hi, Decided to work on data from last year. Data captured with my Esprit 120 @ f5.25 and the ASI1600mm pro and Astronomik 6nm narrowband filters. IC443 the Jellyfish Nebula in Hubble Palette, about 3.5Hrs/filter and i duplicated the Ha layer and added it as Lum Ngc281 or Pacman nebula, this is in HOO and i added 50% of the Lum data
  2. Someone resurfaced this topic with a like. Since the start of the topic i've used this scope as stated above and for a while i deforked it and used it on my EQ6-R, but i used it less and less because the EQ6 was being used for AP with a frac so i mounted it back in the fork. However, a few months back there was the GPS rollover problem, something with the date register that was at his end rendering the internal GPS useless. A fix was made by Celestron in the form of a new update, so i had to continue my previous efforts to update the HC. I managed to do this by trying a different USB to RS232 adaptor, everything works like a charm again, really liking this scope 😀
  3. When you're looking at stars they should be pinpoints. When you're looking at a deepsky target like the Andromeda galaxy, you see a smudge of light with a bright centre, this is normal, but the stars must be in focus. Maybe check out a SCT collimation how-to on you tube to be certain you got this right, it's possible it's way off. I would say, if you get your collimation in check and you still don't get a sharp visual of, say the moon, you may want to contact the dealer that sold the scope.
  4. Hi and welcome, You are certain that your collimation is good ? So when pointing to a star and turning the focus knob left and right before and past focus you see concentric circles ? The corrector plate is not dewed over ? What eyepiece are you using ? Is this a new telescope ? I think the first thing should be to resolve the problem of not being able to use the telescope visually, after that we can look into the imaging.
  5. Ah, yes i mistyped there, i meant for imaging. You're probably right about the sensor size too. For planetary imaging for example, witch i've done with my C11, it's fine.
  6. Thanks for your report, so in summary, for visual there's really no need to spend the extra cash for an Edge HD model, but for visual it is justified .
  7. That's some serious gear you got there ! Can you elaborate on comparing the views between the Edge and the regular SCT, i'm very happy with my C11 but i haven't got the chance looking trough an Edge HD model.
  8. Hi, i can see the difference, but i'm not sure witch i would like "better", after you rotated the EFW is seems like there's a pinched line instead, also didn't that give you more vignetting ? Thanks for sharing your experience
  9. Did some correction in PS on the microlensing
  10. Hi, just dit a quick process on the Ha data i've captured this week of B33, more to be gathered… 2h40min so far
  11. Thanks Olly, i think you're right on the money, microlensing is what a friend told me too and indeed, one can only try and do some touch ups in PS. Must say i didn't pick my targets well since i got the ASI1600, did IC443 and M45, both had the same artifact, guess i should stay clear of bright stars or learn to live with it.
  12. Hi, i'm shooting B33 in Ha right now, and i've just stacked the first 12 4min subs. What i feared came true, Alnitak is all over the place 😞 Suggestions ?
  13. I'm sure there's more to be done with the data, and i'm still not happy with the final image too, i see the mistakes i've made, but keep in mind i'm still a Pix-newbie 😅 I'll probably come up with another new version on some rainy day 🤫
  14. Actualy i lightend the background in the end with a mask on the galaxies, i thought it was too black. If by my darkness you mean the Bortlescale in my backyard, that's Bortle 5. I think i used 10 different masks, it's hard to find the right combo.
  15. i've added some Lum and Ha data to my existing data, total exposure time is about 23,2Hrs now. 500 x 60 sec Lum 121 x 240 sec Ha 147 x 60 sec R 145 x 60 sec G 147 x 60 sec B Working PixInsight is progressing, every run i have on this object it goes a little better, far from perfect, i still need to learn a lot. Crop
  16. I'll adjust it back to original state, but that mount will be stiff again and almost impossible to balance. I realy didn't loosen that bolt a lot, and i don't see the relation to that bolt tension and and the RA slipping, isn't the RA clutch resposible for that ? As for visual use, i've done a 2 star alignment when i was running it with the HC, first star was way of, second star only needed adjustment of 1 axes, it was almost dead on.
  17. Hi, i have tried this mount now for 2 times and both times failed to make it guide. The first time i've connected it to my laptop via EQDIR cable, so no HC, and used the HEQ/EQ6 option in the EQMOD telescope chooser, calibration in PHD2 failed time and time again ==> "Star didn't move enough" i tried different values for the microsteps, in the end i adjusted some value's in the EQMOD toolbox guide settings, calibration did finish then, but wit questionable results. Decided to give u that night... Yesterday i tried again, this time claibration stopped after not even a second and phd promted "guiding stoped mount slewed" At that time i had enough and decided to go old school so plugged in the HC and St4 cable, helas, "Star didn't move enough" no succes with calibration. I've just about had it now with this mount and i'm kicking myself not getting the HEQ5 as a second mount. Suggestions ? Thanks
  18. Hi, i recently bought a second laptop also just for capture, process i do on a more powerful laptop. It's an HP 14 - cf0087nb Azerty, quite happy with it, details here
  19. Here are mine, the AZ5, AZ GTI and Celestron fork. The AZ GTI is good, but it suffers from a horrendous backlash, pointing is also not the best, but it is a very compact goto mount. The AZ5 is good for lightweight gear, i use is mostly for my solar scope, i have used it for my Mak and ED80, if balance is good its not really a problem, but it close to the weight capacity. The Celestron 11GPS mount is very good for it's age, its quiet, pointing and tracking is good, love it, one downside tough, it weighs a ton.
  20. I'm guiding all the time with my EQ6R-pro, but the thing is i connect the EQM-35 as a EQ5/EQ6 and i think this is OK, IF one adjusts some settings, and i'm not quite sure witch ones. In APT for instance slewing at a speed above 0,25 locks the mount up, then again parking at full speed is no problem. As for guiding at first i was unable to calibrate (Star didn't move error), i then adjusted (without knowing what i was doing) some guide settings in the ascom toolbox, and the calibration finished, but still not good, guiding was 1,65", so far from good, at that point i had enough and gave up for that night.
  21. Hi, i've recently put a second imaging rig toghether with my Canon 750D that was replaced by a ASI1600 on my main rig. Before i switched to the ASi i used BackyardEOS for cameracontrol, but now i want to use APT like i do with the 1600, but i've noticed the liveview doesn't show any stars, in backyardEOS i've never had this problem. Wrong settings ? Thanks
  22. Hi, i bought this mount recently, but only had one "night" out with it, mainly to get it installed. Must say i'm not quite there yet, i want to use it via ASCOM with my laptop, but i'm suspecting i have not the right settings. Ascom telecope chooser let's you choose between Skywatcher mount and EQ5/EQ6, the last one works, but my guiding is all wrong. You would happen to have some tips ? Software used : Ascom platform 6.4.0.0 , Cartes du Ciel, Phd2, APT Thanks
  23. Thanks, in a way i’m recording the stars ✨☺️
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.