MicaSense Altum™ and DLS 2 Integration Guide





Revision 09, June 2019


Table of Contents

Table of Contents        1

Introduction​        2

What’s Included?        2

Lens and Imager Information        3

Center wavelengths and bandwidth        4

Measurements and Attachment Points        5

Configuration Options        6

Default        6

DLS 2 with Aircraft GPS        7

HTTP Connection        7

Serial Connection        7

Recommendations​ ​for​ ​Installation        8

Input and Output        9

Host Interface Connector (Power and Data I/O)        9

Power specifications        10

Storage (USB)        10

Capture Rate        11

Accessory Port (ACC)        11

Automatic Capture/Triggering        11

Overlap (recommended)        11

Timer        11

External Trigger        12

PWM        12

HTTP API (Ethernet and Wi-Fi)        12

Serial API        12

Downwelling Light Sensor 2 (DLS 2)        13

Measurements and Attachment Points        14

DLS 2 Connectors and Buttons        15

DLS 2 Installation Guidelines        16

Fixed-wing        16

Multirotor        16

Example Integration        17





MicaSense Altum provides multiple options for integration - from stand-alone (where you only provide power to the sensor) to fully customized integrations. Advanced integrations take advantage of flexible interfaces including Ethernet, serial, RTK, and PWM/GPIO trigger, for seamless integration with any aircraft.

What’s Included?

  • Altum sensor
  • DLS 2 sensor
  • Edimax Wi-Fi adapter
  • 128 GB external USB 3 compact flash drive (Samsung MUF-64BA)
  • 15 cm 14-pin Host interface connector (female) with pigtail cable interface for power, ground, trigger, comm interfaces, and DLS2 connector board
  • 15 cm 3-pin power pigtail (DF13)
  • 60 cm DLS 2 connector cable (JST)
  • Pelican case
  • Lens cover (opaque - not for use during operation)
  • M3 x 6mm screws, washers (QTY 4)
  • M2 x 6mm screws, washers (QTY 2)

Lens and Imager Information






Pixel size

3.45 μm

12 μm


2064 x 1544 px

(3.2 MP x 5 imagers)

160 x 120 px

(0.01 K)

Aspect ratio

4 : 3

4 : 3

Sensor size

7.12 x 5.33 mm

(8.9 mm diagonal)

1.92 x 1.44 mm

Focal length

8 mm

1.77 mm

Field of view (h x v)

48º x 36.8º

57º x 44.3º

Thermal sensitivity


< 50 mK

Thermal accuracy


+/- 5 K

Output bit depth



GSD @ 120 m (~400 ft)

5.2 cm

81 cm

GSD @ 60 m (~200 ft)

2.1 cm

41 cm

Center wavelengths and bandwidth







475 nm

20 nm


560 nm

20 nm


668 nm

10 nm

Red edge

717 nm

10 nm

Near infrared

840 nm

40 nm


11 μm

6 μm



Imager/band number and output












Red edge




Measurements and Attachment Points

There are four M3 screw holes at 60 mm x 35 mm on-center.  The sensor can be attached to the host aircraft using at least two of the four provided threaded mounting points and M3 x 0.5 screws. If using only two mounting points, it is important to choose two threaded points opposite of each other.




82 mm


67 mm


64.5 mm


357 g


Configuration Options

There are two basic ways to configure Altum. The following summaries will help you choose the one that meets your needs.



The default configuration uses the DLS 2’s integrated GPS. Use the provided cable to connect the DLS 2 to the DLS 2 board on the HOST connector. Ensure the DLS 2’s physical installation meets the requirements outlined later in the DLS 2 section of this guide. Provide a supported power supply to pins 1 and 2 on the HOST connector. For more details, see the HOST section of this guide.

DLS 2 with Aircraft GPS


For more control, advanced users can communicate with Altum by HTTP (Ethernet, Wi-Fi) or MAVLink (Serial) using the MicaSense APIs (Application Programming Interfaces). The APIs can be used in lieu of the DLS 2 GPS to provide the sensor with a position and attitude data (from the aircraft GPS, for example). Anytime GPS data is sent to the sensor via the API commands, it will be written to the image metadata, overriding the DLS 2 internal GPS data for five seconds (or until another update is sent via the API).

HTTP Connection

Attach a USB Ethernet adapter or USB Wi-Fi adapter to one of the USB 3 ports. See the Sensor Firmware Guide for connection details and information. For HTTP API details, visit https://www.micasense.com/api

Serial Connection

Use the provided pigtail from the host connector cable to connect to your serial device. See the Input and Output section of this document for pin layout and details. Visit https://www.micasense.com/api to learn more about communicating with the MAVLink API.




Recommendations​ ​for​ ​Installation

The Altum should be installed such that it has a clear view of the area directly below the aircraft. The “cone” of the lenses, especially thermal, which has the widest field of view (57º HFOV), should be considered in the process of deciding where to mount the sensor on the aircraft or payload bay.


Avoid putting windows or covers in front of the thermal sensor. Many materials that are transparent in visible bands are opaque in LWIR (thermal), so any coverings may prevent data collection. Even materials that are mostly transparent in LWIR will negatively affect the radiometric accuracy of the sensor output.


The multispectral sensors feature a global shutter and can withstand some vibration without degrading image quality; nevertheless, we recommend vibration isolation between the sensor mounting platform and the aircraft.


Ensure that the sensor points straight down (with respect to the earth) at all times during flight. The best way to ensure this is to use a gimbal.


Airflow over all surfaces of the sensor is necessary for proper heat dissipation. Do not run Altum on the bench or in the field for extended periods of time without airflow. Do not completely cover or insulate the back surface of the sensor.


Normally, the sensor should be in landscape orientation. If you plan to mount the sensor in a portrait orientation, remember to swap the vertical and horizontal parameters in your mission planner.


Ensure that the sensor is completely protected during landing. Note that we do not recommend using a lens cover during flight as it can filter the wavelengths that the sensor measures. Instead, protect the sensor with a recessed installation or by using landing gear.


Use the provided lens cover when storing Altum, and do not set Altum lens-side-down as it will rest on and scratch the lenses.


More integration guidelines for the DLS 2 are in the DLS 2 section of this guide.


Input and Output

The Altum & DLS 2 sensor kit includes all necessary cables for integration. If extending the cables, ensure that the voltage at the camera is at acceptable levels as outlined in the “Powering” section of this guide.

Host Interface Connector (Power and Data I/O)


Connector type/part number: (provided as pigtail assembly with every Altum integration kit from MicaSense)

        Samtec - 14pin, 2.00mm Tiger Eye™: PN# T2M-107-01-S-D-RA-WT



13 11 9 7 5 3 1












14 12 10 8 6 4 2












Power supply specifications




5.2 V - 25.2 V


5.5 W


7 W


10 W


Altum requires 5.2 V DC for operation, with a maximum operating voltage of 25.2 V. The supply must be able to provide 10 W (~2A @ 5V) peak. Power can be provided to the sensor in two main ways:


  • shared power from aircraft's main battery pack
  • a rechargeable Lithium-Ion battery pack (a two-cell LiPo will provide optimal efficiency).


Because 5 volt USB battery packs can dip well below 4.9V, they should not be used to power the sensor. Ensure the power source conforms to the specifications listed above and can supply the required voltage at the power port of the camera, accounting for any losses in the wiring.

Input and Output



Nominal IO Voltage*

3.3 V DC

IO Voltage Range*

0.0 V DC to 5.5 V DC

Absolute Maximum IO Voltage*

5.6 V DC

PWM Trigger Expected Range

1.0 ms to 2.0 ms

VIH High-level input voltage*

2.0 V to 5.5 V

VIL Low-level input voltage*

0.0 V to 0.8 V


*All 3.3V HOST IO lines are referenced to ISO GND (Pin 8). To ensure proper operation of Trigger, Serial, and PPS lines, make sure ISO GND is connected to your host system ground.  This ground is isolated from the Altum power supply ground and must be connected for the IO to function properly.

Storage (USB)

Altum features two high-speed USB 3 ports which support USB 3 compatible devices. Tested, compatible devices include:


Edimax Wi-Fi adapter

AmazonBasics and CableMatters Ethernet adapters

Most USB external flash storage devices (thumb drives, hard drives, and others)


For details on how the sensor writes files to the storage device, see the File Storage section of the Sensor Firmware Guide

Capture Rate

Altum’s capture rate is heavily dependent on the storage device. The Altum kit includes a 128 GB Samsung MUF-64BA drive which has a maximum capture rate of about 1.5 seconds per capture. Using a USB 3 drive with a fast write rate, such as a 2242 M.2 SATA USB 3 drive, will ensure the fastest capture rate possible (about one capture per second). When setting up a mission or flight plan, adjust the desired overlap, flight altitude, and speed so that the capture interval does not exceed the maximum capture rate (one capture per second).

Accessory Port (ACC)

The accessory port is not available for use at this time, but may be used as an expansion port in the future. When it is available, we will update this guide.

Automatic Capture/Triggering

Altum supports three methods for capturing images: Overlap, Timer, and External Trigger. To learn more about how to configure these settings, please see the Sensor Firmware Guide.

Overlap (recommended)

In overlap mode, when the aircraft climbs to within 50 meters below your target altitude, Altum will start capturing and only take a capture if it has traveled forward enough distance to ensure the overlap percentage you have specified. When the sensor's altitude is below 50 meters from the target altitude, the sensor stops capturing. Overlap mode only calculates the forward overlap, and cannot account for the side overlap, which must be calculated in a flight planner, using the sensor’s field of view to create an appropriate row spacing.


We recommend this mode because it helps ensure proper overlap (75% or higher), which is essential in order to produce high-quality output when processing the data in standard photogrammetry software.


When in timer mode, Altum will capture according the timer period (which is every two seconds by default). If the timer period is set to less than one second, the sensor will capture as quickly as it can (about once every second). The capture rate is heavily dependant on the write speed of the attached storage device.

External Trigger

For more control, you can enable external trigger mode to talk to Altum by serial port, Ethernet, or Wi-Fi.  See the HOST connector section of this document for detailed pin information.


The sensor can be triggered with either a rising-edge/falling edge pulse or a PWM signal (such as is typically used with standard servos). When using a PWM signal as the trigger, the sensor detects a transition from a “long” PWM to a “short” PWM (or vice-versa depending on the configuration setup of the sensor). When using PWM, ensure that a dedicated ground is connected to the isolated ground pin 8 on the Altum.

HTTP API (Ethernet and Wi-Fi)

The HTTP API is the most powerful way to interface to the Altum. You can use this API using either the Ethernet connector or the Wi-Fi access point.


The API is accessed via HTTP connection to port 80 at the sensor IP address. All data is exchanged in the JSON format.


The actual value of the IP address depends on the configuration. When accessing the sensor via its Wi-Fi access point, the sensor IP address will be When the sensor is connected to an Ethernet network, the sensor IP address will be by default.


The sensor can be commanded to take a capture by either a GET or POST request to the /capture URL.


For more information and examples, please see https://www.micasense.com/api

Serial API


The Serial API provides a MAVLink interface to the Altum. You can use this API by connecting your MAVLink-capable system to the host serial port on the sensor.


The API is accessed via serial messages in the MAVLink format. MAVLink provides an open data format for interaction as well as a suite of tools to assist the programmer in developing and testing the interface. Altum uses MAVLink v1.0 messages and communicates with the host at 57600 baud.


For more information and examples, please see https://www.micasense.com/api

Downwelling Light Sensor 2 (DLS 2)

The Downwelling Light Sensor (DLS 2) is an advanced incident light sensor that connects directly to Altum. During a mission, the DLS 2 measures the ambient light and sun angle for each of the five bands of the camera and records this information in the metadata of the TIFF images captured by the camera. This information can then be used by specialized processing tools (like Pix4Dmapper) to correct for global lighting changes in the middle of a flight, such as those that can happen due to clouds covering the sun.


In addition, the DLS 2 provides GPS data to Altum unless GPS data is provided from an external source as outlined earlier in this guide. If using an alternative GPS source, the GPS receiver will remain on at very low power (uBlox C/A code GPS @ 5 Hz).

Measurements and Attachment Points



14.03 mm


46.00 mm


63.50 mm


49 g


DLS 2 Connectors and Buttons

The sensor kit includes all required interface cables to connect to the DLS 2.

The LED camera status indicator mimics the LED signals on Altum. The signal types are outlined in the Sensor Firmware Guide. The camera trigger button will command a capture on the Altum. This is useful for capturing a preflight image of the calibration panel.


The RF connector is not available for use at this time but may be used in the future. When it is available, we will update this guide.


DLS 2 Installation Guidelines

The DLS 2 should always be the highest object on the aircraft in order to avoid shadows or reflections. It contains an integral GPS sensor that may be utilized for geotagging of the Altum imagery if system GPS signals are not provided to the sensor by other means.  Install the module where it will have a clear view of the sky, far away from any devices that could interfere with it (like a data link or video transmitters).


When the DLS 2 starts up, it attempts to calibrate, which requires it to be still and motionless.  Ensure that there is no vibration or movement until the DLS 2 has completed this procedure, indicated by normal LED status lights (shown in the Firmware Guide).



The 6-pin connector on the DLS 2 should be facing forward in the flight direction. Mounting it in the opposite direction will cause the magnetometer calibration process to be backwards.



Always install the DLS 2 at the high-point of the fuselage (if possible) to avoid any shadowing or reflections from aircraft fuselage or rotors.


Do not recess or embed the DLS 2 sensor body below the metallic base.


Local reflections could impact light sensor measurements. Avoid bright or metallic paint near the DLS 2 light sensor as this may interfere with incoming light values.


Install the DLS 2 on a rigid post such that it is the highest object on the aircraft, with a minimum of 5 cm above the rotor plane.


Ensure that there are no obstructions in the DLS 2’s field of view to the sky, including propellers and other items on the aircraft.


Keep the DLS 2 away from the aircraft GPS. Installing the DLS 2 near the aircraft GPS may impact the aircraft’s GPS reception.

Example Integration

Altum and DLS 2 on a Matrice 200. The sensor draws power directly from the Matrice via the Skyport.

The DLS 2 is the highest object on the aircraft.



MicaSense Altum and DLS 2 Integration Guide

Revision 09, June 2019

MicaSense, Inc.

Seattle WA 98103




  • The contents of this guide are subject to change without notice
  • MicaSense, Inc. assumes no liability for incidental or consequential damages arising from the use of this product, and any claims by a third party.
  • Copying of the contents of this guide, in whole or in part is prohibited under the copyright law.


© 2019 MicaSense, Inc

Have more questions? Submit a request