×

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

Bi-monthly release with minor bug fixes and improvements

SynScan mount under KStars/Ekos not responding

  • Posts: 86
  • Thank you received: 5
[Apologies, this should have been posted in the "mounts" topic but I don't seem to be able to delete it from here so am leaving it rather than double-posting]

Hi there. I'm setting up a system with Indi server on a Raspberry Pi-like small board computer (a Hummingboard II) running Arch Linux and Kstars/Ekos on a separate Linux client PC. The Indi server has connected to it a ZWO ASI CCD and a HEQ5 mount (via the SynScan port using a USB adapter cable).

The ZWO camera connects up fine but I can't get the mount part to work. Can anyone tell what I'm doing wrong or suggest some debug steps I can take?

I am running indi server with:

indiserver indi_asi_ccd indi_synscan

I have verified that the SynScan port works with a SynScan handset. I have verified that the USB connection appears on Linux on the small board computer and I have given it a recognisable port name (/dev/heq5) via a rules file. I have entered that port name in the Kstars Indi configuration screen and have entered "SynScan" as the remote telescope name in the Ekos screen. But when I attempt a connection to the mount Ekos says:

2016-03-25T23:00:10: Mount Not Responding
...and the Indi server side spits out the following debug (with the -vv option):

2016-03-25T23:00:08: Client 0: read <newSwitchVector device='SynScan' name='CONNECTION'>
2016-03-25T23:00:08: Driver indi_synscan: queuing responsible for <newSwitchVector device='SynScan' name='CONNECTION'>
2016-03-25T23:00:08: Driver indi_synscan: sending <newSwitchVector device="SynScan" name="CONNECTION
2016-03-25T23:00:10: Driver indi_synscan: read <message device='SynScan' name=''>
2016-03-25T23:00:10: Client 0: queuing <message device='SynScan' name=''>
2016-03-25T23:00:10: Client 0: sending <message device="SynScan" timestamp="2016-03-25T23
2016-03-25T23:00:10: Driver indi_synscan: read <setSwitchVector device='SynScan' name='CONNECTION'>
2016-03-25T23:00:10: Client 0: queuing <setSwitchVector device='SynScan' name='CONNECTION'>
2016-03-25T23:00:10: Client 0: sending <setSwitchVector device="SynScan" name="CONNECTION

I have also attached a full log file taken with the -vvv switch.

I must have some configuration somewhere wrong. Any ideas? I have verified that the SynScan name is correct because if I mistype it Ekos objects that it can't find the other end, rather than that the mount is not responding. I noted the comment in the SynScan driver page that I may need to enter "sudo adduser $USER dialout", but there is no dialout group on this Linux installation and I when I attempt to add it for my user I'm told it doesn't exist.

The log lines:

2016-03-25T23:00:08: Driver indi_synscan: sending <newSwitchVector device="SynScan" name="CONNECTION
2016-03-25T23:00:10: Driver indi_synscan: read <message device='SynScan' name=''>

...look a bit suspicious to me, with the end of the first being truncated and the read line showing an empty name field.

FYI:

INDI Library: 1.0.0
Code $Rev: 2039 $. Protocol 1.7.

Rob
Last edit: 8 years 3 days ago by Rob Meades. Reason: Add apology.
8 years 3 days ago #7421
Attachments:

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

  • Posts: 193
  • Thank you received: 46
The log shows 'mount not responding' messages. That means when the driver polls the hand controller for an echo return, it's not getting the echo.

Confirm, you have the serial port plugged into the hand controller (not the mount) and it's set to 9600 baud with the correct port defined before you hit the connect button.
The following user(s) said Thank You: Rob Meades
8 years 3 days ago #7428

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

  • Posts: 86
  • Thank you received: 5
Ah, many thanks for the swift response, that's identified the problem.

The cable I purchased was an " EQ Direct " cable to plug into the mount, rather than something to plug into the SynScan controller (as I didn't want to have to have the SynScan handset lying around). So my next questions is, is there an Indi driver that would take advantage of the mount's protocol directly or do I have to think again?
8 years 3 days ago #7430

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

  • Posts: 86
  • Thank you received: 5
[Answering my own question]

Silly me, EqMod is what I should have been using all along. I seem to have a problem with it at the moment:

2016-03-26T11:08:55: startup: indiserver -vvv indi_eqmod_telescope 
2016-03-26T11:08:55: Driver indi_eqmod_telescope: pid=20689 rfd=3 wfd=6 efd=7
2016-03-26T11:08:55: listening to port 7624 on fd 4
2016-03-26T11:08:55: Driver indi_eqmod_telescope: sending msg copy 1 nq 1:
<getProperties version='1.7'/>
 
2016-03-26T11:08:55: Driver indi_eqmod_telescope: 2016-03-26T11:08:55: Driver indi_eqmod_telescope: execlp: No such file or directory
2016-03-26T11:08:55: Driver indi_eqmod_telescope: stderr EOF
2016-03-26T11:08:55: Driver indi_eqmod_telescope: restart #1

...but I'll update my source code to the very latest and have a poke around then ask a more sensible question.

Thanks!

Rob
Last edit: 8 years 3 days ago by Rob Meades.
8 years 3 days ago #7432

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

Time to create page: 1.093 seconds