×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

ttyUSB0 issues on OnStepp and RasPi4

  • Posts: 84
  • Thank you received: 0
Hi to everyone,

Today I'll try it to "Kill" the gpsd from the ttyUSB0 and I'm sure that will work my little (But biggest) OnStep .

But last night I check if I had the cp210x drivers was installed (By modprobe cp210x) and seems that no are. Someone could help to me to install or re-install the drivers?

About the issue that I have, astroberry 1 or astroberry 2 are similars? It's mean, if I should install astroberry 1 I succed something diferent from astroberry2?

Thanks a lot,

Pep
4 years 2 months ago #48658

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

  • Posts: 84
  • Thank you received: 0
Hello guys,

<em><strong>WORKS!!!! </strong></em>



Thanks to everyone who helped me and supported me at all times: wolfi, Hy, Adaro, wbirk, aj55, ...:cheer: ... even when at some point I was tempted by the dark side ...:blink: :evil: :woohoo:
At the end it have been the "gpsd" .... ... the gpsd nightmare ...:evil: :sick: :silly:

Thanks again, all of you who helped me and I hope, this forum-topic, helps people who have a problem like this.
Curious that this is not fixed this issue on astroberry2, I suppose in the next version of astroberry they will already sock it.

By the way, with this I can update without any problems when needed, right?

Thanks again to all !!!!
Today I will sleep peacefully.:) ;)

Deeply thanks,

Pep

I change the topic for [SOLVED]?
Last edit: 4 years 2 months ago by Pep.
4 years 2 months ago #48664
Attachments:

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

  • Posts: 389
  • Thank you received: 15
Hello,

Please send me your rules for these two devices.

LX200 OneStep.
GPSD

Also send me your lsusb dump.

Thank you.
Last edit: 4 years 2 months ago by John Robison.
4 years 2 months ago #48666

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

  • Posts: 84
  • Thank you received: 0
Hy Arado,

The OnStep rule is:

KERNEL=="ttyUSB*", SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", MODE="0666", SYMLINK+="OnStep"

About GPSD rule I don't touch nothing I only do it that Aj55 suggest it about to not use from boot moment.
If you want I send it but is to large... (but I don't touch nothing inside).
Thanks,
Pep
PD:
Sorry... I look inside of the gpsd rule and I find my device: (I hope that was you ask me)

# Garmin International GPSmap, various models (tested with Garmin GPS 18 USB) [linux module: garmin_gps]
ATTRS{idVendor}=="091e", ATTRS{idProduct}=="0003", SYMLINK+="gps%n", TAG+="systemd", ENV{SYSTEMD_WANTS}="gpsdctl@%k.service"
# Cygnal Integrated Products, Inc. CP210x Composite Device (Used by Holux m241 and Wintec grays2 wbt-201) [linux module: cp210x]
ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", SYMLINK+="gps%n", TAG+="systemd", ENV{SYSTEMD_WANTS}="gpsdctl@%k.service"

# Cygnal Integrated Products, Inc. [linux module: cp210x]
ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea71", SYMLINK+="gps%n", TAG+="systemd", ENV{SYSTEMD_WANTS}="gpsdctl@%k.service"
Last edit: 4 years 2 months ago by Pep.
4 years 2 months ago #48667

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

  • Posts: 389
  • Thank you received: 15


Let's start with creating a 76-LX200.rules

In this document, place this string. No spaces between comments

KERNEL=="ttyUSB*",SUBSYSTEMS=="usb", ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0666", SYMLINK+="OnStep"

The second step is create a 76-GARMIN.rules. Add these strings. The "#" symbol is a comment field.

# Garmin International GPSmap, various models (tested with Garmin GPS 18 USB) [linux module: garmin_gps]

KERNEL=="ttyUSB*", SUBSYSTEMS=="usb", ATTRS{idVendor}=="091e", ATTRS{idProduct}=="0003", SYMLINK+="gps%n", TAG+="systemd", ENV{SYSTEMD_WANTS}="gpsdctl@%k.service"

# Cygnal Integrated Products, Inc. CP210x Composite Device (Used by Holux m241 and Wintec grays2 wbt-201) [linux module: cp210x]

KERNEL=="ttyUSB*", SUBSYSTEMS=="usb",ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", SYMLINK+="gps%n", TAG+="systemd", ENV{SYSTEMD_WANTS}="gpsdctl@%k.service"

# Cygnal Integrated Products, Inc. [linux module: cp210x]

KERNEL=="ttyUSB*", SUBSYSTEMS=="usb",ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea71", SYMLINK+="gps%n", TAG+="systemd", ENV{SYSTEMD_WANTS}="gpsdctl@%k.service"[/quote]

Reboot the system. See if there are two ttyUSB ports. If not, use dmesg udevadmn and post the results.
4 years 2 months ago #48668

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

  • Posts: 84
  • Thank you received: 0
Hi,
I just do it all the tries that you suggest it and not there are another ttyUSB*. Only this:
crw-rw-rw- 1 root plugdev 188, 0 de gen. 29 23:17 /dev/ttyUSB0

About dmesg udevadmn I don't know how to do it.
But I do it this:
...$ sudo dmesg | grep ttyUSB*
[ 4.307911] usb 1-1.4: cp210x converter now attached to ttyUSB0


I come back on same conditions for not to break nothing, now the tool works...
I hope give you enough information.

Thanks for all,
Pep
Last edit: 4 years 2 months ago by Pep.
4 years 2 months ago #48689

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

  • Posts: 389
  • Thank you received: 15
Hello,

If I am reading this right, two new rules as I described were created. Upon reboot, a check for ttyUSB variations was attempt. The result was ttyUSB0.

I can confirm the same results. Please replace all ttyUSB with ttyACM. Resave the both files. Look in /lib/udev/rules.d for the gps rules. Also, check /etc/udev/rules.d for gps rules. Rename any current files calling out the Garmin. Then reboot.
4 years 2 months ago #48695

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

  • Posts: 84
  • Thank you received: 0
Hi Arado,

Yes, I followed (and copy and paste) all the things that you would to check.

If I understand right, I do the same (only in both 76-* files) but this time change ttyUSB0 for ttyAMC, save and reboot and then check if appear some other ttyAMC device, doesn't it?
And, before to reboot change, too. Into the GPS.rules (or only garmin. rules?), change gps for garmin?
This evening I'll check it.

For future issues of others users about same problem, I need to do something because the people goes directly to the solution post?

Yours,
Pep
4 years 2 months ago #48709

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

  • Posts: 151
  • Thank you received: 27

hi!
let me guess. you get an error stating that exposure was started 3 times and cannot be finished?

this is a problem i know from the 120 MM. there is a workaround.
- use a USB 2 cable, NOT a USB 3 cable
- try the first exposure with 0.01 s exposure time. after that, you can do longer exposures.
- you can also try to set the camera to 8 bit depth.

maybe that helps ...
yours wolfi
4 years 2 months ago #48719

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

  • Posts: 389
  • Thank you received: 15


Hello,

Please be sure to use ttyACM. No such device exists for ttyAMC.

Yes. Only rename GPS files with Garmin in them. Other GPS files are for the different GPS services INDI can provide.

This should be only one file in one location. Buster is a stickler about where rules are located. Sometimes, applications place rules in other OS distribution locations. /etc/udev is legacy.
Last edit: 4 years 2 months ago by John Robison.
4 years 2 months ago #48722

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

  • Posts: 84
  • Thank you received: 0

Replied by Pep on topic ttyUSB0 issues on OnStepp and

Hi Arado,

There are 60-gpsd.rule I supose that is the indi services that you toll before and definet like "tty".

Then afer to do the changes that you propose the results are (on GARMIN.rule file):

astroberry@astroberry:~ $ sudo dmesg | grep ttyUSB*
[sudo] contrasenya per a astroberry:
[ 4.488520] usb 1-1.4: cp210x converter now attached to ttyUSB0
astroberry@astroberry:~ $ sudo dmesg | grep ttyAMC*
[ 0.477197] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 34, base_baud = 0) is a PL011 rev2
astroberry@astroberry:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109 UART Bridge Controller [CP210x family]
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
astroberry@astroberry:~ $

This is all.
Thanks,
Pep
4 years 2 months ago #48731

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

  • Posts: 389
  • Thank you received: 15
Hello,

Please use ttyACM. I keep reading the use of ttyAMC. The use of ttyAMC will yield nothing as demonstrated. Please use

ttyACM

ACM = Asynchronous Communication Manager = ACM
4 years 2 months ago #48736

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

Moderators: Radek Kaczorek
Time to create page: 0.906 seconds