ULS-XSpot Interface Control Document

Interface Control Document ULSDC-PBICD231125, version 1.0.2

ULSDC-PBICD231125 · version 1.0.2 · issued November 23, 2025
The numbered PDF is the controlled copy: download it from the portal.

Introduction

Purpose

This document outlines the interfaces between the ULS-XSpot system components, including the tether-compatible transmitter, receiver, and autopilot systems (Ardupilot, PX4, and similar). The ULS-XSpot is specifically designed for tethered drone operations with a 50-meter working range.

Scope

This document is intended for use by system engineers, integrators, and developers working with ULS-XSpot systems in tethered drone applications. It provides detailed information on the interfaces between the system components, ensuring seamless integration and operation with tether management systems.

Key Features for Tethered Operations

  • Tether-Compatible Design: Center hole in transmitter for cable passage
  • Working Range: 50-meter working distance
  • Standard IR Optical: No DACS technology required
  • Continuous Operation: Designed for 24/7 operation with tethered power

System Components

Transmitter (Ground Unit - Tethered Design)

ULS-XSpot Transmitter

Figure: ULS-XSpot Transmitter with Center Tether Hole The ULS-XSpot transmitter is specifically designed for tethered drone systems. It features a center hole for tether passage, allowing the drone’s power and data cable to pass through while maintaining optical positioning capabilities. The transmitter is placed on the ground (platform, moving object) and emits a signal in the Infrared range, serving as a positioning beacon for tethered drone landing and station-keeping.

The primary function of the transmitter is to continuously send out a coded signal that can be detected and interpreted by the receiver unit onboard the tethered copter. This signal contains critical information needed for the operation of the system, such as positional data and status. The tethered design allows for extended flight duration while maintaining precision positioning.

Key Features:

  • Center hole for tether cable passage (integrated tether management)
  • Working range: 50 meters working distance
  • Optimized for tethered drone operations
  • Continuous power available via tether connection

Receiver (Onboard Unit)

ULS-XSpot Receiver

Figure: ULS-XSpot Receiver The receiver is a device that is placed on board the tethered aircraft. The receiver decodes the IR signal to derive flight information such as positional coordinates, real-time transmitter status updates, and positioning guidance. It interprets the data to navigate accurately and ensure the drone maintains its position relative to the ground station. It provides feedback to autopilot systems, such as Ardupilot and PX4, to adjust the flight parameters as needed for optimal station-keeping, landing, or hovering operations while connected to the tether.

Key Features:

  • Compatible with tethered drone configurations
  • Real-time position feedback for station-keeping
  • Seamless integration with tether management systems

Interface Overview

System Interfaces Overview

Figure: ULS-XSpot System Interfaces Overview

Note: The ULS-XSpot uses the same interface architecture as ULS-Heli-G2, with the addition of tether-compatible mechanical design.

Transmitter to Control PC Interface (External Sensors)

The transmitter can be connected to a control PC or external equipment for configuration, status monitoring, and data exchange.

Data Types

  • Status information
  • Control signals
  • Transmitter configuration
  • External IMU/COMPASS data

Connection Types

  • CAN Bus - For network communication
  • USB - For configuration and firmware updates
  • RS422 - For serial communication with external sensors

Transmitter Pinout

10 pin connector
PinFunction
1Vin +18V – +28V
2RS422A
3RS422B
4RS422Y
5RS422Z
6CAN-L
7CAN-H
8USB-D-
9USB-D+
10GND

Table: Transmitter 10 Pin Connector Pinout

Please DO NOT "HOT-PLUG" Transmitter cable. Apply power on transmitter only when connector connected to transmitter. Please check pin numbers on connector. Incorrect wiring or connection under voltage can damage the device and USB interface of connected PC !

Tethered System Note: When routing tether cable through the center hole, ensure the cable does not interfere with connector access or IR emission pattern.

Transmitter to Receiver Interface

The transmitter and receiver use an optical interface to exchange data. Transmission uses IR emission at 940 nanometers. Data transmission is only in the direction from the transmitter to the receiver.

Optical Range and Performance

ParameterULS-XSpotULS-Heli-G2Notes
Maximum Range50m50mSame range
Working Angle60°60°Emission cone
TechnologyStandard IRIR + DACSSimplified for tethered use
Update Rate20Hz20HzSame performance

Table: Optical Interface Comparison

Data Types

  • Position encoded
  • Status encoded data (Transmitter orientation and instructions)

Connection Type

  • Optical IR 940nm - Infrared optical link

Tethered Operation: The 50-meter range covers typical tethered drone operating heights. Tether provides stable reference, reducing positioning complexity compared to free-flight applications.

Receiver to Autopilot and Receiver to PC Interfaces

Data Types

  • MAVLink messages
  • ULS-Blitz frames
  • ASCII protocol

Connection Types

  • UART - Serial communication with autopilot
  • CAN - Network communication
  • USB - Direct PC connection

Receiver Pinout

Receiver pin connectors
PinFunction
1Vin (+5V)
2CANH
3CANL
4GND

Table: 4 Pin Connector Pinout

PinFunction
1Vin (+5V)
2CANH
3CANL
4UART_TX (OUT)
5UART_RX(IN)
6USB_D-
7USB_D+
8GND

Table: 8 Pin Connector Pinout

Powering Interfaces

Powering Interfaces

Figure: Power Distribution and Connections

Transmitter Electrical Characteristics

ParameterValueUnitNotes
Supply Voltage22.0 - 26.0VNominal 24V
Supply Current4APeak
Power Consumption18.1WTypical

Table: Transmitter Electrical Specifications Tethered System Power: Transmitter can be continuously powered from ground station power supply. Consider tether voltage drop when sizing power system for long tether runs.

Receiver Electrical Characteristics

ParameterValueUnitNotes
Supply Voltage5.0VFrom flight controller or tether
Supply Current1APeak
Power Consumption3WTypical

Table: Receiver Electrical Specifications Tethered Power Option: Receiver can be powered from flight controller or directly from tether power distribution system.

Functional Diagram

Functional Diagram

Figure: Functional description of the system

Functional Interfaces

Functional Interfaces Diagram

Figure: Data Flow and Functional Interfaces

Data Exchange

The ULS-XSpot system implements several data exchange mechanisms optimized for tethered operations:

Control PC Functions:

  • Configure and view status of transmitter
  • Set configuration of receivers
  • Send control signals (On/off, compass override information)
  • Monitor tethered operation parameters

External Equipment:

  • External IMU/Compass equipment can be used to override internal IMU/compass information
  • Tether management system integration for position reference

Receiver Functions:

  • Accept data from transmitter over IR signal (position field information and ground unit IMU data)
  • Accept NED and Attitude information from autopilot to convert coordinate system
  • Multiple receivers can communicate to calculate vehicle orientation (YAW)
  • Send position offset data to autopilot
  • Support for tethered flight modes and station-keeping

Tethered System Integration

Ground Station Interface:

  • Power distribution to transmitter via ground power supply
  • Data connection for configuration and monitoring
  • Tether management system coordination

Aircraft Interface:

  • Position data from ULS-XSpot receiver to autopilot
  • Tether tension and status monitoring (external system)
  • Coordinated flight control for tethered operations

Mechanical Interfaces

ULS-XSpot Receiver Slave dimensions

Figure: Slave Receiver Mechanical Dimensions

ULS-XSpot Receiver Master dimensions

Figure: Master Receiver Mechanical Dimensions

ULS-XSpot Transmitter dimensions

Figure: Transmitter Mechanical Dimensions with Center Tether Hole

Note: The transmitter features a center hole designed for tether cable passage, enabling integration with tethered drone power and data systems.

Transmitter Mounting with Tether

The transmitter features a center hole for tether passage. Key mounting considerations:

  1. Use 16 mounting holes to secure transmitter to platform
  2. Route tether cable through center hole before mounting
  3. Ensure tether has adequate strain relief above and below transmitter
  4. Maintain 10cm minimum clearance around transmitter for IR emission
  5. Verify tether routing does not obstruct 60° emission cone

Receiver Mounting

Both master and slave receivers have mounting provisions for secure installation on tethered aircraft. 3D models of the receivers can be provided upon request.

Tethered Aircraft Considerations:

  • Position receivers to avoid tether shadow/obstruction
  • Consider tether dynamics in receiver placement
  • Maintain clear line-of-sight to ground transmitter

Communication Protocols

Overview

The protocol used by devices for configuration is proprietary and is described in other documents. However, the protocol implements the possibility of transmitting messages (Blitz messages) that can be used by the user to control the device and obtain information. These messages are universal, and the format describes the data that is transmitted by various devices in our system connected to a single network.

Use CMD=6 to send Blitz messages.

In this document, the CAN protocol is specified. RS485 is used to implement custom protocols that can be defined in the future.

CAN Bus Protocol Frame Format

flowchart LR
  A[Sender Device] --> B[GLOBAL]
  B --> C[CMD = 6]
  C --> D[ID]
  D --> E[dsn_lid]
  E --> F[msg_id]
  F --> G[Blitz Payload data <= 8 bytes]
  G --> H[Receiver Device]

The CAN protocol uses the following frame structure:

FieldDescription
GLOBALFlag used to send packets over several local networks
CMDCommand field (Use CMD=6 to send Blitz messages)
IDPacket sender ID (local id src_lid for local packets and device id for global packets src_did)
dsn_lidDestination local ID address
msg_idMessage ID used to identify Blitz packet types

Table: CAN Protocol Frame Fields

Status Bit Definitions

Most messages include a status byte with the following bit definitions:

BitFlagDescription
0ULS_STATUS_RX_CARRIER_OKIR signal detected
1ULS_STATUS_RX_SQ_OKSignal quality OK
2ULS_STATUS_RX_POS_OKPosition estimated
3ULS_STATUS_RX_VEL_OKVelocity estimated
4ULS_STATUS_RX_GU_IMU_OKGround Unit IMU OK
5ULS_STATUS_RX_MRX_OKMRX message received (secondary receiver)
6ULS_STATUS_RX_MRXDATA_OKMRX Yaw and Distance calculated OK

Table: Status Bit Definitions

Common Data Structure

Blitz Common Data Structure

Structure: __blitz_common_data_struct

FieldTypeDescription
src_liduint8_tSource logical ID
msg_iduint16_tMessage ID (see message types below)
dataunionMessage-specific data (8 bytes max)

Table: Blitz Common Data Structure The union contains all possible message structures:

  • xcg1_rx_raw_measurmet
  • rx_raw_measurmet
  • rx_pos_in_tx_frame
  • rx_mrx
  • rx_dacs

Usage: Universal container for all ULS Blitz message types.

Implementation Notes

  1. Packed Structures: All structures use __attribute__((packed)) to ensure no padding bytes are added by the compiler.
  2. Endianness: The protocol assumes little-endian byte order for multi-byte fields.
  3. Angular Precision: Angular measurements use 16-bit signed integers with specific scaling factors for different ranges.
  4. Distance Units: Distance measurements may use different units (cm, 10cm increments) depending on the message type.

Message Types

XCG1 Raw Measurement (0x0010)

Message ID: ULS_BLITZ_MSG_ID_XCG1_RX_RAW_MEASURMENT (0x0010)

Structure: __uls_blitz_xcg1_rx_raw_measurmet

FieldTypeDescription
statusuint8_tStatus bits (see Status Bit Definitions above)
duint8_tDistance in 10 cm increments
aXint16_tAngular information X-axis, proportional [-30000 = -30°, +30000 = +30°]
aYint16_tAngular information Y-axis, proportional [-30000 = -30°, +30000 = +30°]
oFint8_tSensor offset Forward in cm
oRint8_tSensor offset Right in cm

Table: XCG1 Raw Measurement Message Format Purpose: Legacy raw measurement data for XCG1 systems with limited angular range.

Raw Measurement (0x0011)

Message ID: ULS_BLITZ_MSG_ID_RX_RAW_MEASURMENT (0x0011)

Structure: __uls_blitz_msg_rx_raw_measurmet

FieldTypeDescription
statusuint8_tStatus bits (see Status Bit Definitions above)
counteruint8_tMessage counter for tracking
aXint16_tAngular information X-axis [-180° to +180°]
aYint16_tAngular information Y-axis [-180° to +180°]
distanceuint16_tDistance measurement

Table: Raw Measurement Message Format Angular Conversion Formula:

degrees = (value_int16 * 180.0f) / 32767.0f

Purpose: Standard raw measurement data with full angular range.

Position in TX Frame (0x0012)

Message ID: ULS_BLITZ_MSG_ID_RX_POS_IN_TX_FRAME (0x0012)

Structure: __uls_blitz_msg_rx_pos_in_tx_frame

FieldTypeDescription
statusuint8_tStatus bits (see Status Bit Definitions above)
counteruint8_tMessage counter for tracking
posXint16_tPosition X-coordinate in transmitter frame (cm)
posYint16_tPosition Y-coordinate in transmitter frame (cm)
posZint16_tPosition Z-coordinate in transmitter frame (cm)

Table: Position in TX Frame Message Format Purpose: 3D position data relative to the transmitter coordinate system.

MRX Information (0x0013)

Message ID: ULS_BLITZ_MSG_ID_RX_MRX (0x0013)

Structure: __uls_blitz_msg_rx_mrx

FieldTypeDescription
statusuint8_tStatus bits (see Status Bit Definitions above)
counteruint8_tMessage counter for tracking
yawint16_tYaw angle [-180° to +180°]
distanceuint16_tDistance measurement in cm

Table: MRX Information Message Format Purpose: Multi-receiver (MRX) information for secondary receiver data.

DACS Information (0x0014)

Message ID: ULS_BLITZ_MSG_ID_RX_DACS (0x0014)

Structure: __uls_blitz_msg_rx_dacs

FieldTypeDescription
statusuint8_tStatus bits (see Status Bit Definitions above)
counteruint8_tMessage counter for tracking
yawint16_tYaw angle [-180° to +180°]
distanceuint16_tDistance measurement
yawContinuousint16_tContinuous yaw angle ±32768°

Table: DACS Information Message Format Purpose: DACS (Distance and Azimuth Correction System) data with continuous yaw tracking. Available on VTOL systems only.

Ground IMU Measurement (0x0020)

Message ID: ULS_BLITZ_MSG_ID_GIMU_MEASUREMENT (0x0020)

Structure: __uls_blitz_msg_gimu_data

FieldTypeDescription
statusuint8_tStatus bits (see Status Bit Definitions above)
counteruint8_tMessage counter for tracking
rollint16_tRoll angle [-180° to +180°]
pitchint16_tPitch angle [-180° to +180°]
yawint16_tYaw angle [-180° to +180°]

Table: Ground IMU Measurement Message Format Angular Conversion Formula:

degrees = (value_int16 * 180.0f) / 32767.0f

Purpose: Ground unit IMU (Inertial Measurement Unit) orientation data.

IMU Override (0x0030)

Message ID: ULS_BLITZ_MSG_ID_XX_TXC_IMU_OVERRIDE (0x0030)

Structure: __uls_blitz_msg_xx_txc_imu_override

FieldTypeDescription
controluint8_tControl bits (see Control Bits below)
counteruint8_tMessage counter for tracking
rollint16_tOverride roll angle [-180° to +180°]
pitchint16_tOverride pitch angle [-180° to +180°]
yawint16_tOverride yaw angle [-180° to +180°]

Table: IMU Override Message Format Control Bits:

BitDescription
0SET Roll - Enable roll angle override
1SET Pitch - Enable pitch angle override
2SET Yaw - Enable yaw angle override
3-7Reserved

Table: IMU Override Control Bits Angular Conversion Formula:

degrees = (value_int16 * 180.0f) / 32767.0f

Purpose: Override IMU data on ground unit for external orientation control.

Magnetometer Override (0x0031)

Message ID: ULS_BLITZ_MSG_ID_XX_TXC_MAG_OVERRIDE (0x0031)

Structure: __uls_blitz_msg_xx_txc_mag_override

FieldTypeDescription
controluint8_tControl bits (see Control Bits below)
counteruint8_tMessage counter for tracking
mxint16_tMagnetic field X-component
myint16_tMagnetic field Y-component
mzint16_tMagnetic field Z-component

Table: Magnetometer Override Message Format Control Bits:

BitDescription
0SET override - Enable magnetometer override
1-7Reserved

Table: Magnetometer Override Control Bits Magnetic Field Conversion Formula:

mag_value = (value_int16 * 1.0f) / 32767.0f

Purpose: Override magnetometer data on ground unit for external compass control.

Tethered System Note: CAN bus protocol can be extended over tether for ground station integration if required.

Environmental Conditions - Industrial Grade

Equipment is designed to operate reliably in demanding environmental conditions typical of aerospace, industrial automation, and outdoor applications.

Operating Temperature Range

  • Standard operating range: -20°C to +55°C
  • Covers most industrial and outdoor applications
  • Reliable performance across temperature extremes
  • No performance degradation within specified range

Humidity Tolerance

  • Relative humidity: Up to 70% (non-condensing)
  • Protected against moisture in typical operating conditions
  • Suitable for outdoor and semi-protected installations
  • Condensation prevention through sealed design

Ingress Protection

  • IP67 rated (Dust tight and water immersion resistant)
    • 6 - Complete protection against dust ingress
    • 7 - Protected against temporary immersion in water (up to 1 meter depth for 30 minutes)
  • Suitable for harsh industrial environments
  • Protected against rain, splashing, and temporary submersion
  • Dust-tight sealing for contaminated environments

Storage Conditions

  • Storage temperature: -40°C to +70°C
  • Relative humidity: Up to 95% (non-condensing)
  • Long-term storage in industrial facilities

Operational Environment Standards

  • Designed to meet industrial equipment requirements
  • Suitable for UAV/drone applications
  • Outdoor installation capable
  • Protected against:
    • Dust and particulate matter
    • Water spray and rain
    • Temporary water immersion
    • Temperature fluctuations
    • High humidity

Part Numbering

Part NumberDescription
ULS-XSPOTSystem set with 3 receivers for tethered drone systems.
ULSDV-XS-TXTransmitter unit with center tether hole.
ULSDV-XS-RXMMaster receiver unit.
ULSDV-XS-RXSSlave receiver unit.
SA610/P4IB4 Pin Connector for receiver. Manufacturer Weipu.
SA810/P8IIB8 Pin Connector for receiver. Manufacturer Weipu.
SA1610/P10IIB-110 Pin Connector for transmitter. Manufacturer Weipu.

Table: Part Numbering

Tethered System Specific Interfaces

Tether Cable Specifications

Recommended tether cable specifications for integration with ULS-XSpot:

ParameterSpecificationNotes
Center Hole Diameter20-50mmAccommodates various tether sizes
Cable ClearanceMinimum 10mmAround IR emission area
Strain ReliefRequiredBoth ends of transmitter
Cable WeightConsideredDoes not affect IR transmission

Table: Tether Integration Specifications

Ground Station Integration

The ULS-XSpot transmitter should be integrated with the ground station tether management system:

  1. Power Connection: 24V DC supply from ground station
  2. Data Connection: USB or CAN for configuration/monitoring
  3. Mechanical Integration: Mounted at tether launch/recovery point
  4. Cable Management: Integrated with tether handling system

Safety Considerations

  • Tether provides physical backup to optical positioning
  • Loss of optical signal does not mean loss of tether connection
  • Emergency procedures should account for tether recovery
  • Regular inspection of tether routing through transmitter