---
title: "PToB — sub-1µs MCU time transfer over Bluetooth"
description: "Bluetooth and USB software clocks: W12 60.3 ns relative-PPS RMS over 522/600 observations, separate 64 s sampled holdover, and CoreSE diagnostics."
url: "https://ptob.dev/"
language: "en"
robots: "index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1"
representations: {"application/json":"https://ptob.dev/?format=json","text/markdown":"https://ptob.dev/?format=markdown"}
format_description: "https://ptob.dev/agent-formats.json"
---

# Nanosecond time sync over Bluetooth

PToB applies Precision Time Protocol (PTP) principles to BLE-enabled MCUs, using radio-event timestamps and follow-up data for sub-1 µs time transfer over Bluetooth.

**[62.5 ns one-relay PPS-shadow RMS.](https://ptob.dev/research/#t096-relay)**
GM → T096 (nRF52) intermediary → T096 receiver. [Results depend on the MCU’s timing path. (PDF)](https://ptob.dev/papers/preview/?file=%2Fpapers%2Fptob-viability-preprint-20261030.pdf)

## Explore the timing network

**T096  A** Grandmaster  Independent source

**ESP32  B** Receiver  Root A

**T096  C** Receiver  Root A

**ESP32  D** Receiver  Root A

Bluetooth Low Energy   Packet label = sender / root source

V14 grandmaster A broadcasts timing events and later corrections. Receivers synchronize their local clocks through passive reception.

 V14 · illustrative topology

**Public reception** · Receive time without pairing.

**Boundary-clock mesh** · Regenerate time while preserving root provenance.

**GM elections** · Select an authorized time source.

## How PToB synchronizes a clock

A receiver timestamps a radio event and uses follow-up data to recover its transmit instant. A Software PLL tracks offset and drift between heterogeneous devices, synchronizing each local clock. The timing path and calibration determine precision.

1. ### Broadcast

   A time source publishes an event over BLE.
2. ### Capture

   A capable receiver timestamps the physical radio event.
3. ### Correct

   Follow-up data identifies the original transmit instant.
4. ### Synchronize

   The receiver disciplines its own clock to the source.

Basic scanners can use the broadcast time. Higher precision requires hardware timestamps and a calibrated clock model.

[T096 timing architecture Follow hardware capture through the servo, SoftPLL and delivered clock. Explore each mode and trace drift or offsets. Open the interactive schematic](https://ptob.dev/hardware/t096/timing/)

## Explore the protocol, packet by packet

Follow a source through a dedicated relay clock to a client. Match each original event with its later correction, then inspect V14’s exact bytes and clock-age rules.

[Open the V14 packet explorer](https://ptob.dev/packet-explorer/)

V14-RC1 synthetic examples. Physical precision remains unqualified.

### One 62.5 ms timing frame

 Source → RC → client

**Source** GM · TX

**RC 1** RC · TX

**Client** Client · RX

**New events at each clock.** The RC’s nominal slot follows the root by 15.625 ms. Its later correction carries local map generation and inherited age. Marks are widened for visibility; their widths are illustrative.

## Measured timing on BLE-enabled MCUs

Nordic’s nRF52840 captures physical radio events; the ESP32-S3 W12 uses empirical receive-active capture. These separate experiments query delivered BLE time against local PPS witnesses. Each retains its own path, date and coverage.

### nRF52

 Nordic · T096 (nRF52840)

62.5  ns   One-relay PPS-shadow RMS

A grandmaster, relay clock and receiver distribute time across two BLE links, measured against an independent local PPS witness.

Absolute P95 / maximum

123.25 / 191 ns

Usable / nominal observations

436 / 602 · 72.425%

Platform

Heltec T096 · nRF52840

### ESP32-S3

 Espressif · W12

60.3  ns   W12 relative-PPS RMS

W12 checks its delivered BLE clock at local GNSS PPS edges. GNSS observes the clock without training it; the full result retains the source-transition gap.

Absolute P95 / maximum

122 / 180 ns

Eligible / logged observations

522 / 600 · 87.0%

Platform / windows

W12 · ESP32-S3 · 2 × 300 s

Separate sampled shadow holdover

[64 s · P99 760 ns · 128 prefixes](https://ptob.dev/research/#w12-holdover)

The stable second window reached 38.3 ns RMS across 300/300. After W12’s relay, T096 measured 61.9 ns RMS across 451/600, with a 211 ns maximum.

[Read the W12 results and TX limits](https://ptob.dev/research/#w12-utc-basis)

The 30 October holdover study separately reaches 75 s in a fixed cohort, failing at 76 s; later rolling windows end at 24 s. Sampled holdover does not guarantee continuous accuracy.

How these numbers are measured

A PPS-shadow measurement queries the receiver’s already-published BLE clock at a separately captured pulse-per-second (PPS) edge on the same hardware counter. The reference validates the BLE clock and does not train it.

The 12 October T096 one-relay result is 62.504 ns RMS including bias over 436/602 usable/nominal boundaries. The 24 October W12 result is 60.3 ns RMS including bias over 522/600 logged PPS observations. All 78 unavailable records and the 180 ns maximum remain; the stable 300-sample window is reported separately. [Inspect every W12 window and population.](https://ptob.dev/research/#w12-utc-basis)

After the W12 relay, T096 delivered PPS phase is 61.9 ns RMS over 451/600 with a 211 ns maximum. The separately sampled TX check scores 58/120 selected transmissions: 108.3 ns RMS and a 226 ns maximum, with 61 missing matches and one lacking PPS brackets. These have different measurement paths and denominators.

RMS is not a worst-case bound or UTC certification. Physical output, RF endpoint and absolute UTC accuracy remain unqualified. Calibration transfer to other W12 units and profiles is unmeasured. [Earlier direct results](https://ptob.dev/research/#results) remain separately dated.

[Read the hardware guide](https://ptob.dev/hardware/)

Four ESP32-S3 targets: W12, [CoreSE Precision Clock](https://ptob.dev/hardware/#corese), StickS3 and CoreClock. CoreSE adds a touchscreen clock, six diagnostic pages and a separate shadow holdover instrument. CoreClock is not publicly available.

## How PToB compares

PToB uses nRF52 and ESP32-S3 platform timing features that can be reused in compatible devices. Compare the measured target configurations with other BLE timing research.

| Approach | Transport & hardware | Reported precision | Measurement & conditions | Protocol / standard |
| --- | --- | --- | --- | --- |
| [ESP32-S3 · PToB](https://ptob.dev/research/#w12-utc-basis) 24 October 2026 | Passive BLE advertising Meshnology W12 · ESP32-S3 receiver | 60.3 ns Delivered relative-PPS RMS · includes bias P95 122 ns · P99 156 ns · max 180 ns | Local GNSS PPS witness Two 300 s windows; 522/600 eligible, 78 unavailable. Stable second window: 38.3 ns RMS, 300/300. Downstream relay: 61.9 ns RMS, 451/600, max 211 ns. Physical output and calibrated UTC unqualified. | [Public protocol proposal](https://ptob.dev/papers/preview/?file=%2Fpapers%2Fptob-proposal.pdf) W12 fine-clock receiver; empirical RX capture and causal clock mapping. |
| [nRF52 · PToB](https://ptob.dev/papers/preview/?file=%2Fpapers%2Fptob-v14-preprint.pdf) 12 October 2026 | Passive BLE advertising Heltec T096 · nRF52840 · one relay | 62.5 ns One-relay PPS-shadow RMS P95 123.25 ns · P99 160.25 ns · max 191 ns | Independent local PPS witness 601.576 s; 436/602 usable/nominal (72.425%). RMS includes bias; calibration frozen before validation. GPIO output not independently measured. | [Public protocol proposal](https://ptob.dev/papers/preview/?file=%2Fpapers%2Fptob-proposal.pdf) PTP-inspired service contract, profiles, and wire format. Not an adopted standard. |
| [Nordic timeslot demo](https://devzone.nordicsemi.com/guides/short-range-guides/b/bluetooth-low-energy/posts/wireless-timer-synchronization-among-nrf5-devices) 2016 | Proprietary radio timeslots 100 Hz · no competing stack in the cited test | 65.6 ns Mean GPIO difference SD 41.0 ns · max 220 ns | Logic-analyzer GPIO comparison 30 minutes; 439,445 toggles. Two nearby nRF52 development kits. | Open reference code Vendor demo using proprietary timing packets; no standardized BLE time service. |
| [MicroSync](https://da.lib.kobe-u.ac.jp/da/kernel/0100491658/0100491658.pdf) 2024 | Connected BLE nRF52840 · central + three peripherals | 272 ns Mean absolute error SD 319.2 ns · 99% CDF 591.25 ns · RMS not reported | External GPIO comparison · 800 MHz High-accuracy scheduling. Bidirectional exchanges and PA/LNA timing signals. | Published research protocol BLE connection transport. Synchronization and scheduling described in the paper. |
| [BlueSync](https://ieeexplore.ieee.org/document/9555832/) 2021 / 2022 | Connectionless BLE beacons Hardware event capture + follow-up timestamps | 320 ns Average sync error per 60 s Best reported setting · single hop | Two commercial BLE SoCs 10-minute sessions without resynchronization. Drift-management and packet settings vary. | Published research protocol BLE beacon transport. Timing and drift-management methods described in the paper. |
| [CheepSync](https://arxiv.org/abs/1501.06479) 2015 / 2016 | BLE advertising nRF24Cheep broadcasters · Android listeners | ~10 µs Average single-hop accuracy Low-level timestamps and error compensation | Advertiser-to-listener experiments Heterogeneous passive listeners on resource-constrained hardware. | Published research protocol Built on Bluetooth 4.0 advertising. Timing service described in the paper. |

Rows are ordered by the displayed timing value. RMS, mean absolute error, standard deviation, and mean GPIO difference are distinct statistics measured under different test conditions. The studies do not establish a matched output-accuracy or energy benchmark. BLE transport alone does not define a standardized time service.

[Read the measurement methods](https://ptob.dev/research/)

## Plan a wireless timing deployment

Start with nearby devices. Add a grandmaster standby, extend through relay clocks, and bring time into macOS over USB.

[Explore deployment scenarios](https://ptob.dev/deployment/)

**GM  ACTIVE** HOT standby

**RC1****RC2****Clients**

One reference. Local clocks across the network.
Explore 1, 2 or 3 GMs, relay depth, LoRa fallback and USB.

## From the blog

[All articles](https://ptob.dev/blog/)

### [The precision clock hiding in every USB port](https://ptob.dev/blog/usb-frame-timing/)

Every USB connection keeps a steady 1 ms beat. Early PToB experiments on a Mac and a Raspberry Pi suggest it could carry far finer time than its reputation allows.

18 November 2026 [Read the article](https://ptob.dev/blog/usb-frame-timing/)

## Questions about PToB

A starting point for the protocol, the measurements and the work still ahead.

### [What is PToB?](https://ptob.dev/#what-is-ptob)

PToB means Precision Time over BLE, or Bluetooth Low Energy. It is an experimental, PTP-inspired protocol for synchronizing clocks across microcontrollers. Receivers timestamp radio events, recover their transmit times from follow-up data, and track clock offset and drift with a software phase-locked loop (Software PLL). PToB is an independent proposal, not an adopted Bluetooth SIG or IEEE standard. [Explore the timing architecture.](https://ptob.dev/deployment/)

### [How precise is PToB over Bluetooth?](https://ptob.dev/#bluetooth-timing-precision)

In the 24 October 2026 W12 ESP32-S3 experiment, the delivered BLE clock measured 60.3 ns RMS including bias against independent local PPS observations: 522 of 600 observations were eligible, 78 were unavailable, and the maximum measured error was 180 ns. This is a result for that hardware, path and population. RMS is not a worst-case bound; absolute UTC accuracy and continuous availability remain unqualified. [Read the measurements and limits.](https://ptob.dev/research/#w12-utc-basis)

### [Can PToB deliver time to a Mac?](https://ptob.dev/#ptob-macos-time)

The experimental Apple M-series macOS client receives time through a USB-connected PToB clock and uses a private user-level chrony clock. It leaves the system clock unchanged. Reported shared-source agreement is separate from independent UTC accuracy, and withheld observations remain part of the results. [Inspect the USB/macOS findings.](https://ptob.dev/hardware/#macos-results)

### [Does PToB support LoRa timing?](https://ptob.dev/#ptob-lora-timing)

PToB has a separate experimental LoRa timing path. The proposed longer-distance extension uses narrower channels, short broadcasts, channel hopping and known-distance propagation correction for fixed installations. Range and delivered precision need measurement; the measured BLE results do not qualify LoRa performance. [Read the LoRa design direction.](https://ptob.dev/blog/passive-lora-channel-hopping/)

## Explore the research

Read the papers, methods and measured results behind PToB. The research portal connects each study with its summary, evidence and limits.

[Explore the research portal](https://ptob.dev/research/)[View results on GitHub](https://github.com/yantisj2/PToB/blob/main/evidence/README.md)

[PToB viability The architecture, evidence and limits of a rooted BLE timing mesh. Public-review preprint · 30 October 2026 Read summary](https://ptob.dev/research/ble-timing-mesh-viability/)

[V14 protocol proposal How sources, receivers and relays share time and preserve its origin. Public-review release candidate · 6 November 2026 Read summary](https://ptob.dev/research/v14-protocol-proposal/)

[Affordable timing from Starlink over WiFi Explore affordable timing with an existing Starlink, WiFi beacons and an ESP32-S3: 19.226/8.240 µs RMS in two GNSS-phase-calibrated runs. Portable UTC accuracy remains unqualified. Latest paper · 3 November 2026 Read summary](https://ptob.dev/research/starlink-wifi-timing/)

### Jonathan Yantis × GPT 6.1

Jonathan Yantis leads hardware development, protocol design, and research, with GPT 6.1 contributing to implementation, analysis, and documentation.

## Structured data

```json
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebSite",
      "@id": "https://ptob.dev/#website",
      "url": "https://ptob.dev/",
      "name": "PToB",
      "alternateName": [
        "Precision Time over BLE",
        "Precision Time over Bluetooth"
      ],
      "description": "Bluetooth and USB software clocks: W12 60.3 ns relative-PPS RMS over 522/600 observations, separate 64 s sampled holdover, and CoreSE diagnostics.",
      "inLanguage": [
        "en",
        "de"
      ],
      "publisher": {
        "@id": "https://ptob.dev/#jonathan-yantis"
      }
    },
    {
      "@type": "Person",
      "@id": "https://ptob.dev/#jonathan-yantis",
      "name": "Jonathan Yantis",
      "url": "https://github.com/yantisj2/PToB/blob/main/CREDITS.md"
    },
    {
      "@type": "Project",
      "@id": "https://ptob.dev/#project",
      "name": "PToB",
      "alternateName": "Precision Time over BLE",
      "url": "https://ptob.dev/",
      "description": "An independent protocol project researching precision time transfer across Bluetooth-enabled microcontrollers and USB clients.",
      "sameAs": "https://github.com/yantisj2/PToB",
      "member": {
        "@id": "https://ptob.dev/#jonathan-yantis"
      },
      "knowsAbout": {
        "@id": "https://ptob.dev/#protocol"
      }
    },
    {
      "@type": "Thing",
      "@id": "https://ptob.dev/#protocol",
      "name": "Precision Time over BLE",
      "alternateName": "PToB",
      "description": "An experimental PTP-inspired protocol proposal for wireless clock synchronization over Bluetooth Low Energy."
    },
    {
      "@type": "WebPage",
      "@id": "https://ptob.dev/#webpage",
      "url": "https://ptob.dev/",
      "name": "PToB — sub-1µs MCU time transfer over Bluetooth",
      "description": "Bluetooth and USB software clocks: W12 60.3 ns relative-PPS RMS over 522/600 observations, separate 64 s sampled holdover, and CoreSE diagnostics.",
      "inLanguage": "en",
      "keywords": [
        "Precision Time over BLE",
        "sub-1us time transfer over Bluetooth",
        "sub-1us time transfer over USB",
        "Experimental LoRa time transfer",
        "MCU clock synchronization",
        "Software PLL between heterogeneous devices",
        "Boundary-clock relays"
      ],
      "isPartOf": {
        "@id": "https://ptob.dev/#website"
      },
      "author": {
        "@id": "https://ptob.dev/#jonathan-yantis"
      },
      "about": {
        "@id": "https://ptob.dev/#protocol"
      },
      "dateModified": "2026-11-18",
      "image": "https://ptob.dev/social/ptob-timing-v3.jpg",
      "relatedLink": [
        "https://ptob.dev/deployment/",
        "https://ptob.dev/hardware/",
        "https://ptob.dev/research/",
        "https://ptob.dev/blog/"
      ],
      "citation": [
        {
          "@type": "CreativeWork",
          "name": "PToB Viability: Rooted BLE Timing Meshes for Heterogeneous Edge Networks",
          "url": "https://ptob.dev/papers/ptob-viability-preprint-20261030.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "Paired Clock Time Transfer from Starlink over Wi-Fi: Causal Filtering, Drift, and GNSS-Shadow Validation",
          "url": "https://ptob.dev/papers/starlink-wifi-hybrid-timing-20261103.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "A Raspberry Pi Time Server at the Edge of a BLE Timing Mesh: Measured M-HAT PPS Transfer and Prospects for USB and Reverse PTP Gateways",
          "url": "https://ptob.dev/papers/pi5-mhat-gateway-20261102.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "Trustworthy Hardware Timestamps in Zephyr: Event Association, Clock Continuity, and Service Availability",
          "url": "https://ptob.dev/papers/zephyr-hardware-timestamps-20261101.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "Empirical Sub-Microsecond Holdover on BLE-Trained Software Clocks",
          "url": "https://ptob.dev/papers/ptob-empirical-sub-microsecond-holdover-20261030.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "PToB-IPS: Toward GNSS-like Indoor Positioning with Surveyed BLE Timing Beacons",
          "url": "https://ptob.dev/papers/ptob-indoor-ips-preprint.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "V14 protocol proposal",
          "url": "https://ptob.dev/papers/ptob-v14-release-candidate-20261106.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "V14 research paper",
          "url": "https://ptob.dev/papers/ptob-v14-preprint.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "Beyond USB Packet Arrival: Frame-Identified Time Transfer to macOS",
          "url": "https://ptob.dev/papers/usb-macos-time-transfer-20261017.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "Low-Level Timing on ESP32-S3: Event Capture, Clock Bridges, and Causal Validation",
          "url": "https://ptob.dev/papers/ptob-esp32s3-low-level-timing.pdf"
        },
        {
          "@type": "CreativeWork",
          "name": "A Shared Time Base for Robotic gPTP and TSN Systems",
          "url": "https://ptob.dev/papers/ptob-gptp-tsn-robotics-preprint.pdf"
        }
      ]
    }
  ]
}
```
