Berry GPS-IMU not shown in i2c

Forums Technical Support for BerryGPS and BerryGPS-IMU Berry GPS-IMU not shown in i2c

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • #7404
    Xi
    Participant

    Hi there,

    I recently bought Berry GPS-IMU for RP 3, but looks this device doesn't show in i2cdetect at all. I tried 2 IMUs and 2 RPs, no luck.

    I was using the female head to pin it to the GPIO, properly soldered.

    command line output as follows :

    pi@raspberrypi:~ $ sudo i2cdetect -y 1

    0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

    00:          -- -- -- -- -- -- -- -- -- -- -- -- --

    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

    70: -- -- -- -- -- -- -- --

    I was follwing this guide to enable my rp's i2c

    https://learn.adafruit.com/adafruits-raspberry-pi-lesson-4-gpio-setup/configuring-i2c

     

    please help!

    • This topic was modified 2 years, 4 months ago by Xi.
    • This topic was modified 2 years, 4 months ago by Xi.
    Attachments:
    #7408
    PeterP
    Participant

    Hi

    We do test every one before it gets packaged.. so it is very rare that one will not be working, but it does happen.
    Lets first checked i2c.

    ls -l /dev/i2*
    
    lsmod | grep i2c
    
    grep i2c  /boot/config.txt

    Is the GPS working?

    Peter --OzzMaker.com --

    #7412
    Xi
    Participant

    pi@raspberrypi:~ $ ls -l /dev/i2*

    crw-rw---- 1 root i2c 89, 1 Jun 18 18:05 /dev/i2c-1

    pi@raspberrypi:~ $ lsmod | grep i2c

    i2c_bcm2835             7167  0

    i2c_bcm2708             5994  0

    i2c_dev                 6913  0

    pi@raspberrypi:~ $ grep i2c  /boot/config.txt

    dtparam=i2c_arm=on

    dtparam=i2c1=on

     

    GPS is not working either, no green led light, gpsmon is displaying nothing either.

     

     

    #7413
    PeterP
    Participant

    The LEDs will only come on once there is a GPS fix.

    Can you follow this guide up until you reach this command cat /dev/serial0
    https://ozzmaker.com/berrygps-setup-guide-raspberry-pi/

    Let me know if you see any information from the GPS

    Peter --OzzMaker.com --

    #7425
    Xi
    Participant

    somehow I can't paste the whole output from the console, please find screenshot as attached.

    #7427
    Xi
    Participant

    gpsmon's output:

    tcp://localhost:2947          JSON slave driver>

    (115) {"class":"VERSION","release":"3.11","rev":"3.11-3","proto_major":3,"proto_minor":9,"remote":"tcp://localhost:

    2947"}

    (125) {"class":"DEVICES","devices":[{"class":"DEVICE","path":"tcp://localhost:2947#/dev/serial0"}],"remote":"tcp://

    localhost:2947"}

    (154) {"class":"WATCH","enable":true,"json":false,"nmea":false,"raw":2,"scaled":false,"timing":false,"split24":fals

    e,"pps":true,"remote":"tcp://localhost:2947"}

    #7429
    PeterP
    Participant

    thanks, the screenshot shows that the GPS is working.  So the PCB does have power.

    Last item to check, can you please check the solder on the two connections highlighted  below. Maybe touch them up with more solder.

     

     

    If it doesn't work after this, please send your order receipt to sales< at >ozzmaker.com.  we may have to send you a another one

    Peter --OzzMaker.com --

    #7433
    Xi
    Participant

    no luck with more solder.

    I bought 2 from amazon, returned one already due to the same situation, does it has something to do with the whole batch of the product?

    anyway, i'm going to send the receipt to sales email, thanks!

    #15695
    tp52
    Participant

    Hi Xi and Peter,

    I have the same problem: I have a BerryGPS-IMU v3 interfacing with a Raspberry Pi Zero W. I am able to connect to the GPS, but I can't find the I2C devices. I've worked through the IMU tutorial and the GPS one. Here are some relevant terminal outputs.

    pi@raspberrypi:~ $ sudo i2cdetect -y 1
    0 1 2 3 4 5 6 7 8 9 a b c d e f
    00: -- -- -- -- -- -- -- -- -- -- -- -- --
    10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
    70: -- -- -- -- -- -- -- --
    pi@raspberrypi:~ $ ls -l /dev/i2*
    crw-rw---- 1 root i2c 89, 1 Mar 27 04:17 /dev/i2c-1
    
    pi@raspberrypi:~ $ lsmod | grep i2c
    i2c_bcm2835 16384 0
    i2c_bcm2708 16384 0
    i2c_dev 16384 0
    
    pi@raspberrypi:~ $ grep i2c /boot/config.txt
    dtparam=i2c_arm=on
    dtparam=i2c1=on

    I won't show the GPS output since I don't want to dox myself, but the GPS is reading accurately. I have the hat soldered onto a double-stack header board, and what my solder joints lack in elegance they make up for in volume (see pic). I've already added more.

    Any ideas for what might be causing the I2C devices to fail? Maybe I should interface directly with sales, but I want to make sure I haven't missed anything first.

    #15699
    Xi
    Participant

    hi tp52, i had no luck making it work, had to switch to other products.

    #15711
    tp52
    Participant

    Hi Xi and Peter,

    It turns out that there was no continuity between the SCL and SDA pins and the IMU chip pins. I isolated the error to the length of trace between the lower breakout holes and the upper break-out holes. The discontinuity could be caused by my thumb-handed buffoonery while soldering, or there may be a common-cause failure of both traces on the PCB.

    I was able to fix it by soldering wires to connect the lower to the upper breakout holes. If you want to salvage your BerryGPS-IMU, you could see if that is the problem and give it a try!

    Best,

    Tim

    #15712
    Mark Williams
    Keymaster

    Hi Tim
    Do you know exactly where the traces where broken? i can investigate to see if the PCB design can be improved

    Mark --OzzMaker.com --

    #15713
    tp52
    Participant

    Hi Mark,

    I did not see exactly where the traces were broken. When I look closely, I can almost convince myself that I see a bit of copper on the back side of the board where the SCL trace meets the pin, but I'm not sure. I've attached photos of the front and back (please excuse the nasty soldering job -- I'm quarantined away from good tools).

     

Viewing 13 posts - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.

Blip, blop, bloop...