Home › Forums › Forums › Technical Support for BerryGPS and BerryGPS-IMU › Can’t get a fix, can’t see i2c devices
Tagged: nofix
- This topic has 8 replies, 3 voices, and was last updated 3 years, 1 month ago by manbehindthemadness.
- AuthorPosts
- June 14, 2020 at 6:49 am #15889rcwhitejrParticipant
Hi – I have followed the setup instructions for my Raspberry Pi 4 – 8gb. I get the NMEA sentences with cat /dev/serial0 , but they don’t populate with data. I ran it for about an hour. My desk is at a window and a USB fob gets a fix. Thoughts? Attaching nmea sentences and output of i2cdetect as well (which shows all blanks) plus an obligatory solder picture.
Thanks,
Robert
June 14, 2020 at 6:51 am #15890rcwhitejrParticipantSorry, my text files wouldn’t post. Here we go:
NMEA Sentences:
$GPGSV,2,1,02,07,,,20,09,,,23*76^M
$GLGSV,1,1,00*65^M
$GNGLL,,,,,,V,N*7A^M
$GNRMC,,V,,,,,,,,,,N*4D^M
$GNVTG,,,,,,,,,N*2E^M
$GNGGA,,,,,,0,00,99.99,,,,,,*56^M
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E^M
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E^M
$GPGSV,1,1,00*79^M
$GLGSV,1,1,00*65^M
$GNGLL,,,,,,V,N*7A^M
$GNRMC,,V,,,,,,,,,,N*4D^M
$GNVTG,,,,,,,,,N*2E^M
$GNGGA,,,,,,0,00,99.99,,,,,,*56^M
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E^M
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E^M
$GPGSV,1,1,00*79^M
$GLGSV,1,1,00*65^M
$GNGLL,,,,,,V,N*7A^M
$GNRMC,,V,,,,,,,,,,N*4D^M
$GNVTG,,,,,,,,,N*2E^M
$GNGGA,,,,,,0,00,99.99,,,,,,*56^M
$GNGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*2E^Mi2cdetect output:
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: — — — — — — — — — — — — —
10: — — — — — — — — — — — — — — — —
20: — — — — — — — — — — — — — — — —
30: — — — — — — — — — — — — — — — —
40: — — — — — — — — — — — — — — — —
50: — — — — — — — — — — — — — — — —
60: — — — — — — — — — — — — — — — —
70: — — — — — — — —
~
~June 14, 2020 at 12:37 pm #15895PeterPParticipantFor the GPS, you will need to test outside with clear access to skype.
regarding i2c, your soldering looks fine. do you have another i2c device which you can use to confirm that i2c is working on the Pi?
Can you upload an close up image of the bottom half of the board? (the end near the Pi USB ports)Peter --OzzMaker.com --
June 15, 2020 at 1:27 pm #15900rcwhitejrParticipantJune 15, 2020 at 1:28 pm #15901rcwhitejrParticipantJune 15, 2020 at 1:33 pm #15902rcwhitejrParticipantI don’t have another eye to see device currently. I’ll have the ability to test under a clear sky later this week. Wasn’t entirely clear to me what pictures you wanted so you got three. Thanks for any help.
Attachments:
June 15, 2020 at 1:52 pm #15906PeterPParticipantthank you for uploading the images.
everything looks good.
can you contact sales @ ozzmaker.com, copy link to this post. we may need to replace your boardPeter --OzzMaker.com --
June 22, 2020 at 2:11 am #15922rcwhitejrParticipantUpdate – Received replacement board and all appears to work fine so far. Of interest here the command “sudo i2cdetect -y 1” took about a minute or two to scan the defective board with null results, however it completes within a second with this replacement board. Thanks for the great customer support.
Robert
August 8, 2020 at 3:07 am #16052manbehindthemadnessParticipantInteresting, I am experiencing the exact same problem with my GPS data, however I am able to pull in the i2c data from the other sensors.
- AuthorPosts
- You must be logged in to reply to this topic.