![]() The mount would be connected via either USB or WiFi to the indiserver computer. The guide camera will be connected to a computer via USB (either a laptop or an on-scope IOT type computer). Both the mount and camera would be connected to the computer running the indiserver service. If, for example you choose to use Ekos (KStars) internal guider, you would have an indi mount driver and an indi camera driver. The more current way to do guiding (sans ST4 cable) is to talk to the mount through INDI or ASCOM drivers (Linux or Windoze). Although, if you move across the sky a lot to various targets, you probably have to do some centering and other minor tweaks. That works well if your star alignments during setup are tight. Stellarium, in that case, does the initial point and then an external guiding program keeps the tracking honest. The above setup is reasonable for most mounts as a setup with Stellarium. It relies on the mount to talk to the camera (ST4) port or the use of an external, such as PHD2 to talk to the camera and mount through drivers. Want to hear others comment though just so that my understanding is correct! If you have USB to mount, this does the work for youġ) Mount (direct to PC via USB, essentially the same as mount-controller-computer)Ģ) Guide camera, to allow PHD2 to get signalģ) DSLR controller (allows computer to trigger camera), although I could set multiple exposure mode on the camera and ignore this but I don't think that's a good idea - might have to change settings if over/underexposing ST4 adds the extra complication that the computer sends info back to camera for the camera to send to the mount. Once you use Stellarium to slew to object, start PHD2 and it should pass the 'pulses' to the mount via the USB to handset to the mount, effectively keeping the guide star in the same position, meaning the mount is correctly tracking, i.e. In a nutshell, the same cable used to connect to the controller (as step 3). It would help my understanding greatly before i take the plunge □ I wonder if you could describe how i adapt this routine for connecting a guide camera, which port, which lead etc ? ![]() USB cable from Guide camera to laptop running PHD2, USB cable from Laptop to mount ? but which port on which part of the mount, I have an EQM-35 PRO with Handset and separate module that the handset plugs into.Ģ) Switch on mount, and perform 2 star alignmentģ) Once aligned successful I connect the handset to my laptop via "square" USB to standard laptop USB (Printer cable)Ĥ) Start Stellarium and find and slew to target from Stellarium Sure, it works for planets and bright things.but guiding is the ultimate solution. Unguided imaging will only get you so far. One could argue that for guiding, you might get a more pinpoint image from a monochrome camera and therefore the ZWO mono is a better option. I have the SVBONY 9x50 finder/guide scope which as a finder works really well.įrankly, I don't think I would bother with the SV305/Pro.unless your (very old) mount has a specific need for the ST4 port. Im using a Windows 10 lappy so not sure about the driver issues. ![]() How is the 305 connected for guiding i can only see one port on the Camera ? Very interesting, so it could be employed as an unguided planetary imager, I notice it’s the 305 model again which then begs the question is it worth the extra £’s for a ZWO for example ? Or are we thinking the 305 is a better guide camera than the basic ZWO ? V4L2 drivers are basically webcam drivers. The SV205 also uses the V4L2 driver set (in Linux). It works OK, but I haven't used it in a while, mostly because I don't care for the V4L2 driver set in Linux. I haven't used the SV205, but have a SV105. Here's an image I took with the guide scope and SV305 using PHD2 as the "imaging software." I didn't bother with sharp focus, as it was just an experiment at the time. Just FYI, I also use the SVBony guide scope.
0 Comments
Leave a Reply. |