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

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

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.

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

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

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

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

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.

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

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.

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

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.