TROUBLESHOOTING
NO CAMERA CONTROL
If the camera cannot be controlled through QGC, follow the troubleshooting steps below.
1. Check TAG-E and Camera Status
The camera must be ONLINE before troubleshooting camera control.
The TAG-E LED must be GREEN.
Verify that the camera firmware is compatible with the TAG-E firmware.
Make sure an SD card is installed in the camera.
Test the camera using its physical shutter/record button to confirm that the camera itself can capture or record normally.
If the TAG-E LED is not GREEN or the camera cannot be operated using its physical button, resolve the corresponding TAG-E/camera issue before continuing.
2. Check TAG-E Status Messages in QGC
Verify whether TAG-E is successfully communicating with the flight controller.
Open QGroundControl (QGC).
Click the Message icon in the top-left corner of QGC.
Reboot the TAG-E.
Wait until the TAG-E LED becomes BLUE or GREEN.
Check whether TAG-E sends its initialization/status messages in the QGC Message window.
If no TAG-E messages are received:
Check the physical wiring and connections.
Check the MAVLink baudrate settings.
Verify the TAG-E and flight controller serial-port configuration.
If TAG-E status messages are received: Continue to the next step.

3. Check ArduPilot and Camera Configuration
If TAG-E status messages are visible but camera control is still unavailable:
ArduPilot Version
Check the ArduPilot firmware version.
Recommended: ArduPilot 4.6.0 or later.
CAM1_TYPE
Verify the CAM1_TYPE parameter:
or
After changing the parameter, reboot the flight controller.
Component ID 100
Open:
QGC → MAVLink Inspector
Verify that:
is detected.
Component ID 100 not detected → Troubleshoot TAG-E/MAVLink communication.
Component ID 100 detected → Continue checking camera control configuration.
If all settings are correct but camera control is still unavailable, reboot the complete system and test again.

4. Check Camera SD Card
Make sure an SD card is inserted into the camera.
Important: Without an SD card, the camera cannot perform trigger/capture or recording functions.
5. Test the Physical Camera Button
Manually trigger the camera using its physical shutter/record button.
This helps determine whether the issue is related to:
Camera hardware/functionality, or
TAG-E / MAVLink communication and control.
Expected Result
The camera should respond correctly to both:
Physical camera controls
MAVLink/ground-control commands
TAG-E HAS A BLUE LED
Symptom: TAG-E LED remains blue and the TAG-E is not detected correctly by the system.
Troubleshooting:
Check the physical connection between the TAG-E and the camera.
Make sure the connector is fully inserted and securely connected.
Reconfigure the required MAVLink parameters according to the TAG-E configuration guide.
Restart the camera and TAG-E after applying the configuration.
Expected Result: The TAG-E LED should change to green, and the TAG-E should be detected by the flight controller/QGC.
TAG-E shows a Green LED, but Component ID 100 is not shown in QGC
Symptom: TAG-E LED is green, but Component ID 100 cannot be found in the QGC MAVLink Inspector.
Method 1 — Reconfigure MAVLink Baudrate
Check and configure the baudrate as follows:
Device
Parameter
Value
QGC / Flight Controller
SERIAL2_BAUD
921600
gTune / TAG-E
COM2
921600
After changing the baudrate:
Save the configuration.
Reboot the system.
Open QGC → MAVLink Inspector.
Check whether Component ID 100 is detected.
If Component ID 100 is still unavailable, proceed with Method 2.
Method 2 — Manually Configure TAG-E Baudrate via SD Card
Important: This procedure directly modifies the TAG-E configuration. Follow each step carefully.
Step 1 — Remove the SD Card
Remove the SD card from the TAG-E module and insert it into a PC.
Step 2 — Create set.txt
Create a new file named:
Place the file in the root directory of the SD card.

Step 3 — Enter the Configuration Parameters
Open set.txt and enter:
If using 921600 baud, use:
Important:
FW_SAVE_CFG=1 must be the last parameter in the file. This command permanently saves the configuration.
Step 4 — Save the File
Save set.txt and safely eject the SD card from the PC.
Step 5 — Insert the SD Card into TAG-E
Insert the SD card back into the TAG-E module and power on the TAG-E.
Wait until the TAG-E LED becomes blue/green.
Step 6 — Verify the Configuration
Remove the SD card from the TAG-E and reinsert it into the PC.
The SD card LED should:
Blink RED twice.
Stop blinking.
Turn GREEN.
After this process, the TAG-E configuration should be saved and Component ID 100 should be available in the QGC MAVLink Inspector.
Step 7 — Remove set.txt ⚠️
This step is mandatory.
After the configuration has been successfully applied:
Remove
set.txtfrom the SD card, orRename the file so that it will not be executed again.
Warning: Do not leave
set.txton the SD card. Continuous configuration writing may repeatedly overwrite the device memory and potentially damage the TAG-E.
Last updated
Was this helpful?