Paul Haese
01-09-2013, 08:36 PM
The image has a bit of a story to it.
About a month ago I started doing this image to test some automation issues and to chase the dark nebula in the region. Where things got interesting was having failures of the camera disconnecting. Not thinking I took the scope off the mount to install a USB cable through the mount to test if the it was a USB drop out caused by the roll off roof drive system. Not thinking I did not put registration marks to get the scope back in the same orientation again. Nor did I know at the time or even consider putting more cables through at the same time. Big mistake. The USB drop out was most likely caused by an ASCOM incompatibility in the system (I think (my new word for it could be anything) it is the Mount Hub Pro and its ascom driver or API). Subsequently I took more data only to have more drops out and hangs from other pieces of equipment. That meant taking the scope off the mount again and running all the cables through and once again having a slightly different rotation again. Sort of compensated by the rotator and pinpoint but not exact.
So the bottom line the last few days I collected more data and just put it altogether which went from what I thought was a train wreck to something half reasonable. 10 hours of data and ok looking.
Click here (http://paulhaese.net/M7.html)for the larger image.
About a month ago I started doing this image to test some automation issues and to chase the dark nebula in the region. Where things got interesting was having failures of the camera disconnecting. Not thinking I took the scope off the mount to install a USB cable through the mount to test if the it was a USB drop out caused by the roll off roof drive system. Not thinking I did not put registration marks to get the scope back in the same orientation again. Nor did I know at the time or even consider putting more cables through at the same time. Big mistake. The USB drop out was most likely caused by an ASCOM incompatibility in the system (I think (my new word for it could be anything) it is the Mount Hub Pro and its ascom driver or API). Subsequently I took more data only to have more drops out and hangs from other pieces of equipment. That meant taking the scope off the mount again and running all the cables through and once again having a slightly different rotation again. Sort of compensated by the rotator and pinpoint but not exact.
So the bottom line the last few days I collected more data and just put it altogether which went from what I thought was a train wreck to something half reasonable. 10 hours of data and ok looking.
Click here (http://paulhaese.net/M7.html)for the larger image.