User manual

Phantom Miro Control via "Touch-Sensitive" LCD Screens 289

To Edit a specific MultiCine follow the steps described in the Phantom Miro Control via

"Touch-Sensitive" LCD Screens>Step-by-Step Procedures>Editing a Stored Cine File.

To Delete a specific MultiCine follow the steps described in the Phantom Miro Control via

"Touch-Sensitive" LCD Screens>Step-by-Step Procedures>Deleting a Stored Cine File.

Deleting All MultiCine Files Stored in DRAM

From the Cine Screen Display gently tap on the Delete All Selector.

In the Delete All Cines? Display gently tap Yes to delete all MultiCine recorded to the

partitioned DRAM, or click No to return to the Cine Screen Display.

6.2.17 Using Image-Based Auto-Trigger with a Phantom Miro

WARNING

The Image-Based Auto-Trigger feature should never be used in applications where missed or

false triggers cannot be tolerated or where a false trigger could cause harm to people or

property.

The hardware signaling available in some Image-Based Auto-Trigger modes should be used

only to synchronize multiple Phantom cameras together and should never be used to trigger or

control any other external device or event.

CONSEQUENCES RESULTING FROM SYSTEM FAILURE, FALSE TRIGGERING OR MISUSE OF

THIS FEATURE ARE THE SOLE RESPONSIBILITY OF THE USER.

Introduction

The Image-Based Auto-Trigger feature allows the user to trigger the camera from the motion

detected in the live image.

General Operation

The Image-Based Auto-Trigger feature allows selected Phantom camera models, (Miro 2, Miro

eX 2 (optional), Miro 4, and Miro eX 4, to trigger themselves when the image changes in a

selectable region of the frame.

A few user definable parameters allow the auto-trigger behavior to be adjusted to operating

conditions, filtering out unintended triggers due to vibration, changes in illumination, slow-moving

shadows, etc.

The Auto-Trigger operation begins by the user selecting a rectangular area within the image,

similar to the region used for auto-exposure, the Auto-Trigger region.

As each frame is captured, the image in the Auto-Trigger region is compared to an earlier copy of

the same region that has been stored in a dedicated memory. After the comparison is made, the

image in memory is updated to the current image, to be used in the future.

The result of the comparison determines if a trigger is generated. A pixel being compared is