×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Question about Ekos/PHD2 and guidescope/tracker

  • Posts: 169
  • Thank you received: 5
Hi folks, I'm new to all this and trying to understand the relation of these programs and their interfacing with hardware. As I understand it, my ZWO ASI120mm cam connects to the computer by USB, and to my Skyguider Pro tracker via ST4.

Now, my Skyguider Pro is not listed in the iOptron product list in Ekos/PHD2. Is this because the Skyguider is single axis and the supported mount list is for dual axis mounts?

When the hardware is set as described above, Ekos/PHD2 see the ASI120, but not the tracker. Am I to assume that this isn't important, because the programs will communicate with the guide cam and the guide cam will take care of sending the proper correction signals to the tracker?

If not, why is the tracker not recognized? Do I need to plug the tracker directly into the Pi 4 instead of the guide cam's ST4 port?

Thanks for any info on this.
3 years 10 months ago #54916

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
The iOptron Skyguider Pro is not a GoTo mount, so KStars can not control it. In its place run the Telescope Simulator, it should then show a position if you attempt to plate solve.
As you can not send slew commands to this mount, you will have to use the ST4 cable directly between the camera and the mount's guideport and select On-Camera for 'Mount' in the autoguider configuration.

Also worth noting is the USB2.0 version of the ASI120mm has compatibility issues with Linux. But in my experience can work as an autoguider reasonably well on the Raspberry Pi4 and the compatibility firmware installed on the camera. This is not an issue with the USB3 or Mini version.
3 years 10 months ago #54921

Please Log in or Create an account to join the conversation.

  • Posts: 169
  • Thank you received: 5
Thanks for your reply. So am I running telescope simulator with the settings of my actual gear, so as Ekos/PHD2 tracks it sends the proper correction data back to the guide cam, which will in turn send the data to the tracker? Also, I noticed there is a mount driver for another mount I just got, an Explore Scientific iEXOS 100. When using that unit's setting, do I plug the mount directly to the Pi 4 network jack, or do I continue to run it via the guide cam?
Thank you for your time.
3 years 10 months ago #54964

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
The telescope simulator doesn't serve much purpose in practice. It is mainly a placeholder mount, as a valid profile requires a mount to be listed. You are probably mainly interested in EKOS to manage your capture sequence and guiding. Necessary if you dither between frames. As long as you choose On Camera as the mount in the autoguider, it will send the corrections over the ST4 cable relayed through the guidecam.

As for your iEXOS 100, I'm not familiar with it's PC interface, but it may well be network based. Then presumably what you described should work. And it will give you the option to pulse-guide that mount without the need for the ST4 cable. In that situation you would select the INDI Driver for iEXOS 100 as the mount settings in the auto-guider to output the corrections.
3 years 10 months ago #54966

Please Log in or Create an account to join the conversation.

  • Posts: 169
  • Thank you received: 5
Thanks again for your reply. This is all really confusing to me, trying to set up this gear. That I'm doing all this on Linux doesn't help either, but that's beside the point here. :unsure:

So I really don't understand the point of the telescope simulator then. Honestly, I'm not understanding any of it. More than anything else at this time, I just want the hardware/software to be able to polar align, be able to track, and send the proper tracking correction data to the tracker(s). So if I somewhat understand this correctly, in my case the only hardware that Ekos/PHD2 really needs to see is the guide cam, everything else is unimportant in my simple setup, which is either the Skyguider Pro with an Astro Tech AT60ED and either an M4/3, APS-C, or full frame camera, or the iEXOS 100 EQ mount similarly set up. There are no INDI drivers for my M4/3 cameras, and I've only seen a generic Nikon driver for my APS-C and FF Nikons, but I have yet to have the programs actually see any of the cameras, so I wrote that off altogether and will be using an external intervalometer instead to control the cameras. With the new iEXOS 100 mount, I have no idea at this time how it should be connected. I'm just gonna have to keep poking around I guess.
3 years 10 months ago #54980

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
Let me break it down for you:

iOptron Skyguider requires ST4. Set 'On Camera' PHD2. This is true whether or not you are using PHD2 with EKOS or by itself on Window, Mac or Linux.
If you wish try the internal guider in EKOS it will instead be Via: ZWO CCD ASI120MM.


The Telescope Simulator (Found under Other) will have to be included in the Profile of INDI Drivers if you wish to use the plate-solve features of the Polar Align Assistant in EKOS.
To do so will require manually rotating the mount in RA approximately 30° between frames in that routine.


To control the iEXOS 100 mount. Add it to the profile instead of Telescope Simulator. It will also allow you to pulse guide without the need for an ST4 cable. Simply choose the mount driver instead of 'On Camera'


As for your M4/3 Camera. I am not familiar with it, but it may work with the GPhoto Driver that supports many camera models.
www.gphoto.org/proj/libgphoto2/support.php
The following user(s) said Thank You: Phil
3 years 10 months ago #54988
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 1119
  • Thank you received: 182

What Nikon models do you have? For instance, I have the D3300, so the lowest end model, and that is fully compatible with Ekos without the need of an intervalometer.

Also, the Skyguider Pro has an excellent polar scope, I would just use that one for alignment. Then all that is left is guiding and for that I would use PHD2 via ST4 cable, if you choose an intervalometer anyway, because that can be done then without calling up Ekos.

Andrew, correct me if I'm wrong, but drift alignment in PHD2 does not require a mount to be connected, is that correct? I only tried that one time and I do not remember.
3 years 10 months ago #54990

Please Log in or Create an account to join the conversation.

  • Posts: 169
  • Thank you received: 5
Hey thanks so much for that. Raining right now but when I wake up I'm just gonna plug everything in and see if it sees everything. I have a question tho on this:
"To control the iEXOS 100 mount. Add it to the profile instead of Telescope Simulator. It will also allow you to pulse guide without the need for an ST4 cable."
So how would the iEXOS 100 communicate with the computer? It has 3 ports I believe, ST4, USB, and DB9. Do I connect it to the computer through the USB port?
Thanks again for laying that out.

For El Corazon, the Nikon bodies I have are a D600 FF and a D5100 APS-C. The Skyguider polar scopes are well known to be out of alignment often. Mine deviates mildly from center to the edge of the first circle at pretty much 270°. I also just got the William Optics alt-az mount for it, which will make alignment, whether optical or digital, much more straightforward affair.
Thanks again.
3 years 10 months ago #54992

Please Log in or Create an account to join the conversation.

  • Posts: 1119
  • Thank you received: 182
I have the D600 as well, that definitely works fine.

An Alt/Az mount is not going to be suitable for serious astrophotography unless you also use a field rotator. That would make things unnecessarily complicated and expensive.
Last edit: 3 years 10 months ago by Jose Corazon.
3 years 10 months ago #54999

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
Correct. I haven't tried it, but I reason that PHD2 will have to be calibrated to perform drift alignment. So that would require some kind of guided tracking mount.
I am pretty sure he is talking about a latitude adjustment base for the star tracker. Not an Alt-Az tracking mount. williamoptics.com/high-latitude-wo-vixen-style-base-mount
3 years 10 months ago #55006

Please Log in or Create an account to join the conversation.

  • Posts: 1119
  • Thank you received: 182


I had a quick look at PHD2 PA last night. There are two methods: Drift alignment and Static alignment. For static alignment it would definitely need a tracking mount. For the drift alignment it looked like that might work without one.
My mount was too far off the NCP, so the crosshairs were out of the FOV of my guide cam, but the drift line stabilized, so I assume I would have been able to align using that method. It does not seem to take a lot longer than the PA method in Ekos, the drift line took only a minute to stabilize. But of course, that would have to be repeated 3 or 4 times to get a good PA. So in the end, it does probably take longer. But it should be possible to use that method for a non-tracking mount.

Thanks for clarifying the Alt/Az part. I don't have that device, why would one need it? The Skyguider Pro can be adjusted just fine without it.
3 years 10 months ago #55008

Please Log in or Create an account to join the conversation.

  • Posts: 1309
  • Thank you received: 226
The mount appears to have two options for PC control. Wired, over USB, and Wireless over internal WiFi. The mount appears to be configured for WiFi as the Default, and requires a few steps to switch it to Serial for UBS connection.
Pages 14/15:

This browser does not support PDFs. Please download the PDF to view it: Download PDF

The following user(s) said Thank You: Phil
3 years 10 months ago #55009
Attachments:

Please Log in or Create an account to join the conversation.

Time to create page: 0.342 seconds