Print

[Gonzo]

Hi guys,

I'm Gonzo from SGL, been using the AstroEQ without any problems so far however after taking a break playing with it.... it doesn't seem to be working again.

I'm using a Raspberry pi, AstroEQ (purchased, not built).
I have in /dev/:

Code: [Select]

crw-rw---T 1 root dialout 166,   0 Jan 25 16:50 ttyACM0
lrwxrwxrwx 1 root root          12 Jan 25 16:46 ttyUSB0 -> /dev/ttyACM0

dmesg:

Code: [Select]

[ 5603.082103] usb 1-1.4: USB disconnect, device number 5
[ 5604.874359] usb 1-1.2: USB disconnect, device number 10
[ 5608.950462] usb 1-1.4: new full-speed USB device number 11 using dwc_otg
[ 5609.068491] usb 1-1.4: New USB device found, idVendor=04d8, idProduct=000a
[ 5609.068530] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5609.068549] usb 1-1.4: Product: CDC RS-232 Emulation Port
[ 5609.068565] usb 1-1.4: Manufacturer: Microchip Technology Inc.
[ 5609.082593] cdc_acm 1-1.4:1.0: This device cannot do calls on its own. It is not a modem.
[ 5609.082731] cdc_acm 1-1.4:1.0: ttyACM0: USB ACM device


I am able to use the astroequoloader (when I ln -s ttyS64) without any issues.

The issue which was never there before is that after starting the indi server, I am unable to connect to the AstroEQ.
I get errors like:

Code: [Select]

tty read failed, check connection: Timeout error

and

<setSwitchVector device="EQMod Mount" name="CONNECTION" state="Busy" timeout="60" timestamp="2015-01-25T15:50:30" message="connecting to port /dev/ttyUSB0">


I have done the unplug power/usb plug power first then usb cable trick but no go.
I'm sure I must be missing something somewhere.


Could someone throw in some ideas as to why I'm getting /dev/ttyUSB0 resource busy???


Gonzo

[Gonzo]

If anyone is interested, head over to http://www.indilib.org/forum/general/557-unable-to-connect-to-dev-ttyusb0.html

Good news, installed EqMAC on my Mac and the AstroEQ works perfectly fine.
But still not working with indiserver, which was before.

[TCWORLD]

Hi Gonzo,

Glad you have found a solution. Sorry I haven't been able to get back to you sooner, been snowed under at work.

It might be worth asking on the RPi forum to see if something has changed between the working kernel and the latest one which could be causing the issue.

Regards,
Tom.

[Gonzo]

Hi Tom,

It was diving me nuts, I realised after reading an old post on the RPI forum they said that upgrading to the "latest" firmware/kernel is not always the best solution.
A quick re-install of the PI fixed it.
It's all sorted now, working correctly as intended.

Stephane aka Gonzo