Customized Betaflight
Our team modifies Betaflight to meet military mission requirements and integrates it with the Spectre FPV platform.
SPECTRE DYNAMICS · SOFTWARE ENGINEERING
FPV UAS Software Development
Spectre Dynamics develops nearly all of its FPV platform software within our own team at the Phatthalung and Trang labs. Our work spans customized Betaflight for military mission requirements, Reaper Eye integration and Control Link software, alongside the wider Flight Controller, communications, VTX/VRX and ground station stack.
PHATTHALUNG · TRANG · THAILAND
Our software. Developed in our Thailand labs.
Nearly all of the software for our FPV platforms is developed by our own team at the Phatthalung and Trang labs. This includes adapting Betaflight and building the software that connects flight control, onboard systems and ground equipment.
Reaper Eye integration
Our platform software supports integration with Reaper Eye visual systems as part of the agreed platform configuration.
Control Link software
We develop Control Link software with reduced detectability by commercially available Drone Detector systems and resilience against jammers and electronic warfare (EW) as design goals.
Control Link performance depends on the selected hardware, software configuration, operating environment and the detection or interference system involved. Evaluation criteria are defined for each project.
Software across the entire FPV UAS stack.
Develop an individual subsystem or bring the aircraft, communications, video and ground software together. Hardware compatibility, interfaces and performance requirements are defined with your team at the start of the project.
01
Communications & telemetry
Software for communication interfaces, telemetry transport and data exchange between the aircraft and ground equipment. Scope can include link monitoring, gateway integration and connection-loss handling, with behaviour evaluated for the selected hardware and operating conditions.
02
Flight Controller software
Develop and adapt Flight Controller firmware, hardware drivers, sensor interfaces, configuration tools and flight data logging. Integrate onboard subsystems and define operating states, diagnostics and failsafe behaviour against the platform requirements.
03
VTX / VRX software
Software and firmware integration for Video Transmitters (VTX) and Video Receivers (VRX), including equipment configuration, video pipeline interfaces, status monitoring and ground display applications. Video quality, latency and compatibility are assessed for the agreed equipment.
04
Custom protocols & APIs
Design project-specific protocols, message formats, APIs and adapters for control, telemetry, video metadata and equipment management. Deliver interface documentation and integration tools, with authentication, access control and version compatibility included in the agreed scope.
05
Ground software & system integration
Build ground station applications, operator interfaces, configuration utilities and diagnostic tools. Connect existing systems, support firmware update workflows and verify interactions across the FPV stack through bench, simulation and hardware integration testing.
One engineering stack. Tactical and industrial applications.
Dual-use development applies the same software engineering capabilities to institutional and civilian requirements. Define the operating environment, operator workflow and equipment constraints so the software can be scoped for the intended application.
- Tactical training, observation and field communications
- Infrastructure inspection and industrial site surveys
- Search and rescue and disaster response
- Research, platform prototyping and equipment evaluation
From project brief to software handover.
01
Define the system
Review the use case, hardware, existing code, interfaces and acceptance criteria.
02
Develop and integrate
Implement the agreed firmware and applications, then connect and validate subsystem interfaces.
03
Test against requirements
Evaluate diagnostics, connection behaviour and system performance through agreed bench, simulation, hardware and field tests.
04
Document and hand over
Agree the deliverables, source code and licensing terms, interface documentation, update process and ongoing support.
Deliverables your team can build on.
Define the handover requirements alongside the development scope. Deliverables, source code access, licensing and support terms are agreed for each project.
Firmware and applications
The agreed firmware, ground software, configuration files and release packages for the selected equipment.
Interfaces and protocol documentation
Message definitions, API documentation, version compatibility notes and examples for connecting your systems.
Build and maintenance documentation
Build instructions and source code where included in the contract, dependency and licensing notes, and an agreed update and maintenance process.
Testing and acceptance evidence
Test procedures, results and known limitations mapped to the acceptance criteria agreed with your team.
FPV UAS software development questions
Can you develop software for our existing FPV hardware?
Yes. Share the aircraft, Flight Controller, communication equipment and VTX/VRX details, together with the available firmware and interface documentation. We review compatibility, development access and licensing before confirming the integration scope.
Can a project cover only one part of the stack?
Yes. A project can focus on a communication gateway, Flight Controller integration, VTX/VRX software, custom protocol or ground application. It can also combine these areas into a complete FPV UAS software project.
What does custom protocol development include?
The agreed scope can include message and interface design, implementation, adapters, diagnostic tools, authentication and access control, version compatibility and integration documentation. Start with the systems and data that need to communicate.
Is VTX/VRX work limited to the ground video viewer?
The scope can span transmitter and receiver configuration or firmware interfaces, video pipeline integration, status monitoring and ground display software. The available development interfaces and selected hardware determine what can be implemented.
Will source code be included in the handover?
Source code access, ownership or licensing, build instructions and third-party dependencies are defined in the project agreement. Include your source code and maintenance requirements in the initial brief so they can be reflected in the quotation.
How is the software tested?
Acceptance criteria are agreed before development. Depending on the project, testing can cover bench operation, simulation, hardware integration and field evaluation, including connection-loss behaviour, diagnostics and video or telemetry performance.
Can the same stack support industrial and tactical use?
Yes. Dual-use projects can apply these capabilities to institutional training and observation, infrastructure inspection, industrial surveys, search and rescue or research. The software and evaluation scope follow the intended application and operating environment.
Tell us what your FPV system needs to do.
Share a project overview to discuss scope, deliverables and a quotation with the team.
- Your organization, application and operating environment
- Aircraft, Flight Controller, radio and VTX/VRX hardware
- Existing firmware, software and protocols to integrate
- Required features, performance targets and acceptance tests
- Timeline, source code handover and maintenance requirements