Loading...

 
View Categories

TAG-E

14 articles

Basics

Last Updated: August 5, 2025

First power-up Warning!​ TAG-E accepts input voltage of 5V ONLY! Higher voltage can harm the device and also connected camera via USB! Use our uBEC if voltage is higher! All GNDs are interconnected! All input and output pins of 5V and Ground are interconnected. Input power is interconnected to IO A/B/C, PPS, USB. Make sure...

Pinouts

Last Updated: October 2, 2025

TAG-E pinout description All GNDs are interconnected! All input and output pins of 5V and Ground are interconnected. Input power is interconnected to IO A/B/C, PPS, USB. Make sure that external device can handle 5V input, or does not output higher voltage to TAG-E. If you are not sure, contact us at info@airpixel.cz or disconnect...

Mavlink connection – Ardupilot

Last Updated: March 13, 2026

MavLink basics By default TAG-E uses MAV_COMP_ID_CAMERA For highest geotagging accuracy TAG-E needs: Working TIMESYNC protocol Receive SYSTEM_TIME packets at 1Hz Receive GPS_RAW_INT (freq. depends on configuration) Receive GLOBAL_POSITION_INT (freq. depends on configuration) Receive ATTITUDE packets at 10Hz Messages are also automatically requested by command long SET_MESSAGE_INTERVAL If SET_MESSAGE_INTERVAL protocol is supported by your FC...

Mavlink connection – PX4

Last Updated: March 13, 2026

MavLink basics By default TAG-E uses MAV_COMP_ID_CAMERA For highest geotagging accuracy TAG-E needs: Working TIMESYNC protocol Receive SYSTEM_TIME packets at 1Hz Receive GPS_RAW_INT (freq. depends on configuration) Receive GLOBAL_POSITION_INT (freq. depends on configuration) Receive ATTITUDE packets at 10Hz Messages are also automatically requested by command long SET_MESSAGE_INTERVAL If SET_MESSAGE_INTERVAL protocol is supported by your FC...

GPS delay calculation

Last Updated: August 7, 2025

Impact of GPS delay to geotagging GPS or RTK system provides data via serial bus, which delays the position data for some very short time. When GPS or RTK is connected to flightcontroller, and than forwarded to TAG-E or ENTIRE, there is another delay of transmission. Both TAG-E and ENTIRE calculates automatically offset of this...

Camera connection (direct)

Last Updated: September 26, 2025

Power connection How to connect power input to the TAG-E is described on separate page. Mavlink connection Connection to flight controller and all configuration is described on separate page. Direct connection of Sony ILX-LR1 This manual is about TAG-E connection and installation for direct connection (no gimbal) to Sony ILX-LR1 camera with cables included with...

Pixy-LR set connection for PX4

Last Updated: September 26, 2025

About this usage scenario This manual is about TAG-E connection and installation for connection to Gremsy Pixy LR gimbal and Sony ILX-LR1 camera. For this installation you need PixyLR connection set from our store.Our wiring set for Pixy-LR uses Mavlink forwarding of the gimbal. That means, the TAG-E shares the same TELEM port as the...

Pixy-LR set connection for Ardupilot

Last Updated: March 27, 2026

PX4 users This page is dedicated for Ardupilot. For PX4 firmware please follow this link. About this usage scenario This manual is about TAG-E connection and installation for connection to Gremsy Pixy LR gimbal and Sony ILX-LR1 camera. For this installation you need PixyLR connection set from our store.Our wiring set for Pixy-LR uses Mavlink...

Parameter description

Last Updated: April 22, 2026

How to access configuration QGC   Open QGC and wait for vehicle connection Open Vehicle Setup page Expand “Component 100” in the list If you do not see “Component 100”, your Mavlink connection between TAG-E and the Cube is not configured properly. Follow this manual to proceed. Loading of TAG-E parameters may take few seconds...

Firmware update

Last Updated: April 22, 2026

Download update pack FW:0.151 – (22.4.2026) New feature – gimbal control of Follow/Lock mode for Gremsy gimbals (command p1:3030 | p7 value 1-lock / 2-follow) Added support for MAV_CMD_DO_SET_CAM_TRIGG_DIST Added support for MAV_CMD_DO_SET_CAM_TRIGG_INTERVAL Added support for MAV_CMD_DO_TRIGGER_CONTROL Added dynamical MavLink stream stopping for unwanted streams (applied to PX4 only) Corrected MavLink PassThrough mode for IO...

MissionPlanner camera control plugin

Last Updated: May 25, 2025

Installation 1.    Download our Mission Planner plugin here2.    Unzip and copy all files to Mission Planner plugins path:     – “C:Program Files (x86)Mission Plannerplugins”3.    Open Mission Planner application 5.    Right click to tabs and enable Camera control plugin 4.    In few seconds new tab will appear Updated release notes: Initial release v 1.01: Added support...

QGC camera control

Last Updated: June 19, 2025

Download & install QGC DOWNLOAD Select version you would like to install, click to “Assets”.For PC installation select QGroundControl-installer.exeFor Android (HereLink or SIYI) select QGroundControl.apk https://github.com/mavlink/qgroundcontrol/releases VERSION Select version – v4.4.3– v4.4.4– v4.4.5– v5.0 – Release Candidate 4– or later (do not use v5.0 RC 1/2/3) QGC camera control usage LAUNCH QGC Launch QGC in...

Action Button installation

Last Updated: November 22, 2025

Action Button purpose Action button is simple external push button device for ENTIRE R3 and TAG-E. It is used to manually (without accessing of WiFi or using QGC / drone) start and stop geotagging session. Button is used applied mainly in non-drone application of our geotaggers. Installation Connect UNI cable #1 Use included UNI cable...

Developer information

Last Updated: April 13, 2026

Notice​ This page is draft and needs to be imrpoved. Majority of users should not need informations at this page This page is aimed to implementators and developers who would like to implement own camera control software for their users MavLink basics By default TAG-E uses MAV_COMP_ID_CAMERA6 For highest geotagging accuracy TAG-E needs: Working TIMESYNC...

MavLink camera control

TAG-E uses PARAM_EXT protocol to control camera exposure values and configuration. Accurate and most recent description of available PARAM_EXT parameters and optional values is listed in camera description XML file shared by your TAG-E unit. You can find it under QGC files -> \Documents\QGroundControl\Parameters\Tag-E_ILX-LR1_xxx.xml

MavLink TAG-E status packets

TAG-E sends status packets depending on the state of the camera or TAG-E configuration. These packets are generated on predefined interval or as soon as some change happened.
******************************************
TAG-E sends:

  • Heart beat
    • custom_mode 0x1A6EC654L
  • Data32
  • Data16


******************************************

—- packet Data32 structure —-

byte 0 – 0xAC -> AirPixel data sync byte
byte 1 – 0xD6 -> TAG-E status packet type
byte 2:
    bit 0 – camera connected status
    bit 1 – IO-A status
    bit 2 – IO-B status 
    bit 3 – IO-C status 
    bit 4 – timesync status (1-ready)
    bit 5 – Time synced in camera (1-ready)
    bit 6 – Auto take-off detection enabled status
byte 3 – reserved (00)
byte 4 – MavLink GPS speed
byte 5 – NMEA GPS speed 
byte 6 – ERB GPS speed 
byte 7 – MavLink ATTI speed
byte 8 – MavLink TIMESYNC speed 
byte 9 – Camera ISO Lbyte
byte 10 – Camera ISO Hbyte
byte 11 – Camera ISO-min Lbyte
byte 12 – Camera ISO-min Hbyte
byte 13 – Camera ISO-max Lbyte
byte 14 – Camera ISO-max Hbyte
byte 15 – Camera Sh.Speed Lbyte
byte 16 – Camera Sh.Speed Hbyte1
byte 17 – Camera Sh.Speed Hbyte2
byte 18 – Camera Aperture (x10)
byte 19 – Camera Mode
byte 20 – Camera Exp.Corr
byte 21 – Camera AF-mode
 

—- packet Data16 structure —-
byte 0 – 0xAC -> sign of Entire generated packet
byte 1 – 0xA9 -> Geotagging status packet

byte 2 – Logging session status
    0 – IDLE
    1 – Initialization
    2 – RUN
    3 – Saving (Geotagging under progress)
    100 – Error
byte 3 – Geotagging progress
    0-100 (% of progress of geotagging)

byte 4 – Detected photos in session Lbyte
byte 5 – Detected photos in session Hbyte

byte 6 – Current LightWare measured distance Lbyte
byte 7 – Current LightWare measured distance Hbyte
byte 8 – Camera ready status