Gravity: GNSS GPS BeiDou Receiver Module

SKU: TEL0157

DFRobot's Gravity Quectel-L76K GNSS positioning module supports single and multi-system positioning, delivering data like longitude, latitude, altitude, and time quickly. Multi-system combo offers higher precision/faster speed than single GPS (more satellites), stable in complex urban areas. With I2C/UART outputs, it works with Arduino, ESP32, Raspberry Pi. Ideal for outdoor scenarios: vehicle navigation, handheld trackers, item tracking, weather stations.

Front of GNSS GPS BeiDou receiver module for Arduino/Raspberry Pi-DFRobot product sku:TEL0157 image.
  • Docs
  • Tech Specs
  • Projects
  • Specification

    Parameter Details
    Operating Voltage 3.3 to 5.5V DC
    Output Signal I2C/UART
    GNSS module Quectel-L76K
    GNSS bands - GPS L1 C/A: 1575.42 MHz
    - GLONASS L1: 1602 MHz
    - BeiDou B1: 1561.098 MHz
    Channels 32 tracking channels
    Sensitivity - Auto-aquisition: -147dBm
    - Tracking: -162dBm
    - Re-acquisition: -159dBm
    Accuracy - Position: 2.0m CEP
    - Velocity: 0.1m/s
    - Acceleration: 0.1m/s²
    - Timing: 30ns
    Time for First Positioning 30s for cold start; 2s for hot start
    Power Consumption 40mA
    Antenna Interface IPEX1
    Antenna Frequency 1561-1575.42MHz±3MHz
    Dimension 27mm×37mm/1.06×1.46"

    Pinout

    Num Label Description
    1 D/T I2C data line SDA/UART Data Transmitting- TX
    2 C/R I2C clock line SCL/UART Data Receiving- RX
    3 - GND
    4 + VCC

    When no GPS signal is acquired, the indicator light appears red.
    When GPS signal is successfully acquired, the indicator light is green.

    FAQ

    • I feel that every time I purchase a product from DF Robot I'm left with no support and sub-par implementations. Don't get me wrong, the hardware is great, but the firmware / libraries that are (sometimes) included are not operable.

      In this instance the firmware on the chip reports latitude and longitude incorrectly. I'm not sure how to proceed forward with fixing this, there's no documentation (that I can find) on the issue. But now I've got to dedicate a day or three to figure out this issue, hopefully fix it before trying to use this in my project.

      This isn't the first time something from DFRobot has blocked my project progress, but hopefully it'll be the last time (I won't be buying more from DFRobot)

      Sorry, the Raspberry library does not have either of these features at this time.
      This is because the I2C/UART baud rates are fixed parameters set in the GNSS on-board MCU.
      And there is no option to change the baud rate in Raspberry library.

    • Why can't I get a GPS signal?

      This product only uses GPS functionality and does not use WiFi or Bluetooth for location assistance like mobile phones or other electronic devices. So we recommend that you use this product by a window, on a penthouse, or outdoors.

      When the on-board indicator light turns from red to green, it means that the product has successfully acquired a GPS signal.

    • Encountering I2C address conflicts?

      For a comprehensive guide on identifying and resolving I2C address conflicts in embedded systems, check out this detailed article: How to Resolve I2C Address Conflicts. It covers practical hardware and software solutions to ensure smooth communication in your IoT devices.

    Explore More Related Questions >

    Was this article helpful?

    TOP