Skip to content
Lab 11 motors and controls
Lab Report – DATX Integration, TX/RX Binding, and Parameter Configuration
Receivers (RX) and transmitters (TX) are essential subsystems in every unmanned aircraft, as they enable the two-way communication required for safe and controlled flight. The receiver is responsible for taking commands from the transmitter and delivering them to the flight controller, while the transmitter sends aircraft telemetry data back to the operator. Without this link, the RPIC would be unable to manipulate aircraft behavior, monitor system health, or respond to changing conditions in flight. This lab focused on establishing that full communication chain, configuring firmware, and validating aircraft connectivity using the Believer training platform.
Objective and Group Responsibilities
My team and I were tasked with preparing our flight controller and radio system for operation by confirming hardware readiness, binding the transmitter and receiver through the DATX interface, exploring the purpose and function of LUA scripts, flashing and verifying a compatible FCU version, testing system connectivity, and creating a complete wiring diagram of the Believer UAS. Our group consisted of Isabella Avedician, Kenzie Florkiewicz, Diego Hernandez, Nico Jaekle, and Clayton Brown.
Hardware and Documentation Resources
To complete the integration, we relied on official component documentation:
These resources allowed us to verify pinouts, voltage requirements, and wiring conventions before connecting anything to the Cube.
Receiver Preparation and Transmitter Flashing
Since the Believer aircraft uses the DATX only as a user interface and not as a native transmitter, our first task was preparing the TBS Tracer Micro Starter Set for installation. We soldered header pins to the receiver module on Ground, 5-Volt, and Channel 1. A fourth unused pin was also soldered to physically stabilize the connection and reduce vibration-induced arcing, which can cause intermittent power loss and sparking in flight. After soldering, we inserted the provided SD card—which contained all seven Believer DATX models—into the controller.
Using the TBS Agent Web Interface, we flashed the transmitter firmware to version 6.17. A valid USER ID appearing in the device information confirmed that the TX module was recognized and properly updated.
Model File Verification and LUA Script Importance
After flashing the firmware, we used Diff-Checker to compare model00 against models01–06. Each model contained three critical fields: the model name, the value number, and the “view” setting. The name field was changed to “PUB,” identifying the aircraft as a Purdue University Believer. The value field determines which receiver belongs to which aircraft, preventing students from accidentally connecting to the wrong airframe. Finally, we changed the default view setting from “view: 1” to “view: 2” across all seven models so that the controller displays detailed telemetry—including signals, battery voltage, and flight mode—immediately at startup.
While comparing models, we encountered a LUA script being called as part of the binding configuration. LUA is a lightweight and embeddable scripting language widely used in UAS systems because it can instruct transmitters and flight controllers without requiring excessive processing power. Its flexibility allows users to modify aircraft behavior, build custom telemetry pages, and automate hardware bindings. In this lab, LUA provided the interface that allowed us to bind the transmitter and receiver directly from the DATX.
Receiver Installation and TX/RX Binding
To complete the binding process, we connected the receiver to the Cube using a servo lead with black wire oriented to ground. The opposite end was inserted into RCIN on the flight controller. The receiver’s pin alignment followed standard convention: ground on top, signal on bottom (Channel 1), and 5-volt power in the center. Once physically installed, we powered the DATX, accessed the onboard LUA script, and followed the on-screen binding procedure. A successful bind confirmed that soldering, firmware flashing, LUA scripting, and model configuration were all correct.
FCU Firmware and Parameter File Alignment
In Lab 09, we flashed our Cube with FCU Version 1.31.3, which was incompatible with the parameter file we needed in this lab. When attempting to upload the new configuration, Ground Control generated an error. To resolve this, we first exported the existing parameter set, reflashed the flight controller to FCU Version 1.27.1, and then uploaded the modified parameter file.
Parameter Version Log
Table 13
Date
FCU Version
File Name
11/06/25
1.31.3
parameters_PUB06.json
11/13/25
1.27.1
parameters_new_PUB06.json
There are no rows in this table
Exporting parameters before and after every upload ensures configuration traceability—an essential aviation maintenance requirement.
System Connectivity Testing
Once parameters were fully synchronized, we connected the GPS, airspeed sensor, telemetry radio, and DATX to the Cube. The aircraft was then moved outside to ensure a clear view of the sky. After a short initialization period, the GPS acquired satellites and the Platform Health window confirmed that every subsystem was operating in the green. This demonstrated that wiring, firmware, and radio system integration were successful.
Wiring Diagram Production
With only one day to physically reference the DAB010 sample platform, we documented every servo connection, ESC routing, motor lead, telemetry port, and sensor location into a comprehensive wiring diagram. This document will serve as the master reference when assembling our own Believer, ensuring signal continuity without needing the original aircraft present.
Wiring reference file:
Believer_Wiring_Diagram_111425.drawio.pdf
Summary and Learning Outcomes
This lab demonstrated how essential two-way communication is to UAS operations. Without a properly bound TX/RX pair, an aircraft cannot receive flight instructions nor transmit telemetry back to the operator. Through hands-on soldering, transmitter flashing, model editing, parameter file management, and system testing, my team successfully established radio link functionality and ensured compatibility between firmware and configuration files. We also gained first-hand experience using LUA scripting in a real embedded environment—an increasingly common requirement in advanced multirotor and fixed-wing platforms.
The skills practiced in this lab directly translate to real aviation and UAS integration roles. Troubleshooting version mismatches, validating wiring, binding radio systems, and documenting configuration changes mirror procedures used in professional drone manufacturing, BVLOS operations, and Department of Defense UAS programs. Completing this lab not only strengthened my technical skills—it reinforced the discipline and documentation structure required to ensure aircraft safety, reliability, and regulatory compliance.
Believer_Wiring_Diagram_111425.drawio.pdf
Believer_Wiring_Diagram_111425.drawio.pdf
91 KB
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.