×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Problem connecting HEQ5 mount to PHD2 under linux

  • Posts: 8
  • Thank you received: 0
Hi all,

First, congrats to you all for this awesome work with INDI driver (support and development stuff)!

I'm new trying to get running all the astronomical setup under linux... I downloaded a distro based on linux Mint called "DistroAstro" and I've been able of making it works more or less. Kstars detects my HEQ5 mount and CCD camera (ASI 120 MC).

The thing is that I want to use PHD2 for guiding but after installing the .deb package, I can run the camera but I cannot do the same with the mount... If I run PHD2 from the shell I see the following error every time I click on the "Connect" icon for the mount:
"connect: connection refused" .

I've tried to add the driver path into the "driver" field that appears into the PHD2's INDI configuration window (/usr/bin/indi_synscan) with no luck, as the field is cleared once I click on "Connect" again... I've added my user into "dialout" group too..

Any idea or suggestion? I've attached a screenshot btw...

Many thanks mates :)
8 years 6 months ago #5088
Attachments:

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

  • Posts: 210
  • Thank you received: 104
Hi,
You must start your indiserver with the mount and camera driver, something like "indiserver indi_synscan indi_asi_ccd".
Then in phd2 you can select "SynScan" for the mount Driver field.
8 years 6 months ago #5094

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

  • Posts: 8
  • Thank you received: 0
Hi pch,

Thanks for replying, I think I've already started the server as I've launched the Indi Serve from Ekos via Kstarts...There I can manage both camera and mount... but from PHD, I can only manage the camera... So I guess the server started properly... (Although I haven't done it manually like you mention...).

I tried adding "synscan" into the driver field too with no success either (could it be case sensitive??)

Thanks again,
KR, Miguel
8 years 6 months ago #5096

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

  • Posts: 210
  • Thank you received: 104
I make some testing and it look like indi_asi_ccd do not respond to <getProperties version='1.7'/> and phd2 rely on this information.

Try to start a server with only indi_synscan : indiserver indi_synscan
and look if the SynScan appear in the mount driver list.

Here the description of the problem I have with indi_asi_ccd using last version from ppa:
Server log:
$ indiserver -vvv indi_asi_ccd
2015-09-16T05:40:43: startup: indiserver -vvv indi_asi_ccd
2015-09-16T05:40:43: Driver indi_asi_ccd: pid=5800 rfd=3 wfd=6 efd=7
2015-09-16T05:40:43: listening to port 7624 on fd 4
2015-09-16T05:40:43: Driver indi_asi_ccd: sending msg copy 1 nq 1:
<getProperties version='1.7'/>

2015-09-16T05:40:52: Client 0: new arrival from 127.0.0.1:50665 - welcome!
2015-09-16T05:40:59: Client 0: read getProperties
2015-09-16T05:40:59: Driver indi_asi_ccd: queuing responsible for <getProperties device='' name=''>
2015-09-16T05:40:59: Driver indi_asi_ccd: sending msg copy 1 nq 1:
<getProperties version="1.7"/>

Client log:
$ telnet localhost 7624
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
<getProperties version='1.7'/>
... no response forever
8 years 6 months ago #5110

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

Patrick, the reason there is no response is that unless the camera is attached, no driver is constructed. This happens in drivers where they support multiple-devices-per-driver such as ASI/QHY/SX..etc.
8 years 6 months ago #5111

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


If you're already using Ekos, did you try guiding from there?
8 years 6 months ago #5112

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

  • Posts: 8
  • Thank you received: 0
Hi Patrick and knro

I haven't tried guiding from Kstars yet, I'm just trying to make it works before going outside... I think it will work from Ekos as both camera and mount seems to have connected well... Currently I'm at work, when I get home I could try running indiserver only with the mount driver to see if the camera one is causing the issue... If it works, then I will have the problem that the camera is not connected.. hehe...

The reason why I want to use PHD for guiding is to be able to use its functionality of Drift Alignment.... I don't know if it could be done through Ekos as well...

Many thanks for your help!
8 years 6 months ago #5113

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

No drift alignment in Ekos. Instead, it uses astrometry to help your polar alignment and make corrections to make misalignments more manageable.
8 years 6 months ago #5114

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

  • Posts: 8
  • Thank you received: 0
Interesting... I didn't know it... does astrometry method require internet connection to run?
8 years 6 months ago #5115

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

No internet connection is required, you can solve offline.
8 years 6 months ago #5116

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

  • Posts: 9
  • Thank you received: 1
I'm doing very much what you're trying to do, and ran into what looks like the same problem. You're very close. The issue is EKOS increments the port listened on by the indi server, so while it may start at 7624, after a restart it will be 7625 etc. you can figure out the port in use by doing a ps grepping for the indi server process.

Forget about drift alignment, plate solving is a little more effort to setup, but is awesome when working.

I should add that I'm using PHD2 for several reasons, one is that with the ASI-120MM, the ekos guide module repeatedly halts at the same point. I suspect this is due to the asi indi driver not keeping up on my hardware. I use the built in ZWO driver in PHD2 and it's very stable, plus I can keep the window off to the side and keep an eye on it while doing other stuff in Ekos, and the graph in phd2 shows the corrections sent.

While having an all in one tool is great for getting going and ease of integration, there's something to be said for specialised tools and being able to swap them out. Fortunately indi allows this. Handling sequencing with dithering is slightly more challenging this way but can be done.

I'll append a screenshot of it all working afterwards.

UPDATED: added images, including port setup and the first imaging run. Despite the oscillations in RA (I was experimenting with settings) and no effort with balance or imbalance I got decent results for 5 minute exposures on the first night out. Works well.


Andrew
Last edit: 8 years 6 months ago by Andrew Nilsson. Reason: added images
8 years 6 months ago #5125
Attachments:

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

  • Posts: 8
  • Thank you received: 0
Hi knro and Andy,

Thank you very much for your guidance... wow how interesting is this thread becoming for me... hehe
I didn't know about those alignment methods, I'm eager to try them, I will have to investigate how to use the astrometry and plate solving methods (because I guess they are different... right?)

I will try to change the INDI port in PDH2 later on and see if it works for me too (It would be nice...)

Thanks again mates!
8 years 6 months ago #5126

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

Time to create page: 0.895 seconds