Flight & Sensor Control Management System

FCMS 3.
22 Documentation
All basic volumes
This Documentation contains important information. Please

read carefully through before you use the system.
Document code 757 041

Document release Version 3.22-15, Feb / 24 / 2010
FCMS Documentation
This document shall not be reproduced in whole or in part without prior permission in writing
from Leica Geosystems AG, 9435 Heerbrugg (Switzerland), either by mechanical, photographic,
electronic, or other means (including conversion into or transmission in machine-readable form);
stored in any retrieval system; used for any purpose other than that/ those for which it is
intended; nor accessible or communicated in any form to any third party not expressly authorized
by Leica Geosystems AG to have access thereto.
ii Version 3.22-15 - Feb / 24 / 2010

FCMS Documentation
Contents
Leica FCMS Documentation

Volume 1 User Manual . . . . . . . . . . . . . . . . . . . xxiii
Volume 2 Field Manual . . . . . . . . . . . . . . . . . . . . . 85
Volume 3 Installation Information . . . . . . . . . . . 217
Version 3.22-15 - Feb / 25 / 2010 iii

FCMS Documentation
Contents
iv Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Contents FCMS Documentationi

About FCMS Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi
Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi
Where to get more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi
Version 3.22-15 - Feb / 25 / 2010 v

FCMS Documentation
Volume 1 User Manual . . . . . . . . . . . . . . . . . . . xxiii
About this User Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Scope of document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Product identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Meaning of symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Where to get assistance and training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Headquarter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Contact Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Overview of different setups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
IS40 Interface Stand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
OC52 and OC50 for operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
OC50 for pilot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
GI40 Guidance Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Installing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Pre-requirements for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
General note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installation of the operator interface OC52 / OC50. . . . . . . . . . . . . . . . . . 13
Installation of IS40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Attaching of OC52 or OC50 Operator Controller . . . . . . . . . . . . . . . . . . . . 14
Adjustment of IS40 and OC50/OC52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installation of the OC50 for pilot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Adaptation of the anti-dazzle shield. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installation of the Guidance Indicator GI40. . . . . . . . . . . . . . . . . . . . . . . . 15
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Cabling overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chassis ground connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Connection to GNSS antenna. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Power cable connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Software and Firmware installation and update . . . . . . . . . . . . . . . . . . . . . . . . 21
Update of GI40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Update of OC52/OC50 for operator and of OC50 for pilot . . . . . . . . . . . . 21
Installation of 3rd party Software on the OC for Operator . . . . . . . . . . . . . . . . . 23
Installation of 3rd party software on the OC52/OC50 for Operator . . . . . . 23
Preparation before installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
vi Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Installation of 3rd party software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Restore system protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Perform system test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Automatic license check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
License file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Upload of license file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Trouble shooting for license file upload . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
User check of license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
System Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Before starting the system for the first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Flight checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Important notes for the photo flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
FCMS Field Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Hardware operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Power switches on devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Power switch on OC52/OC50 for operator . . . . . . . . . . . . . . . . . . . . . . . . . 30
Power switch on OC50 for pilot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Mandatory procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
For takeoff and landing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
For takeoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Start-up sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
System shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Status LEDs and status messages on the hardware. . . . . . . . . . . . . . . . . . . . . 32
Status LEDs on devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Locking management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
First help level- short description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Second help level - online documentation . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Language selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Select the language for the operator on the operator interface. . . . . . . . . . . 36
Select the language for the pilot on the OC50 for pilot . . . . . . . . . . . . . . . . 36
File operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
How to select data in the file selection dialogs . . . . . . . . . . . . . . . . . . . . . 38
Delete Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Delete data on the external USB stick . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Delete data in the Control Unit memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Version 3.22-15 - Feb / 25 / 2010 vii

FCMS Documentation
Select data and delete it . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Upload projects with flight plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Download projects, flight plans and flight data.. . . . . . . . . . . . . . . . . . . . . 40
Flight execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Pre-flight check list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Start flight execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Ground start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Air-Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Sensor Status view during start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Sensor status and configuration after successful start-up . . . . . . . . . . . . . . 43
FCMS views, controls and GUI during flight execution. . . . . . . . . . . . . . . 43
Operation during flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Main user tasks during flight execution. . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Flight plan controlled flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Manually controlled flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Manual Start / Stop line sensor data recording . . . . . . . . . . . . . . . . . . . . . 45
Start recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Stop recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Manual release of frame sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Prepare for manual frame release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Manual frame release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Quit frame release level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Annotation - user log file entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Log data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Flight plan controlled flight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Project and flight plan selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Flight line selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Direct selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Selection from the line listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Selection by line number or line label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Reverse line execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Abort line or project execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Shorten and/or extend a line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Marking sections of a line during data recording . . . . . . . . . . . . . . . . . . . 55
User activation of FCMS route-finder algorithm . . . . . . . . . . . . . . . . . . . . 56
System check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Trouble shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
When FCMS is running. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
During flight execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Failure of the master sensor of a multi-sensor system . . . . . . . . . . . . . . . . . 58
Export of status data for error analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Care & Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Care. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Cleaning and drying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Cables and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
viii Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Touch screen of the OC52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Dust filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Replacement of dust filters on the OC50/52 . . . . . . . . . . . . . . . . . . . . . . . 61
Safety Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Safety Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Intended use of the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Prohibited use of the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Usage limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Limits of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Manufacturer of the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Manufacturers of non Leica Geosystems accessories . . . . . . . . . . . . . . . 65
Person in charge of the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Hazards of use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Electromagnetic Compatibility EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
FCC Statement, Applicable in U.S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Type shields on OC52 with or without keyboard. . . . . . . . . . . . . . . . . . . . . 70
Type shields on OC50 for operator (with keyboard) for Pilot (without key-
board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
About Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Applied standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Conformity to national regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Hardware components for FMCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Devices and parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Tools and accessories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Documentation, Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Warranty - Software License Agreement . . . . . . . . . . . . . . . . . . 77

International Limited Warranty, Software License Agreement . . . . . . . . . . . . . 78
International Limited Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Software License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Version 3.22-15 - Feb / 25 / 2010 ix

FCMS Documentation
Microsoft End User License Agreement ("EULA"). . . . . . . . . . . . . . . . . . . . . . . 79

End user license agreement for MICROSOFT embedded systems . . . . . 79
Product specific terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
General terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
x Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Volume 2 Field Manual . . . . . . . . . . . . . . . . . . . . . 85
About Field Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Scope of document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Product identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Meaning of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Where to get more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Where to get assistance and training . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
General for photo flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
GNSS requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Required GNSS quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Distance to GNSS ground reference station for DGNSS processing. . . . . . 90
Distance to GNSS ground reference station for PPP processing . . . . . . . . . 91
Location of GNSS ground reference station . . . . . . . . . . . . . . . . . . . . . . . . 91
Hints for the sensor operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Hints for the pilot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Flight plan requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Flight recommendations and mandatory procedures . . . . . . . . . . . . . . . . . . . . 92
Turns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
On the flight line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
In-flight alignment for GNSS-IMU system . . . . . . . . . . . . . . . . . . . . . . . . . 93
FCMS - Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
FCMS tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Basic function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Main task of the Software module ‘Flight Guidance’ . . . . . . . . . . . . . . . . . 96
Main task of the module ‘Remote Control’ . . . . . . . . . . . . . . . . . . . . . . . . . 96
Highlights of FCMS for ALS, frame and other sensors . . . . . . . . . . . . . . . 97
Modular software components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Easy to learn and simple operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
High-precision, GNSS-supported navigation. . . . . . . . . . . . . . . . . . . . . . . . 97
Automatic sensor release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Multi-sensor system control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Monitoring the progress of project execution . . . . . . . . . . . . . . . . . . . . . . . 97
In-flight quality control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Accurate repetition of specific flight sections . . . . . . . . . . . . . . . . . . . . . . . 98
Flexible user log entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Version 3.22-15 - Feb / 25 / 2010 xi

FCMS Documentation
Data logging for post-flight evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Leica FCMS, the optimal interface in the Leica work flow . . . . . . . . . . . . 98
GUI design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Controls to group information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Use of color to group information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figurative language on icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Key figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Key figures for components of the sensor system . . . . . . . . . . . . . . . . . 102
Icon types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
General screen layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Touch screen interface on OC52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Hard key interface on OC50 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Navigation within the menu tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Navigation within the menu tree in flight execution. . . . . . . . . . . . . . . . . 107
Navigation within the menu tree to reach ‘Configuration’ . . . . . . . . . . . . 108
Menu ‘Configuration’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Menu ‘Flight’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
First help level- short description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Second help level - online documentation . . . . . . . . . . . . . . . . . . . . . . . 110
Icon reference list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Most frequently used icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Icons for the on-line help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Icons to control sensor release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Icons to change views during flight execution. . . . . . . . . . . . . . . . . . . . . 113
Icons to scroll in list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Icons to select input fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Icons to enter values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Input and message control icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Icons to select / unselect data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Icons to edit / create data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Icons for execution of planned flights . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Icons to adjust video image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
More icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Icons to zoom graphical information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Icons to show or hide data in graphical or alphanumerical views . . . . . . 120
Icons to filter data when browsing log data . . . . . . . . . . . . . . . . . . . . . . . 122
Icons to copy data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Icons in service area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Icons to delete data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Icons for stabilized mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
FCMS - Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

About configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
xii Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Configuration data base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Data base structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Configuration sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Pre-defined configuration sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
User defined configuration sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Current configuration set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
System configuration: Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Sensor and GNSS Configuration sets for different sensors . . . . . . . . . . 131
Enter Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Sensor configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Select configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Sensor type ‘ALS LAN’. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Typical setting ‘ALS60 LAN with frame sensor’ . . . . . . . . . . . . . . . . . . . 135
Sensor type ‘ALS via Serial’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Typical setting ‘ALS via Serial with frame sensor’ . . . . . . . . . . . . . . . . . . 136
Typical setting ‘Line Sensor without protocol’ . . . . . . . . . . . . . . . . . . . . . 137
Typical setting ‘Line Sensor with protocol’. . . . . . . . . . . . . . . . . . . . . . . . 137
Typical setting ‘Frame Sensor without protocol’. . . . . . . . . . . . . . . . . . . . 138
Typical setting ‘Frame Sensor with protocol’ . . . . . . . . . . . . . . . . . . . . . . 138
Typical setting ‘RC30’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Typical setting ‘R10/RC20’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Typical setting ‘No Camera’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
GNSS- IMU system configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Typical setting ‘IPAS (LAN)’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Typical setting ‘Simulator’. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Typical setting ‘Simulator IPAS’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Typical setting ‘NMEA (RS232)’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Typical setting ‘POS Legacy fibre’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
System configuration: Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Overview configuration of Global 1 parameters . . . . . . . . . . . . . . . . . . . 147
Configuration of ‘Flight Guidance & Sensor Release’. . . . . . . . . . . . . . . 147
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Names of pre-configured ‘Flight Release’ configuration sets . . . . . . . . . . 148
Flight Release configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Configuration of Guidance Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Configuration of Guidance Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Configuration of Sensor Release and Control . . . . . . . . . . . . . . . . . . . . . . 154
Summary of Flight Guidance & Sensor Release settings . . . . . . . . . . . . . 156
Configuration of parameter ‘Time zone’ . . . . . . . . . . . . . . . . . . . . . . . . . 157
Configuration of parameter ‘Installation’ . . . . . . . . . . . . . . . . . . . . . . . . . 158
Configuration if the IMU type is pre-defined for the Sensor. . . . . . . . . . . 158
Configuration if IMU type is not pre-defined for the Sensor Head . . . . . . 159
Configuration if the sensor is installed 180° opposite to the flight direction. .
160
Version 3.22-15 - Feb / 25 / 2010 xiii

FCMS Documentation
Overview configuration of Global 2 parameters . . . . . . . . . . . . . . . . . . . 160

Configuration of global parameters ‘Units’ . . . . . . . . . . . . . . . . . . . . . . . 161
Configuration of global parameters ‘Views’. . . . . . . . . . . . . . . . . . . . . . . 162
Configuration ‘Advanced’ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
FCMS - Flight Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Basic layout of navigation view during flight execution . . . . . . . . . . . . . . . . . . 166
Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
What is a control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
System controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Take-Off control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Sensor control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Sensor control for Generic Sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Sensor control for Leica RC30. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Memory control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
GNSS control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Flight guidance controls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Color codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Wind control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Track and line direction control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Track deviation control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Position control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
North-up navigation control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Nose-up navigation control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Line deviation control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
In-line navigation control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
3-D Navigation control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
3-D Navigation control during approach . . . . . . . . . . . . . . . . . . . . . . . . . . 179
3-D Navigation control along the line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Flying altitude control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Aircraft to target control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Line progress control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Speed control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Speed control for ALS60 or a multi-sensor system ‘ALS60+Frame’ . . . . 187
Speed control for generic line sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Speed control for frame sensor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Controls with project related information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Project control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Flight plan controlled flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Manually controlled flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Project progress control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Data filter control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Project area control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
xiv Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Line detail control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Graphic in-flight evaluation control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Alphanumeric in-flight evaluation control . . . . . . . . . . . . . . . . . . . . . . . . 193
Views during flight execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
FCMS views for flight navigation and project management . . . . . . . . . . 194
FCMS views for sensor controll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Sensor status views for all types of sensors . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Main system status view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
GNSS status view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
GNSS-IMU status view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Mount status view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Leica ALS60 specific status view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Flight guidance views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Nose-up view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
North-up view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
In-line view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
3-D Navigation view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Flight Guidance information on the GI40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Guidance information on the GI40 during approach . . . . . . . . . . . . . . . . 206
Guidance information on the GI40 along the flight line . . . . . . . . . . . . . . 208
Error information on the GI40 along the flight line . . . . . . . . . . . . . . . . . 209
Project status views for in-flight evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Graphic and alphanumeric in-flight evaluation . . . . . . . . . . . . . . . . . . . . 210
In-flight evaluation - graphic view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
In-flight evaluation - alphanumeric view. . . . . . . . . . . . . . . . . . . . . . . . . . 212
Annotation - user log file entries during flight . . . . . . . . . . . . . . . . . . . . . . . . . 213
Edit or create annotation text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Browsing of logged status data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Start browser from Flight menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Start browser from Service menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Browsing log data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Version 3.22-15 - Feb / 25 / 2010 xv

FCMS Documentation
Volume 3 Installation Information . . . . . . . . . . . 217
About Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . 219

Scope of document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Structure of this volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Product identification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Meaning of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Where to get more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Where to get assistance and training . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Aircraft Installation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Leica Geosystems company profile. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Leica Geosystems’ Business Unit Digital Imaging . . . . . . . . . . . . . . . . . 222
Large format airborne sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Leica Geosystems Sensor Installation Policy . . . . . . . . . . . . . . . . . . . . . . . . . 223
Sensor and GNSS installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Environment and Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Aircraft modifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Responsibility for aircraft modifications. . . . . . . . . . . . . . . . . . . . . . . . . . 223
Main tasks to be performed by the installer . . . . . . . . . . . . . . . . . . . . . . 223
Installation tasks to be performed by the user . . . . . . . . . . . . . . . . . . . . 224
Leica Geosystems installation support . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Leica Geosystems installation drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Environmental qualification form OC50 and GI40 . . . . . . . . . . . . . . . . . . . . . . 225
Environmental qualification form OC52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Installation of IS40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Ideal position of IS40 in aircraft. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Chassis ground connection between IS40 and aircraft structure . . . . . . 227
IS40 base plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Installation of OC52/OC50 for operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Ideal position of OC52/OC50 for operator in aircraft. . . . . . . . . . . . . . . . 230
Alternative mounting without means of the IS40. . . . . . . . . . . . . . . . . . . 230
Chassis ground connection for OC52/OC50 for operator . . . . . . . . . . . . 230
Summary OC52/OC50 for operator if mounted not on IS40 . . . . . . . . . . 230
Airflow for cooling purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Installation of OC50 for pilot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Ideal position of OC50 for pilot in aircraft . . . . . . . . . . . . . . . . . . . . . . . . 237
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Storage of the OC50 for pilot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
xvi Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Chassis ground connection for OC50 for pilot . . . . . . . . . . . . . . . . . . . . 237

Summary OC50 for pilot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Airflow for cooling purposes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Installation of GI40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Ideal position of GI40 in aircraft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Storage of the GI40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Summary GI40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Chassis ground connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
General about cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Cabling diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Power connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Version 3.22-15 - Feb / 25 / 2010 xvii

FCMS Documentation
xviii Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Chapter 0 About FCMS Documentation
Version 3.22-15 Feb / 24 / 2010 xix

FCMS Documentation
xx Version 3.22-15 - Feb / 24 / 2010

FCMS Documentation
General
The FCMS documentation consists of several volumes. It is distributed as a whole or as subsets.
Sub-sets contain only some of the volumes, selected according to the needs of the target reader.
Volumes
• Volume 1 - User Manual, document code 757 046
It contains important safety directions as well as instructions for setting up the system. The
volume also describes how to operate and maintain the system as well as important care and
handling information and Technical Data.
• Volume 2 - Field Manual

It provides complete description of the software.
• Volume 3 - Installation Information

It contains all information and data for preparing an aircraft for installation of the hardware
components for FCMS.
Where to get more information

Internet www.leica-geosystems.com
Version 3.22-15 - Feb / 24 / 2010 xxi

FCMS Documentation
xxii Version 3.22-15 - Feb / 24 / 2010

FCMS Documentation Volume - 1
User Manual
This User Manual contains important information. Please read

carefully through before you use the system.
Document code 757 046

Volume 1 FCMS User Manual
xxiv Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Contents
Content User Manual

About this User Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Scope of document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Product identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Meaning of symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Where to get assistance and training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Headquarter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Contact Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
System Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Overview of different setups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
IS40 Interface Stand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
OC52 and OC50 for operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
OC50 for pilot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
GI40 Guidance Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Installing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Hardware installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Pre-requirements for installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
General note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Installation of the operator interface OC52 / OC50. . . . . . . . . . . . . . . . . . 13
Installation of IS40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Attaching of OC52 or OC50 Operator Controller . . . . . . . . . . . . . . . . . . . . 14
Adjustment of IS40 and OC50/OC52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installation of the OC50 for pilot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Adaptation of the anti-dazzle shield. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installation of the Guidance Indicator GI40. . . . . . . . . . . . . . . . . . . . . . . . 15
Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Cabling overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Chassis ground connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Connection to GNSS antenna. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Power cable connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Software and Firmware installation and update . . . . . . . . . . . . . . . . . . . . . . . . 21
Update of GI40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Update of OC52/OC50 for operator and of OC50 for pilot . . . . . . . . . . . . 21
Installation of 3rd party Software on the OC for Operator . . . . . . . . . . . . . . . . . 23
Installation of 3rd party software on the OC52/OC50 for Operator . . . . . . 23
Version 3.22-15 - Feb / 25 / 2010 xxv

FCMS Documentation
Contents
Preparation before installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Installation of 3rd party software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Restore system protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Perform system test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Automatic license check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
License file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Upload of license file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Trouble shooting for license file upload . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
User check of license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
System Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Before starting the system for the first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Flight checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
FCMS Field Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Hardware operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Power switches on devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Power switch on OC52/OC50 for operator . . . . . . . . . . . . . . . . . . . . . . . . . 30
Power switch on OC50 for pilot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Mandatory procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
For takeoff and landing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
For takeoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Start-up sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
System shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Status LEDs and status messages on the hardware. . . . . . . . . . . . . . . . . . . . . 32
Status LEDs on devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Software operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Locking management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
First help level- short description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Second help level - online documentation . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Language selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Select the language for the operator on the operator interface. . . . . . . . . . . 36
Select the language for the pilot on the OC50 for pilot . . . . . . . . . . . . . . . . 36
File operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
How to select data in the file selection dialogs . . . . . . . . . . . . . . . . . . . . . 38
Delete Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Delete data on the external USB stick . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
xxvi Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Contents
Delete data in the Control Unit memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Select data and delete it . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Upload projects with flight plans. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Download projects, flight plans and flight data.. . . . . . . . . . . . . . . . . . . . . 40
Flight execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Pre-flight check list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Start flight execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Ground start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Air-Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Sensor Status view during start-up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Sensor status and configuration after successful start-up . . . . . . . . . . . . . . 43
FCMS views, controls and GUI during flight execution. . . . . . . . . . . . . . . 43
Operation during flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Main user tasks during flight execution. . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Flight plan controlled flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Manually controlled flight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Manual Start / Stop line sensor data recording . . . . . . . . . . . . . . . . . . . . . 45
Start recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Stop recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Manual release of frame sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Prepare for manual frame release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Manual frame release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Quit frame release level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Annotation - user log file entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Log data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Flight plan controlled flight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Project and flight plan selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Flight line selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Direct selection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Selection from the line listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Selection by line number or line label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Reverse line execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Abort line or project execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Shorten and/or extend a line. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Marking sections of a line during data recording . . . . . . . . . . . . . . . . . . . 55
User activation of FCMS route-finder algorithm . . . . . . . . . . . . . . . . . . . . 56
System check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Trouble shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
When FCMS is running. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
During flight execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Failure of the master sensor of a multi-sensor system . . . . . . . . . . . . . . . . . 58
Export of status data for error analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Care & Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Care. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Cleaning and drying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Version 3.22-15 - Feb / 25 / 2010 xxvii

FCMS Documentation
Contents
Cables and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Touch screen of the OC52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Dust filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Replacement of dust filters on the OC50/52 . . . . . . . . . . . . . . . . . . . . . . . 61
Safety Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Safety Directions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Intended use of the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Prohibited use of the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Usage limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Limits of Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Manufacturer of the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Manufacturers of non Leica Geosystems accessories . . . . . . . . . . . . . . . 65
Person in charge of the product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Hazards of use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Electromagnetic Compatibility EMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
FCC Statement, Applicable in U.S. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Type shields on OC52 with or without keyboard. . . . . . . . . . . . . . . . . . . . . 70
Type shields on OC50 for operator (with keyboard) for Pilot (without key-
board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
About Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Applied standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Conformity to national regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Hardware components for FMCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Devices and parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Cables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Tools and accessories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Documentation, Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Warranty - Software License Agreement . . . . . . . . . . . . . . . . . . 77

International Limited Warranty, Software License Agreement . . . . . . . . . . . . . 78
International Limited Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
xxviii Version 3.22-15 - Feb / 25 / 2010

FCMS Documentation
Contents
Software License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Microsoft End User License Agreement ("EULA"). . . . . . . . . . . . . . . . . . . . . . . 79
End user license agreement for MICROSOFT embedded systems . . . . . 79
Product specific terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
General terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Version 3.22-15 - Feb / 25 / 2010 xxix

FCMS Documentation
Contents
xxx Version 3.22-15 - Feb / 25 / 2010

Chapter 1 About this User Manual
Version 3.22-15 Feb / 25 / 2010 1

Scope of document
This User Manual contains important safety directions as well as instructions for setting up the
system, operating and maintaining it.
Important: Read carefully through the User Manual before you switch on the system
This User Manual describes:

• Description. See section "System Description" in Volume 1, Chapter 2 on Page 7.
• Installation. See section "Installing the system" in Volume 1, Chapter 3 on Page 11
• Operation. See section "System Operation" in Volume 1, Chapter 4 on Page 27.
• Care and handling. See section "Care & Handling" in Volume 1, Chapter 5 on Page 59.
• Safety directions such that the system can be used quickly and safely. See section "Safety
Directions" in Volume 1, Chapter 6 on Page 63.
• Technical data. See section "Technical Data" in Volume 1, Chapter 7 on Page 71
Product identification
The article numbers and serial numbers of the components of the FCMS are indicated on the type
shields. Enter them in the table below, and always refer to this information when you need to
contact your agency or service center.
Table 1. Product identification
Device Article number Serial number

OC50 for operator
OC50 for pilot
GI40
2 Version 3.22-15 - Feb / 25 / 2010

Abbreviations
Table 2. Abbreviations
Abbreviation Meaning
ADS Airborne Digital Sensor
AGL Above ground level
ALS Airborne Laser Scanner
ALT Altitude
AMSL Altitude above mean sea level
CD Compact Disk
CT Sensor Cycle Time
CU Control Unit
DGPS Differential GPS
FCMS Flight & Sensor Control Management System
FPES Flight Planning & Evaluation Software
FW Firmware
GI Guidance Indicator
GLONASS Global Navigation Satellite System (Russia)
GNSS Global Navigation Satellite System
GPS Global Positioning System
GS Ground Speed (Speed over Ground)
GSD Ground Sampling Distance
GUI Graphical User Interface
HDG Heading
HDOP Horizontal Dilution of Precision
HW Hardware
IMU Inertial Measurement Unit
IP Initial Point
IPAS Inertial Position & Attitude System
IS Interface Stand
IT Integration Time
LAN Local Area Network
MM Mass Memory
OC Operation Controller
OI Operator Interface
PAV Gyro-stabilized camera mount
PCMCIA Personal Computer Memory Card International Association
PDOP Position Dilution of Precision
POS Positioning and Orientation System
PPP Precise Point Positioning
Version 3.22-15 - Feb / 25 / 2010 3

Table 2. Abbreviations
Abbreviation Meaning
RTCM Radio Technical Commission for Maritime Services
SW Software
TGT True Ground Track
TRM Technical Reference Manual
USB Universal Serial Bus
USM User Manual
UTC Coordinated Universal Time
WGS84 World Geodetic System 1984
4 Version 3.22-15 - Feb / 25 / 2010

Meaning of symbols
Danger: Indicates an imminently hazardous situation which, if not avoided, will result in
death or serious injury.
Warning: Indicates a potentially hazardous situation which, if not avoided, could result in
death or serious injury.
Caution: Indicates a potentially hazardous situation which, if not avoided, may result in minor
or moderate injury and/or appreciable material, financial and environmental damage. The symbol
is also used to alert against unsafe practices.
Important: Important paragraphs which must be adhered to in practice as they enable the
product to be used in a technically-correct and efficient manner.
Note: Highlights a point of special interest about a topic under discussion.
Tip: This points to a useful hint that may save time and trouble.
Trademarks
• Windows and Windows XP are registered trademarks of Microsoft Corporation

• CompactFlash and CF are trademarks of SanDisk Corporation
• Bluetooth is a registered trademark of Bluetooth SIG, Inc.
All other trademarks are the property of their respective owners.
Version 3.22-15 - Feb / 25 / 2010 5

Where to get assistance and training

Important: Please be aware, that for a complete understanding of the functionality and
operation of the system it is necessary to participate in a Leica ADS80 product training and
maintenance course.
For assistance and training courses please contact your local Leica Geosystems subsidiary or rep-
resentative.
Headquarter
Contact Leica Geosystems AG e-mail:
Business Unit Digital Imaging info@leica-geosystems.com
Heinrich-Wild-Strasse Phone: + 41 71 727 3131
9435 Heerbrugg Fax: + 41 71 727 4674
Switzerland
Contact Support
Region Contact e-mail
Americas sensors@leica-geosystems.com
U.S.A., Canada, Central & South America
Asia / Pacific sensors-ap@leica-geosystems.com
(incl. Australia and China, except Japan / Korea)
EMEA sensors-emea@leica-geosystems.com
Europe, Middle East & Africa
Japan / Korea sensors-jako@leica-geosystems.com
6 Version 3.22-15 - Feb / 25 / 2010

Chapter 2 System Description
Version 3.22-15 Feb / 25 / 2010 7

Components
Overview of different setups

The Hardware and Software allow three different flight guidance setups.
Figure 1: FCMS flight guidance setups
FCMS setup premium FCMS setup standard FCMS setup economic
Components
1. OC52 with keyboard
2. IS40 Interface Stand
3. OC50 for pilot
4. GI40 Guidance Indicator
5. Control Unit of the Sensor System
Figure 2: Examples of other setup possibilities
OC50 for operator Setup with 2nd device for the operator.
Additional OC52 or OC50
8 Version 3.22-15 - Feb / 25 / 2010

IS40 Interface Stand

The IS40 holds the OC52 or the OC50 for operator. All
adjustable parts can be safely blocked.
To meet safety requirements the tube can be separated easily and
stored in a safe place.
1. IS40 base plate

2. IS40 tubes
3. Fixing plate for OC52/OC50 for operator
OC52 and OC50 for operator

Front side of OC52
1. Status LED
2. Power switch
3. Touch screen
4. Hardware keys
5. Keyboard
Front side of OC50 for operator

1. Status LED
2. Power switch
3. Screen
4. Hardware keys
5. Keyboard
Rear side of OC50 for operator, also valid for OC52

1. LEMO connector for Keyboard
2. USB port
3. Airflow grid
4. Connection to OC50 for pilot or GI40
5. Connection to control unit of sensor system
6. Fastening thread
Version 3.22-15 - Feb / 25 / 2010 9

OC50 for pilot
1. Airflow grid
2. Power switch
3. Screen
4. Hardware keys
5. Removable dazzle shield
GI40 Guidance Indicator

The GI40 provides guidance information to the pilot. It is
designed to be placed on the dashboard in the cockpit or
any other desired place.
Brightness is controlled automatically depending on the
ambient illumination level.
To switch off the GI40 simply disconnect the device.
10 Version 3.22-15 - Feb / 25 / 2010

Chapter 3 Installing the system
Version 3.22-15 Feb / 25 / 2010 11

Unpacking
Important: The FCMS hardware components are shipped in a shock-protected shipping case.
Check the shock indicators which are located outside the shipping cases. If an indicator appears
RED, inform the freight handler immediately. Also inspect all components and make sure they
are not damaged.
Hardware installation
Pre-requirements for installation

Is is assumed that a provider authorized for installation of payloads has completed all the tasks
listed in section "Main tasks to be performed by the installer" in Volume 3, Chapter 2 on Page
223.
General note
This chapter contains only information about installation for and by the user for the FCMS com-
ponents of the sensor system. Sensor system specific information can be found in the correspond-
ing sensor system manuals.
Important: Install all components according to the guidelines given by the authorized provider
for installation of payloads.
Use only hardware from the authorized provider for installation of payloads to secure the compo-
nents to the aircraft.
Important: Install complete payload. The complete payload consists of all components of the
sensor system. Do not power on individual components if the complete payload is not installed
and/or all cable connections are not made correctly.
12 Version 3.22-15 - Feb / 25 / 2010

Installation of the operator interface OC52 / OC50
Installation of IS40
Procedure
1. Place the IS40 base plate on to the prepared location
in the aircraft.
2. Ensure that the IS40 base plate is securely fastened
to the aircraft structure according to the guidelines
given by the authorized installer.
3. Ensure efficient chassis ground connection from

IS40 base plate to the aircraft structure according to
the guidelines given by the authorized aircraft
installer.
As an example the photo on the left shows a chassis
ground strap connected to one of the two conductive
areas located close to the tube.
Ground connection can also be made by means of
the conductive areas surrounding the screw holes.
4. Insert the tube into the IS40 base plate.

5. Fasten and tighten the lever on the flange of the
IS40.
Version 3.22-15 - Feb / 25 / 2010 13

Attaching of OC52 or OC50 Operator Controller

Procedure
1. Place the fixing plate of the OC52/OC50 for Opera-
tor on to the fixing plate of the IS40 tube.
The two centering bolts on the IS40 fixing plate
must fit into the centering holes on the OC50 fixing
plate.
2. Fasten the centering screw to ensure safe fixing of

the OC50/OC52 on the IS40.
Adjustment of IS40 and OC50/OC52

Procedure
1. Adjust height of the IS40 tube as desired for conve-
nient operation.
2. Fasten and tighten the lever.
3. Adjust inclination of the OC50/OC52 on the IS40

tube as desired for convenient operation.
4. Fasten and tighten the lever.
14 Version 3.22-15 - Feb / 25 / 2010

Installation of the OC50 for pilot

Note: The OC50 for pilot is part of the flight guidance setup ‘standard’ or ‘premium’.
Procedure
1. Place the OC50 on to the prepared location in the
aircraft.
2. Ensure that the OC50 is securely fastened according
to the guidelines given by the authorized installer.
OC50 screw holes to the aircraft structure accord-
ing to the guidelines given by the authorized air-
craft installer.
Adaptation of the anti-dazzle shield

Depending on the place of the OC50 in the cockpit an anti-dazzle shield might be required to
avoid reflection on the OC50 screen. A number of anti-dazzle shields are provided with the stan-
dard delivery. This shield is a low-cost item (consumable) part. Cut it to adapt it for a specific
installation and the pilot’s requirements.
Adaptation of the anti-dazzle shield
1. Attach the anti-dazzle shield to the OC50
2. On the anti-dazzle shield mark the shape which fits
the pilots needs.
3. Use a scissors to cut the shield into the required
shape.
Installation of the Guidance Indicator GI40

Note: The GI40 is part of the flight guidance setup ‘economic’ or ‘premium’.
Procedure
1. Place the GI40 on to the prepared location in the air-
craft.
2. Ensure that the GI40 is securely fastened according
to the guidelines given by the authorized installer.
GI40 screw holes to the aircraft structure according
to the guidelines given by the authorized aircraft
installer.
Version 3.22-15 - Feb / 25 / 2010 15

Cabling
Cabling overview
Note: Below only the cabling of FCMS components is described. Cabling information for the
components of the sensor system is given in the corresponding sensor installation documen-
tation.
Caution:
Do not modify the cables.
Do not extend the cable lengths.
All cables needs to be connected according to Figure 3. Additional information is given in the
paragraphs below.
Tip: The part numbers of the cable are labeled on the cables, close to one of the connectors.
Figure 3: FCMS components cabling diagram for ALS60
Connection of OC50 for pilot and GI40

Both devices can be connected in series to the OC52/OC50 for operator. Connect the OC50 for
pilot to the OC52/OC50 for operator and the GI40 to the OC50 for pilot. The plugs on the OC50/
52 as well as the connectors of the cables are color coded. Connect the cables on the OC50/52
corresponding to the colors.
If no OC50 for pilot is installed, the GI40 is connected to the OC52/OC50 for operator.
16 Version 3.22-15 - Feb / 25 / 2010

Cabling of multi-sensor systems
Figure 4: FCMS cabling diagram for ALS60 + RCD105
Figure 5: FCMS cabling diagram for ADS80 + ALS60
Version 3.22-15 - Feb / 25 / 2010 17

Cabling with IPAS20
Figure 6: FCMS cabling diagram for RC30 with IPAS20and RCIF30
Figure 7: FCMS cabling IPAS20 with up to four sensors
18 Version 3.22-15 - Feb / 25 / 2010

Figure 8: FCMS cabling IPAS20 with PAV30 and two 3rd party sensors
Figure 9: FCMS cabling IPAS20 with PAV80 and two 3rd party sensors
Version 3.22-15 - Feb / 25 / 2010 19

Chassis ground connection

Caution: For safety reasons, an efficient chassis ground connection between the aircraft
structure and the following FCMS hardware components has to be fulfilled:
IS40, OC52/OC50 for operator if not installed on IS40, OC50 for pilot.
Details about chassis ground connection for components of the sensor system are given in the
corresponding sensor system documentation.
Connection to GNSS antenna

Caution: On the fuselage of a survey flight aircraft often more than one GNSS antenna is
installed. Make sure the GNSS antenna cable is connected to the GNSS antenna for the Leica
RCD100. GNSS antennas can have different electrical characteristics. If a GNSS antenna is
connected to the Leica RCD100 system which does not fit, the Leica RCD100 system can
become damaged or the GNSS data quality is poor.
Power cable connection

Warning: Power for all components of the sensor system should only be supplied directly
from the power source of the aircraft. Be sure to use only the connectors and plugs as
defined by the authorized provider for installation of the payload.
The OC52/OC50 for operator, the OC50 for pilot and the GI40 have no power connector to the
aircraft power source. Power is provided by the sensor system. How to connect the sensor system
to the aircraft power is described in the corresponding sensor installation documentation.
20 Version 3.22-15 - Feb / 25 / 2010

Software and Firmware installation and update

Depending on the sensor system a FCMS release consists either of Software or a full set of Soft-
ware and Firmware. The FCMS installation process takes care of the correct installation for a
dedicated sensor system. Software and Firmware to update the system comes on a CD/DVD. If
this is not the case (e.g. Software was downloaded from the Web) copy the Software and Firm-
ware to a CD/DVD. Software and Firmware update of the sensor system is made through the CD/
DVD drive. Depending on the sensor system the CD/DVD drive is connected either to the OC52/
OC50 for operator, the OC50 for pilot or the Control Unit of the Sensor System. The CD/DVD
drive is connected via the USB port.
Important: To ensure proper power use the HUB and always both cables to connect the DVD/
CD drive to the OC50/OC52.
Important: Make sure the same FCMS version is installed on all components: OC52/OC50 for
operator, OC50 for pilot and GI40.
Update of GI40
Connect the GI40 to the OC50/52. The GI40 Firmware will be updated during the OC50/52
update process. No other user action is required.
Update of OC52/OC50 for operator and of OC50 for pilot

Note: Different hardware setups can be used for FCMS. The OC50 for pilot and the GI40 are
not always part of the system. If either OC50 for pilot or GI40 is missing, the corresponding
steps or instructions listed below can be skipped.
To update the SW and FW, proceed as follows:
1. Make sure the sensor system’s control unit power switch is OFF
2. Make sure the power switches on the OC52/OC50 for operator and OC50 for pilot are OFF
3. Connect the OC52/OC50 for operator to the sensor control unit.
4. Connect the OC50 for pilot to the OC52/OC50 for operator
5. Connect the GI40 to the OC50 for Pilot or to the OC52/OC50 for operator.
Important: The steps 6 to 16 must be performed two times. First perform it to update the
OC52/OC50 for operator. Second perform it to update the OC50 for pilot.
6. Connect the external CD drive to the USB port on the OC50/52:

Caution: Ensure non interrupted power during the whole update process. After a power failure
during the installation process the OC50/52 can be in an undefined state and only a Leica
Geosystems Service Engineer can recover it.
7. Insert the CD into the CD drive.

8. Set power switch to ON on the sensor control unit.
Version 3.22-15 - Feb / 25 / 2010 21

9. Set power switch to ON on OC50/52

10. Wait until FCMS main menu is displayed on the OC50/52.
Important: If the OC50 for pilot is updated do not make any selections in the FCMS on the
OC52/C50 for operator until the update is complete.
11. Select [Service] from FCMS main menu.
12. Select [SW-Upload] to enter dialog to install FCMS.
13. Confirm [Continue] to start installation process.
The system powers down, reboots and the installation will take place.
14. Watch the information displayed on the screen in a window with black background.
If an installation step fails a corresponding message is displayed. Do not interrupt the installa-
tion process. Proceed until the end of the installation procedure and after that contact a Leica
Geosystems Aerial Sensor Service Center because the system is not in an operational state.
Note: After the installation is complete the system restarts. Do not disconnect the CD drive nor
remove the CD from the drive! After restart the system is ready for use through the FCMS main
menu. Now the CD drive can be disconnected.
15. Select [End] to quit FCMS on OC50/52.
16. After automatic shutdown, switch OFF power on OC50/52
17. If step 15 was made to update the OC52/OC50 for operator start now the 2nd loop to update
the OC50 for pilot. Goto step 5. Perform all tasks to the OC50 for pilot.
22 Version 3.22-15 - Feb / 25 / 2010

Installation of 3rd party Software on the OC for Operator

Important: Do only install additional software on the OC50/52 if it is mandatory required to
operate 3rd party components which are add-ones to the Leica Geosystems sensor system.
On the OC50/52 the operating system and the installed Leica Geosystems software is protected
by a write filter. This ensures that the system does not get damaged e.g. during a power failure or
incorrect shutdown. Before software can be installed which is not provided by Leica Geosys-
tems, the write filter has to be disabled
Installation of 3rd party software on the OC52/OC50 for Operator

Caution: 3rd party software installation can damage the system . Also 3rd party software
running in parallel with with Leica Geosystem software can cause problems. It is the user’s
responsibility to verify that the 3rd party software does not in any case affect the performance of
the Leica Geosystems software.
Preparation before installation
Disable write filter

1. Execute’WriteFilterManagement.EXE from’ ‘Start->Program files-> Leica Geosystems ->
FCMS’
2. Confirm ‘Disable’
3. Confirm ‘Exit’
4. Shutdown and reboot the operating system on OC52/OC50 for Operator
Installation of 3rd party software

Install 3rd party software according to the installation guidelines given by the 3rd party software
provider. It is recommended to reboot the system after the installation has finished.
Restore system protection
Enable write filter

1. Execute ‘WriteFilterManagement.EXE’ from ‘Start->Program files-> Leica Geosystems ->
FCMS’
2. Confirm ‘Enable’
3. Confirm ‘Exit’
4. Shutdown and reboot the operating system on OC52/OC50 for Operator
Perform system test

Perform a system test to validate proper operation of the sensor system. See also section "System
check" in Volume 1, Chapter 4 on Page 57
Check the proper operation of the 3rd party software. If it is not running correctly the write filter
settings for this software may need to be adjusted.
Caution: Write filter adjustements require in-dept software knowledge. Only professionals in
this field of application shall try to tune the write filter. The write filter can be tuned with the
functions offered in the advanced section of the ’WriteFilterManagement.EXE’ programm.
Version 3.22-15 - Feb / 25 / 2010 23

Licensing
Automatic license check

On every startup FCMS automatically checks
the system license. If no license or if a
temporary license is found a message window is
displayed. See example on the left.
To upload a license file proceed as described in
section "License file" below.
License file
A license file has the following naming format:
AirborneLicense_Counter_SerialNumber.Filetype
The first section of the license file contains the description of the license.
Example of a license file AirborneLicense_2397_36072.txt:

Licensed Device: FCMS
System ID: 00-30-59-04-6A-0D
System serial number: 36072
Modules:
- Sensor Control ALS (766470), 3.10, permanent
- Flight Guidance (749513), 3.10, permanent
- Remote Control (749515), 3.10, permanent
Created on Thursday, December 11, 2008 by vol

License Version v3
#
F6Crm1WNOuTOMTS5uUJbhoNNdb6073vRL7h/h32xEUKDTXW+tO
970YNNdb6073vRg011vrTve9GkTe55ro2mOYoHfrM3jyCcG8tj
M99dxPPETZB+HiSEmKbyZCW0EFPxzlbc2U9Ym3/bPt+bQf8klQ
l3oSsuY8TZyTYhpIhgXXnfm83DdIAoNhQnR9wiNUWO2z7fm0H/
JJUJd6ErLmPE2ck2IaSIYF1535vNw3SAKDanul+fCcDAjds+35
tB/ySVCXehKy5jxNnJNiGkiGBded+bzcN0gCg22cwEqL/3dTTz
dRy0iOxMrfN1HLSI7Eyt
#
24 Version 3.22-15 - Feb / 25 / 2010

Upload of license file
To upload a license file proceed as follows:

1. Copy the license file to the root directory of the transfer media (USB stick).
2. Connect the transfer media to the OC52/OC50 for operator.
3. Set power switch to ON on sensor system control unit.
4. Wait until FCMS main menu is displayed.
6. Select [License]
The upload starts automatically. After the upload a message window displays whether a new
license file was uploaded or not. The message window also lists the licensed modules and their
expiration date. In case the license file was not uploaded make trouble shooting actions as given
below in section "Trouble shooting for license file upload".
7. Confirm [Accept] to close the message window.
8. Select [End] to quit FCMS on OC52/OC50 for operator.
Trouble shooting for license file upload

Table 3. License file upload failures
Error source Remedy - user action

No licence file found on Check content of the transfer media. Make sure the license file
transfer media. is available in the root directory.
License file contains license Check if latest license file was used. Check the license file for
which is already expired. license expiring date.
System ID does not match Check if the serial number of the OC corresponds to the serial
with license file. number in license file name. The serial number is also listed in
the license file. If the serial number is correct, export the
logfile (see section "Export of status data for error analysis" in
Volume 1, Chapter 4 on Page 58) and contact Leica
Geosystems Aerial Sensor Support.
Version 3.22-15 - Feb / 25 / 2010 25

User check of license
To check the installed license proceed as follows:

1. Set power switch to ON on sensor system control unit.
2. Wait until FCMS main menu is displayed.
4. Select [License]
The message ‘No new license uploaded’ and the licensed modules and the expiration date is dis-
played in a message window.
5. Confirm [Accept] to close the message window.
26 Version 3.22-15 - Feb / 25 / 2010

Chapter 4 System Operation
Version 3.22-15 Feb / 25 / 2010 27

Before starting the system for the first time

Important: Before you switch on the sensor system for the first time carry out the following
operations:
• Read through the user manuals of FCMS and the sensor system.
• Follow the installation recommendations with great care. See section "Installing the sys-
tem" in Volume 1, Chapter 3 on Page 11.
• Make sure that the correct supply voltage is available. See section "Electrical" in Volume
1, Chapter 7 on Page 72.
• Make sure that the cabling of the system is correct. See section "Cabling" in Volume 1,
Chapter 3 on Page 16.
• Be aware of the safety instructions. See whole chapter ‘Safety Direction’ starting with sec-
tion "Safety Directions" in Volume 1, Chapter 6 on Page 63.
Initial configuration
The system is delivered with pre-defined configuration sets. Nevertheless, the following global
configurations must be redefined:
• Sensor and mount type
• System installation parameters
- GNSS antenna vector
- selection of IMU type
- Aircraft ID, minimum and maximum aircraft speed
• Time zone
All configurations are set within the FCMS software. Please follow the instructions in section
"Configuration" in Volume 1, Chapter 4 on Page 36.
Important: Make sure initial configuration for Leica PAV80 is also made according to the
instructions given in the Leica PAV80 User Manual, section ‘Operation’, paragraph ‘Before
Starting the system the first time’
Flight checklist
Important: A flight checklist is delivered with the sensor system documentation. It is recom-
mended to operate the sensor system according to this checklist. The list contains specific checks
for the sensor system. General rules and procedures for a photo flight might be different for
various flight crews. Feel free to adapt the checklist according to your individual rules and
requirements.
28 Version 3.22-15 - Feb / 25 / 2010

Important notes for the photo flight
General
Warning: GNSS is not officially approved for flight navigation! FCMS is only a tool for
survey flight navigation. It only suggests an approach to the flight line and assists a user
when flying on the photo line. It is the full responsibility of the user to watch the airspace.
Important: Pay special attention to all paragraphs in the sensor system documentation about
flight recommendations and mandatory procedures. These paragraphs contain important infor-
mation which must be taken into account when executing photo flights with a specific sensors
system.
FCMS Field Manual

TheLeica RCD100 Field Manual contains important information which should be taken into
account for acquiring perfect data.
In section "General information for photo flights" in Volume 3, Chapter 2 on Page 191 the Field
Manual covers the following aspects:
• Required GNSS quality
• Distance to GNSS ground reference station
• Location of GNSS ground reference station
• Hints for the sensor operator
• Hints for the pilot
• Flight plan requirements
• Flight recommendations and mandatory procedures
• In-flight alignment for GNSS-IMU system
In section "FCMS - Flight Execution" in Volume 2, Chapter 5 on Page 165, the Field Manual
covers the following aspects:
• Basic layout of navigation view during flight execution
• Speed control and flying altitude control
• Device status and Project controls
• Views during flight execution
• GI40 Guidance Indicator during flight
Version 3.22-15 - Feb / 25 / 2010 29

Hardware operation
Note: This chapter contains only information about operation of the FCMS components of the
sensor system. Sensor system specific information can be found in the corresponding sensor
system manuals.
Important: The OC52 has a touch screen. Operate FCMS and other software only by pointing
with your fingers to the screen. To avoid scratches on the screen and malfunction of the touch
screen do not point with pencils, roller pens or other devices. If you like to point by using a
stylus use only a stylus designed for touch screen models.
Power switches on devices
Power switch on OC52/OC50 for operator

Switch position Function
. .
ON Power ON
. When power is set to ON, the OC52/OC50
. for operator boots and starts FCMS and
. specific sensor software automatically, if
. such SW is installed.
. .
OFF Power OFF.
Do not switch power OFF until Windows is
shut down.
See section "Shutdown sequence for FCMS
(including OC50 for pilot)" in Volume 1,
Power switch on OC50 for pilot

Switch position Function
. .
ON Power ON
. When power is set to ON, the OC50 for pilot
. boots and starts FCMS automatically. It then
. connects to the FCMS running on the OC52/
. OC50 for operator.
. .
OFF Power OFF.
Do not switch power OFF until the OC50 for
pilot is shutdown remotely from the OC52/
OC50 for operator or by pressing the
‘Startup/Shutdown’ key on the front panel
on the OC50 for pilot.
See section "Shutdown sequence for OC50
for pilot only" in Volume 1, Chapter 4 on
Page 31.
30 Version 3.22-15 - Feb / 25 / 2010

Mandatory procedures
For takeoff and landing

Warning: Store OC50 for pilot and GI40 in a safe place for takeoff and landing. Depending
on the safety recommendations given by the aircraft installer this might be valid for OC52/
OC50 for operator and the IS40 as well.
For takeoff
Important: If a Leica PAV is part of the sensor system the rotation of the axis must be locked
for takeoff.
The PAV30 is locked if it is set to operational mode ‘OFF/MANUAL’. Press the push button on
the operator panel to change manually the operational mode.
The PAV80 is locked by default. If this is not the case use FCMS or the PAV80 controller soft-
ware to change the operational mode. Select the mount status view to set the mode.
For both mounts manual setting is not required if a flight plan is selected in FCMS and if the user
has not changed the mount default settings.
Start-up sequence
Start-up sequence
1. Set power switches of the components of the sensor system to ON.
2. Set power switch on the OC52/OC50 for operator to ON.
3. Set power switch on the OC50 for pilot to ON. (If part of the system)
System shutdown
Shutdown sequence for FCMS (including OC50 for pilot)

1. Exit FCMS on the OC52/C50 for operator.
2. Terminate all specific sensor software
3. Shutdown windows
4. Wait until the Operating System is shut down.
5. Set power switch on OC52/OC50 for Operator to OFF.
6. Set power switch on OC50 for pilot to OFF.
Shutdown sequence for OC50 for pilot only

1. Press [Shutdown] key located on the front side below the status LED.
2. Wait until the Operating System on the OC50 for pilot is shut down.
3. Set power switch on OC50 for pilot to OFF.
Version 3.22-15 - Feb / 25 / 2010 31

Status LEDs and status messages on the hardware
Status LEDs on devices

Status LED on OC50/52 Color Indicated status
Green o.k.
Orange Temperature error
Red Voltage error
Status LED on GI40 Color Indicated status

Red Power ON
If the GI40 receives no flight guidance
information the display automatically is
switched off. This state is indicated by one
illuminated LED located on the upper right
center part of the display.
32 Version 3.22-15 - Feb / 25 / 2010

Software operation
General
Note: This chapter contains only information about operation of FCMS. Sensor system specific
information can be found in the corresponding sensor system manuals.
Figure 10: FCMS Main menu
From the main menu the following can be selected

• File operation
• Flight execution
• Mount
• Service
• Language
• Configuration
On-line help is selectable any time.
The Flight & Sensor Control Management System (FCMS) is used to conduct all aspects of a
flight plan controlled survey flight.
• Language and Configuration. See “Configuration” on Page 36.
• File operations. See “File operations” on Page 38.
• Flight execution. See “Flight execution” on Page 41.
• Mount see PAV80 documentation
• Service. See “Software and Firmware installation and update” on Page 21.
The following pages of the USM give information for the basic operation of FCMS. Additional
information is given in various chapters of the Field Manual.
Licensing
All FCMS software modules and components are licensed. If a system is not licensed or if the
license is expired an appropriate message is displayed on the operator interfaces after start-up.
How to upload a license file and how to check the license of a system is described in section
"Licensing" in Volume 1, Chapter 3 on Page 24.
Locking management
FCMS can be operated simultaneously from multiple user interfaces. To ensure unambiguous
configuration of the system a locking management is implemented.
Example:
To prevent the system from being configured at the same time by two different users the
configuration icon is controlled by the locking management. Who ever selects first a
configuration icon locks the icon on the other user interfaces. A locked icon is inactive and
therefore cannot be selected. If the first user returns from configuration the lock is released.
Version 3.22-15 - Feb / 25 / 2010 33

Online help
Online help can be selected from any menu level at any time. The 'Help' button is part of the but-
ton bar on each view. The online help facility consists of two levels:
• First help level gives a short description of each button on the status line.
• Second help level allows browsing of FCMS documentation.
Note: Entering help does not interrupt operation of the sensor. For example, if the recording of
data was activated, this status remains the same even if the user enters help.
First help level- short description

Select [Help] to activate first help level.
Select any button or control to display the corresponding help text in the status line.
Figure 11: Example view first help level
The Green background of the status line indicates that

first help level is activated.
In this mode, just touch any button or control to get a short
description of it on the status line.
Select [Help Return] to quit help level and to return to normal operation.
Select [Help Detail] to activate second help level to browse the FCMS documentation.
34 Version 3.22-15 - Feb / 25 / 2010

Second help level - online documentation

Note: Entering second level help is only possible from first level help. It does not interrupt
operation of the sensor. For example, if the recording of data was activated, this status remains
the same even if the user enters second level help.
Use [Left arrow] and [Right arrow] to jump to previous or next section of the text.
Use [Scroll up] and [Scroll down] to scroll smoothly in the text.
Use [Fast scroll up] and [Fast scroll down] to scroll pages in the text.
Use [Home] to jump to table of content in second help level. (Online documentation).
Select [Help-Return] to leave help level.
Version 3.22-15 - Feb / 25 / 2010 35

Configuration
Language selection
The language can be selected independently for the operator and for the pilot. Therefore, lan-
guage selection has to be made individually on each user interface
Important: Make sure flight execution is not started on the operator interface.
Select the language for the operator on the operator interface.

Select [Language] from the main menu on the operator interface.
Figure 12: ‘Language selection’ dialog
The black frame indicates the selected language.

The following languages are currently implemented:
• English
• German
• Spanish
• Portuguese
• Japanese, if installed
Use [TAB left] or [TAB right] to move the selection to the desired configuration set.
Select [Return] to activate the selected language and to return from the dialog to main menu.
Select the language for the pilot on the OC50 for pilot
Important: Before you select the language for the pilot make sure that FCMS is not in flight
mode. Check if on the OI40 operator interface FCMS is in the main menu.
Select [Language] from the main menu on the OC50 for pilot.
36 Version 3.22-15 - Feb / 25 / 2010

Initial configuration
Important: This must always be performed under the following circumstances:
• after installation (either upon first use of system or when system is moved to another air-
craft)
• when time zone has changed
The following initial configuration must be made:
• Sensor and mount type
See section "Sensor configuration" in Volume 2, Chapter 4 on Page 133
• GNSS system
See section "GNSS- IMU system configuration" in Volume 2, Chapter 4 on Page 141
• Flight Guidance & Sensor Release configuration
See section "Overview configuration of Global 1 parameters" in Volume 2, Chapter 4 on
Page 147.
• Time zone
See section "Configuration of parameter ‘Time zone’" in Volume 2, Chapter 4 on Page 157
• Installation
- GNSS antenna vector
- selection of IMU type
- Aircraft ID, minimum and maximum aircraft speed
See section "Configuration of parameter ‘Installation’" in Volume 2, Chapter 4 on Page 158
Version 3.22-15 - Feb / 25 / 2010 37

File operations
How to select data in the file selection dialogs

Note: The procedure below is an example. It is valid for data selection on the external memory
or internal memory.
Figure 13: Example of ‘Delete Project data’ dialog
To delete data proceed as follows

1. Mark the files
2. Delete marked files
Use the arrow up and arrow down button to move the

highlighted bar.
Use [Scroll Up] [Scroll Down] to move the highlighted bar to the desired file.
Use [+] to expand listing.
Use [-] to collapse listing.
Use [Select] to mark the file at the current highlighted bar position.
Select [Select All] to mark all files.
Select [Deselect] if a marked file should not be selected.
Select [Deselect All] if all marked file should not be selected.
38 Version 3.22-15 - Feb / 25 / 2010

Delete Data
Select [File] from FCMS main menu to enter file operations.
Select [Delete].
Delete data on the external USB stick

Attach the USB memory stick to the USB port on the OC52 or OC50 for Operator
Select [Delete external] to enter dialog to delete data on the USB memory stick.
Delete data in the Control Unit memory

Select [Delete Internal] to enter dialog to delete data in the Control Unit memory.
Select data and delete it

Select data as described in section "How to select data in the file selection dialogs" in Volume 1,
Select [Delete selected] to delete the marked files from the storage media (either external, internal
or Memory). A window opens for ‘Continue delete’ or ‘Cancel’.
Select [Return] to return. If files are marked for deleting, a window opens with the question
whether the selection shall be rejected or not. In case of ‘OK’ the ‘Delete’ dialog quits. Cancel
returns to the ‘Delete’ dialog.
Version 3.22-15 - Feb / 25 / 2010 39

Upload projects with flight plans.

Important: Attach the USB memory stick to the USB port on the OC52 or OC50 for Operator.
Make sure FCMS is in the Main menu during this operation. Because some sticks are not recog-
nized by the operating system, if they are attached either before or during system start-up.
Select [Upload selected] to enter dialog to select data on the USB memory stick.
Select [Upload selected] to upload the marked files.
During upload a message window and a turning hour glass pops up.
Select [Return] to return. If files are marked, a window opens with the question whether the
selection shall be rejected or not. In case of ‘OK’ the ‘Upload’ dialog quits. Cancel returns to the
‘Upload’ dialog.
Download projects, flight plans and flight data.

Important: Attach the USB memory stick to the USB port on the OC52 or OC50 for Operator.
Make sure FCMS is in the Main menu during this operation. Because some sticks are not recog-
nized by the operating system, if they are attached either before or during system start-up.
Select [Download selected] to enter dialog to select data.
Select [Download selected] to download the marked files.
During download a message window and a turning hour glass pops up.
Select [Return] to return. If files are marked, a window opens with the question whether the
selection shall be rejected or not. In case of ‘OK’ the ‘Download’ dialog quits. Cancel returns to
the ‘Download’ dialog.
40 Version 3.22-15 - Feb / 25 / 2010

Flight execution
Pre-flight check list

• Required GNSS quality available for the time span of the photo flight?
See section "Flight recommendations and mandatory procedures" in Volume 2, Chapter 2 on
Page 92.
• Whole system properly installed in the aircraft and ready for takeoff?
See section "Unpacking" in Volume 1, Chapter 3 on Page 12.
• Cabling of all components is in accordance with diagram?
See section "Cabling" in Volume 1, Chapter 3 on Page 16.
• All cables properly laid out and connected, no danger for bending of fiber optic cable,
clamping of cables on PAV etc.?
• Front of the sensor head of the installed sensor system and of the belly of the aircraft free
from dust and oil?
• Old data deleted
• Check for sufficient disk space on memory.
• Flight plans uploaded?
See section "Upload projects with flight plans." in Volume 1, Chapter 4 on Page 40.
• Global configuration parameters ‘Time Zone’ and ‘Installation’ set correctly?
See section "Configuration of parameter ‘Time zone’" in Volume 2, Chapter 4 on Page 157.
• Data recording at GNSS ground reference station(s) started? (valid if data are required for
DGNSS postprocessing)
Tip: A flight checklist is stored on the sensor system documentation CD in DOC-format. It is

recommended to operate the sensor system according to this checklist. The list contains specific
checks for the sensor system. General rules and procedures for a photo flight might be different
for various flight crews. Feel free to adapt the checklist according to your individual rules and
requirements.
Version 3.22-15 - Feb / 25 / 2010 41

Start flight execution

Select [Flight] from FCMS main menu to start flight execution.
Ground start
Typically [Flight] is selected while the aircraft is on ground ready for take-off. With this proce-
dure the system is checked on ground. Troubleshooting in case of any malfunction is much sim-
pler than airborne.
Air-Start
Important: In the case where [Flight] is selected when the aircraft is already airborne an in-
flight alignment must be performed to initialize and stabilize the ‘Real-Time-Solution’ of the
GNSS/IMU system. See section "In-flight alignment for GNSS-IMU system" in Volume 2,
Chapter 2 on Page 93. The procedure during an ‘Air-Start’ is given below.
How to perform an ’Air-Start’

1. Select [Flight]
2. Fly straight and level flight, with constant speed until the GNSS and the IMU symbol has
disappeared on the Take-Off control. See Figure 15, “Example of Take-Off control” in Vol-
ume 1, Chapter 4 on Page 43
3. Continue to fly straight and level flight, with constant speed for 2 to 3 more minutes
4. Fly an S-turn. (No need for whole circles or other figures as given in Figure 24, “Examples
of in-flight alignment patterns” in Volume 2, Chapter 2 on Page 94)
Sensor Status view during start-up

During start-up of flight execution all necessary subsystems will be automatically initialized.
During this initialization phase the system remains in the Sensor Status view (Figure 14) until the
initialization is completed and all subsystems have passed the checks. The Sensor Status view
can be skipped. This allows to select the project and the flight plans during the initialization pro-
cess.
Figure 14: Example of ‘Sensor system status’ view during initialization
This view gives an overview of the sensor systems.

Memory and GNSS control are displayed on the upper left
and center. In the area below these controls the status of
the GNSS system is displayed
During initialization the Take-Off control (Figure 15) is displayed on all views at the place of the
Sensor control. The Take-Off control shows the status of the system check. As long as a sub-
system has not passed the system check, the corresponding icon is displayed. If the initialization
42 Version 3.22-15 - Feb / 25 / 2010

phase is successfully completed the Take-Off control indicates o.k. by a check mark symbol and
the systems switches to the default view.
Figure 15: Example of Take-Off control
As long as the system is not ready for the flight an hour glass
symbol is displayed on the upper right side of the control.
The hour glass is replaced by a check mark symbol if all
components of the system are ready. After remaining in this state
a few seconds the Take-Off control is replaced by the Sensor
Head control.
Select [Arrow Right] to skip the Sensor Status view during initialization.
Sensor status and configuration after successful start-up

If the Take-Off control indicates o.k. with a check mark symbol, FCMS is configured according
to the current configuration. This is either the configuration FCMS had the last time just before
flight execution was quit or the configuration the user has set in the configuration menu if he had
re-configured FCMS since flight execution was quit.
If another configuration is required proceed as given in section "System configuration: Software"
in Volume 2, Chapter 4 on Page 146.
PAV80 status indicated on LED

Table 4. PAV80 LED status
LED color PAV80 status
orange - green blinking Initialization
orange i) Operational mode ‘Stabilization OFF’, if the PAV80 is in
mechanical Zero position.
ii) Mount at the stabilization range limits.
Check message on the operator interface.
green Operational mode ‘Stabilization ON’
long green – short red blinking Operational mode ‘Stabilization ON’, but no data for drift
control are available.
This is the case if the system is not moved. E.g. during ground
check, if the aircraft is not moving.
short green – long red blinking Operational mode ‘Stabilization ON’, but no data from the
GNSS/IMU system are available. Check message on the
operator interface.
red Failures. For details and troubleshooting in the Leica PAV80
User Manual
FCMS views, controls and GUI during flight execution

See section "FCMS - Flight Execution" in Volume 2, Chapter 5 on Page 165.
Version 3.22-15 - Feb / 25 / 2010 43

Operation during flight
Main user tasks during flight execution

Important: How to operate the sensor is not part of this manual. Instructions for sensor system
operation are given in the sensor system manuals.
Flight plan controlled flight

In a flight plan controlled flight the operator has to perform the following main tasks:
• Set configuration.
See section "FCMS - Configuration" in Volume 2, Chapter 4 on Page 127
• Select Project/ Flight plan.
See section "Flight plan controlled flight" in Volume 1, Chapter 4 on Page 48
• If desired select flight line and direction of approach.
See section "Flight plan controlled flight" in Volume 1, Chapter 4 on Page 48.
• Mark part of a line, if the part might not be usable. e.g. clouds obscuring the terrain.
See section "Marking sections of a line during data recording" in Volume 1, Chapter 4 on
Page 55.
• In case of an error react to the error messages and trouble shooting options.
See “Trouble shooting” on Page 58
Manually controlled flight

• Start image data recording - stop image data recording.
See “Manual Start / Stop line sensor data recording” on Page 45
• In case of an error react to the error messages and trouble shooting options.
See “Trouble shooting” on Page 58
44 Version 3.22-15 - Feb / 25 / 2010

Manual Start / Stop line sensor data recording

Note: If a PAV30/80 is part of the sensor system the stabilization mode control is linked to the
Start and Stop of image data recording if the PAV control mode is configured AUTO. See section
"Overview configuration of Global 1 parameters" in Volume 2, Chapter 4 on Page 147.
Start recording
Select [Start Stop] to enter sensor release level.
Note: Entering the sensor release level sets the PAV30/80 stabilization mode to ‘ON-AUTO’ if
the PAV control is configured accordingly. For PAV30 only, the drift stabilization starts with a
delay of 10 seconds.
Select [Start] to start recording.
FCMS automatically returns from release level.
The red blinking dot on the Sensor Control indicates the

recording of image data is taking place.
The contents of the Sensor control depends on the installed
sensor type. See section "Sensor control" in Volume 2, Chapter
5 on Page 168.
or
Select [Return] to return from release level without starting recording.
Note: Return without starting recording sets the PAV30/80 stabilization mode to ‘OFF-
MANUAL’ if the PAV control is configured accordingly.
Stop recording
Select [Stop] to stop recording.
Note: Stop recording sets the PAV30/80 stabilization mode to ‘OFF-MANUAL’ if the PAV
control is configured accordingly.
Version 3.22-15 - Feb / 25 / 2010 45

or
Select [Return] to return from release level without stopping recording
Manual release of frame sensors

Note: If the PAV30/80 is part of the sensor system the stabilization mode control is linked to the
Start and Stop of image data recording if the PAV control mode is configured AUTO. See section
"Overview configuration of Global 1 parameters" in Volume 2, Chapter 4 on Page 147.
Prepare for manual frame release

Note: Entering the sensor release level sets the PAV30/80 stabilization mode to ‘ON-AUTO’ if
the PAV control is configured accordingly. For PAV30 only, the drift stabilization starts with a
delay of 10 seconds.
Select [Start] to prepare for release.
The red blinking dot on the Sensor control indicates that the
system is prepared for manual frame releases.
The content of the Sensor control depends on the installed
sensor type. See section "Sensor control" in Volume 2, Chapter
5 on Page 168.
Manual frame release

For each manual frame release confirm [Frame].
Select [Return] to return from release level.
46 Version 3.22-15 - Feb / 25 / 2010

Quit frame release level

Select [Stop] to quit frame release level.
Note: [Stop] sets the PAV30/80 stabilization mode to ‘OFF-MANUAL’ if the PAV control is
configured accordingly.
or
Select [Return] to return from release level without quitting release level
Annotation - user log file entries

This feature allows to make user text entries to the flight plan data during flight execution. The
entries are time tagged. The data is passed to FPES for flight evaluation.
Details are given in section "Annotation - user log file entries during flight" in Volume 2, Chapter
5 on Page 213.
Log data
During operation the system logs status information. This feature allows for error analysis.
Details are given in section "Browsing of logged status data" in Volume 2, Chapter 5 on Page
215.
The log data might also be required for analysis by a Leica Geosystems Sensor Service Techni-
cian. How to export the log data for this purpose is described in section "Export of status data for
error analysis" in Volume 1, Chapter 4 on Page 58.
Version 3.22-15 - Feb / 25 / 2010 47


Important: Set the sensor configuration as for manual flights. If the sensor configuration is part
of the flight plan make sure in FCMS configuration the configuration source is set to ‘Flight
Plan’.
Project and flight plan selection

To select a project and a flight plan from main flight toolbar proceed as follows:
Select [Select Project] to list the projects/flight plans.
Figure 16: Examples ‘Project & Flight Plan Selection’ dialog’
In this dialog, all projects stored in the flight data base

are listed.
The listing can be expanded to flight plan level and to
flight level, if flight data are available. See Figure 17 on
Page 49.
Use [Scroll Up fast], [Scroll Up], [Scroll Down fast] or [Scroll Down] to select the desired
project.
The project is marked with the highlighted bar.
Use [‘+’] to expand the highlighted project/flight plan by one column. See Figure 17 on Page 49.
Use [‘-’] to collapse the expanded columns associated to the highlighted project / flight plan.
Select [Select] for selection. For selection confirm the check mark icon according to the rules
given below in Table 5.
Select [De-select] for de-selection. De-selection is opposite to the rules given Table 5 on Page 49.
48 Version 3.22-15 - Feb / 25 / 2010

Select [Configuration] to change configuration of global parameters ‘Flight Guidance & Sensor
Release’. See section "Overview configuration of Global 1 parameters" in Volume 2, Chapter 4
on Page 147.
Select [Return] to return form the selection dialog. If a selection was made it is loaded for flight
execution.
Figure 17: Detail examples of project listings
Collapsed project listing. Project ‘Hemisphere’ is Project ‘FPES-FCMS-TEST-2’

expanded by one level. No is expanded by one level.
flight plans are yet flown. Already all flight plans are at
Therefore, no aircraft icon is least partly flown.
shown.
Table 5. Rules for project, flight plan and flight selection

Position of Confirm Selected project Selected flight Selected flights
highlighted bar check mark plan(s) (if existing)
project_A once A all non
project_A twice A all all
fight plan_I once A flight plan_I non
fight plan_I twice A flight plan_I all
flight_x once A flight plan_I flight _x
Version 3.22-15 - Feb / 25 / 2010 49

Figure 18: Examples of project, flight plan and flight selection
How to select one flight plan and one existing flight

1. Move highlighted bar to project ‘FPES-FCMS-TEST-2’
2. Confirm button [+]
3. Move highlighted bar to flight plan ‘Sargans’
4. Confirm button [+]
5. Move highlighted bar to flight ‘Sargans_8’
6. Confirm [Accept]
The check mark in brackets on the left side of the project name
(FPES-FCMS-TEST-2) indicates that not all flight plans of the
project are selected.
The check mark in brackets on the left side of the flight plan
name (Sargans) indicates that not all flights are taken into
account.
The check mark on the left side of the flight ‘Sargans_8’ indi-
cates that this flight is taken into account.
Figure 19: Examples for adding a flight plan to a selection
How to add one flight plan to the selection of Figure 18

1. Move highlighted bar to flight plan ‘Unterrheintal’
2. Confirm [Accept]
The check mark in brackets on the left side of the flight plan
name (Unterrheintal) indicates that no or not all flights are
selected to be taken into account during flight execution.
Use [+] to expand the flight plan to list the flights for selection.
50 Version 3.22-15 - Feb / 25 / 2010

Flight line selection

Definitions:
• The ‘next line’ is always the line to be flown following the next IP.
• The ‘current line’ is the line currently in execution.
A next line becomes the current line if the IP is passed and remains the current line until the end
of the line.
Note: FCMS flight guidance selects the next flight line automatically according to the configu-
ration. See section "Configuration of Guidance Project" in Volume 2, Chapter 4 on Page 149.
But at any time the user can override the automatic selection.
To select a flight line manually proceed as follows:

Select [Flight plan more] from the main toolbar to display more buttons for flight line selection.
Direct selection
Use [Previous line] to select the last not yet flown line.
This previous line is the last not yet flown line of the planned sequence.
Use [Next line] to select the first not yet flown line.
This next line is the first not yet flown line of the planned sequence.
Selection from the line listing

Select [GOTO line] to open the line selection dialog.
Figure 20: Example ‘Flight line selection’ dialog’
This dialog gives an overview. It lists for each line:

- flight plan name
- line number
- line label
- status information (shown with icons)
- the maximum horizontal and vertical deviation of the
flown line to the planned line.
See also section "Alphanumeric in-flight evaluation
control" in Volume 2, Chapter 5 on Page 193.
Version 3.22-15 - Feb / 25 / 2010 51

Use [Scroll Up fast], [Scroll Up], [Scroll Down fast] or [Scroll Down] to select the desired line.
The line is marked with the highlighted bar.
Select [Cancel] to quit dialog without selection.
Confirm [Accept] to execute the selected line.
A message window is displayed if the selected line was already partly flown.
Confirm [Execute part] to execute only the missing parts of the line.
Confirm [Execute whole] to execute the whole selected line.
Selection by line number or line label

Select [GOTO line] to open a dialog to enter either the line number or the line label.
Figure 21: Example ‘Keyboard’ dialog
Use the touch screen keyboard to enter either the number

or the label of the line to be flown next.
Use [Tab Left] [Tab Right] to select the desired input field.
52 Version 3.22-15 - Feb / 25 / 2010

Select [Cancel] to quit the dialog.
Select [Return] to return and to execute the line.
Reverse line execution

The planning direction is not relevant for flight execution. A line can be flown in either direction.
To reverse the line execution proceed as follows:
Select [Reverse line] to reverse the direction of approach to the next line.
Abort line or project execution

Important: Manual stop of data recording as described in section "Manual Start / Stop line
sensor data recording" in Volume 1, Chapter 4 on Page 45 will not stop flight execution nor stop
project execution.
To abort execution of the current line or flight execution of a project proceed as follows:
Select [Flight plan more] from the main toolbar to display more buttons for flight line selection
Alternatively the [More buttons] can be selected as well.
Confirm [Abort]
If flying along a line, line execution is aborted.
If not flying along a line, project execution is stopped.
Version 3.22-15 - Feb / 25 / 2010 53

Shorten and/or extend a line

A line can temporarily be modified for execution. The line can be extended and/or shortened at
the start and/or at the end point.
To select a flight line for temporarily modification proceed as follows:
Select [GOTO line] to open the line selection dialog.
Use [Scroll Up fast], [Scroll Up], [Scroll Down fast] or [Scroll Down] to select the desired line.
The line is marked with the highlighted bar.
Select [Part line] to activate the line modification dialog located on the bottom part of the view.
Figure 22: Example ‘shortened line’ dialog
The example on the left shows a line which was

shortened on both ends.
On the bottom of the window the planned line length is
shown in blue.
The data of the modified line are shown in red.
Use [Tab Left] [Tab Right] to set the focus either to the line start or to the line end.
Select [+] buttons to increment value.

Use button with small [+] to increment in small steps.
Use button with large [+] to increment in large steps.
Select [-] button to decrement value.

Use button with small [-] to decrement in small steps.
Use button with large [-] to decrement in large steps.
54 Version 3.22-15 - Feb / 25 / 2010

Select [Cancel] to quit the dialog.
Confirm [Accept] to execute the modified line.
Marking sections of a line during data recording

This feature allows to mark sections of a line during data recording.
Note: The marking can only be activated along a planned flight line or during manual image
data recording.
At the end of a planned flight line FCMS automatically stops marking.
A marked section is handled by FCMS and by FPES like a section which was recorded with a
system error. Therefore, this feature is used to identify data which might be useless. E.g. the ter-
rain is obscured by clouds during data recording.
• In flight evaluation the marked section is displayed color coded. See Table 29, “Color codes
in the graphical presentation showing the line status” in Volume 2, Chapter 5 on Page 192.
• If a line is selected for re-flight, FCMS offers automatic re-flight of the marked section only.
To start / stop marking during data recording proceed as follows:

either
Confirm [Quality Error] to start marking.
or
Confirm [Quality Cancel] to stop marking.
Select [Return] to return from sensor release level.
Version 3.22-15 - Feb / 25 / 2010 55

User activation of FCMS route-finder algorithm
Restart search for closest line

To reactivate the FCMS line finder algorithm proceed as follows:
Select [Recompute] to search for the closest line.
Recompute suggested approach path

To reactivate the FCMS line approach path computation proceed as follows:
Select [More buttons] from the main toolbar to display more buttons.
Select [Recalc] to compute a new optimum flight path to the next line.
56 Version 3.22-15 - Feb / 25 / 2010

System check
The system performs a self test during the start up phase of flight
execution. Therefore, to check if the system is operating
correctly, just start flight execution. If the check mark symbol
appears on the upper right side in the take-off control as shown
in the example on the left side the system has passed the check
successfully.
Important: Sensor specific checks may be performed by using the sensor software. E.g.
TracGUI for ALS50-II.
Steps of system check for a system installed in the aircraft

1. Move the aircraft to a place where there is no obstruction of the incoming signals to the
GNSS antenna.
2. Follow the recommendations in section "Before starting the system for the first time" in Vol-
ume 1, Chapter 4 on Page 28.
3. Start-up system according to section "Start-up sequence" in Volume 1, Chapter 4 on Page 31
4. Start flight execution according to section "Start flight execution" in Volume 1, Chapter 4 on
Page 42.
5. Wait until system has successfully passed the system check. The take-off control shows the
check mark symbol as shown in the example above for a short period of time. After that the
tool bar shows the main level icons for flight execution.
6. Exit flight and shut down the system according to section "System shutdown" in Volume 1,
Version 3.22-15 - Feb / 25 / 2010 57

Trouble shooting
When FCMS is running
During flight execution

During flight execution an internal monitoring program permanently checks the status of all
tightly integrated sensor sub-systems. (For all other sub-systems specific software must be used
for monitoring. e.g. TracGUI for ALS50-II.) If an error or an inconsistency is detected by the
FCMS monitoring program, an ‘Error message window’ is displayed on the user interfaces. In
the Error message window suggested user actions are displayed to solve the problem. Because
trouble shooting information is given on the user interfaces, no further description is given here.
Failure of the master sensor of a multi-sensor system

If the master sensor of a multi-sensor system is in error state the operation is blocked for all sen-
sors.
In case the error on the master system cannot be solved proceed as follows:
1. Stop flight execution
2. deactivate the master system
3. Select in FCMS configuration and define the slave sensor as master sensor.
4. Restart flight execution and continue
Export of status data for error analysis

During operation status information as well as other relevant information is logged by FCMS
into a data base. This data base is stored on the internal memory. If a malfunction cannot be
solved by following the instructions given by FCMS to the operator, help is probably required
from a Leica Geosystems customer support technician. In this case the support technician will
need at least a clear error description and the log data to be able to make an error analysis.
How to download logged status data from OC52 or OC50 for Operator
1. Attach the USB memory stick to the USB port on the OC52 or OC50 for operator.
Important: Make sure FCMS is in the Main menu during this operation. Some sticks prevent
system startup, if they are attached either before or during system start-up.
3. Select [Download log data].
58 Version 3.22-15 - Feb / 25 / 2010

Chapter 5 Care & Handling
Version 3.22-15 Feb / 25 / 2010 59

Care
Cleaning and drying

If the equipment becomes wet, leave it unpacked. Wipe down, clean, and dry the equipment,
transport cases, foam inserts and accessories. Pack up the equipment only when it is perfectly
dry.
Cables and plugs

Keep plugs clean and dry. Blow away any dirt lodged in the plugs of the connecting cables. If
you unplug connecting cables during the flight mission, you may lose data. Always switch off the
system before removing the cables.
Touch screen of the OC52

Use only a clean, soft, lint-free cloth for cleaning. If necessary, moisten the cloth with water or
pure alcohol.
Important: Do not use other liquids; these may attack the polymer components.
Dust filters
Dust filters are located on the input fans of the OC50/52. To ensure proper cooling replace these
filters if they have become dirty. Check the filters about every 6 month. Spare filters are part of
the Standard tools and accessories. Seesection "Tools and accessories" in Volume 1, Chapter 7 on
Page 75. Instructions how to change the filters are given in.section "Replacement of dust filters
on the OC50/52" in Volume 1, Chapter 5 on Page 61.
Transport
When shipping the equipment, always use the complete original Leica Geosystems packaging
(case and, if supplied, cardboard box).
Important: The shipping cases have shock indicators on the outside. After transport check the
shock indicators. If an indicator appears RED, inform immediately the freight handler. Also
inspect all components and make sure they are not damaged.
When transporting the equipment in connection with its use, always carry it in its original case.
After transport, or after storage for long periods, carry out the system checks described in this
user manual.
60 Version 3.22-15 - Feb / 25 / 2010

Storage
When storing the equipment, take the storage temperature limits into account and keep the
humidity to a minimum. See also section "Environmental" in Volume 1, Chapter 7 on Page 72.
Maintenance
Caution: Opening the system for service purposes is only allowed if an Service and
Maintenance training course given by Leica Geosystems AG has been completed.
Replacement of dust filters on the OC50/52

Warning: Before starting to exchange filters, disconnect all cables.
Separate the OC52/OC50 for Operator from the holder plate.

Replacement of the fan filters
1. Disconnect all cables
2. Turn the OC50/52 so you see the back
3. Loosen the eight screws. See arrows on the picture
on the left.
4. Remove the back cover
5. Remove the dust filters from the two fans.
Version 3.22-15 - Feb / 25 / 2010 61

6. Exchange the filter element. Make sure the filters

fit perfectly into the frames of the fans. See picture
on the left side.
7. Put back the cover onto the housing
8. Carefully insert the eight screws into the screw
holes
9. Securely fasten the eight screws
62 Version 3.22-15 - Feb / 25 / 2010

Chapter 6 Safety Directions
Version 3.22-15 Feb / 25 / 2010 63

Safety Directions
The following directions should enable the person responsible for the product, and the person
who actually uses the equipment, to anticipate and avoid operational hazards.
The person responsible for the product must ensure that all users understand these directions and
adhere to them.
Intended use of the system

The FCMS system is suitable for sensors designed for photography from aircraft or helicopters
for the purpose of:
• surveying (cartography, construction sites, highway construction etc.)
• remote sensing (land use, change detection, etc.)
• monitoring (land-slips, agriculture etc.)
• publicity (panoramic views, specific objects etc.)
During operation for the purposes listed above the FCMS system is designed and used for:
• navigation support and guidance during survey flights
• control of airborne sensor components during survey flights
• collection of data during a survey flight for flight evaluation
Prohibited use of the system
• Installation in an aircraft without an authorized provider of such installations.

• Use of the product without instruction.
• Use outside of the intended limits.
• Disabling safety systems.
• Removal of hazard notices.
• Opening the product using tools, for example screwdriver, unless this is specifically permit-
ted for certain functions.
• Modification or conversion of the product.
• Use after misappropriation.
• Use of products with obviously recognizable damages or defects.
• Use with accessories from other manufacturers without the prior explicit approval of Leica
Geosystems.
• Inadequate safeguards at the working site.
Warning: Adverse use can lead to injury, malfunction and damage. It is the task of the
person responsible for the equipment to inform the user about hazards and how to
counteract them. The product is not to be operated until the user has been instructed on
how to work with it.
64 Version 3.22-15 - Feb / 25 / 2010

Usage limitations
Please refer also to section "Technical Data" in Volume 1, Chapter 7 on Page 71
Limits of Use
Environment
Suitable for use in an atmosphere appropriate for permanent human habitation: not suitable for
use in aggressive or explosive environments.
Responsibilities
Manufacturer of the product

Leica Geosystems AG, CH-9435 Heerbrugg, hereinafter referred to as Leica Geosystems, is
responsible for supplying the product, including the user manual and original accessories, in a
completely safe condition.
Manufacturers of non Leica Geosystems accessories

The manufacturers of non Leica Geosystems accessories for the product are responsible for
developing, implementing and communicating safety concepts for their products, and are also
responsible for the effectiveness of those safety concepts in combination with the Leica Geosys-
tems product.
Person in charge of the product

The person in charge of the product has the following duties:
• To understand the safety instructions on the product and the instructions in the user manual.
• To be familiar with local regulations relating to safety and accident prevention.
• To inform Leica Geosystems immediately if the product and the application becomes
unsafe.
Warning: The person responsible for the product must ensure that it is used in accordance
with the instructions. This person is also accountable for the training and the deployment of
personnel who use the product and for the safety of the equipment in use.
Version 3.22-15 - Feb / 25 / 2010 65

Hazards of use
Warning: The absence of instruction, or the inadequate imparting of instruction, can lead
to incorrect or adverse use, and can give rise to accidents with far-reaching human,
material, financial and environmental consequences.
Precautions: All users must follow the safety directions given by the manufacturer and the direc-
tions of the person responsible for the product. The latter person is to make use of the sensor
course arranged annually by Leica Geosystems.
Caution: Watch out for erroneous flight results if the system is defective, if it has been dropped,
misused or modified. All of the connecting cables are particularly at risk.
Precaution: Before each flight, carry out the system check. It is the duty of the person responsi-
ble for the system to ensure that the regular servicing prescribed in the User Manual is carried
out. These measures are particularly important after the equipment as a whole has been subjected
to abnormal use, and before and after important measurements.
Caution: If the accessories used with the product are not properly secured and the product is
subjected to mechanical shock, for example blows or falling, the product may be damaged or
people may sustain injury.
Precautions: When setting-up the product, make sure that the accessories are correctly adapted,
fitted, secured, and locked in position. Avoid subjecting the product to mechanical stress.
Caution: In the case of a crash landing or extreme turbulence the crew and passengers may be
hurt by loose equipment parts.
Precautions: Store unused system components during flight in a safe place. Make sure that the
installation of the product is done by a certified aircraft modification company. The installation
must comply with the requirements stated in the installation drawings.
Caution: Do not open the system when it is connected to the power source. This may damage
your system and there is also a hazard of electrical shock.
Precautions: Only open the product if you have completed a service course at Leica Geosystems.
Always disconnect the product from the power source before opening the system.
Caution: Loose equipment parts (especially cables) can destroy the equipment and can harm the
flight crew and passengers.
Precautions: When installing the product make sure that no loose equipment parts (especially
cables) are within the aircraft. Follow the installation instructions on the installation drawings.
66 Version 3.22-15 - Feb / 25 / 2010

Warning: If the product is improperly disposed of, the following can happen:
• If polymer parts are burnt, poisonous gases are produced which may impair health.
• If batteries are damaged or are heated strongly, they can explode and cause poisoning, burn-
ing, corrosion or environmental contamination.
• By disposing of the product irresponsibly you may enable unauthorized persons to use it in
contravention of the regulations, exposing them-selves and third parties to the risk of severe
injury and rendering the environment liable to contamination.
Precautions: The product must not be disposed with household waste.

Dispose of the product appropriately in accordance with the national regulations in force in your
country.
Always prevent access to the product by unauthorized personnel.
Product specific treatment and waste management information can be downloaded from the
Leica Geosystems home page at http://www.leica-geosystems.com/treatment or received from
your Leica Geosystems dealer.
Caution: Never fly according only to the positional information provided by the product. GNSS
is not permitted as a sole source of information for navigation. Flying with products position and
altitude information only can lead to crash landings.
Precautions: Always fly with a supplementary navigation system and under VFR conditions.
Caution: During the operation of the product there is a hazard of squeezing extremities or
entanglement of hairs and/or clothes by moving/rotating parts.
Precautions: Keep a safe distance of the moving/rotating parts.
Warning: Only Leica Geosystems authorized service workshops are entitled to repair these
products.
Warning: Inadequate securing of the working site can lead to dangerous situations, for
example in traffic, on building sites, and at industrial installations.
Precautions: Always ensure that the working site is adequately secured. Adhere to the regula-
tions governing safety and accident prevention and road traffic.
Warning: If computers intended for use indoors are used in the field there is a danger of
electric shock.
Precautions: Adhere to the instructions given by the computer manufacturer with regard to field
use in conjunction with Leica Geosystems products.
Version 3.22-15 - Feb / 25 / 2010 67

Electromagnetic Compatibility EMC
Description
The term Electromagnetic Compatibility is taken to mean the capability of the product to func-
tion smoothly in an environment where electromagnetic radiation and electrostatic discharges are
present, and without causing electromagnetic disturbances to other equipment.
Warning: Electromagnetic radiation can cause disturbances in other equipment.
Although the product meets the strict regulations and standards which are in force in this
respect, Leica Geosystems cannot completely exclude the possibility that other equipment
may be disturbed.
Caution: There is a risk that disturbances may be caused in other equipment if the product is
used in conjunction with accessories from other manufacturers, for example field computers,
personal computers, two-way radios, non-standard cables or external batteries.
Precautions: Use only the equipment and accessories recommended by Leica Geosystems.
When combined with the product, they meet the strict requirements stipulated by the guidelines
and standards. When using computers and two-way radios, pay attention to the information about
electromagnetic compatibility provided by the manufacturer.
Caution: Disturbances caused by electromagnetic radiation can result in erroneous

measurements. Although the product meets the strict regulations and standards which are in force
in this respect, Leica Geosystems cannot completely exclude the possibility that the product may
be disturbed by very intense electromagnetic radiation, for example, near radio transmitters, two-
way radios or diesel generators.
Precautions: Check the plausibility of results obtained under these conditions.
Warning: If the product is operated with connecting cables attached at only one of their
two ends, for example external supply cables, interface cables, the permitted level of
electromagnetic radiation may be exceeded and the correct functioning of other products
may be impair.
Precautions: While the product is in use, connecting cables, for example product to external bat-
tery, product to computer, must be connected at both ends.
68 Version 3.22-15 - Feb / 25 / 2010

FCC Statement, Applicable in U.S.

Warning: This equipment has been tested and found to comply with the limits for a Class B
digital device, pursuant to part 15 of the FCC rules.
These limits are designed to provide reasonable protection against harmful interference in a resi-
dential installation.
This equipment generates, uses and can radiate frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communication.
However, there is no guarantee that interference will not occur in a particular installation.
If this equipment does cause harmful interference to radio or television reception, which can be
deter-mined by turning the equipment off and on, the user is encouraged to try to correct the inter-
ference by one or more of the following measures:
• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and the receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
• Consult the dealer or an experienced radio/TV technician for help.
Warning: Changes or modifications not expressly approved by Leica Geosystems for

compliance could void the user's authority to operate the equipment.
Version 3.22-15 - Feb / 25 / 2010 69

Labeling
Type shields on OC52 with or without keyboard
Type shields on OC50 for operator (with keyboard) for Pilot (without keyboard)
70 Version 3.22-15 - Feb / 25 / 2010

Chapter 7 Technical Data
Version 3.22-15 Feb / 25 / 2010 71

About Technical Data

The Chapter Technical Data contains relevant information about the FCMS hardware:
• Electrical data
• Environmental conditions
• Weight and part numbers of components
Note: Dimensions for all parts is given in section "Aircraft Installation Data" in Volume 3,
Electrical
Voltage input 22.0 - 30.3 V DC
Maximum voltage ripple 1.4 Vpp (1 to 15 kHz)
Reverse polarity protection Internal on all devices with power input.
Over voltage protection Internal on all devices (continuous short circuit after over voltage).
Table 6. Power consumption at 28 V DC
Device Average Peak Connected to device

OC52 30 W 40 W,<0.3s Control unit of sensor system
OC50 for operator 30 W 40 W,<0.3s Control unit of sensor system
OC50 for pilot 30 W 40 W,<0.3s OC50 for operator
GI40 10 W 40 W,<0.3s OC50 for pilot or operator
Environmental
Operating temperature -20°C to +55°C *)
Storage temperature -40°C to +85°C *)
Pressure non pressurized aircraft ICAO 25,000 ft, 7’620 m
Pressurized aircraft ICAO 50,000 ft, 15’240 m
Humidity 0% rH to 95% rH according to ISO 7137
EMC according to ISO 7137
Vibrations according to ISO 7137
Shock operational according to ISO 7137
Crash safety according to ISO 7137
Emergency landing according to FAA Part 25
Environmental qualification forms see section "Environmental qualification form OC50 and
GI40" in Volume 3, Chapter 2 on Page 225 and section "Environmental qualification form
OC52" in Volume 3, Chapter 2 on Page 226.
Tip: *) Startup is faster if OC50 and OC52 are not below 0°C or above 55°C. Store in cold or
hot seasons this light weight components in the office and not in the aircraft on the tarmac.
72 Version 3.22-15 - Feb / 25 / 2010

Applied standards
General standards for temperature,
ISO 7137, RTCA DO-160F, EUROCAE-14E
electronics environment etc.
Emergency landing FAR § 23.561 and 27.561
Conformity to national regulations

• FCC Part 15 (applicable in US)
• Hereby, Leica Geosystems AG, declares that the IPAS20 system with GNSS antenna is in
compliance with the essential requirements and other relevant provisions of Directive 1999/
5/EC. The declaration of conformity may be consulted at http://www.leica-geosystems.com/
ce.
• Class 1 equipment according European Directive 1999/5/EC (R&TTE) can be placed on the
market and be put into service without restrictions in any EEA member state.
The conformity for countries with other national regulations not covered by the FCC part 15 or
European directive 1999/5/EC has to be approved prior to use and operation.
Version 3.22-15 - Feb / 25 / 2010 73

Hardware components for FMCS
Devices and parts

Table 7. FCMS system devices and parts
Part # Device / Part Net weight

767841 OC52 Operation Controller with Keyboard 3.55 kg
767840 OC52 Operation Controller 2.6 kg
757026 OC50 for Operator 2.5 kg
743070 IS40 Interface Stand, consisting of mount and tube 5.45 kg
745210 OC50 for Pilot 1.50 kg
756135 OC50 Hand Bag 0.1 kg
861330 GI40 Guidance Indicator 0.4 kg
862620 Accessories case 1.3 kg
763733 CD, DVD drive 0.55 kg
763734 USB Hub, 4 port 0.05kg
743064 USB Memory Stick 0.03 kg
757727 GNSS antenna splitter 0.03 kg
Note: Dimensions for all parts is given in section "Aircraft Installation Data" in Volume 3,
Cables
Table 8. Cables
Part # Connection Length

745938 Cable OC50 to CU40,SC50 or 2nd OC50 7.0 m
764030 Cable OC50 to CU40, SC50 or 2nd OC50 0.8 m
822132 GI40 to OC50 or CU40 5.0 m
757734 Cable ADS40 to ALS50 7.0 m
821218 GNSS antenna cable 10 m
757759 GNSS antenna cable 2.5 m
74 Version 3.22-15 - Feb / 25 / 2010

Tools and accessories

Table 9. Tools and accessories for OC50
Part # Qty Part

3 Dazzle shield
752446
6 Dust filter for OC50 input fans
Documentation, Software
Table 10. Documentation, Software
Part # Name Form

757041 FCMS Documentation Digital on CD
749560 FCMS Flight & Sensor Control Management System Digital on CD
757046 FCMS User Manual Hardcopy
753771 FCMS Flight Simulator Digital on CD
Version 3.22-15 - Feb / 25 / 2010 75

76 Version 3.22-15 - Feb / 25 / 2010

Chapter 8 Warranty - Software License Agreement
Version 3.22-15 Feb / 25 / 2010 77

International Limited Warranty, Software License Agreement
International Limited Warranty

This product is subject to the terms and conditions set out in the International Limited Warranty
which you can download from the Leica Geosystems home page at http://www.leica-geosys-
tems.com/internationalwarranty or collect from your Leica Geosystems distributor. The forego-
ing warranty is exclusive and is in lieu of all other warranties, terms or conditions, express or
implied, either in fact or by operation of law, statutory or otherwise, including warranties, terms
or conditions of merchantability, fitness for a particular purpose, satisfactory quality and non-
infringement, all of which are expressly disclaimed.
Software License Agreement

This product contains software that is pre-installed on the product, or that is supplied to you on a
data carrier media, or that can be downloaded by you online pursuant to prior authorization from
Leica Geosystems. Such software is protected by copyright and other laws and its use is defined
and regulated by the Leica Geosystems Software License Agreement, which covers aspects such
as, but not limited to, Scope of the License, Warranty, Intellectual Property Rights, Limitation of
Liability, Exclusion of other Assurances, Governing Law and Place of Jurisdiction. Please make
sure, that at any time you fully comply with the terms and conditions of the Leica Geosystems
Software License Agreement.
Such agreement is provided together with all products and can also be referred to and down-
loaded at the Leica Geosystems home page at http://www.leica-geosystems.com/swlicense or
collected from your Leica Geosystems distributor.
You must not install or use the software unless you have read and accepted the terms and condi-
tions of the Leica Geosystems Software License Agreement. Installation or use of the software or
any part thereof, is deemed to be an acceptance of all the terms and conditions of such license
agreement. If you do not agree to all or some of the terms of such license agreement, you may not
download, install or use the software and you must return the unused software together with its
accompanying documentation and the purchase receipt to the dealer from whom you purchased
the product within ten (10) days of purchase to obtain a full refund of the purchase price.
78 Version 3.22-15 - Feb / 25 / 2010

Microsoft End User License Agreement ("EULA")
End user license agreement for MICROSOFT embedded systems

• You have acquired a device ("DEVICE") that includes software licensed by Leica Geosys-
tems from Microsoft Licensing, GP or its affiliates ("MS"). Those installed software prod-
ucts of MS origin, as well as associated media, printed materials, and "online" or electronic
documentation ("SOFTWARE") are protected by international intellectual property laws
and treaties. The SOFTWARE is licensed, not sold. All rights reserved
• IF YOU DO NOT AGREE TO THIS END USER LICENSE AGREEMENT ("EULA"),
DO NOT USE THE DEVICE OR COPY THE SOFTWARE. INSTEAD, PROMPTLY
CONTACT LEICA GEOSYSTEMS FOR INSTRUCTIONS ON RETURN OF THE
UNUSED DEVICE(S) FOR A REFUND. ANY USE OF THE SOFTWARE, INCLUD-
ING BUT NOT LIMITED TO USE ON THE DEVICE, WILL CONSTI-TUTE YOUR
AGREEMENT TO THIS EULA (OR RATIFICATION OF ANY PREVIOUS CON-
SENT).
• GRANT OF SOFTWARE LICENSE. This EULA grants you the following license:
You may use the SOFTWARE only on the DEVICE.
NOT FAULT TOLERANT. THE SOFTWARE IS NOT FAULT TOLERANT. LEICA
GEOSYSTEMS HAS INDEPENDENTLY DETERMINED HOW TO USE THE SOFT-
WARE IN THE DEVICE, AND MS HAS RELIED UPON LEICA GEOSYSTEMS TO
CONDUCT SUFFICIENT TESTING TO DETER-MINE THAT THE SOFTWARE IS
SUITABLE FOR SUCH USE.
NO WARRANTIES FOR THE SOFTWARE. THE SOFTWARE is provided "AS IS"
and with all faults. THE ENTIRE RISK AS TO SATISFACTORY QUALITY, PERFOR-
MANCE, ACCURACY, AND EFFORT (INCLUDING LACK OF NEGLICENCE) IS
WITH YOU. ALSO, THERE IS NO WARRANTY AGAINST INTERFERENCE WITH
YOUR ENJOYMENT OF THE SOFTWARE OR AGAINST INFRINGEMENT. IF YOU
HAVE RECEIVED ANY WARRANTIES REGARDING THE DEVICE OR THE
SOFTWARE, THOUSE WARRANTIES DO NOT ORIGINATE FROM, AND ARE
NOT BINDING ON, MS.
No Liability for Certain Damages. EXCEPT AS PROHIBITED BY LAW, MS SHALL
HAVE NO LIABILITY FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL OR
INCIDENTAL DAMAGES ARISING FROM OR IN CONNECTION WITH THE
USE OR PERFORMANCEOF THE SOFTWARE. THIS LIMITATION SHALL
APPLY EVEN IF ANY REMEDY FAILS OF ITS ESSENTIAL PURPOSE, IN NO
EVENT SHALL MS BE LIABILE FOR ANY AMOUNT IN EXCESS OF U.S. TWO
HUNDRED FIFTY DOLLARS (U.S.$250.00).
Limitations on Reverse Engineering, Decompilation, and Disassembly. You may not
reverse engineer, decompile, or disassemble the SOFTWARE, except and only to the extent
that such activity is expressly permitted by applicable law notwithstanding this limitation.
SOFTWARE TRANSFER ALLOWED BUT WITH RESTRICTIONS. You may per-
manently transfer rights under this EULA only as part of a permanent sale or transfer of the
Device, and only if the recipient agrees to this EULA. If the SOFTWARE is an upgrade, any
transfer must also include all prior versions of the SOFTWARE.
EXPORT RESTRICTIONS. You acknowledge that SOFTWARE is subject to U.S. export
jurisdiction. You agree to comply with all applicable international and national laws that
apply to the SOFTWARE, including the U.S. Export Administration Regulations, as well as
Version 3.22-15 - Feb / 25 / 2010 79

end-user, end-use and destination restrictions issued by U.S. and other governments. For
additional information see http://www.microsoft.com/exporting/.
Product specific terms

• RESTRICTED FUNCTIONALITY. You are licensed to use the SOFTWARE to provide
only the limited functionality (specific tasks or processes) for which the DEVICE has been
designed and marketed by Leica Geosystems. This license specifically prohibits any other
use of the SOFTWARE programs or functions, or inclusion of additional software programs
or functions that do not directly support the limited functionality on the DEVICE.
a) Notwithstanding the foregoing, you may install or enable on the DEVICE systems utili-
ties, resource management or similar software (including without limitation anti-virus
software) (collectively, "Support Software") solely for the purpose of administration,
performance enhancement and/or preventive maintenance of the DEVICE. You acknowl-
edge and agree that with respect to any Support Software: (i) the Support Software may
not be compatible with the SOFTWARE installed on your DEVICE; (ii) no warranty is
provided by MS, Micro-soft Corporation or their affiliates for any Support Software that
you may install on your DEVICE; and (iii) neither MS, Microsoft Corporation nor their
affiliates is responsible for technical support of any Support Software you may install on
your DEVICE. Please contact Leica Geosystems if you have any questions regarding any
Support Software that you are considering installing on your DEVICE.
b)The DEVICE may use terminal services protocols (such as Remote Desktop Protocol,
Remote Assistance or Independent Computer Architecture) to connect or access Applica-
tions (as defined below) running on a server; however, these Applications may not run
locally on the DEVICE. For purposes of this provision, "Applications" mean software
that provides any of the following functionality: consumer or business tasks or processes
performed by a computer or computing device, including email, word processing, spread-
sheets, database, scheduling, or personal finance.
• DEVICE CONNECTIONS. The SOFTWARE may not be used by more than two (2) pro-
cessors at any one time on the DEVICE. You may permit a maximum of ten (10) computers
or other electronic devices to connect via Server Message Block (SMB) to the DEVICE to
utilize one or more of the following services of the SOFTWARE: (a) file services, print ser-
vices, (b) Internet information services and/or (c) remote access (including connection shar-
ing). The ten connection maximum includes any indirect connections made through
"multiplexing" or other software or hardware which pools or aggregates connections. This
ten connection maximum does not apply to other uses of the SOFTWARE. Unlimited simul-
taneous inbound connections are permitted via TCP/IP.
• CLIENT ACCESS LICENSES. If you use the DEVICE to access or utilize the services or
functionality of Microsoft Windows Server products (such as Microsoft Windows Server
2003), or use the DEVICE to permit workstation or computing devices to access or utilize
the services or functionality of Microsoft Windows Server products, you may be required to
obtain a Client Access License for the DEVICE and/or each such workstation or computing
device. Please refer to the end user license agreement for your Microsoft Windows Server
product for additional information.
• REMOTE DESKTOP FEATURES/NETMEETING/REMOTE ASSISTANCE. The
SOFTWARE may contain NetMeeting, Remote Assistance, and Remote Desktop technolo-
gies that enable the SOFTWARE or other applications installed on the DEVICE to be used
remotely between two or more computing devices, even if the SOFTWARE or application
is installed on only one DEVICE. You may use NetMeeting, Remote Assistance, and
Remote Desktop with all Microsoft products; provided however, use of these technologies
80 Version 3.22-15 - Feb / 25 / 2010

with certain Microsoft products may require an additional license. For both Microsoft prod-
ucts and non-Microsoft products, you should consult the license agreement accompanying
the applicable product or contact the applicable licensor to determine whether use of Net-
Meeting, Remote Assistance, or Remote Desktop is permitted without an additional license.
• REMOTE BOOT FEATURE. Your DEVICE may be enabled with a Remote Boot feature
which includes the Remote Boot Installation Service tool. You may (i) use the Remote Boot
Installation Service tool to install one (1) copy of the SOFTWARE onto your server solely
for the purpose of deploying the SOFTWARE to one or more DEVICEs on which you are
licensed to run the SOFTWARE (i.e. DEVICEs to which the appropriate Certificate of
Authenticity is affixed) ); (ii) download the SOFTWARE over your internal network only
onto such licensed DEVICEs; and (iii) use the Remote Boot Installation Service only for
deployment of the SOFTWARE to licensed DEVICEs as part of the Remote Boot process.
Please refer to the DEVICE documentation, if provided with your DEVICE, or contact
Leica Geosystems for additional information.
• AUTOMATIC INTERNET-BASED SERVICES. The SOFTWARE features described
below are enabled by default to connect via the Internet to Microsoft computer systems
automatically, without separate notice to you. You consent to the operation of these features,
unless you choose to switch them off or not use them. Microsoft does not use these features
to collect any information that will be used to identify you or contact you. For more infor-
mation about these features, please see the privacy statement at http://go.microsoft.com/
fwlink/?LinkId=25243
Web Content Features. Under the SOFTWARE's default configuration, if you are con-
nected to the Internet, several features of the SOFTWARE are enabled by default to retrieve
content from Microsoft computer systems and display it to you. When you activate such a
feature, it uses standard Internet protocols, which transmit the type of operating system,
browser and language code of your DEVICE to the Microsoft computer system so that the
content can be viewed properly from your DEVICE. These features only operate when you
activate them, and you may choose to switch them off or not use them. Examples of these
features include Windows Catalog, Search Assistant, and the Headlines and Search features
of Help and Support Center.
Digital Certificates. The SOFTWARE uses digital certificates based on the x.509 standard.
These digital certificates confirm the identity of Internet users sending x.509 standard
encrypted information. The SOFTWARE retrieves certificates and updates certificate revo-
cation lists. These security features operate only when you use the Internet.
Auto Root Update. The Auto Root Update feature updates the list of trusted certificate
authorities. You can switch off the Auto Root Update feature.
Windows Media Player. Some features of Windows Media Player automatically contact
Microsoft computer systems if you use Windows Media Player or specific features of it: fea-
tures that (A) check for new codecs if your DEVICE does not have the correct ones for con-
tent you attempt to play (this feature may be switched off), and (B) check for new versions
of Windows Media Player (this feature will operate only when you are using Windows
Media Player).
Windows Media Digital Rights Management. Content providers are using the digital
rights management technology for Windows Media contained in this SOFTWARE ("WM-
DRM") to protect the integrity of their content ("Secure Content") so that their intellectual
property, including copyright, in such content is not misappropriated. Portions of this
SOFTWARE and third party applications such as media players use WM-DRM to play
Secure Content ("WM-DRM Software"). If the WM-DRM Software's security has been
compromised, owners of Secure Content ("Secure Content Owners") may request that
Microsoft revoke the WM-DRM Software's right to copy, display and/or play Secure Con-
Version 3.22-15 - Feb / 25 / 2010 81

tent. Revocation does not alter the WM-DRM Software's ability to play unprotected content.
A list of revoked WM-DRM Software is sent to your DEVICE when-ever you download a
license for Secure Content from the Internet. Microsoft may, in conjunction with such
license, also download revocation lists onto your DEVICE on behalf of Secure Content
Owners. Secure Content Owners may also require you to upgrade some of the WM-DRM
components in this SOFTWARE ("WMDRM Upgrades") before accessing their content.
When you attempt to play such content, WM-DRM Software built by Microsoft will notify
you that a WM-DRM Upgrade is required and then ask for your consent before the WM-
DRM Upgrade is downloaded. WMDRM Soft-ware built by third parties may do the same.
If you decline the upgrade, you will not be able to access content that requires the WM-
DRM Upgrade; however, you will still be able to access unprotected content and Secure
Content that does not require the upgrade. WM-DRM features that access the Internet, such
as acquiring new licenses and/or performing a required WM-DRM Upgrade, can be
switched off. When these features are switched off, you will still be able to play Secure Con-
tent if you have a valid license for such content already stored on your DEVICE.
• WINDOWS UPDATE AGENT (ALSO KNOWN AS SOFTWARE UPDATE SER-
VICES). If the SOFTWARE includes Windows Update Agent ("WUA") (also known as
Software Update Services) functionality that may enable your DEVICE to connect to and
access updates ("Windows Updates") from a server installed with the required server com-
ponent then the following conditions apply:
Without limiting any other disclaimer in this EULA, or any EULA accompanying a Win-
dows Update, you acknowledge and agree that no warranty is provided by MS, Microsoft
Corporation or their affiliates with respect to any Windows Update that you install or
attempt to install on your DEVICE;
In addition, you acknowledge and accept that (i) Windows Updates may not be necessary or
suitable for installation on or use with your DEVICE or the SOFTWARE, and (ii) if
installed or attempted to be installed on your DEVICE, Windows Updates may not function
on the DEVICE or may malfunction and/or cause harm to the DEVICE, to operators of the
DEVICE or to other persons or property. If you connect to a server that installs a Windows
Update, you agree that you assume all risk and liability with regard to any Windows Update
that you install or attempt to install on your DEVICE using functionality provided by SOFT-
WARE. You further agree that neither MS, Microsoft Corporation nor their affiliates have
any liability to you with respect to any Windows Update that you install or attempt to install
on your DEVICE; and
Leica Geosystems is solely responsible for providing technical support, if any, to you in
connection with your installation of Windows Updates installed on your DEVICE using
WUA functionality provided by the SOFTWARE. Please contact Leica Geosystems if you
have any questions regarding any Windows Update that you are considering installing on
your DEVICE or otherwise regarding the WUA functionality.
NOTICES REGARDING THE MPEG-4 VISUAL STANDARD. The SOFTWARE may
include MPEG-4 visual decoding technology. This technology is a format for data compres-
sion of video information. For this technology, MPEG LA, L.L.C. requires this notice:
"USE OF THIS PRODUCT IN ANY MANNER THAT COMPLIES WITH THE
MPEG-4 VISUAL STANDARD IS PROHIBITED, EXCEPT FOR USE
DIRECTLY RELATED TO (A) DATA OR INFORMATION (i) GENERATED
BY AND OBTAINED WITHOUT CHARGE FROM A CONSUMER NOT
THEREBY ENGAGED IN A BUSINESS ENTERPRISE, AND (ii) FOR PER-
SONAL USE ONLY; AND (B) OTHER USES SPECIFICALLY AND SEPA-
RATELY LICENSED BY MPEG LA, L.L.C.
82 Version 3.22-15 - Feb / 25 / 2010

If you have questions regarding this notice, please contact MPEG LA, L.L.C., 250
Steele Street, Suite 300, Denver, Colorado 80206; Telephone 303 331.1880; FAX
303 331.1879; www.mpegla.com."
General terms
• PRODUCT SUPPORT. Product support for the SOFTWARE is not provided by MS,
Micro-soft Corporation or their affiliates. For product support, please refer to Leica Geosys-
tems support number provided in the documentation for the DEVICE. Should you have any
questions concerning this EULA, or if you desire to contact Leica Geosystems for any other
reason, please refer to the address provided in the documentation for the DEVICE.
• END USER PROOF OF LICENSE. If you acquired the SOFTWARE installed on the
DEVICE, or on a compact disc or other media, a genuine Microsoft "Proof of License"/Cer-
tificate of Authenticity label with a genuine copy of the SOFTWARE identifies a licensed
copy of the SOFTWARE. To be valid, the label must be affixed to the DEVICE, or appear
on Leica Geosystem's software packaging. If you receive the label separately other than
from the Leica Geosystems it is invalid. You should keep the label on the DEVICE or pack-
aging to prove that you are licensed to use the SOFTWARE. This End User License Agree-
ment ("EULA") is valid and grants the end-user rights ONLY if the SOFTWARE is genuine
and a genuine Certificate of Authenticity for the SOFTWARE is included. For more infor-
mation on identifying whether your SOFTWARE is genuine, please see http://www.micro-
soft.com/piracy/howtotell.
• BACKUP COPY. You may make one (1) backup copy of the SOFTWARE. You may use
this backup copy solely for your archival purposes and to reinstall the SOFTWARE on the
DEVICE. Except as expressly provided in this EULA or by local law, you may not other-
wise make copies of the SOFTWARE, including the printed materials accompanying the
SOFT-WARE. You may not loan, rent, lend or otherwise transfer the backup copy to
another user.
• RESTRICTED USE. The SOFTWARE is not designed or intended for use or resale in haz-
ardous environments requiring fail-safe performance, such as in the operation of nuclear
facilities, aircraft navigation or communication systems, air traffic control, or other devices
or systems in which a malfunction of the SOFTWARE would result in fore-seeable risk of
injury or death to the operator of the device or system, or to others.
• NO RENTAL/COMMERCIAL HOSTING. You may not rent, lease, lend or provide com-
mercial hosting services with the SOFTWARE to others.
• SEPARATION OF COMPONENTS. The SOFTWARE is licensed as a single product. Its
component parts may not be separated for use on more than one device computer.
• CONSENT TO USE OF DATA. You agree that MS, Microsoft Corporation and their affil-
iates may collect and use technical information gathered in any manner as part of product
support services related to the SOFTWARE. MS, Microsoft Corporation and their affiliates
may use this information solely to improve their products or to provide customized services
or technologies to you. MS, Microsoft Corporation and their affiliates may disclose this
information to others, but not in a form that personally identifies you.
• INTERNET GAMING/UPDATE FEATURES. If the SOFTWARE provides, and you
choose to utilize, the Internet gaming or update features within the SOFTWARE, it is neces-
sary to use certain computer system, hardware, and software information to implement the
features. By using these features, you explicitly authorize MS, Microsoft Corporation, their
affiliates and/or their designated agent to use this information solely to improve their prod-
ucts or to provide customized services or technologies to you. MS, Microsoft Corporation or
Version 3.22-15 - Feb / 25 / 2010 83

their affiliates may disclose this information to others, but not in a form that personally iden-
tifies you.
• TRADEMARKS. This EULA does not grant you any rights in connection with any trade-
marks or service marks of Leica Geosystems, MS Microsoft Corporation or their affiliates
and suppliers.
• LINKS TO THIRD PARTY SITES. You may link to third party sites through the use of
the SOFTWARE. The third party sites are not under the control of MS, Microsoft Corpora-
tion or their affiliates. Neither MS, Microsoft Corporation nor their affiliates is responsible
for contents of any third party sites, any links contained in third party sites, or any changes
or updates to third party sites, or any changes or updates to third party sites. Neither MS,
Microsoft Corporation nor their affiliates is responsible for webcasting or any other form of
transmission received from any third party sites. MS, Microsoft Corporation or their affili-
ates are providing these links to third party sites to you only as a convenience, and the inclu-
sion of any link does not imply an endorsement by MS, Microsoft Corporation or their
affiliates of the third party site.
• ADDITIONAL SOFTWARE/SERVICES. This EULA applies to updates, supplements,
add on components, product support services, or Internet-based services components ("Sup-
ple-mental Components"), of the SOFTWARE that you may obtain from Leica Geosystems,
MS, Microsoft Corporation or their affiliates after the date you obtain your initial copy of
the SOFTWARE, unless you accept updated terms or another agreement governs. If other
terms are not provided along with such Supplemental Components and the Supplemental
Components are provided to you by MS, Microsoft Corporation or their affiliates then you
will be licensed by such entity under the same terms and conditions of this EULA, except
that (i) MS, Microsoft Corporation or their affiliates providing the Supplemental Compo-
nents will be the licensor with respect to such Supplemental Components in lieu of the
"COMPANY" for the purposes of the EULA, and (ii) TO THE MAXIMUM EXTENT
PERMITTED BY APPLICABLE LAW, THE SUPPLEMENTAL COMPONENTS AND
ANY (IF ANY) SUPPORT SERVICES RELATED TO THE SUPPLEMENTAL COMPO-
NENTS ARE PROVIDED AS IS AND WITH ALL FAULTS. ALL OTHER DISCLAIM-
ERS, LIMITATION OF DAMAGES, AND SPECIAL PROVI-SIONS PROVIDED
HEREIN AND/OR OTHERWISE WITH THE SOFTWARE SHALL APPLY TO SUCH
SUPPLEMENTAL COMPONENTS. MS, Microsoft Corporation or their affiliates reserve
the right to discontinue any Internet-based services provided to you or made available to you
through the use of the SOFTWARE.
• RECOVERY MEDIA. If SOFTWARE is provided by Leica Geosystems on separate
media and labeled "Recovery Media" you may use the Recovery Media solely to restore or
rein-stall the SOFTWARE originally installed on the DEVICE.
• TERMINATION. Without prejudice to any other rights, Leica Geosystems or MS may ter-
minate this EULA if you fail to comply with the terms and conditions of this EULA. In such
event, you must destroy all copies of the SOFTWARE and all of its component parts.
• NOTICE REGARDING SECURITY. To help protect against breaches of security and
malicious software, periodically back up your data and system information, use security fea-
tures such as firewalls, and install and use security updates.
84 Version 3.22-15 - Feb / 25 / 2010

Field Manual
Technical Data are important information. Please read carefully

through before you use the system.
Document code
Volume 2 FCMS Field Manual
86 Version 3.22-15 - Feb / 25 / 2010

Chapter 1 About Field Manual
Version 3.22-15 Feb / 25 / 2010 87

Chapter 1 About Field Manual
Scope of document
The Field Manual contains relevant information about:
• Operational aspects of the FCMS system
• Flight recommendations
General
See section section "Product identification" in Volume 1, Chapter 1 on Page 2
Abbreviations
See section "Abbreviations" in Volume 1, Chapter 1 on Page 3
Meaning of symbols
See section "Meaning of symbols" in Volume 1, Chapter 1 on Page 5

Documents Other volumes of FCMS Documentation or in the documentation
delivered to the sensor system

See section "Where to get assistance and training" in Volume 1, Chapter 1 on Page 6
88 Version 3.22-15 - Feb / 25 / 2010

Chapter 2 General for photo flights
Version 3.22-15 Feb / 25 / 2010 89

Important notes for the photo flight
General
Warning: GNSS is not officially approved for flight navigation! FCMS is only a tool for
survey flight navigation. It only suggests an approach to the flight line and assists a user
when flying on the photo line. It is the full responsibility of the user to watch the airspace.
Important: Pay special attention to all paragraphs in section "Flight recommendations and
mandatory procedures" in Volume 2, Chapter 2 on Page 92. These paragraphs contain important
information which must be taken into account when executing photo flights with the FCMS
GNSS requirements
Required GNSS quality

Important: Be sure that GNSS fulfills always at least the following limits during a photo flight:
• At least five satellites are tracked
• PDOP is always lower than 4
If the GNSS quality is checked in advance during mission planning always take stricter limits
than given above. E.g. never plan a flight for a time where the expected PDOP is more than 3,
because the actual GNSS constellation during the photo flight might be worse.
Note: The limits given above in the “Important” section are only guidelines because the
following factors have also to be taken into account:
• Distance of airborne system to ground reference station, see below in paragraph " Distance
to GNSS ground reference station for DGNSS processing".
• Area surrounding the ground reference station, e.g. buildings shading the antenna. etc.
• Quality of ground reference receiver
• For Leica IPAS airborne systems providing a deeply coupled real-time solution and if the
data are processed by using Leica IPAS TC the limitations during steep turns are different.
See section "Turns" in Volume 2, Chapter 2 on Page 92.
Distance to GNSS ground reference station for DGNSS processing

Important: Be sure always to fulfill during a photo flight the following limits:
• Fly-over ground reference station before and after image data acquisition.
• In-flight alignment is flown not more than 20 km away from the location of the ground ref-
erence station.
• No part of the project is more than 50 km away form the ground reference station.
• Consider the use of multiple base stations when lines are longer than 100km.
Note: The limits given in the important section above are only guidelines because the following
factors have also to be taken into account:
• Parameters listed above in paragraph " Required GNSS quality".
• No loss of lock during photo flight.
90 Version 3.22-15 - Feb / 25 / 2010

Distance to GNSS ground reference station for PPP processing

PPP processing does not require a GNSS ground reference station. Therefore, no distance limit
exists.
Note: For PPP processing the following factors have also to be taken into account during the
photo flight:
• Parameters listed above in paragraph " Required GNSS quality".
• No loss of lock during photo flight.
Location of GNSS ground reference station

Note: Place the GNSS ground reference station away from hangars, buildings, trees or similar
obstructions. It should have a clear view of the sky at any angle above 10º from the horizon.
Hints for the sensor operator

Note: If you are not flying with real-time differential GNSS, please take into account that the
horizontal error of the GNSS position can be up to 10 m/30 ft. The error in GNSS height can be
up to three times the horizontal error.
Tip: Use the video image to check the path of the flight line at random. This is to detect errors in
flight planning in a timely manner.
Hints for the pilot

Note: It is highly recommended to maintain the required aircraft altitude according to the
displayed value on the altimeter. The GNSS height value is accurate only within a tolerance of up
to +/- 50 m/150 ft.
The pilot is being guided by track offset, heading and true course information. Due to the nature
of these calculations, a certain latency exists in the feedback provided. Therefore, the pilot
should not attempt to make too frequent corrections for every indicated deviation. Too frequent
corrections shorten the heading and offset calculation cycle, which results in pilot induced oscil-
lation and confusion. Therefore, it is recommended to maintain the aircraft heading for a short
time and then correct the heading substantially. In other words:
Too many heading corrections made within a matter of seconds will result in a rough trajectory
and confusing navigation information.
Flight plan requirements

The flight plan should meet certain requirements. Details are given in the corresponding sections
in the sensor system documentation.
Version 3.22-15 - Feb / 25 / 2010 91

Flight recommendations and mandatory procedures
Turns
Important: To avoid loss of lock on GNSS data, flat turns must be flown during the photo
flight. A typical bank angle should be 25° or less if the GNSS constellation is on the required
limits. This helps to ensure perfect post-processing of GNSS-IMU data.
Note: The latest Leica IPAS provides a deeply coupled real time solution. If the sensor system
is equipped such an IPAS system the recommendations for flat turns are no longer valid. With a
system providing a deeply coupled real-time solution, steep U-turns with up to 45° bank can be
flown.
On the flight line

Important: During the image data recording the aircraft attitude in Pitch and Roll must be
within the rotation limits of the gyro-stabilized sensor mount PAV30/80. Only if this is the case,
the sensor can be leveled by the mount and angular image motion is compensated.
The maximum limits of PAV30 rotation are:

• Pitch + 5°
• Roll + 5
• Drift + 30°
The maximum limits of PAV80 rotation are:

• Pitch -8° to +6°
• Roll + 7
• Drift + 30°
Note: Please be aware that the rotation limits of the PAV30/80 given above can be reduced due
to the following reasons:
• Confined space of the aircraft imposes a restriction.
• Aircraft is flying with a low airspeed and therefore the attitude angle is larger than the typi-
cal attitude angle to which the sensor installation was adopted.
92 Version 3.22-15 - Feb / 25 / 2010

In-flight alignment for GNSS-IMU system

In-flight alignment is necessary to initialize and stabilize the IMU of the GNSS-IMU system.
Table 11. Phases during flight execution where an in-flight alignment is required
Air-Start Project execution Interrupted flight execution

After Start-up Before each survey area Before interruption
After each survey area After interruption
Note: For Project execution as an exception there is no need to perform an in-flight alignment if
another survey area was flown less than 20 minutes ago.
Figure 23: Example of in-flight alignments
Steps of in-flight alignment BEFORE flight over survey area or AFTER restart of execution
1. Depending on approach direction, choose one of the patterns given in Figure 24.
2. Start in-flight alignment procedure no more than 10 minutes before first line.
3. At least 5 minutes of flight with constant heading, velocity and altitude.
4. Perform turns according to the pattern at bank angle <25°.
5. Turns must be finished with less than 5 minutes of flight remaining until reaching first line.
Steps of in-flight alignment AFTER flight over survey area or BEFORE flight interruption
1. Depending on the exit direction from the survey area, choose a pattern given in Figure 24.
2. Start in-flight alignment immediately after the last line.
3. Fly a pattern as given in Figure 24 in reverse direction (Example for reverse see Figure 23).
4. Perform turns according to the pattern at bank angle <25°.
5. After turns at least 5 minutes of flight with constant heading, velocity and altitude.
Version 3.22-15 - Feb / 25 / 2010 93

Figure 24: Examples of in-flight alignment patterns
Pattern A Pattern B
This in-flight alignment pattern ensures a This in-flight alignment pattern is economic
perfect in-flight alignment. with respect to flying time. But it needs to be
Sequence of turns is not important. That is, flown perfectly. Otherwise in-flight alignment
either left or right 360 turn can be first. will not be accurate.
Sequence of the 180° tuns is not important. That
is, either left or right turn can be first.
Pattern C Pattern D
This in-flight alignment pattern is ideal if the This alignment pattern is ideal if the approach is
approach is opposite to the line direction. opposite to the line direction.
Pattern E Pattern F Pattern G
This in-flight alignment pattern This in-flight alignment pattern This in-flight alignment pattern
is ideal if approach is opposite is ideal if the approach is 90° to is ideal if the approach is 90° to
to the line direction. the line direction. the line direction.
This pattern needs to be flown This pattern needs to be flown
perfectly. Otherwise in-flight perfectly. Otherwise in-flight
alignment will not be accurate. alignment will not be accurate.
94 Version 3.22-15 - Feb / 25 / 2010

Chapter 3 FCMS - Introduction
Version 3.22-15 Feb / 25 / 2010 95

General
FCMS tasks
The Leica Flight & Sensor Control Management System (FCMS) makes survey flights easier to
perform. Flight guidance and sensor release are conducted using this software. FCMS Software
consists of modules.
Basic function
• Configuration management
Allows flexible system configuration.
• System monitor
For in-flight error detection and recovery. Supervises the system and dataflow to detect mal-
function or operation out of limits.
• Status data logger
Collects data for post flight error analysis.
Main task of the Software module ‘Flight Guidance’

• Flight guidance
Provides flight guidance information on various views for efficient survey flight.
• Device control
Automatic sensor release and configuration. Automatic control of PAV30/80.
• Flight plan management
Monitors progress of project execution and provides in-flight quality control.
Main task of the module ‘Remote Control’

• Locking Management
Operation of multiple user interfaces.
96 Version 3.22-15 - Feb / 25 / 2010

Highlights of FCMS for ALS, frame and other sensors
Modular software components

Leica FCMS is a bundle of powerful components. It includes an operating system, firmware and
software modules. The software modules are licensed according to the customer's requirements.
Easy to learn and simple operation

Leica FCMS supports all types of sensors. It adapts automatically or can be configured for differ-
ent hardware. Clear icons and quick navigation within the menu tree allow easy and simple oper-
ation. The simulator software supports training of operators and pilots on the ground. Leica
FCMS makes survey flights easier to perform.
High-precision, GNSS-supported navigation

Navigation and graphical guidance information is displayed during all phases of the survey flight
• Approach to the mission area
• During the turns
• On the flight line
Both the sensor operator and the pilot can compare the actual aircraft position with the desired
position on their screens. The flight lines to be flown and the direction of approach can be freely
selected. Also, an optimized route-finder algorithm can select the nearest flight line automati-
cally. The best flight path from the current position to the target is displayed. Wind speed and
wind direction are taken into account.
Automatic sensor release

During a flight-plan-controlled survey flight, FCMS starts and stops data recording of a line sen-
sor or LiDAR sensor or releases a frame sensor at the pre-planned positions. Additional record-
ing sequences can be released manually at any time. The Leica PAV80/PAV30 gyro-stabilized
mount is also controlled automatically.
Multi-sensor system control

FCMS can handle multi-sensor systems. Currently, control of the following dual sensor systems
is implemented:
• ADS40/80 and ALS50-II/60
• ALS50-II/60 and frame sensor
Monitoring the progress of project execution

For an efficient photo flight, it is important to know in-flight which lines are not yet flown and
which lines need to be re-flown for various reasons, such as clouds. FCMS monitors the project
execution. It keeps track of the project execution progress and supports in-flight evaluation. If
desired, previous flights are taken into account.
In-flight quality control

During the survey flight, FCMS monitors various parameters such as GPS quality, navigation
accuracy along the flight line, sensor status if available as well as other error conditions. If the
survey data are unusable, flight lines or parts of flight lines are marked accordingly. The user can
also manually mark unusable parts. This information is used for accurate in-flight or post-flight
evaluation repetition.
Version 3.22-15 - Feb / 25 / 2010 97

Accurate repetition of specific flight sections

If a specific portion of a flight line is missed, FCMS will exactly guide the pilot to the missing
parts. For complete coverage of the project area, the re-flown part of the line can be extended.
Flexible user log entries

This feature allows the user to make text entries into the log file during flight execution. The
entries are time tagged and passed along with the flight and image data to the flight evaluation
and data post-processing step.
Data logging for post-flight evaluation

Post-flight mission analysis is essential to manage aerial survey projects, especially for large
projects where more than one aircraft used. All data required to evaluate flights are stored by
FCMS during flight execution.
Leica FCMS, the optimal interface in the Leica work flow

Perfect integration of Hardware and Software into one system is the key for most effective work.
Leica Geosystems' proven integrated workflow starts with flight planning and ends with the
deliverable. With Leica FCMS the sensor is tightly integrated in the entire workflow. This
increases productivity and cuts cost.
Figure 25: work flow form flight planning to flight evaluation
98 Version 3.22-15 - Feb / 25 / 2010

GUI design
The FCMS features a graphical user interface with the following main features:
• clear icons on large buttons
see section "Figurative language on icons" in Volume 2, Chapter 3 on Page 99
• simple hard key interface
see section "User Interface" in Volume 2, Chapter 3 on Page 105
• quick navigation within the menu-tree
see section "Navigation within the menu tree" in Volume 2, Chapter 3 on Page 107
• on-line help
see section "" in Volume 2, Chapter 3 on Page 125
Controls to group information

The graphical user interface ensures a uniform look and feel. During flight execution information
is provided to the user in a simplified form. Close related information is shown in controls. A
control is an area which displays standardized information. E.g. relevant information about the
line in execution is displayed in the line progress control. The controls are part of the different
selectable views. This ensures that the information always appears the same on all views. See
section "Controls" in Volume 2, Chapter 5 on Page 166.
Use of color to group information

For simpler identification information related to each other is displayed in equal color.
Examples:
• Cyan is used as main color for the aircraft. Therefore, the aircraft symbol appears in cyan,
the aircraft’s track over ground and the aircraft’s altitude are displayed in a field with cyan
background or frame.
• Red is used for the flight line. Therefore, the actual flight line is displayed as red line in the
graphics and the values for desired altitude and the target GS are displayed in a red frame.
• Yellow background is used for fix settings.
Figurative language on icons

• self-explanatory, easy to learn
• same key figures are used in many icons
• hot key buttons for quick change of view during flight execution
• well known symbols from other GUI are used in icons
Version 3.22-15 - Feb / 25 / 2010 99

Key figures
Aircraft
Indicates flight and flight related data.
Used in combination with flight line, heights and flight plan.
Sheet
Indicates data.
Used for flight plan and projects.
Examples
Red line
Indicates flight line.
Used in combination with flight line selection, project/filter and air-

craft.
Examples
Various shapes
Indicates system configuration.
Used in combination with manual configuration, other data set, etc.
Examples
100 Version 3.22-15 - Feb / 25 / 2010

Magnifying glass
Indicates view of details.
Used in combination with image for zoom in/out and to show more
information.
Examples
Funnel
Indicates data filtering.
Used in combination with devices and actions.
Examples
Hand
Indicates manual actions.
Used in combination with other symbols.
Examples
Trash Can
Indicates data deletion.
Used also in combination with data symbols.
Examples
Version 3.22-15 - Feb / 25 / 2010 101

Eye
Indicates visualization.
Used also in combination with other symbols.
Examples
Key figures for components of the sensor system

Sensor symbol
Indicates information related to the sensor.
Used in combination to show next information, data filter etc.
Examples
Arrow with rotated circle

Indicates Inertial Measurement Unit (IMU).
Used also in combination with data filter.
Examples
Satellite symbol
Indicates Global Navigation Satellite System (GNSS).
Used also in combination with data filter.
Examples
102 Version 3.22-15 - Feb / 25 / 2010

Cylinder
Indicates Mass Memory.
Used also in combination with data filter and actions.
Examples
Safe
Indicates internal memory of Control Unit.
Used mainly in the data handling dialogues (upload, download,

delete).
Examples
Mount symbol
Indicates Gyro-stabilized mount.
Used to set operational status or mount manually.
Examples
PC Card
Indicates transfer media. Either PC-Card or USB memory stick.
Used in the data handling dialogues (upload, download, delete).
Examples
Version 3.22-15 - Feb / 25 / 2010 103

Icon types
Workflow
Examples
Enter data handling module. Enter configuration module.
Enter flight execution module. Return to previous menu.
Activity
Example
Start image data recording. Select to fly previous line.
Stop image data recording. Decrease value.
Change of view
Examples
Show Sensor status view. Show next sub-view.
Show Project view. Show Nose-up navigation view.
Button change
Examples
Change buttons on toolbar-display Change buttons on toolbar-display
buttons related to current view. buttons to adjust display of
images.
Change buttons on toolbar-display Change buttons on toolbar-display

buttons to select view. buttons to set filter to hide infor-
mation.
104 Version 3.22-15 - Feb / 25 / 2010

User Interface
General screen layout
Figure 26: Example screen layout
Title bar For name of view
View area To display information dialogs etc.
Status line For short help text or other messages

Toolbar Area for the icons
Each view has a title bar with the name of the view or dialog.
The content of the view area is according to the view or dialog.
In the status line, status or error messages as well as first help level texts are displayed.
On the bottom of the screen a bar with a maximum of 10 large icons is displayed. This icons
allow the user to control FCMS.
Touch screen interface on OC52

On the bottom of the screen of the OC52 display, a bar with a maximum of 10 large touch sensi-
tive icons is displayed. This is the main touch interface area on the screen. All user interaction for
workflow commands, activities, change of views and button changes can be performed by touch-
ing the appropriate icon on the tool bar.
Beside the tool bar, additional areas on the screen are touch sensitive in some views. These addi-
tional touch sensitive areas enable user input shortcuts.
Examples:
• to select an input field the user can touch the input area on the view
• to display another view the user can touch the desired TAB on the screen
• to show status of a sub-device the user can touch the corresponding control on the screen.
Figure 27: Examples of touch screen fields in different views
As an alternative to the [Next view] icon, the

TABs on top of the screen can be selected
directly.
As an alternative to using the [Up] or [Down]

icons to select a configuration sub-set, the
area of the desired sub-set can be touched on
the screen.
Version 3.22-15 - Feb / 25 / 2010 105

As an alternative to using the [Tab left] or

[Tab right] icons to select an input field, the
desired input field can be touched on the
screen.
To display status views of a sensor sub-

systems such as ‘GNSS’, the corresponding
control can be touched.
Hard key interface on OC50

On the bottom of the housing of the OC50 10 hardware keys are placed below the screen. This is
the main interface. All user interaction for workflow commands, activities, change of views and
button changes can be performed by touching the appropriate hardware key located below the
icon displayed on the FCMS tool bar.
Additional hardware keys are located on the housing on the left side of the screen. These keys
enable user input shortcuts. E.g. In 1st level help mode the key located by the control can be con-
firmed to display the 1st level help text in the status line.
Figure 28: Hardware keys on OC50 for FCMS control
106 Version 3.22-15 - Feb / 25 / 2010

Navigation within the menu tree

The user interface is designed to minimize the complexity of the system. Therefore, the tasks are
organized into just a few menus and each menu tree has only a few levels. The menu tree is just
the internal skeleton of the software. To use the system, the user has not necessarily to memorize
it. The user interface allows for quick navigation within the menu tree.
• In menu ‘Flight’ hot-key buttons allow for fast changes of views.
• In menu ‘Flight’ direct links between nodes in ‘Flight’ to ‘Configuration’ are implemented.
See section "Navigation within the menu tree in flight execution" in Volume 2, Chapter 3 on
Page 107.
Navigation within the menu tree in flight execution

During fight execution different processes (sub-programs) are running simultaneously. These dif-
ferent processes control:
• Sensor sub-systems such as GNSS-IMU.
• Flight guidance based on GNSS and flight plan
• Project management - In-flight evaluation
Status of each process is shown on the operator interface. Therefore, the user can select different
views:
• GNSS Status
• Flight guidance - Nose-up
• Flight guidance - North-up
• Flight guidance - In-line
• Flight guidance - 3D view
• In-flight evaluation
Select the button [View] on the toolbar of the operator interface to select another view. This is
like switching from one process to another.
In terms of software design this is similar to horizontal navigation in the menu tree.
Select the button [More buttons] to change the toolbar. This is to show buttons to control work-
flow, confirm activities or to show a status view of a sub-system.
In terms of software design this is similar to vertical navigation in the menu tree.
Illustration see Figure 29, “Illustration of menu tree during flight execution” in Volume 2, Chap-
ter 3 on Page 108.
Version 3.22-15 - Feb / 25 / 2010 107

Figure 29: Illustration of menu tree during flight execution
Navigation within the menu tree to reach ‘Configuration’
Menu ‘Configuration’
FCMS configuration allows for the quick adaptation of the Software for different applications. In
menu ‘Configuration’ the user can predefine configuration sets as required for the various appli-
cations.
Menu ‘Flight’
Links from the flight menu tree to the configuration menu tree are implemented to enable quick
changes of the FCMS Configuration during flight without the need to quit ‘Flight’ and select
‘Configuration’ from the FCMS main menu. Unlike in menu ‘Configuration’ the Sensor sub-sys-
tems like GNSS/IMU are in a operational state in menu ‘Flight’. Therefore the global parameter
‘Installation’ cannot be changed.
Figure 30: Illustration of menu tree during configuration
108 Version 3.22-15 - Feb / 25 / 2010

Online help
Online help can be selected from any menu level at any time. The 'Help' button is part of the but-
ton bar on each view. The online help facility consists of two levels:
• First help level gives a short description of each button on the status line.
• Second help level allows browsing of FCMS documentation.
Note: Entering help does not interrupt operation of the sensor. For example, if the recording of
data was activated, this status remains the same even if the user enters help.
First help level- short description

Select [Help] to activate first help level.
Select any button or control to display the corresponding help text in the status line.
Figure 31: Example view first help level
The Green background of the status line indicates that

first help level is activated.
In this mode, just touch any button or control to get a short
description of it on the status line.
Select [Help Return] to quit help level and to return to normal operation.
Version 3.22-15 - Feb / 25 / 2010 109

Second help level - online documentation

Note: Entering second level help is only possible from first level help. It does not interrupt
operation of the sensor. For example, if the recording of data was activated, this status remains
the same even if the user enters second level help.
Use [Left arrow] and [Right arrow] to jump to previous or next section of the text.
Use [Scroll up] and [Scroll down] to scroll smoothly in the text.
Use [Fast scroll up] and [Fast scroll down] to scroll pages in the text.
Use [Home] to jump to table of content in second help level. (Online documentation).
Select [Help-Return] to leave help level.
110 Version 3.22-15 - Feb / 25 / 2010

Icon reference list
Most frequently used icons

Name 001-File
Type Workflow
Purpose Enter data handling module - file operations, data upload and download.
Name 002-Flight/Sensor Start-Stop

Type Workflow
Purpose Enter flight execution module - automatic or manual sensor release.
Name 004-Configuration
Type Workflow
Purpose Enter configuration module. (When selected from main menu.)
Enter configuration dialog to current view. (When selected within flight execution.)
Name 134-End
Type Workflow
Purpose Exit Flight.
Quit FCMS and shutdown FCMS system.
Name 031-Return
Type Workflow
Purpose Return to previous menu. Quit or cancel. Appropriate message box appears.
Name 010-More buttons

Type Button change
Purpose Change buttons on toolbar - display buttons related to current view.
Name 011-Annotation
Type Workflow - Activity
Purpose Enter module to manage text for log file entries.
Generate a log file entry. Highlighted text is stored with a time tag in the log file.
Name 005-Service
Type Workflow
Purpose Enter service level.
Start system recovery
Version 3.22-15 - Feb / 25 / 2010 111

Icons for the on-line help

Name 006-Help
Type Activity
Purpose Activate first help level to display short help text in status line.
Name 158-Help detail

Type Workflow
Purpose Enter second help level to browse the on-line documentation.
Name 159-Help return

Type Workflow
Purpose Return from help, first or second level.
Name 094-Home
Type Activity
Purpose Jump to table of content in second help level (online documentation).
Icons to control sensor release

Name 145-Start/Stop recording
Type Workflow
Purpose Enter sensor release/sensor stop level.
Name 008-Start recording

Type Activity
Purpose Start image data recording.
Name 072-Stop recording

Type Activity
Purpose Stop image data recording.
Name 053-Single release

Type Activity
Purpose Release manually a single frame
Name 051-Quality Error

Type Activity
Purpose Start marking a section on a line. (E.g. data are useless due to clouds)
Name 052-Quality Cancel

Type Activity
Purpose Stop marking a section on a line. (Because data are not any more useless)
112 Version 3.22-15 - Feb / 25 / 2010

Icons to change views during flight execution

Name 009-Select View
Type Button change
Purpose Change buttons on toolbar - display buttons to select view.
Name 016-North-up View

Type Change of view
Purpose Show North-up navigation view.
Name 015-Nose-up View

Type Change of view
Purpose Show Nose-up navigation view
Name 017-In-line View

Type Change of view
Purpose Show In-line navigation view.
Name 175-3D-Navigation
Type Change of view
Purpose Show 3D-navigation view.
Name 019-Project View

Type Change of view
Purpose Show Project view.
Name 074-Text
Type Change of view
Purpose Show Project data alphanumerically.
Name 075-Graphic
Type Change of view
Purpose Show Project data graphically.
Name 020-Sensor system

Type Change of view
Purpose Show system status view.
Name 088-Sensor
Type Change of view
Purpose Show Sensor Head status view.
Name 090-IMU
Type Change of view
Purpose Show GNSS-IMU system status view.
Name 055-PAV
Type Change of view
Purpose Show Gyro Stabilized Mount status view.
Version 3.22-15 - Feb / 25 / 2010 113

Name 091-GNSS
Type Change of view
Purpose Show GNSS status view.
Name 078-Log Data

Type Change of view
Purpose Show log data.
Icons to scroll in list

Name 023-Fast scroll up
Type Activity
Purpose Scroll up fast in list.
Name 024-Scroll up
Type Activity
Purpose Scroll up in list.
Name 025-Scroll down

Type Activity
Purpose Scroll down in list.
Name 026-Fast scroll down

Type Activity
Purpose Scroll down fast in list.
Icons to select input fields

Name 027-TAB left
Type Activity
Purpose Select previous input field in view.
Name 028-TAB right

Type Activity
Purpose Select next input field in view.
114 Version 3.22-15 - Feb / 25 / 2010

Icons to enter values

Name 042-Large increment
Type Activity
Purpose Increase value in input field in large steps.
Name 043-Increment
Type Activity
Purpose Increase value in input field in steps.
Name 044-Decrement
Type Activity
Purpose Decrease value in input field in steps.
Name 045-Large decrement

Type Activity
Purpose Decrease value in input field in large steps.
Name 133-Default set

Type Activity
Purpose Restore default values
Input and message control icons

Name 164-Accept
Type Activity
Purpose Accept message, changes etc.
Name 155-Cancel
Type Activity
Purpose Cancel changes - restore previous settings.
Name 165-Save
Type Activity
Purpose Accept changes and save.
Name 166-Save as
Type Activity
Purpose Accept changes and save as new data set.
Version 3.22-15 - Feb / 25 / 2010 115

Icons to select / unselect data

Name 029-Select
Type Activity
Purpose Select data at cursor position.
Name 041-Select all

Type Activity
Purpose Select all data listed.
Name 030-Deselect
Type Activity
Purpose Deselect data at cursor position.
Name 107-Deselect all

Type Activity
Purpose Deselect all selected data
Icons to edit / create data

Name 104-Edit
Type Workflow
Purpose Enter dialog to edit selected data set.
Name 105-New
Type Workflow
Purpose Enter dialog to create new data set.
116 Version 3.22-15 - Feb / 25 / 2010

Icons for execution of planned flights

Name 007-Select Project
Type Change of view
Purpose Display project listing for project/flight plan selection.
Name 022-Plan line more

Type Button Change
Purpose Change buttons on toolbar - display buttons to select flight lines.
Name 033-Select Plan

Type Change of view
Purpose List flight plans for flight plan selection. Not yet implemented.
Name 035-Previous line

Type Activity
Purpose Select to fly previous line.
Name 036-Next line

Type Activity
Purpose Select to fly next line
Name 034-GOTO line

Type Workflow
Purpose List lines for selection of the line to be flown next
Name 037-Part line

Type Workflow
Purpose Shorten or extend the line at line start or line end point.
Name 038-Reverse line

Type Activity
Purpose Reverse direction of approach to next line
Name 032-Abort
Type Activity
Purpose If flying along a line: Abort line execution
If not flying along a line: End project execution.
Name 039-Recompute
Type Activity
Purpose Search for closest line
Name 056-Recalc
Type Activity
Purpose New computation of optimum flight path to next line.
Name 046-Alignment
Type Change of view
Purpose Show in-flight alignment patterns. Not yet implemented
Version 3.22-15 - Feb / 25 / 2010 117

Name 171-Execute part

Type Activity
Purpose Execute only part of line
Name 172-Execute whole

Type Activity
Purpose Execute whole line.
Icons to adjust video image

Name 061-Adjust image
Type Button change
Purpose Change buttons on toolbar - display buttons to adjust the image.
Name 062-Decrease brightness

Type Activity
Purpose Decrease brightness of image.
Name 063-Increase brightness

Type Activity
Purpose Increase brightness of image.
Name 064-Decrease contrast

Type Activity
Purpose Decrease contrast of image.
Name 065-Increase contrast

Type Activity
Purpose Increase contrast of image.
118 Version 3.22-15 - Feb / 25 / 2010

More icons
Name 120-Previous configuration set
Type Activity
Purpose Display previous configuration set.
Name 121-Next configuration set

Type Activity
Purpose Display next configuration set.
Name 151-Next ADS status view

Type Change of view
Purpose Show next sensor status sub-view.
Name 154-Next view

Type Change of view
Purpose Show next sub-view, wrap from last sub-view to first sub-view.
Name 069-Arrow down

Type Activity
Purpose Select section below, or pan graphics
Name 068-Arrow up
Type Activity
Purpose Select section above, or pan graphics
Name 070-Arrow left

Type Activity
Purpose Jump to previous item, section etc. Or pan graphics
Name 071-Arrow right

Type Activity
Purpose Jump to next item, section, continue in process etc. Or pan graphics
Name 097-Previous error warning

Type Activity
Purpose Jump to previous warning / error log file entry when browsing the logged data.
Name 098-Next error warning

Type Activity
Purpose Jump to next warning / error log file entry when browsing the logged data.
Name 182-Auto Config

Type Activity
Purpose Start automatic configuration.
Version 3.22-15 - Feb / 25 / 2010 119

Icons to zoom graphical information

Name 057-Zoom out
Type Activity
Purpose Zoom out.
Name 073-More zoom

Type Button change
Purpose Change buttons on toolbar - display buttons to shift / zoom graphical information.
Name 058-Zoom in
Type Activity
Purpose Zoom in.
Name 092-Zoom wrap

Type Activity
Purpose Change to next zoom step, wrap from maximum zoom to minimum zoom.
Name 066-Zoom optimum

Type Activity
Purpose Scale adjustment to display the whole project in this view.
Name 170-Center AC
Type Activity
Purpose Pan center of viewing area to aircraft.
Icons to show or hide data in graphical or alphanumerical views

Name 083-Show lines with one flight
Type Activity
Purpose Show flight lines completed in one execution.
Name 083A-Hide lines with one flight

Type Activity
Purpose Hide flight lines completed in one execution.
Name 084-Show multi flights

Type Activity
Purpose Show flight lines completed in more than one execution.
Name 084A-Hide multi flights

Type Activity
Purpose Hide flight lines completed in more than one execution.
Name 129-Show flights with warnings

Type Activity
Purpose Show flight lines flown with warnings.
120 Version 3.22-15 - Feb / 25 / 2010

Name 129A-Hide flights with warnings

Type Activity
Purpose Hide flight lines flown with warnings.
Name 130-Show erroueous flights

Type Activity
Purpose Show flight lines flown with error condition.
Name 130A-Hide erroueous flights

Type Activity
Purpose Hide flight lines flown with error condition.
Name 086-Show not flown flights

Type Activity
Purpose Show flight lines not yet flown.
Name 086A-Hide not flown flights

Type Activity
Purpose Hide flight lines not yet flown.
Name 168-Show manual flights

Type Activity
Purpose Show non-planned manually released flight lines.
Name 168A-Hide manual flights

Type Activity
Purpose Hide non-planned manually released flight lines.
Name 079-Show planning

Type Activity
Purpose Show flight planning.
Name 168A-Hide planning

Type Activity
Purpose Hide flight planning
Name 169-Show path

Type Activity
Purpose Show flight path.
Name 169A-Hide path

Type Activity
Purpose Hide flight path.
Version 3.22-15 - Feb / 25 / 2010 121

Icons to filter data when browsing log data

Name 076-Set filter
Type Button change
Purpose Change buttons on toolbar - display buttons to set filter to hide information.
Name 077-Remove filter

Type Activity
Purpose Remove all filters - show all information.
Name 085-Filter user actions

Type Activity
Purpose Set filter: show logged user actions.
Name 124-Filter Sensor system

Type Activity
Purpose Set filter: show logged Sensor status data.
Name 100-Filter Sensor Head

Type Activity
Purpose Set filter: show logged sensor status data.
Name 102-Filter IMU

Type Activity
Purpose Set filter: show logged GNSS-IMU status data.
Name 103-Filter GNSS

Type Activity
Purpose Set filter: show logged GNSS status data.
Name 081-Filter warnings/errors

Type Activity
Purpose Set filter: show logged warnings and errors.
Name 099-Date/time
Type Activity
Purpose Seek in the log database the entry closest to the defined date and time.
Name 095-Remove date/time

Type Activity
Purpose Seek in the log database the latest log data entry.
122 Version 3.22-15 - Feb / 25 / 2010

Icons to copy data

Name 136-Upload all
Type Activity
Purpose Upload all data on PC-Card to CU40.
Name 137-Upload selected

Type Activity
Purpose Upload selected data on PC-Card to CU40.
Name 147-Download all

Type Activity
Purpose Download all data on CU40 to PC-Card.
Name 135-Download selected

Type Activity
Purpose Download selected data on CU40 to PC-Card.
Name 146-Download new

Type Activity
Purpose Download new data on CU40 to PC-Card.
Name 050-Download log data

Type Activity
Purpose Download log data on CU40 to PC-Card or USB Stick.
Icons in service area

Name 047-SW-Upload
Type Workflow
Purpose Enter dialog to upload new firmware, software releases and modules.

Type Activity
Purpose Download log data on CU40 to PC-Card or USB Stick.
Name 005-Service
Type Workflow
Purpose Upload special configuration
Name 173-License
Type Workflow
Purpose Upload or check license.
Version 3.22-15 - Feb / 25 / 2010 123

Icons to delete data

Name 106-Delete
Type Workflow
Purpose Enter data delete level.
Name 138-Delete external

Type Workflow
Purpose Enter dialog to delete data on PC-Card.
Name 139-Delete internal

Type Workflow
Purpose Enter dialog to delete data on internal memory of Control Unit.
Name 40-Delete selected

Type Activity
Purpose Delete selected data.
Name 167-Delete configuration

Type Activity
Purpose Delete highlighted configuration set.
Name 093-Delete annotation

Type Activity
Purpose Delete highlighted annotation text line from the text list.
124 Version 3.22-15 - Feb / 25 / 2010

Icons for stabilized mount

Name 055-PAV
Type Change of view
Purpose Show Gyro Stabilized Mount status view.
Name 008-Start
Type Activity
Purpose Start selftest
Name 178-PAV-Auto
Type Activity
Purpose Set PAV operational mode to AUTO
Name 179-PAV-Auto
Type Activity
Purpose Set PAV operational mode to OFF
Name 176-ListWarning
Type Change of view
Purpose Show logged warnings and errors
Name 177-ListPAV
Type Change of view
Purpose Show logged PAV performance data.
Name 078-Log Data

Type Change of view
Purpose Show log data.

Type Activity
Purpose Download log data to USB memory stick.
Name 164-Accept
Type Activity
Purpose Move PAV to desired position
Name 165-Save
Type Activity
Purpose Store current attitude angle as maximum range.
Version 3.22-15 - Feb / 25 / 2010 125

126 Version 3.22-15 - Feb / 25 / 2010

Chapter 4 FCMS - Configuration
Version 3.22-15 Feb / 25 / 2010 127

About configuration
Configuration data base
Overview
All configurable parameters are store in a configuration data base. From the user’s point the
parameters are grouped as given in Table 12:
Table 12. Overview configurable parameters
Scope Main Group Group Sub-Group

Configuration Set Sensor & Height Sensor
Height
System Hardware Primary Sensor
See page 131
Slave Sensor
GNSS/IMU System
Global 1 Flight & Release Guidance Project
See page 147 Guidance Approach
Sensor Release Control
Time Zone
Installation
Real-time view
Global 2 Units
See page 160
Views
Advanced
See page 163
The configuration of FCMS is given by a ‘Sensor and height configuration set’ and the ‘Global
configuration’ consisting of ‘Hardware’, ‘Global 1’, ‘Global 2’ and ‘Advanced’.
The FCMS configuration sets allow for the quick adaptation of FCMS different applications. Just
select a configuration set and all relevant configuration parameters for an application are set.
Data base structure

• Configuration of sensor and height parameters
Sensor and height configuration parameters are stored in records in the main list of the
FCMS configuration database. The number of records is not limited. A record is called a
Sensor & height configuration set. Each configuration set in the main list contains fields
with links to records in sub-lists of the FCMS Sensor & height configuration database. A
sub-list contains closely related configuration parameters. Examples of sub-lists: sub-list
with records for Sensor configuration, sub-list with records for Height configurations etc.
The number of records in a sub-list is not limited. A record in a sub-list is called a configu-
ration sub-set.
• Configuration of global parameters
128 Version 3.22-15 - Feb / 25 / 2010

Additionally global configuration sub-lists are defined in the system. Global sub-lists con-
tain system parameters with a scope not necessarily limited to an application. Examples of
global sub-lists: Sub-list with records for installation parameters, sub-list with records for
time zone etc. This sub-lists allows storing of different configurations to enable a quick and
convenient change of configuration parameters. The global configuration contains links to
records in global configuration sub-lists.
Note: To change the configuration typically another ‘Sensor & height configuration set’ is
selected.
To change the Time Zone the link in the global configuration to the record in the global sub-list
‘Time Zone’ is changed.
Configuration sets
Select [Configuration] from the FCMS main menu to enter Leica RCD100 configuration dialog
view.
Figure 32: Example ‘Main Configuration’ dialog’
The topmost on the list is the ‘Current configuration’ set.

The origin of this configuration set is displayed in the
right most column.
In the next group of sets the ‘Pre-defined sets’ are listed.
A set can also be selected by touching the desired row.
In the last group of sets the ‘User defined sets’ are listed,
if such sets have been defined.
Use [Scroll Up] [Scroll Down] to select the desired configuration set.
The selected configuration set is marked with the highlighted bar.
Select [Configuration] to enter configuration dialog to configure the highlighted configuration

set.
Select [Delete Configuration] to delete the highlighted configuration set. A message window will
pop up to confirm deletion.
Pre-defined configurations cannot be deleted. An appropriate message will appear.
Select [Return] to load the highlighted configuration set and to return from dialog.
Version 3.22-15 - Feb / 25 / 2010 129

Pre-defined configuration sets

This icon shown on the left most column of the configuration set listing indicates a
set of type ‘Pre-defined’.
Pre-defined configuration sets can be selected to load to the system. These sets can also be
selected for editing to save as a ‘User defined set’. The pre-defined sets cannot be deleted.
Note: A description of the pre-defined configuration data sets is given in the appendix to the
FCMS release notes.
User defined configuration sets

This icon shown on the left most column of the configuration set listing indicates a
set of type ‘User defined’.
Any number of configuration sets can be defined by the user. To create a new set, an existing set
is selected, edited and stored under a new name. The existing set can be either a pre-defined or a
user defined set already defined.
Current configuration set

This icon shown on the left most column of the configuration set listing indicates
that this set is the ‘Current configuration’.
If a configuration set of type ‘Pre-defined’ or ‘User defined’ is selected to be used for system
configuration the set is duplicated and replaces the previous ‘Current configuration set’ in the
configuration set listing. The origin of this set is displayed on the right most column of the con-
figuration set listing.
The ‘Current configuration’ set can be selected during configuration just like a ‘Pre-defined’ or
‘User defined’ set. This set can then be edited and saved as ‘User defined’. It cannot be deleted.
If changes are made to the system configuration during flight execution via a direct link to a low
level configuration node, the changes affect the ‘Current configuration’ set. See section "Naviga-
tion within the menu tree" in Volume 3, Chapter 3 on Page 288. The modification will be indi-
cated on the right most column of the configuration set listing. The set of origin will not be
affected.
130 Version 3.22-15 - Feb / 25 / 2010

System configuration: Hardware

Important: Always perform a system check after a hardware configuration change was made.
Sensor and GNSS Configuration sets for different sensors

Table 13. Overview of configuration sets for various sensor systems
Sensor system Name of pre-defined Name of pre- Sensor release trigger

sensor configuration set defined GNSS
configuration
set
ALS60 ALS LAN IPAS(LAN) FCMS command
ALS60 ALS LAN with frame IPAS(LAN) ALS by FCMS command
with frame camera sensor Frame by IPAS event
ALS50 ALS via serial IPAS(LAN) FCMS command
ALS50 ALS via serial with IPAS(LAN) ALS by FCMS command
with frame camera frame sensor Frame by IPAS event
Frame Sensor Frame Sensor without IPAS(LAN) by IPAS event
without protocol protocol
Line Sensor Line Sensor without IPAS(LAN) by IPAS event
without protocol protocol
RC30 IPAS FCMS command
RC30 with IPAS
RC20 or Frame Sensor IPAS FCMS command or IPAS

RC10/20 with IPAS
without protocol trigger
Ground test of any According to the system Simulator with ALS by FCMS command
sensor system to be tested IPAS Frame by IPAS event
Desktop simulation None Simulator None
Version 3.22-15 - Feb / 25 / 2010 131

Enter Hardware Configuration

Select [Configuration] from the main menu.
Confirm [Next view] to display configuration of parameters Hardware.
Figure 33: Example of main configuration dialog TAB Hardware
In the main configuration dialog a summarized overview

of the parameters of the selected configuration is given.
This is also the entry point for changing, editing and creat-
ing configuration sub-sets.
The dialog shows an overview of the selected hardware:
- Primary sensor system
- Secondary sensors system
- GNSS system
Use [Previous configuration set] or [Next configuration set] to display another configuration set
in the selected sub-set field.
Use [Up] and [Down] to select another sub-set field.

On the OI40 you can also touch on the area to select another sub-set field.
Select [Return] to open dialog for ‘Save’, ‘Cancel’
132 Version 3.22-15 - Feb / 25 / 2010

Sensor configuration
Parameter description
Note: Some settings may not be applicable for certain sensor types
Table 14. Sensor configuration parameters
Parameter Setting Remarks

Sensor type select from list Select sensor type according to Table 13 on
Page 131.
Sensor generates MEP Yes If the frame sensor sends a mid exposure pulse
No back to the IPAS input event port select “Yes”.
FCMS checks that the pulse is received and issues
a warning if it is missing.
FCMS also uses the pulse’s time to store the
frame’s position accurately in the flight plan
database.
Lens Cone Type 8.8 cm Only relevant for the Leica RC20/30 cameras
15cm/21cm/30cm
LAN IP address select from list In a typical configuration only one address is
listed.
Sensor Lead Time 0.001 to 10.0 sec Relevant for frame sensors. This field defines
how many seconds ahead of the planned release
position the release pulse is sent
Release Pulse Width typically 0.025 s Relevant for frame sensors, but not if triggered
through IPAS
Minimum Cycle Time sensor specific Minimal time between frame releases. Set this
value to the time the frame sensor needs after a
release to be ready for a next release.
Ground Test Mode Disabled Only used for ALS60. If ‘Enabled’ the shutter is
Enabled always closed. This is to ensure safe operation on
ground for test or service purposes. Enable is
mandatory if GNSS receiver is configured to
‘Simulation’ or ‘Simulation with IPAS’
Sensor Port Settings: COM port setting specifies the port used for the camera
communication protocol
Mount Mount type Defines mount type.
Use ’PAV80 Sim’ for simulation only
COM port settings Defines the port used for the PAV communication
(COM OP)
Port setting for simulation: None
Version 3.22-15 - Feb / 25 / 2010 133

Select configuration
To enter the sensor configuration dialog from the FCMS main menu proceed as follows:
1. select [Configuration]
2. select TAB ‘Hardware’
3. Use [Arrow up] and [Arrow down] to highlight the sub-set ‘Sensor’
Select [Configuration] to enter configuration dialog for the sub-set.
Figure 34: Example of ‘Hardware Configuration’ dialog for ‘Sensor configuration’
In this dialog an overview of the configuration is given for

the sensor configuration.
The fields displayed depend on the sensor type
Only advanced users shall make sensor configurations.
A description of typical settings for the various sensor

systems starts at paragraph “Sensor type ‘ALS LAN’” on
Page 135.
Use [Tab Left] [Tab Right] to select desired input parameter.
Select [Default] to restore default values.
Select [+] button to increment a value or to toggle a parameter.


Select [Return] to open dialog for ‘Save’, ‘Save as’ or ‘Cancel’.
134 Version 3.22-15 - Feb / 25 / 2010

Sensor type ‘ALS LAN’

Select this type to use an ALS60 connected on the specified port. For a standard installation don’t
change these settings.
This option is not available in the FCMS desktop simulation.
Typical setting ‘ALS60 LAN with frame sensor’

Select this type to use an ALS60 connected on the specified port. This setup additionally triggers
a frame camera through the IPAS system's 4 output events. This setup requires that "IPAS-
(LAN)" is selected in the GNSS configuration, otherwise the frame sensor will not be released.
Important: Do only set the field ‘Sensor generates MEP ‘ to ‘Yes’ if the frame sensor transmits
a MEP to FCMS.
Important: This option is not available in the FCMS desktop simulation
Version 3.22-15 - Feb / 25 / 2010 135

Sensor type ‘ALS via Serial’

Select this type to use an ALS connected on the specified port. For a standard installation don’t
change these settings.
Typical setting ‘ALS via Serial with frame sensor’

Select this type to use an ALS connected on the specified port. This setup additionally triggers a
frame camera through the IPAS system's 4 output events. This setup requires that "IPAS-(LAN)"
is selected in the GNSS configuration, otherwise the frame sensor will not be released.
a MEP to FCMS.
136 Version 3.22-15 - Feb / 25 / 2010

Typical setting ‘Line Sensor without protocol’

Select this type to use a line sensor attached to the IPAS event lines.
a MEP to FCMS.
Typical setting ‘Line Sensor with protocol’

Select this type to use a line sensor connected to the IPAS event lines. The sensor port may differ
for your particular setup. If a PAV is installed, the port needs to be set according to the installa-
tion.
a MEP to FCMS.
Version 3.22-15 - Feb / 25 / 2010 137

Typical setting ‘Frame Sensor without protocol’

Select this type to use a frame sensor attached to the IPAS event lines.
a MEP to FCMS.
Typical setting ‘Frame Sensor with protocol’

Select this type to use a frame sensor connected to the IPAS event lines. The Sensor port may dif-
fer for your particular setup. If a PAV is installed, the port needs to be set according to the instal-
lation.
a MEP to FCMS.
138 Version 3.22-15 - Feb / 25 / 2010

Typical setting ‘RC30’

Select this type to use an RC30 connected via the RCIF30 to IPAS. Typically, a PAV30 is part of
the camera system.
Important: Select the lens cone type in use to ensure the photographs are released at the
desired positions.
Typical setting ‘R10/RC20’

Select this option to use an RC10A or an RC20 connected via the RCIF30 to IPAS. Disable MEP
if it is an RC10A which does not generate an MEP. Enable MEP for a RC20. If the camera is a
RC20+EDI, select Sensor type ‘RC30’ instead.
Version 3.22-15 - Feb / 25 / 2010 139

Typical setting ‘No Camera’

Select this type to use the system without an attached sensor
140 Version 3.22-15 - Feb / 25 / 2010

GNSS- IMU system configuration
Parameter description
Note: Some settings may not be applicable for certain receiver types
Table 15. Receiver configuration parameters

Receiver type select from list Select sensor type according to Table 13 on
Page 131.
Receiver generates PPS Yes Only applicable for NMEA. If YES, FCMS
No expects and uses the PPS signals; a warning is
issued if there is no PPS signal.
LAN IP Address select from list During configuration the system browses the
network to detect all available IPAS systems.
Port Master Used by IPAS controller software
Slave1 Used for ALS data logger or ADS80 MMAgent
Slave2 Default for FCMS. Do not change it unless
advised by Leica support.
Slave3 Used for RCD100 or for frame camera attached to
ALS
Slave4 not used
Slave5 not used
MEP Event Channel 0 to 3 IPAS supports event channel 0 to 3. FCMS
monitors one of these channels. Select in FCMS
the same event channel as configured in IPAS.
In case of a multi- sensor system set the event
channel of the sensor which should be supervised
by FCMS.
In case of a configuration ‘ALS with attached
frame camera’, the default connector on the SC50
is Aux 1. In this case in FCMS Event Channel #2
has to be configured.
RS232 Port Settings COM port Make sure the settings match with the NMEA
setting source port settings
Version 3.22-15 - Feb / 25 / 2010 141

Configuration
To enter the GNSS configuration dialog from the FCMS main menu proceed as follows:
2. select TAB ‘Hardware’
3. Use [Arrow up] and [Arrow down] to highlight the sub-set ‘Sensor’
Figure 35: Example of dialog for ‘GNSS configuration’
In this dialog an overview of the configuration is given for

the GNSS configuration.
The active fields depend on the Receiver type

In case of IPAS the IP address and the Port has to be set.
For this the IPAS system must be connected and powered.
A description of typical settings starts at paragraph

“Typical setting ‘IPAS (LAN)’” on Page 143.
Select [Default] to restore default values.


142 Version 3.22-15 - Feb / 25 / 2010

Typical setting ‘IPAS (LAN)’

Select this type to use an IPAS system as a position source through a network connection. The
editable fields are "LAN IP Address" and “Port”. The LAN IP address allows browsing through
the available systems on the network. Typically there is only one system with the address
10.60.135.4 available. The Port is typically ‘Slave 2’.
Note: The flight plan prepared in FPES for flight execution with FCMS contains release events.
Each release event is labeled with a release event type. The release event type depends on the
sensor type. During flight execution FCMS sends the release events and the corresponding
release event types to IPAS. IPAS has four event channels. Each event channel can be configured
to pass or block events based on the release event type. This configuration is made in the IPAS
controller software. Details are given in the IPAS Technical Reference Manual.
Figure 36: Example. Event channel setup in IPAS Controller.
Version 3.22-15 - Feb / 25 / 2010 143

Typical setting ‘Simulator’

Used to run FCMS simulation on a desktop computer
Select this type to use static default values for all position parameters. If the application "Flight-
Sim" is running, FCMS receives position information and a flight can be simulated.
Typical setting ‘Simulator IPAS’
Used for ground test of a sensor system.

Select this type to use static default values for all position parameters. If the application "Flight-
Sim" is running, FCMS receives position information and a flight can be simulated.
Typical setting ‘NMEA (RS232)’
144 Version 3.22-15 - Feb / 25 / 2010

Select this type to use NMEA messages from a RS232 connection as a position source. To use
the Aux port on the OC50, choose the default COM2 setting. This option is not available in the
FCMS desktop simulation.
Minimum messages required from the NMEA source: **GGA, **VTG and **ZDA
Supported messages: **HDT, **GSV, **GSA, PRDID
Typical setting ‘POS Legacy fibre’

Select this type for ADS40 Control Unit CU40 with POS V4 ONLY.
Version 3.22-15 - Feb / 25 / 2010 145

System configuration: Software
General
Select [Configuration] from the main menu.
Confirm [Next view] to display configuration of parameters Global 1 or Global 2.
Figure 37: Example of main configuration dialog TAB Global 1

The dialog shows an overview of the group Global 1:
- Flight release
- Time Zone
- Installation

The dialog shows an overview of the group Global 2:
- Unit
Use [Up] and [Down] to select another sub-set field.

On the OC52 you can also touch on the area to select another sub-set field.
Select [Return] to open dialog for ‘Save’, ‘Cancel’
146 Version 3.22-15 - Feb / 25 / 2010

Overview configuration of Global 1 parameters

An overview of the parameters in this configuration group is given in Table 16.
Group Sub-Group
Flight & Release Guidance Project
Guidance Approach
Sensor Release Control
Time Zone
Installation
Configuration of ‘Flight Guidance & Sensor Release’
Introduction
During a flight plan controlled flight FCMS calculates the optimal approach from the position of
the aircraft to the start of the line. The user can set various parameters to influence the calcula-
tion. See Figure 39 below. The settings are made in the dialogs described in the following sec-
tions of this paragraph.
Pre-configurations are delivered for different aircraft classes. See Table 17 on Page 148.
Figure 39: Illustration of lateral distances for approach and on the line
Version 3.22-15 - Feb / 25 / 2010 147

Names of pre-configured ‘Flight Release’ configuration sets

These names have been given so as to be self-explanatory according to the conventions listed
below:
Table 17. Naming conventions in pre-configured ‘Flight Release’ sets
Name Description
Slow AC Parameters suitable for aircraft flying at 70 kts to 120 kts
Standard AC Parameters suitable for aircraft flying at 110 kts to 170 kts
Fast AC Parameters suitable for aircraft flying at 150 kts to 250 kts
Very fast AC Parameters suitable for aircraft flying at 200 kts to 400 kts
Flight Release configuration
To enter this dialog from the FCMS main menu proceed as follows:
2. select TAB ‘Global 1’
3. Use [Arrow up] and [Arrow down] to highlight the sub-set ‘Flight Release’
Flight Guidance & Sensors Release configuration is split into the following dialogs selectable in
TABs:
• Guidance Project
• Guidance Approach
• Sensor Release Control
Figure 40: Example of ‘Flight Release Configuration’ dialog
Parameter ‘Flight plan execution’ defines the preferred

flight line sequence for automatic flight line execution by
FCMS. During flight execution the user can any time
interact and override this setting.
Parameter ‘Target height mode’ defines if the lines shall
be flown either at constant ALT MSL or constant ALT
AGL. The latter setting can only be used with ALS50 and
is typically selected for corridor mapping projects.
148 Version 3.22-15 - Feb / 25 / 2010



Configuration of Guidance Project
Figure 41: Example of ‘Guidance Project’ dialog
An explanation of the parameters and settings is given in

Table 18.
Version 3.22-15 - Feb / 25 / 2010 149

Table 18. Parameters ‘Guidance Project’

Flight plan Auto search for During flight execution FCMS suggests the next approach
execution nearest route to the closest line within the project.
Any time the user can any time select a different line or
direction of approach.
Planned During flight execution FCMS suggests the next approach
sequence to the line next in sequence. The sequence is defined in
FPES during flight planning.
The user can any time select a different line or direction of
approach.
Reverse to During flight execution FCMS suggests the next approach
planned to the line next in reverse sequence. The sequence is
sequence defined in FPES during flight planning.
The user can any time select a different line or direction of
approach.
Target height ALT MSL The desired altitude in the Flying altitude control shows
mode an ALT MSL value to maintain a flight at constant flying
height above mean see level. The reference value is
derived from the flight plan.
This mode is typically used for fix wing aircraft. See
Figure 42, “Illustration of target height mode ALT MSL”
in Volume 2, Chapter 4 on Page 151
ALT AGL The desired altitude in the Flying altitude control shows
an ALT MSL value to maintain a flight at constant flying
height above ground level. The reference values are either
taken from the flight plan if a DTM was used. And/or the
reference values are provided by the ALS50. This mode is
typically used with ALS50 for corridor mapping with
Helicopters.
Figure 42, “Illustration of target height mode ALT MSL”
in Volume 2, Chapter 4 on Page 151
150 Version 3.22-15 - Feb / 25 / 2010

Figure 42: Illustration of target height mode ALT MSL
Figure 43: Illustration of target height mode ALT AGL
Important: ALT AGL mode works only if a DTM was used during flight planning in FPES
9.1.5 and /or if an ALS50-II is installed.
Version 3.22-15 - Feb / 25 / 2010 151

Configuration of Guidance Approach
Figure 44: Example of ‘Guidance Approach’ dialog

Table 19.
Figure 45: Illustration of lateral distances for approach and on the line
Figure 46: FCMS control of PAV30/80 stabilization mode
152 Version 3.22-15 - Feb / 25 / 2010

Table 19. Parameters ‘Guidance Approach’

Lateral deviation Typical range If the lateral deviation from the ideal course exceeds the
1000 m to 2500 specified value a new ideal course is calculated from the
m. current position of the aircraft.
See Table 21 The faster the aircraft the larger the distance should be. If
a pilot is not experienced to fly with FCMS flight
guidance, this value should be set to a larger number than
usual.
Illustration of parameter see Figure 45 on Page 152.
Desired bank Typical value FCMS calculates the turns according to the desired bank
angle 15° to 25°, for angle. See section "Turns" in Volume 3, Chapter 2 on
deeply coupled Page 235.
systems U- If the system provides a deeply coupled real-time solution
turns up to 45° a corresponding icon is displayed on the GNSS control.
Short turn / Short turn In this case the last turn is calculated as all other turns
Smooth turn is typically during approach. The desired bank angle is taken for
selected if calculation.
wind is taken
into account
Smooth turn is In this case the last turn is calculated differently than the
typically other turns during approach. The turn starts at the desired
selected if wind bank angle and becomes smoother the closer the IP is. The
is not taken graphic in the view illustrates the smooth turn.
into account A smooth turn allows corrections during final approach
without the danger of exceeding the maximum bank angle.
Switch view Typically 15 Flying time left to the IP along suggested flight when
before IP seconds FCMS switches to the In-line navigation view. The In-line
navigation view allows a more precise final approach.
IP Typically 20 to A certain time (in seconds) ahead of the first release point
(Initial Point) 60 seconds on the flight line, FCMS computes a fictitious IP along the
See Table 21 direction of approach. See illustration in Figure 45 on
Page 152.
PAV IP Typically 10 to A certain time (in seconds) ahead of the first release point
20 seconds. on the flight line, FCMS switches the PAV to operational
See Table 21 mode ON-AUTO. See illustration in Figure 46 on
Page 152.
Wind No (cross) No wind is taken into account to calculate the suggested
flight path.
Set User setting for wind direction and wind speed are taken
into account to calculate the suggested flight path.
Auto Requires GNSS/IMU system! FCMS detects wind
direction and wind speed automatically. The results are
taken into account to calculate the suggested flight path.
Version 3.22-15 - Feb / 25 / 2010 153

Table 19. Parameters ‘Guidance Approach’

Magnetic OFF/True Directions are displayed true north.
variation North
Auto/ Var FCMS applies the magnetic variation for a line by using
Model the US/UK World Magnetic Model for 2005-2010. Details
to the magnetic model see:
http://www.ngdc.noaa.gov/seg/WMM/.
User Def User input of magnetic variation
Configuration of Sensor Release and Control
Figure 47: Example of ‘Sensor Release Control’ dialog

Table 20.
Table 20. Parameters ‘Sensor release control’

Lateral warning Typical value If this lateral distance is exceeded when flying along the
75 m - 150 m line, the aircraft points to the grey warning bar in the line
See Table 21 deviation control which is displayed on the In-line
navigation view. See illustration in Figure 45 on
Page 152.
Lateral release Typical value If the specified permissible lateral deviation is exceeded
shut-off 200 m - 400m when flying along a line, the aircraft points to the solid bar
See Table 21 in the line deviation control which is displayed on the In-
line navigation view.
The sensor release is blocked. No image data will be
recorded as long as the deviation is exceeded.
See illustration in Figure 45 on Page 152.
Vertical warning Typical value If this vertical distance is exceeded, the actual altitude is
100 m displayed in the area of one of the grey warning bars
which are displayed on the Flying altitude control.
154 Version 3.22-15 - Feb / 25 / 2010

Table 20. Parameters ‘Sensor release control’

Vertical release Typical value If this vertical distance is exceeded, the actual altitude is
shut off 300 m displayed in the area of one of the black bars which are
displayed on the Flying altitude control.
The sensor release is blocked. No image data will be
recorded as long as the deviation is exceeded.
Safety factor in Typical value If only a missed part in a flight line is repeated FCMS
repeat 1 to 3 extends for the re-flight the repeated segment of the line.
This is to avoid data gaps. The safety factor is used to
adjust the overlap of the line segment. The larger the
safety factor the longer the overlapping section of the line
segments.
Sensor release Auto In mode ‘Auto’ the Sensor is released according to the
mode events defined in the flight planning.
Inactive In mode ‘Inactive’ all planned release events are
suppressed. The Sensor configuration is set according to
the flight planning or to user actions.
If the user toggles the mode back to ‘Auto’ on an
observation period, image data recording starts until the
end of the observation period or until the sensor mode is
reset to ‘inactive’.
Mount AUTO In this mode FCMS controls the stabilization mode of the
(PAV30/80) mount by software commands during project execution.
control mode FCMS commands the PAV to switch OFF stabilization
during approach and turns. FCMS commands the PAV to
switch ON stabilization when flying along a flight line
from the point defined by the parameter ‘PAV
initialization time’ till the end of the flight line. See
illustration in Figure 46 on Page 152.
ON-AUTO This setting is to override FCMS. The PAV stabilization is
switched ON during the entire flight. A warning message
will be displayed in the status line.
OFF- This setting is to override FCMS. The PAV stabilization is
MANUAL switched OFF during the entire flight. A warning
message will be displayed in the status line.
Important: The PAV30 stabilization mode has to be set to ON-AUTO on the PAV30 operator
panel. Only if the PAV30 is in this state FCMS can control by SW commands the PAV30 stabili-
zation mode.
Version 3.22-15 - Feb / 25 / 2010 155

Summary of Flight Guidance & Sensor Release settings

Table 21. Typical configuration settings for various aircraft types
Parameter Parameter Slow aircraft Standard Fast Very fast

Group aircraft aircraft aircraft
Guidance Flight plan Auto search Auto search Auto search Auto search
Project execution for nearest for nearest for nearest for nearest
route route route route
Guidance Lateral warning 1000 m 1250 m 1500 m 2500 m
Approach
Desired bank 22 ° 22 ° 22 ° 22 °
Turn smooth smooth smooth short
Switch view 20 sec 20 sec 20 sec 20 sec

before IP
IP 25 sec 30 sec 40 sec 60 sec
PAV IP 15 sec 15 sec 20 sec 20 sec
Wind No No No No
Sensor Lateral warning 75 m 75 m 100 m 150 m

release
control Lateral release 200 m 250 m 300 m 400 m
shut off
Vertical warning 100 m 100 m 100 m 100 m
Vertical release 300 m 300 m 300 m 300 m

shut off
Safety factor in 2x 2x 2x 2x
repeat
Sensor release AUTO AUTO AUTO AUTO

mode
PAV operational AUTO AUTO AUTO AUTO

mode
Note: The parameter ‘desired bank angle’ is used by FCMS to compute the radius in the turn
sections of the suggested flight path. If the aircraft is flown with a bank angle equal to the
‘desired bank angle’ the FCMS turn radius matches with the aircraft’s turn radius. Wether the
turn radius matches in a real flight depends on the aerodynamic characteristics of the aircraft. If
the turn radius does not match, adjust in the FCMS configuration the desired bank angle. To
adjust, increase or decrease the value until the turn radius flown with the aircraft at desired bank
angle is coincident with the flight path suggested by FCMS.
156 Version 3.22-15 - Feb / 25 / 2010

Configuration of parameter ‘Time zone’
2. select TAB ‘Global 1’
3. Use [Arrow up] and [Arrow down] to highlight the sub-set ‘Time Zone’
All time zones are pre-defined.

Daylight saving is handled by the operating system.
Figure 49: Example of Time Zone dialog
Select Configuration to display a time zone graphic. This

is for information purposes only. No user settings can be
made in this dialog.
Select [Return] to close dialog
Version 3.22-15 - Feb / 25 / 2010 157

Configuration of parameter ‘Installation’

Important: Store the installation parameter with a unique name to reduce mistakes. Use the
aircraft registration number (also called tail number) as a name to save the installation param-
eters.
2. change view to ‘Global 1’
3. Use [Arrow up] and [Arrow down] to highlight the sub-set ‘Installation’
Use [Previous Configuration set] or [Next Configuration Set] to select one of the records stored
in the configuration data base.
If the record matches:

If no desired configuration is stored in the configuration database proceed with the next para-
graph.
Configuration if the IMU type is pre-defined for the Sensor

Important: If the sensor is installed 180° opposite to the flight direction make all settings
according to this paragraph and make additionally settings according to section "Configuration if
the sensor is installed 180° opposite to the flight direction" in Volume 2, Chapter 4 on Page 160.
Select [Configuration] to enter ‘Installation Parameter’ dialog to edit the current record or to cre-
ate a new record.
Figure 50: Example of ‘System Installation Parameters’ dialog
In this dialog the following parameters are defined:

• IMU type. For not pre-defined IMU types see section
"Configuration if IMU type is not pre-defined for the
Sensor Head" in Volume 2, Chapter 4 on Page 159.
• Offset Reference to GNSS antenna as measured for
the sensor system.
• Aircraft identifier and the minimum and the maxi-
mum aircraft speed.
158 Version 3.22-15 - Feb / 25 / 2010

Select [+] buttons to increment value.



Use the aircraft registration number (also called tail number) as a name to save the installation
parameters.
Configuration if IMU type is not pre-defined for the Sensor Head

Caution: Only make settings in the advanced system installation parameter dialog if the IMU
type is not pre-defined in the FCMS database or if the sensor is not installed such that the sensor
coordinate system ist perfectely aligned with the aircraft coordinate system.
Use [Manual Configuration] to enter advanced installation parameter dialog.
Figure 51: Example of ‘Advanced System Installation Parameters’ dialog

• Offset Reference to GNSS antenna. This is the same
offset as in dialog Figure 50.
• Offset Reference to IMU. The offset depends on the
IMU type and Sensor head type. See Table 22 below.
• Rotation Reference to aircraft. For standard installa-
tions the values are Zero.
• Rotation Reference to IMU. This depends on the
IMU mounting. Average accuracy is sufficient. High
Origin of the reference as well as the accurate rotation parameters are applied in the
orientation of the axis are shown in the
GNSS/IMU data post -processing step.
illustration placed in the lower part of
the view.
Table 22. Offsets Reference to IMU
IMU type Offset x Offset y Offset z Rotation ω Rotation ϕ Rotation κ

User def. Contact Leica Geosystems Airborne Sensor Customer Support
Version 3.22-15 - Feb / 25 / 2010 159

Configuration if the sensor is installed 180° opposite to the flight direction

Caution: Only make settings in the advanced system installation parameter dialog if the IMU
type is not pre-defined in the FCMS database or if the sensor is not installed such that the sensor
coordinate system ist perfectely aligned with the aircraft coordinate system.
Use [Manual Configuration] to enter advanced installation parameter dialog.
Figure 52: Example of ‘Advanced System Installation Parameters’ dialog

• Offset Reference to GNSS antenna. This is the same
offset as in dialog Figure 50.
• Offset Reference to IMU. The offset depends on the
IMU type and Sensor head type. See Table 22 below.
• Rotation Reference to aircraft. If the sensor is
installed 180° opposite to the flight direction the
Kappa value has to be set to 180°
• Rotation Reference to IMU. This depends on the
Origin of the reference as well as the IMU mounting. Average accuracy is sufficient. High
orientation of the axis are shown in the accurate rotation parameters are applied in the
illustration placed in the lower part of
GNSS/IMU data post -processing step.
the view.
Figure 53: Example of ‘Reference to Aircraft’ settings
Kappa has to be set to 180° if the sensor is installed

opposite to the flight direction.
Overview configuration of Global 2 parameters

An overview of the parameters in this configuration group is given in Table 23.
Group Remarks
Units Predefined sets with definition of units for operator and pilot
Views User definable default views for operator and pilot
160 Version 3.22-15 - Feb / 25 / 2010

Configuration of global parameters ‘Units’
3. Use [Arrow up] and [Arrow down] to highlight the sub-set ‘Units’
If the set matches:

Table 24. Predefined unit configuration sets
Version 3.22-15 - Feb / 25 / 2010 161

Configuration of global parameters ‘Views’
3. Use [Arrow up] and [Arrow down] to highlight the sub-set ‘Views’
If the set matches:

If no desired configuration is stored in the configuration database:

Select [Configuration] to enter ‘View Configuration’ dialog to edit the current record or to create
a new record.
Figure 54: Example of ‘View configuration’ dialog
In this dialog the following can be set independently for

the operator and the pilot:
- default view during approaches and turns
- default view on the line
Check ‘Optimized for the pilot’ to activate simplified

controls and toolbar for the pilot. If this option is checked
the pilot’s access to FCMS is limited to flight guidance
related configuration and operation only.
Use [Tab Left] [Tab Right] to move the focus to the desired view.
Select [+] to check the desired view per group.
162 Version 3.22-15 - Feb / 25 / 2010

Configuration ‘Advanced’
2. change view to TAB ‘Advanced’
Figure 55: Example of ‘Global Advanced’ dialog
In this dialog advanced configurations can be made. Do

only make settings according to instruction given by the
Leica Geosystems Customer support.
Use [Arrow Up] or [Arrow down] to set the focus to ‘ALS connection to ADS’
Select [+] or [-] to enable the desired COM line
Table 25. Parameters ‘Advanced’

Release signals Enable ‘Enabled’ by default
from FCMS to Disable Leica Geosystems Customer Support will inform if this
IPAS feature shall be disabled.
Extended status Enable ‘Disabled’ by default
logging Disable Leica Geosystems Customer Support will inform if this
feature shall be enabled.
Display GNSS Enable ‘Enabled’ by default
error message Disable If disabled GNSS error messages will only be displayed in
window the status line.
Beta features Enable ‘Disabled’ by default
Disable Do only enable this feature if you have signed a Beta test
agreement with Leica Geosystems.
Version 3.22-15 - Feb / 25 / 2010 163

164 Version 3.22-15 - Feb / 25 / 2010

Chapter 5 FCMS - Flight Execution
Version 3.22-15 Feb / 25 / 2010 165

Basic layout of navigation view during flight execution
Views
Different views can be selected during flight execution. See section "Views during flight execu-
tion" in Volume 2, Chapter 5 on Page 194. The views are composed of controls.
Controls
What is a control
A control is an area on a view which shows data relevant during flight execution
• System controls
Information about the hardware like Sensor, Memory, GNSS etc.
• Flight guidance controls
Information to navigate.
• General controls
Information about the project, Zoom factor of graphic displays etc.
Figure 56: Controls on the navigation views
Figure 57: Controls on the 3-D navigation view
166 Version 3.22-15 - Feb / 25 / 2010

For details see:

Project control see section "Project control" in Volume 2, Chapter 5 on Page 189
Sensor control see section "Sensor control" in Volume 2, Chapter 5 on Page 168
Project progress control section "Project progress control" in Volume 2, Chapter 5 on Page 190
Memory control see section "Memory control" in Volume 2, Chapter 5 on Page 170
GNSS control see section "GNSS control" in Volume 2, Chapter 5 on Page 170
Wind control, Track and line direction control, Position control see section "Views during
flight execution" in Volume 2, Chapter 5 on Page 194
Nose-up navigation control, North-up navigation control, In-line navigation control and 3-
D Navigation control section "Views during flight execution" in Volume 2, Chapter 5 on Page
194
Flying altitude control see section "Flying altitude control" in Volume 2, Chapter 5 on Page 183
Aircraft to target control see section "Views during flight execution" in Volume 2, Chapter 5 on
Page 194
Line progress control see section "Views during flight execution" in Volume 2, Chapter 5 on
Page 194
Speed control see section "Speed control" in Volume 2, Chapter 5 on Page 187
Figure 58: Controls on the in-flight evaluation views
For details see:

Project control see section "Project control" in Volume 2, Chapter 5 on Page 189
Project progress control section "Project progress control" in Volume 2, Chapter 5 on Page 190
Data filter control see section "Data filter control" in Volume 2, Chapter 5 on Page 190
Line detail control see section "Line detail control" in Volume 2, Chapter 5 on Page 191
Project area control see section "Project area control" in Volume 2, Chapter 5 on Page 190
Graphic in-flight evaluation control see section "Graphic in-flight evaluation control" in Vol-
ume 2, Chapter 5 on Page 192
Alphanumeric in-flight evaluation control see section "Alphanumeric in-flight evaluation con-
trol" in Volume 2, Chapter 5 on Page 193
Version 3.22-15 - Feb / 25 / 2010 167

System controls
Take-Off control
The Take-Off control gives information about the status of the system during start-up, whether it
is ready or not for take off.
Figure 59: Example of Take-Off control
As long as the system is not ready for the flight an hour glass
symbol is displayed on the upper right side of the control.
The hour glass is replaced by a check mark symbol if all
components of the system are ready. After remaining in this state
for a few seconds the Take-Off control is replaced by the Sensor
Head control.
Sensor control
The Sensor control gives information about the sensor system if the data are provided by the sen-
sor to FCMS.
A large red spot flashes on the upper right side of the control display if sensor data are being
recorded to the Memory.
Sensor control for Generic Sensor
Figure 60: Examples of Sensor control for Generic Sensor
Image data are not being recorded.

The control appears like this during approach to a flight line.
Image data are being recorded.

The control appears like this while on the fight line.
Sensor control for Leica RC30
Figure 61: Example of Sensor control for Leica RC30
In case of the RC30 connected to the RCIF30 the camera

counter, the shutter speed and the aperture are displayed.
168 Version 3.22-15 - Feb / 25 / 2010

Sensor control for Leica ALS50/60
Figure 62: Examples of Sensor control for Leica ALS60
Example: during approach

Actual Laser Pulse rate is 158 kHz
Actual Laser current is 57%
Actual Scan rate is 52 Hz
Field of view is 40°
MPiA option is OFF
• only one vertical arrow displayed
The laser is fired
• Laser warning symbol is displayed
The shutter is closed
• vertical arrow is displayed with red borders
Example: during approach
MPiA option is ON:
• two vertical arrows are displayed
Example after IP
Shutter is open:
• vertical arrows are displayed in solid red
• Laser warning symbol is blinking
Example along the line

Data recording is ON:
• Red blinking dot.
Figure 63: Example of Sensor control for height information for ALS60
Example during approach

Minimum range is 1139 m
Eye safety binocular is 1279 m
Maximum range is 1464 m
Example along the line

ALT AGL 839 m
Distance from minimum height to minimum range is 90 m
Distance from maximum height to maximum range is 97 m
Version 3.22-15 - Feb / 25 / 2010 169

Memory control
The memory control graphically displays the usage rate of the memory. The two lines on the
upper right display numerical information about available FCMS disk space. The two lines on
the lower right display numerical information about available Mass Memory disk space if the
information is available.
Note: FCMS can only display the data storage information of the mass memory of the sensor
system if the sensor system provides this data to FCMS.
Figure 64: Example of Memory control
60 GB of data are left FCMS memory device.

121 GB of data are used on the FCMS memory device.
3.1 GB of data are left on the sensor mass memory.

171.96 of data are stored on the sensor mass memory.
GNSS control
The GNSS control shows status of the GNSS receiver, the number of satellites in view and the
HDOP and PDOP value
Figure 65: Example of GNSS control
Navigation mode is in 3D quality

Currently 8 satellites are in view
PDOP is 2.1
Pitch and Roll is given for the sensor’s aircraft frame
If the aircraft rolls from horizontal counter-clockwise the roll value becomes negative.
If the aircraft nose is lower than level the pitch value is negative.
The warning symbol displayed on the lower left side indicates

that the GNSS/IMU system is not yet in mode ‘Full Navigation’.
The ‘deeply coupled’ symbol appears on the lower left indicates

that the GNSS/IMU hardware is capable to provide for
navigation a deeply coupled real-time solution..
170 Version 3.22-15 - Feb / 25 / 2010

Flight guidance controls
General
An overview of the location of the controls on the views is given in Figure , “Basic layout of nav-
igation view during flight execution” in Volume 2, Chapter 5 on Page 166
Color codes
Information displayed on different controls but related to each other is shown in the same color
Table 26. Color codes in the flight guidance controls
Color Relationship Examples

Red Information • Line direction is displayed in a red frame
about the actual
• Target GS is displayed in a red frame
line
• Desired altitude is displayed in a red frame
• In the graphics the line in execution is displayed solid red
Cyan Information • Actual track is displayed in a cyan frame

about the
aircraft
• Target GS is displayed on cyan background
• Desired altitude is displayed on cyan background
Blue Information • Suggested flight path is displayed in blue

about the line to
be flown next
• Line length is displayed in blue font
• Execution time of the line is displayed in blue font
• The bearing to the next line is displayed in a blue frame.
• In the graphics the next line is displayed solid blue
Table 27. Color codes in the graphical presentation showing the line status
Line Status Line label Line representation

North-up view Nose-up view In-flight eval.
Successfully flown Green Dotted grey line Green line
Flown with warnings Orange Dotted grey line Warning part

orange
Flown with errors Red Dotted grey line Warning part red
Flown but user set Black Thin black line Not recorded part
recording OFF thick black
Not yet flown Black Thin black line Thin black line
Next line Blue Thick blue line Thick blue line
Line in execution Red Thick red line Thick red line
Version 3.22-15 - Feb / 25 / 2010 171

Wind control
The wind control shows wind direction and wind speed
Note: The wind control is only displayed if FCMS is configured to take wind into account.
Configuration see section "Configuration of Guidance Approach" in Volume 2, Chapter 4 on
Page 152.
The wind direction is defined according to definitions in weather reports.
The yellow background indicates user setting of the parameters
Wind direction is 176° (Wind is coming from West)
Wind speed is 14 kts
The grey background indicates automatic wind detection by FCMS.

The red triangle indicates the wind direction relative to the aircraft.
The aircraft is slightly rotated to the left. The rotation angle is equal the angle
between the aircraft’s heading and the aircraft’s track.
Note: If the wind Icon is displayed without any numbers, there’s either too little wind or FCMS
needs more time to complete the wind direction or wind speed calculation.
Track and line direction control

The track and line direction control shows actual track in a cyan frame and the line direction in a
red frame.
Important: A flight line must be selected that the line direction control can display infor-
mation. For a non-planned line only the track information is displayed.
Important: All directions are in true north by default.
Shown in cyan frame: actual track 031.1°
Shown in red frame: line direction 026.1°
Track and line direction are displayed in True North
The horse shoe symbol displayed on the left side of each frame
indicates that track and line direction are displayed with
magnetic variation.
172 Version 3.22-15 - Feb / 25 / 2010

Track deviation control

The track deviation control shows the aircraft’s deviation from the suggested flight path. Units
are shown in the control.
Important: A flight line must be selected previously so that track deviation can display infor-
mation.
The aircraft position is about 1,000 m

left of the suggested flight path.
The aircraft position is perfectly on
the suggested flight path
The aircraft position is about 500 m
right of the suggested flight path.
Configuration of the track deviation control see section "Configuration of Guidance Approach"
in Volume 2, Chapter 4 on Page 152.
Position control
The position control shows actual position in WGS84, Sun elevation and time in UTC.
Version 3.22-15 - Feb / 25 / 2010 173

North-up navigation control

This control is the key element of the North-up view. See section "North-up view" in Volume 2,
Chapter 5 on Page 202. The examples below show the North-up control surrounded by the wind
control, the track and line direction control, the track deviation control and the position control.
Figure 66: Example of North-up navigation control
This control displays a project overview in North-up

orientation. Flight guidance information is optimized for
approaches and turns. The example on the left shows the
control during approach to the line.
The detail below shows the suggested approach to the IP.
The line approach is opposite to the planned direction.
The example on the left shows the control during line

execution. The next line (blue) is already pre-selected.
The detail below shows the aircraft along the line (red),
the suggested flight path to the next line which will be
approached in the planned direction.
The line direction according to the flight planning is indicated by a fork at the starting point of a
line. The line label is displayed at the same side of the line. The examples above show, that a line
can be flown in either direction, as planned or in the opposite direction.
174 Version 3.22-15 - Feb / 25 / 2010

Nose-up navigation control

This control is the key element of the Nose-up view. See section "Nose-up view" in Volume 2,
Chapter 5 on Page 201. The examples below show the Nose-up navigation control surrounded by
the wind control, the track and line direction control, the track deviation control and the position
control.
Figure 67: Example of Nose-up navigation control
This control is optimized for the pilot. It provides graphic

flight guidance information during approaches and turns.
The orientation is Nose-up. North direction is indicated
on the lower right corner of the control.
The example on the left shows the aircraft position on the

right side of the optimal approach path. The lateral
deviation is about 400m.
The optimum approach path will require a right turn. The
aircraft is already close to that turn. A cross bar indicates
the transition point from the straight flight path to the turn
part of the optimum approach.
The pilot should start the turn just before the cross bar
passes the nose of the aircraft icon.
The example on the left shows the aircraft already close to

the IP. The aircraft position is on the right side of the
optimum flight path. The lateral deviation is about 100 m.
A fictive line is displayed in thin blue. This is the

extension of the flight line towards IP and approach. This
line is an aid for the pilot during the final approach to the
IP. It allows to identify whether the aircraft is on the left
side or right side of the line.
The example on the left shows the nose-up navigation

control with the track deviation control.
The aircraft flies perfectly along the suggested flight path.

The track deviation control shows no lateral deviation.
Version 3.22-15 - Feb / 25 / 2010 175

Line deviation control

The line deviation control shows the lateral deviation of the line from the aircraft’s actual posi-
tion. Units are shown in the control. This control is part of the in-line navigation control. For
more information see section "In-line navigation control" in Volume 2, Chapter 5 on Page 176.
Important: A flight line must be selected previously so that the line deviation control can
display information.
The deviation is -22m

Seen from the aircraft position the
line is 22m on the right side.
Seen from the planned line position,
the aircraft is 22m on the left side.
Configuration of the line deviation control see section "Configuration of Sensor Release and
Control" in Volume 2, Chapter 4 on Page 154.
In-line navigation control

This control is the key element of the In-line view. See section "In-line view" in Volume 2, Chap-
ter 5 on Page 204. The examples below show the In-line navigation control surrounded by the
wind control, the track and line direction control and the position control. The line deviation con-
trol is incorporated.
The in-line navigation control is optimized for the pilot. It provides graphic flight guidance infor-
mation during line execution.
Figure 68: Example of In-line navigation control
Any sensor. PAV30/80 installed.
The example on the left shows the aircraft position just

before reaching the IP. Also the PAV IP is just ahead in
time.
The red line with the circle shows relative position and
direction of the line to be executed.
The planned line is about 60 m to the right side of the

aircraft’s position. The offset is still tolerable. It is in the
‘white’ range.
The difference of true track and line direction is about
2.6°.
176 Version 3.22-15 - Feb / 25 / 2010

Figure 69: Example of In-line navigation control for any sensor
The example on the left shows a typical final approach to

the line. The aircraft is flying the final turn to the IP.
The line is about 188 m to the left side of the aircraft. The
offset is in the warning range.
The difference between the true track and the line

direction is 20.5°.
The example to the left shows the approach to the line

with a large lateral offset.
The line is about 882 m on the left side of the aircraft. The
offset is in the release shut-off range.
The difference between the true track and the line

direction is 38.6°.
The example on the left shows the approach to the line if

the line direction is opposite to the current track.
The line is about 3147 m to the right side of the aircraft.
The relative position of the line to the aircraft is shown in

the Aircraft to target control. See “” on Page 183.
Version 3.22-15 - Feb / 25 / 2010 177

Figure 72: Example of In-line navigation control for frame sensor
The example on the left shows the photo release point

along the line.
The planned line is about 62 m to the right side of the

aircraft’s position. The offset is still tolerable. It is in the
‘white’ range.
The difference of true track and line direction is about

1.4°.
178 Version 3.22-15 - Feb / 25 / 2010

3-D Navigation control

This control is the key element of the 3-D Navigation view. It provides graphic and numeric
information for flight guidance. See section "3-D Navigation control" in Volume 2, Chapter 5 on
Page 179.
Figure 73: Layout of the 3D navigation control
Bank indicator and Pitch indicator: display of

information provided by the IPAS system.
Track and line deviation indicator
During approached and turns: displays the
deviation from the suggested flight path.
Along the line: displays the deviation to the line.
Height deviation indicator: displays desired
ALT MSL. Similar as the flying altitude control
Ground speed indicator: displays the actual
and target GS. Similar as the speed control.
Important: Bank and pitch indicator are only displayed if the IPAS system is in the mode 'Full
Navigation'. If the sensor mount is installed with an attitude angle, the pitch information will be
different to the aircraft's pitch.
3-D Navigation control during approach

During this phase of the photo flight the control appears mainly in blue color. The target dot is
displayed in blue as well.
Figure 74: Example 1 of ‘3-D Navigation’ control during approach and turns
• The 3D line indicator (tunnel) appears

symmetrically. This is the case if the
approach direction is a straight line
• The ground speed indicator shows a GS of
156 kts.
• The bank indicator show a roll angle of
zero.
• The pitch indicator shows a pitch value of
zero.
• The track and line deviation indicator shows a deviation of +2m. The value is displayed on
white background which indicates that the deviation can be ignored. The limit can be con-
figured in FCMS.
• The height deviation indicator shows a deviation of 0 ft. This is the case if the aircraft is fly-
ing at desired altitude. The value is displayed on white background. This is the case if the
deviation can be ignored.
Version 3.22-15 - Feb / 25 / 2010 179

Figure 75: Example 2 of ‘3-D Navigation’ control during approach and turns
• The 3D line indicator appears as a tube

turned to the right side. This is the case if
the aircraft should fly a right turn during
the approach. The turn will end if the air-
craft's heading is 271°.
• The ground speed indicator shows a GS of
111 kts.
• The bank indicator displays a roll angle of
zero.
• The pitch indicator displays a pitch angle of zero. The aircraft is levelled.
• The track and line deviation indicator shows a deviation of -8m. The value is displayed on
figured in FCMS.
• The height deviation indicator shows a deviation of -427ft. The value is displayed on grey
background which indicates that the deviation should be corrected. The limit can be config-
ured in FCMS.
Figure 76: Example3 of ‘3-D Navigation’ control during approach and turns
• The 3D line indicator appears as a tube

turned to the left side. This is the case if the
aircraft should fly a left turn during the
approach. The turn will end if the aircraft's
heading is 257°.
• The ground speed indicator shows a target
GS of 180 kts and a aircraft GS of 175 kts.
about -14°. The aircraft is turning left.
• The pitch indicator displays a pitch angle of about +4°. The aircraft is climbing.
• The track and line deviation indicator shows a deviation of +246m. The value is displayed
on white background which indicates that the deviation can be ignored. The limit can be
configured in FCMS.
• The height deviation indicator shows a deviation of -627ft. The value is displayed on grey
background which indicates that the deviation should be corrected. The limit can be config-
ured in FCMS.
180 Version 3.22-15 - Feb / 25 / 2010

3-D Navigation control along the line

During this phase of the photo flight the control appears mainly in grey/black color. The target
dot is displayed in black and if recording is ON it is displayed in red.
Figure 77: Example 1 of ‘3-D Navigation’ control along the line
• The 3D line indicator (tube) appears sym-

metrically. This is the case if the planned
flight line is a straight line.
• The height deviation indicator shows a
deviation of 0 ft. White background indi-
cates that the deviation can be ignored.
Grey background indicates that the devia-
tion should be corrected. Black back-
ground indicates that it is out of limit. The
limits can be configured in FCMS.
• The bank indicator displays a roll angle of 0°.

• The pitch indicator displays a pitch angle of 0°.
• The aircraft is on the final approach to the line. The sensor is not recording. The target dot is
displayed in black.
• The track and line deviation indicator shows a deviation of +1m. The value is displayed on
figured in FCMS.
• The ground speed indicator shows an aircraft GS of 201 kts.
Figure 78: Example 2 of ‘3-D Navigation’ control along the line
• The 3D line indicator appears twisted to

the left. This is the case if the aircraft track
is not aligned with the line direction.
• The ground speed indicator shows an air-
craft GS of 125 kts.
• The track correction would be 3.6° to the
left.
• The pitch indicator displays a pitch angle
of 0°.
• The bank indicator displays a roll angle of 0°.

• The sensor is recording. The target dot is displayed in red.
• The track and line deviation indicator shows a deviation of -17m. The value is displayed on
figured in FCMS.
• The height deviation indicator shows a deviation of -427 ft. Grey background indicates that
the deviation should be corrected. The limits can be configured in FCMS.
Version 3.22-15 - Feb / 25 / 2010 181

Figure 79: Example3 of ‘3-D Navigation’ control along the line
• The 3D line indicator appears twisted to

the left. This is the case if the aircraft track
is not aligned with the line direction.
• The ground speed indicator shows a target
GS of 180 kts and an aircraft GS of 175
kts.
• The track correction should be 2.2° to the
left.
about +3°.
• The sensor is recording. The target dot is displayed in red.

• The pitch indicator displays a pitch angle of about +2°.
• The track and line deviation indicator shows a deviation of +6 m. The value is displayed on
figured in FCMS.
• The height deviation indicator shows a deviation of -326 ft. White background indicates that
the deviation can be ignored. The limits can be configured in FCMS.
182 Version 3.22-15 - Feb / 25 / 2010

Flying altitude control

Important: The flying altitude control shows as desired altitude ALT MSL regardless of the
target height mode configuration. See section "Configuration of Guidance Project" in Volume 2,
Important: All altitude data are referenced to ellipsoidal height WGS84.
The desired altitude is taken from the flight plan. In case of manual operation of the ADS40 it is
taken from the Height, Altitude and GSD configuration.
The flying altitude control shows the desired altitude in a red frame. The background color
depends on the target Height mode configuration. In case of ALT MSL the background color is
yellow. In case of ALT AGL the background color is grey.
The actual altitude is shown on a cyan background. The actual altitude source depends on the tar-
get Height mode configuration. In case of ALT MSL the source is the GNSS. The mode ALT
AGL is implemented as option for the Leica ALS60. In this case the source is the ALS60 LIDAR
data.
The difference between the desired and actual altitude is shown in black. The vertical bar in the
center of the control indicates in grey the vertical warning and in black the vertical release shut-
off range. See configuration in section "Configuration of Sensor Release and Control" in Volume
2, Chapter 4 on Page 154.
Figure 80: Example of Flying altitude control
Actual flying altitude is 3,940 ft.

Desired flying altitude is 6,490 ft. (ALT MSL)
The aircraft should climb 2,550 ft.
The aircraft altitude indicator points to the black range. That is,
the aircraft is flying outside the specified vertical sensor release
range.
Actual flying altitude is 6,890 ft.

Desired flying altitude is 6,490 ft. (ALD AGL)
The aircraft should descend 400 ft.
The aircraft altitude indicator points to the white range. That is,
the aircraft is flying within the specified sensor release tolerance.
Version 3.22-15 - Feb / 25 / 2010 183

Aircraft to target control

This control shows the relative position of the next line to the aircraft.
The information displayed depends on the line status:

• If no line is selected the control displays no information.
• If a line is selected the information is displayed as given in Figure 81 below.
• If the IP is passed the information given in the control is valid for the pre-selected next line.
Figure 81: Example of Aircraft to target control
The orientation is Nose-up.

North direction is indicated in the upper right section.
The relative position of the IP to the aircraft and the Line

direction relative to the aircraft is graphically displayed.
The x- and y-offsets to the IP are numerically displayed.
The Bearing to the IP is displayed in degrees.
Line progress control

Note: A flight line must be selected that the line progress control can display full information.
For a non-planned line the line progress control shows only limited information.
The line progress control provides information about progress in line execution. The information
is color coded. See also section "Color codes in the flight guidance controls" in Volume 2, Chap-
ter 5 on Page 171.
Note: FCMS can be configured to display the Line progress control optimized for the pilot. In
this case only the time and the distance to IP or line start respectively and the time and distance
to the line end will be displayed. How to configure see section "Configuration of global param-
eters ‘Units’" in Volume 2, Chapter 4 on Page 161.
Figure 82: Example of Line progress control. Aircraft position before IP
Red: Time required to fly from current position along the

suggested flight path to the end of the line. Length of suggested
flight path.
Blue: Time needed to fly at current GS along the line. Line
length.
Magenta: Required memory space for data acquisition on the
line.
Black: Time required to fly from current position along the
suggested flight path to the IP. Length of suggested flight path.
184 Version 3.22-15 - Feb / 25 / 2010

Figure 83: Example of Line progress control. Aircraft position before IP
Red: Time required to fly from current position along the

suggested flight path to the end of the line. Length of suggested
flight path.
Blue: Time needed to fly at current GS along the line. Line
length.
Red: Number of frames to be taken on the line.
Figure 84: Example of Line progress control. Aircraft position between IP and line start
Red: Time required to fly from current position to the end of the
line. Distance from current position to the end of the line.
Magenta: Required memory space for data acquisition on the
line.
Cyan triangle: Indicates aircraft position before IP.
Figure 85: Example of Line progress control. Aircraft position between line start and line end
line. Distance from current position to the end of the line.
Black: Time and distance already flown along the line.

Magenta: Remaining memory space required for data
acquisition on the line.
Black: Amount of data recorded along the line.
Cyan triangle: Indicates aircraft position along the line.
Figure 86: Example of Line progress control. Aircraft position between line start and line end
line. Distance form current position to the end of the line.
Black: Time and distance already flown along the line.
Red: Remaining frames to complete the line.

Black: Amount of frames taken along the line.
Cyan triangle: Indicates aircraft position along the line.
Version 3.22-15 - Feb / 25 / 2010 185

Figure 87: Example of Line progress control. No Flight line selected
No information displayed because no line is selected.
Figure 88: Example of Line progress control. No flight line, manual release
Black: Time and distance flown since release start.
Black: Amount of data recorded since release start.
186 Version 3.22-15 - Feb / 25 / 2010

Speed control
Note: The speed control appears different by depending on the sensor type configured in
FCMS.
Speed control for ALS60 or a multi-sensor system ‘ALS60+Frame’

In this configuration the speed control displays the actual GS and the target GS.
Figure 89: Examples of speed control for ALS or ‘ALS+Frame’l
Either no line is selected or Actual GS is 156 kts

the planning was not made Target speed is not known
by using FPES 9.1.5 or later
Line is selected, the aircraft Actual GS is 120 kts

is approaching the line Target speed is 130 kts
Line is selected, the aircraft The green check mark

is flying along the line indicates that the actual GS is
either slower or within the
range of +10 % to target GS
of 130 kts.
Line is selected, the aircraft A parachute indicates that the
is flying along the line actual GS is within +10 % and
the warning limit for GS.
Line is selected, the aircraft Warning: Actual GS exceeds

is flying along the line the limit for GS.
The GS is more than +20%
too fast.
Speed control for generic line sensor

In this configuration the speed control displays only the actual GS. Target GS is not known.
Figure 90: Examples of speed control for generic line sensor
In all cases Actual GS is 156 kts

Target speed is not known
Version 3.22-15 - Feb / 25 / 2010 187

Speed control for frame sensor

In this configuration the speed control displays the actual GS and the maximum GS. The maxi-
mum GS is computed in-flight by FCMS based on the shortest base length on a line and the sen-
sor cycle time defined in FCMS sensor configuration. Make sure the sensor cycle time is
configured correctly. See section "Sensor configuration parameters" in Volume 2, Chapter 4 on
Page 133
Important: To avoid lost photographs along the line do not exceed the maximum GS
Note: Depending on the aircraft type and the GSD of the photographs, the indicated maximum
GS can be faster than the aircraft is able to fly. The indicated maximum GS just gives the GS
limit which shall not be exceeded. With a frame sensors it is always possible without restrictions
to fly along the line slower than the maximum GS.
Figure 91: Examples of speed control for frame sensor
Line is selected, the aircraft Actual GS is 120 kts

is approaching the line Maximum speed is 130 kts
Line is selected, the aircraft The green check mark

is flying along the line indicates that the actual GS is
less than 90% of the
maximum GS of 210 kts.
Line is selected, the aircraft A parachute indicates that the
is flying along the line actual GS which is 150 kts is
within 90% and 99 % of the
maximum GS which is 158kts
Line is selected, the aircraft Warning: Actual GS of 154
is flying along the line kts exceeds the limit for GS
which is 151 kts.
188 Version 3.22-15 - Feb / 25 / 2010

Controls with project related information
Project control

The project control gives an overview which Project, which Flight Plan of the Project and which
Flight Line of the Flight Plan is selected to be flown.
Also the number of the flight execution for the selected project is shown.
Figure 92: Example of Project control
The project name is St.Gallen

The flight plan name is Rheintal-E
The line label is REA001
The line number is 027
The project St.Gallen is flown the 2nd time: Flight number 002
If during a flight plan controlled flight the sensor is manually released by the user, FCMS adds to
the project a non-planned flight plan to store the manually released flight line.
Manually controlled flight

This is the case if no Project is selected. If the sensor is released either manually or externally by
ASCOT, FCMS stores the release information in a dummy project. For each ‘Flight’ such a
dummy project is created by FCMS. It stores information about all manually released flight lines
taken during the period of start Flight till quit Flight.
The name of the unplanned project is generated in the format: YearMonthDayHHMMSS

A dummy planning consists of a 'non-planned Project' with a ‘Non-planned Flight Plan’. Each
release sequence generates a line. The line number starts with 1 and is increment for each line.
Figure 93: Examples of Project control
The project name is Unplanned 20060104150803

It was generated by the FCMS to store information for manually
released lines if no project is loaded.
The flight line label is UL001
Version 3.22-15 - Feb / 25 / 2010 189

Project progress control

The project progress control shows information about the progress in the project execution.
In case of line or LIDAR sensors it shows the amount of memory in GB. In case of a frame
sensor it shows the numbers of frames.
Figure 94: Example of project progress controlsr
Line sensor
Number of remaining and number of flown lines.

Length of remaining and length of flown lines.
Approximate amount of remaining and taken image data.
Frame sensor
Number of remaining and number of flown lines.

Length of remaining and length of flown lines.
Number of remaining and number of taken frames.
Data filter control

The data filter control shows the user settings for data to be displayed in the graphic or numeric
in-flight evaluation controls. See “Graphic in-flight evaluation control” on Page 192 and
“Alphanumeric in-flight evaluation control” on Page 193.
Figure 95: Example of Project control
The selections are:

flown lines / multiple flown lines / lines not flown / planning
Line flown with errors / warnings / manual released / flight path
Project area control

This control displays a thumbnail display of the whole project area and a red frame indicating the
area displayed on graphic views.
Figure 96: Example of Project area control
.
The orientation is North-up.
190 Version 3.22-15 - Feb / 25 / 2010

Line detail control

This control displays details relevant to the highlighted data when the user browses project data
in the alphanumeric project view control.
Figure 97: Example of line detail control
Date and UTC time of line execution. If a line is flown multiple

times the date and time of the last execution is displayed.
The line in the example was flown once and was completed.
If a line is not completed the appropriate detail information is

displayed in the control: e.g. length of missed parts, number
multiple partly flights.
For lines flown with warnings or errors detailed information

about the errors are displayed in the control. See Table 28.
Table 28. Status icons used in Figure 97 and Figure 99

Status Warning and error information
Icon Description Icon Description
Line currently in execution Navigation, deviation exceeded warning
or release shut off distances, or speed
Line flown once PAV30/80 out off limits
Line flown multiple times GNSS constellation out of limits
Line flown with warnings Underexposure warning
Line flown with errors Overexposure warning
System configuration failed
Mass Memory - data recording error
IMU error
Temperature error
Version 3.22-15 - Feb / 25 / 2010 191

Graphic in-flight evaluation control

This control is the key element of the In-flight evaluation graphic view. See section "Project sta-
tus views for in-flight evaluation" in Volume 2, Chapter 5 on Page 210.
Figure 98: Example of graphic in-flight evaluation control
This control provides a graphic

project overview for in-flight
evaluation and control of
project execution. The
orientation is North-up.
The displayed data depend on

the user settings. See “Data
filter control” on Page 190.
The color codes are given below in Table 29

Table 29. Color codes in the graphical presentation showing the line status
Color Line status Representation is the graphics
Green Successfully flown The whole line is green.
Orange Flown with warnings The part of the line flown with warnings is orange.
Red Flown with errors The part of the line flown with errors is red.
Line in execution The whole line is red.
Additionally a fictive line is displayed. This thin red line
is the extension of the flight line to the IP (black square).
Blue Next line The whole line is blue.

Additionally a fictive line is displayed. This thin blue
line is the extension of the flight line towards the IP
(black square) and approach.
Black Recording was The part of the line flown with recording OFF is black.
manually set OFF
Not yet flown Thin black line
Flight path Thin black line
192 Version 3.22-15 - Feb / 25 / 2010

Alphanumeric in-flight evaluation control

This control is the key element of the In-flight evaluation alphanumeric view. See section
"Project status views for in-flight evaluation" in Volume 2, Chapter 5 on Page 210.
Figure 99: Example of alphanumeric in-flight evaluation control
This control lists for each line

- flight plan name
- line number
- line label.
- status information (shown
with icons)
- the maximum deviation of the
flown line to the planned line
horizontal and vertical.
The displayed data depend on

the user settings. See “Data
filter control” on Page 190.
Table 30. Status icons used in Figure 97 and Figure 99

Status Warning and error information
Icon Description Icon Description
Line currently in execution Navigation, deviation exceeded warning
or release shut off distances.
Line flown once PAV30/80 out of limits
Line flown multiple times GNSS constellation out of limits
Line flown with warnings Sensor system error
Line flown with errors
no icon Line not yet flown
Version 3.22-15 - Feb / 25 / 2010 193

Views during flight execution

During flight execution several views can be selected. This will not have any influence on the
sensor operation, e.g. if the sensor is recording, changing the view will not stop it. The different
views allow the user to have preferred specific information displayed.
Select [Select View] to display buttons to select view.
FCMS views for flight navigation and project management

Table 31. Flight guidance and project status views selectable during flight execution
View Icon Configuration Toggle view Icon Configuration

Nose-up Flight guidance No sub-view Flight guidance
and sensor release
control
configuration.
North-up Flight guidance No sub-view Flight guidance
and sensor release
control
configuration.
In-line Flight guidance No sub-view Flight guidance
and sensor release
control
configuration.
3-D Flight guidance No sub-view Flight guidance
navigation and sensor release
control
configuration.
Project No Graphic view No
Alphanumeric No
view
194 Version 3.22-15 - Feb / 25 / 2010

FCMS views for sensor controll

Table 32. Flight guidance and project status views selectable during flight execution
View Icon Configuration Toggle view Icon Configuration

Sensor status Main GNSS Status No configuration
configuration
GNSS-IMU No configuration
Status during flight
For ALS only

Sensor status Main Sensor Yes
configuration
Version 3.22-15 - Feb / 25 / 2010 195

Sensor status views for all types of sensors
Main system status view

This view is displayed by default after starting-up flight execution. It gives an overview of the
sensor systems.
To display this view from flight menu proceed as follows.
Select [Sensor System] to display sensor system status view.
Figure 100: Example of ‘System Status’ view generic sensor
This view gives an overview of the sensor systems.

and center. In the area below this controls the status of the
GNSS system is displayed.
Figure 101: Example of ‘System Status’ view fro ALS60
This view gives an overview of the ALS sensor systems.

and center. The ALS Sensor control is displayed on the
upper right area. In the area below this controls the status
of the GNSS system is displayed.
Select [Configuration] to enter main configuration dialog.

See section "Navigation within the menu tree" in Volume 2, Chapter 3 on Page 107.
196 Version 3.22-15 - Feb / 25 / 2010

GNSS status view

To display this view from flight menu proceed as follows:
Select [More buttons] to select views for more detailed information about sensor sub-systems.
Select [GNSS] to display GNSS status view.

Also, the GNSS control can be touched to display GNSS status view.
Figure 102: Example of ‘GNSS Status’ view
The GNSS status view shows actual values for position,

altitude, speed over ground, track over ground, date and
time. The lower section lists for every satellite in view the
satellite number, its status, azimuth and elevation angles
and the signal to noise ratios for both of the frequency
bands.
At the upper right a sky plot is displayed which
graphically displays the positions of the satellites in view
as well as of the sun.
Select [Filter Warning/errors] to show logged warnings and errors for the GNSS.
Select [Filter GNSS] to show logged status data for the GNSS.
Version 3.22-15 - Feb / 25 / 2010 197

GNSS-IMU status view

Select [IMU] to display GNSS-IMU status view.
Figure 103: Example of ‘GNSS-IMU Status’ view
The GNSS-IMU status view displays all position and

attitude information provided by the IPAS systems.
On the lower left side the operational status of the IPAS is
displayed. All ‘lights’ should be green during the flight
mission.
As the attitude information is coupled to the GNSS
information GNSS data are also displayed in the GNSS-
IMU view.
A sky plot on the upper right graphically displays the
positions of the satellites in view.
Select [Filter Warning/errors] to show logged warnings and errors for the GNSS-IMU.
Select [Filter IMU] to show logged status data for the GNSS-IMU.
198 Version 3.22-15 - Feb / 25 / 2010

Mount status view

Select [Sensor System] to display Leica ADS80 system status view.
Select [More buttons] to select views for more detailed information about Leica ADS80 sub-sys-
tems.
Select [Mount] to display Mount status view.
Figure 104: Example of ‘Mount Status’ view’
The Mount status view displays information about the

gyro-stabilized sensor mount. Details can be found in the
corresponding device documentation.
Select [Mount mode] to toggle mount stabilization OFF or ON respectively
Select [Log data] to display logged status data of the Mount.
Version 3.22-15 - Feb / 25 / 2010 199

Leica ALS60 specific status view

Select [Sensor System] to display sensor system status view
Select [Sensor] to display Sensor status display
Figure 105: Example of ‘ALS60 System Configuration settings’ view’
The ALS60 System Configuration settings view shows the

current ALS60 settings.
A description of the parameters is given in the Leica
ALS60 documentation.
Configuration source is typically ‘Flight Plan’. In this
case the relevant ALS configuration parameters are taken
from the flight plan.
Select [Configuration] to enter configuration dialog.
In the ALS60 System Configuration dialog the current

ALS60 settings can be adjusted.
A description of the parameters is given in the Leica
ALS60 documentation.
If the configuration source is ‘Flight plan’ and if the user
edits the Laser & Scanner settings the configuration
source will be set to ‘Manual’ on exit of this dialog and an
appropriate message window will be displayed.
200 Version 3.22-15 - Feb / 25 / 2010

Flight guidance views
Nose-up view
Note: A license for the FCMS module ‘Flight Guidance’ is required to get flight guidance infor-
mation displayed. If a project and a next flight line is selected full information is displayed. For a
non-planned line the view shows only limited information.

Select [Nose-up view] to display navigation data.
Figure 106: Example of ‘Nose-up’ view
This view is optimized for the pilot. It provides graphic

flight guidance information during approaches and turns.
The orientation is nose-up. North direction is indicated on
the lower right corner of the Nose-up navigation control.
A description of the controls displayed on this view is
given in “Basic layout of navigation view during flight
execution” on Page 166, “System controls” on Page 168,
“Flight guidance controls” on Page 171 and in “Controls
with project related information” on Page 189.
on Page 147.
Confirm [More buttons] to display the secondary toolbar with the following additional buttons:
Select [Recompute] to compute new optimum flight path to next line.
Select [Zoom -] or [Zoom +] to zoom-out/out the graphics in the Nose-up navigation control.
Select [Abort] to abort line execution or the close the project respectively. If the IP is passed the
line execution is aborted, during approach and turns the project is closed.
Version 3.22-15 - Feb / 25 / 2010 201

North-up view

Select [North-up view] to display navigation data.
Figure 107: Example of ‘North-up’ view
This view displays a project overview in north-up orienta-

tion. Flight guidance information is optimized for
approaches and turns.
on Page 147.
Select [Recompute] to compute new optimum flight path to the next line.
Select [Zoom -] or [Zoom +] to zoom-out/out the graphics in the Nose-up navigation control.
202 Version 3.22-15 - Feb / 25 / 2010

Select [Zoom-more] to display another secondary toolbar.
After [Zoom -more] additionally the following buttons can be selected:

Use [Left arrow] and [Right arrow] to pan the graphic in the north-up navigation control to left or
right.
Use [Up arrow] and [Down arrow] to pan the graphic in the north-up navigation control up or
down.
Select [Zoom optimum] for automatic scale adjustment. The whole project area will be displayed
on the Nose-up navigation control.
Select [Aircraft center] to pan automatically such that the aircraft is displayed in the center of the
Nose-up navigation control.
Version 3.22-15 - Feb / 25 / 2010 203

In-line view

Select [In-line view] to display navigation data.
Figure 108: Example of ‘In-line’ view

flight guidance information during line execution.

on Page 147.
204 Version 3.22-15 - Feb / 25 / 2010

3-D Navigation view


Select [3-D Navigation view] to display navigation data.
Figure 109: Example of ‘3-D Navigation’ view

flight guidance information during line execution.

If the toolbar is optimized for the Pilot select [Return] to display the main tool bar.
on Page 147.
Version 3.22-15 - Feb / 25 / 2010 205

Flight Guidance information on the GI40

The GI40 provides flight guidance information during approach and turns as well as when flying
along the line. Also error messages are displayed. The content of the display of the GI40 changes
accordingly.
Guidance information on the GI40 during approach

Important: This phase is indicated on the GI40 by red illuminated LEDs located on the right
side of the inscription ‘BRG’ and on the left side of the inscription ‘IP
The flight guidance information is similar to the information given on the Nose-up or North-up
views.
Figure 110: General layout of GI40 during approach
Line direction Turn information. Desired line altitude

Bearing from the Time to fly straight at the given track. Time required to fly
aircraft’s position Aircraft’s deviation from the suggested flight path. along the suggested
to the IP Climb or descend information. flight path to the IP.
Table 33. Flight guidance information

Suggested flight path Track and time information
Straight line Desired track over ground, time to fly this track.
Turn Make a turn till the given heading, make left or right turn.
Note: During approach the area for guidance information shows in an alternative sequence
either track and time information or information about the deviation from the suggested
approach path.
The time information is either >99 min. or the actual value which decrements in 1 minute steps
for the range from 99 min. to 1 min. and in 1 sec. steps for the range of 60 sec. to 1 sec.
The range for the deviation is scaled according to the flight guidance configuration. See section
"Overview configuration of Global 1 parameters" in Volume 2, Chapter 4 on Page 147. The
graphics coincide with the track deviation control. See section "Track deviation control" in Vol-
ume 2, Chapter 5 on Page 173.
Figure 111: GI40 examples during approaches
Line direction is 203° Des. altitude 7806 ft.

Bearing is 116° Time to IP is not
defined, > 99 min.
The aircraft should fly straight with a track over
ground of 012° for > than 99 minutes.
The arrow pointing down indicates that the
aircraft should descend to the desired line
altitude.
206 Version 3.22-15 - Feb / 25 / 2010


Bearing is 021° Time to IP 6 min. 50 sec
ground of 012° for 4 minutes.
The arrow pointing up indicates that the aircraft
should climb to the desired line altitude.

The aircraft should fly a right turn till the
heading is 357°.
altitude.

ground of 012° for 18 seconds.
The vertical line in the center indicates that the
aircraft is at the desired line altitude.

The aircraft should fly a right turn till the
heading is 203°. The square on the right side of
the arrow indicates that this is the final turn to
the IP.
altitude.
In an alternative sequence to the turn and track information as shown in the examples above, the
deviation from the suggested approach path is displayed on the GI40.

The aircraft is on the right side of the suggested
approach path.

The aircraft has no deviation from the suggested
approach path.

The aircraft is a large amount on the left side of
the suggested approach path.
Version 3.22-15 - Feb / 25 / 2010 207

Guidance information on the GI40 along the flight line

Important: This phase is indicated on the GI40 by the red illuminated LEDs located on the
right side of the inscription ‘DIF’ and on the left side of the inscription ‘END’.
Figure 112: General layout of GI40 during line execution
Line direction. The lateral deviation of the line from the aircraft’s Desired line altitude.
Difference of true actual position. Time required to
track to line Sensor status, if OFF. complete the line.
direction. Climb or descend information.
Note: Along the flight line the area for flight guidance information shows similar information as
the line deviation control. The range for the deviation is scaled according to the sensor release
configuration. See section "Overview configuration of Global 1 parameters" in Volume 2,
Chapter 4 on Page 147. The graphics coincide with the line deviation control. See section "Line
deviation control" in Volume 2, Chapter 5 on Page 176.
Figure 113: GI40 examples during line execution

Difference is 00° Time to end 3min 34sec
The line is perfectly below the aircraft.

The line is slightly on the left side of the aircraft,
but within the tolerance.

The line is on the left side of the aircraft. The
offset is within the warning tolerance.

Difference is -12° Time to end 1min 12sec
The line is on the far left side of the aircraft in
the release shut off area. The broken vertical line
in the center indicates that data recording is
interrupted.

The line is slightly on the left side of the aircraft.
but within the tolerance.
The aircraft should descend to desired altitude.
208 Version 3.22-15 - Feb / 25 / 2010

Error information on the GI40 along the flight line
Figure 114: GI40 error examples during line execution

Difference is 00° Time to end 1min. 42sec
The aircraft is flying too fast. GS should be
reduced by 28 kts.

The aircraft is flying slow. GS could be increased
by 42 kts.

A fatal error occurred on the sensor system. At
the same time an error message with trouble
shooting options is displayed on the OI40.
Version 3.22-15 - Feb / 25 / 2010 209

Project status views for in-flight evaluation
Graphic and alphanumeric in-flight evaluation

Note: A license for FCMS 2.x, module ‘Flight Guidance’ is required to get flight guidance
information displayed. If a project and a next flight line is selected full information is displayed.
For a non-planned line the view shows only limited information.
To display this views from flight menu proceed as follows:

Select [Project view] to display project data.
Note: Project data is displayed either graphically or numerically. To toggle select the corre-
sponding icon which is displayed on the toolbar alternatively.
In-flight evaluation - graphic view

Select [Graphic] to display project data graphically.
Figure 115: Example of ‘In-flight evaluation - graphic view’
This view provides a graphic project overview for in-

flight evaluation and control of project execution. The ori-
entation is North-up.

execution” on Page 166 and in “Controls with project
related information” on Page 189.
Select [Set filer] to display a secondary toolbar to set/reset filters to hide/show information.
210 Version 3.22-15 - Feb / 25 / 2010

Figure 116: Filters to query project and flight data
Show lines Show lines Show lines Show lines Show lines Show lines Show Show flight
flown once flown not yet flown with flown with manually planning path
multiple flown errors warnings released
Hide lines Hide lines Hide lines Hide lines Hide lines Hide lines Hide Hide flight
flown once flown not yet flown with flown with manually planning path
multiple flown errors warnings released
From the main view toolbar select [Zoom-more] to display a secondary toolbar.
After [Zoom-more] additionally the following buttons can be selected:

Use [Left arrow] and [Right arrow] to pan the graphics in the graphic in-flight evaluation control
to left or right.
Use [Up arrow] and [Down arrow] to pan the graphics in the graphic in-flight evaluation control
up or down.
Select [Zoom -] or [Zoom +] to zoom-out/out the graphics in the graphic in-flight evaluation con-
trol.
Select [Zoom optimum] for automatic scale adjustment. The whole project area will be displayed
on the graphic in-flight evaluation control.
Select [Aircraft center] to pan automatically such that the aircraft is displayed in the center of the
graphic in-flight evaluation control.
Version 3.22-15 - Feb / 25 / 2010 211

In-flight evaluation - alphanumeric view

Select [Text] to display project data alphanumerically.
Figure 117: Example of ‘In-flight evaluation - alphanumeric view’
This view is for in-flights evaluation. It lists for each

flight line the most relevant data.
execution” on Page 166 and in “Controls with project
related information” on Page 189.
Select [Log data] to browse log data.
Select [Fast scroll up] or [Fast scroll down] to browse the list page by page.
Select [Scroll up] or [Scroll down] to move the highlighted bar in the list.
Select [Set filer] to display a secondary toolbar to set/reset filters to hide/show information.
The settings are given in Figure 116, “Filters to query project and flight data” in Volume 2, Chap-
ter 5 on Page 211.
212 Version 3.22-15 - Feb / 25 / 2010

Annotation - user log file entries during flight

This feature allows to make user text entries into the log file during flight execution. The entries
are time tagged. The log file is part of the data which is passed along with the image data to the
data post processing step.
The text for log file entries is selected by the user from a list. This list can contain an unlimited
number of text lines. Each line can be up to 80 characters long. The user can enter new text lines
to the list. Also he can edit an existing text line in the list or he can delete a text line. Each text
line has a preceding ID. The text list is sorted by the text line identifiers. The identifier is not part
of the text line and therefore will not become part of the log file entry.
Select [Annotation] from main menu to enter annotation dialog.
Figure 118: Example of ‘Annotation’ dialog
To make a log file entry select from the list of text lines
the desired line. Multiple log file entries are made line by
line.
Select [Fast scroll up] or [Fast scroll down] to browse the list page wise.
Select [Scroll up] or [Scroll down] to move the high lighted bar in the list.
Select [Edit] to modify the high lighted text line.
Select [New] to enter a new text line.
Select [Delete Annotation] to delete the high lighted text line from the list.
Version 3.22-15 - Feb / 25 / 2010 213

Select [Annotation] to generate a log file entry. The high lighted text is copied with a time tag into
the log file.
Select [Return] to return to main level, load settings and to exit from dialog.
Edit or create annotation text

First step
Edit or enter text group ID.
FCMS sorts the annotation text lines by the text group ID.
See Figure 118 on Page 213.
Select [Accept] to accept.

Edit: Assign changed group ID to selected annotation element.
New: Assign group ID to new annotation element.
Select [Cancel] to continue.

Edit: Rejects changes and leaves text as before.
New: No new entry with annotation text is being created.
Second step
Edit existing text or enter new text.
Select [Accept] to accept.

Edit: Assigns changed text to selected annotation text.
New: Store new text in list.
Select [Cancel] to abort.

Edit: Rejects changes and leaves text as before.
New: No new entry with annotation text is being created.
214 Version 3.22-15 - Feb / 25 / 2010

Browsing of logged status data

Log data can be browsed either from Flight menu or from Service menu.
If the browser is started from the Flight menu only data related to the current flight are listed in
the browser.
If the browser is started from the Service menu all data stored in the log data base can be
browsed.
Start browser from Flight menu

Select [Select View] from flight main tool bar to display buttons to select view.
Select [System] to display sensor system status view.
Select [More buttons] from sensor system status view.
Start browser from Service menu

Select [Service] from FCMS main menu.
Version 3.22-15 - Feb / 25 / 2010 215

Browsing log data
Figure 119: Example of ‘Log Data’ view”
The ‘Log data view’ displays the status information

logged during system operation:
• Change of operation status
• Warnings
• Errors
• User interactions
• etc.
Select [Fast scroll up] or [Fast scroll down] to browse the data page wise.
Select [Scroll up] or [Scroll down] to browse the data.
Select [Previous warning / error] or [Next warning / error] to jump in the logged data to previous
or next error warning.
Seek in the log database the entry closest to the defined date and time.
Seek in the log database the latest log data entry.
Select [Set filter] to change buttons on toolbar to set filters to query log data.
Selectable filters see Figure 120 below.
Figure 120: Filters to query logged data
Show logged Show logged Show logged Show logged Show logged Show logged Remove all
Sensor Head Mass IMU status GNSS status user warnings / filters
status Memory interactions errors
status
216 Version 3.22-15 - Feb / 25 / 2010

Installation Information
This Installation Manual contains important information. Please

read carefully through before you use the system.
Document code
Volume 3 FCMS Installation Data
218 Version 3.22-15 - Feb / 25 / 2010

Chapter 1 About Installation Information
Version 3.22-15 Feb / 25 / 2010 219

Volume 3 FCMS Installation Data
Chapter 1 About Installation Information
Scope of document
Installation Information contains important information about installation of the FCMS into an
aircraft.
• General note on aircraft for airborne sensing
• Leica Geosystems installation policy
• List of tasks to be performed by the installer
• Conditions to be fulfilled for sensor installation
• Installation data and installation drawings
• Environmental qualification forms
Note: Electrical data, environmental condition, weight and part numbers for all parts is given in
section "Technical Data" in Volume 1, Chapter 7 on Page 71
Structure of this volume

Chapter 2 ‘Aircraft Installation Manual’ gives important general installation information
Chapter 3 ‘Installation Questionnaire’ helps to collect customers specific dimensions and param-
eter requested for installation
Chapter 4 ‘Installation data’ contains installation data and drawings
General
See section section "Product identification" in Volume 1, Chapter 1 on Page 2
Abbreviations
See section "Abbreviations" in Volume 1, Chapter 1 on Page 3
Meaning of symbols
See section "Meaning of symbols" in Volume 1, Chapter 1 on Page 5

Documents Other volumes of the FCMS Documentation

See section "Where to get assistance and training" in Volume 1, Chapter 1 on Page 6
220 Version 3.22-15 - Feb / 25 / 2010

Chapter 2 Aircraft Installation Data
Version 3.22-15 Feb / 25 / 2010 221

Volume 3 FCMS Undefined
Leica Geosystems company profile
Leica Geosystems’ Business Unit Digital Imaging

The product groups of Leica Geosystems’ Business Unit Digital Imaging are: RC30 aerial cam-
era, ADS40 Airborne Digital Sensor, ALS50 Airborne Laser Scanner and related software.
The activities of Leica Geosystems covers the whole range from product development and man-
ufacture through marketing and sales to services such as installation, training, systems support
and integration.
Large format airborne sensors

Large format airborne sensors are a unique and well balanced combination of features which can-
not be provided by any other sensor or sensor systems owing to simple physical laws governing
image geometry (size, focal length, distortion, resolution), surface of the area to be photographed
and the highest possible in-flight economy.
222 Version 3.22-15 - Feb / 25 / 2010

Leica Geosystems Sensor Installation Policy
Sensor and GNSS installations

Airborne sensor systems are not considered an integral part of the aircraft. These sensors are
removable “carry-on” type of equipment, which includes interchangeable modules. Therefore,
they are not classified as integrated avionics equipment, which has to be certified by national or
international aircraft safety authorities.
Environment and Standards

The FCMS Hardware components qualifies to the standards given in section "Applied standards"
in Volume 1, Chapter 7 on Page 73. Details see section "Environmental qualification form OC50
and GI40" in Volume 3, Chapter 2 on Page 225..
Important: It is the aircraft owner’s responsibility to ensure that enough power is available to
operate the sensor components which he has chosen to install in the aircraft. It is the aircraft
owner’s responsibility to ensure that the power consumption of the installed sensor system
components does not jeopardize the safe operation of the aircraft and that adequate circuit
breakers are installed. The power requirements are defined in section "Electrical" in Volume 1,
Aircraft modifications
Important: Aircraft modifications involve changes in the structure of the aircraft. In this case,
the strict regulations governing these activities have be followed. Normally modifications to the
fuselage have to be certified by the FAA or national aviation associations. This is also valid for
changes to an already certified aircraft modification.
Responsibility for aircraft modifications

Important: The responsibility to have aircraft modifications certified lies either with the
manufacturer of the aircraft or the specialized contractors or subcontractors of such special
modifications.
Main tasks to be performed by the installer

• Installation of the GNSS antenna on the fuselage of the aircraft.
• Prepare aircraft, provide required adapter plates and adequate fixing screws for installation
of all components of the sensor system. For FCMS in particular:
Interface Stand with OC50 for operator, OC50 for pilot and GI40 Guidance Indicator.
• Prepare aircraft to provide adequate power, fuse protection and chassis ground connections
to operate the system.
• Adapt the open ended power cable to conform the aircraft’s power connectors.
• Install looming of the sensor system if it is required to place them in protected channels.
• Weight and balance calculations.
Version 3.22-15 - Feb / 25 / 2010 223

Installation tasks to be performed by the user

The installation tasks to be performed for and by the user are described in section "Unpacking" in
Volume 1, Chapter 3 on Page 12.
Leica Geosystems installation support

Leica Geosystems does not have the expertise or the authorization to carry out aircraft modifica-
tions, but it is in Leica Geosystems’ interest that these modifications fulfill the customers' speci-
fications and requirements concerning the optimal use of the aerial sensor system purchased.
Leica Geosystems can provide consulting and checking services for sensor installations. If the
installation of the sensor was based on Leica Geosystems' installation drawings, the Leica Geo-
systems expert will check and confirm that the sensor holes are adequate for unrestricted use of
the FCMS. The Leica Geosystems expert will not undertake any modification of the aircraft
structure or interior modifications made for the sensor installation. The Leica Geosystems expert
is not qualified to comment on the airworthiness of modifications, which should be certified by
the appropriate body.
Leica Geosystems installation drawings

Installation drawings found in this documentation are valid for normal installation. That is:
• no optical window
• full rotation range of mount in Pitch, Roll and Drift.
It is the customers' responsibility or that of the companies or institutions which he has desig-
nated, to warrant a perfect aircraft modification according to the drawings provided by Leica
Geosystems.
References
Available upon request from Leica Geosystems.
224 Version 3.22-15 - Feb / 25 / 2010

Environmental qualification form OC50 and GI40
Version 3.22-15 - Feb / 25 / 2010 225

Environmental qualification form OC52
226 Version 3.22-15 - Feb / 25 / 2010

Installation of IS40
Ideal position of IS40 in aircraft

The Interface Stand IS40 holds the OC52 or OC50 for operator. The IS40 should be installed
such that the operator has convenient access to the OC52 or OC50. The ideal position is in front
of the operator’s seat.
Tip: For safety reasons the tube of the IS40 can be removed for take off and landings and stored
in a safe place.
Chassis ground connection between IS40 and aircraft structure

Caution: For safety reasons, an efficient chassis ground connection between the base plate of
the IS40 and the aircraft structure has to be fulfilled.
The areas surrounding the screw holes on the IS40 base plate are conductive. If the IS40 is
secured by metallic screws directly to the aircraft structure, chassis ground connection is suffi-
cient. If the IS40 is secured on a non-metallic intermediate fixing plate, a ground strap has to
connect one of the two conductive areas on the IS40 base plate with electrically conductive
metallic aircraft structures. See Drawing 1, “IS40 base plate” in Volume 3, Chapter 2 on
Page 228.
IS40 base plate

Material Aluminium
Thickness 10 mm at the mounting screw holes.
Fixing holes 4 x 10 mm diameter for M8 size screws, location see Drawing 1, “IS40 base
plate” in Volume 3, Chapter 2 on Page 228.
Chassis ground Each fixing hole is surrounded with a conductive area.
Additionally two conductive areas are located on the plate.
Use either the fixing holes or one of the conductive areas with a chassis
ground strap.
Drawings See following pages. Units in drawings: mm
Caution: INSTALLATION NOTES: Follow all applicable rules for installation in aircraft. Use
FAA AC 43.13-1B and FAA AC 43.13 2A and Aircraft Manufactureres Recommendations for
installation guidance.
Version 3.22-15 - Feb / 25 / 2010 227

Figure 121: Detail photo IS40 base plate
The photo on the left shows the IS40 mounting

plate. The screw holes for mounting are
located at each corner and the holes are
surrounded by a conductive area.
Additionally two conductive areas are located
close to the tube holder.
Drawing 1: IS40 base plate
228 Version 3.22-15 - Feb / 25 / 2010

Drawing 2: Adjustment and center of gravity of IS40 and OC50/52
Version 3.22-15 - Feb / 25 / 2010 229

Installation of OC52/OC50 for operator

The OC52/OC50 for operator can be attached to the IS40. In this case no special aircraft modifi-
cation is required.
Tip: For safety reasons the OC50/52 can be removed for take off and landings and stored in a
safe place.
Ideal position of OC52/OC50 for operator in aircraft

The OC52/OC50 for operator should be installed such that the operator has convenient access to
the hard keys on the screen and to the keyboard. The ideal position is in front of operator’s seat.
The OC52/OC50 for operator is fitted by means of a screw on to the Interface Stand IS40. There-
fore, the position of the OC52/OC50 for operator is given by the position of the IS40.
Alternative mounting without means of the IS40

Use either:
• The screw holes located on the holder plate.
See Drawing 8, “OC50 for operator side view and top view of keyboard” in Volume 3,
Chapter 2 on Page 236
• The fastening threat located on the back side.
See Drawing 7, “OC50 for operator front and rear view” in Volume 3, Chapter 2 on
Page 235
Chassis ground connection for OC52/OC50 for operator

Chassis ground connection for OC52/OC50 for operator is established via IS40. No separate
chassis ground connection is required if the OC52/OC50 for operator is mounted on the IS40.
Caution: For safety reasons, an efficient chassis ground connection between the fastening threat
or the screw holes of the Oc52/OC50 holder plate and the aircraft structure has to be fulfilled if
the OC52/OC50 for operator is mounted without means of the IS40.
Summary OC52/OC50 for operator if mounted not on IS40

Material Aluminium
Thickness 4 mm at the mounting screw holes
Fixing holes 4.3 mm diameter for M4 size screws. Location see section "OC52 with
keyboard front and rear view" in Volume 3, Chapter 2 on Page 232 and
Drawing 8, “OC50 for operator side view and top view of keyboard” in
Volume 3, Chapter 2 on Page 236.
Chassis ground Each screw hole is a conductive area.
Ensure ground connection from on of the screw holes to the aircraft
structure.
230 Version 3.22-15 - Feb / 25 / 2010

Airflow for cooling purposes

On the rear part of the OC50/52 there are fans with airflow inlets. The airflow outlet is on the
left, right and top side of the OC50/52 rear part of the housing.
Important: The space at the airflow inlets and the space at the airflow outlets should not be
obstructed. Install the OC50/52 with a minimum space to walls.
Airflow inlet is at the lower part of the

rear side of the OC50/52. Two fans
are located at this position.
Airflow outlet is on the left, right and
top side through the slots located
close to the rear of the OC50/52.
The space in front of the airflow inlet

and in front of the airflow outlets
should not be obstructed. Install the
OC50/52 with a minimum space of 50
mm to walls at the airflow areas.
Drawing 3: OC50 for operator oblique view
OC52 with keyboard OC50 with keyboard
Version 3.22-15 - Feb / 25 / 2010 231

Drawing 4: OC52 with keyboard front and rear view
232 Version 3.22-15 - Feb / 25 / 2010

Drawing 5: OC52 with keyboard side view and top view of keyboard
Version 3.22-15 - Feb / 25 / 2010 233

Drawing 6: OC52 front, rear and side view
234 Version 3.22-15 - Feb / 25 / 2010

Drawing 7: OC50 for operator front and rear view
Version 3.22-15 - Feb / 25 / 2010 235

Drawing 8: OC50 for operator side view and top view of keyboard
236 Version 3.22-15 - Feb / 25 / 2010

Installation of OC50 for pilot
Ideal position of OC50 for pilot in aircraft

The OC50 for pilot should be installed ideally in front of the pilot such that he can conveniently
read the display and operate the keys. Nevertheless, the customer is free to choose any other loca-
tion in the aircraft for mounting. The exact position depends mainly on pilot preferences and
available space and is a customizing task.
Safety
Warning: The OC50 should be mounted such that there is no safety hazard to the pilot etc. in
rough and turbulent flight conditions.
The OC50 should be mounted that it is removable for safe storage very quickly, with as little
manual effort as possible and without tools. Safe storage must take place during take off and
landings and very turbulent flight conditions.
Cabling
A single cable connects power and data. The connector of the cable is protected against being
pulled out of its socket.
Storage of the OC50 for pilot

Once the OC50 has been removed from the operating position, it must be safely storable.
Chassis ground connection for OC50 for pilot

Caution: For safety reasons, an efficient chassis ground connection between the screw holes of
the OC50 and the aircraft structure has to be fulfilled.
Drawing 9: OC50 for pilot oblique and rear view
Version 3.22-15 - Feb / 25 / 2010 237

Summary OC50 for pilot

Material Aluminium
Fixing holes 3 x M5 threads, 10 mm deep. Location see Drawing 10, “OC50 for pilot
front, side, top and bottom views” in Volume 3, Chapter 2 on Page 239.
Chassis ground Each screw hole is a conductive area.
Ensure ground connection from on of the screw holes to the aircraft
structure.
Airflow for cooling purposes

On the rear part of the OC50 there are fans with airflow inlets. The airflow outlet is on the left,
right and top side of the OC50 housing.
Important: The space at the airflow inlets and the space at the airflow outlets should not be
obstructed. Install the OC50 with a minimum space to walls.
Airflow inlet is at the lower part of the

rear side of the OC50. Two fans are
located at this position.
Airflow outlet is on the left, right and
top side through the slots located
close to the rear of the OC50.
The space in front of the airflow inlet

and in front of the airflow outlets
should not be obstructed. Install the
OC50 with a minimum space of 50
mm to walls at the airflow areas.
238 Version 3.22-15 - Feb / 25 / 2010

Drawing 10: OC50 for pilot front, side, top and bottom views
Version 3.22-15 - Feb / 25 / 2010 239

Installation of GI40
Ideal position of GI40 in aircraft

The Guidance Indicator GI40 should be installed ideally in front of the pilot such that he can con-
veniently read the display. The exact position depends mainly on pilot preferences and available
space and is a customizing task.
Safety
Warning: The GI40 should be mounted such that there is no safety hazard to the pilot etc. in
rough and turbulent flight conditions.
The GI40 should be mounted that it is removable for safe storage very quickly, with as little man-
ual effort as possible and without tools. Safe storage must take place during take off and landings
and very turbulent flight conditions.
Cabling
A single cable connects power and data. The connector of the cable is protected against being
pulled out of its socket.
Storage of the GI40

Once the GI40 has been removed from the operating position, it must be safely storable.
Summary GI40
Material Aluminium
Fixing holes 2 x M6 threads, 10 mm deep. Location see Drawing 11, “GI40” in Volume 3,
Chassis ground Not required.
Cables See section "Cabling" in Volume 3, Chapter 2 on Page 243.
240 Version 3.22-15 - Feb / 25 / 2010

Drawing 11: GI40
Version 3.22-15 - Feb / 25 / 2010 241

Chassis ground connection

IS40/OC50/52 need efficient chassis ground connection. For details see
• section "Chassis ground connection between IS40 and aircraft structure" in Volume 3, Chap-
ter 2 on Page 227
• section "Chassis ground connection for OC52/OC50 for operator" in Volume 3, Chapter 2
on Page 230
• section "Chassis ground connection for OC50 for pilot" in Volume 3, Chapter 2 on Page 237
The photo on the left side shows the conductive area

surrounding a screw hole on IS40 base plate.
The photo on the left side shows a ground strap

connected to one of the conductive areas located on the
IS40 base plate.
Chassis ground connection OC50/52

OC52/ OC50 for operator The fixing screw holes on the mounting plate are
Conductive areas on chassis conductive.
Ensure ground connection from on of the screw holes
to the aircraft structure.
Drawings See Drawing 8, “OC50 for operator side view and top
view of keyboard” in Volume 3, Chapter 2 on
Page 236.
OC50 for pilot The fixing screw holes on the OC50 are conductive.
Conductive areas on chassis Ensure ground connection from on of the screw holes
to the aircraft structure.
Drawings See Drawing 10, “OC50 for pilot front, side, top and
bottom views” in Volume 3, Chapter 2 on Page 239.
242 Version 3.22-15 - Feb / 25 / 2010

Cabling
General about cabling

Cable lengths see section "Cables" in Volume 1, Chapter 7 on Page 74.
Caution:
Do not modify the cables.
Do not extend the cable lengths.
Cabling diagram
Note: Below only cabling of FCMS components is described. Cabling information for the
components of the sensor system is given in the corresponding sensor installation documen-
tation.
Figure 122: FCMS components cabling diagram for ALS60
Cable lengths are given in Table 8, “Cables” in Volume 1, Chapter 7 on Page 74.
For power and chassis ground connection see section "Electrical" in Volume 1, Chapter 7 on
Page 72.
It is the certified aircraft installer’s task to install looming of the sensor system if it is required to
place them in protected channels.
Important: The total cable length from the SC60 System Controller to the OC50 for pilot
together, must not exceed 15 m. This allows the following cable combinations: 4m + 4m, 4m +
7m, 4m + 10m, 7m + 7m. Plus additionally 0.8 m for a 2nd operator interface.
If no OC50 for pilot is installed, the GI40 is connected to the OC52/OC50 for operator.
Version 3.22-15 - Feb / 25 / 2010 243

Figure 123: FCMS cabling diagram for ALS60 + RCD105
Figure 124: FCMS cabling diagram for ADS80 + ALS60
244 Version 3.22-15 - Feb / 25 / 2010

Figure 125: FCMS cabling diagram for RC30 with IPAS20and RCIF30
Figure 126: FCMS cabling IPAS20 with up to four sensors
Version 3.22-15 - Feb / 25 / 2010 245

Power connection
The OC52/OC50 for Operator, the OC50 fro Pilot and the GI40 have not power connector to the
aircraft power source. Power is provided by the sensor system. How to connect the sensor system
to the aircraft power source is described in the corresponding sensor installation documentation.
246 Version 3.22-15 - Feb / 25 / 2010

Flight &amp; Sensor Control Management System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Flight &amp; Sensor Control Management System

Uploaded by

Copyright:

Available Formats

FCMS 3.

This Documentation contains important information. Please

Document code 757 041

ii Version 3.22-15 - Feb / 24 / 2010

Leica FCMS Documentation

Version 3.22-15 - Feb / 25 / 2010 iii

iv Version 3.22-15 - Feb / 25 / 2010

Contents FCMS Documentationi

Version 3.22-15 - Feb / 25 / 2010 v

Volume 1 User Manual . . . . . . . . . . . . . . . . . . . xxiii

About this User Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Installing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

vi Version 3.22-15 - Feb / 25 / 2010

Installation of 3rd party software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Version 3.22-15 - Feb / 25 / 2010 vii

Select data and delete it . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Care & Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

viii Version 3.22-15 - Feb / 25 / 2010

Touch screen of the OC52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Warranty - Software License Agreement . . . . . . . . . . . . . . . . . . 77

Version 3.22-15 - Feb / 25 / 2010 ix

Microsoft End User License Agreement ("EULA"). . . . . . . . . . . . . . . . . . . . . . . 79

x Version 3.22-15 - Feb / 25 / 2010

Volume 2 Field Manual . . . . . . . . . . . . . . . . . . . . . 85

About Field Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

General for photo flights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Version 3.22-15 - Feb / 25 / 2010 xi

Data logging for post-flight evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

FCMS - Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

xii Version 3.22-15 - Feb / 25 / 2010

Configuration data base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Version 3.22-15 - Feb / 25 / 2010 xiii

Overview configuration of Global 2 parameters . . . . . . . . . . . . . . . . . . . 160

FCMS - Flight Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

xiv Version 3.22-15 - Feb / 25 / 2010

Line detail control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Version 3.22-15 - Feb / 25 / 2010 xv

Volume 3 Installation Information . . . . . . . . . . . 217

About Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . 219

Aircraft Installation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

xvi Version 3.22-15 - Feb / 25 / 2010

Chassis ground connection for OC50 for pilot . . . . . . . . . . . . . . . . . . . . 237

Version 3.22-15 - Feb / 25 / 2010 xvii

xviii Version 3.22-15 - Feb / 25 / 2010

Chapter 0 About FCMS Documentation

Version 3.22-15 Feb / 24 / 2010 xix

xx Version 3.22-15 - Feb / 24 / 2010

• Volume 2 - Field Manual

• Volume 3 - Installation Information

Where to get more information

Version 3.22-15 - Feb / 24 / 2010 xxi

xxii Version 3.22-15 - Feb / 24 / 2010

This User Manual contains important information. Please read

Document code 757 046

xxiv Version 3.22-15 - Feb / 25 / 2010

Content User Manual

Installing the system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Version 3.22-15 - Feb / 25 / 2010 xxv

Preparation before installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

xxvi Version 3.22-15 - Feb / 25 / 2010

Delete data in the Control Unit memory . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Care & Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Version 3.22-15 - Feb / 25 / 2010 xxvii

Cables and plugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Flight & Sensor Control Management System

Flight & Sensor Control Management System