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

Read More...

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....

Read More...

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 GPS daemon? in dmesg it was shown pps0
Try to disable gpsd:
sudo systemctl stop gpsd gpsd.socket"

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

START_DEAMON="false"
USBAUTO="false"
and also put # in front of the rest...
And Now works perfectly.

For my hand is SOLVED!!!
Thanks to all,
Pep

Read More...

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:

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

Read More...

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

Read More...

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

Read More...

Hi,
I just try it and not there are other 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.
Only 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 works...
I hope give you enogh information.
Thanks for all,
Pep

Read More...

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

Read More...

Hello guys,

WORKS!!!!

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

Read More...

Hi guys,

A little bit light on my live... I executed "sudo lsof /dev/ttyUSB0" (this returns all the devices or process runs on the ttyUSB0. And the answer is:

sudo lsof /dev/ttyUSB0
[sudo] contrasenya per a astroberry:
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1001/gvfs
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
gpsd 1297 gpsd 8u CHR 188,0 0t0 22412 /dev/ttyUSB0

Then I understand that I need to KILL this device. Someone should help me to do it?
Thanks a lot,
Pep

Read More...

Hi Arado,
Then you suggest I do a rules file like:
SUBSYSTEMS=="usb", ACTION=="add", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", MODE="0666", SYMLINK+="OnStep"
but change usb for ttyACM.? and left like next:
SUBSYSTEMS=="ttyACM", ACTION=="add", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", ATTRS{serial}=="0001", MODE="0666", SYMLINK+="OnStep"ç
Is necessary to add someone other parameter on the rules file for this case (Kernel, run, ...)?
Someone knows how to change (if it's possible) the serial of the device?
Thanks,
Pep

Read More...

Hi Arado,
May I ask you send an exemple of the rules of ttyACM would have to create it? (kernel I'd use, subsystem, add, dventor,... All the thinks that you believe that is necessary)
Thanks,
Pep

Read More...

Hy to every body,

I tried, this weekend, a lot of test, include a script of AstroPi3 for generate a correct rules file. But continuos not work.
But this script only works for usb/ttyusb*, you suggest that could be that onstep use an other type of device? (like ttyS* or ttyAM*...)
For other hand I checked if, direct, to connect on PC (by Linux) works, and works perfectly.
Then I think that the problem cames from the raspi4 (4gb), i seems remember that raspi4 4gb are not completely stable yet, and obviously the kstart /indi doesn't works well.
Today I want to check on raspi3B and Rasoi3B+, and look what happens?
Thanks for all your support,

Pep

Read More...