Skip to content

Lab 09 - Believer Avionics

Today, we focused on dialing in the Believer Avionics specifically through the alteration of parameters in the system.
We added in the airspeed sensor and the GPS sensor to the system.
We also made sure that we could communicate with the GCS wirelessly. We paired the telemetry modules once again, but this time connected the cube to the Air Telem. It then was able to communicate with the GCS. We then modified the SERIALX Parameters to the proper values.

IMG_8850.JPG

SERIALX Parameters
Name
Original
Modified
Notes
SERIAL1_BAUD
115,200
115
Open
SERIAL1_PROTOCOL
MAVLink1
MAVLink
Open
There are no rows in this table



Next we set up the Air Speed sensor. We connected it to the proper CubePilot port and proceeded to modify the parameters to the proper values. We did this successfully and were able to see the value change on the GCS as air was blown into the sensor.
IMG_8847.JPG

ARSPDX Parameters
Name
Original
Modified
Notes
ARSPD1_TYPE
None
I2CMS4525D0
Open
ARSPD1_ADDR
40
0x28H
Open
ARSPD1_BUS
Bus1(external)
Bus0(internal)
Open
ARSPD1_TUBE_ORDR
either port
Port1
Open
ARSPD1_USE
Use
Use
Open
There are no rows in this table

Next, we proceeded to connect and setup the GPS sensor. We plugged it into the CubePilot as well and flashed the FDU with Arduplane. We proceeded to go into the parameters and alter these as well.

We then verified that the GPS was able to connect to the satellites by taking it outside. Eventually the location showed on our GCS so we knew that it worked.

CAN Parameters
Name
Original
Modified
Notes
CAN_P1_DRIVER
Disabled
1
Open
CAN_P1_BITRATE
1000000
1000000
Open
CAN_D1_PROTOCOL
UAVCAN
DRONECAN
Open
CAN_D2_PROTOCOL
UAVCAN
DRONECAN
Open
There are no rows in this table
GPSX Parameters
Name
Original
Modified
Notes
GPS1_TYPE
AUTO
UAVCAN
Open
GPS1_ADDR
0
20
Open
GPS1_DELAY
150ms
100
Open
GPS1_POS_X
0
0
Open
GPS1_POS_Y
0
0
Open
GPS1_POS_Z
0
0
Open
GPS1_USE
UseForNavigation
UseForNavigation
Open
There are no rows in this table

Reflection:
This lab was overly beneficial to the setup of the believer. Being able to see the avionics that we will be using in the aircraft and seeing them all work is interesting and a relief. We were able to complete all aspects of this lab successfully and now understand the different components of the Believer thus far.

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.
Obtain Starter Set
Identify the items
Solder appropriate parts (confirm with instructor)

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 a brand new SD Card to insert into your DATX.
When you power on the DATX you will see two models. “DAB10” and “PUB” Edit the PUB to be PUB## corresponding with your group number. To pair you will need to download a LUA Script. You will need the appropriate . In the zip file you will have two versions to choose from. Research which version is the correct one. Power off your DATX and up the SD card in your computer. Insert the correct files into the “SCRIPT” folder.

Questions

What is a LUA Script?
It’s a lightweight and embeddable coding language that’s generally designed for embedded applications and scripting.
Which is the correct version for the Lua script? Why?
We are utilizing EdgeTX 2.7.1. Per the instructions from TBSAgentLite099_readme, versions of EdgeTX to include 2.10.x and prior should use tbs-agent-lite-099-etx-lua52 (LUA52).

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
Broken link
, we flashed the BlueCube 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

Following
Broken link
, upload the FCU version provided.
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.
Add the parameter file to the
Broken link
table above.
Import and upload the parameters file attached:
111025Dab10Parm - Modified.json
Export the parameters again as a file named parameters_PUB##
Add the parameter file to the
Broken link
table above.

Task: Test System Connectivity

With the new parameters uploaded, it’s important to test that all systems are green.
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.

Questions

What is the current FCU version? This information is available in the status text window of Ground Control.
Version 1.31.3

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.

Reflection: In this lab, we continued to add and sync more instruments and parameters into our believer.

We have to make sure our believer is able to be connected to. For that, we needed a transmitter and receiver.We acquired a TBS Tracer Starter Set and began to identify which was which and soldered them to the appropriate parts.
We then had to pair the TX ad RX. We had a zip file to download and insert into the DATX in order to properly set this up. We were able to successfully bind the two together.
Next we we had to alter our FCU and paraemters becasue they did not align. SO, we uploaded a new file in order for them to work together. We then proceeded to test System connectivity and connected all sensors to the flight controller. We had all systems in the green as well.
Unfortunately, when we tried modifying the parameters tht prevented the GPS from working, even through troubleshooting, the system would never load and download/change the parameters. So we were unsuccessful in doing that.

image.png
image.avif
Screenshot 2025-11-04 at 3.31.04 PM.png
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.