Quick Start Guide

Getting Started

Understand PNX in 5 minutes — from principles to practice

What is PNX

PNX (Phone · Near · eXecute) is a decoupled keyless entry technology standard. It splits traditional BLE proximity mode's "fully automatic" into two automatic layers + one manual layer:

  • Phone: Phone Bluetooth seamlessly verifies identity
  • Near: RSSI signal determines if user is present
  • eXecute: User presses micro-switch to manually trigger unlock

Core idea: Verification completes automatically, execution triggers manually. Signal fluctuations no longer affect the final outcome.

Why PNX

Traditional BLE proximity mode has three major pain points:

  • Lockout: Standing at the car door, RSSI interference prevents threshold from being reached, door won't open
  • False trigger: Walking past three meters away, signal reflection suddenly strengthens, car unlocks unknowingly
  • Premature lock: Just exited vehicle, RSSI briefly drops, car locks early

PNX's decoupled design transfers "execution control" from automatic system judgment to user physical action, completely eliminating uncertainty from signal fluctuations.

Three-Step Workflow

1

Phone Verification

User carries authorized phone near vehicle. Module scans BLE broadcast, matches UUID whitelist.

Typical duration 1-3 seconds, completed seamlessly without taking out phone.

2

Proximity Confirmation

Module continuously monitors verified phone's RSSI value. When signal strength reaches unlock threshold (recommended -65dBm), system determines user is "present."

Micro-switch enters standby state, waiting for user trigger.

3

Manual Execution

User presses door handle micro-switch. System detects edge signal, confirms Layer 1 and Layer 2 both satisfied, then sends unlock command to vehicle control domain.

Typical delay ≤ 200ms. User retains final control authority.

For DIY Makers

If you're a Bluetooth key DIY enthusiast, PNX provides a clear architectural paradigm:

  • Unified naming: Call your "phone verification + manual execution" solution a PNX-compatible solution
  • Reference implementation: Read the technical specification for detailed BLE handshake, RSSI threshold, and micro-switch circuit parameters
  • Open source collaboration: Submit your implementation case to GitHub, building the PNX ecosystem together
  • Get certified: After passing compatibility tests, apply to use the PNX Compatible badge

PNX is not a single product, but an architecture standard. Any solution conforming to the Phone · Near · eXecute three-layer decoupled design can be called PNX.

For Solution Providers / Automakers

If you're a solution provider or automaker配套部门, PNX provides a low-cost, highly compatible keyless entry standard:

  • Low cost: Based on BLE 5.x, no UWB chips or NFC readers needed
  • High compatibility: Supports retrofit upgrade for 95%+ existing vehicles
  • Customizable: RSSI thresholds, switch logic, debounce time all configurable on demand
  • Certifiable: Pass PNX compatibility testing to obtain official certification badge

Learn about certification and technical whitepaper to start integrating PNX standard.

Next Steps

Join the PNX Ecosystem

Whether you're a DIY maker, solution provider, or automaker, you can participate in building and promoting the PNX standard.

Explore Certification