The small residual comet drift is most probably because of field rotation around the guide star because of the quick polar alignment and poor guide scope parallelism. This is my set up: Windows 7 Laptop > 10m active USB 3.0 cable > 4 port powered Atolla USB 3. (MAKE SURE TTL SIDE IS CONNECTED TO MOUNT) 3. To show the result I make an animated GIF of the six RAW images just stretched and cropped, without any alignment: I’m trying to drive it from Stellarium using EQMOD but I’m running into a problem I haven’t the experience to solve. Connect serial cable from COM port of computer to the EQDirect module 2. But I wanted to be sure to show the comet movement so I keep at 0.95"/pixel. The seeing was unfortunately bad and I have normally imaged with a shorter focal length on this night. (MAKE SURE TTL SIDE IS CONNECTED TO MOUNT). ![]() The guide scope is a Skywatcher achro 80/400, the guide camera a DMK21.Īll running on Win7, I not wanted to mix Linux problem at this time. Connect serial cable from COM port of computer to the EQDirect module. The main camera is an Atik 314L+ drived by APT. Through it i connect to the mount via ascom. I take 6 x 10 minutes exposure with my 8" f/d7 Newtonian on a HEQ5 + Eqmod. Not a nina user but here is how I do things: first launch CDC Skychart, my planetarium program. The drift rate Arcsec/hour computed by CdC was 12 in RA and -37 in Dec. ![]() We can now test our connection using the EQASCOM Toolbox. The target is C/2014E2 Jacques on October 22 between 19h56UT and 20h56UT. Use the EQASCOM Toolbox to connect to the Mount. Finally I find some time, telescope access, and clear night to test the comet drift.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |