LogoLogo
  • Ruuvi Developer Documentation
  • Ruuvi Hardware
    • RuuviTag B
    • RuuviTag Pro
    • Ruuvi Gateway
    • Ruuvi DevShield
    • Ruuvi Connector Kit
    • TMP 117 External Sensor
  • Ruuvi Connector System
    • Introduction
    • Expansion boards
    • Cables
    • Connectors
  • Ruuvi Sensor Firmware
    • 1.2.12
    • 2.5.9
    • 3.X
      • 3.x Sensors
      • 3.x Heartbeat
    • Device Firmware Update (DFU)
  • Ruuvi Gateway Firmware
    • GW Getting Started
    • GW Web-UI
      • Greeting window
      • Internet connection settings
        • Connection via Wi-Fi
        • Connection via Ethernet
      • Software update
      • Automatic configuration download
      • Automatic updates
      • Access Settings from LAN
      • Cloud Options
        • Backend: HTTP(s)
        • Backend: MQTT(s)
        • Backend: Statistics
      • Time Synchronisation Options
      • Bluetooth Scanning Settings
      • Configuration completion
      • Authentication when accessing from LAN
    • GW Install custom firmware
    • GW nRF52811 Firmware
      • GW nRF52811 selftest
      • GW nRF52811 scanning
      • GW nRF52811 repeating
      • GW nRF52811 UART communication
  • GW ESP32 Firmware
    • GW ESP32 WiFi Hotspot
    • GW ESP32 Button
    • GW ESP32 LED
    • GW ESP32 HTTP Client
    • GW ESP32 MQTT client
  • GW Data formats
    • HTTP: Time-stamped data from Bluetooth-sensors
    • HTTP: Data from Bluetooth-sensors without timestamps
    • MQTT: Time-stamped data from Bluetooth-sensors
    • MQTT: Data from Bluetooth-sensors without timestamps
    • HTTP GET /history (with timestamps) and decoding
    • HTTP: Gateway status
    • Gateway configuration
  • GW Examples
    • Polling mode
    • Poll endpoint "/metrics"
    • Configuration update via API
    • Firmware update via API
    • Configuration download from a remote server via API
    • MQTT examples
    • Home Assistant
    • MQTT+AWS IoT Core
  • Communicate with RuuviTag devices via Bluetooth
    • Bluetooth advertisements
      • Data format 3 (RAWv1)
      • Data format 4 (URL)
      • Data format 5 (RAWv2)
      • Data format C5 (Cut-RAWv2)
      • Data format 8 (Encrypted environmental)
    • Bluetooth connection
      • DIS (Device Information Service)
      • NUS (Nordic UART Service)
        • Heartbeat transmissions
        • Read logged history
    • Real Time Transfer (RTT)
  • Communicate with Ruuvi Cloud
    • Ruuvi Cloud
      • User API
      • Gateway API
      • Internal API
      • Alerts
      • Cloud stored app settings
  • Ruuvi Community projects
    • Integrations
Powered by GitBook
On this page
Edit on GitHub
  1. Ruuvi Gateway Firmware
  2. GW nRF52811 Firmware

GW nRF52811 scanning

nRF52811 scans continuously with 7000 ms scan window and 7000 ms scan window. This allows Ruuvi Gateway to reliably detect slow RuuviTag advertising which is once per 6425 ms.

Each scan is done on one enabled channel at a time, and once every selected channel is scanned next PHY is scanned. For example if the default setting of scanning all primary advertising channels 37, 38 and 39 on long range and 1 MBit / s modulation is enabled, one complete scan takes 3 channels * 2 PHYs * 7000 ms for a total of 42 seconds.

Some Bluetooth devices can also advertise on secondary channels, the secondary advertisement works by first advertising information of secondary advertisement on primary channel and then sending secondary advertisement on any channel and modulation. If the primary advertisement was on long range PHY only long range secondary advertisements are scanned, if primary advertisement was on 1 MBit / s PHY secondary advertisement can be either 1 MBit / s or 2 MBit / s.

By default nRF52811 will report only Ruuvi manufacturer specific data, but it's possible to configure the scan to report all seen beacons.

Gateway can be configured via UART to enable/disable channels and PHYs with ruuvi_endpoint_ca_uart commands.

PreviousGW nRF52811 selftestNextGW nRF52811 repeating

Last updated 1 year ago