syberand
-
Posts
4 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Events
Blogs
Posts posted by syberand
-
-
10 hours ago, si717 said:
i have the same mount i use a 4 port usb hub ,i connect my hand controller into it from the usb port on the hand controller if yours has this you need to download the hand control software from skywatcher,i also connect my guidecam direct into the usb hub and dslr into usb hub then from the usb hub i have one wire extention cable from the usb hub direct to one port on the laptop ,you do not need to connect st4 cable at all you just need the skywatcher hand control software and ascom platform drivers hope that gives a general idea in apt then all you have to do is connect dslr connect mount then open up phd2 when connecting to guide hope this helps fairly simple once its setup good luck
I haven't tried with the hand control software. To connect to the mount, I assume you are going through the handcontroller or do you have a special cable?
-
Ah, I knew I was missing something. I'm using a SW EQ5 Pro synscan. Does the mount also need to be connected to the computer?
-
Hi,
I am about to loose my mind. I have no idea if what I'm doing is correct or just wrong.To sum up:
I'm trying to set up dithering.The longer story:
I have a Skywatcher 150PDS with a Synscan. I'm using my Canon M50 on my SW and to aid tracking I have bought a ZWO 120 Mini.
On my laptop I'm running APT and PHD2. My laptop is connected to my DSLR which I control with APT and guidecam is connected to the laptop and to the mount with ST4.I have gotten autoguiding to work after a cold cold night. After that I thought, lets look at Dithering. In APT to go in to "Guide" and set it up as I have been able to understand from misc guides. And I can see in APT that it connects to PHD2.
When I start my sequence and it starts dithering, I can see in PHD2 it goes to pause and never seems to recover from it and APT just continues on "Dither".
What am I missing?
APT Dither and PHD2
in Getting Started With Imaging
Posted
I figured out the problem. I had the port number wrong. 4400, not the default 4300