AirPixel
Support & knowledge base

Answers from years of real support cases

This is an AI-generated knowledge base based on our email history; it may contain errors. 117 technical questions and answers, compiled from the AirPixel support archive (2018–2026). Choose your system first – ENTIRE, TAG-E and MavPorter are kept apart.

Before you write to support: collect this

Covers the ENTIRE controller (web page over its own WiFi hotspot), AIR Commander Link, SmartPlug and the Extension Box. If your unit has no WiFi and is set up with MAVLink parameters, you have a TAG-E.

  • Firmware versions: ENTIRE, camera, gimbal, flight controller
  • ENTIRE log: MENU → About → blue heart icon, before any reboot
  • Settings screenshots or MENU → Share Settings → Download
  • Photos of the wiring (hotshoe, USB, UNI)
  • Two or three JPGs and the GPS text log (geotagging problems)

Getting started & diagnostics

What should I collect before contacting support?

These five items resolve or diagnose most cases:

  1. Firmware versions of the ENTIRE, the camera, the gimbal and the flight controller. Many reported bugs were already fixed in a newer build.
  2. The ENTIRE log (dump). Open the ENTIRE web page, MENU → About, click the small blue heart icon and wait a few seconds for a .TXT download. Do this before rebooting; a reboot erases the information about the failed flight. In MavCam: swipe right, expand the Exposure panel, scroll down, click LOG (saves to the camera card).
  3. Screenshots of the settings (or MENU → Share Settings → Download) and the flight-controller parameter list.
  4. Photos of the wiring, especially the hotshoe, USB and UNI connectors.
  5. Sample files: a few JPGs from the flight plus the GPS text log (details_xxxx.txt and the GPS file on the camera card).

Short video of the behaviour (LEDs, camera screen) helps a lot. Keep multiple problems in separate threads.

supportlog

Copy link

The web interface looks wrong (greyed-out options, missing items)

Press Ctrl+Shift+R to force a reload of the page's CSS and JavaScript after a firmware update. If upload or settings pages misbehave, try another browser or device. The WiFi is deliberately weak, so keep the phone or tablet within about 10 cm of the unit while setting up.

GUI

Copy link

What do the status LED colours mean?

  • White blink when a command is executed. Pressing a button on the Link transmitter and seeing a white blink proves the command arrived.
  • Short blue blink after each trigger: a capture was detected on the hotshoe / EXPOSURE wire. No blue blink means geotagging cannot work (wiring).
  • Blue after boot: the unit is ready. Wait for it before connecting.
  • Slow green blink: geotagging is running. If you never see it after takeoff, geotagging did not start.
  • White then red when starting geotagging: the start failed (wrong geotag mode for the camera, no or unformatted SD card, camera not in Mass Storage).
  • Purple blink, then steady purple: WiFi reset in progress (see the WiFi section).
  • Continuous white blinking: an SBUS channel is constantly triggering a function, which can lock the unit. Check your SBUS mapping.

LED

Copy link

How do I reset the ENTIRE, copy settings between units, or reset Bluetooth?

  • Copy settings: update both units to the same firmware, then MENU → Share Settings: download from the working unit and upload to the other.
  • Factory-style reset: load an empty settings bank (for example B), then save it to A.
  • WiFi reset: see the WiFi section (the WIRELESS button).
  • Bluetooth reset: at the bottom of the menu there is a Bluetooth reset; reboot afterwards and remove old pairings from the camera.

settingsreset

Copy link

Which ENTIRE hardware revision do I have, and what changed?

Rev 1 and Rev 2 reached end of firmware development in 2023. Rev 3 (R3) is the current board and is more stable. Multiport cables for Rev 2 are no longer supplied because the wiring differs. Rev 2 can still run Sony control, but new features (e.g. A7R V, ILX-LR1 improvements) are not guaranteed. All current manuals are for R3; each product has a QR code on its back that leads to the right installation page.

R3revision

Copy link

How AirPixel support works best

  1. Send the log before theories.
  2. Separate multiple issues and number them.
  3. Check the obvious: SD card inserted, camera firmware, did the drone actually fly.
  4. When appropriate a development build is sent for a single issue.

support

Copy link

Power, cables & hardware

How must I power the ENTIRE?

The ENTIRE takes 5 V only (5 to 5.5 V), able to deliver about 2 A without drop or oscillation, because the same input is forwarded to the camera's USB and the Link receiver. A USB port, for example on a Ronin, works directly. Feeding it more than about 5 to 6 V (for example 12 V) damages it within seconds.

  • From a battery use the AirPixel Power adaptor or uBEC (input 7 to 23 V; for stable WiFi keep it at 9 V or more). The Power adaptor has over-voltage, over-heat and short-circuit protection; the plain uBEC has no reverse-polarity protection.
  • Reversed polarity usually burns the main module. Short overloads can also burn the USB power switch inside. Contact support with photos of the unit; repair is often possible.
  • Weak power shows up first as WiFi instability and later as random behaviour.

Documentation: Power adaptor uBEC v2

poweruBEC

Copy link

Hotshoe sync error or missed captures

Usually a damaged spring contact because the hotshoe plug was inserted the wrong way round. A bad contact also causes "random" missing geotags. Check that the plug is fully seated and no pin is broken; gently pulling the contact spring out a little raises the pressure on the camera pin. Never put more than about 3.3 V on the sense wire. When you share the signal with an Emlid or a Cube, share GND and connect their event input; both can be used together.

hotshoe

Copy link

Cable lengths and USB problems

  • The Multiport cable is limited to about 15 cm; do not extend it. The ENTIRE should sit at the camera; the serial/MAVLink side can be extended.
  • Keep USB runs as short as possible. For home-made harnesses twist the D+/D− pair, check the soldering (some solder pastes caused intermittent faults) and a 5.1 kΩ resistor in the USB-C at the camera end.
  • Bent pins in the USB-MULTI connector appear when the plug is inserted crooked.
  • If USB works in only one direction (typical through a Gremsy quick-release), reverse the USB-C plug.
  • Test the USB path separately: plug the QR/camera cable into a PC to see if the camera mounts as a drive.

Documentation: USB-C connection issues

cablesUSB

Copy link

SD cards: which format, which size, and why a slow card breaks geotagging

  • ENTIRE's own SD card: exFAT or FAT32; tested up to 128 GB. Optional.
  • Camera card: format it in the camera (the camera's own format differs from a PC format).
  • If the camera is still saving images tens of seconds after landing, the geotags cannot be written and your photos stay without EXIF. A slow card caused this at one customer (about 100 kB/s writes even with a fast-looking card). Use a fast card and, if possible, wait in the air until the camera has finished saving. In the camera's NETWORK menu set Still Img. Save Dest. = Camera Only.
  • Recovery of the ENTIRE's own firmware is done over USB, not from an SD card.

SD card

Copy link

Battery door, overheating and video recording

When the SmartPlug battery dummy is fitted, remove the battery door. A closed or forced door can overheat during long video recording in warm weather. High frame-rate series triggering can cause a voltage drop and power off the camera. Check the supply before blaming the controller.

SmartPlugpower

Copy link

WiFi & web interface

The ENTIRE hotspot disappears or drops after 10 to 30 seconds

Three causes, most likely first:

  1. Weak power. WiFi is the first thing to fail. The unit draws close to 1 A at high WiFi load. Give the uBEC at least 8 to 9 V; a 3S LiPo or higher is fine.
  2. The ENTIRE is joining another network. Its own hotspot is disabled for the whole time of any outgoing connection, and each time it reconnects to a camera. A wrong password makes it loop. Use the WiFi reset below.
  3. Range / interference. WiFi power is deliberately very low so it does not disturb the drone's links. Keep the phone within 5 to 10 cm during setup, power off HereLink or LightBridge, and mind that an inserted SD card slightly reduces range. The antenna sits under the SD slot: place the unit on its back for the best signal to the camera. 2.4 GHz video transmitters (an air unit running alone) are the worst case.

WiFi

Copy link

How do I reset the WiFi?

Insert a wire or needle into the hole labelled WIRELESS (under the status LED) and press the internal button. The LED blinks purple; keep holding until the LED is steady purple, then release. All WiFi configuration returns to default and the hotspot is back in about a minute.

WiFireset

Copy link

Can the ENTIRE join my router or LAN?

Yes. Open the WiFi page, enter the network and password, and (for automatic reconnect) allow enough connection timeout (up to 60 s). While joining, the hotspot is off and the phone may disconnect. Then the web UI is reachable over the LAN and cameras on that LAN can be controlled with exposure, REC, etc. (Sony FX3/FX30 work well; FS5 is not guaranteed). LR1 camera IP is checked by address, so the camera IP must be configured manually and unique.

WiFiLAN

Copy link

Sony WiFi control setup

  1. Switch the ENTIRE to WiFi mode.
  2. In the camera: Control w/ Smartphone → ON, then Connection; the camera creates an access point.
  3. From the ENTIRE WiFi page join the camera access point. After each ENTIRE firmware update repeat the camera pairing (camera menu PC Remote → Pairing).

Sony firmware updates have broken WiFi control in the past (e.g. FX3); USB is the more robust fallback for A7-series. For the ILX-LR1 the camera must be in M (manual) exposure mode; in the default intelligent auto mode exposure cannot be controlled.

Documentation: WiFi camera control

SonyWiFi

Copy link

Camera-specific WiFi notes (Canon, RED, Panasonic)

  • Canon: the camera's hotspot name must contain EOS (uppercase), for example EOS-myname. Enable CCAPI (Camera Control API) first.
  • RED Komodo / V-Raptor: use Ad-Hoc mode, 2.4 GHz band, a middle channel, WPA2.
  • Panasonic: WiFi is the only control path.

WiFiCanonRED

Copy link

Geotagging

How does ENTIRE geotagging work?

On a drone with ArduPilot or DJI, geotagging starts by itself at takeoff, records GPS/RTK and attitude for every photo, and when the drone lands it writes the data into the EXIF/XMP of the new JPGs. Three modes exist: Direct EXIF (Sony cameras), and Full TEXT or Event TEXT (a text file with the positions, for cameras without USB mass storage).

The photos are only changed after landing, so nothing is lost if you pull the card mid-flight. After takeoff wait a few seconds for the slow green blinking: it confirms that geotagging is running.

Bench test: on the Control page use START / STOP geotagging. After START the camera connects for a few seconds, then the LED blinks green. Trigger 10 to 20 photos, wait until they are saved, press STOP. Run MENU → Geotagging → Configuration test first.

Documentation: How EXIF geotagging works · Geotagging modes

sessionEXIF

Copy link

The geotag session will not start (white, then red)

  • Cameras without USB storage access (Wiris, thermal, Phase One) must use EventTEXT. Direct EXIF cannot start for them and loops.
  • The camera must be in Mass Storage USB mode and have an SD card; the ENTIRE also needs its own SD card inserted in its slot, formatted FAT32/exFAT.
  • Camera folders and names must be the default ones (DCIM/100MSDCF/DSC_xxxx.jpg); additional folders or old photos can confuse the search for the first picture.
  • Self-test error "Camera mount error (E#1)": check in this order – SD card in the camera, correct format, camera in Mass Storage mode, 5.1 kΩ resistor in the USB-C at the camera end, D+/D− not swapped.
  • If the camera shows "Connecting to Mass Storage" but never "Accessing", suspect the USB data pair.

sessiontroubleshooting

Copy link

Geotagging does not start automatically

The ENTIRE detects takeoff and landing from the flight state reported by ArduPilot, not from arming and not from GPS. Arming and disarming on the ground is not enough: the drone must actually fly for a few seconds. On Rover firmware and non-ArduPilot/PX4 platforms the automatic function does not exist; start and stop through MAVLink or the web page. You can also disable the automatic start in MENU → Geotagging → Settings and drive it from your own software; the end of the mission is a better stop trigger than landing detection.

autoheartbeat

Copy link

Geotagging stops mid-flight, or a photo series gets no EXIF

  • Update the firmware: an old class of crash while rewriting XMP was fixed (for the LR1: 1.878 and newer in the old 1.x numbering; R3 firmware is now 2.0xx).
  • Check the camera's firmware; outdated Sony firmware often halts SD writing.
  • Format the card before a session after more than 9999 photos or when there are multiple folders. The ENTIRE copes with the roll-over from 100MSDCF to 101MSDCF but not with a mixed card.
  • Download the dump (before reboot) and look for "unable to connect camera after landing".

EXIFtroubleshooting

Copy link

XMP data randomly missing on some photos

Some photo variants were occasionally left without XMP angle data in older firmware. Update the firmware; if it still happens, send a few sample JPGs from the flight to support so that file type can be added.

XMP

Copy link

The same coordinates repeat across several photos

  • Wired connection: use a 100 Hz stream (50 Hz also works).
  • No RTK installed: RTK must be set to "Do not send".
  • Check connectors for looseness and moisture.
  • Do not let the flight controller push extra GPS streams (SRx must be 0, see the MAVLink section).

GPS

Copy link

Wrong date or time in the photos

The ENTIRE has no real-time clock. Two modes: (1) time via MAVLink or the DJI API – on Pixhawk set SRxEXTRA3 = 1 (1 Hz), on DJI set the TimeStamp message to 1 Hz, then set MENU → Geotagging → Settings → Time Zone Offset. It works even with an unset camera clock. (2) otherwise the ENTIRE uses the camera clock (time of the last photo, accuracy about a minute).

The file modification date is the time of tagging, not capture; the EXIF/XMP capture date remains correct. A SmartPlug that cuts camera power resets the camera clock.

time

Copy link

Can I rename photos or sort them into folders?

ENTIRE does not rename or sort photos (TAG-E does per-flight folders). For naming by field section, process the photos afterwards in your mapping software where sections can be marked on the map.

names

Copy link

Gimbal angles and heading in the EXIF

Angles (roll, pitch, yaw) go into XMP, since EXIF has no field for them. Three XMP flavours exist in the ENTIRE settings (Legacy, inverted, Pix4D); fly 10 photos in each if your software disagrees. Pix4D converts to omega/phi/kappa itself. The report shows heading relative to north.

  • Angles from a DJI Ronin: only on an M600; DJI gimbals do not pass third-party data. Gremsy over CAN gives no data back.
  • Add Frame Angles in the menu replaces gimbal angles by airframe angles; disable it if gimbal angles are expected.
  • Without a Pixhawk there is no true-north heading (a gimbal alone only knows its yaw relative to the mount). A small Pixhawk Mini can supply it.
  • Control by SBUS only: the angles in the metadata may show 0 – feed the real angles by MAVLink.

anglesXMP

Copy link

Photo count mismatch between QGC and the real number of images

The flight controller and the ENTIRE both report every photo, so QGC counts each photo twice. This is how QGC and PX4 count; the photos and geotags themselves are correct.

QGC

Copy link

What is EventTEXT mode and when do I need it?

EventTEXT (since firmware of April 2023) stores each trigger event with GPS and, where available, camera attitude in a text file on the ENTIRE's SD card; no USB connection to the camera is needed. Use it for Nikon, Phase One, Wiris/thermal, GFX or any camera without Mass Storage. Map it to photos afterwards: the EXIF_Geotagger application (1.16+) reads an EventTEXT log and a folder of JPGs line by line (it fails if the counter rolled over 9999). A configurable camera offset of up to 750 mm is available. For Phase One the camera geotags itself while the ENTIRE supplies MAVLink-to-NMEA data; no file-name feedback exists.

Documentation: Geotagging modes · PC EXIF geotagging application

EventTEXTPhase One

Copy link

Can I record video during a geotagging session?

During a session USB is in Mass Storage, so USB or WiFi control is not available and only IR commands work. Older firmware blocked video start/stop during a session; a release in April 2024 added video trigger during geotagging for the ILX-LR1. Without WiFi (Expander) the camera must be switched to video mode manually. Photos are triggered by GPIO, so they work in all modes.

videosession

Copy link

Accuracy, RTK & offsets

How do I tune the GPS link delay for centimetre accuracy?

The delay between a position being measured and the photo being tagged is different for each drone setup. Measure it once:

  1. Update the ENTIRE; set the flight-controller streams correctly (all SRx = 0 and the ENTIRE MAVLink GPS rate at about 5 Hz via MENU → Miscs → MAVLink input options). A flooded GPS link changes the delay.
  2. Fly 3 or 4 straight lines (two in each direction) at about 10 m/s with an RTK fix, over a structured site (quarry, concrete foundations) – not grass or trees, where stitching can place photos wrongly.
  3. Fly to the middle of the site, same altitude, and shoot several static photos (0 m/s) with different yaw. These show the static error (XYZ offsets); the shift between opposite lines shows the dynamic error (delay).
  4. Stitch an orthomap, read the shift along the flight direction, convert with the speed and enter the value in GPS link delay (examples seen: about −100 ms; with some links +190 to +220 ms). The range is ±220 ms in current firmware. Repeat until the lines match.

Customers who completed all steps reach 3 to 5 cm. Note: photos already tagged cannot be corrected; fly again after each change.

Documentation: GPS delay calculation

delayRTK

Copy link

Where do I set camera and antenna offsets?

Set the GPS antenna position in the flight controller correctly (e.g. GPSx_POS) and the camera XYZ offset in the ENTIRE. Watch the sign and polarity: a wrong sign easily gives 30 to 40 cm. The ENTIRE shows the NED offsets it applies in MENU → Geotagging → Settings → GPS data preview. If the frame and the gimbal look north, yaw should read about 0°. With an Emlid connected to the ENTIRE, only the Emlid position is used (the Cube is used for attitude and heading), so the Cube's own GPS offsets no longer matter.

offsets

Copy link

RTK, Emlid and external GPS

The ENTIRE writes whatever position the autopilot provides (or an external NMEA/ERB source) – no corrections, only the lever-arm offsets. Connect an Emlid (or any NMEA receiver) via an UNI port in the matching mode, share GND, and the ENTIRE uses it automatically. A GNSS height mismatch of tens of metres is almost always geoid vs ellipsoid or the CRS in the stitching software. The hotshoe wire can be shared with an Emlid's event input (GND and MARK only; its 5 V pin is not needed).

Documentation: EMLID connection

RTKEmlid

Copy link

Does the ENTIRE support PPK?

No. ENTIRE was built to save time by writing tags directly, so raw RTK data for post-processing are not recorded. PPK was long planned but not implemented in R3. You can use the ENTIRE together with another PPK source (Cube logging or Emlid) by sharing the hotshoe pin and GND, then choose EXIF tags or PPK. TAG-E offers a Propeller-format PPK output.

PPK

Copy link

MAVLink & flight controllers

Which flight-controller port and baud rate should I use?

Telem1 / Telem2 are strongly preferred. GPS2 works but is not recommended (serial bandwidth may be limited, and the connector has a different pin count so the cable must be reworked). Reference rates:

  • Cube to Gremsy COM2: 921 600 bps; Gremsy COM4 to ENTIRE: 230 400 bps.
  • Cube directly to ENTIRE: 500 000 bps (1 250 000 on capable boards). HereLink air unit: 115 200.
  • All SRx stream parameters 0: the ENTIRE requests what it needs. Extra streams overload the link and change the GPS delay.

If a platform can only do slower speeds, use 500 000. Reboot the Cube after any baud change, and check the right port number.

MAVLinkbaud

Copy link

ArduPilot configuration basics

With ArduPilot most things work by default: the ENTIRE appears as a camera component, the Cube generates trigger commands itself (no PWM or SBUS wiring needed for photos) and heartbeats are exchanged. CAM1_TYPE must be 5 for the ENTIRE; any other value blocks Trigger camera NOW. Use the installation manual for your gimbal. Inspect the MAVLink Inspector for the gimbal heartbeat if the ENTIRE reports "MavLink online" but no gimbal.

ArduPilot

Copy link

Using the ENTIRE with PX4

  • No dedicated manual: follow the TAG-E PX4 manual, which has the same settings. The serial port must be in Onboard mode, MAV_x_RATE = 0, reboot everything.
  • Start at 230 400 bps; set UNI-B/C of the ENTIRE to MAVLink, SER_TELx_BAUD equal, MAV_1_MODE = Onboard. The ENTIRE shows UNI-B/C "ONLINE".
  • PX4 does not forward GCS data to a device on a port by default. If you cannot modify PX4, put a MavPorter on the telemetry link (as done for Alta X).
  • CAN devices flooding MAVLink can stop parameters from loading; this is a PX4 behaviour. See the TAG-E FAQ for details and the PX4 routing fix.

PX4

Copy link

"Camera stopped transmitting" or intermittent connection

The connection to the camera or controller was interrupted. This is almost always a wiring or connector fault, not software. Re-seat and test every connector first.

heartbeat

Copy link

Missing triggers in missions

The most common cause is a telemetry port that is too busy: when the link between the Cube and the gimbal (shared with the ENTIRE) is more than about half full, the autopilot starts losing messages, including some trigger commands. Use 921 600 bps from the Cube to the Gremsy and switch off data streams you do not need (a gimbal can add several fast streams on its own). Other causes: autofocus fails so no photo is taken (try MF, or a longer fixed AF time in the ENTIRE menu, from 100 ms), or a bad contact.

triggersbaud

Copy link

MavCam, Mission Planner plugin, QGC and UgCS

  • MavCam (Android app for HereLink/SIYI) gives camera panel, exposure controls and the dump LOG button. The ENTIRE's MENU → Miscellaneous → MavCam options lets you hide features per payload (MavCam 2.17 + firmware 1.908 and newer). A yellow sliding line under the trigger button means MavCam is not connected to the ENTIRE.
  • Mission Planner plugin: copy the .cs file to the plugins folder (see airpixel.cz/docs/missionplanner-camera-control-plugin/); after a Mission Planner update download the current plugin again (older MP such as 1.3.74 worked as a fallback). No MENU or arrows in the plugin.
  • QGC dropped plugin support. Use the AirPixel desktop application: start it first, connect to the drone until it shows "Run QGC now", then launch QGC.
  • UgCS with MavCam needs a different UDP port (documentation: Herelink camera control, step 7; port 14562 bypass).
  • Own software: every control is available via MAVLink; see the serial/MAVLink API pages and ask for the missing bytes.

Documentation: HereLink camera control · Mission Planner plugin

MavCamQGCMP

Copy link

When should I use MavPorter?

MavPorter shares one MAVLink telemetry line between several devices. Typical uses: PX4 without ground-station forwarding, or an ENTIRE and a gimbal that must share a single autopilot port. Set NO_OWN_DTA on the gimbal and camera ports (the Gremsy may misbehave otherwise) and use firmware 21 or newer. See the MavPorter section.

Documentation: MavPorter docs

MavPorter

Copy link

Gimbals (Gremsy & others)

Gremsy wiring and firmware

  • Pixy-S / Pixy-LR: only one Pixhawk cable, shared with the gimbal's quick release. Gremsy COM4 goes to the ENTIRE UNI-A (via the AUX cable), COM2 to the Cube. Set COM2 921 600, COM4 230 400 in gTune, click REBOOT, wait.
  • Gremsy firmware must be recent: version 773 (early 2024) or newer is needed so MAVLink is forwarded from the Cube to the ENTIRE; older firmware loses the GPS stream. Releases in the 7.8.x line were used in AirPixel's own tests.
  • Disable all "Gremsy options" in the ENTIRE when using the new-style wiring; no UNI-to-Cube connection.
  • A faulty Pixy S cable set batch had swapped serial wires; photos of the connections help.
  • If the Cube says Mount not healthy there is no gimbal heartbeat on the Cube link, an issue between the gimbal and the Cube, not the ENTIRE. Unplug the ENTIRE and solve it first.
  • Faulty quick-release: measure resistance between the CTRL pins (no short) and replace the QR if needed.

Documentation: Gremsy Pixy-LR installation · Gremsy Pixy-S installation · Gremsy EVO T3/S1/T7

Gremsy

Copy link

Two valid wiring topologies for Gremsy

New style (with ArduPilot gimbal control): Cube —921 600— Gremsy COM2; Gremsy COM4 —230 400— ENTIRE UNI. Old style: Cube —500 000— ENTIRE UNI-B (MAVLink); ENTIRE UNI-C/A (mode Gremsy) —230 400— Gremsy COM2. Do not mix; MAVLink forwarding as a workaround for gimbal control costs MavCam control and causes more problems.

Gremsytopology

Copy link

The gimbal drops offline when yaw is centred

Typically the gimbal link is overloaded because two things control the gimbal at once: MNT_TYPE is set for MAVLink control from the Cube while the ENTIRE is in Force SBUS mode. Turn off MNT_MODE. Optionally set a fixed attitude stream in the gimbal's MAVLink settings. Then send an ENTIRE log that covers the gimbal going online, offline and online again.

Gremsy

Copy link

The gimbal switches to MAVLink mode and I lose HereLink control

New Gremsy firmware switches to MAVLink mode as soon as the drone is connected; this cannot be avoided. With Force SBUS the ENTIRE puts the gimbal back to SBUS control (not HereLink mode, so SBUS channel mapping in gTune applies). A known-good combination: Gremsy 7.5.4, all "Gremsy options" off, and "Gimbal control" in MavCam settings off (otherwise it overrides SBUS). Mixing MavCam gimbal control with SBUS confuses the gimbal; use the MavCam Joystick option or don't mix. MavCam's joystick takes exclusive MAVLink control until the hand icon is pressed.

GremsySBUS

Copy link

Gimbal pitch does not follow waypoints

Waypoint gimbal commands do not reach the gimbal when the ENTIRE sits between the Cube and the gimbal. Do not use MAVLink forwarding as a workaround, it causes more problems. Go back to the standard wiring and control the gimbal with SBUS or MAVLink; with current firmware and MavCam the gimbal can be driven completely by joystick. Horizon or roll drift is normally a gimbal or ArduPilot tuning issue, not the ENTIRE.

Gremsymission

Copy link

DJI Ronin, Movi, Freefly and other gimbals

  • DJI gimbals accept no third-party data; the only way is a "hanging wire" from the camera position to the drone (Universal geotagging set, rotation is not blocked, only rewind after a shot).
  • Movi Pro and others: ENTIRE sits at the camera; connect Extension Box on the drone for DJI API and PWM.
  • Gimbals without a yaw axle report only relative yaw; the Pixhawk supplies the heading.

gimbal

Copy link

Sony cameras

Only some Sony functions work (Menu, Display, arrows do nothing)

Only shutter speed, aperture, ISO, Photo and Video travel over USB. More than half of the Sony commands are sent by IR. Attach the IR LED (second connector on the HotShoe unit if fitted) and enable Remote Ctrl → ON in the camera (default OFF). Avoid direct sun on the sensor or LED; tape the LED to the camera with black tape. In sunlight use BURST (via SmartPlug) instead of PHOTO.

SonyIR

Copy link

Mass Storage vs PC Remote: which USB mode?

They are mutually exclusive. For control set USB → PC Remote Function → ON. For geotagging the camera must be in Mass Storage; then no USB or WiFi control, only IR commands. (The ILX-LR1 control uses USB; "USB control" is the correct mode for it.)

SonyUSB

Copy link

The trigger does not fire

Most often a non-Multiport cable. Use the official Multiport cable, which connects every pin. A working trigger does not prove that USB is fine: the trigger can work while the USB data link is dead. Cameras without a multiport (ZV-E10, A7R V) cannot be triggered outside PC-remote USB mode and so cannot be geotagged with the standard set; see the A7R V item.

SonyMultiport

Copy link

Trigger AF, AF time, repeated shots

  • "Trigger AF" is a shutter half-press. Check that AF-on-half-press is not disabled. A focus failure can silently prevent the photo; test in MF.
  • The ENTIRE menu has a fixed AF time (100 ms and up) that gives the camera time to focus before the shutter.
  • The camera answers "Access Denied" when triggered before the previous frame is saved; this is camera behaviour and cannot be avoided.
  • To speed up repeated shooting enable Disconnect USB on MENU and Don't reconnect USB after photo (a reconnect takes about 2 s).
  • Automatic trigger interval can go below 1 s (down to 0.7 s) in newer firmware.

SonyAF

Copy link

ILX-LR1 setup choices: WiFi or LR Expander

Two options (both give geotagging; the ENTIRE R3 is required):

  • USB + GPIO + WiFi (no opening of the camera): full exposure control, photo triggering by GPIO, video start/stop from photo mode. No MENU/navigation by WiFi. The camera must be in M mode, and re-paired after every ENTIRE update. Minimum for trigger and geotag only: wire TRIGGER, FOCUS and EXPOSURE.
  • LR Expander (module installed in the camera, MAVLink to the ENTIRE): no WiFi, MENU/navigation available (OK enters the menu, AF leaves it). Exposure compensation cannot be set in M mode; the custom-key mapping of the camera must follow the manual exactly. Without WiFi video needs the camera switched to video mode by hand. The "for ENTIRE R3" cable set is required.

Camera hints: update the camera to its latest firmware, reset it to default, let the ENTIRE finish connecting (a few minutes at first); the top banner then shows "ILX-LR1". The ENTIRE uses USB for geotagging and WiFi or the Expander for control; the WiFi variant does not need the camera opened.

Documentation: Sony LR1 control · LR1 Expander

LR1Expander

Copy link

A7R V, ZV-E10, A1, FX3, FX6

  • A7R V: no IR sensor; controllable through USB. Bracketing works. MENU/arrows are unavailable without IR; the A9 SmartPlug can replace parts of it. Rev 2 firmware is closed.
  • ZV-E10: no multiport, cannot be triggered outside PC-remote; no geotagging. Full control works when geotagging is disabled.
  • A1: works with the USB-C cable after updating the ENTIRE; IR mount not tested.
  • FX6: LANC zoom has 10 speeds; needs SBUS control for zoom.
  • FX3 / FX30: LAN control works well.

SonyA7R5

Copy link

Other camera brands

Which other cameras can the ENTIRE control?

  • Nikon Z6II / Z7 / D850: Z7 is nearly plug-and-play; D850 needs workarounds (movie mode via the mechanical switch, no focus point move). Check Nikon body firmware: early revisions have broken tethering. Nikon has no Mass Storage, so no EXIF geotagging (use EventTEXT).
  • Canon R5 / R3 (CCAPI): WiFi only. Enable the Camera Control API (Canon tool, or the ENTIRE UI procedure) once over USB; then use WiFi. BURST is not implemented in CCAPI. C80 and LANC models: no ISO.
  • Phase One iXM: via the iXM mode; the camera geotags itself from MavLink-to-NMEA; live-view zoom, focus slider in MavCam; no file-name feedback. Phase One's own sync cannot be combined with iXlink and occupies both serial ports.
  • Fujifilm GFX 50S / 100 / 100S / 100 II: wired cable; the ENTIRE disconnects USB before a REMOTE-jack shutter, hence a delay. Enable Don't reconnect USB after photo. The GFX 100 II has a 3.5 mm jack and is not fully tested; pulling the plug slightly out has helped some users. Video via the camera switch.
  • Blackmagic BMPCC 4K / 6K / 6K Pro: Bluetooth pairing (tested up to camera firmware 8.1) or, preferably, wired USB-C. No ND control. Pairing hint below.
  • RED KOMODO / V-Raptor: serial RCP2 cable (includes the RED licence) or WiFi; menu/custom keys are not available from RED; shutter-speed remote has been a known issue.
  • Z-CAM: USB (set the ENTIRE to LAN mode, camera USB to network mode) or WiFi. Shutter angle and live-view zoom are supported; zoom is not proportional. LANC not recommended.
  • Panasonic GH3 / GH4 / GH5 / GH5s / S1 / S1H / BGH1: WiFi only. GH3 cannot run HDMI and WiFi together.
  • Thermal (Workswell Wiris, ViewPro): EventTEXT geotag; Wiris needs a customised SBUS-out cable to press its buttons; ViewPro has no arrow navigation, use the on-screen joystick.
  • Not suitable: Sigma fp-L (rolling shutter, no mechanical shutter) for mapping.

Documentation: Canon R5 CCAPI · RED · Fuji GFX · PhaseOne iXLink · Z-CAM · Panasonic WiFi · Wiris · ViewPro

camerascompatibility

Copy link

Blackmagic Bluetooth pairing fails

Pairing is sometimes tricky. Try: BT reset at the bottom of the ENTIRE menu, reboot, remove all pairings from the camera, scan again. The ENTIRE does not scan while a browser is connected to its GUI; close it and wait 20 to 30 seconds. Switching the camera off while it is listed breaks a retry loop. Newer BM camera firmware is incompatible with the original BT dongle; wired USB-C is more stable and was recommended in 2024.

BlackmagicBT

Copy link

Time-lapse

Hold the TL button for a second; ZOOM buttons set the delay. Interval is shown as battery percentage on A7 SmartPlug cameras. On A7 third series, A9 and the Entire the percentage is not visible due to Sony changes: count presses of zoom-down until empty is shown (1 s), each press up adds a second. The ENTIRE also has its own timed or distance trigger. Several synchronised cameras: use one main ENTIRE as the trigger source and the others for geotagging only.

timelapse

Copy link

Firmware & licences

Firmware update hangs at "Decompressing 99%"

Not necessarily a failure; it can sit there several minutes. If no "Start" message arrives within 5 to 10 minutes, reboot and upload again. Try another PC, phone or browser if the page misbehaves. After the update re-upload the validation package if requested and wait a few seconds for the confirmation. After any update re-pair the LR1 or Sony WiFi camera. Firmware page: airpixel.cz/docs/firmware-update/ (R3, latest 2.043 of 1 October 2026; R1 and R2 use a different package). Official steps: join the ENTIRE hotspot, open http://entire, MENU → Firmware, pick the unzipped .img, confirm. The LED turns purple while memory is rewritten (do not interrupt; a power failure can damage the unit) and red when it restarts and self-checks. Downgrading is possible but rarely helps.

Firmware updates over MAVLink are possible but slow (30 to 40 minutes) and less reliable than WiFi.

Documentation: ENTIRE R3 firmware update

firmwareupdate

Copy link

Licences and upgrades (RED, Panasonic BS1H, and others)

Feature upgrades are bound to one ENTIRE. In MENU → About generate the request code (use the "send by email" button or copy the code from a device with a mail client), send it with your order, and paste the validation / upgrade code you receive into the unit. Cables may be moved between units; the licence stays with the unit. Some new firmware features need a hardware genuineness validation pack.

Documentation: HW authentication

licenceRED

Copy link

Before you write to support: collect this

Covers TAG-E (tag-e.net): the newer controller for the Sony ILX-LR1 that needs no WiFi. If you open a web page on the unit's own hotspot, you have an ENTIRE.

  • Firmware versions: TAG-E, camera (must be 2.01 or 3.00), gimbal, autopilot, ground software
  • Processing log: empty file savedump on a microSD in the running TAG-E, no reboot
  • TAG-E parameter list and the Messages tab after boot
  • Photos of the wiring, especially the EXPOSURE wire and IO connector
  • Does the unit blink blue after each photo? (yes/no)

Basics & differences

What is TAG-E and how is it different from ENTIRE R3?

TAG-E is the newer AirPixel controller, designed for the Sony ILX-LR1. It has the same housing and connectors as the latest ENTIRE hardware, so it can replace an ENTIRE in a Gremsy Pixy LR SP.

  • One USB-C cable carries both camera control and geotagging. No WiFi control, no LR Expander.
  • Instant geotagging: nothing to start. As soon as the status LED is green, every photo you take is recorded and gets its position when the drone lands.
  • No WiFi at all. You configure it with MAVLink parameters in Mission Planner or QGC and update it from a microSD card.
  • Works with the MAVLink camera control panel of QGC and Mission Planner without any plugin. MavCam is optional.
  • Also included: camera clock setting, camera MENU and navigation, video start/stop while in photo mode, geotagged video and a separate folder for every flight.
  • One unit controls and geotags one camera.

overviewLR1

Copy link

Which cameras does TAG-E support?

Geotagging and full control are made for the Sony ILX-LR1. It needs camera firmware 2.01 or 3.00 (see Camera setup).

With another camera TAG-E works in a reduced mode: you get remote control but no geotagging, and QGC hides the geotagging controls. Tested on an A7R IV: ISO, aperture, shutter speed, exposure compensation, AF trigger, AF mode, image resolution and photo trigger work; switching the exposure mode does not, and video start/stop depends on the camera. Treat this mode as experimental and update the camera firmware first.

LR1cameras

Copy link

Should I buy TAG-E or ENTIRE R3 for an ILX-LR1 build?

For new ILX-LR1 builds AirPixel recommends TAG-E: far less configuration, no WiFi link and simpler wiring. Choose ENTIRE if you need other camera brands, SBUS-style cinema control, Link remotes or EventTEXT logging for non-Sony cameras.

  • Pixy-LR (standard): TAG-E plus the Connection set for Pixy-LR (TAG-E).
  • Pixy-LR-SP (ENTIRE built in): TAG-E alone replaces the ENTIRE; move the COM4 wire to IO-B.
  • Gremsy T3 V3: TAG-E plus the EVO wiring set.
  • Camera on a table or your own mount: TAG-E plus the USB-C cable and the exposure wire.

buyingGremsy

Copy link

Can one TAG-E handle two cameras, or can I run TAG-E and ENTIRE in one system?

One TAG-E per camera. Several units can work in one ArduPilot system if each has its own MAVLink component ID (parameter MAV_COMP_ID, 100 to 105, default 100). TAG-E and ENTIRE can share one MAVLink line, but MavCam cannot handle both at once.

To change the ID: write MAV_COMP_ID, reconnect Mission Planner (the unit now answers under the new ID), then write FW_SAVE_CFG = 1 on its own.

multi-cameracomponent id

Copy link

Camera setup

The camera is not detected or there is no USB link. What camera mode is needed?

TAG-E uses USB for everything: without a USB link nothing works.

  1. Set the camera USB connection to PC Remote (not Mass Storage) and switch the camera off and on.
  2. If the camera says Cannot recognize this USB cable, turn the USB-C plug of the TAG-E harness around. This is a known quirk of the cable.
  3. Check the cable is fully seated at both ends.

When the drone lands, the camera briefly shows its Mass Storage screen while the geotags are written; this is normal.

SonyUSB

Copy link

Which camera firmware does TAG-E need?

Use the latest Sony firmware. Versions 2.01 and 3.00 are supported. The first 1.x releases are unusable, and 2.00 caused crashes when geotags were written. Many problems (camera stops writing, no controls, geotagging failing) disappeared after the camera was updated.

With an older camera firmware TAG-E reports Camera FW unsupported (x.xx)! in its messages.

Sonyfirmware

Copy link

Which camera settings must I check before geotagging?

  • Photo mode at all times. Movie mode on the dial gives unexpected behaviour.
  • S, A or M exposure mode if you want to control exposure. In iAuto the exposure controls are hidden.
  • Autofocus: AF-S or AF-C, and the lens AF/MF switch on AF. The camera decides how long to focus.
  • Save format: JPG, JPG+RAW or RAW-only all work with current firmware (older TAG-E releases could not tag RAW-only, so update). JPG+RAW is the safest choice.
  • Nothing to set for the save destination: TAG-E puts the camera to "camera only" every time it connects. If the camera refuses, you see Image Save Dest. error! and no photo is taken until it is fixed.
  • Default file naming and folders (DCIM/100MSDCF). If the camera still has custom image info or naming from earlier use, reset it with Initialize.

Sonysettings

Copy link

Which SD card should I use, and can old photos stay on the card?

Format the card in the camera (menu Format) before the first test. 128 GB cards are used in AirPixel's own tests.

Which photos get geotagged: every photo taken since TAG-E connected to the camera, up to the moment of landing (or Write EXIF). Photos from earlier flights, earlier days or other folders are left untouched, so the card does not have to be empty. If you take test photos on the ground after power-up, make sure the TAG-E blinks blue for each of them; otherwise the positions of the following photos can end up shifted.

The message GTG Log file error! means there is a photo for which no position was recorded. There is no limit on photos per flight (the largest test was about 1 000), and the camera's 9999 counter roll-over and new folders are handled.

SD cardfolders

Copy link

Wiring, power & LEDs

What has to be connected to a TAG-E?

  • USB-C to the camera.
  • EXPOSURE (capture detection) wire from the camera's 6-pin multi connector to TAG-E USB pin 2. The Trigger and Focus wires are not needed.
  • 5 V power (use the AirPixel Power adaptor / uBEC, input 7 to 23 V).
  • MAVLink on IO-B, directly from the flight controller or through the gimbal. The default speed is 921 600 bps on all IO ports (units with older firmware: 230 400).
  • Leave the EXT port (named PPS) empty unless you really use PPS.

Pinouts: see the TAG-E pages of the documentation. An early drawing of IO-B had the wires reversed; it was corrected in October 2025, so use the current version.

Documentation: TAG-E pinouts · Direct camera connection

wiringEXPOSURE

Copy link

What do the TAG-E LEDs mean?

  • Blue – starting up, or no camera connected yet.
  • Solid green – camera connected and ready. Your photos are being recorded for geotagging.
  • Short blue blink after each photo – the capture was detected. If you never see it, geotagging cannot work.
  • White blink – a command was received.
  • Fast red blinking – the last geotagging run ended with errors (check the messages and send the log).
  • Alternating green and red – the camera went offline during a run.
  • Fast purple blinking, then solid purple – firmware update running: do not touch the unit. Solid blue right after an update attempt means the update failed.
  • Red SD-card LED – the unit is using its microSD card (log, update, validation, settings file). Remove the card after the LED goes off.

Some older documentation pages said blue for "camera ready". Green is correct.

LEDstatus

Copy link

How should TAG-E be powered?

TAG-E needs a solid 5 V and draws about 1 W. Use the AirPixel Power adaptor (7 to 23 V in), one per unit; it can sit directly on a 3S to 5S battery. 6S (25.2 V) is above the limit. A 5.3 V BEC is acceptable. The Gremsy QR output can be noisy, so it is not recommended, although it will not damage anything.

Do not cut the power during a firmware update: it can corrupt the unit (see the recovery question).

poweruBEC

Copy link

Random behaviour, unit offline, missing triggers. Where do I start?

In the vast majority of reported cases it was a connector. TAG-E's connectors are small and easily end up slightly crooked or not fully inserted, and pins can bend. Typical symptoms: the unit starts but never receives MAVLink (RX wire missing), or photos are only missed in flight (vibration).

  1. Re-seat every connector and inspect the pins of the IO and USB sockets.
  2. Wire TX to RX and RX to TX on the chosen telemetry port. When it works you see Mavlink connected!, GPS OK! and ATTI OK!; GPS lost!, ATTI lost! or Too high! point to the link or to too many streams.
  3. Wiggle the harness while watching the LEDs (the blue blink on each photo).
  4. To rule out a bad IO port, set IO-C as MAVLink: IOC_MODE = 1, IOC_BAUD = 9216 (baud values are in units of 100 bps: 9216 = 921 600, 4608 = 460 800; these two need firmware 0.193 or newer), then FW_SAVE_CFG = 1.

troubleshootingconnectors

Copy link

How long can the UART cable be?

A 24-hour test at 500 000 bps over 4 m of unshielded cable (20 connectors in series) ran without data loss. For a real installation a shielded 1 to 2 m cable is very reliable. The MAVLink side can be long; keep the USB and exposure wires short and fixed near the camera.

cableUART

Copy link

Flight controller (ArduPilot / PX4)

How do I connect TAG-E to ArduPilot?

  • Use a telemetry port set to MAVLink as in the installation manual, with the matching baud rate (see below). Mission Planner then shows the camera and the TAG-E messages in the Messages tab after boot.
  • CAM1_TYPE = 6 (MAVLink Camera v2). The type 5 used for ENTIRE does not work with TAG-E.
  • The documentation is written for ArduPilot 4.6. Older or custom builds usually work, but may need the camera addressing change from ArduPilot pull request #30517 for trigger commands to reach the TAG-E.
  • All SRx stream parameters can stay at 0; TAG-E asks for what it needs.

To keep a changed TAG-E parameter, write FW_SAVE_CFG = 1 as a separate write, never together with other values.

Documentation: TAG-E ArduPilot connection

ArduPilotCAM1_TYPE

Copy link

Which baud rates should I use?

  • From firmware 0.193 TAG-E supports 921 600 and 460 800 bps and uses 921 600 as the default on every port. After updating, set all your links to 921 600.
  • Cube to Gremsy COM2: 921 600. Gremsy COM4 to TAG-E: 230 400 (the Gremsy limit). If you change the Gremsy COM4 baud, change TAG-E to match.
  • Cube directly to TAG-E: 921 600 (500 000 on older firmware).
  • Platforms limited to 500 000: first set the TAG-E to 230 400, switch the flight controller to 500 000, then save the TAG-E configuration.
  • Ground link: 921 600 where possible. HereLink air units offer it; SIYI air units top out at 115 200.

baudGremsy

Copy link

What is the setup for PX4?

  • Set the port used by the gimbal / TAG-E to MAV_x_MODE = Onboard (no other mode works), MAV_x_RATE = 0, forwarding enabled, and MAV_x_CONFIG to that port.
  • Set SER_TELx_BAUD to the TAG-E rate (230 400 through a Gremsy, otherwise the rate set in TAG-E).
  • Reboot everything, including the gimbal.
  • Use a current PX4 release or daily build. It includes AirPixel's fix for parameter loading through a gimbal (pull requests #25650 and #25651); older builds may not load TAG-E parameters in QGC.

Mission triggering is most reliable with time-based triggering (TRIG_MODE = time). Trigger by distance needs TAG-E firmware 0.148 or newer.

Documentation: TAG-E PX4 connection

PX4QGC

Copy link

QGC loads parameters very slowly or never when TAG-E is connected (PX4)

Check these in order:

  1. Logic level: a telemetry module with 5 V logic instead of 3.3 V can lock the Gremsy to PX4 link once connected.
  2. DroneCAN devices (CAN GPS, optical-flow or rangefinder nodes) flood the MAVLink link and PX4 cannot filter them. Disconnect them to confirm.
  3. PX4 version: use a build with the AirPixel routing fix (see the PX4 setup question).
  4. Link bandwidth: low ground baud, throttling (MAV_x_RATE) or Bluetooth emulation on the controller. Test over USB or UDP from a PC.
  5. If the camera panel is missing after a TAG-E update, delete the cached files in Documents/QGroundControl/Parameters.

If it still stalls, send support the log (see Firmware, logs & recovery).

PX4QGCCAN

Copy link

Which camera commands does TAG-E accept from the autopilot?

TAG-E answers the standard MAVLink camera commands: take image (single, interval and count), stop capture, start/stop video, trigger by distance and trigger by interval. Current ArduPilot together with current TAG-E firmware triggers from Do Action, Trigger camera NOW and the AUX function. While a distance trigger is running, other capture commands are answered as temporarily rejected.

If an older setup ignores triggers from the AUX function or the map menu, update TAG-E (a fix for commands sent without a target was released in June 2025) and use an ArduPilot build with pull request #30517.

triggerArduPilot

Copy link

Can TAG-E share a port through a MavPorter?

Yes. Run the flight controller to MavPorter at 921 600 and MavPorter to TAG-E at 500 000 (or the TAG-E rate). Use the latest MavPorter firmware with smart routing, switch off forwarding between devices that must not see each other (for example ADS-B to TAG-E) and set PRTx_NO_OWN_DTA = 1 on the gimbal and camera ports. See the MavPorter section for details.

MavPorter

Copy link

My other MAVLink device (Remote ID, ADS-B) stopped working after connecting TAG-E

TAG-E asks the autopilot to stop sending data it does not need, because unwanted data can overload the link. On a custom stack this can also stop messages another device relies on; an example was a Remote ID module on a CubeID system. Tell support if a device on the same line is affected. Also make sure your ground software addresses autopilot requests only to component 1.

To make TAG-E quieter on screen use MAV_HIDE_MESGS: 0 default, 1 errors only, 2 everything as info, 5 none.

Remote IDstreams

Copy link

Gremsy & other gimbals

Which wiring options exist for Gremsy Pixy-LR / Pixy-LR-SP?

New style (recommended): Cube —(921 600)— Gremsy COM2; Gremsy COM4 —(230 400)— TAG-E IO-B (mode 1). The gimbal passes the MAVLink data on to the TAG-E and ArduPilot controls the gimbal. On the Pixy-LR-SP just move the former ENTIRE COM4 wire to IO-B; nothing else changes.

Old style: Cube —(500 000 or 921 600)— TAG-E IO-B (mode 1); TAG-E IO-C or IO-A (mode 6 = Gremsy) —(230 400)— Gremsy COM2. TAG-E then also controls the gimbal (see below).

The "EVO" cable (COM2 plus COM4 forward) is the more future-proof choice. MAVLink pass-through through TAG-E can overload the link when ArduPilot gimbal control is used as well.

Only one IO port can be MAVLink: if you set IO-C to MAVLink, IO-B is switched off, and Mission Planner loses the unit until you reconnect.

Documentation: Pixy-LR set (ArduPilot) · Pixy-LR set (PX4) · Gremsy T3/S1/T7

Gremsywiring

Copy link

How do I control the Gremsy gimbal through TAG-E (SBUS or MAVLink)?

This is for the old wiring style. In the new style ArduPilot controls the gimbal, and MavCam or QGC can drive it directly.

  • Set the IO port connected to the gimbal to mode 6 (Gremsy). Port modes (IOx_MODE): 0 off, 1 MAVLink, 2 MAVLink pass-through, 3 NMEA in, 4 NMEA out, 5 Basecam, 6 Gremsy, 7 LightWare rangefinder, 8 Emlid ERB, 10 Action Button.
  • Commands via MAV_CMD_DO_DIGICAM_CONFIGURE, param1: 3001 set tilt (param6 = angle), 3002 back to SBUS mode, 3003 look down, 3004 toggle motors, 3005 look at the horizon, 3006 tilt speed (param6), 3007 yaw (param6), 3008 yaw speed (param6), 3009 yaw and tilt speed (param5, param6), 3030 lock/follow ratio (param7). Every command except 3002 switches the gimbal to MAVLink control; 3002 hands it back to SBUS.
  • Yaw can only be set in lock mode, so 3009 puts the gimbal in lock mode.
  • No hidden options need to be switched on in current firmware.

GremsySBUS

Copy link

Does TAG-E work with BaseCam / SimpleBGC gimbals?

Yes, from firmware 0.123 to 0.126. TAG-E recognises the gimbal automatically; allow 10 to 15 seconds after power-up before the angles are available. The gimbal must boot with its yaw aligned with the airframe, because BaseCam reports yaw relative to where it was when it started. Angles are written as 0° for nadir and 90° for the horizon.

BaseCamangles

Copy link

Geotags contain NaN or yaw is wrong

  • A gimbal that reports invalid yaw values (for example a two-axis Pixy-LR set up as three-axis) can make the coordinates NaN. Check the mount type.
  • The yaw written in the photo is the real compass heading of the camera. Check it in the real world (nose to north: about 0°; turned south: about 180°), not against the gimbal's own yaw display, which starts at 0 at every power-up.
  • With a Pixy-LR-SP, tags once showed airframe instead of gimbal attitude. This was fixed in firmware 0.159; update if you see it.
  • Calibrate the autopilot compass before comparing headings.

anglesyaw

Copy link

Geotagging

How does geotagging work, and how can I test it on the ground?

While the status LED is green, every photo you take is recorded together with the position and camera attitude. When the drone lands, or when you ask for it, the data are written into the photos on the camera card. A running video recording is stopped automatically at that moment, and the camera briefly shows its Mass Storage screen.

Bench test (no GPS fix and no flight needed): power everything, wait for green, take 3 to 5 photos and check that the TAG-E blinks blue after each. Then click EXIF > Write now in QGC (or in the Mission Planner plugin; the parameter is TG_WR_EXIF, which must be exactly 1). You see GTG start..., Found n photos! and GTG done!. Without a GPS fix the coordinates are zero, but you can see that the files and folders are created.

Photos of every flight are moved into a new date-named folder on the card (FLD_NEW_ENABLE, default on; FLD_NEW_FORMAT chooses one of four folder names, default DDMMYYYY_hhmmss) and numbered IMG_0000.jpg onwards (FLD_REN_FROM_0, default on). Files are never copied. The camera's own play mode does not show these folders; look at the card on a PC.

Documentation: Parameter description

EXIFbench test

Copy link

I get "GTG no logs to process!" or "GTG - no captures!"

"GTG no logs to process!" – TAG-E did not see any photo being taken, so there is nothing to write. (Older firmware called this no JPG to geotag.) Check:

  1. EXPOSURE wire: bad contact or wrong pin. It belongs on USB-port pin 2, not on the EXT/PPS port. A short blue blink after each photo proves it works. Loose contacts that only fail in flight are typical; wiggle the connector.
  2. GTG_PPS_ENABLE is on but no PPS signal exists. Switch PPS off while commissioning.
  3. Only video was recorded (video is not counted as a photo).
  4. If the blue blink is missing, try the camera's mechanical shutter.

"GTG - no captures!" – photos were recorded, but TAG-E found no images on the camera card. Check that the card works (format it in the camera, try another card), the USB cable and its polarity, that the camera firmware is 2.01 or newer, and that no Image Save Dest. error! was shown.

Related messages: GTG mount error! (the camera would not open its card), GTG init error! (gave up after repeated tries), GTG Log file error! (a photo without a recorded position). After such errors the unit saves a log you can send to support (see Firmware, logs & recovery).

EXPOSUREtroubleshooting

Copy link

Photos get the wrong date, or the folder name shows 2019 / a wrong time

Folder names and the camera clock take their time from the flight controller. If you take off before a good GPS time has arrived, the date can be wrong (for example 2019). Wait for the message TAG-E: Time synced (mav) before flying. A bug that applied the time-zone setting TIME_ZONE_OFF twice was fixed in October 2025. TAG-E also sets the camera clock after connecting.

timefolders

Copy link

Which GPS data does TAG-E use? How do I get RTK-quality altitude?

  • By default the autopilot's fused position is used (50 Hz). Its altitude is height above mean sea level.
  • MAV_GPS_RAW = 1 uses the GNSS fix directly (lower rate, but it is the true RTK-corrected position; TAG-E fills in between samples). Recommended with an RTK system.
  • MAV_GPS_ELIPSO = 1 (spelled MAV_GPS_ELLIPSO in the online parameter list; use the name your unit shows) writes the ellipsoidal height instead of mean sea level. It is on by default on new units; units upgraded from older firmware keep 0 until you change it.
  • RTK corrections reach the GNSS through the autopilot (NTRIP / MAVLink injection). TAG-E writes the position it receives and only adds the camera and antenna offsets.

If the processed model is off by tens of metres in height, compare with the altitude in the autopilot log and check the coordinate system and geoid in your photogrammetry software.

GPSRTKaltitude

Copy link

Can TAG-E use an external RTK receiver (Emlid, Here)?

Yes. The flight controller combines its GPS inputs into one stream, so you cannot pick GPS2; instead connect the receiver's NMEA output to TAG-E directly: receiver TX to the RX of IO-A, B or C (mode 3 NMEA in, or mode 8 for Emlid ERB), and share GND. A receiver with a free output port is best, for example an Emlid Reach. TAG-E then uses the external GPS and falls back to the MAVLink GPS if the external data stop. Make sure the flight stack does not change the baud rate or protocol on a shared GPS port.

A rangefinder (for example Lightware) goes on IO-A or IO-B in mode 7; its distance is written into the geotags.

RTKEmlidrangefinder

Copy link

How do I set the camera and antenna offsets and the GPS delay?

  • OFF_ANT->MNT_X/Y/Z: distance from the flight controller position to the gimbal mount. OFF_CAM->MNT_X/Y/Z: distance from the mount to the camera. Set ArduPilot's own GPS position (GPSx_POS) correctly first, and watch the sign of each value: a wrong sign easily gives 30 to 40 cm of error. The recent firmware has a QGC offset preview to check the values in use.
  • A camera mounted with a 45° rotation has no single answer for all three axes: use MNT_YAW_OFF and test.
  • If roll/pitch/yaw is 90° off in Pix4D or Metashape, set MNT_PITCH_OFF to +90 or -90, depending on the mount.
  • GPS delay matters more than anything else for accuracy. Fly lines at about 10 m/s in opposite directions with RTK fix, process them, read the shift along the flight direction and enter it in MAV_LINK_DELAY (about -300 to +300 ms; the starting value differs between firmware versions). The procedure is the same as for the ENTIRE (see its FAQ). Do this before using GTG_GPS_ACCU / GTG_IMU_ACCU, which are not recommended for production because wrong accuracy values can mislead stitching software.

Documentation: GPS delay calculation · GPS to camera offsets

offsetsdelayaccuracy

Copy link

Does TAG-E support PPK?

Yes, as an export. GTG_PPK_ENABLE = 2 shows the extra PPK settings in QGC (manufacturer, model and serial); after setting them use 1 to keep the export but hide the settings. TAG-E writes a Propeller-format text file (file name, time stamp, GPS, attitude) to the camera card, with a backup on the TAG-E microSD. Other PPK tools need the file converted. For the highest precision give the receiver the camera's capture signal on its own event input (with Emlid the EXPOSURE signal can be paralleled; TAG-E has its own pull-up): the receiver's own timing is always more precise than TAG-E's. A capture-pulse output from TAG-E was tested as a development feature; ask support whether your firmware has it.

PPKEmlid

Copy link

Which angles are written, and does Pix4D / Metashape read them?

EXIF has no field for camera angles, so TAG-E writes roll, pitch and yaw as XMP in the Pix4D structure; yaw is the heading from north. Pitch 0° = nadir, 90° = horizon. Windows file properties do not show them; use Pix4D, Metashape or ExifTool. Metashape reads them automatically since the February 2026 firmware; if it asks you to load angles manually, update. ARW files are tagged correctly since the same update.

Focal length is entered in tenths of a millimetre: 400 for a 40.0 mm lens (the documented limit of 200 does not apply). Agisoft and Pix4D read tilt differently depending on the camera source, so confirm with one short real flight.

XMPPix4DMetashape

Copy link

Landing detection and starting/stopping geotagging from my own software

When the drone lands the tags are written automatically (GTG_LAND_DETECT, default on; to keep a changed value run FW_SAVE_CFG = 1). Landing detection is not perfect, so a better trigger is the end of the mission or the last mission photo; that saves the waiting time after landing.

  • Stop and write: MAV_CMD_DO_DIGICAM_CONFIGURE param1 = 133, or TG_WR_EXIF = 1, or QGC EXIF > Write now.
  • Start: param1 = 132; normally not needed because tagging runs while the camera is online.
  • Throw away what has been recorded and start again: param1 = 260 (nothing is written).
  • Physical button: set an IO port to mode 10 (Action Button, see the Action Button manual) to start geotagging with a button.

With landing detection off the unit simply waits for your command. A running video is stopped automatically when the write begins.

landingcommands

Copy link

QGC shows twice as many photos as were taken

The flight controller sends its own photo feedback and TAG-E sends another one, so QGC counts every photo twice. This is a QGC and autopilot behaviour that has been reported upstream. The photos and tags on the card are correct.

QGCcounter

Copy link

Camera control (QGC, MP, MavCam)

The QGC camera panel is missing, or the photo/video buttons are dead

  • The controls appear only when the camera is online (green LED); they show up by themselves, no reboot needed.
  • Clear the cache Documents/QGroundControl/Parameters; QGC keeps the camera description there.
  • After a power cycle QGC sometimes leaves the photo/video buttons dead; updating TAG-E reduces this a lot. Restarting QGC also helps.
  • Video streaming problems in some QGC 5 builds on SIYI are known. The video comes from the radio, not from TAG-E; QGC may log an error about streaming, which you can ignore.
  • The QGC bundled with HereLink or SIYI may be too old. MavCam 2.25 or newer works with TAG-E, although MavCam is no longer the intended control app.

Documentation: QGC camera control

QGCUI

Copy link

How do I set exposure values and control TAG-E from my own ground software?

Use the MAVLink PARAM_EXT protocol, the same one QGC uses. The camera description XML (available over MAVLink FTP) lists every parameter and option. Camera parameters: TG_EXPMODE (iAuto 294912, P 65538, A 131075, S 196612, M 1), TG_APERTURE, TG_SHTTERSPD, TG_ISO, TG_AISOMIN / TG_AISOMAX, TG_AFMODE (MF 1, AF-S 2, AF-C 32772, AF-A 32773, DMF 32774), TG_EXPC, TG_IMGRES, TG_FORMAT, TG_WR_EXIF and TG_CAM_MODE (99 = camera not ready, 0 = full control, 88 = reduced mode for other cameras). Bool controls are 0/1. Text parameters: TG_CINFO (user comment written into the photo metadata, default "TAG-E") and TG_PLD_ID (payload serial, up to 16 letters or digits).

Commands use MAV_CMD_DO_DIGICAM_CONFIGURE (202) with param1 as the code: 100–105 arrows, OK and MENU; 106 video; 107 burst; 109/110 white balance; 111–114 manual focus steps; 115 live-view zoom; 116 Play; 117 P/A/S/M toggle; 118–121 focus-plane cursor; 122/123 exposure compensation; 124–131 soft keys; 132/133 geotagging start/stop; 134 Display; 135 AF trigger; 136 zoom (direction only, one fixed step); 137 focus magnification 0–3; 180 AF area mode (param7); 260 start geotagging again; 1100 save the log to microSD; 1101 AF target position (param2 = X %, param3 = Y %); 3001–3009 and 3030 gimbal; 6000–6010 custom text tags (24 characters over param2–7); 6549 with param2 = 666 formats the camera card. Aperture, ISO and shutter steps use param2/3/4 = 99 (down) or 101 (up) with param1 = 0. Unknown codes are acknowledged and ignored. There is no Delete command.

AF area: param1 = 180, param7 = the camera's area code (1 Wide, 2 Zone, 3 Center, 257 to 263 flexible spot sizes, 513 and up lock-on variants on the LR1). Setting the AF point does not change the area mode; set both.

For your own app TAG-E also sends a status packet (DATA32, bytes 0xAC 0xD6) with connection, IO and time-sync flags, stream rates and camera values. The DATA64 packet of the ENTIRE is no longer used.

Documentation: Parameter description · Developer information

PARAM_EXTAPI

Copy link

Can I record video and take photos in one flight? Is video geotagged?

Yes. Keep the camera in photo mode; TAG-E starts and stops video over USB. The geotags of a video are saved as subtitles (an .srt file). A running recording is stopped automatically when the geotags are written at landing, and videos are not counted as photos.

HDMI output resolution can be fixed with HDMI_FIX_RES (0 off, 1 4320p/2160p, 2 2160p, 3 2160p/1080p, 4 1080p, 5 720p, 6 480p, 7 576p, 260 1080i, 262 480i, 263 576i, 65535 auto); it is applied every time the camera connects. Some HDMI receivers ignore the interlaced settings.

videoHDMI

Copy link

Does MavCam still work with TAG-E?

MavCam 2.24 and 2.25 support TAG-E (including MENU navigation), and later builds show gimbal controls when a gimbal is found. AirPixel plans to move toward standard MAVLink camera control. When you touch the MavCam joystick it takes control of the gimbal from everything else; the hand icon gives control back to QGC or the RC wheel (this is how ArduPilot works).

Documentation: Mission Planner plugin for TAG-E

MavCamHereLink

Copy link

The camera does not focus before it shoots

Check that the camera is in AF-S or AF-C (not MF), the lens AF/MF switch is on AF and the camera firmware is 3.00. The camera decides how long to focus. The AF-trigger button in QGC focuses without taking a photo.

focus

Copy link

Firmware, logs & recovery

How do I update TAG-E?

  1. Download the update from the firmware page (airpixel.cz/docs/tag-e-firmware-update/; latest at the time of writing 0.204 of 4 October 2026; up- and downgrading is allowed). Unzip it; you get a .img file. Keep its name: the unit only accepts files that start with tag-e_ and end in .img.
  2. Via MAVLink: copy the file to the TAG-E microSD, insert the card and wait a few seconds. Refresh parameters and check that FW_UPDATE_CTRL reads 1. Set it to 2 and write (Write Params in Mission Planner). The LED blinks purple, the unit goes quiet and restarts after about 3 to 4 minutes. You see Firmware write start! in the messages.
  3. If it fails: FW_UPDATE_CTRL reads 154 and you see Firmware update failed! or Update file error #E1/#E2/#E3: the file is damaged or wrong. Copy it again; it often works on a second try.
  4. Without MAVLink / if the unit does not answer: put the firmware file in the card root together with an empty file named forceupdate (no extension) and insert the card. The update starts by itself; take the card out as soon as the red LED lights, otherwise it may update again. forceupdate is a fallback given by support and is not on the manual page.
  5. A red LED that stays red for a long time: disconnect everything and power only the TAG-E for about 15 minutes. If it does not turn blue, the update was interrupted (see recovery).

Update the Mission Planner plugin and MavCam to the versions that mention TAG-E. Units shipped early may carry very old firmware, so update first.

Documentation: TAG-E firmware update

updatemicroSD

Copy link

The unit blinks strange colours after a failed update. How do I recover it?

  1. Copy fw.img to the root of a USB flash drive.
  2. Connect the flash drive to the TAG-E USB connector. The flash drive needs its own 5 V and a common GND.
  3. Power the flash drive first. Press and hold the button inside the front hole (use a needle) and power the TAG-E.
  4. When the LED shows green, release the button. Recovery takes a few minutes; steady green means done.
  5. Power-cycle and wait about 5 minutes for the first start.

Recovery removes the factory validation, and the unit then shows HW validity failed. Update to firmware 0.121 or newer, send the serial (sn:... from the Mission Planner messages) to support and you receive a validation package. Copy it to the microSD root without renaming it (legal.pck), insert the card and wait until the red SD LED goes off. A file validation_OK on the card means the unit is fully operational; validation_ERROR means the package does not match the unit.

recoveryvalidation

Copy link

How do I get the log for support?

  1. Reproduce the problem and do not reboot the TAG-E afterwards.
  2. On a PC create an empty file named savedump (no extension) in the root of a microSD card.
  3. Insert the card into the running TAG-E and wait until the SD-card LED turns red and then goes off.
  4. Take the card out. The folder dump_logs now holds a file TAG-E_dump_NNNN.txt; send it to support. The savedump file is renamed savedump_done, so create it again for the next log. The log is not readable by users; only AirPixel can read it.

You can also request the log by MAVLink (DO_DIGICAM_CONFIGURE param1 = 1100) without handling the card. After a geotagging run with errors the unit also saves a log by itself, as processing_log_NNNN.txt next to the photos on the camera card. For geotagging problems repeat the steps after pressing EXIF > Write now with a few test photos.

Please also send: firmware versions of TAG-E, camera, gimbal, autopilot and ground software; the parameter list of the TAG-E; photos of the wiring; a screenshot of the Messages tab after power-up.

Documentation: SD card parameter configuration

logsupport

Copy link

What do the TAG-E status messages mean?

TAG-E reports through status messages (Messages tab in Mission Planner, MAVLink console in QGC):

  • Mavlink connected!, GPS OK! / lost! / Too high!, ATTI OK! / lost! / Too high! – state of the data from the autopilot ("Too high" = far more messages than needed).
  • Camera connected! / Camera disconnected!, Camera FW unsupported (x.xx)!, Image Save Dest. error!.
  • Time synced (mav): ... (or (emlid)) – the clock was set from the autopilot or the Emlid.
  • Gimbal connected! / connection lost!, RangeFinder online! / offline!, PPS online! / offline!.
  • GTG start..., Found n photos!, GTG progress n%, GTG done!, GTG no logs to process!, GTG - no captures!, GTG mount error!, GTG init error!, GTG Log file error!, GTG XMP Error!, GTG EXIF ... error!, GTG FocalLength error!, Stopping movie recording!.
  • Configuration saved!, Firmware write start!, Firmware update failed!, HW validity passed! / failed!.

MAV_HIDE_MESGS reduces the messages: 1 errors only, 2 everything as info, 5 none.

messagestroubleshooting

Copy link

Can I configure TAG-E without a ground station?

Yes. Put a text file named set.txt in the root of a microSD card and insert it into the TAG-E. Write one name=value per line; lines starting with # are ignored. Any TAG-E parameter name works, for example IOB_BAUD=9216, MAV_COMP_ID=101 or GTG_LAND_DETECT=0. The file is applied every time the card is inserted, and it can be a way back in if a wrong baud rate locked you out of MAVLink. Add FW_SAVE_CFG=1 as the last line to keep the values; without it they are gone after the next restart.

microSDconfiguration

Copy link

Before you write to support: collect this

Covers the MavPorter serial MAVLink router (docs: airpixel.cz/docs-mavporter/). It is a separate product that is used together with ENTIRE or TAG-E.

  • MavPorter firmware version (at least FW 24; FW 30 is current)
  • Screenshot of the PRTx baud, MODE, FWD_TO and NO_OWN_DTA parameters (component 241 in QGC, UART_BRIDGE in Mission Planner)
  • Flight-controller serial parameters (baud, protocol) and a photo of the wiring
  • What is connected to which port and whether the device sends heartbeats
  • Flight .bin log if the link drops during a flight

What it is & when to use it

What is MavPorter?

MavPorter is a small MAVLink router. It shares one serial MAVLink connection between up to five ports (PRT1 to PRT5), each with its own baud rate, forwarding rules and message filters. It replaces the old Extension Box; the two are different products and cannot be converted into each other.

It handles MAVLink 1 and 2 at the same time. You configure it from your ground station: in Mission Planner it appears as UART_BRIDGE, in QGC as component 241.

Documentation: MavPorter basics · IO description

overview

Copy link

When do I need a MavPorter?

  • The flight controller has too few free serial ports: put the gimbal, an ENTIRE or TAG-E, ADS-B, Remote ID or a FLARM device behind one port.
  • PX4 that you cannot modify: PX4 does not forward ground-station data to a device by default. A MavPorter on the telemetry link to the ground station (for example between the flight controller and a HereLink air unit) lets an ENTIRE receive the control data. This was used for Alta X systems.
  • Different baud rates per device on one link, or limiting what a slow device receives (filters and rate limits).
  • Carrying external serial data (rangefinder, Emlid, NMEA) to an ENTIRE over a single MAVLink connection.

It is not needed for a standard ArduPilot + Gremsy + ENTIRE or TAG-E installation; those sets work without one. Remember that every extra device on the telemetry line is one more point of failure, so add it only when you need it.

use casesPX4

Copy link

Connecting & configuring

Which ports and default baud rates does it have?

  • PRT1: 921 600 bps – normally the flight-controller side (set the controller's telemetry baud to 921 600 as well).
  • PRT2: 921 600 bps
  • PRT3: 500 000 bps
  • PRT4: 115 200 bps
  • PRT5: 230 400 bps

The baud parameter PRTx_BAUD holds the rate divided by 100: 921 600 = 9216, 500 000 = 5000, 230 400 = 2304, 115 200 = 1152, 57 600 = 576 (the value for a FLARM unit). Most standard rates up to 1 500 000 bps work. Use 921 600 on the HereLink air-unit side too, to avoid data loss (115 200 works but is slow).

A cable made for connecting an autopilot is wired for an autopilot only; a WiFi module or other device with the same connector may need a different pinout.

portsbaud

Copy link

How do I open the MavPorter settings?

  • Mission Planner: connect to the drone, open the device selection menu and choose UART_BRIDGE; wait until the parameters have loaded. AirPixel also provides a MavPorter plugin for Mission Planner.
  • QGC: Q icon → Vehicle Configuration → Parameters → choose component 241.
  • Any ground software that supports the MAVLink parameter protocol can be used.

If component 241 does not show, the MavPorter is not online (see Troubleshooting). EMIT_PARAMS = 1 (recommended) makes the parameters visible; with 0 the others are hidden and cannot be changed.

Documentation: Parameter accessing · Mission Planner plugin

configurationMission PlannerQGC

Copy link

What are the MavPorter parameters?

  • PRTx_MODE – 1 MAVLink (default), 0 disabled.
  • PRTx_BAUD – baud divided by 100.
  • PRTx_FWD_TO_Py – forward data from port x to port y (all enabled by default).
  • PRTx_NO_OWN_DTA – 1 stops MavPorter sending its own heartbeat and parameter data to that port, making it invisible (default 0).
  • PRTx_FLT_MODE – 0 block the listed message IDs, 1 block everything except the listed IDs.
  • PRTx_FLT_A_ID to _E_ID – up to five message IDs per port; PRTx_FLT_A_SPD to _E_SPD – limit how often that ID is sent (0 = no limit) without blocking it.
  • PRTx_FORCE_MV1 – force MAVLink 1 on a port (v1 in is upgraded to v2 for forwarding, out is converted to v1). Added in FW 30.
  • PRTx_FORCE_FWD – forward even before data has been received from the device (added in FW 26).
  • SMART_ROUTING – see the routing answer.
  • EMIT_PARAMS – show or hide the parameters.

Reboot all devices after changing baud rates or modes.

Documentation: Parameter configuration

parameters

Copy link

Forwarding, filters & routing

How do I stop devices from flooding each other?

  • Disable forwarding between ports that must not talk, for example PRT2_FWD_TO_P3 = 0 and PRT3_FWD_TO_P2 = 0 for a gimbal on port 2 and a camera or ADS-B on port 3.
  • Set PRTx_NO_OWN_DTA = 1 on the gimbal and camera ports: a Gremsy can behave oddly when the MavPorter emits its own heartbeat.
  • Switch on SMART_ROUTING: MavPorter works out which device is on which port and sends commands addressed to a device only to that port.
  • Use filters to block or rate-limit streams a slow device cannot handle. For a gimbal and a camera payload, keep the gimbal-attitude message (GIMBAL_DEVICE_SET_ATTITUDE, id 284) reaching only the gimbal.
  • Use 921 600 bps on busy links and the higher rate (for example 500 000) towards a TAG-E.

forwardingfilters

Copy link

Typical installations with ENTIRE, TAG-E and gimbals

  • PX4 + HereLink + ENTIRE R3 (no PX4 modifications): break the serial link between the flight controller and the air unit and insert the MavPorter; the ENTIRE sits on one of its ports. Wiring on the drone is your own work; with no geotagging it runs fine with MavCam.
  • TAG-E with a full flight-controller UART: flight controller to MavPorter at 921 600, MavPorter to TAG-E at 500 000, latest MavPorter firmware, smart routing on, and forwarding rules that keep ADS-B data away from TAG-E.
  • Gimbal plus payload (for example Pixy-U and a Pico NV): use the highest baud both support, disable forwarding between them, set NO_OWN_DTA on both ports and let the gimbal-control message through only to the gimbal.
  • Remote ID, FLARM, Dronetag: set the baud of the port (FLARM 576, Dronetag 1152) and optionally NO_OWN_DTA = 1 there.

ENTIRETAG-EGremsy

Copy link

Troubleshooting

MavPorter not found, component 241 missing, or the plugin stays offline

  1. Baud match: the flight controller's telemetry baud must equal the baud of the MavPorter port it is plugged into (PRT1 default 921 600).
  2. Wiring: TX to RX and RX to TX. A typical symptom is that MavPorter can send to the flight controller but receives nothing; check the wire and try another telemetry port.
  3. Connector pins: disconnect PRT1 and look for bent pins.
  4. If MavPorter shows up in QGC (component 241) but the Mission Planner plugin says offline, the device works and you can use it; send AirPixel your parameter list and the ArduPilot version so the plugin can be checked. Mission Planner 1.3.80 and 1.3.83 were tried in one such case.
  5. A cable for an autopilot may not suit a WiFi module or other device; check that device's pinout and baud rate.

troubleshootingwiring

Copy link

A connected device (FLARM, Remote ID, WiFi module) gets or sends no data

  • MavPorter starts passing data to a port only after the device on it has sent its first message (normally a heartbeat). Check in the plugin that data arrives on that port.
  • If the device stays silent until it receives data, set PRTx_FORCE_FWD = 1 (firmware 26 or newer) so MavPorter forwards from the start.
  • Baud rate must match the device; many devices have no published pinout, so swapping TX and RX was the fix for a Remote ID module.
  • No need to configure MAVLink 1 for old devices: both versions are understood. Use PRTx_FORCE_MV1 only when a device really needs v1 output (FW 30).

FLARMRemote ID

Copy link

Connection drops or QGC loses the drone after a few minutes

Several firmware bugs have been fixed, so update first: FW 19 did not work with HereLink; FW 21 corrected errors that could even cause a flight-controller signing lock; FW 24 fixed dropouts with newer QGC versions; FW 26 fixed a case where one port stopped transmitting. Disconnect the camera and gimbal before updating. If it still drops, send the flight .bin log for a replay.

QGCHereLink

Copy link

Firmware, reset & recovery

How do I update MavPorter, and which firmware is current?

Latest in the documentation is FW 30 (21 September 2024), which adds PRTx_FORCE_MV1 and stability fixes. Use at least FW 24; older versions may cause problems.

  1. Download the update application and unzip it into a new folder; run the EXE (as administrator if blocked).
  2. Connect the drone to the PC over USB as for Mission Planner or QGC and select the same COM port.
  3. Click Connect: the label should show Online! and the device should read MavPorter.
  4. Click UPDATE. The same step re-flashes the same firmware as a recovery.

MavPorter can stay connected; power only the flight controller and MavPorter. If it reports no success, retry without rebooting it, then reboot the whole drone. Details: the MavPorter firmware-update page.

Documentation: MavPorter firmware update

firmwareupdate

Copy link

I lost the connection (wrong baud) or the device is stuck. How do I reset or recover it?

Emergency reset to defaults: power up and wait for the main application; press the hidden back button with a needle; the LED blinks blue/green quickly; hold until the LED goes dark; reboot. All settings return to default.

At power-up the LED is steady blue for 3 seconds. Only PRT1 listens then, at its own baud rate (500 000 bps if the firmware is damaged). Pressing the button during this time changes that rate: steady blue = PRT1 rate (or 500 000), steady green = 230 400, blue and green = 115 200.

Stuck in boot: temporarily set the Cube's SERIALx_BAUD to 115, reboot, reconnect and press UPDATE in the updater within about 2 seconds. Afterwards MavPorter is back at 921 600 on PRT1, so set the serial baud back to 921 600.

Documentation: MavPorter basics

resetrecoveryLED

Copy link