#211 - Wednesday, September 18, 2019 - Back in Action

Full-moon week is finally over, and I can start imaging again!  Not for very long yet, unfortunately, but each night I'll be able to image a little later before moonrise.  My telescope was snug as a bug under its Telegizmos 365 cover, especially with all the power cables inside of the water-resistant cable box.  Good thing too -- it rained on Sunday and Monday mornings, but the scope and cables were nice and dry!  How convenient for the first rain I've seen since I moved here a month ago to happen during full moon week :D

Last night, the moon was not up until 9:50, and since astronomical darkness started at about 8:40, I'd be able to squeeze in about an hour of imaging between two targets, M27 Dumbbell Nebula and the Eastern Veil Nebula.  Last night was trivia night with my fellow grad students, so I made a quick trip home to get the scope set up to run autonomously during trivia, since I wouldn't be back until after 10 PM.  So I got it uncovered and hooked up, which went smoothly.  However, since I had removed the camera last weekend while trying to figure out a way to attach my luminance filter to cut IR since my Astronomik CLS filter alone does not, I needed some way to verify that it was still in focus.  It was too bright for stars still at 6:30 PM while I was doing this, but I figured the camera might be able to see Jupiter.  Unfortunately, Jupiter was well west, and I haven't worked on the declination axis issue yet and really didn't want to lose alignment in case it slipped again.  So I checked SkySafari to see where Saturn was -- still east of the meridian.  It was magnitude 0.4, so I figured I might be able to see it in the camera.  So I commanded the scope to slew over to Saturn, but the dec axis slipped a little bit just before it got there!  Luckily the scope caught back up and didn't seem to lose alignment.

I turned on SharpCap and connected my ZWO ASI294MC, and sure enough, there was a little speck!  I zoomed in, and it was, indeed, Mars.  (By zooming in, I mean that I cropped the image.)

It looked pretty in-focus to me!  So I told the scope to go back to the home position, I connected SequenceGenerator Pro and PHD to all my hardware, and then I headed out the door for trivia.

When I got back around 10:20, the scope was home, and the sequence complete, since I told it to end the sequence at 10:15.  PHD went whacko for some reason near the end, which ruined the last frame on the Eastern Veil Nebula that came in, but all of the other frames looked fine.

The forecast is looking clear for the next many days, so looking forward to more data!  I've also already built my October sequence, which includes the Cocoon Nebula, Stephan's Quintet, galaxy M74, the Pleiades, the Rosette Nebula, and M42, the Great Nebula of Orion (which I'll activate later in the month when it doesn't come up so close to sunrise).  Since I completed my image of M33 from this month already, I'm going to look into swapping it out for another target today for the rest of September.  Lots of fun ahead!

Next post: #212 - Thursday, September 19, 2019 - New Targets

Previous post: #210 - Tuesday, September 10, 2019 - Curse You, Moon!

Table of Contents

#210 - Tuesday, September 10, 2019 - Curse You, Moon!

The moon is useful for a lot of things.  For one thing, it probably made life on Earth possible because of the tides and stuff.  It gave us something nearby to land on.  It helps us study the sun during solar eclipses.  It's helped us learn about the formation of our solar system, and our own planet.  I will even admit that it's quite beautiful to look at in the telescope, and even naked eye.

However, it is SO BRIGHT.  I have a perfectly clear night, the forecast is even calling for good seeing and transparency conditions, but I can't image because the moon is up nearly all night, and it's nearly full!  And it won't rise late enough to squeeze in any imaging between post-sunset darkness and moonrise until a week from now :(  So a week of taking darks it is!

Except, I'm having a bit of a problem with the dark frames.  Here is a single dark frame, auto-stretched:

It looks like a bright light, just off the edge of the frame.  Now, this is a 10-minute long frame (on my ZWO ASI294MC Pro), so it shines brighter above the background, but it's present in shorter-exposure frames too, just less obvious from an auto-stretch.  My first thought was that I had a light leak somewhere, so I made sure I had the cover over the scope the next time I took darks.  But the result was the same.  I debayered the image so I could see if the light had color, but it was white, which either means it's actually a white light, or it's far enough infrared to not look reddish and just appear white (much like how a remote control looks in your cell phone camera).  The extra weird part is that it's not really showing up in the light frames.  So then I thought, maybe it's a lot dimmer than it looks, and the light pollution and target are so much brighter than it that it won't show up.  However, when I calibrated some light frames with matching dark frames, the light showed up inversely as a shadow, since it had been subtracted out from what wasn't really there in the image.  Very weird.  Further testing is needed...unfortunately this camera doesn't have a physical shutter, so light could be leaking in from somewhere, but I have no idea where, except for its own red LED that is quite far away and facing the opposite direction as the camera chip.  (And I haven't seen this in my ZWO ASI1600MM Pro, which is the same body design).  More testing is needed...

Anyway, since the moon was setting around 3:15 AM, I set the telescope to start at 3 AM and just do M33, M77, and the Flaming Star Nebula before sunrise.  Worked again, no problems!  Now I have 168x3-minute frames on M33, which is 8.7 hours.  That is hands-down the most amount of data I've ever collected on a single target on the same imaging rig!  So I think I'm going to go ahead and process it during this full-moon break and see how things go.  Get excited!

Next post: #211 - Wednesday, September 18, 2019 - Back in Action

Previous post: #209 - Monday, September 9, 2019 - It's All Coming Together

Table of Contents

#209 - Monday, September 9, 2019 - It's All Coming Together

The moon is starting to get bright, which is limiting the amount of time I can image.  It kills me that it's so clear and I can't image!!  It feels like wasted time!  My first two targets of the night, M27 Dumbbell Nebula and the Eastern Veil Nebula, are too close to the moon and would be washed out, but the Cocoon Nebula was a healthy distance away, so I just unticked those two targets so that it would start right away on the Cocoon Nebula (which was high enough to image).

When I went to connect everything, the autoguiding program PHD2 didn't want to talk to the guide camera again (even though it connected just fine), so I restarted PHD, and then it worked.  Guess I'm going to just have to do that every time.  And SequenceGenerator Pro, so that it doesn't point my telescope at the ground on the wrong side of the meridian...

I had another fully clear night ahead, and the moon would be setting around 2:30 AM, so lots of imaging to be done still, all without me having to do things :D  The cooler had brought the camera down to -15C by the time it was done slewing to the Cocoon Nebula and plate solving, and away it went!  Watching PHD run by itself is so cool...when SGP changes targets, it pauses the autoguider, slews, and starts re-capturing frames, acquires a guide star, and starts guiding, all without any of my input.  All I have to do is connect the hardware.  (And I don't even think I have to do that -- I have which profile I want to use connected to my equipment profile in SGP, and I think it will connect them for me if I let it).

I wound up staying up until about 11:30 PM catching up on blog posts and finishing the processing on the Western Veil Nebula dataset I still had leftover from the Texas Star Party.  So I remoted into my tablet using TeamViewer on my phone and watched it change targets to M33 Triangulum Galaxy.  What an age we live in :D  It failed to solve the frame, and the frame looked blank!  I flipped over to PHD to see the guide camera's view, which looked like it was partially blocked.  So I ventured outside in my PJ's and outside slippers, and saw that M33 hadn't cleared my neighbor's garage!  Transit times have gotten early enough from when I first wrote the sequence that now M33 is starting before my telescope can actually see it.  So I used an app on my phone to measure the angle above the ground that the garage cut me off at, and then looked in SkySafari to see when it would clear that altitude, and set that as the start time for the target.  It had to clear about 50 degrees in altitude, and that would happen around 12:15 AM, so I set it, and went back inside.  This is probably why the log showed it failing to plate solve a couple of times last night as well.

I was about to head to sleep when one of my cats (Orion) threw up!  He ate his crunchy food too fast after I fed them before bed, and threw it all back up.  I'll get to bed at some point...

Oh, I forgot to mention on Saturday: I finally put together something I've been wanting to do for a long time, which was a power cable box!  Previously, I made some progress on solving my cable mess by creating a cable bundle with some self-closing cable wrap, which has done a lot to make my setup better.  But my power cables were still an absolute mess, and now that my scope is going to be out in the backyard for long stretches (including through rainshowers, thanks to my Telegizmos 365 cover), I needed to do more to protect my electrical connections.  So I bought a large rainproof power cable box on Amazon, and neatly tucked my power strip, AC-to-DC converters for the mount and dew heater, tablet plug, RoboFocus plug (which currently doesn't work), and camera power plug into the box, utilizing additional velcro cable ties to keep bundles together.

At last, less mess!  Now I just need a way to attach my cable bundle to a moving part of the mount somehow so that I can prevent it from getting yanked, and I'll be good to go!  It's laying on top of the counterweight bar at the moment because otherwise gravity pulls on the cables, which will disrupt guiding and stuff like that.  Of course, doing that gives it less play, so it ends up pulling tight when I point due south and low (which none of my targets are, but during alignment it was a problem).  And sometimes it catches on the polar alignment adjustment screws as the mount swing around, so I have to guide it by hand right now (which is not conducive for future meridian flips, once I finish fixing the declination axis issues).

Bring on the clear skies!

[ Update September 12, 2019 ] 

Because I'm now in a full-moon break, I went ahead and processed M33, since I have by far the most number of frames on it.  7 hours of frames passed through my inspection and quality control in PixInsight!  That's the longest image I've ever done :O  Very exciting.  And the result was even more exciting.  Remember, now this is from Bortle 7 suburban/urban transition skies of the East Bay area, well within the light dome of San Francisco, Oakland, and all of the other 7 million people that live around the bay.  

Details:

Date: 1, 8, 9, 10 September 2019

Location: East Bay Area, CA

Object: M33 Triangulum Galaxy

Attempt: 7

Camera: ZWO ASI294MC Pro

Telescope: Takahashi FSQ-106N

Accessories: Starlight Xpress filter wheel, Astronomik CLS 2-inch filter

Mount: Celestron AVX

Guide scope: Orion 50mm mini-guider

Guide camera: QHY5

Subframes: 140x180s (7h)

Gain/ISO: 120

Acquisition method: SequenceGenerator Pro

Stacking program: PixInsight 1.8.6

Post-Processing program: PixInsight 1.8.6

Darks: 0

Biases: 81

Flats: 50

Temperature: -15C (chip)

Look at this!!!  I can't believe this came out so well from inside the city!!  This is very promising, very promising indeed.  And this is just with a light pollution filter, no narrowband or anything!  (Actually, I don't even have an IR-cut filter on here yet -- hence the weird star halos.  I'll be rectifying that this weekend).  Lots of detail came through, helped by the good tracking on my mount.  Those stars were perfect circles!  

M33, the Triangulum Galaxy, is located just 2.7 million lightyears away.  It's a member of our Local Group, the third largest after our own galaxy and the Andromeda Galaxy. It's located behind the constellation Triangulum, which is below the midway point between the W-shaped Cassiopeia and the prominent square of Pegasus. It's about 60% the size of our own Milky Way, but contains only a tenth as many stars. It has a number of fascinating structures and giant nebula that can be seen even in amateur images.

More exciting things to come!

Next post: #210 - Tuesday, September 10, 2019 - Curse You, Moon!

Previous post: #208 - Sunday, September 8, 2019 - Automation Nation

Table of Contents

#208 - Sunday, September 8, 2019 - Automation Nation

After Sunday night's episode of The Astro Imaging Channel (which I finally had time to join that night!), I got outside about 8:50 PM (after chit-chatting with some of the members once we were off-air).  It was clear again!  Goodness this is awesome.

Same routine -- took the cover and caps off, connected tablet, powered everything up.  I had to restart PHD again when it wouldn't get images from the guide camera.  I wonder what's up with that.  I disconnect the equipment before I unplug the USB cable!

I figured out while I was catching up on blog posts earlier in the day that the RA and dec coordinates I was grabbing from Cartes du Ciel to put into the location boxes in SequenceGenerator Pro were the "apparent" coordinates, and not the J2000 epoch coordinates.  So I went through and copied the other coordinates instead, hoping that that would fix the weird offset problem.  I found it strange that every target would be offset from actually being centered by the same amount every time if it was a mount error, and that plate solving didn't fix it.  I thought, maybe everything is working right -- but the coordinates are slightly wrong!

Then I had some other software weirdness.  I started the SequenceGenerator Pro sequence, and it started the slew to the Dumbbell Nebula, except that instead of going where it was supposed to, it started slewing west instead, and then down toward the ground!  I stopped the slew and ended the sequence, reset to home position, and tried again.  Same thing!  I was perplexed.  I double-checked the time, date, and coordinates on the telescope and my computer, and they were correct.  I used the scope's hand controller to slew to the Dumbbell, and that worked just fine.  So what was wrong with SGP?  Finally, I disconnected everything in SGP and restarted the program.  When it slewed to the Dumbbell this time, it did it correctly.  Phew!  But also annoying.  The good news is, putting in the J2000 coordinates seemed to have worked -- M27 was smack in the middle of the screen.  Yay!  One more problem solved.

Another thing I did earlier in the day was to investigate how to let the sequence try again if something failed.  The log kept saying "no recovery options selected," so I decided to go find these recovery options.  It didn't take too long to find them, and you can set it to try the sequence again where it left off every X minutes for X minutes.  So I set it to do every 10 minutes for 3 hours.  This way if clouds are passing through, or the plate solve fails, it will try again.  But if the clouds stick around, it will eventually give up.  I may modify this, but we'll see!  Another problem solved.  Getting closer to being able to sleep easy while the sequence is running.

The moon is heading toward full, so I'm going to have to start imaging later and later, then take off a few nights around full moon, and then end earlier and earlier as the moon waxes.  But with it all automated, I can have it start or end at whatever time of the night, and I don't have to do anything.  So glorious!  I'm going to get a lot of imaging done.  Limited range of targets, but a south view still gives me plenty!

In the morning, I checked on how everything went -- it did fail to plate solve a few times, but with the recovery options on, it tried again, and eventually succeeded.  I had a full night of images!

Here's a single frame of M33, the Triangulum Galaxy.

M33 Triangulum Galaxy, single 3-minute frame

Camera: ZWO ASI294MC Pro, Astronomik CLS filter; telescope: Takahashi FSQ-106N; mount: Celestron AVX

(click here for the final image!)

The light pollution is definitely going to be a challenge, but we'll see what I can do with it!  Also, during the TAIC presentation, after much talk about the Advanced Imaging Conference, I went ahead and registered!  San Jose is only about an hour from me in low traffic -- way closer than the plane flight it would have been before!  I'll probably take public transit out there, or maybe stay down there for the weekend, I'm not sure yet.  Really excited to learn some new techniques and talk to other astrophotographers!

Next post: #209 - Monday, September 9, 2019 - It's All Coming Together

Previous post: #207 - Saturday, September 7, 2019 - Chugging Along

Table of Contents

#207 - Saturday, September 7, 2019 - Chugging Along

The physics department graduate students held our "post-prelims party" on Saturday night, which was some good fun.  We had a good turnout, and the view from the back deck of the student's house who was hosting was gorgeous!  Wish I could set my telescope up on a deck like that!  I heard he had a great view, and I almost brought my DSLR on a tripod to do timelapse...almost.  ;)

Before I went, though, I got my telescope queued up to run without me, since it promised to be clear.  Shortly after sunset, before I had any stars, I pulled off the cover and the caps, and plugged in my tablet and got everything connected.  PHD connected to my guide camera (red hockey puck QHY5), but it couldn't grab any frames, so I rebooted PHD, and then it was happy.

Since my current last target, galaxy M77, transits at 4:44 AM now, that leaves another half an hour until the first light of dawn begins to appear at 5:13 AM, according to my handy "Calendar - Sun & Moon" app.  So I decided to add another target, since M77 will transit earlier and earlier, and sunrise will come later and later anyway.  After scrolling through SkySafari's "Best Deep Sky Objects" list and gating out targets that were too low or not in my open sky view, I settled on the Flaming Star Nebula.  I've tried it once before, way back in March 2017 on my astronomy club's Vixen 140mm neo-achromat, but I only got a couple of subframes that night and had other issues.  Time to try again!

The half-moon was just east of the meridian, so before I finished getting ready to head to the party, I slewed to it to grab some video.  I grabbed two -- one with the Astronomik CLS filter I've been using (it's currently sitting where my luminance filter previously sat, so I don't currently have a clear filter loaded), and the other with my infrared filter.  IR filters can help because infrared light isn't as disturbed by the atmosphere, generally speaking -- not at the super-near IR wavelengths, anyway.  I haven't processed the video yet (RegiStax is having issues with my one-shot color cameras), but here's a single frame!

I cropped the frame size in SharpCap so that it would download faster, and got a nice 25 fps at this size on my ZWO ASI294MC, which is USB 3.0.  The moon does have a slight reddish tint -- that IR filter dips a tiny bit into the red, so if I hold it up to an incandescent lightbulb, I can see a little bit of very red light through it.  It's actually a Johnson-Cousins photometric filter, part of a photometric filter set I got from one of my previous astronomy club members.  The atmosphere was pretty shimmery, so we'll see how it turns out!

While at the party, I was telling some people about how my telescope was running autonomously in my backyard! :D  The idea also struck me -- I wonder if TeamViewer has a smartphone app?  So I went to the app store (I'm Android), and sure enough, they do!  I had recently installed TeamViewer on my tablet so that I could watch progress from inside (I'm prepping for winter here) after failing to get the new Windows Remote Desktop app to install on my desktop, since my Microsoft Store (and the Feedback Hub) haven't worked for months.  My tablet is also running Windows 10 Home edition instead of Pro, which I've read can't do remote desktop (although it might be accessible by it, maybe it just can't initiate a connection, which would be fine).  Anyway, TeamViewer is free for personal use, and it's been working great.

So the next day, I tested out the smartphone app -- and it totally worked!  Now I can check on the progress of my setup anytime, anywhere (especially my bed)!  And not only that, I can even control the computer from it.  Very exciting :D

Looking at my tablet screen from my smartphone!  Watching it slew to my next target and center it.

The sequence ended up ending early when it couldn't plate solve for M33's position -- perhaps some clouds rolled in, I have no idea.  Or maybe the plate solver just failed.  I need to investigate if there's a way to let the sequence try again after some time, or wait for the next target, or something.

So far, so good!  Making progress toward automation!

Next post: #208 - Sunday, September 8, 2019 - Automation Nation

Previous post: #206 - Thursday, September 5, 2019 - Backyardathon

Table of Contents

#206 - Thursday, September 5, 2019 - Backyardathon

Yet another clear evening!  This is so great :D Really liking California so far...

I've been trying various modes of transportation to get to school; this time, I tried taking the bus.  The trip there in the early afternoon was fairly quick, but the return trip home took a lot longer, and involved me waiting at a bus stop in the dark for 20 minutes :/ But I eventually made it back to my house, and I went straight to the backyard without even going into the house!  I threw off the cover, plugged in my tablet, connected PHD and SequenceGenerator Pro, started the camera cooler, and then updated the target switch times for their new transit times.  SGP has a handy utility called Planning Tools that, for a given target, will tell you where it will be in the sky when, and by right-clicking and left-clicking on a plot of its trajectory over the course of the night, you can set the end and start times without having to fill them in yourself.  Unfortunately, SGP doesn't have a target catalog built in (at least, not one I've been able to find), but it's really good at parsing a wide variety of input formats for the RA and Dec coordinate boxes.  So I simply went into Cartes du Ciel, searched for the target there, copied the RA and dec coordinates (complete with the "RA:" and "dec" text), and then pasted it into the declination coordinate box in SGP.  It very quickly parsed it into the actual RA and dec coordinates.  Woot!  Then I could use the Planning Tools, and this is how it's been slewing to those targets.

This time around, I didn't reset the sequence, but tried just starting from where it left off (which it saves automatically for you).  This worked!  It started with M27, the first target on the list, even though I don't have start times for any of the targets (just end times).  This will let me keep the frame numbers of each target sequential, instead of having frame1, frame1 (1), frame1 (2), etc, for every night I image.

The plate solver had issues again, however -- it didn't want to solve on the second, verification solve.  (It was doing the first solve just fine).  My wifi driver had died again, but the plate solver was set to the offline Astrometry.net server.  While I was working on this issue, I heard a scratching noise from the back fence.  I turned on my cell phone's flash light, and saw a raccoon peak its reflective eyes at me!  The light didn't seem to scare it much, so I sort of fussed at it, and also kicked the fence.  It would duck down, and then peak back up.  Finally, I grabbed a lemon off my lemon tree and threw it at him!  I missed, but it hit the fence, and I didn't see him again after that.  After watching the fence for a few minutes to see if he'd be back, I went back to my computer to keep working on the plate solve issue.

When I tried it again, it worked, and since PHD was still calibrated from the other night, everything was ready to go.  So I finally went inside to feed the kitties and go to bed.  So nice not to have to stay up!

I've got a lot more data I want to collect before I process any of this, so here's a single frame to tie you over!  A noisy, low signal-to-noise ratio one, but you know the power of stacking by now.

Cocoon Nebula, single 3-minute frame

Camera: ZWO ASI294MC, Astronomik CLS filter, telescope: Takahashi FSQ-106N, mount: Celestron AVX

Next post: #207 - Saturday, September 7, 2019 - Chugging Along

Previous post: #205 - Tuesday, September 3, 2019 - Working Out the Bugs, Part 2

Table of Contents

#205 - Tuesday, September 3, 2019 - Working Out the Bugs, Part 2

I biked to school on Tuesday, since I drove in the morning, but forgot a few important things at home, and knew I wouldn't be able to find a spot again if I drove back.  I'm a little out of biking shape, and it's a general uphill to campus, so it was a bit of a brutal ride!  But it was pretty fun.  I rode home in the dark, and it was clear!  So when I got home, I threw my backpack off, quickly fed the cats, and then darted outside to start imaging.  First, though, I had to re-align again, since I wasn't able to complete the alignment last night.

After uncovering the scope and getting everything connected, I used the Celestron PWI app to slew to some stars up above Polaris, since as I discovered last night, something's still wrong with my declination axis, and I can't slew very far south if I'm facing the west side of the meridian.  But it still did the rapid-wagging thing it did yesterday!  So I decided to characterize the problem a bit.  I disconnected the mount from PWI and rebooted it, and then used the hand controller to slew around and see where it started.  However, the dec axis behaved normally, all the way around!  Now I'm wondering if it's an issue with PWI.  It's relatively new software, and only very recently released for their non-USB mounts like my AVX.  So I decided to run things the ol'-fashioned way -- using the hand controller and the ASCOM driver instead of PWI.

I aligned, re-polar aligned (one of the legs had sunk accidentally a little bit), and then while I was doing the second alignment post-polar-alignment, the dec axis did the wagging thing for a southerly star on the western half.  So I restarted the alignment (luckily I didn't need to polar align again), and picked western stars that were less far south.  Finally, finally, I got the mount aligned.

I started the sequence to start imaging, but plate solving using the Astrometry.net downloaded offline server wasn't working in SequenceGenerator Pro.  My tablet's wifi card driver had died, so I had to reboot the tablet to get it working again so that I could use Astrometry.net's remote server instead.   (One of the benefits of not using software to run the mount!)  However, after the reboot with functional wifi, the plate solver still didn't want to work.  So I switched back to the local server, and that finally worked.  It is super slow though, which I don't understand -- it has my scope's focal length, camera sensor size, the coordinates where my scope should be pointing, and I'm even binning the image 2x2 to make it smaller, so it should be a pretty quick plate solve, since it has all of this information and shouldn't have to do a blind solve.  Rawr.  The plate solving helps to get the image centered in the frame when the mount didn't quite do it.  It's not doing a great job, however -- it does the initial solve, moves the mount, and then solves again to check, but it's usually just back in the same spot as before.  I increased the number of attempts, but it still stops after the first move.

I also adjusted the target-switch times in the sequence, since everything was crossing the meridian about six minutes earlier than when I had first programmed the sequence.  I really didn't want the scope to go past the meridian, since even though the mount can go as far back as 20 degrees past, I haven't yet fixed the issue of the dec axis coming loose and sliding out a tiny bit, which was probably the cause of it not being able to park on the first night.

Once everything was rolling, I went inside and went to bed, hoping that it would still successfully park.  (I did test earlier that it would park using the ASCOM command instead of PWI).

The next morning, I went and checked on it -- yup, it parked, and the camera warmed!  It got through M27 Dumbbell Nebula and the Eastern Veil Nebula, but the log showed that it failed to plate solve the Cocoon Nebula.  Now whether this was due to a passing cloud or the plate solver not working again, I'm not sure.  Before I powered everything down, I checked that parking the mount in SGP actually put it into "hibernate" mode, where it would save the point model, and this turned out to be the case.  Woot!  So all I had to do was disconnect hardware from SGP and the PHD2 autoguiding software, and then flip the main power strip switch and put the cover on.  Beautiful!

Here's a single frame, debayered and auto-stretched:

M27 Dumbbell Nebula, single 3-minute frame

Camera: ZWO ASI294MC, Astronomik CLS filter, telescope: Takahashi FSQ-106N, mount: Celestron AVX
(Click here for the final image!)

A promising start!

Next post: #206 - Thursday, September 5, 2019 - Backyardathon

Previous post: #204 - Monday, September 2, 2019 - Working Out the Bugs

Table of Contents