Recently Browsing 0 members
No registered users viewing this page.
By Gary Shaw
I just acquired a 200mm F4 newtonian from TS Optics which I'll use primarily for Electronic Assisted Observing with several ZWO cmos cameras.
My challenge is that my current scope is an F3.6 schmidt newtonian so I have no experience with coma correctors or spacers/adaptors in the optical train. TS tells me that I need 55mm from the coma corrector (TSGPU) to the sensor. They provided 40 mm of various adaptors and spaces and I guess I get the remaining 15mm from the camera housing itself - as shown in the attached image. The threads on several of the adaptors(see notes) are bad so those pieces need to be replaced but, once that's fixed, I have four questions for this community:
1. ...is this odd assortment of parts and pieces typically how one goes about achieving the required 55mm dimension from the Coma Corrector to the camera sensor? Just seems that there must be a simpler, and sturdier way to do this without having to use 4-5 separate parts.
2. Once all the adaptors add up to the correct dimension and are attached to the Coma Corrector, where does one locate the whole assembly(with coma corrector) in the focuser draw tube? Is it a matter of trial and error?
3. If one did not care about viewing peripheral stars looking a bit like comets and didn't, therefore, use the coma corrector, would any of these adaptor/spacers be needed to bring the camera to focus so one could observe using, say, Sharpcap 3.2 Pro or other software?
4. If I were to use a filter or two, where would these best be located in the lineup and do they work with the various threads and adaptors?
Apologies for my lack of experience and thank you for any help you can provide me in understanding how to observe and image with coma correctors
After a pretty dreary September and part of October, I was finally able to get out with students to do some viewing. Here are some of the objects viewed over two nights using Starlight Live software on my Borg 77edii (f/4) and Borg 125SD (f/5) with a Trius 694 mono camera. In most cases an IDAS NB-1 "nebula" filter was employed to help with the suburban light pollution in our skies. The first night (mainly 125SD) was much steadier and drier, but along the coast we take what we can get when it isn't raining! ;-D
It's so much fun to see these objects from less-than-optimal skies... I often intend to quit much earlier, only to find myself saying (over and over!) "... oh, look, <object> is coming up... I should just have a look at that before I pack up." And then another hour goes by!
- Greg A
Eastern & Western Veil
Comparison of FOV between two scopes on the NA Nebula
Again, FOV comparison on the Elephant Trunk Nebula
And again, with the Rosette Nebula
Pacman Nebula through the 125SD:
And Crab Nebula:
And the Cocoon Nebula:
Finally, a few wider shots of objects using the Borg77: Flame/Horsehead, California Nebula, Pelican Nebula and Andromeda Galaxy:
After updating my legacy HC to the 99.22 (I had to, because of the GPS rollover issue) and the MC to the 5.23 firmwares (siply because it was there, and I've got greedy), both acquired via Teamcelestron, my CPC was operating normally until, all of the sudden, its altitude motor stopped working. I've uploaded a video at youtube showing what happens:
As you can see, I don't get any error message in my HC but, if I try to move the scope in altitude, nothing happens (no movement, no motor noises, nothing). When I release the clutch and move the scope manually in altitude, it does move but has a weird noise by the same place where previously it used to make a snap one, which I already reported to celestron tech support once, and even made a video that I also uploaded to youtube:
I've already seeked help from Celestron Tech support (and the folks at Cloudy Nights) but any help from you would be very much appreciated. Best regards,