Monday, September 9, 2019

#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!




#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!




Sunday, September 8, 2019

#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


#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!)



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

Another clear night! :D I went out at twilight to add more stars to the alignment model.  I slewed to Altair, but on its way over, the cable bundle got pulled too tight, which caused the dec axis to "jump," so I had to re-do the whole alignment.  I also wanted to add some western stars to help beef up the model.  Jupiter hadn't gone behind my lemon tree yet, so I commanded it to slew over there, but partway over, the dec axis motors started wagging it back and forth at high speed!  I shut off the power and reset back to home position.  I tried it again, starting with Jupiter, but got the same behavior!  It seemed to be happening past a certain declination heading south, but only on the western side of the meridian; I could go all the way to due south from the eastern side without issue.

So I picked some western stars that were much further north and just peaking out from behind the roof of my house.  I first went to Mizar -- I figured out that in the PWI app, you don't have to use just the couple of recommended stars in the alignment list, but you could click on any star on the map and use that as the alignment star.


That worked fine, but by this point clouds were rolling in, and it was hard to find stars.  The clouds didn't show any sign of letting up, so I gave up on trying to image that night, and instead just put the caps and cover on and just took dark frames instead.  Darn!



#203 - Sunday, September 1, 2019 - Handywoman Skills

Another clear night right away to try again with the backyard rig.  After the disengagement of the dec axis gears the night before when it didn't successfully park,  I thought all was well that morning when I was able to slew the mount up around the north, but as it turned out, I was wrong.  When I had it slew to Deneb for alignment, the dec axis stopped slewing partway there.  I used the controls on the computer in the Celestron PWI app to slew the mount by hand, and sure enough, RA was slewing fine, but dec wasn't moving!  So in the dark, I took the mount apart to see what was up.

Looking down into my Celestron AVX mount with the dovetail saddle and declination axis motor cover removed.

I ran inside and grabbed my allen wrenches and screwdrivers, and then took my telescope and everything attached to it off as one rather heavy piece, carefully set it on the ground.  I started to remove the top cover of the dec axis motor box, but I couldn't get to one of the screws without taking off the dovetail saddle.  So I removed that too, and then also ended up having to take off the bottom cover of the dec axis motor box.  There was a small pile of fine golden dust in the corner of the box -- the gears must have ground on each other at some point.  Greaaaaat.  The motor drive gear and the worm drive gear had become offset from each other, and the motor drive gear was pushed in very tightly with the worm drive gear.  Having recently adjusted the motor drive gear to mesh more closely with the worm drive gear to take up the backlash, I knew exactly how to add a little separation back and get them re-aligned.  

The motor drive gear is attached to the motor shaft with some tiny hex bolts, so I loosened those and pulled the gear off.  Then I loosened the screws holding the motor to the block, and put the gear back on.  This allows you to slide the motor back and forth so you can set exactly how tightly you want the gears meshed.  So I pulled it back a bit, and once I was satisfied with the fit, I removed the gear again, tightened the motor screws, and then put the gear back on and tightened it down.  I put the dovetail saddle back on, and then tested the slewing.  It slewed normally again!  Woo hoo!  So I re-attached the telescope, hooked everything back up, and re-started alignment.  Luckily, I didn't need to re-polar align, so I just put in some stars in the eastern half of the sky where I was imaging.

I re-loaded the script with all of the targets from the night before, and checked that the settings I had changed that morning to actually succeed at parking were still set.  Everything looked good to go.  I hit the start button, and off it went!

SequenceGenerator Pro
(Check out the final image of M27!)

I came back out around 10:15 to watch it switch targets from M27 to the Eastern Veil Nebula, which went smoothly and happily.  Then I went to bed!  So glorious.

The next morning, I woke up and looked out the back door to a beautiful sight: my telescope, pointing north and parked.  The camera cooler had turned off as well, and I had a full night of images.  So amazing!!


So the plan is, I'm going to run this multi-target list every night I can, tracking targets rising in the east until the hit the meridian, and then heading back down to the next target.  It doesn't get me a lot of frames in one night, but over many nights, it will get me a lot of frames.  So long as a passing cloud doesn't end the sequence early!  Super excited about this.  Hello sleep!  The targets for the next couple of weeks are: M27 Dumbbell Nebula, Eastern Veil Nebula, Cocoon Nebula, M33 Triangulum Galaxy, and M77 Cetus A galaxy.  Right now I'm sticking to 3-minute subframes, but once it looks like that is generally working well with the autoguiding, I'll try bumping up to 5 minutes, which is at least what I'll need for narrowband imaging.  My light pollution filter (Astronomik CLS) seems to be doing a pretty good job for my Bortle 7 skies, and the histograms of my images are still pretty far to the left, so I want to try for 5 minutes.  I have my new ZWO ASI294MC color CMOS camera attached now, thank you to my good friend and astro-buddy John, and I'll be switching back and forth to the ZWO ASI1600MM Pro monochrome CMOS camera for doing narrowband once I actually get myself some filters and another carousel for my filter wheel.  Exciting times ahead!



Sunday, September 1, 2019

#202 - Saturday, August 31, 2019 - New Digs!

I recently moved to the East Bay area of California to start my PhD in physics at the University of California, Berkeley!  I found a house to rent during my first week in town, and spent the second week moving in and attending orientation events.  My house has a little backyard with a gorgeous lemon tree, as well as a plum tree, and several cement squares.  Between the cement squares grows some mint, which smells awesome!  The lemon tree also smells incredible.  It's a nice little spot.

After getting mostly unpacked and having several clear days that had cloudy nights, I finally set my telescope up this afternoon.  My backyard faces south, which is great, since there are more deep sky objects (and planets!) southward.  I have about a 100-degree-wide swath of open sky between my neighbor's large evergreen tree and my lemon tree, which only goes down to 60 degree of altitude over their backyard, but goes as low as 37 degrees above my back fence.  If I am patient and image over many nights, I should still be able to do some good imaging!  I've seen some phenomenal images from light-polluted skies, and I'm at Bortle 7.  Many of those images are narrowband, which takes a thin slice of the spectrum where there is little light pollution, but some of them are wideband using light pollution filters, or multi-bandpass filters like the Optolong-L.  It's certainly not an ideal setup, but I can still do some good with it, and best of all -- I can set it up, and go to sleep!  No one can see into my backyard unless they walk all the way up my neighbor's driveway and peak over the locked fence.

Gear:
Mount: Celestron Advanced VX
Telescope: Takahashi FSQ-106N
Camera: ZWO ASI294MC
Filter wheel: Starlight Xpress, with 2-inch Astronomik LRGB Type 2c filters
Guide scope: Orion 50mm
Guide camera: QHY5

The rest of the afternoon, I processed photos and double-checked software on my tablet.  I saw a Celestron ad in Sky & Telescope that said that their new Planewave application for controlling Celestron mounts now included several serial-based models, and not just their USB-controlled mounts!  Any mount with a NexStar+ hand controller can now be controlled by their PWI software.  This is really exciting because I can save alignment models and re-load them instead of relying on hibernation to work and hoping there's not a power cut from me doing something stupid.  It also includes some more intelligence than the hand controller alone; for example, after you do the polar alignment, it automatically updates the star alignments you already made, so you don't have to re-align after a polar alignment!  

Once twilight began, I went outside to get my tablet hooked up and get everything checked.  I decided to attach my Astronomik CLS filter, which is a light pollution filter that cuts out the waveband where high-pressure sodium lies.  I forgot that 2-inch filters are M48 and not M42/T-thread, however, so I couldn't attach it directly to the camera.  So I ran inside and got my filter wheel, swapped the luminance filter for the CLS filter, and put the filter wheel on.  I've been meaning to try using the CLS filter for luminance on my monochrome ZWO ASI1600MM Pro anyway, and now I can swap them in and out without even having to change focus.  Luckily, my Starlight Xpress filter wheel is super easy to swap filters in and out of -- it has five thumbscrews on the front, and then the filter wheel carousel just slides right out, no tools needed.  

A couple of brighter stars had appeared, so I slewed to Deneb to focus so that I could do a star alignment.  (The PWI software lets you do a "quick align," where you just say you're at the home index position and it bases your alignment model on that).  After auto-stretching the histogram in SharpCap and changing the exposure time to 1s, I could see a defocused Deneb in the frame (after I put the star in my red dot sight).  However, I ran into an immediate problem: the manual controls for my Robofocus weren't working, even though the pilot light was on.  I tried connecting it to my computer via serial-to-USB, but the Robofocus app wasn't detecting it.  Finally, I powered down the Robofocuser and just focused manually (the Robofocuser disengages a magnetic lock when it's shut off so that you can do this without breaking your focuser).  I'll have to keep investigating that.

I got focused using my Bahtinov mask, and then did an alignment with just some eastern stars, since my western view is largely blocked by my lemon tree, except up near the meridian.  After two stars and Saturn, the PWI software prompted me to do an All-Star Polar Alignment, which gave me a few options for stars near the horizon & meridian, and I chose Nunki, which was easily visible.  The mount slewed to where Nunki should be if I was perfectly polar aligned, and then I moved the mount there, and hit Done.  Easy!  The only hard part was using the mount controls via keyboard in the PWI app while also seeing my camera's live feed.  The slew controls have to be on top, but unfortunately the window their in is not separate from the main PWI window -- when I select that window, the whole PWI app comes back up on the screen, blocking SharpCap.  So I had to make each app half-screen in order to see my camera feed and have the PWI app open so I could actually slew the mount.  Very annoying!  Anyway, I'm glad Celestron has that All-Star Polar Alignment feature, since the roof over my porch, my neighbor's garage, and my plum tree block the north star.


With that complete, it was time to do some testing.  I wanted to see if the auto-meridian flip would work (and make sure cables wouldn't get snagged).  So I found a star that was about to cross the meridian, got the settings set, and gave it a try.  Plate solving was being really slow, however.  By the time I changed some settings, the star would have already crossed, so when I told the mount to slew to that target so I could test the flip, it would already flip just on the slew.  This happened about three times before I gave up and decided just to have it stop imaging about a half hour after the target transitted (my mount can go 20 degrees past the meridian).  After I calibrated guiding, my original target for the evening, M27 Dumbbell Nebula, was only about an hour away from going behind the tree, so I decided to pick a different target and settled on the Eastern Veil Nebula.  Slewing to it put it mostly where I wanted it inside the frame, so I next started testing what exposure time I could get that night.  30s had nice round stars, then 60s, then 120s.  With the CLS filter, the histogram peak was still pretty far toward the left, and since this was an experiment night anyway, I went ahead and just left it at 120s.  I'll see how far I can push it with guiding on future nights.  Guiding wasn't looking all that great, but a 530mm focal length on the telescope is pretty forgiving.


I ticked the box in Equipment Profile to park the mount upon sequence completion, set the number of frames to take, and went inside to get ready for bed.  I was worried that the park command wouldn't work, but it at least should stop the mount from tracking.  I also took comfort in knowing that even if the mount kept tracking, there was a safety stop in RA that would stop the gears if it was hit.  After I got ready for bed, I went out and checked it one more time -- everything looked good.  

While I was working outside, my neighbors behind me were on the other side of the fence sitting around a fire pit and singing.  One person played guitar, and another played cello.  It was a family choir; they even harmonized together.  It was lovely being serenaded while I worked!  I wanted to grab my cello and join!  They sang songs like Space Oddity, The Boxer, and even the Foo Fighter's "Stranger Things Have Happened," along with some tunes with which I was unfamiliar.  I did sing along to a few songs quietly, which was fun.  (I also hoped that the smoke wouldn't fuzz out my images too much!)

I slept in and got up around 8 AM the next morning, and went outside to go check it.  Sure enough, it was all the way over on one side -- the park command hadn't worked.  And the gears were still spinning!  I was very worried about this.  I cut the power to the mount and logged back into my tablet to see what had happened.  It was still trying to park it -- I think it didn't give PHD a command to stop guiding, and that was interfering with the ability for it to park.  When I manually brought the mount back to home position, the dec axis column slid down a bit -- I had forgotten that when I was troubleshooting the issue with the frozen dec axis, some extra space had been created, and the dec column wasn't quite tightened down all the way (which would have re-frozen it), so when it was tipped past the meridian, it slides out a tiny bit.  As it turns out, it's enough for the gears to disengage, which is why they were spinning freely when I got out there this morning.  This meant they weren't actually turning against a load, so I most likely didn't actually break anything.  Phew!  I will just have to set SequenceGenerator Pro to do the meridian flip shortly past the meridian so that the column doesn't slip.

Still in my pajamas, I went ahead and started troubleshooting the parking issue.  As it turns out, I didn't have a park location set, so I set that in the PWI app, which is what SGP commands to park.  I tested it, and it worked!  Then I created a dummy sequence to make sure it would work in a sequence and not just with me hitting the "park" button.  I added two targets to the target list -- two stars in Ursa Major to save me some time in slewing.  I set them just to slew and not also center since it was daytime anyway.  I also disabled guiding so that it wouldn't wait for PHD to be ready.  After some fiddling with settings, a beautiful thing occurred -- it slewed to the first star, took some 1-second exposures until I stop time that I set, then slewed to the second star, took a set number of exposures, and then parked itself in the home position!  It continued tracking, however, so I'll have to work on getting it to stop tracking too.  (If you tick the "park at end of sequence" button, you cannot also tick the "stop tracking at the end of sequence" button.)  I might be able to get around this by having it disconnect equipment at the end of the sequence.  

Things are starting to come together!  Can't wait to start getting bunches of data to process.

Eastern Veil Nebula, single 120s frame
(click here for the final result!)