Table of Contents
Download update pack #
- Enhanced stability of geotagging procedure
- New feature – Gimbal detection in Mavlink PassThrough channel
- Correction of tilt interpretation for Gremsy gimbals
- Correction of GTG_FOCAL_LEN propagation
- Correction of Roll/Pitch/Yaw reading for DJI API connected drones
- New feature – custom XMP label strings geotagging
- New feature – automatic disable of custom EXIF information writing configured in camera
- New feature – support for other than ILX-LR1 camera (geotagging is supported only for LR1)
- New feature to save processing log via COMMAND_LONG -> DIGICAM_CONFIGURE (param1 – 1100)
- New feature to set HDMI output resolution via parameter HDMI_FIX_RES
- Available values:
0 —disable HDMI handling
1 — 4320p/2160p
2 — 2160p
3 — 2160p/1080p
4 — 1080p
5 — 720p
6 — 480p
7 — 576p
260 — 1080i
262 — 480i
263 — 576i
65535 — Auto
- Available values:
- New feature to control Autofocus Area mode via COMMAND_LONG -> DIGICAM_CONFIGURE (param1 – 180, param7 – mode)
- Available modes:
1 — Wide
2 — Zone
3 — Center
257 — Flexible Spot S
258 — Flexible Spot M
259 — Flexible Spot L
260 — Expand Flexible Spot
261 — Flexible Spot
262 — Flexible Spot XS
263 — Flexible Spot XL
4353 — Flexible Spot Free Size 1
4354 — Flexible Spot Free Size 2
4355 — Flexible Spot Free Size 3
513 — Lock on AF Wide
514 — Lock on AF Zone
515 — Lock on AF Center
516 — Lock on AF Flexible Spot S
517 — Lock on AF Flexible Spot M
518 — Lock on AF Flexible Spot L
519 — Lock on Expand Flexible Spot
520 — Lock on AF Flexible Spot
521 — Lock on AF Flexible Spot XS
522 — Lock on AF Flexible Spot XL
4609 — Lock on AF Flexible Spot Free Size 1
4610 — Lock on AF Flexible Spot Free Size 2
4611 — Lock on AF Flexible Spot Free Size 3
- Available modes:
- New feature – reporting of SD Card status in DATA32 camera status byte 22.
- Optional values:
0 — Unknown / Camera disconnected
1 — OK
2 — No Card
3 — Card Error
4 — Card Recognizing / Card Locked and DB Error
5 — DB Error
6 — Card Recognizing
7 — Card Locked and DB Error
8 — DB Error (Cannot Repair and Need Format)
9 — Card Error (Read-Only Media)
- Optional values:
- Added support for HW 3.2
- 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 A/B/C
- New parameter: MAV_HIDE_MESGS to control TAG-E’s STATUS TEXT messaging:0 – Default messaging
1 – Send only error messages
2 – All messages send with flag “MAV_SEVERITY_INFO”
5 – Disable all status_text messaging
- New feature – Control of image resolution (S/M/L)
- New feature – X_OPTIONS parameter used for custom features and debugging tools control
- Improved compatibility of ILX-LR1 XMP geotags for Agisoft Metashape
- Corrected geotagging of RAW (ARW) files for ILX-LR1
- Correction of SimpleBGC YAW alignment handling
- Correction of automatic Mavlink stream requesting
- Correction of geotaggign overview (data16) packet
- Correction of Landing detection feature
- Correction of PPK configuration
- New parameter MAV_GMB_ID for manual selection of gimbal
- Used when more than one gimbal is present
- Allows user to disable gimbal readings if a gimbal is present, but related to other camera
- More information
- Correction of Basecam driven gimbals compatibility
- Mavlink compatibility and stability enhanced over 0.126
- Correction of small issues of FW 0.123, 0.124 and 0.126
- New feature -> Payload serial geotagging. Serial number is configurable via PARAM_EXT “TG_PLD_ID”
- New feature -> Automatic subscription for CAMERA_TRIGGER messages when used with PX4 firmware
- New feature -> User HW validation via SD card for cases of firmware recovery
- New feature -> DJI compatibility
- New feature -> Automated trigger by time or by flown distance for DJI usage
- Correction of camera offset calculations when used with Pixy LR 2-axis
- Enhanced triggering timing to be faster and more robust with bad AF
- Added broadcast of initial parameter to enable better sync with QGC parameter list
- Enhanced capture detection code to avoid double trigger detection with long exposures
- Correction of data in CAMERA_IMAGE_CAPTURED message
- New feature – Zoom control for Power zoom lenses via QGC UI
- New feature – Option for ELLIPSOID altitude geotagging (New parameter MAV_GPS_ELIPSO)
- New feature – Automatic configuration of “Still Img. Save Dest.” option in the camera when set incorrectly
- Correction of USB MASS STORAGE mounting with zoom lenses (delay of zoom close could lead to mount fail)
- Correction of TimeZone offset handling and camera time setting
- Correction of Mavlink packet numbering issue – resolving mavlink stability reporting error
- Correction of Mavlink camera firmware reporting
- Correction of IO port mode configuration
- Corrected automatic GPS/ATTI stream handling via MavLink
- Added automatic Mavlink stream stopping for unwanted data streams
- Added support for processing log download
- Enhanced stability of Mavlink Camera control protocol v2
- Correction of Gremsy gimbal attitude reading
- Support for ARW geotagging
- Correction of MavLink packet numbering to avoid false packet-loss reporting
- PX4 compatibility improvements
- Support for ARW geotagging
- Supported modes:
- JPG only
- RAW only
- JPG & RAW
- Camera firmware version recognition and reporting
- Support for broadcast commanding of Ardupilot
- support for GIMBAL_MANAGER_INFORMATION message
- corrected SD Card formating issues
- Lading detection issue resolved
- Gimbal angles reading correction
- Automatic gimbal mount orientation stream requesting
- Tuning of GPS LINK DELAY default value
- Initial FW release
Firmware update procedure #
Transfer of FW pack is done via Micro SD card slot of TAG-E.
STEP 1
Download ZIP file with desired FW version for TAG-E at the top of this page. You are free to upgrade or downgrade through all versions.
STEP 2
Unzip .img file from the zip and copy this .img file to micro SD card
STEP 3
Remove micro SD card from your device and insert to TAG-E
Wait few seconds for SD card scan in TAG-E
STEP 4
Open QGC or MissionPlanner and navigate to parameters, and refresh values
Check for FW_UPDATE_CTRL value
If .img file is recognized on SD card, FW_UPDATE_CTRL will turn to value of “1”
If parameter FW_UPDATE_CTRL is 0, make sure the SD card contains correct file and also make sure you refreshed parameters.
STEP 5
If STEP 4 is passed, write value of “2” to FW_UPDATE_CTRL
Remember to click to Write params if using MissionPlanner
TAG-E will start blinking purple
WARNING - DO NOT REBOOT
Once TAG-E's "CAMERA LED" lights PURPLE (blinking or solid), DO NOT REBOOT or manipulate device!
Critical state of FW rewrite is processing!
Critical state of FW rewrite is processing!
STEP 6
You can check FW update progress in TAG-E messages in multiple steps
- Step 1 OK!
- Step 2 OK!
- Step 3 OK!
- Firmware write start!
- After this point TAG-E stops all communication
- Reboot will occur during rewrite process
- Once update is done, TAG-E will turn LED to blue
First three steps are decompression of firmware file and takes approx. 1 minute.
Whole procedure of FW update will take 3 to 4 minutes.
Do not reboot or manipulate device during any step.
Check actual firmware #
Check with QGC or MissionPlanner in Messages
- Power up and connect your drone via USB to the PC with MissionPlanner installed
- Reboot TAG-E and wait for its boot (blue LED)
- Check MissionPlanner tab “Messages” for TAG-E’s boot Status Messages
