×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

ttyUSB0 issues on OnStepp and RasPi4

  • 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 1 month ago #48736

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,

Firstly, I'm so sorry I'm a little bit dislexic.
I copy the results after to change ttyUSB* for ttyACM* and after reboot:

Hi Arado,

Firstly, I'm so sorry I'm a little bit dyslexic.
I copy the results after to change ttyUSB* for ttyACM* and after reboot:

<em>astroberry@astroberry:~ $ sudo dmesg | grep ttyACM*
astroberry@astroberry:~ $ ls /dev
argon-h264mem fuse loop5 port ram7 stdout tty22 tty38 tty53 ttyS0 vcs7 vcsu6
argon-hevcmem gpiochip0 loop6 ppp ram8 tty tty23 tty39 tty54 ttyUSB0 vcsa vcsu7
argon-intcmem gpiochip1 loop7 ptmx ram9 tty0 tty24 tty4 tty55 uhid vcsa1 vga_arbiter
argon-vp9mem gpiochip2 loop-control pts random tty1 tty25 tty40 tty56 uinput vcsa2 vhci
autofs gpiomem mapper ram0 raw tty10 tty26 tty41 tty57 urandom vcsa3 video10
block gps0 media0 ram1 rfkill tty11 tty27 tty42 tty58 v4l vcsa4 video11
btrfs-control hwrng mem ram10 rpivid-h264mem tty12 tty28 tty43 tty59 vantage vcsa5 video12
bus i2c-1 memory_bandwidth ram11 rpivid-hevcmem tty13 tty29 tty44 tty6 vchiq vcsa6 watchdog
cachefiles initctl mmcblk0 ram12 rpivid-intcmem tty14 tty3 tty45 tty60 vcio vcsa7 watchdog0
char input mmcblk0p1 ram13 rpivid-vp9mem tty15 tty30 tty46 tty61 vc-mem vcsm zero
console kmsg mmcblk0p2 ram14 serial tty16 tty31 tty47 tty62 vcs vcsm-cma zram0
cpu_dma_latency log mqueue ram15 shm tty17 tty32 tty48 tty63 vcs1 vcsu zram1
cuse loop0 net ram2 snd tty18 tty33 tty49 tty7 vcs2 vcsu1 zram2
disk loop1 network_latency ram3 spidev0.0 tty19 tty34 tty5 tty8 vcs3 vcsu2 zram3
fb0 loop2 network_throughput ram4 spidev0.1 tty2 tty35 tty50 tty9 vcs4 vcsu3
fd loop3 null ram5 stderr tty20 tty36 tty51 ttyAMA0 vcs5 vcsu4
full loop4 OnStep ram6 stdin tty21 tty37 tty52 ttyprintk vcs6 vcsu5
astroberry@astroberry:~ $

Thanks for all. and I hope to help to you a little bit.
Best,
Pep
Last edit: 4 years 1 month ago by Pep.
4 years 1 month ago #48739

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

  • Posts: 84
  • Thank you received: 0
I post the solution step for not forget it:

After some talk with Jasem :
"I'm starting to suspect that something else is interfering with it. Maybe the <em>GPS daemon</em>? in dmesg it was shown pps0
Try to disable gpsd:
<strong>sudo systemctl stop gpsd</strong> gpsd.socket"

...
But the problem returned so the final solution:
Now totally disabled the gpsd deamon. <strong>Edited the /etc/default/gpsd script and made</strong>:

START_DEAMON="false"
USBAUTO="false"<strong></strong>
and also put #<strong></strong> in front of the rest...

And Now works perfectly.

For my hand is <em><strong>SOLVED!!!</strong></em> ;-)
Thanks to all,
Pep
Last edit: 4 years 1 month ago by Pep.
4 years 1 month ago #48740

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

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

If my scope is in a fixed position, disabling gps makes sense. For me, I need my GPS for I am mobile. However, the Garmin device must remain unplugged to the mount and the RPI4. Disabling GPSD does not stop a plugged device from loading.

Run this command

Dmesg | grep “udevadm”

Please share the results.
4 years 1 month ago #48749

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

  • Posts: 73
  • Thank you received: 11
Hi Pep,

Nice to see the solution workes!
In all honesty I think it shouldn't be necessary to know so much about Linux to solve these things.....
As for my coordinates I simply look on my phone ;-))

Cheers, Arnold
4 years 1 month ago #48770

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

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

Yes. The solution to disable GPS applets in INDI is one solution. I used my phone also. The issue I had was time. KSTARS has a method of guessing time when not connected to a network. KSTARS guesses were not helpful. KSTARS is dependent on some time keeper.

I use my GPS to give the longitudinal and latitudinal time to KSTARS. This makes KSTARS relative to my position.

I agree that having to know Linux is a big ask. AstroBerry makes it easier. The trouble is technology. Vendor devices follow standards to their liking. The Raspbian OS approach to hardware management is different from Ubuntu Mate. No, INDI is not responsible for every vendor’s hardware. Vendors are. If a vendor’s driver is behaving rudely, knowing how to manage rude vendors is key. You contain them as I described.

I need to see what if any syntax errors were introduced during Pep’s attempts. I understand dyslexia. I know people who struggle with it. The potential was identified in this thread.
4 years 1 month ago #48782

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

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

I propouse an idea, you review if there are any mistake and then you send me (or paste all the paremeters, places where do it,... ) that you want I check .
And all the steps (comands and options )to execute and I give you the results. I removed all the test that you propouse it.
And, I undertand now, why the kstars needs the gps system...
Really all of you are genius .
Thanks again
Pep
Pd: I hope this weekend I hope to debuted on control remotely my telescope and take photos and guide....
4 years 1 month ago #48787

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

  • Posts: 389
  • Thank you received: 15

Hello,

I would be happy to look. I have AstroBerry 2.0.0 running now. For AB 2.0.0, I installed the application System Log. This allowed me to get to udevadm easier. Dmesg sometimes doesn’t see udevadm. Instead, we will use the command, journalctl.

With everything plugged in, open a terminal. Type this within the quotes, “journalctl -g udevadm”. This command will display any syntax errors within the drive rules load process. This will be the basis line.
Last edit: 4 years 1 month ago by John Robison.
4 years 1 month ago #48789

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

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

Frist of all, sorry for my delay... I had to much thing open on my main.
About your check. I attach the results...
first I so a journalctl and I stoped because I dont know when it was possible to stop it. and the I did journalctl -g udevadm (you shuld show it next):

de febr. 04 00:17:01 astroberry kernel: EXT4-fs (mmcblk0p2): write access will be enabled during recovery
de febr. 04 00:17:01 astroberry kernel: usb 1-1: new high-speed USB device number 2 using xhci_hcd
de febr. 04 00:17:01 astroberry kernel: usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
de febr. 04 00:17:01 astroberry kernel: usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
de febr. 04 00:17:01 astroberry kernel: usb 1-1: Product: USB2.0 Hub
de febr. 04 00:17:01 astroberry kernel: hub 1-1:1.0: USB hub found
de febr. 04 00:17:01 astroberry kernel: hub 1-1:1.0: 4 ports detected
de febr. 04 00:17:01 astroberry kernel: usb 1-1.1: new high-speed USB device number 3 using xhci_hcd
de febr. 04 00:17:01 astroberry kernel: EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs
de febr. 04 00:17:01 astroberry kernel: EXT4-fs (mmcblk0p2): 1 orphan inode deleted
de febr. 04 00:17:01 astroberry kernel: EXT4-fs (mmcblk0p2): recovery complete
de febr. 04 00:17:01 astroberry kernel: EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
de febr. 04 00:17:01 astroberry kernel: VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
de febr. 04 00:17:01 astroberry kernel: devtmpfs: mounted
de febr. 04 00:17:01 astroberry kernel: Freeing unused kernel memory: 2048K
de febr. 04 00:17:01 astroberry kernel: Run /sbin/init as init process
de febr. 04 00:17:01 astroberry kernel: usb 1-1.1: New USB device found, idVendor=046d, idProduct=0808, bcdDevice= 0.09
de febr. 04 00:17:01 astroberry kernel: usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=2
de febr. 04 00:17:01 astroberry kernel: usb 1-1.1: SerialNumber: 44867560
de febr. 04 00:17:01 astroberry kernel: usb 1-1.4: new full-speed USB device number 4 using xhci_hcd
de febr. 04 00:17:01 astroberry systemd[1]: System time before build time, advancing clock.
de febr. 04 00:17:01 astroberry kernel: usb 1-1.4: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00
de febr. 04 00:17:01 astroberry kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
de febr. 04 00:17:01 astroberry kernel: usb 1-1.4: Product: CP2102 USB to UART Bridge Controller
de febr. 04 00:17:01 astroberry kernel: usb 1-1.4: Manufacturer: Silicon Labs
de febr. 04 00:17:01 astroberry kernel: usb 1-1.4: SerialNumber: 0001
de febr. 04 00:17:01 astroberry kernel: NET: Registered protocol family 10
de febr. 04 00:17:01 astroberry kernel: Segment Routing with IPv6
de febr. 04 00:17:01 astroberry systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +
de febr. 04 00:17:01 astroberry systemd[1]: Detected architecture arm.
de febr. 04 00:17:01 astroberry systemd[1]: Set hostname to <astroberry>.
de febr. 04 00:17:01 astroberry systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
de febr. 04 00:17:01 astroberry systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directo
de febr. 04 00:17:01 astroberry systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directo
de febr. 04 00:17:01 astroberry kernel: random: systemd: uninitialized urandom read (16 bytes read)
de febr. 04 00:17:01 astroberry kernel: random: systemd: uninitialized urandom read (16 bytes read)

astroberry@astroberry:~ $ journalctl -g udevadm
Compiled without pattern matching support
astroberry@astroberry:~ $


I hope that this help you for understand what happen.
Thanks a lot for all,
Pep
4 years 1 month ago #49118

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

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

I concur. journalctl does not supply the desired impact of rules being applied. Try xgps.
4 years 1 month ago #49129

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

  • Posts: 9
  • Thank you received: 1


JEEEEEZZ thank youuuu!!!!

This solved my problem with my QHYCFW2 in standalone mode!

It uses the CP210x chipset too, and it wasn't working on the PI4 (but on PI3 B+ was).

Disabled the GPSD stuff and now it is working, ahhaha, it is wonderful!
The following user(s) said Thank You: Milan Kučera
4 years 3 days ago #51161

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

  • Posts: 5
  • Thank you received: 2
Hi,
the same here with a QHY CFW3, and the same CP210x chipset, disabled GPS, and also I needed to solve CFW3 problem on EKOS (error: Handshake failed: Timeout error. Firmware must be higher than 201409) I changed EKOS to use a CFW2 and now is working.
3 years 4 months ago #62405

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

Moderators: Radek Kaczorek
Time to create page: 2.007 seconds