Skip to main content

Xexun - U01 Protocol

This page summarizes the public protocol context for using the Xexun U01 UWB high precision positioning watch with the Plaspy platform. It explains how the device transmits positioning and telemetry data to Plaspy in broad, non sensitive terms and what role the communication protocol plays in a successful integration.

Plaspy uses shared connection settings across supported devices and automatically detects the tracker protocol when the device is configured to report to the Plaspy endpoint. Exact protocol behavior and available telemetry can vary by U01 firmware version, hardware revision, and manufacturer implementation, so this page focuses on general, public facing communication concepts rather than firmware internals.

Protocol Overview​

The U01 is a wristwatch style UWB positioning tag that provides high precision indoor location data plus physiological and event telemetry. In deployments the U01 broadcasts to UWB anchors and a positioning engine, and Plaspy ingests the resulting positional outputs and telemetry for live tracking, alerts, and reporting.

  • The protocol provides the means for the device to deliver position fixes and sensor telemetry to a central endpoint for processing.
  • It enables the tracker to identify itself and include device state such as battery and event flags alongside location and health data.
  • Protocol messages allow Plaspy to map UWB derived coordinates and telemetry to user accounts, geofences, and alarm rules.
  • The communication channel supports event driven reporting such as SOS alarms, low battery notices, and motion or activity updates.
  • By delivering consistent timestamps and device identifiers, the protocol makes historical playback and analytics possible.

How Plaspy Detects the Protocol​

Plaspy receives incoming device connections on a shared network endpoint and automatically determines which supported protocol a device is using. When a U01 or other compatible device is pointed to the Plaspy endpoint and port, manual protocol selection inside the platform is generally not required.

  • Plaspy uses the public server domain d.plaspy.com as a primary endpoint for device reporting.
  • The Plaspy server IP 54.85.159.138 is also available for devices that require a numeric address.
  • All devices in Plaspy use the same port and Plaspy automatically detects the tracker protocol without per device port changes.
  • Devices may be configured to use either UDP or TCP on port 8888 depending on their capabilities and deployment preferences.
  • When a U01 is properly configured to report to the Plaspy endpoint, Plaspy will ingest positional outputs and telemetry for processing and display.

Transport and Connection Context​

Connection context describes how the U01 reaches Plaspy rather than the internal format of protocol frames. The choice between UDP and TCP and the way devices point to Plaspy are typical transport level considerations during setup.

  • The U01 may be configured to send data using UDP or TCP on port 8888 depending on device support and site requirements.
  • Devices can be pointed to the Plaspy domain d.plaspy.com or the numeric address 54.85.159.138 as needed by the deployment.
  • Plaspy uses the same port for all supported devices which simplifies firewall and network configuration.
  • Transport selection can affect delivery guarantees and may be chosen to match network reliability or latency needs.
  • Ensure network routes and firewall rules allow outbound traffic to the Plaspy endpoint on port 8888 for reliable reporting.

Protocol Compatibility Notes​

  • Firmware revisions on the U01 can change available telemetry fields and event behavior; always check the device release notes.
  • Hardware revisions or optional modules such as RFID or NFC can affect which telemetry and events the device supplies to Plaspy.
  • Manufacturer configuration options may allow selecting UDP or TCP transport and configuring the report endpoint and interval.
  • Integration behavior depends on the external positioning engine and anchors that convert UWB broadcasts into coordinates ingested by Plaspy.
  • Verify that OTA updates or custom firmware do not change reporting endpoints or message timing required by Plaspy.
  • When in doubt, validate compatibility using test devices and review manufacturer documentation for the exact firmware build in use.

Why Protocol Understanding Matters​

Knowing the public aspects of the U01 communication protocol helps teams plan deployments, troubleshoot connectivity, and maintain reliable tracking over time. A clear grasp of transport and reporting expectations reduces integration time and improves operational uptime.

  • Properly configure the device to point to d.plaspy.com or 54.85.159.138 and use port 8888 to ensure data reaches Plaspy.
  • Understanding whether the device uses UDP or TCP helps tune network policies and expectations around message delivery.
  • Awareness of available telemetry items aids dashboard configuration and alert mapping in Plaspy.
  • Recognizing that firmware and hardware changes affect behavior reduces surprises after updates.
  • Protocol awareness speeds diagnosis of missed reports, battery alerts, or event notifications.

Why Use Plaspy with This Protocol​

Using the Xexun U01 with Plaspy provides a practical solution for organizations that need high precision indoor positioning together with physiological telemetry and event reporting. Plaspy ingests positional outputs from UWB anchors plus the U01’s vitals and state information to offer centralized visibility, alerting, and historical analysis for safety and operational workflows.

If you want to learn more about how Plaspy can integrate U01 devices in your deployment, visit https://www.plaspy.com to explore platform capabilities and deployment guides. For the most current device specific protocol details, firmware notes, and hardware revision information please verify with the manufacturer at https://www.xexun.com/ as protocol support and firmware behavior can change over time.

Tracker Communication

Looking for a platform that works with compatible protocols

Plaspy helps receive data from supported trackers and organize monitoring, visibility, and reporting in one place.

Learn more about Plaspy