hi!
worth a try as well - but the dmesg log pep posted clearly states that the adapter connects to ttyUSB0 ...
yours wolfi

Hi Wolfi,

The results is:

astroberry@astroberry:~ $ lsusb -v -d 10c4:ea60

Bus 001 Device 003: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109 UART Bridge Controller [CP210x family]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x10c4 Cygnal Integrated Products, Inc.
idProduct 0xea60 CP2102/CP2109 UART Bridge Controller [CP210x family]
bcdDevice 1.00
iManufacturer 1 Silicon Labs
iProduct 2 CP2102 USB to UART Bridge Controller
iSerial 3 0001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0020
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 2 CP2102 USB to UART Bridge Controller
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)

Thanks,
Pep

Hi Arado,

How I can do it?

Thanks,
Pep

hi!
USB devices can also be set in the dev rules, i think ... but i have a more important question: why are you running on USB 1.1????

it should work, i am just wondering.
yours wolfi

Hi Wolfi,

Well, I don't know where should it be connected? And how do I set up the rule file correctly? (I have tried everything and I do not succeed)
I show you my 99-observatory.rules files

#OnStep per reconeixer port OnStep

SUBSYSTEMS=="usb", ACTION=="add", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", MODE="0666", SYMLINK+="O$
#SUBSYSTEMS=="usb-serial", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", MODE="0666", SYMLINK+="OnStep"

#SUBSYSTEMS=="usb-serial", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", MODE="0666", SYMLINK+="OnStep"
#SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", MODE="0666"
#SUBSYSTEMS=="tty", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", MODE="0666"

#OnFocus per reconeixer port OnFocus
#SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0000:01:00.0", MODE="0666", SYMLINK+="OnFocus"
#SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0000:01:00.0", MODE="0666"
#SUBSYSTEMS=="usb", ACTION=="add", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0000:01:00.0", MODE="0666", SY$

I tried a lot of things and I do not runs never.
Is it possible to change the USB1.1?
Thanks for your time,

Pep

hi!
i checked the doc - USB 1.1 seems to be the response from this converter, which is apparently an older model.
as far as i can tell, all is fine with your converter. so it is either a hardware failure (scarce) or a software problem ...

i am running out of suggestions, maybe someone with a better understanding of udev rules might be able to help.
... i still see the focuser as a separate device here - which is suspicious.

one idea:
- move the udev rules file to a different location so that they are not executed at startup
- reboot
- now, you cannot access /dev/ttyUSB0 UNLESS you are root OR - i hope that works - you give everyone else access to the device by typing

sudo chmod a+rw /dev/ttyUSB0

in the terminal. start kstars in the same terminal. if this works (unless i typed some BS, which is always possible), then the udev rules are the problem. this is not a remedy, by the way. next time you reboot, access is gone again ...

yours wolfi

Hi Wolfi,

Thank you so much.
I'll try it tonight (within 13 hours or so, now I'm working ... ).
I hope it works and clarifies the topic, or better: Fix it.
If not, I suppose I will have to reload astroberry 2.0 from a new image and wait works and/or reprogram the STM32.
At the beginings, the focus should be fine and the indi-LX200_OnStep takes control of the mount and focus, but it is true that maybe it is misconfigured and I need to start like an indi-driver in part for focus....
..... Wow this I haven't tried it !!!: I also start the focus with INDI-OnFocus and, then, maybe one thing works for me and not the other? ... One more thing to try !!! )
Still thank you very much ....
I'll tell you .... (I need to solve early because if not my wife kill me )

Pep

Hello,

Now that I have my rig up, I can describe my configuration. I researched udevadm requirements. From there, I decided that all Ill-behaving devices would have their own rules. I have two, a USB DYI GPS and an AstroEQ. I created two rules in /lib/useful/rules.d.

First, udevadm requirements state, KERNEL== is required to enumerate a new instance of a device.

Ex. KERNEL==“ttyACM*” ,SUBSYSTEM== “tty”

This says increment the next asynchronous communication management device is needed under subsystem tty. This addition and rules management style allowed me to manage both devices and give them the desired resources.

I only have two such devices. Only 4 ports exist on every RPI. Other device type may have more.

Also, I took the information after the RUN== and ran the string under sudo to see if any syntax errors or other errors were present. Syntax errors are common.

Hi Arado and wolfi,

First, I tried the focus an mount driver and not works. Many trys but only works on a PC (Ubuntu mate, like a local)
Arado, I'll try it this evening. Is to say: remove all the rules on rules. d directory. And create a new one but this time with the suggestions that you did it. On this new rule file I add a kernel, subsystem, (by USB or tty?) and then... What more? Similar like I posted some interventions before?
Thanks for your help.
Pep

Hello,

I am puzzled why deleting all rules is required. The next update will replace the missing, maybe. This why I create specific rules for specific hardware.

Other drivers might be necessary. Be sure to check your device list before deleting everything.

Let us know whether it was the GPS deamon

Hello

I do believe ttyUSB0 = ttyS0 which is the console terminal. This is why ttyACM is the better choice.