Skip to content
What is CRSF and SBUS? What are the differences?CRSF is a fast, low-latency digital RC protocol with full telemetry support. SBUS is an older, slower serial protocol that carries basic control channelsWhat is Multi-Bind on the TBS Tracer? This function lets you use multiple Tx with the same Rx
Screenshot of Platform Health Status
Connect your DATX and verify connectivity in the ribbon. 
View your servo outputs in the Live Data tab (more on this in the next section)
What does the RCMAP_X parameter control? Flight control axis and functionWhat does the SERVO#_FUNCTION controlThe function the autopilot sends to that servoList all possible power sources for the following systems:Servo: MAINRAIL, which comes from esc Motor: Battery to esc Cube/FCU: POWER1 & POWER2ALL LAB TABLES
Lab 11 - Motors and Controls
ALL LAB QUESTIONS + PICTURES + WIRING DIAGRAM
DATX Setup
AVIONICS SETUP
Motor and Control Setup
Wiring Diagram (My Creation):
ALL LAB TABLES
RCMAP_X
name
Parameter
BREAK
0
FLAP
0
PITCH
2
ROLL
1
THROTTLE
3
YAW
4
There are no rows in this table
SERVO#_FUNCTION
Name
Column 2
SERVO1
FLAPERONRIGHT
SERVO2
FLAPERONLEFT
SERVO3
THROTTLE
SERVO4
THROTTLE
SERVO5
VTAILLEFT
SERVO6
VTAILRIGHT
SERVO7
RUDDER
There are no rows in this table
SERVO IMPUT
RIGHT STICK
LEFT STICK
VTAILRIGHT
THROTTLE
VTAILLEFT
VTAILRIGHT
FLAPERONRIGHT
VTAILLEFT
FLAPERONLEFT
RUDDER
There are no rows in this table
LAB REPORT
In this lab, we aimed to simulate the avionics and control surfaces for the Believer. We started by calibrating the DATX transmitter. This ensured that communication worked correctly between the DATX transmitter, receiver, and flight controller. Then, we went through the stick calibration. After that, we customized the home screen to fit our needs. Then we opened the LUA script. We enabled the Multi-Blind mode there. We checked that Channel 1 on the Tracer Nano RX was set up as SBUS properly. After that, we looked over all the sensors hooked up to the Cube. We made sure each module was running fine and talking to the system without issues, as seen in the platform health screenshot. However, we did have issues with the GPS system, as it kept giving a warning and then dropping off soon after, even when positioned next to a window. Other groups had this issue too. Once we confirmed most of the sensors were healthy, we checked how the DATX inputs linked to the servo outputs. We figured out how pitch, roll, yaw, and throttle inputs matched up with the right servo functions. Such as flaperons, rudder, V-tail surfaces, and throttle. This helped us verify the RCMAP_X configuration and SERVO#_FUNCTION assignments were correct. Originally, our parameters were not set up in the way we needed for windracers; there were only 4 inputs out of the 7 required, so after comparing it to the built believer with our TA’s assistance, we were able to swap over the needed assignments to our parameters. Also, it appears that the believer actually only needs 6 functions, as the 7th was a rudder function that was connected to nothing and is only redundant, due to the v-tail functions already in place, and there was literally no connection for the rudder.
The last part of the lab dealt with the motor and ESC control. We hooked up a servo and ESC to the right outputs based on our mapping. We confirmed the servo moved as expected. Next, we mounted the ESC and motor on the thrust stand. We ran through the ESC calibration procedure. The aircraft stayed in Manual Mode and armed through the Ground Control Station. When calibration finished, we slowly ramped up the throttle to full power to let us check motor operation. As a result, we spotted a throttle dead zone on the first four clicks, which we didn’t have any more time to diagnose.
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.