Build with UNIVIPLink to the section Build with UNIVIP
On this page
Choose the side of the connection you are implementing, or run the simulator first. The reference software implements the v0.2 working draft and is intended for development and interoperability work.
Choose a starting pointLink to the section Choose a starting point
- Run the simulator Start a simulated vehicle and inspect its capabilities and telemetry. Add the .NET web viewer to see its synthetic camera stream.
- Integrate a vehicle or gateway Translate a vehicle's native interface into a UNIVIP Device.
- Integrate a VMS Host a Client endpoint, receive state and video, and expose supported controls.
Reference implementationsLink to the section Reference implementations
| Component | Purpose | Source |
|---|---|---|
| Python gateway | Simulator, MAVLink and DJI Cloud API adapters; Device REST and session proxy | Gateway documentation |
| .NET Client SDK | Session endpoint, typed devices, command tracking and leases | SDK documentation |
| .NET web viewer | Browser video, map, telemetry, events and optional control | Viewer documentation |
| .NET gateway | ASP.NET Core Device implementation with a simulator adapter | Gateway documentation |
Validation and securityLink to the section Validation and security
-
Software validation and emulation: package installation, fault injection, SDK interoperability and recorded browser checks in one command.
-
Implementation findings: gaps found while implementing the drafts.
-
SITL validation: PX4 and ArduPilot software-in-the-loop evidence and limitations.
-
Recording test: video and telemetry preservation and replay.
-
WebRTC security review: internal review of the .NET media stack and open work.
These reports have different scopes. Simulator or software-in-the-loop results do not establish performance on hardware. Self-declared interoperability reports are not conformance certificates; the conformance specification defines the claim boundary.