Thanks, Yes I tried the Synscan and a few others that looked interesting however each one returned that message.

Is there a way of getting more information out of the log? I tried clicking all the log checkboxes however nothing else. I noticed there is a debug version of indi if that would help. Anyway thanks just looking at other solutions out there this looks like a fun project.

I am using the virtual machine that was assembled, and then I applied all the updates.

It seems to be a communication error with /dev/ttyUSB0. Either when setting the parameters, or when reading response and getting -1 as number of bytes read.The AZEQ5 has a USB client port (type B ) which can be used to communicate directly with a computer. I suppose this is the one you use. Try typing lsusb in a terminal to see which USB-RS232 chipset is in use. Concerning indi drivers, you may use either indi-eqmod or indi_skywatcherAPIMount (in altaz mode). Recent Skywatcher firmware use autobaudrate when initializing the RS232 communication, so if the mount has already been initialized, this may be a problem as indi-eqmod defaults to 9600 bauds. So you may try to change the baudrate in the indi-eqmod driver. Finally you could also check the connection by hand using minicom or picocom to directly talk to the mount and sets the communication parameters (should be 8N1 i.e. 8bits, no parity, one stop bit). If you succeed to connect using minicom or picocom, try sending :e1 followed with ctrl-J and sees if there is a response (should be a = sign followed with some figures).
If you use a virtual machine, the host os (or a process on the host os) may also interfere with the communication.

Thank you for the reply this was quite useful.

First of all the onboard USB Chipset is: "pl2303 prolific"

I was unable to connect to the mount with the minicom. However I tried it with my host machine and it worked (through Putty) the :e1 command reported the motor drive version 030106.

I also tried on a second computer (virtualbox). So it would seem the biggest issue I have is it does not appear to be working through the virtual machine at this point. This is unfortunate for testing purposes but I may have an older computer that I may be able to install Ubuntu native so I can test with.

Thanks again.

Did you google for virtualbox usb share on windows host? It seems that virtualbox should install an USB filter driver, and that you have to make some adjustments when switching from host to guest OS. But I don't use it so can't really help.

Hi everyone, just an update. I installed Ubuntu 15.10 on a separate physical machine and had the exact same problem. I do have some more information:

It's reporting that it's attempting to set the baud rate to 49664 instead of 115200 which is selected. When choosing other baud rates it shows the correct parameter.

When I try minicom it did not work connecting to the port so I installed putty for ubuntu and it worked perfectly reporting the motor version!

So I ask if someone could check the baud rate 115200 is in fact setup to be passed, and if so where is this 49664 number coming from.

Thanks!

PS. 115200 is the required baud rate for this mount.

You are right, there was a problem with the baud rate and it is now fixed. Should be available in tomorrow's PPA. Thanks!

I have the same mount and I'm experiencing the same problems in ubuntu 14.04.
When I set the baud rate of the Eqmod driver to 115200 it gives the following message:
Connecting to port /dev/ttyUSB0 at speed 49664
I checked that the 230400 has a similar error but the other baud rates report the correct speed.

I searched in the source files for this option but didn't found it.
While the change is not included in the PPA, could you tell us in which source file can we make the correction?

Entilza,
have you been able to connect with eqmod driver?
Let me know about your progress.
Using the screen serial terminal set to 115200, I receive =030106 in response to :e1
But the driver still cannot connect at 115200.

The good news is that I have successfully connected trough a separated USB->SERIAL converter and the SERIAL->AUTO-GUIDE port in the hand controller using the indi_synscan driver. With this set up the kstars program is able to slew nicely the mount however, with the program I wanted the most, PHD2 (autoguiding program), I'm having some problem that I cannot solve.
In PHD2 the indi configuration window connects nicely to the mount but when I close this window and try to reconnect from the main program window, I get only Connection Failed.
So none of the ways are working for me.

Thanks for any help.

The prior fixes were not propagated to EQMod, so I just did that. With tomorrow's PPA, you can connect @115200. Regarding PHD2, did you try Ekos guide module first?

I have realized today, the changes I propogated out the other day for the synscan driver are indeed broken. The quick work around, dont set any sync points. If you do, then you need to turn off the alignment layer in the alignment tab after setting a second one, because the data will quickly become garbage if you dont.

I'm working on trying to figure out what's wrong, and how to fix it, but I dont have a solution that works in all cases yet. If I cant get it working this evening, I'll revert the current driver code back to what it was before this round of updates went in.

Perfect.
Today I connected at 115200 with eqmod.

knro, I didn't knew ekos could do auto-guiding. In fact I'm beginning to put the pieces together on controlling a mount with a computer. Surely I'll give ekos a try. It seems to do everything needed for astrophotography.

Thank you!

I saw the update before today got the 115200 baud working, I was going to try it however an update went after and it now causes segmentation faults when I start INDI.

This is using the virtual machine, and should be easily reproduced.

Jan 5 07:04:41 ekos kernel: [ 2164.485975] indi_eqmod_tele[30773]: segfault at 40 ip 00007fb49c4dba40 sp 00007ffdbe6c3330 error 6 in libc-2.21.so[7fb49c48a000+1c0000]
Jan 5 07:04:41 ekos kernel: [ 2164.650137] indi_eqmod_tele[30778]: segfault at 40 ip 00007f5fd7b6fa40 sp 00007ffe7f210130 error 6 in libc-2.21.so[7f5fd7b1e000+1c0000]
Jan 5 07:04:41 ekos kernel: [ 2164.818740] indi_eqmod_tele[30783]: segfault at 40 ip 00007f9e346d8a40 sp 00007ffd4081f160 error 6 in libc-2.21.so[7f9e34687000+1c0000]
Jan 5 07:04:45 ekos kernel: [ 2168.335466] show_signal_msg: 19 callbacks suppressed
Jan 5 07:04:45 ekos kernel: [ 2168.335471] indi_eqmod_tele[30883]: segfault at 40 ip 00007f59caa4aa40 sp 00007ffe43a2b8b0 error 6 in libc-2.21.so[7f59ca9f9000+1c0000]
Jan 5 07:04:45 ekos kernel: [ 2168.503865] indi_eqmod_tele[30888]: segfault at 40 ip 00007f63374e3a40 sp 00007ffcb95b2690 error 6 in libc-2.21.so[7f6337492000+1c0000]
Jan 5 07:04:45 ekos kernel: [ 2168.686247] indi_eqmod_tele[30893]: segfault at 40 ip 00007f5488efca40 sp 00007fff7758d930 error 6 in libc-2.21.so[7f5488eab000+1c0000]
Jan 5 07:04:45 ekos kernel: [ 2168.852761] indi_eqmod_tele[30898]: segfault at 40 ip 00007efd591aca40 sp 00007ffd34a8e580 error 6 in libc-2.21.so[7efd5915b000+1c0000]
Jan 5 07:04:45 ekos kernel: [ 2169.031421] indi_eqmod_tele[30903]: segfault at 40 ip 00