Hi! Finally I bought the telescope and today I tried it to run by Kstars/indi, but failed. Please see the attached pictures.
I tried LX200 GPS library.
lsusb output: ST-Ericsson is most probably the telescope. because when I plug out the telescope usb it disappears.

Please would anyone explain me why indi is showing such errors? What can I do now to control the telescope using kstars?

Thanks in advance!

First, check if you have /dev/ttyUSB0 , then as indicated in the FAQ , add your user to the dialout group and restart:

Hi!
I followed the FAQ but failed to work it out. Dialout user command does work. but ls -l /dev/ttyUSB0 shows: cannot access /dev/ttyUSB0: No such file or directory.
Note that LS8 connects with pc via Print port to USB cable.
Any further suggestion?

I'm not sure if ST-Ericsson is a USB Serial driver. Anyway, we can see what happens if you unplug it, then plug it back, and type
Post the output here.

Sorry for my late reply. I could not control the telescope yet. please help! Here is the output:

bao@bao-desktop:~$ dmesg | tail -n 20
[ 11.556640] brcmfmac: brcmf_add_if: ignore IF event
[ 11.565773] brcmfmac: power management disabled
[ 11.785255] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 11.785277] Bluetooth: BNEP filters: protocol multicast
[ 11.785302] Bluetooth: BNEP socket layer initialized
[ 12.760774] brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
[ 12.760798] brcmfmac: brcmf_add_if: ignore IF event
[ 24.407431] fuse init (API version 7.23)
[ 30.436181] Bluetooth: RFCOMM TTY layer initialized
[ 30.436245] Bluetooth: RFCOMM socket layer initialized
[ 30.436297] Bluetooth: RFCOMM ver 1.11
[ 72.972470] usb 1-1.2: USB disconnect, device number 4
[ 74.744076] usb 1-1.2: new high-speed USB device number 7 using dwc_otg
[ 74.844944] usb 1-1.2: New USB device found, idVendor=04cc, idProduct=0000
[ 74.844965] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 74.844979] usb 1-1.2: Product: Meade eFinder Serial Emulator
[ 74.844991] usb 1-1.2: Manufacturer: Meade
[ 74.845002] usb 1-1.2: SerialNumber: 1234567890
[ 74.846371] cdc_acm 1-1.2:1.0: Zero length descriptor references
[ 74.846397] cdc_acm: probe of 1-1.2:1.0 failed with error -22

To me it looks like not recognized USB port. What the bluetooth stuff is doing in the log?
Do you have a serial over BT device? What do you meen by "printer port"?

Hi! I don't have any serial over bluetooth device. I have been using Rpi3. The telescope connects through printer usb connector cable. I have attached a picture of it. This time I have connected a TPlink wifi adapter and the Meade LS8 in USB port. See the results:

bao@bao-desktop:~$ dmesg | tail -n 20
[ 497.560367] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 497.560380] usb 1-1.4: Product: 802.11n NIC
[ 497.560392] usb 1-1.4: Manufacturer: Realtek
[ 497.560404] usb 1-1.4: SerialNumber: 00E04C0001
[ 497.564610] Chip Version Info: CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[ 498.716633] r8188eu 1-1.4:1.0 wlxec086b11c324: renamed from wlan1
[ 498.781609] IPv6: ADDRCONF(NETDEV_UP): wlxec086b11c324: link is not ready
[ 499.289767] MAC Address = ec:08:6b:11:c3:24
[ 499.291374] IPv6: ADDRCONF(NETDEV_UP): wlxec086b11c324: link is not ready
[ 499.302350] R8188EU: ERROR indicate disassoc
[ 499.316207] IPv6: ADDRCONF(NETDEV_UP): wlxec086b11c324: link is not ready
[ 499.455753] IPv6: ADDRCONF(NETDEV_UP): wlxec086b11c324: link is not ready
[ 500.529539] usb 1-1.2: new high-speed USB device number 10 using dwc_otg
[ 500.630783] usb 1-1.2: New USB device found, idVendor=04cc, idProduct=0000
[ 500.630805] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 500.630818] usb 1-1.2: Product: Meade eFinder Serial Emulator
[ 500.630831] usb 1-1.2: Manufacturer: Meade
[ 500.630843] usb 1-1.2: SerialNumber: 1234567890
[ 500.632393] cdc_acm 1-1.2:1.0: Zero length descriptor references
[ 500.632426] cdc_acm: probe of 1-1.2:1.0 failed with error -22

From Meade download page they offer PL2302 driver, but then the 0x04CC vendor is ST-Ericsson and the Kernel cdc_acm driver does not recognize it. I think maybe the kernel needs to be patched to support this, but I'm not sure, I'll investigate later.

It seems that the serial interface is in fact a PL2303 but it's using Meade's own VID:PID and that is why it is not recognized.

There is some work done on this issue that involves recompiling the kernel/module with that VID:PID but it dates from 2014.
Maybe that should be addressed by now with a new kernel or patch?

Here's the reference I found:
www.cloudynights.com/topic/385710-piastr...page-16#entry5874359

If it is pl2302 it should work after inserting vendor/dev id into list for the pl2302 driver. I believe cdc_acm is a driver for usb modems - they usually have serial port. This is a different device and thus did not get recognized. You can try to make a following test:

1) Block the cdc_acm driver by putting "blacklist cdc_acm" ()no quotes in /etc/modprobe.d/acm_driver.conf (or some other .conf file there
2) dynamically adding a new id to the driver by
- load the candidate driver: modprobe pl2303
- check if there is new_id in /sys/bus/usb-serial/drivers/pl2303/
- as superuser: echo VID PID > /sys/bus/usb-serial/drivers/pl2303/new_id
- check the logs
3) Party
in your case VID PID will be: 04cc 0000
4) Let us know how it went

Hi! Thank you guys for helping me.

The commands didn't show any positive result. What I did:

1. Pluged in the usb cable. As root I put: blacklist cdc_acm in /etc/modprobe.d/acm_driver.conf and /etc/modprobe.d/blacklist.conf

2. In terminal: modprobe pl2303 (It shows no error message)

3. I found new_id file in the directory: /sys/bus/usb-serial/drivers/pl2303/new_id

4. In terminal: echo 04cc 0000 > /sys/bus/usb-serial/drivers/pl2303/new_id

5. I checked the VID and PID is written in the new_id file. (Things gone right!)

6. In terminal:
bao@bao-desktop:~$ lsusb
Bus 001 Device 005: ID 1c4f:0026 SiGma Micro Keyboard
Bus 001 Device 004: ID 09da:c10a A4Tech Co., Ltd.
Bus 001 Device 007: ID 04cc:0000 ST-Ericsson
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

7. Terminal:
bao@bao-desktop:~$ dmesg | tail -n 20
[ 728.051600] pl2303 ttyUSB0: pl2303_set_line_request - failed: -71
[ 728.051771] pl2303 ttyUSB0: pl2303_set_control_lines - failed: -71
[ 728.051941] pl2303 1-1.2:1.0: pl2303_vendor_write - failed to write [0000]: -71
[ 737.999606] pl2303 ttyUSB0: pl2303_get_line_request - failed: -71
[ 737.999843] pl2303 ttyUSB0: pl2303_set_line_request - failed: -71
[ 738.000016] pl2303 1-1.2:1.0: pl2303_vendor_write - failed to write [0000]: -71
[ 738.253778] pl2303 ttyUSB0: pl2303_set_control_lines - failed: -71
[ 738.253928] pl2303 ttyUSB0: error sending break = -71
[ 738.255226] pl2303 ttyUSB0: pl2303_get_line_request - failed: -71
[ 738.255333] pl2303 ttyUSB0: pl2303_set_line_request - failed: -71
[ 738.255433] pl2303 1-1.2:1.0: pl2303_vendor_write - failed to write [0000]: -71
[ 738.255635] pl2303 ttyUSB0: pl2303_set_control_lines - failed: -71
[ 738.256272] pl2303 ttyUSB0: pl2303_get_line_request - failed: -71
[ 738.257479] pl2303 ttyUSB0: pl2303_set_line_request - failed: -71
[ 738.257665] pl2303 1-1.2:1.0: pl2303_vendor_write - failed to write [0000]: -71
[ 744.999874] pl2303 ttyUSB0: pl2303_get_line_request - failed: -71
[ 745.000100] pl2303 ttyUSB0: pl2303_set_line_request - failed: -71
[ 745.000285] pl2303 1-1.2:1.0: pl2303_vendor_write - failed to write [0000]: -71
[ 745.253391] pl2303 ttyUSB0: pl2303_set_control_lines - failed: -71
[ 745.253552] pl2303 ttyUSB0: error sending break = -71

8. What is the wrong!?
9. Plugged out and plugged in the cable. no result!

That means procedure worked but the device is probably not a pl2303 based serial link - the pl2303 driver is unable to talk to the device.
It is probably not pl2303. Send us the output of lsmod - maybe some other part of ericsson driver is interfering with the communication.
I have only one more idea to try: instal meade driver under windows let it connect to the scope and check with device manager if the
device is still 04cc:0000. The modem chipsets are notorious for having "dual personality" feature - you need to send particular
initialisation sequence to the device to make it switch to the serial adapter mode. It effectively reboots the chipset and brings up other personality of the device. There is a special tool to make these devices switch - usb_modeswitch (and it has a 04cc:225c device in the database - you can add your own devices to the config). That is all I have right now. BTW other people have problems with this - I have found some reports on cloudynights.