[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