User Guide for MicaSense Sensors


Download this guide as a PDF



Seattle, WA

Table of Contents 

Table of Contents        1

Updating the Firmware        3

Establishing a Connection        4

Wi-Fi Connection  4

Ethernet Connection  4

Web Configuration Page Overview        5

Home Page        6

Live View Page        7

Capture  8

QR  8

Streaming  8

Exposure (Advanced)  9

Options  9

API  10

Coverage Page  10

Download KMZ  10

Pre-Flight Estimator  11

Coverage Estimator  12

Settings Page        16

Basic Configuration        17

Timer Mode  17

External Trigger Mode  18

Overlap Mode  19

Manual Exposure  19

Advanced Configuration        20

Audio Options  20

Format for RAW files  20

PPS Pin Usage  21

Pin Purpose  21

Input (default)  21

Top of Frame Output  21

Post Processing Required  21

Technical Information and Options  22

Pulse Polarity  22

Streaming Allowed  22

Enabled SD Card Output  22

Multi-Sensor Configuration  22

Ethernet Configuration  23

Configure the host computer  23

Configure the sensor’s IP address (optional)  23

Magnetometer Calibration        24

Magnetic Heading Check  27

Magnetic Interference Check  28

File Storage        29

LED Signals        30

Sensor/DLS 2 LED Signals  30

DLS 1 LED Signals  31

MicaSense Sensor APIs        32


Serial API  32

API Documentation  32


Updating the Firmware

It is essential to keep the sensor firmware updated at all times. The firmware in the sensor can be easily updated as follows:

Establishing a Connection

Any device (such as a computer, tablet, or smartphone) can be used to establish a connection with the sensor using Wi-Fi or Ethernet.

Wi-Fi Connection

When the sensor has been powered on and has finished initializing, it will broadcast a Wi-Fi signal (if the Wi-Fi adapter is attached). The SSID includes the sensor name and serial number. The serial number is printed on the rear of the sensor.


The password for this Wi-Fi access point is 


 Once connected to the sensor’s Wi-Fi, open any web browser and access the sensor’s web page by typing in “” in the address bar of the browser (no quotes).

Ethernet Connection

It is possible to connect to the sensor via Ethernet. First, you will need a cable or adapter that connects an Ethernet cable to the appropriate port on the sensor (see your sensor’s integration guide for details).


Manual TCP/IP configuration is required. Set the host computer’s Ethernet to use a manual IP address in the block We recommend the IP address if it is not in use already. Set the host computer’s subnet mask to


Once the host computer's Ethernet has been configured, connect to the configuration page using the Ethernet IP address ( by default). The IP address can be changed in Settings > Advanced > Ethernet Configuration.


Web Configuration Page Overview

There are 4 main “pages” for the sensor:



Home Page


Live View Page


Coverage Page


Settings Page



Home Page 

Provides status information for the sensor and the GPS receiver that is connected to it.

The time is provided by a connected GPS device. If no GPS is found, the time will show as UNIX time (January 1, 1970). If and when the sensor detects a GPS it will update the time automatically.

“Capture Config” shows the current automatic trigger setting (overlap, timer, external trigger, or disabled).

Storage: This will report your available and maximum storage space, as well as the file system (e.g. FAT32). 

GPS Sats: Indicates the amount of satellites that are detected and currently being used. There is also an area at the bottom of the page that shows the signal strength of detected satellites.

DLS Status: Will be green if DLS is powered and communicating with the camera.

Time: Will initially be set at UNIX time (1970-01-01 00:00:00 UTC). Once GPS has a lock, this will update to the current date/time in UTC (Universal Time). It cannot be changed to a different time zone, as many data processing programs rely on UTC for accurate calculations.

Location: This is the detected location coming from GPS, written in Decimal Degrees. 

Altitude: This indicates your current altitude in Mean Seal Level (MSL) and Above Ground Level (AGL).

The altitude AGL reported on the status page is an estimate based on the initial GPS lock received by the camera. If the initial GPS lock is not very accurate, it's possible for the AGL reported to be significantly off, especially as a better GPS lock is established over time. Powering the camera off and then back on will reset the ground estimate.

Speed: Current speed detected in meters per second. These unit of measurement cannot be converted at this time.

Heading: Your current magnetic heading. If properly calibrated, you can check the reading against a handheld compass to verify its accuracy. We recommend re-calibrating the compass regularly, but at the very least when it has been moved to another location on the aircraft, or if you are flying in a different time zone (which would slightly alter the magnetic heading).

Capture Config: This shows your current setting for your Automatic Triggering Mode. 


Live View Page 

Provides a live preview of images captured with the sensor.



Whenever the sensor captures images manually (using either the physical button or the web button), the selected image(s) will be displayed in the Live View page based on the setting of the “Band” pull-down menu. Instead of displaying “All Bands” you can choose to display individual band numbers, which are notated in the image above. The total number of bands available for display depends on the sensor.


The capture button forces a capture for the sensor, and is equivalent to pressing the manual trigger button on the sensor.


The QR button starts automatic panel detection mode. In this mode, the sensor displays a live preview, updated about twice every second. The configuration page and sensors with internal speakers will play a sound until the sensor detects a MicaSense reflectance panel and QR code. Once detected, the sensor will trigger a capture of the panel automatically and exit the mode. To exit the automatic panel detection mode, press the “Stop” button.


The Streaming checkbox is used for near-real-time preview images from the sensor. When the Streaming mode is enabled, the images shown will update as quickly as the sensor can support it (approximately twice a second). The “Refresh count” shows how many times the display has been updated. Note that streaming mode does not save any images to the storage device. It just enables fast capture of the sensor for preview purposes only. Streaming mode works best when connected to the sensor via Ethernet.


Please note that if you are using a multi-camera system, such as the RedEdge-MX Dual Camera System, this streaming mode will be unavailable.





Streaming mode is intended for live-preview. Disable streaming mode before starting any other operations (particularly before enabling auto-capture mode or flying).



Exposure (Advanced)

If Manual Exposure has been enabled in the Settings page, exposure settings will appear at the top of the Live View page. There are exposure settings available for each band of the sensor. These settings will apply to each image the sensor takes until they are changed or disabled.  



This is an advanced operation option and should normally be disabled. By default, the sensor automatically adjusts gain and exposure.



The first option controls the length of exposure. It ranges from 0.066 ms to 24.5 ms and indicates the amount of time the global shutter is “open” and recording light.


The second option controls the gain, which indicates how much to amplify the incoming signal. The available values are 1x, 2x, 4x, and 8x. The original pixel values are multiplied by the chosen option.


These settings can be configured dynamically using the MicaSense API. See the exposure section of the API documentation for details:

Coverage Page

The coverage page provides information on the geographic location where images in the storage device were captured based on the GPS module information. This page also provides a calculator for estimating parameters for mission planning.




Download KMZ

Clicking the “captures.kmz” link will cause the sensor to generate a KMZ file that will be downloaded by your browser. The KMZ file contains the lat/lon/alt of all captures in the storage device and can be used to verify coverage after a flight or series of flights. The KMZ file can be opened using a GIS application (like QGIS or Google Earth)



Pre-Flight Estimator

The Pre-flight Estimator is a calculator that can estimate the results of a flight mission. Enter the mission parameters and press the “calculate” button to see the results below.


Coverage Estimator


The Coverage Estimator is a tool for quickly checking that a flight has sufficient overlap. From the initial Coverage Page, select one or more image sets to estimate and click “Next” (note: image sets must be geographically close together in order to work properly).

The Flight Adjustment tab should appear, and show a summary of its current estimation settings. Sensor Orientation indicates the directionality of the sensor with respect to the aircraft, as shown below.

The Flight AGL is estimated based on the GPS positions recorded for the images, with the assumption that calibration panel pictures were taken near ground level, but if the estimate is incorrect, you can manually enter the correct AGL.

The Estimate Resolution sets the quality of the output map. Low is sufficient for most applications.



Clicking “Draw Coverage” will render the coverage estimate. The rendering time depends on your device’s CPU, the size of the field, number of images, flight AGL, and quality setting, but typically runs in under 30 seconds on a modern smartphone.


Finally, you will be presented with an estimate of your coverage. This is a colorblind-friendly color scheme.

Dark blue areas have a high probability of correctly being processed in photogrammetry software such as Pix4D. Areas that are orange may work, but likely will not. Red areas will almost certainly not process correctly. Edges around the field will typically show as red or orange. This is okay as long as the data you are trying to collect is all contained within the dark blue region.


Example of good field coverage (above)  

 If you discover that your field coverage estimate shows poor coverage, double check to make sure the Flight AGL is set correctly. If the Flight AGL is incorrect, click back on the Flight Adjustment section, correct the Flight AGL, then click on “Draw Coverage” again. If the Flight AGL is correct, your overlap settings may have be wrong. You will need to capture more images of the field to ensure that post-processing will be successful.

The most common cause of incorrect overlap is that the sensor’s parameters have not been entered into the flight planning software for use in calculating track distances. Check our knowledge base or your sensor’s integration guide for sensor parameters that should be used in flight planning. You can also confirm that the track spacing is correct by checking it against the values given by the sensor’s Pre-Flight Estimator tool (“Distance between capture” is the forward overlap distance and “Distance between track” is the side overlap distance).


Settings Page 

The settings page is used primarily to configure the Auto-Capture options for the sensor. The sensor supports three methods of Auto-Capture: Timer mode, External Trigger mode, and Overlap mode.  




Basic Configuration

Timer Mode

Use the drop-down menu to select Auto-Capture Mode as “Timer” 



In the updated window, specify the “Timer Period (sec)” (the interval between pictures) to the desired setting. If the timer interval is set to less than 1.0 seconds, the sensor may not run at the specified interval, but will capture as quickly as it can (about once per second).


Press the “Save” button to save the Timer mode settings. Items that have been changed will be colored yellow until saved, at which point they will turn green.


Press the Start button to begin capturing images at the desired interval rate.


Press the Stop button to stop capturing images.


External Trigger Mode


For external trigger mode, you will need to connect a triggering signal to the sensor – refer to your sensor’s Integration Guide.

Use the drop-down menu to select Auto-Capture Mode as “Ext. Trigger”



In the updated window, select the external trigger mode from the list. The settings are as follows:




Rising Edge

Sensor will trigger on the rising edge of a pulse

Falling Edge

Sensor will trigger on the falling edge of a pulse

Short PWM

Sensor will trigger if PWM transitions from longer than Threshold to shorter than Threshold

Long PWM

Sensor will trigger if PWM transitions from shorter than Threshold to longer than Threshold


For PWM mode, enter the threshold PWM – note that this value is in milliseconds (ms), so the value is typically between 1.0 and 2.0.


Press the “Save” button to save the External Trigger mode settings.


Verify that the triggering is functioning by commanding a sensor capture through the host device.


Overlap Mode

Use the drop-down menu to select Auto-Capture Mode as “Overlap”




In the updated window, select the Target Alt to be the altitude AGL (Above Ground Level) at which the aircraft will be operating during the mapping mission. Note that this is specified as AGL altitude.


Specify the Along-Track Overlap as a percentage (%) of image that is common between one image and the next one.

Specify the Target Alt Tolerance. This is the distance from your target altitude that the camera will begin capturing. If your target altitude is 120 meters, and you set the Target Alt Tolerance to 50 meters, the camera will begin capturing once it reaches 70 meters. 

Press the “Save” button to confirm the settings.


When the aircraft reaches the target altitude minus 50 meters, it will initiate taking captures. In overlap mode, it will only take a capture if the distance traveled is detected to be greater than the required distance at the specified target altitude as specified in the % overlap setting.


For example, if you set the target altitude to 120 meters, the sensor will start capturing when it reaches 70 meters altitude. When the measured altitude is lower than 70 meters (target altitude minus 50 meters), the sensor stops capturing.

Manual Exposure

The manual exposure checkbox enables manual control of the exposure and gain of the sensor, with settings available in the Live View Page. This is an advanced operation option and should normally NOT be enabled.


Disabled Mode

This mode is designed only for use with a PSDK (SkyPort) enabled camera models. This mode disables the camera’s automatic triggering functions, and will require trigger commands directly from the drone via PSDK.

Advanced Configuration

The Advanced Configuration menu provides controls for managing file storage as well as Ethernet and Multi-Sensor configurations.




Make sure to click the “Save” button after making any changes, or the changes will be lost.


Audio Options

On sensors that have internal speakers, users can enable or disable audio output. This applies to all sounds, including the start-up sound as well as the sound made during the “QR” or automatic panel detection mode.

Format for RAW files

You can specify the RAW Format to be either 12-bit TIFF (DNG) or 16-bit TIFF. The 12-bit DNG TIFF format will produce files that are 25% smaller in size than 16-bit TIFF files, but are not supported by some image software. Note that the sensor outputs 12-bit data, so storing the data as 12-bit DNG TIFF is lossless, whereas storing it as 16-bit TIFFs adds extra padding (but is still lossless).

PPS Pin Usage

You can specify how you wish to use the PPS pin on the sensor. PPS Pin Usage differs between RedEdge and Altum. For details about PPS pin usage and Top of Frame output, please visit the integration guide specific to your sensor model. For advanced integrations, this pin can be changed from a digital input to a digital output in the Advanced Configuration page.

Pin Purpose

Altum’s Pin 3 is an output. By default, it is a PPS output. For advanced integrations, this pin can be configured as a Top of Frame output instead, to signal to external devices the precise moment when the Altum captures images.

Input (default)

RedEdge GPS Pin 4 is, by default, a general-purpose input pin but can become an output pin as specified below.

Top of Frame Output



Enabling Top of Frame output changes the PPS pin purpose from a digital input to a digital output.


Damage to the sensor may occur if another output pin, such as the PPS output on a GPS receiver, is connected when Top of Frame Output mode is enabled.


If you are using the provided GPS, please disconnect it entirely or at least unplug the wire going to the PPS pin before enabling top-of-frame output.


This is for advanced integrations only, when external hardware, such as an RTK GPS receiver, needs to know the precise moment the sensor captures images. It is available in firmware version 1.5.28 and higher.

Post Processing Required

If you use top-of-frame output with an RTK GPS device, you will have to update the metadata of the images with the RTK GPS information in post processing; the sensor does not write this information into the image metadata. As a backup, it is a good idea to send constant GPS information to the sensor during flight using the Serial or HTTP APIs (, which the sensor will write into the image metadata.

Technical Information and Options

The Top of Frame output is a 3.0 V, 1 ms pulse, with the leading edge indicating the beginning of the exposures. The output should be considered an open-drain output (though it has an edge-accelerator in both directions). Large capacitive loads can cause the edge-accelerator to be triggered multiple times as the signal rises and falls which may cause double triggering. The output is coupled to the connector pin through a 100 ohm resistor and has around 25 pF of capacitance to the pin.

Pulse Polarity

“Pulse high, rest low”: The pin will output 0 V until a capture is taken, then it will output a 3 V signal for 1 ms.


“Pulse low, rest high”:  The pin will output 3 V until a capture is taken, then it will output 0 V for 1 ms.

Streaming Allowed

When enabled, if the sensor is in streaming mode, a top-of-frame output signal will be sent each time the image updates (about once per second), even though the images shown in streaming mode are not saved to the storage device.

Enabled SD Card Output

This menu enables the user to specify which bands to write to the SD card. The default of capturing all bands is the recommended setting. However, if only a subset of the bands are desired, the other bands can be deselected. Click the “Save” button to commit any changes.

Multi-Sensor Configuration

The Network Mode is only relevant if you have more than one sensor and wish to capture simultaneously. The table will list the settings of all other networked sensors. In addition to configuring a single master (main), all of the sensor software versions should match. After changing the sensor’s network mode, you must click “Save”, and then reboot the sensor in order for the new setting to take effect.


Below is an example of what it should look like when using the RedEdge-MX Dual Camera system. Notice that the one camera is the “main” and the other(s) are “auxiliary”.


The DLS 2 will always be listed as auxiliary.


Ethernet Configuration

Here, you can assign a different Ethernet IP address to the sensor. To use the Ethernet, you will need to obtain or build an adapter that connects to the appropriate port on the sensor (see your sensor’s integration guide or the MicaSense knowledge base for details).



The Ethernet IP address is by default. Changing this setting does not update the Wi-Fi address, which will always be


Configure the host computer

Set the host computer Ethernet to use a manual IP address in the block We recommend the IP address if it is not in use already. Set the host computer’s subnet mask to


Once you have configured your host computer's Ethernet, you can connect to the configuration page using the IP address you have set up.

Configure the sensor’s IP address (optional)

The Ethernet IP address is by default. If you would like to change this, you may need to connect via Wi-Fi. Enter the desired IP address (must be on the same subnet as the host computer) and press Save. The sensor must be rebooted for an IP change to take effect.

Storage and Firmware

Update Firmware

This section displays a list of all *.bin files on the attached USB drive. Use the radio button to select the .bin file you wish to use to upgrade.  Alternatively, click the "Choose File" or "Browse" button to select a different file on your computer.  Once the file of choice is selected, click the "Update Firmware" button to begin the update process. Do not disconnect the power or turn off the sensor until the process is complete.

Reformat Storage

Press the “Reformat Storage” button to erase all data on the attached storage device and reformat the device to a compatible format type (FAT32).



A warning will appear for confirmation.Press “OK” to format and erase all data on the storage device or “Cancel” to keep all information on the disk







FAT32 is the only supported file system for RedEdge cameras. If you are using high-capacity SD cards, you will need to reformat them to FAT32 using this tool before the camera can reliably write images to the SD card.



Magnetometer Calibration


This procedure is for the provided GPS only and is not required for configurations that provide GPS and attitude information via the serial or Ethernet connection. If the configuration for your sensor is one that uses the provided module for GPS and magnetometer data, a calibration process for the magnetometer is needed.



You will need a compass to verify the calibration once completed.


From the Settings page, access the DLS Configuration section.



“Calibrate DLS Mag” is a clickable button that will start the calibration process. This calibration process is for the magnetometer sensor that is inside the 3DR GPS module.


Ensure that the DLS is connected to the GPS module with both the 4-pin and 6-pin connectors. Additionally, your DLS and GPS module should be rigidly mounted to your aircraft frame.







Before beginning the calibration routine, position yourself and the drone away from large metal objects such as cars and buildings. Also avoid paved areas, which may have metal rods inside the cement. An open field is preferred to avoid interaction with any sources of magnetic interference or objects that may perturb the Earth’s natural magnetic field.


Once the startup sequence has finished, you will be guided through the orientations your drone should be in for each of the calibration steps.



To calibrate the magnetometer, a 6-axis calibration routine needs to be performed. During the routine, the drone (specifically the GPS module) should remain in a fixed position while being rotated, i.e. the user performing the calibration should be moving around the magnetometer. The drone and GPS module should also be kept level to the plane they are on in each position. The on-screen rotation guide will show you when you have successfully completed one orientation and can move on to the next.



The black dot is a level (like a bubble level), indicating how level the unit is compared to the plane it is on. It does not indicate how far away from the center of rotation the unit is.






If you are using a Serial or HTTP connection to supply GPS and attitude information to the sensor, you do not need to perform the magnetometer calibration described above.



Magnetic Heading Check 

Once the calibration routine has been completed, it is important to verify that the magnetometer information displayed in the Heading section of the sensor’s Home Page is accurate.


A handheld compass has been provided with your kit that will allow you to verify this in the field. Access the sensor’s Home Page and use the “Heading” field to check the four cardinal directions (North, East, South, West) and ensure a good match between the compass and the reading by the sensor. You should see an error of less than +/- 5 degrees. If this error is exceeded, redo the magnetometer calibration.



Additionally, you will want to perform a magnetic interference test to verify that your drone will not affect the heading readings during flight.


Magnetic Interference Check


A test procedure should be conducted any time electrical equipment is added or removed from the drone to ensure the magnetic field profile of the aircraft has not changed.


To test for any magnetic interference from the drone that is affecting the magnetometer, start by placing your drone facing North (you can use the magnetic heading from the Wi-Fi page to align yourself).





The next section involves spinning up the motors of your drone.


If you have a fixed wing aircraft this will require holding the aircraft in place while keeping clear of the propeller.


If using a multi-rotor, setup the aircraft as if it was ready for a normal take off, but you do not need to actually take off, just spin up of motors.


You DO NOT need to provide full power to the motor(s).


Throttle up the motor(s) on your drone and ensure that the heading reading has not changed, then throttle back down. Repeat this for each direction (North, East, South, West) to ensure there is no magnetic interference in any of the four cardinal directions.








Electromagnetic interference during the operation of your drone can cause errors in the magnetic heading readings. This can cause the irradiance data generated by the DLS to be not usable during processing.


File Storage

The sensor stores files in the storage device in a folder structure. A new folder is created for each time the sensor is powered up. For example: “0000SET”, “0001SET”, ...



Within each folder, a subfolder with the images themselves is created. If more than 200 images are stored, a second image folder is created (“000” and “001” for instance). Two log files are also created for each sensor power cycle (diag.dat and paramlog.dat). The log files are proprietary and can only be read by MicaSense.


Within each subfolder, a group of TIFF files is created for each image capture. The suffix at the end of each file indicates the imager number. Please see your sensor’s integration guide for details.


The TIFF files are 12-bit resolution stored in either 12-bit DNG TIFF RAW format or 16-bit TIFF RAW format, depending on the setting (see Settings > Advanced). Metadata tags are embedded for each file in standard EXIF format.



12-Bit DNG

16-Bit TIFF

Files per capture


Altum (MS)

4.78 MB

6.4 MB


2064 x 1544

Altum (Thermal)

45 KB

45 KB


160 x 120


1.8 MB

2.5 MB


1280 x 960


Altum-PT (MS) 4.8 MB 6.4 MB 5 2064 x 1544
Altum-Pt (PS) 18.6 MB 24.7 MB 1 4112 x 3008
Altum-PT (Thermal) 170.9 KB 170.9 KB 1 320 x 256
Rededge-P (MS) 2.4 MB 3.2 MB 5 1456 x 1088
Rededge-P (PS) 7.6 MB 10.1 MB 1 2462 x 2056


LED Signals

Sensor/DLS 2 LED Signals

One flash indicates normal behavior, that the sensor is operating as expected. More than one flash indicates an issue as outlined in the following table:






1 Flash

Sensor is ready for operation (it has a GPS fix and more than 2 GB available on the storage device)


1 Flash

Capture completed


2 Flashes

GPS unit detected, but does not have a fix


3 Flashes

GPS timeout


4 Flashes

No storage device is installed


5 Flashes

The storage device is full (or almost full)


If you see more than 5 red flashes, contact support.

DLS 2 LED Signals

The DLS 2 LED mimics the attached camera’s LED signals, except during initial start-up. When powered on, the DLS 2 LED cycles through all of the colors for a “rainbow” effect, indicating that the DLS 2 is calibrating and needs to be motionless. Aircraft vibration and other subtle movement could cause the DLS 2 to stay in calibration mode until the motion stops.

DLS 1 LED Signals

There are two green LED lights on the DLS 1, one on either side of the unit. The meaning of the LEDs is as shown in the table below. The LEDs are small and may not be easy to see without getting close to the unit. Refer to the following table for signal meanings:


DLS LED Signal Type


4 simultaneous flashes on both LEDs

This occurs upon boot-up of the DLS

Sporadic flashing

Communications received. This is normal behavior

Alternating blinking between the two LEDs

Indicates a software/hardware problem. If the problem persists, contact MicaSense at

Both LEDs solid ON

Indicates a software/hardware problem. If the problem persists, contact MicaSense at



Power OFF the sensor before removing the storage device. Failure to do so may corrupt some of the files in the storage device if they are still being written.



MicaSense Sensor APIs

Using the API, users can communicate with the sensor programmatically via an HTTP or Serial connection.


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

Serial API

The Serial API provides a MAVLink interface to the sensor. You can use this API by connecting your MAVLink-capable system to the serial connections on the sensor. See the Integration Guide for your sensor to determine where to connect.

API Documentation

For the latest API documentation, including example code, please visit:



User Guide for MicaSense Sensors

Revision 10, Jan 2022

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.


© 2018-2020 MicaSense, Inc

Have more questions? Submit a request