Overview
In this lab we are configuring the DATX controller, pairing the TBS Tracer transmitter and receiver, updating the BlueCube flight controller firmware and parameters, and verifying full system connectivity for the Believer platform.
By the end of this lab you will have:
Flashed the TBS Tracer Micro TX and bound it to the RX Updated the BlueCube FCU version and parameter files Verified system health (GPS, telemetry, RC link, airspeed) in Ground Control Captured wiring notes that mirror the DAB010 model for future work Resources
Hardware and Documentation
TBS Agent & Tools
TBS Agent Web (for TX firmware):
Use this table to track parameter exports before and after uploading the modified file.
Parameters Version Control
Assignment – DATX and TX/RX Pairing
Concept
For this aircraft, the DATX controller is used as a user interface that talks to a third-party transmitter (TBS Tracer Micro TX), instead of using the controller’s internal RF module. The Tracer TX/RX handle the radio link; the DATX is the front-end UI.
Steps
DATX / TBS Tracer Setup
Obtain the TBS Tracer Micro Starter Set. Identify all items in the kit: Tracer Nano RX (or equivalent) Antennas, cables, and accessories Solder the appropriate connectors to the RX as directed by your instructor. TX Firmware & Model Files
Insert the provided SD card into your DATX. Confirm that models model00 – model06 are present. If they are missing, stop and get help. Connect the TBS Tracer TX to your computer and open TBS Agent Web. Flash the TX to firmware v6.17. In Agent, connect to the “Tracer Micro TX” and go to the About tab. Confirm that a USER ID is displayed. Show this step to your instructor.
Model View Change (Diff Checker)
Use Diff Checker to compare model00 and model01. Identify the three differences between the files. For models 01–06, change: This sets View 2 as the default, which displays more data while piloting. LUA Script and Binding
Q1: What is a LUA Script?
Answer: LUA is a simple scripting language used to create automated functions and custom tools inside the radio system.
Q2: Why are we using one in this lab?
Answer: We are using a LUA script to make it easier to control and configure the Believer from the DATX. It lets us run a simple program on the radio to handle things like binding and telemetry setup without digging through a lot of menus.
Binding Process
Plug your RX into the BlueCube correctly (power, signal, ground). Power on the DATX with the Tracer TX module installed. Navigate to the LUA Script menu on the DATX. Run the binding LUA script and put both the TX and RX into bind mode. Confirm successful binding: RC inputs visible in Ground Control RC link status showing connected RSSI/Link quality visible (depending on config) FCU and Parameters
In Lab 09 – Believer Avionics, the BlueCube was flashed to FCU v1.31. For this lab, we are reverting and aligning firmware and parameter files.
Task – Upload Firmware and Parameters
Following Lab 09 – Believer Avionics · AT 209, upload the provided FCU version (1.27) to the BlueCube. Connect the FCU to Ground Control and open the Parameters tab. Download the current parameters from the aircraft. Export the parameters as: where ## is your 2-digit group number. Add this file to the Parameters Version Control table above. Import & upload the modified parameters file: 111025Dab10Parm - Modified.json In the Engineering window, reboot the autopilot. After reboot, export parameters again as: Add this second file to the Parameters table, noting that it is the post-modified set. Task – Test System Connectivity
With the new parameters uploaded, confirm that the aircraft is healthy.
Connect the following to the BlueCube: Move the aircraft (or antenna) near a window with a clear view of the sky to obtain GPS. In Ground Control, verify: All connected systems show green status in Platform Health Status. The aircraft obtains a valid GPS fix. RC link is active (channels responding). Lab Questions & Answers
What is the current FCU version? Originally 1.31, but we changed it back to 1.27 for this lab. Include a screenshot of your Platform Health Status.