Recently Browsing 0 members
No registered users viewing this page.
I scrapped all the Oiii and Sii data I previously took during a full moon (about 15 hours worth) and retook it all when the moon was a bit smaller at 76%. Ha was taken during 98% and 67% moon. All the lights were taken on the following nights: 12th, 19th and 20th September 2019.
Integration times, all in 600s subs unbinned:
Ha = 28.33 hours
Oiii= = 5.67 hours
Sii = 5.67 hours
The Ha data is really nice, and unsurprisingly the Oiii and Sii is not as strong (or nice).
I'm missing that (vital) step in my processing routine of getting the Sii and Oiii properly stretched to match the Ha, before combining. I dont really know how to deal with the weaker data properly. Any pointers would be appreciated.
What I do currently:
All the data is loaded into APP into separate channels/sessions.
The data is stacked and registered against the best Ha sub
This produces individual stacks of Ha, Sii and Oiii that are all registered
Each channel is processed with DPP in APP and then saved as a 16bit TIFF
Each is opened in PS
Stars removed with AA and any remnants removed and tidied up
I then open a blank RGB document in PS
I paste Ha into Green, Sii into Red and Oiii into Blue
Adjust the selective colour settings to get 'Hubble palette'
Adjust levels, curves, saturation until looks ok
All the Ha Sii Oiii data is then combined together in a single 'super' stack in APP using quality weighted algorithm to create a 'luminance'
That luminance layer is adjusted using levels, curves, and NC tools such as local contrast enhancement and deep space noise reduction (using masks to apply as required)
The luminance is pasted onto the above colour layer, and incrementally added using gaussian blur
Cropped and saved.
Here it is anyway I haven't intended on any more exposure time for this one, but will consider it, if the expert opinion dictates otherwise!
Just spent 4 hours resurrecting my AVX mount, it had become so stuff in RA it just wouldn't track at all. Googled as much as I could find and used the http://rocketsparrow.blogspot.com/2017/01/how-i-made-better-celestron-avx.html?m=1 as a guide.
Decided to use a bearing as discussed in thread. I chose the https://simplybearings.co.uk/shop/p503131/32007-Premier-Budget-Metric-Single-Row-Taper-Roller-Bearing-35x62x18mm/product_info.html?backstep=1 as the dimensions were perfect ( almost perfect, bearing is 2mm too thick but works fine)
Cleaned all the gungy grease off and used thin layers of superlube.
It's so much smoother now and I can actually balance the mount.
Only problems I had were the 2 bolts that hold the RA and Dec assembly together stripped the mount ! Soft cast ally by the looks of it but there are 4 holes for 2 bolts (almost like Skywatcher knew 😂) and refitting the motor worm assembly is tedious to get backlash adjusted .
Can't wait to try it out.
Ps the new bearing wouldn't quite fit til I put the mount in the oven @ 80 degrees and the bearing in the freezer for 5 minutes.
My EQ6 mount is old now. Very stiff RA and DEC axis, it's time to dismantle it and see how bad the inside is.
I followed the Astro Baby guide and it was not any big problem to dismantle it. It looks fine inside, I suspect some earlier owner already have done this cleaning and put new grease on. But that must be years ago.
When I now have dismantled everything, shall I rebuilt it and install timing belt drives? I feel it's a little to much money to put on this old mount. I have to think about it and see what alternatives there are.
Here is my EQ6 dismantling story:
Only first part, now I'm drawing plans.
By Anne S
I'm trying to update my v3 handset prior to selling the mount. I need to update the bootloader from v1.0 to v1.7 before I can upgrade the firmware from 3.12 to the newest version. I've tried following the instructions in the bootloader download but the upgrade loader refuses to install anything.
Before I realised I needed to update the bootloader, the synscan loader v3.3 just showed 255 255 255 where it should display the handset software, ie 3.12.
Can anyone advise what I'm doing wrong?
The handset won't run the mount probably because I had a replacement motor control board a few years ago., I'm guessing. It worked fine before that. I've been using eqMod for years.