UAV Systems | VECTIS R Relay M2
VECTIS R Relay M2 – octocopter for increased relay payload margin
Coaxial octocopter platform for tactical relay, radio, datalink and network tasks with increased payload margin.
VECTIS R Relay M2 is designed as a tactical relay UAV for mission profiles where communication hardware, radio modules, antennas, datalink components and project-specific system equipment require more payload margin than a standard VECTIS relay configuration.
The platform is based on the VECTIS / Kite 75 system architecture and uses four arms with an upper and lower motor on each arm. The coaxial layout provides additional propulsion and payload reserves for relay configurations with MANET/mesh radio, IP-based system integration and mission-specific communication hardware.
The primary focus is the relay and datalink function. Optionally, a compact detachable EO/IR situational-awareness camera with quick release can be added, for example for local area awareness or visual support during system positioning, while the platform remains primarily configured for heavy relay payloads.
Tether operation can be engineered on a project-specific basis. Due to the lower propellers and the different landing gear and landing geometry, VECTIS R Relay M2 is not treated as a standard configuration for the existing TELEVATOR / landering architecture.
Relay Configuration | Radio, Datalink & IP Network
Relay hardware, datalink and network function
VECTIS R Relay M2 is intended for tactical communication and datalink applications where radio modules, antennas, network components, mission computer and power architecture must be combined into an airborne relay platform.
The coaxial octocopter configuration provides payload and integration margin for more demanding relay setups. This allows multiple antennas, IP-capable radio systems, buffer battery, cabling, mounts and project-specific system integration to be evaluated together.
Relay and radio payloads
Depending on project requirements, VECTIS R Relay M2 can be configured for MANET/mesh datalinks, tactical IP radio networks, video and telemetry transmission, range extension or elevated communication nodes. The specific radio and datalink hardware depends on frequency range, operating range, encryption, antenna geometry and integration into existing C2 or network structures.
IP-based system architecture
The relay configuration can be integrated into an IP-based system architecture. This allows video, telemetry, control data, network connectivity and mission-specific data streams to be routed through suitable datalinks and ground systems.
Optional situational-awareness camera
Optionally, a compact detachable EO/IR situational-awareness camera with quick release can be added. This camera is not intended as the primary recon payload, but for situational and system monitoring or supplementary observation during relay operation.
Technical Data | Relay Configuration
Technical key data VECTIS R Relay M2
The technical key data of VECTIS R Relay M2 depend on relay hardware, antenna geometry, mission computer, power supply, datalink, optional EO/IR situational-awareness camera and operating mode. The following values describe a realistic working configuration for tactical relay and datalink applications.
| Platform class | coaxial octocopter variant of the VECTIS M2 system architecture |
|---|---|
| Configuration | four arms, each with one upper and one lower motor/propeller |
| Wheelbase | approx. 1,000 mm |
| MTOW class | up to approx. 12 kg, depending on relay payload, battery setup, antennas, datalink and operational reserves |
| Empty weight | approx. 5.2 kg as a technical working assumption without mission-specific payload |
| Battery configuration | typically 2× 17,000 mAh 6S semi-solid batteries, approx. 3 kg combined |
| Propulsion class | 6S propulsion with motors in the 20–22" propeller class, depending on configuration |
| Propellers | 22" preferred for higher efficiency and payload margin; 20" as a more compact and robust alternative |
| Coaxial layout | coaxial arrangement with conservatively accounted downwash and interference losses; the technical layout is calculated with roughly 15 % reserve deduction |
| Relay payload | radio modules, datalink hardware, antennas, network components, mission computer and mounts can be configured on a project-specific basis |
| Mission payload on battery | up to approx. 3.5–4.0 kg depending on configuration with reduced flight time; 5 kg is not specified as a standard value for battery-powered operation |
| Optional camera | compact detachable EO/IR situational-awareness camera with quick release possible |
| Flight time, light relay configuration | operationally above 30 minutes with low additional payload and suitable battery configuration |
| Flight time, medium relay configuration | approx. 24–30 minutes, depending on radio hardware, antennas, mission computer and reserves |
| Flight time, high relay configuration | approx. 20–25 minutes with high mission payload, depending on configuration |
| Tether operation | possible depending on configuration; not intended for the existing TELEVATOR / landering architecture |
| Mission computer | project-specific mission computer configuration, e.g. with 256-GB SSD, video and data processing, IP streaming, recording and a container-capable software environment |
| System integration | IP-based architecture for video, telemetry, control data, network services and mission-specific data streams |
Relay configurations are not assessed solely by the weight of individual radio modules. The decisive factors are the complete system integration of antennas, cabling, mounts, power demand, thermal reserve, datalink architecture and required operating duration.
Tether Operation | Relay Height & Payload Margin
Tether operation for elevated relay positions
VECTIS R Relay M2 can be engineered as a project-specific tethered relay configuration. For relay applications, this is particularly relevant when radio and datalink hardware must be operated for extended periods from an elevated position.
In tether operation, the usable mission payload is defined by the complete tethered system. In addition to relay hardware and antennas, tether cable, tether interface, buffer battery, mission computer, mounts, cabling, integration reserve as well as wind and side-load effects must be considered.
A higher tether position can improve radio and datalink coverage, but it also reduces the realistically available payload margin. Cable weight, tether angle, wind load and thermal operating reserves are therefore evaluated together with the required relay height.
| Tether height | realistic relay mission payload with wind reserve | Classification for VECTIS R Relay M2 |
|---|---|---|
| approx. 50–60 m | approx. 2.2–2.5 kg | suitable for heavier relay hardware, antennas and mission computer configurations |
| approx. 75 m | approx. 1.8–2.0 kg | suitable for medium relay payloads with good height reserve, wind-dependent |
| approx. 100 m | approx. 1.0–1.3 kg | suitable for more compact relay configurations or lighter communication modules |
Relay configurations above approx. 2.5 kg mission payload are not specified as a standard configuration for tether operation. Such setups must be evaluated on a project-specific basis, considering wind load, tether angle, power demand, antenna geometry, center of gravity and thermal reserves.
Due to its lower propellers and different landing gear and landing geometry, VECTIS R Relay M2 is not intended for the existing TELEVATOR / landering architecture. Tether operation is therefore treated as an independent, configuration-dependent system setup.
Project Request | VECTIS R Relay M2
Configure VECTIS R Relay M2 for relay and datalink applications
VECTIS R Relay M2 is intended for projects that require radio modules, antennas, datalink hardware, mission computers and project-specific communication or network components to be integrated into an airborne relay platform. The final configuration depends on payload, antenna geometry, power demand, battery-powered or tethered operation, operating height and required endurance.
For a robust relay configuration, we evaluate relay hardware, datalink architecture, power supply, IP connectivity, ground system, flight-time reserve, tether operation and integration effort together with the project requirements.