×

INDI Library v1.9.8 Released (Yesterday)

Bi-monthly INDI Library released with new drivers and bug fixes.

Esatto on new ubuntu linux

  • Posts: 100
  • Thank you received: 8
I have been using an Esatto focuser successfully on stellarmate for quite sometime. I am migrating to ekos/kstars on a new mele mini pc running ubuntu 22.04 and am having trouble sorting out port/connection. It shows up if i lsusb:

Bus 001 Device 005: ID 10c4:ea60 Silicon Labs CP210x UART Bridge

and that comes and goes as I unplug the cable. If I ls /dev/serial/by-id all I see is:

usb-Pegasus_Astro_PPBADV_revB_PPBA5UXVM0-if00-port0

nothing for the esatto. The Pegasus astro does connect although it sometimes seems to think another device is using the port?
Borg 107FL on RST-135 + QHY268C, Astro-Tech AT130EDT on GM1000HPS + QHY600PH Chroma LRGBHSO; IR Guiding WO Uniguide 50 & QHY5-III-462C ASUS PN51 and Mele Quieter 3 ubuntu, kstars/ekos, & firecapture; Pegasus PPBA; WO Redcat, Skyguider Pro RT90C, Canon 7DmkII, rPi4/stellarmate
Last edit: 2 months 4 days ago by Thomas Mason.
2 months 5 days ago #84637

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

  • Posts: 154
  • Thank you received: 22
Try removing GPSD

apt remove gpsd

and reboot

See if that helps.
Last edit: 2 months 4 days ago by Sonny Cavazos.
2 months 4 days ago #84639

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

  • Posts: 100
  • Thank you received: 8
gpsd not installed so nothing removed
Borg 107FL on RST-135 + QHY268C, Astro-Tech AT130EDT on GM1000HPS + QHY600PH Chroma LRGBHSO; IR Guiding WO Uniguide 50 & QHY5-III-462C ASUS PN51 and Mele Quieter 3 ubuntu, kstars/ekos, & firecapture; Pegasus PPBA; WO Redcat, Skyguider Pro RT90C, Canon 7DmkII, rPi4/stellarmate
2 months 4 days ago #84649

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

  • Posts: 257
  • Thank you received: 54
Some time ago there was a /lib/udev/rules.d/99-vantage.rules rule that created a /dev/vantage link to a device that conflicted with my Esatto and gave me a similar message to the one you get (another device was grabbing the port). The rule has been removed since then (latest builds), but you may check if you see a /dev/vantage device or any other device that you do not have in your system. "ls -l /dev | grep USB" should show you all USB devices, real and linked. If this is the case, I suggest you delete the /lib/udev/rules.d/99-vantage.rules file, reboot, and see if the problem goes away.

Since getting rid of the 99-vantage.rules file, I do not have conflicts anymore, rules seem to behave correctly. BTW, I have an Esatto and a Pegasus PPBA, among other devices.
2 months 4 days ago #84651

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

  • Posts: 100
  • Thank you received: 8
Nothing here that looks like that:

thomas@mele:~$ ls -l /dev | grep USB
crw-rw-rw- 1 root dialout 188, 0 Jul 24 21:33 ttyUSB0
thomas@mele:~$ ls -l /dev/vantage
ls: cannot access '/dev/vantage': No such file or directory
Borg 107FL on RST-135 + QHY268C, Astro-Tech AT130EDT on GM1000HPS + QHY600PH Chroma LRGBHSO; IR Guiding WO Uniguide 50 & QHY5-III-462C ASUS PN51 and Mele Quieter 3 ubuntu, kstars/ekos, & firecapture; Pegasus PPBA; WO Redcat, Skyguider Pro RT90C, Canon 7DmkII, rPi4/stellarmate
2 months 4 days ago #84661

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

  • Posts: 257
  • Thank you received: 54
Sorry it did not help. Power to the Esatto is OK I guess?!

Would your Esatto be connected to the USB port of the PPBA that can provide high power, the one that can be used to power a Raspberry Pi? I think it's the lower left one on the PPBA. I could never get USB devices to work out of that port even though Pegasus says that it can be used to that purpose. If the Esatto is connected there, try connecting it to another USB port; if not, I'm sorry to be out of suggestions.
2 months 4 days ago #84662

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

  • Posts: 100
  • Thank you received: 8
I have a 12V power connected since I found USB alone was not sufficient. I also tried direct connection to mini pc without going through pegasus. It looks like the kernel isn't recognizing it and setting up a /dev/ even through it enumerates properly as CP210x and the kernel mod is present?

thomas@mele:~$ lsusb -d 10c4:ea60 -v

Bus 001 Device 009: ID 10c4:ea60 Silicon Labs CP210x UART Bridge
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x10c4 Silicon Labs
idProduct 0xea60 CP210x UART Bridge
bcdDevice 1.00
iManufacturer 1 Silicon Labs
iProduct 2 CP2102N USB to UART Bridge Controller
iSerial 3 286da66d47a6e9118cc0dda44458cd37
bNumConfigurations 1
...
Device Status: 0x0000
(Bus Powered)
thomas@mele:~$
thomas@mele:~$ modinfo cp210x
filename: /lib/modules/5.15.0-41-generic/kernel/drivers/usb/serial/cp210x.ko
license: GPL v2
description: Silicon Labs CP210x RS232 serial adaptor driver
srcversion: CBE34CC45167BD29F312F4D
alias: usb:v413Cp9500d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v3923p7A0Bd*dc*dsc*dp*ic*isc*ip*in*
...
alias: usb:v10C4pEA60d*dc*dsc*dp*ic*isc*ip*in*
...
alias: usb:v045Bp0053d*dc*dsc*dp*ic*isc*ip*in*
alias: usb:v0404p034Cd*dc*dsc*dp*ic*isc*ip*in*
depends: usbserial
retpoline: Y
intree: Y
name: cp210x
vermagic: 5.15.0-41-generic SMP mod_unload modversions
sig_id: PKCS#7
signer: Build time autogenerated kernel key
sig_key: 1F:4E:23:82:4E:7F:DB:01:30:C1:63:2D:9B:09:11:2C:89:6D:22:1F
sig_hashalgo: sha512
signature: A3:70:1B:BA:0A:F3:A6:B4:69:C7:CD:01:40:69:F6:5E:98:10:AD:F6:
...
Borg 107FL on RST-135 + QHY268C, Astro-Tech AT130EDT on GM1000HPS + QHY600PH Chroma LRGBHSO; IR Guiding WO Uniguide 50 & QHY5-III-462C ASUS PN51 and Mele Quieter 3 ubuntu, kstars/ekos, & firecapture; Pegasus PPBA; WO Redcat, Skyguider Pro RT90C, Canon 7DmkII, rPi4/stellarmate
Last edit: 2 months 4 days ago by Thomas Mason.
2 months 4 days ago #84663

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

  • Posts: 100
  • Thank you received: 8
Here is what I get in the boot log:

Jul 24 21:26:03 mele kernel: usb 1-1.4: new full-speed USB device number 6 using xhci_hcd
Jul 24 21:26:03 mele kernel: mc: Linux media interface: v0.10
Jul 24 21:26:03 mele kernel: videodev: Linux video capture interface: v2.00
Jul 24 21:26:03 mele systemd-udevd[341]: Using default interface naming scheme 'v249'.
Jul 24 21:26:03 mele kernel: usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
Jul 24 21:26:03 mele kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 21:26:03 mele kernel: usb 1-1.4: Product: CP2102N USB to UART Bridge Controller
Jul 24 21:26:03 mele kernel: usb 1-1.4: Manufacturer: Silicon Labs
Jul 24 21:26:03 mele kernel: usb 1-1.4: SerialNumber: 286da66d47a6e9118cc0dda44458cd37
Jul 24 21:26:03 mele kernel: mei_me 0000:00:16.0: enabling device (0000 -> 0002)
Jul 24 21:26:03 mele mtp-probe[362]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1"
Jul 24 21:26:03 mele mtp-probe[362]: bus: 1, device: 4 was not an MTP device
Jul 24 21:26:03 mele kernel: usbcore: registered new interface driver usbserial_generic
Jul 24 21:26:03 mele kernel: usbserial: USB Serial support registered for generic
Jul 24 21:26:04 mele mtp-probe[405]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1.1"
Jul 24 21:26:04 mele mtp-probe[405]: bus: 1, device: 4 was not an MTP device
Jul 24 21:26:04 mele kernel: usbcore: registered new interface driver cp210x
Jul 24 21:26:04 mele kernel: usbserial: USB Serial support registered for cp210x
Jul 24 21:26:04 mele kernel: cp210x 1-1.4:1.0: cp210x converter detected
Jul 24 21:26:04 mele kernel: usb 1-1.4: cp210x converter now attached to ttyUSB1
Jul 24 21:26:05 mele brltty[532]: USB configuration set error 16: Device or resource busy
Jul 24 21:26:05 mele brltty[532]: brltty: USB configuration set error 16: Device or resource busy
Jul 24 21:26:05 mele brltty[532]: USB interface in use: 0 (cp210x)
Jul 24 21:26:05 mele brltty[532]: brltty: USB interface in use: 0 (cp210x)
Jul 24 21:26:05 mele kernel: usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
Jul 24 21:26:05 mele kernel: fbcon: i915drmfb (fb0) is primary device
Jul 24 21:26:05 mele kernel: cp210x ttyUSB1: cp210x converter now disconnected from ttyUSB1
Jul 24 21:26:05 mele kernel: cp210x 1-1.4:1.0: device disconnected
Jul 24 21:26:05 mele brltty[532]: USB control transfer error 32: Broken pipe
Jul 24 21:26:05 mele brltty[532]: brltty: USB control transfer error 32: Broken pipe
Jul 24 21:26:05 mele brltty[532]: unexpected CP2101 baud divisor size: 0
Jul 24 21:26:05 mele brltty[532]: brltty: unexpected CP2101 baud divisor size: 0
Jul 24 21:26:05 mele brltty[532]: USB control transfer error 32: Broken pipe
Jul 24 21:26:05 mele brltty[532]: brltty: USB control transfer error 32: Broken pipe
Jul 24 21:26:05 mele brltty[532]: brltty: unable to set CP2101 baud divisor: Broken pipe
Jul 24 21:26:05 mele brltty[532]: unable to set CP2101 baud divisor: Broken pipe
Jul 24 21:26:05 mele systemd-logind[625]: Watching system buttons on /dev/input/event6 (BRLTTY 6.4 Linux Screen Driver Ke>
Jul 24 21:26:05 mele ModemManager[683]: <info> [base-manager] port ttyUSB1 released by device '/sys/devices/pci0000:00/0>
Jul 24 21:26:05 mele ModemManager[683]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00>

so it looks like it sets up /dev/ttyUSB1 but then runs into trouble - I don't see the device when I log in.
Borg 107FL on RST-135 + QHY268C, Astro-Tech AT130EDT on GM1000HPS + QHY600PH Chroma LRGBHSO; IR Guiding WO Uniguide 50 & QHY5-III-462C ASUS PN51 and Mele Quieter 3 ubuntu, kstars/ekos, & firecapture; Pegasus PPBA; WO Redcat, Skyguider Pro RT90C, Canon 7DmkII, rPi4/stellarmate
Last edit: 2 months 4 days ago by Thomas Mason.
2 months 4 days ago #84665

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

  • Posts: 100
  • Thank you received: 8
The boot log was the key. I removed brltty (which is braille display) and /dev/ttyUSB1 now became visible and connects me to the esatto.

This was probably similar to the cases observed by others where gpsd and vantage were conflicting. Thanks for the suggestions, it gave me ideas to narrow things down.

By the way the problem with the first USB port on PPBA is that it is USB3 only, won’t work with USB2 or USB3 devices that start on USB2 then switch to USB3 (like ZWO and QHY cameras). The new V2 PPBA fixes this.
Borg 107FL on RST-135 + QHY268C, Astro-Tech AT130EDT on GM1000HPS + QHY600PH Chroma LRGBHSO; IR Guiding WO Uniguide 50 & QHY5-III-462C ASUS PN51 and Mele Quieter 3 ubuntu, kstars/ekos, & firecapture; Pegasus PPBA; WO Redcat, Skyguider Pro RT90C, Canon 7DmkII, rPi4/stellarmate
The following user(s) said Thank You: Gilles Gagnon
Last edit: 2 months 4 days ago by Thomas Mason.
2 months 4 days ago #84666

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

Time to create page: 0.468 seconds