Explore

Lab 07 - DATX Setup and Modification

20 points

Overview

In this lab, you will modify and configure the DATX controller to meet Windracers’ operational standards. Our current Taranis controllers include unnecessary switches and default software that differ from the Windracers configuration, which can make flight operations more complex and introduce potential safety risks.

Working in your Believer groups, you will divide tasks between hardware modification and software configuration. The hardware team will physically modify the controller by removing or securing unused switches to match the Windracers layout, while the software team will migrate the controller’s firmware from OpenTX to EdgeTX 2.7.1 and adjust key settings for compatibility.

Once both teams complete their sections, the group will reassemble and test the DATX, ensuring full functionality and communication with the TBS Tracer transmitter and receiver. By the end of this lab, your DATX should be fully standardized, safe to operate, and ready for integration with your Believer aircraft.

Resources

Assignment

In this lab we will be modifying the controller physically and changing the software. We will also be setting up our receiver to connect to our newly modified controller. You will be working in your believer groups to get the DATX properly configured for flight operations. Your group should divide in half and have half physical modification while the others get ready to modify the software and begin working on the receiver.

Hardware Modification

We will be modifying our controllers to match Windracers. Windracers modifies them by removing some of the switches and knobs. As you may be able to tell our controllers currently have too many switches that can make operation difficult. Some of the switches get in the way and may cause safety risks.

Goals

Software configuration

We will be modifying the software that comes preloaded on these controllers. The controllers come with a version of OpenTX. The software that we will be installing is EdgeTX version 2.7.1. We will also be inspecting Windracers controller settings to check for a key difference between them.

Loading manual.edgetx.org⁠

⁠

Goals

Using the OpenTX to EdgeTX guide successfully flash our desired software version onto your controller.

Receiver setup

Now that we have our controller setup correctly we need to be able to communicate with our aircraft. You will be provided with a TBS Tracer transmitter and receiver.

Actions

Solder header pins onto Nano RX board.

Update TX according to Page 7 on TBS Manual

Connect your RX to the built Believer frame

Bind your RX and TX

Deliverables

Effective communication

Communication during this lab was found to be excellent, and all group members worked together well to accomplish the tasks at hand. There were six total members in this group (Group 4), and while Elijah, Ryan, and I worked on the physical modification of the controller, Madison, Venkata, and Nolan worked on the software flashing. Each person knew what they were doing, and this communication saved time during the lab overall. At the end of the lab, each side of the group efficiently communicated their tasks and successes, and everyone was on the same page.

Physical Modification of Controller

The modification of the controller was completed such that we could use the controllers for the Believer fixed wing UAS in the future. The modification was conducted in a group setting, and it was completed thoroughly so that problems did not occur. For instance, one group modified the controller in such a way that the joystick on one side did not move. It was for reasons like these that Group 4 decided to take their time on the lab. Steps and images of this process can be seen below in the reflection steps for this part of the project.

Edge TX 2.7.1

The flashing of the software of the controller was completed by half of the group, and there were many struggles with this. The firmware used was that which came from the teaching assistant, and there were many crucial steps used to ensure that things went well. These steps are highlighted below in the reflection entry. Many groups became frustrated with the software steps because they were not as intuitive as students would have liked to imagine, and sometimes even the right steps did not lead to the desired result. Nonetheless, our group persevered and completed this part well.

Reflection

Group 4, which consisted of Venkata, Madison, Nolan, Ryan, Elijah, and myself, worked well to complete this lab. I was in the hardware team, and while we took longer than the other half, we worked well and with precision. The two DATX numbers we modified were #4, relating to hardware, and #1, relating to software. The process of each task and its inherent importance is highlighted below, and without adequate collaboration between group members, none of it would have been possible.

Steps to complete controller physical modification:

First, the controller given for the lab was compared to the functional controller in the optimal setup.

⁠

Second, the controller was carefully taken apart, and special care was taken to protect the ribbon cable which spanned between the front and back sections of the controller. Two switches and a potentiometer were taken from the back, and two switches were taken from the front.

⁠

Third, the parts which were not used were hot glued to the interior of the controller, and this was done so that they could be easily accessed should they need to be reinstalled. The image below depicts this process as well as the group getting along.

⁠

Fourth, the new antenna was placed onto the back of the controller, and the switches and joysticks were tested for operation. The modified controller was then placed in the case and put away.

⁠

Steps to complete controller software flashing:

First, the correct firmware was downloaded from teaching assistant Tsagris’s computer. This file was then uploaded to EdgeTX buddy.

Second, the controller was plugged into the same computer used for the first step, and it was ensured that the controller was turned off.

Third, the instructions on EdgeTX were followed closely and the below image shows what appeared after the completion of the tasks. After this step and the conficmation image, the flashing of the software for the drone is complete.

⁠

Importance of each task:

Both the software and the hardware orientation and modification were necessary for the success of this lab. One cannot modify one without the other because the software and the hardware must interact and work together to fly safely and well. Also, especially when updating controllers, it is important that the input switches and knobs are aligned well with the useful electronic actions they perform, and this lab was practice in ensuring that. The updating of the software is particularly important because of the protections against cyber threats and possible additional functions, let alone the improved ability to talk to the controller. The controller modification is also particularly important because switch number reduction reduces confusion for pilots and makes those flying look all the more industry ready. The parts unused were hot glued inside of parts of the controller so that they can be easily accessed and used in the future. Overall, the success of the believer program rests on the training conducted in the lab, and the training is made much simpler with updated quipment.

Lab 07 Scoring Table

Lab 07 Scoring Table

Deliverable

Points

Effective Communication within group and complete understanding of all work done

Correct physical modification of controller

Successful flash of Edge TX 2.7.1

Reflection entry

There are no rows in this table

Sum

⁠

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

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.