Explore

Lab 07: DATX Setup & Modification

Overview

In this lab, our group modified and configured the DATX/Taranis controllers to match Windracers’ operational standards. The original controllers had more switches and a different default software setup than the Windracers configuration, which can increase pilot workload and introduce safety risks. To align them with the controllers used on the Believer training drones for the Windracers Ultra, we removed or disabled unnecessary switches, upgraded the firmware from OpenTX to EdgeTX 2.7.1, and adjusted key channel mappings and safety-critical settings. I participated in this work as part of the group, helping ensure that both the hardware layout and the software behavior of the controllers now mirror the Windracers configuration and support safer, more standardized flight operations..

Hardware Modification

Group Number - 5

Controller Modified - DATX #5

I was a part of the hardware team

Steps for Modification

We took off back panel by unscrewing the 6 screws holding it together (fig 1)

We compared the switches on our controller vs the ones for the Windracer one and identified which ones needed to be removed

We removed the 2 switches in the back (shown in fig 2) as they wont be used for anything

We removed some of the front switches from the controller. Three 3 position switches and a dial were removed.

We hot glued the switches and dial we won’t be using inside of the controller (fig 3)

Finally, we screwed the controller back together (fig 4 shows the finished product)

Why we modified the controller like this: We took these switches off so that there would be less confusion for the operator as to what switches have to be switched to do something. If you have a controller with multiple switches that serve no purpose you might accidentally flip one of those thinking that you flipped one that is actually used. By removing the switches that aren’t being used we eliminate the chances of something like this happening.

⁠

⁠

fig 1: Controller Taken Apart

⁠

⁠

fig 2: two switches we removed

⁠

⁠

Fig 3: switches inside the controller

⁠

⁠

Fig 4: Finished controller with modifications

Software Modification

A seperate team was in charge of this. They flashed controller #2 with EdgeTX software to make it ready for use in accordance with Windracer standards.

Steps

Go to EdgeTX website

Make sure controller is off

Plug in controller

Move binary file from version provided by TA to the radio and select system 32 boot loader

Flash USB

Why we modified the software: We modified the software so that it would be on par with Windracer standards.

Individual Reflection

I was in Group 5 and participated as a member of the hardware team, but throughout the lab I closely followed and engaged with the work of both the hardware and software teams. Our group modified two controllers, DATX #5 and DATX #2. The hardware team physically modified DATX #5 to match the Windracers controller layout, while the software team flashed DATX #2 with the EdgeTX 2.7.1 firmware and adjusted its settings to conform to the Windracers standard.

⁠

Hardware Team – DATX #5 (My Team)

The goal of the hardware portion in this lab was to simplify the switch layout on DATX #5 so that it would match the Windracers controller as closely as possible and reduce unnecessary pilot workload. We carried out this work through the following steps:

Disassembly – First, we removed the six screws on the back of the controller and took off the rear panel, opening the case so we could access the internal components.

Comparison with Windracers controller – With the case open, we compared the switch layout of DATX #5 with the reference Windracers controller and identified which switches were not part of the standard operational layout.

Removing unused switches – We removed two rear switches that are not used in Windracers operations, and also removed three three-position switches and one dial on the top/front of the controller.

Securing removed switches/dial inside the shell – Instead of cutting everything off completely, we placed the unused switches and dial inside the controller shell and secured them firmly with hot glue so they would not move or be accidentally actuated. This way, they are not used in actual operations but remain physically present in case they are needed in the future.

Reassembly and visual check – Finally, we reassembled the controller, tightened the screws, and checked that the externally visible switch layout now matched the simplified Windracers configuration. At this point, only the switches that the pilot actually needs to use were accessible from the outside.

I actively participated in this entire hardware process. I helped open the controller, compare the layouts, physically handle and label the switches, secure them with glue, and reassemble the unit so that our final hardware configuration was clean and consistent with the Windracers standard.

⁠

Software Team – DATX #2 (Other Team)

Although my official role was on the hardware team, I also closely observed the work of the software team and followed what was being done on DATX #2. The software team’s goal was to bring DATX #2’s firmware and settings up to Windracers’ operational standard, focusing on flashing the EdgeTX 2.7.1 firmware and ensuring compatibility with the reference configuration.

The software team carried out their work roughly through the following steps:

Preparing the controller and tools – First, they fully powered off DATX #2, connected it to a computer via USB, and accessed the EdgeTX website and related tools as described in the documentation.

Selecting the correct firmware – Using the TA-provided EdgeTX 2.7.1 binary file, they confirmed that this version was the correct firmware to match the Windracers configuration.

Flashing DATX #2 – With the controller connected, they copied the EdgeTX binary onto the radio and used the STM32 bootloader / “Flash via USB” option to upload the new firmware to DATX #2.

Verifying operation and compatibility – After flashing, they rebooted the controller into EdgeTX and confirmed that it ran correctly. They then checked key options—such as model settings, channel mapping, and basic safety parameters—to verify that they aligned with the Windracers controller configuration.

Even though I was not formally assigned to the software subgroup, I stayed engaged by watching their process, asking questions, and helping verify that the hardware changes we made on DATX #5 and the software configuration applied to DATX #2 were all aligned toward the same Windracers standard.

⁠

Importance of Each Team’s Task

The hardware team’s work on DATX #5 was very important because it dealt directly with pilot workload and safety. When there are too many unused switches, especially in high-stress situations, there is a greater chance that a pilot might accidentally touch the wrong switch. By removing switches whose functions are not defined in Windracers operations and securing them inside the case, we reduced the likelihood of accidental inputs and made the controller interface more intuitive. This not only makes flight operations safer, but also represents a better design from a human-factors perspective by simplifying the interface.

The software team’s work on DATX #2 was equally important. Consistency in firmware and settings is a key factor in system reliability and efficient troubleshooting. By flashing EdgeTX 2.7.1 and aligning the configuration with the Windracers standard, they ensured that the controller would behave predictably and consistently across different aircraft and pilots. This kind of standardization reduces confusion when switching between controllers, makes it easier to follow common procedures, and simplifies maintenance and debugging. Without a shared software baseline, even identical hardware can behave differently, which ultimately can undermine operational safety.

⁠

Personal Reflection

Before this lab, I had almost no hands-on experience with directly modifying radio controller hardware or flashing firmware for UAS operations. Seeing the inside of DATX #5 and physically changing its switch layout made the controller feel less like a sealed “black box” and more like a system that I can understand and safely modify as long as there is a clear standard to follow. Going through the process of disassembling, modifying, and reassembling the controller with my teammates gave me confidence that even small hardware changes can significantly improve usability and safety.

At the same time, observing the software team’s work on DATX #2 made me deeply appreciate the importance of firmware and configuration management in an environment with multiple aircraft and multiple pilots. I was able to see firsthand that only when hardware simplification and standardized software come together can the overall system be operated stably. I was especially impressed by the idea that the pilot’s interface must be clear, and the firmware running underneath must be consistent and trustworthy.

As we move toward more complex UAS operations, I want to maintain this perspective: always considering how hardware and software design decisions together affect pilot workload, safety, and the robustness of the overall system.

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.