Deterministic Control
Sensor-redundant flight control with triple IMUs, dedicated compass, and centimeter-level barometer for precise, reliable attitude and heading reference.
SkyPulse Helios FMU
SkyPulse Helios एक इंटीग्रेटेड एवियोनिक्स और कंप्यूट स्टैक है, जिसे अगली पीढ़ी के मानवरहित सिस्टम के लिए इंजीनियर किया गया है।
P/N SP-HEL-4G
- ट्रिपल रिडंडेंट IMUs (इंडस्ट्रियल ग्रेड), बेहद कम ड्रिफ़्ट के साथ
- 6–36 V डायरेक्ट इनपुट, बाहरी हार्डवेयर की ज़रूरत नहीं
- ArduPilot और PX4 के साथ पूरी तरह से संगत - कस्टम बिल्ड सहित
- 100% NDAA अनुरूप
- नेविगेशन, डिटेक्शन और कस्टम एल्गोरिदम के लिए Linux चलाने वाला ऑनबोर्ड कंपैनियन कंप्यूटर
- Regular price
- $850.00 USD
- Sale price
- $850.00 USD
- Regular price
-
SkyPulse
SkyPulse Helios FMU- Regular price
- $850.00 USD
- Sale price
- $850.00 USD
- Regular price
-
100% NDAA अनुरूप हार्डवेयर
Questions? Email an engineer
Last updated
SkyPulse Helios FMU: key capabilities
संख्याएँ जो मायने रखती हैं
94 ग्राम
द्रव्यमान
6–36 V
इनपुट
~12 W
पूरा भार
फ़र्मवेयर
निष्क्रिय शीतलन
थर्मल
NDAA अनुरूप
विनिर्माण
Onboard Compute
Raspberry Pi Compute Module 5 companion computer with 4x Cortex-A76 cores, up to 8 GB RAM, and Debian Bookworm for real onboard AI and autonomy workloads.
Rugged Thermal Design
Passive cooling and a low-SWaP-C architecture engineered for sustained operation in harsh vibration and temperature environments.
Open Integration
Native ArduPilot and PX4 support, 6 UARTs, 2 CAN buses, 3 I2C ports, PCIe expansion, and open firmware for custom builds.
One board where a conventional stack needs three.
Helios is an integrated flight controller and companion computer in a single thermally managed unit, accepting battery voltage directly. The comparison below is against a conventional multi-board architecture, not against any specific product.
Conventional stack
- Pixhawk-class flight controller
- Separate companion computer
- DC-DC power converter
- Interconnect harness between all three
Helios
- Flight controller and companion compute on one unit
- 6–36 V accepted directly at J5
- One documented connector set
पूर्ण दस्तावेज़ीकरण
SkyPulse Helios FMU: संपूर्ण संदर्भ
Overview
Flight control and companion compute, unified.
Helios combines a sensor-redundant flight controller with a Raspberry Pi Compute Module 5 companion computer in a single integrated module. Triple IMUs, a dedicated compass, and centimeter-level barometric sensing feed deterministic control, while the onboard CM5 runs Debian Bookworm with PCIe expansion for AI accelerators. Native ArduPilot and PX4 support keeps the platform open and field-proven across hundreds of flight hours.
SkyPulse Helios एक इंटीग्रेटेड एवियोनिक्स और कंप्यूट स्टैक है, जिसे अगली पीढ़ी के मानवरहित सिस्टम के लिए इंजीनियर किया गया है।
Specifications
Flight Control & Sensors
| Main IMU | Low drift, high accuracy in harsh vibration environments |
|---|---|
| Secondary IMU | High vibration rejection, strong temperature stability |
| Third IMU | 6-DOF industrial, extended temperature range |
| Compass | Dedicated compass; accurate heading, extremely low drift |
| Barometer | 1x onboard barometer with centimeter-level accuracy |
| Motor Outputs | 8 outputs (DSHOT, PWM, OneShot, Relay — protocols can be mixed and matched) |
| RC Input | ELRS, CrossFire, SBUS, FrSky |
| CAN Ports | 2 CAN bus ports, redundant |
| I2C Ports | 3 I2C ports on separate buses |
| UARTs | 6 UARTs |
| Safety Switch | Safety-switch input |
| Logging / Status | Micro-SD slot, buzzer, RGB status LED, FRAM for parameters and mission waypoints |
Companion Compute
| Companion Computer | Raspberry Pi Compute Module 5 (eMMC variant) |
|---|---|
| Operating System | Debian Bookworm (clean image) |
| CPU | 4x Arm Cortex-A76 @ 2.4 GHz |
| RAM | 4 GB or 8 GB |
| Storage | 32 GB or 64 GB onboard eMMC |
| Wireless | Wi-Fi + Bluetooth |
| USB | 1x USB 2.0; 2x USB 3.0 |
| MIPI CSI-2 | 2x MIPI CSI-2 camera interfaces, 4 lanes each |
| IP Camera Protocol | RTSP |
| Ethernet | 1x Gigabit Ethernet |
| Video Output | micro-HDMI output, analog video output |
| PCIe | PCIe for AI accelerators, SDRs, storage, expansion |
| GPIO | GPIOs for servos, actuators, custom I/O |
| Companion UART | CM_RX/CM_TX (ttyAMA0) to flight controller UART4/SERIAL3; J4 pin 24 (CM_RX), pin 26 (CM_TX) |
Interfaces & I/O
| Connector Family (FMU) | Molex Pico-Clasp 501189-3010 |
|---|---|
| Power Connector (J5) | 2-pin Molex Nano-Fit locking (45130-0201); Pin 1 = VIN, Pin 2 = GND J5 polarity must be verified before power-up; reverse polarity damages the unit. |
| J1 / J2 (FMU1 / FMU2) | Flight-controller interfaces: telemetry radios, sensors, ESCs, RC, CAN, I2C |
| J3 (Interface) | Companion: Ethernet, USB cameras, AI accelerators, PCIe |
| J4 (GPIO) | Companion: GPIO, USB, UART, secondary 5 V / 3.3 V outputs |
| BATT_VOLT / BATT_CURR | Analog voltage and current sensing inputs BATT_VOLT and BATT_CURR are sensing inputs only; connecting more than 3.3 V can significantly damage the unit. |
| J3 VIN Pins (25, 28) | Direct battery VIN, unprotected outputs J3 pins 25 and 28 are direct battery VIN, unprotected outputs — must NOT be used to power Helios. |
Serial port mapping
| UART | ArduPilot Serial | PX4 Serial | Recommended Function | Flow Control |
|---|---|---|---|---|
| UART2 | Serial 1 | TEL1 (ttyS0) | Main Telemetry | Yes |
| UART3 | Serial 2 | GPS1 (ttyS1) | GPS Module | Yes |
| UART4 | Serial 3 | TEL2 (ttyS2) | Helios companion computer | No |
| UART6 | Serial 4 | TEL3 (ttyS3) | Secondary Telemetry / Payload | Yes |
| UART7 | Serial 5 | TEL4 (ttyS4) | ESC Telemetry / Debug | No |
| UART8 | Serial 6 | RC in (ttyS5) | RC Receiver | No |
Power, Thermal & Firmware
| Input Voltage | 6–36 V |
|---|---|
| Max Input | 36 V |
| Battery | 2–6S |
| Power Draw (Full Load) | ~12 W |
| Power Draw (Moderate) | ~7 W |
| Power Draw (Idle) | 2.7 W |
| Recommended BEC | >20 W for headroom Required for systems above 36 V. |
| Thermal | Passive cooling; low-SWaP-C design for sustained operation |
| Weight | 94 g |
| Firmware Support | ArduPilot, PX4, custom builds |
| Default Firmware | ArduCopter (PX4 flashable via USB) |
| Compliance | 100% NDAA compliant, built on high-quality non-Chinese components. |
| Communications Tested | ELRS, CrossFire, DTC, MicroHard, Siyi, FrSky, Futaba, RFD900x, Silvus, Doodle Labs, fiber optics Validated over hundreds of flight hours. |
Interfaces & pinout
Every connector is documented: designator, type, function and mating part number. J5 carries power, J1/J2 the flight-controller interfaces, J3 the companion-computer interfaces and J4 the additional GPIO.
Flight-controller I/O
6 UARTs, 2 CAN bus ports, 3 I2C ports on separate buses and 8 motor outputs supporting DSHOT, PWM and OneShot — protocols may be mixed. RC input covers ELRS, CrossFire, SBUS and FrSky.
Companion-computer I/O
1x USB 2.0, 2x USB 3.0, 2x MIPI CSI-2 and Gigabit Ethernet, plus micro-HDMI and analog video out. PCIe is available for AI accelerators, SDRs and storage.
Documented mating parts
J5 power is a 2-pin Molex Nano-Fit 45130-0201. The FMU and interface connector family is Molex Pico-Clasp 501189-3010. Order the matching harness without guessing.
Pinout drawing is being prepared for publication. Contact engineering for the current revision.
Software & firmware
Production ArduPilot and PX4 on a standard toolchain — no vendor SDK licence required. The companion computer runs a clean Debian Bookworm image.
- ArduPilot Supported Helios ships with ArduCopter by default.
- PX4 Supported Can be flashed via USB.
- Custom builds Supported Custom firmware builds are described as supported in the documentation set.
- ROS / TensorFlow / OpenCV Supported Run on the companion computer alongside the SkyPulse software stack.
Compliance & export
100% NDAA अनुरूप, उच्च गुणवत्ता वाले गैर-चीनी कंपोनेंट्स से निर्मित।
शिपिंग और अनुपालन पृष्ठ पर मूल देश, सीमा शुल्क वर्गीकरण और निर्यात स्थिति बताई गई है।
Downloads
All documents are public. No email, no account.
Known limitations
- Direct 8S connection requires external protection
- For systems up to 6S, direct battery connection is typical. Direct 8S connection requires an external filter or protection circuit because of inductive motor spikes.
- 36 V is the documented maximum input
- Above 36 V, use a BEC with adequate current capacity. Because Helios can draw approximately 12 W at full load, the documentation recommends a BEC capable of delivering more than 20 W to preserve headroom.
- J5 polarity is not reverse-protected
- Reversing J5 polarity will damage the unit. Verify polarity before every power-up.
FAQ
What firmware does Helios support?
Helios fully supports ArduPilot and PX4. Custom firmware builds are also supported. Helios FMUs ship with ArduCopter by default; PX4 can be flashed via USB.
What companion computer does Helios use?
Helios integrates a Raspberry Pi Compute Module 5 (eMMC variant) running a clean Debian Bookworm image, with 4x Arm Cortex-A76 cores at 2.4 GHz, up to 8 GB RAM, and up to 64 GB onboard eMMC.
Can I run AI workloads on Helios?
Yes. The companion computer supports TensorFlow, OpenCV, ROS, and other applications from the SkyPulse software stack, and PCIe on the J3 Interface connector is available for AI accelerators.
How do I power Helios?
Helios accepts up to 36 V via the J5 Molex Nano-Fit connector. Direct battery connection is typical for systems up to 6S. For direct 8S, an external filter or protection circuit is required due to inductive motor spikes. For systems above 36 V, use a BEC capable of delivering more than 20 W. Always verify J5 polarity before power-up — reversing polarity will damage the unit.
What connectors does Helios use?
J5 is a 2-pin Molex Nano-Fit locking connector (45130-0201) for power. J1/FMU1 and J2/FMU2 use Molex Pico-Clasp 501189-3010 connectors for flight-controller interfaces. J3 provides companion-computer interface signals (Ethernet, USB, PCIe), and J4 exposes additional GPIO, USB, and UART signals.
Is Helios NDAA compliant?
Yes. 100% NDAA compliant, built on high-quality non-Chinese components.
Questions about integration? किसी इंजीनियर को ईमेल करें.
दस्तावेज़ों से
कंपैनियन कंप्यूटर के साथ शुरुआत
कंपैनियन कंप्यूटर डिफ़ॉल्ट रूप से Debian 12 (Bookworm) चलाता है। पहला कनेक्शन Ethernet पर होता है; उसके बाद आप अपने Wi-Fi क्रेडेंशियल जोड़कर वायरलेस तरीके से SSH कर सकते हैं।
-
कनेक्ट करें और पावर अप करें
दिए गए Ethernet एडैप्टर को Interface कनेक्टर से जोड़ें, फिर यूनिट को पावर अप करें।
-
सबनेट से जुड़ें
अपने कंप्यूटर को 192.168.168.X नेटवर्क पर एक स्टैटिक IPv4 पता दें। Helios 192.168.168.33 पर जवाब देता है।
-
कंपैनियन कंप्यूटर में SSH करें
डिफ़ॉल्ट क्रेडेंशियल प्रारंभ करने वाली मार्गदर्शिका में सूचीबद्ध हैं।
ssh skypulse@192.168.168.33 -
फ़्लाइट-कंट्रोलर लिंक जाँचें
फ़्लाइट कंट्रोलर SERIAL3 (UART4) पर कंप्यूटर से बात करता है, जो /dev/ttyAMA0 के रूप में दिखता है। SERIAL3_PROTOCOL को MAVLink2 और SERIAL3_BAUD को 921600 पर सेट करें, PySerial, PyMavlink, MAVProxy और Future इंस्टॉल करें, फिर चलाएँ:
MAV> Detected vehicle 1:1 on link 0~/.local/bin/mavproxy.py --master=/dev/ttyAMA0 --baudrate=921600
डिफ़ॉल्ट पोर्ट मानचित्र · ArduPilot
| UART | ArduPilot Serial | PX4 Serial | Recommended Function | Flow Control |
|---|---|---|---|---|
| UART2 | सीरियल 1 | TEL1 (ttyS0) | टेलीमेट्री 1 | Yes |
| UART3 | सीरियल 2 | GPS1 (ttyS1) | GPS पोर्ट | Yes |
| UART4 | Serial 3 | TEL2 (ttyS2) | Helios companion computer | No |
| UART6 | सीरियल 4 | TEL3 (ttyS3) | RC इनपुट | Yes |
| UART7 | सीरियल 5 | TEL4 (ttyS4) | ESC टेलीमेट्री | No |
| UART8 | Serial 6 | RC in (ttyS5) | RC Receiver | No |
| Ethernet | — | — | हाई-स्पीड लिंक | — |
| CH1–8 | — | — | PWM / DShot / रिले | — |
| I2C | — | — | सेंसर इनपुट | — |
| CAN bus | — | — | सेंसर इनपुट / IO | — |
पहली बार पावर ऑन करने से पहले सभी प्रोपेलर हटा दें। पूरा पिनआउट Helios डेटाशीट में है।
