Recently Browsing 0 members
No registered users viewing this page.
Sooo...I'm getting quote frustrated here. This spring I tested my HEQ5 with guiding. The synscan controller was connected to the computer trough the USB plug on the hand controller. This worked like a charm in my living room. On the new controllers you dont need the rs cable. But when I tried the whole thing with guide cameara for some live shooting, it just did not work. I get something wrong with the com port in decice manager, driver not working. I have tried 3 different drivers. The whole thing responded, connected and was guiding when i did a dummy test before the summer. So setup is pc-synscan via usb for pulse guiding. Can it be a problem with windows 10? What t h.... just happened? Where can I find a driver that works? And believe me it worked 5 months ago, argh. Thanks for any respons and support
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!
I recently got into astronomy so I bought my first telescope. I've read through several articles and the recommendation for a beginner's telescope (value/price) was Celestron Astromaster 130EQ-MD. I bought this from someone who was not really using it and it is in a very good condition. Prior to actually purchasing this, I've watched countless videos on how the telescope works, what needs to be done - latitude, RA/DEC alignment, polar alignment, etc..
After reading through all available manuals and videos, I finally brought it home from the seller (they've had it for around 5 years but it wasn't used much). After setting up the tripod, mounting the telescope and familiarising myself with all the different knobs, I pointed the mount/telescope towards north. The first thing I had to do was setting up the latitude. Since I am based in London, the latitude is around 52 degrees. Afterwards, I had to align the declination axis so the telescope can be balanced. As I understand it, you should be able to move it to any position on the axis and it should stay in that position. If the front or rear was heavier, I would either pushing or pulling the telescope after unlocking the brackets holding it together. This is where the issues began, I could balance the telescope so it doesn't move while in the horizontal position, however, when pointing it towards north, it would exclusively lean towards one direction - to the left. If the telescope was pointing to north, north-east or east, it would pull towards the west all the time. It is probably easier to show it in the video. I've spent three days trying to balance the telescope by using different methods and it just would not work.
I've also tried balancing the RA axis first. This could be somehow done, but the declination axis would still pull the telescope to the left.
It is extremely frustrating as I don't know what could be causing this. Balancing the telescope should be relatively easy from what I have heard - either push it or pull it depending on where the weight is. However, I have been really struggling to get it set-up.
I would be thankful for any suggestions and please feel free to ask any questions so I can help with finding out what is wrong.
With several clear nights over the past week, I've been playing with the Synscan Pro app (Android) in conjunction with a Synscan WiFi adapter on an EQ3Pro mount. I have to say I'm generally quite impressed. Much cheaper than buying a traditional handset.
However, this evening I was trying to "creep up" on the Andromeda Galaxy by star hopping towards it via Mirach, Mu Andromedae and Nu Andromedae. Mirach was no problem but the other stars were not available for selection in the app. Am I missing something? I couldn't find any way to enter an SAO number or any other catalogue number to find the minor stars.
Is this a limitation of the app? Or the adapter perhaps? Or is it me?