Skip to content
Obtain Starter SetIdentify the itemsSolder appropriate parts (confirm with instructor)
solder header pin on GND, 5V, CH1 on the receiver module solder the 4th empty pin to reduce vibration to minimize potential sparks
7 different modelmodel 0: name, value numbers, and view is different name = name of model PUB (Purdue University Believer), value = number receiver is tied to to ensure people do not connect to different receivers, view = when it turns on, we have to modify the view for believer change view 1 to view 2 for all 7 What is a LUA Script?known for being lightweight, fast, and embeddablecommonly used to add custom functionality to larger applications for controlling application behavior(.lua) Why are we using one in this lab.Plug the receiver into the servo wire, black to ground... plug the other end of the servo wire into RCIN...Black on top(negative) channel 1 is bottom(signal) and 5V middle (positive)
Connect the flight controller to Ground Control and navigate to the Parameters tab.Download the parameters (this is always required to download the current parameters).Export the parameters as a file named parameters_PUB## where ## corresponds with your two digit group number.Import and upload the parameters file attached: From the Engineering windows, reboot the autopilot.Export the parameters again as a file named parameters_PUB##
Connect the following sensors to the flight controller: GPS, airspeed sensor, telemetry, and DATX.Verify that all systems are in the green and that the aircraft gets GPS signal. Take a screenshot of the Platform Health Status window and the RC connection status in the top ribbon.This may require setting the system near a window with a clear view of the sky.
What is the current FCU version? V1.27.1Screenshot of Health Status
Modify the previous e-portfolio post to include this lab in your individual writeup. Using the tools in to identify the parameter that was missing preventing the GPS from working.Export as PDF using /pdf and submit to Brightspace
Lab 10 - Motors and Controls
Overview
In this lab we are creating great things
Resources
There are no rows in this table
Parameters Version Control
Date
FCU Version
File
Notes
11/6/2025
1.31.3
Open
11/13/2025
1.27.1
Open
Open
Open
There are no rows in this table
Assignment
DATX
Connecting to any aircraft require two things. A transmitter and receiver. On our aircraft we are using the controller as a User Interface for a third party transmitter rather than using the built in transmitter. The TBS Tracer Micro Starter set is what we are using.
Pairing TX and RX
When the TX and RX are properly setup we need to pair them together to make them work. You will be given an SD Card to insert into your DATX after all models have been downloaded. When you plug the SD card into your computer you will see that I so kindly added all of the models and you should see model00-model06. If you do not please stop and get help.
You will need to flash your tx to version 6.17 using the TBS Agent Web. Once you flash the firmware ensure that you connect to the “Tracer Micro TX” select the about column and ensure that there is a USER ID: (When you get to this step please show your instructor)
Now you will need to use and upload model00 and model01 and compare the differences. There will be 3 differences. Change “view: 1” to “view: 2” on models 01-06. This is the default view you see when piloting the aircraft and view 2 gives us more data.
LUA Script is a set of instructions written in the LUA scripting language
We are using it in this lab because it is lightweight and efficient due to its fast execution in Flight Controllers and RC transmitters. It is also flexible and customizable which allows the user to monitor and manipulate behaviors. LUA is also a common in drone platforms as it makes it easier for users to implement and share custom functionalities.
Plug your RX into your BlueCube correctly. Power on your DATX and navigate to the LUA script and go through the binding process. Ensure that TX and RX are in bind mode. Confirm that you have successfully bound the two together.
FCU and Parameters
In , we flashed the Blue Cube with FCU Version 1.31. The FCU version and the parameters file we will be using do not align, so uploading causes an error.
Task: Upload Firmware and Parameters
111025Dab10Parm - Modified.json
Task: Test System Connectivity
With the new parameters uploaded, it’s important to test that all systems are green.
Questions
Servos, ESC and Motors
Using the DAB010 model as a working guide, develop a wiring table and notes for all connections including, telemetry, sensors, flight controls, and motors. This should mirror DAB010 and be 100% complete and comprehensive. This is the only day that the sample platform will be available. All remaining work will be completed from your wiring notes.
Deliverables
Believer Wiring Diagram
Believer_Wiring_Diagram_111425.drawio.pdf
93.2 kB
Believer Wiring Diagram
Reflection
For this lab, our deliverables were to pair the RX with the TX and create a wiring diagram. This lab was fairly intensive with a decent amount of work ahead of us, so in order to complete it all within the time frame, we divided the work up into two groups.
At the beginning of the lab, we were introduced to the TBS RX and TX. These little receivers are put on the nano receiver, and then a 4-head pin is soldered onto the left side of the nano receiver. We only needed 3 of the 4 pins to work, but we soldered all 4 to reduce sparks and vibration.
Once our module was properly set up, anesite gave us the SD card to put into the computer. Our next goal was to change the LUA script on the SD card to a different view. The default was a #1 view, and we had to change it to the #2 view for a successful checkoff. It was more time-consuming than difficult, but eventually we changed all the views. LUA scripts are useful for controlling application behavior, so we used it for the believer.
We then plugged the receiver into a servo wire and the servo wire into the cube. Making sure that we set it up correctly, because one wrong move and it could reverse polarity and release the magic smoke. We also plugged in the TX to the DATX and made sure everything was powered on. We then made sure everything was put into binding mode. Once bound correctly, we then moved on to flashing the FCU
The FCU parameters were given to us in the lab, and all we had to do was take these parameters and flash them onto the cube. An AIEDA certified computer was required for this to work properly. We also had to save the previous parameters just in case. Once everything was flashed, we had to reboot in order to see if everything worked correctly. Once confirmed, we went outside to make sure we had GNSS support and if satellites were communicating.
Once that was completed, our other groupmates came together to explain the wiring diagram, and we wrapped up the lab.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.