Home › Forums › Forums › Technical Support for BerryGPS and BerryGPS-IMU › incorrect data received from the berrygps
- This topic has 3 replies, 2 voices, and was last updated 4 years, 8 months ago by bepeho.
- September 13, 2018 at 6:33 am #7546
My berrygps-imu is connected to a RPI3B+
I’ve double check its input DC power, the antenna wiring, and the connection between the 2 pieces of hardware
When cat /dev/ttyS0
I have at the beginning correct NMEA sentences. Exemple:
But after a few seconds, I’m receiving incorrect data. Exemple:
YV#�$:B”�7�TYt”��5#D23V33�D# F3TI6#FK��5!2D#�! D2
Could you please advise on the way to correct this ?
PSeptember 13, 2018 at 1:25 pm #7547PeterPParticipant
How do you have it connected? is it sitting on top of the GPIO of the Raspberry Pi?
What about the console… have you disabled it on the Serial?
what is the output of;
dmesg | grep tty
Peter --OzzMaker.com --September 13, 2018 at 3:44 pm #7548
Thank you very much for your reactivity.
The berrygps is soldered to its header, which is plugged to the rpi3.
The console is disabled as specified here
dmesg | grep tty
[ 0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=0bd45b7a-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[ 0.000284] console [tty1] enabled
[ 0.664405] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[ 0.665965] 3f215040.serial: ttyS0 at MMIO 0x0 (irq = 166, base_baud = 73500000) is a 16550
Note (for what is may worth), that I’ve checked with both the internal and the external antenna with the switch, for the same results.
I’ve tried a lot of things, even removing gpsd with the same results
PSeptember 14, 2018 at 10:42 pm #7551
It looks like I’ve fixed the issue by resetting to the default set of parameters in the /boot/config.ini file.
May be a bad power config ?
Everything’s back to normal now.
Thank you for your help.
- You must be logged in to reply to this topic.