Three items in one box: the Helios FMU, SkyNav Standard and the Breakout Board — the first SkyPulse bundle that is bring-up complete on day one.
P/N SP-KIT-01
SkyPulse
SkyPulse Evaluation Kit100% NDAA compliant hardware
Questions? Email an engineer
Last updated
Firmware
Every item in the kit is also a product in its own right, with its own specifications, interfaces and documentation. Open any of them to read the detail.
The kit includes the Breakout Board, which is the adapter the Helios getting-started procedure asks for in its opening instruction. The companion computer is reachable over SSH from the first power-up instead of after a second order.
Helios carries the flight controller and the Compute Module 5 companion computer on one unit. SkyNav Standard adds L1 + L5 multi-band positioning on the Pixhawk / Cube standard connector.
The Helios companion computer is a Raspberry Pi Compute Module 5 with four Arm Cortex-A76 cores at 2.4 GHz and a clean Debian Bookworm image, with PCIe on the J3 Interface connector for expansion.
The stack runs from a single 6–36 V input at the Helios J5 connector. No separate DC-DC converter and no extra wiring between the boards.
The comparison below is against the conventional way of assembling a first evaluation bench — a flight controller, a companion computer and a GNSS module from separate catalogues, with the bring-up adapter discovered only once the hardware is on the desk. It is not a comparison against any specific product.
Three items at one price: the Helios FMU, the SkyNav GNSS Module in its Standard configuration and the Breakout Board. The breakout board is the difference that matters. It is the adapter the Helios getting-started procedure asks for in its first instruction, so the companion computer is reachable over SSH, and flashable over USB-C, from the first power-up rather than after a second order.
Three items in one box: the Helios FMU, SkyNav Standard and the Breakout Board — the first SkyPulse bundle that is bring-up complete on day one.
| Flight control + compute | SkyPulse Helios FMU Flight controller and a Raspberry Pi Compute Module 5 companion computer on one unit. |
|---|---|
| Positioning | SkyNav GNSS Module — Standard uBlox NEO-F10N receiver, L1 + L5 multi-band, on the 6-pin JST-GH Pixhawk / Cube standard connector. |
| Bring-up | SkyPulse Breakout Board Gigabit Ethernet RJ45 and a dual-mode USB 2.0 Type-C port, broken out from the Helios Interface port. |
| First connection | Ethernet, over the Breakout Board The Helios getting-started procedure opens by connecting the ethernet adapter to the Interface connector and powering the unit. |
|---|---|
| Companion access | SSH and VNC The companion computer sits on a documented static IPv4 address, and VNC is enabled by default. |
| Image flashing | USB 2.0 Type-C in BOOT mode Slide SW1 to BOOT, wait for the status LED to turn off, then connect the USB-C port to a PC. |
| Wi-Fi | Configured after the first wired setup Wi-Fi credentials are defined once the first setup has been done over Ethernet. |
| Input Voltage | 6–36 V |
|---|---|
| Battery | 2–6S |
| Recommended BEC | >20 W for headroom Required for systems above 36 V. |
| GNSS bands | L1 + L5 multi-band |
|---|---|
| GNSS receiver | uBlox NEO-F10N The SkyNav Standard configuration. |
| Compass | Isentek IST8310 |
| Connector | 6-pin JST-GH Pixhawk / Cube standard pinout. |
| Firmware Support | ArduPilot, PX4, custom builds |
|---|---|
| Companion OS | Debian Bookworm (clean image) |
| Manufacturing | 100% NDAA compliant Built on high-quality non-Chinese components. Every module is tested before it ships. |
Every connector in the kit is documented: designator, type, function and mating part number.
6 UARTs, 2 CAN bus ports, 3 I2C ports and 8 motor outputs on the flight controller; Gigabit Ethernet, USB and PCIe on the companion computer.
The Breakout Board attaches to the Helios Interface port with a single 20-pin Molex Pico-Clasp connector and presents a Gigabit Ethernet RJ45 jack alongside a dual-mode USB 2.0 Type-C port.
J5 power is a 2-pin Molex Nano-Fit 45130-0201. The Helios connector family is Molex Pico-Clasp 501189-3010. SkyNav is 6-pin JST-GH. Order spares without guessing.
Pinout drawing is being prepared for publication. Contact engineering for the current revision.
Production open firmware on the standard toolchain — no vendor SDK licence required — and a clean Debian Bookworm image on the companion computer.
Country of origin, customs classification and export position are stated on the shipping & compliance page.
Three items: the SkyPulse Helios FMU, the SkyNav GNSS Module in its Standard configuration and the SkyPulse Breakout Board.
Because it is the first instruction in the Helios getting-started procedure: connect the ethernet adapter to the Interface connector. Without that link there is no SSH session to the companion computer and no path for flashing an image — and no route to Wi-Fi either, since Wi-Fi credentials are defined only after the first setup over Ethernet.
Yes. The Helios FMU, the SkyNav GNSS Module and the Breakout Board are each sold on their own product page, each with its own specifications, interfaces and documentation. The kit is the three of them in one order at one price.
No. The kit is a single configuration and ships with SkyNav Standard. The Pro RTK configuration, which adds the uBlox NEO-F9P receiver and RTK, is available on the SkyNav product page.
No. The stack runs from a single 6–36 V input at the Helios J5 connector. For systems above 36 V, use a BEC capable of delivering more than 20 W.
Yes. Every item in it is 100% NDAA compliant, built on high-quality non-Chinese components, and every module is tested before it ships.
Questions about integration? Email an engineer. A human who knows the board answers.
Native firmware support and compliance
100% NDAA compliant hardware
Your cart may be empty now, but let us help you fill it up with amazing products.
