VEKTOR Autopilot (for INAV/ArduPilot)
SKU: 1551
The use of this product, parts of it, certain software/hardware combinations, unsupervised use, may not be permitted in your country! Compliance to local laws is solely the responsibility of the user! This product is shipped without firmware; the user must install the firmware themselves and assumes full responsibility for doing so. The warranty and support applies exclusively to the hardware (printed circuit board and components) and does not cover any software-related issues.
Peripherals
GNSS: We recommend using UBlox M10 modules or newer.
RX: This module only works with digital serial protocols. Therefore only RX modules with SBUS, IBUS or CRSF (ELRS), SUMD. Consider using ELRS when building a new system.
HoTT telemetry is also activated and supported.
Check the list of supported RX systems for ArduPilot and iNav.
For new builds, we recommend using a 7.2V or 8.4V architecture for the BEC, servos, and other peripherals. A higher voltage architecture provides several advantages, including improved stability, better performance, and a higher current capacity.
Power
For Current/Voltage sensing: A power module is needed, consult the power modules page for more information.
Current sensing via power module requires calibration from the user.
5V peripheral power is supplied when BEC power is connected to any of the PWM ports.
Use with VEKTOR Core
Also see the comparison page VEKTOR Core/Autopilot.
The VEKTOR Autopilot functions as a HAT (Hardware Attached on Top) on the VEKTOR Core, allowing the two modules to interconnect the power pins. The Autopilot can be configured to send MAVLink or SBUS signals through the HAT port to the VEKTOR Core, enabling it to control complex propulsion systems and eliminating the need for a dedicated RX.
This integration enables the direct transmission of autopilot signals, such as AHRS, GPS data and automated throttle and steering, to the VEKTOR Core.
Other specific signals, such as switches, that need to be transmitted to the VEKTOR Core must be configured as passthrough signals in the Autopilot configuration software.
Wiring example
Wire colors may change, RX connects to TX and viceversa.
The Autopilot only supports receivers that output a serial signal like IBUS, SBUS, SUMD, ELRS..
The easiest and most reliable way is to connect an ELRS serial receiver.
For complex wiring also look up the common power and signal rails.
Receivers with many PWM ports and a serial output can be used togheter with the Autopilot. A careful channel mapping on the transmitter is necessary. It is then possible to combine the serial signal to the Autopilot and use the remaining PWM ports on the receiver.
For short distance applications we recommend FlySky iA6B and iA10 receivers, which have PWM outputs and a serial output.
This is also doable with some Graupner HoTT receivers.
- 100% INAV/ArduPilot compatible architecture
-Waypoint navigation
-Mission planning - ARM Cortex-M4 @ 168MHz
- Bosch Sensortec BMI088 High-precision, industrial-grade IMU
- RCIN port with activable RX hardware inverter
- 6x PWM output channels (JR connectors and solder pads)
16x SBUS output channels - Sonar port
- MicroSD slot to store mission data, logs and blackbox data
- Multifunction port for voltage/current sensing
- Raspberry Pi Zero formfactor (85x30mm)
- Compatible with VEKTOR Core, Raspberry Pi or standalone mode
- USB-C programming/configuration interface
- (5*) 6-9V input voltage from PWM pin header
- Can also be powered from USB-C or Power module port (via solder bridge).
- Possible MAVLink interconnect with Nvidia Jetson or Raspberry Pi over 40pin header (activated via solder bridge).
- 7pin connector with high current passthrough and UART port for SBUS input, as HAT on the VEKTOR Core
- Gold-plated contacts
- Vibration resistant JST-GH connectors
- Automotive grade ESD protection up to 15kV
- EMI Filtered ports
* 5V are also supported but some older RX and GPS peripherals may not work correctly. Modern peripherals (2020+) should be compatible.
Suited for:
- Commercial USV, Rovers, Drones, Robots
- Academia, schools, research
Variant with barometer available.
Also available with encrypted datalink. Contact us for further details.
Regulatory compliance has to be obtained by the system integrator/OEM.
This product is RoHS compliant.
This product is not an independently functional unit and DOES REQUIRE professional installation and configuration.
This product requires a complex configuration process with a prior use case planning, and is not plug-and-play by any means.
* The appearance and design of the board are subject to changes. The functionality and size always remain unchanged.
Upon request, we provide a variant of this product with potting (plastic, resin).