← All IP · the catalog
Drone, Robotics & UAV Safety

Remote ID Broadcaster

remoteid is an ASTM F3411 / FAA Remote-ID broadcast-message framing engine for uncrewed aircraft (drones) — the regulatory “digital license plate”…

Request this IP →Browse the catalog
ASIL-B
target
91.00%
SPFM
89.01%
LFM
PASS
FMEDA
2.6K
gates
1.0.0
version
The deliverable

What you’re licensing

remoteid is an ASTM F3411 / FAA Remote-ID broadcast-message framing engine for uncrewed aircraft (drones) — the regulatory “digital license plate”… It is delivered as a licensable soft-IP block engineered as an ASIL-B Safety Element out of Context — not just RTL, but the complete functional-safety work package needed to carry it into an ISO 26262 program:

Synthesizable RTL
Portable, vendor-neutral SystemVerilog that drops onto your existing SoC fabric — no foundry or EDA-tool lock-in.
Per-IP FMEDA report
SPFM / LFM / PMHF computed against the ASIL target per ISO 26262-5 — the quantitative analysis your assessor asks for.
Safety manual
Assumptions of use, the safety mechanisms and their diagnostic coverage — written to drop straight into your safety case.
IP-XACT + integration docs
A machine-readable descriptor plus register and integration documentation for fast, low-risk bring-up.
Self-checking testbench
A self-checking (crypto: bit-exact) testbench and a one-command build, so you can reproduce every claim on day one.

What it is

remote_id is an ASTM F3411 / FAA Remote-ID broadcast-message framing engine for uncrewed aircraft (drones) — the regulatory “digital license plate” broadcaster.

Key Features

Standards & Compliance

ASTM F3411, FAA Remote ID (14 CFR Part 89)

Functional Safety

ASIL-B (SEooC) · SPFM 91.00% · LFM 89.01% · PASS

ISO 26262:2018 · FMEDA available · Safety Manual included

Register Map

OffsetRegisterDescription
0x00CTRLRW [0]=EN [1]=GO(self-clear, force one broadcast) [2]=WD_EN
0x04STATUSRO [0]=BUSY [1]=FRAME_RDY [3:2]=fsm_state [6:4]=msg_sel [7]=ERR_VALID [11:8]=ERR_CODE [23:16]=byte_count
0x08MSG_HDRRW [3:0]=protocol_version [7:4]=message_type(active) [12:8]=ua_type [16]=id_type [21:17]=msg_qty(pack) [28:24]=uas_i…
0x0CBASICRW [3:0]=op_status [7:4]=loc_flags (location body[0] fields)
0x10LATRW [31:0] latitude (signed, degrees * 1e7)

…20 more registers — see datasheet for the full table.

Getting Started

// Minimal instantiation
remote_id #(
  .ADDR_W(6)
) u_remote_id (
  .clk       (clk),
  .rst_n     (rst_n),
  // APB4
  .p_paddr   (paddr),
  .p_psel    (psel),
  .p_penable (penable),
  .p_pwrite  (pwrite),
  .p_pwdata  (pwdata),
  .p_prdata  (prdata),
  .p_pready  (pready),
  // Safety
  .err_clear (1'b0),
  .err_valid (err_valid),
  .err_code  (err_code)
);

Configure via the CTRL register after reset to enable the IP and set operating parameters. Monitor err_valid / err_code for any safety faults reported by the built-in safety monitor.

Applications

Where it fits

Typically deployed in UAV flight controllers and robotics platforms operating under a functional-safety mandate.

The case

Why license it, not build it

Skip 12–18 months
The FMEDA and the safety case are already generated. You integrate a finished safety element — you don’t stand up a safety-IP program to originate one.
One vendor, one safety story
Every block in the catalog shares the same safety architecture, fault-reaction model, and FMEDA methodology — so subsystems roll up cleanly.
Verified, not vapor
The RTL builds and passes today; the safety metrics come from analysis and fault injection against real RTL, not a datasheet promise.

Interested in Remote ID Broadcaster?

Pricing, the per-IP FMEDA, safety manual, and RTL data room are shared under a mutual NDA.

Talk to us →See related IP

Figures are pre-silicon engineering-grade estimates for a Safety Element out of Context (SEooC); final ASIL sign-off is the integrator’s, supported under NDA. FMEDA and Safety Manual available under NDA.

circuit-design.space · +1-971-357-1400 · sales@circuit-design.space