Current Firmware Release
The current Firmware release of the TENGRI REMOTE COCKPIT is version 1.040 . If you are using a previous version and require assistance in upgrading your firmware, please email firstname.lastname@example.org
Installation & Support
The TENGRI REMOTE COCKPIT has been designed for ease of use and is Plug & Play. Please read the brief Setup Guide for installation instructions. If you are however having difficulty with the setup for any reason, please contact the technical support team at email@example.com for further assistance. Our support team would be happy to help resolve the problem. Some frequently asked questions and instructions are also shown below for your convenience.
Click here to download the TENGRI REMOTE COCKPIT SETUP GUIDE (PDF) version 1.0.1
Click here to view or join our Facebook Professional UAV piloting forum and interact with support or learn from experienced users.
CONNECTING AN USB KEYBOARD OR KEYPAD FOR NAVIGATING THE CONFIGURATION MENU
An external laptop or tablet is not required for configuring the Remote Cockpit. The device can be configured from your Radio Control device.
However an USB keyboard or keypad can also be connected to the Remote Cockpit via the USB port for configuring the device. Press the [Enter] key to bring up the configuration menu and thereafter use the Arrow keys to navigate the menu.
HDMI AND ANALOG VIDEO INPUTS & OUTPUTS CAN BE MIXED
The HDMI and Analog video inputs and outputs can be mixed on the Tengri Remote Cockpit. Analog camera inputs can be transmitted via the HDMI output. HDMI input can also be transmitted via the analog output. In addition, HDMI and Analog video inputs can be mixed for the on-screen display (i.e. HDMI main window with analog Picture in Picture window).
SERIAL BAUD RATE FOR ARDUPILOT AND PX4 TELEMETRY CONNECTION
ARDUPILOT and PX4 Flight Controller users, please note that the serial baud rate on the connected telemetry port needs to bet set at 921600 as per the SETUP Guide.
For technical support, please contact the technical support team on the contact details received with your shipment.
FIRMWARE UPGRADE INSTRUCTIONS
1) Download the firmware from the download link you have received via email to a USB stick or pen drive
Filename : trc_1-0XX.swu (APPROX 42MB)
2) Insert the USB stick or pen drive into USB port on the remote cockpit.
3) Power up the remote cockpit and go to the update option on the menu and select the firmware version to update.
Note : You can also downgrade to the previous version at anytime in the future if you experience any issues with the
upgrade using the same process.
4) The firmware will be updated and the remote cockpit will reboot when the update is completed.
5) Invoke the menu again and ensure that the version number on the top right of the menu screen shows the version number that was updated.
TENGRI REMOTE COCKPIT QUICK REFERENCE LAYOUT
On-board flight data & OSD recording quick reference
______________________________________________________________________________________________________________________________ FOR MAPPING USERS
SETTING THE CAMERA HOT SHOE DELAY INTERVAL FOR MAPPING USERS
The infographic below shows how to set the correct capture delay interval for determining failed and successful camera capture events.
1. Test the camera capture on the ground by manually triggering the camera and observing the hot shoe capture delay interval
2. On the TENGRI configuration menu, set the camera capture delay interval as explained in the graphic below.
If your camera shutter interval is more than 2 seconds, leave the setting at the maximum value of 2000 milliseconds. If your running a fast shutter interval (ie 1 second), it needs to be set between the camera hot shoe capture interval and the camera shutter interval to accurately classify events as failed or successful captures.
If the TENGRI is reporting a high camera capture delay which is too close to your camera shutter interval, check the CAM_DURATION setting in APM. This value is set in Deciseconds (10 for 1 second). Try reducing the setting to less than 10 depending on your camera specifications.
If a lower setting is not within your camera specifications, the mission parameters will need to be adjusted to accommodate the capabilities of the camera (ie reduction in speed)
Infographic below explaining the parameters.
The Tengri automatically logs and matches camera trigger and camera capture events in log files on a USB stick or SD card that can quickly be processed for geotagging. Without this auto matching, identifying even a 1 picture mismatch in a 1000+ picture mission is a very tedious process. In addition, the Tengri log files can also be used for gaining a better understanding of your missions and fine tuning your UAV autopilot and camera settings for conducting more effective mapping missions.
One of the most frequent causes of a mismatch in a camera trigger event (triggered from the flight controller) and a camera capture event (triggered from the camera hotshoe) is the varying auto focus delay on the camera conflicting with the CAM_DURATION setting in the flight controller. If the camera capture duration is not in sync with the CAM_DURATION settings in the flight controller, mismatched geotagging events or out of focus images will get generated.
Reviewing the camera capture latency data in your Tengri log files and understanding the impact of various auto focus options (especially on newer camera systems) on different types of terrain/object coverage will greatly help in increasing the effectiveness and accuracy of mapping missions. Changes in pitch, roll, and yaw affect the camera focus and capture delays so setting your mission plan and camera settings with proper margins for turns and wind conditions also increases the effectiveness and accuracy of mapping missions.
Mapping OSD screenshot examples