9. System integration

9.1. Supported sensors

IMU

• Applanix POSAV

• Applanix AP+

• all GNSS sending NMEA

• iXBlue AIRINS / ATLANS

Imaging sensors

• ITRES

• Nasa CWIS-II DCS

• Phase One

• Simplex

• UltraCam

LiDAR

• Riegl

Integrated systems

• AISPECO - Robincop

Sensor mount platforms

• SOMAG Version 1

• SOMAG Version 2

• Aerostab3

• SteadyTrack

9.2. Setting up a list of SensorHandler integrated sensors

This chapter is intended for the system integrator only.

9.2.1. The SensorHandler sensor list

Each button on the left of the SensorHandler panel represents a device being used. Right click on a button to add or remove a device from the list of devices.

SensorHandler will communicate with Applanix to receive position information and to control the SOMAG platform and, optionally, to take an image. SensorHandler will communicate to RiAcquire to start and stop scanning In the settings the following information is stored: location of the log files location of the settings files Definition of COM ports (not needed in Riegl configuration) Definition of Ethernet ports used

9.2.2. SensorHandler Ethernet settings

In the Ethernet settings dialog, set the IP address and port of each of the devices:

9.3. Setting up a PhaseOne camera

By default, PhaseOne and iXCapture both run on the same computer (usually on an iXController). The operator thus can see the images taken (with iXCapture) while also seeing the navigation window of the flight. This default installation implicates that SensorHandler runs on the same machine.

Some special installations are required to run iXCapture on a different machine than that of the navigation program. In this case, NAVIGATOR and SensorHandler run on one machine and iXCapture on another.

Adding PhaseOne into SensorHandler

The PhaseOne handler needs to be visible in the sensor list. Right click on a free button and select PhaseOne sensor to populate the free button:

Configuring the Ethernet settings

Set the IP to the local address (127.0.0.1) and the port to 9569. This allows SensorHandler and iXCapture to exchange information on the images taken and on correct file names including the line and the image number.

Accessing the Phase One dialog

1. Click on the PhaseOne button in SensorHandler’s main list of connected sensors to open the dialog box. Normally, this dialog does not need to be opened. However, it is useful for verifying correct system behavior.
   
   The symbol is colored green as soon as the camera is connected correctly and running. It sends the system ready message to SensorHandler. The symbol is colored red when there is no connection to the camera.

   The instant the camera takes an image, the red box around the lens changes to green for 0.4 seconds. Then it turns back to red.

   Click this button to ask if the system is ready. It shows system ready on the bar at the bottom of the dialog.

   In the default setting, an image will be released the instance the airplane passes the position where the image is to be taken. Optionally, images can be released at regular time intervals between the start and end of the line of flight (no images will be taken if the airplane is outside of the line of flight).

   This button can be pressed to manually release an image. This is often used to verify that the system is working correctly or to define the correct values for aperture and exposure time.

   Click on this button for more settings.

   
   
2. Use standard communication with iXCapture This is the default option. It is used in standard installations where NAVIGATOR, SensorHandler and iXCapture are installed on the same machine.

   Use TCP/IP bridge to remote iXCapture This option is selected when NAVIGATOR/SensorHandler are installed on a different computer than iXCapture. In this case, use the IP address of the remote computer on which IXCapture and iXBridge are running.
   

Optional installing with iXBridge: iXCapture separate from SensorHandler

If iXCapture runs on a different computer than NAVIGATOR / SensorHandler then SensorHandler needs to know the IP address of the computer on which iXCapture is running. Additionally, iXBridge software needs to run on the same computer as iXCapture. As its name suggests, iXBridge builds a bridge for commands between the navigator’s computer and the computer on which iXCapture is running.

Example of such an integration:

On computer 1, TOPOFLIGHT NAVIGATOR and SensorHandler are running. The GPS/IMU and an ITRES multispectral sensor are also connected to computer 1.

Computer 2 is used to control the PhaseOne camera(s) and to store the collected images.

1. Settings of SensorHandler on computer 1

   

   PhaseOne handler needs to be visible in SensorHandler’s list of sensors: right click on a free button and select PhaseOne sensor to populate the free button.

   

   Set IP address of the remote computer on which iXCapture and iXBridge are running. Set the port to be used with iXBridge on the remote computer. By default, it is port 5000.

2. Settings on computer 2

   The program iXBridge needs to be launched automatically at system start. It opens as a minimized dialog and is shown on the task list. When clicking on its icon, the following dialog appears:
   

   Port for iXCapture This is the port through which data flows from SensorHandler to iXCapture (e.g. actual line deviation, image number). The default port is 9569. iP address of iXCapture This address is that of the computer on which iXCapture runs The address is usually 127.0.0.1 since iXBridge normally is installed on the same machine as iXCapture. Port for FMS This is the port defined in SensorHandler. Through this port, the remote SensorHandler and the local iXCapture communicate. Default port is 5000.

3. A log file is written and saved in the windows temp folder. The log file is named in the form of iXBridgeYYMMDD-HHMM.txt. The log file can be opened with Notepad by clicking on the open log file entry in the main menu.

9.4. Riegl RiAcquire settings

9.4.1. Settings in SensorHandler

SensorHandler

Automatic mode: This mode stops scanning at the end of a line of flight by setting the scanner to initialized mode. It starts scanning again at the beginning of the line the scanner is set to logging mode. Semi-automatic mode: this mode switches between working and logging only. This option is recommended for the newest Riegl scanners and the following scanners: VQ-1560II, CVQ-1560I, LMS-Q1560, VQ-780i, VQ-780II, LMS-Q780 (all 1560 and 780 models). Manual mode: In this mode the scanner won’t stop logging at the end of the line. In fact, it continuously keeps scanning after the first start of logging on the first line. It can be started and stopped manually with RiAcquire.

If the airplane leaves the defined corridor the scanner will normally stop scanning by changing from logging to working mode. If the option if outside corridor do not stop scanning is set, then the scanner will keep scanning even outside of the corridor. If the option outside corridor do not stop taking images is set the images will be taken even if the airplane is outside of the horizontal tolerance (corridor).

RiAcquire

	Get devices from Riegl can be selected as soon as the scanner has been connected. Both lists (scanners and cameras) will automatically be filled with the existing scanners and cameras. A Q1560 scanner typically has two scanners and one camera. By default, the scanner(s) and camera(s) are switched on, meaning that TOPOFLIGHT controls the devices.
	Automatic connection and disconnection set the time limits of when the scanner switches to working mode before the start of the line when to change to working-logging mode before the start of the line when to change to initialized mode after the end of the flight line Make sure to switch off Release camera using RiAcquire
	To change any of the values above, the lock has to be opened. Click on the black lock symbol and use the password: riegl

9.4.2. Settings for Image Takings in RiAcquire method 1

Standard method

SensorHandler takes images through RiAcquire and NOT through Applanix:

	The picture shows the default settings in the RiAcquire dialog. If the release camera is enabled SensorHandler will release the camera using RiAcquire.
	In the Applanix dialog, disable the option to take images through Applanix.
	In RiAcquire, set trigger mode to Manual Remote Control.

9.4.3. Settings for Image Takings in RiAcquire method 2

Alternative method

SensorHandler takes images through Applanix POS and NOT through RiAcquire:

	If the release camera is disabled SensorHandler will NOT release the camera using RiAcquire.
	In the Applanix dialog, enable the option to take images through Applanix. This means that SensorHandler will take images using Applanix POS commands.
	In RiAcquire, set trigger mode to External High.

9.5. Setting up Applanix POSAV

9.5.1. Applanix POSAV in SensorHandler

	Set the Display Port, TCP Control Port, TCP Real Time Port Ports 5605 and 5606 can only be used if the Applanix FMS option is installed
	Use GPS and IMU Data for navigation. Position, speed and altitude will be read and sent to TOPOFLIGHT NAVIGATOR. For special applications, the other options can be selected.
	Switch this option to ON if you need to release images through Applanix. For UltraCam and Riegl scanners these options are usually not activated.
	If ON, the mount will be controlled through Applanix. Default: ON. Follow mean track: the mount will be steered to match the ground track. Follow desired heading: the mount will be steered on the planned angle of the flight line.
	Switching ON this option will correct the received GPS ellipsoidal altitudes to get orthometric heights (heights on the geoid). Default: ON.

9.5.2. Settings in Applanix POSView program

Make sure the following settings are made in POSView Ethernet Real-Time Port 2:

Enable the following groups:

• 1: Navigation solution

• 3: Primary GNSS Data

• 5: Event 1

• 200: Gimbal Encoder Data

• 203: Gimbal Yaw Drift Correction Data

• 222: Reference frame Navigation solution, only if you use direct control of the mount with the special handler for somag mount V2 (by default group 222 is not activated).

  

Store the settings in PosView:

9.6. Setting up Applanix AP+

SensorHandler needs two ports to communicate with Applanix AP+:

• TCP/IP to get navigation data (it is usually defined as port 28001)

• TCP/IP to get event information (it is usually defined as port 28002)

9.6.1. Definition in web interface of Applanix AP+

Ports 28001 and 28002 are used. These are the default ports but other port numbers can also be used.

Definitions for navigation data (port 28001):

Definitions for event port (28002):

9.6.2. Settings in SensorHandler

Integrating Applanix AP+ in SensorHandler

1. In SensorHandler, add IMU / Applanix AP+ to one of the buttons:

   

2. Click on Ethernet button to define the address and port of navigation data:

   

3. In one of the combo boxes, select Applanix AP+. Enter the IP address of AP+. In this example it is 10.8.121.90. Then set the port for receiving the navigation data:

   

4. Click on the Applanix AP+ button:

   

5. Tick the option to trigger images if Applanix is to trigger the images and enter the port number through which the event numbers will be received.

   

6. Set the option Mount is controlled by Applanix if the mount is connected to Applanix AP+. In this case, do NOT define a special mount button in SensorHandler:

   

Important

Note for conducting Riegl scanners

If the images will be released through the RiAcquire interface, then do NOT enable the Trigger images option:

Enable it in the RiAcquire dialog instead:

9.6.3. Remarks for controlling a gyro mount

If the system is leveled using a mount, the corresponding option must be set.

The figure shows that the mount is switched to STAB mode 30 seconds before the start of the line.

Important

The mount will only switch to STAB mode (unfreeze) when the aircraft is inside the corridor.

The green box signifies that the mount is in MAN mode (freeze). The aircraft is outside the corridor, so the two buttons (set manually ON, set manually OFF) can be activated.

The green box signifies that the mount is in STAB mode (unfreeze). The aircraft is inside the corridor. Therefore, the two buttons (Set manually ON, set manually OFF) cannot be activated.

A prompt indication of whether the mount is in stabilization mode is provided through the icon displayed in the main window of the NAVIGATOR program, see Status of MNT - SOMAG Mount.

9.7. Setting up Applanix GSOF in AVX 210

9.7.1. Settings for GSOF in SensorHandler

Adjusting the settings in SensorHandler

1. In SensorHandler, click on the Ethernet button to check IP address and port.

   
2. The standard IP address is 192.168.53.100

   The standard port for navigation data is 5017
   

3. Open the GSOF dialog by clicking on the IMU Applanix GSOF button in SensorHandler.

4. Then click the Settings button.

   

5. Adjust the settings:

   

   In the standard case navigation data from this IMU is used for navigation. So, for default settings, select the first option.

   The port 5018 is the default port through which the event ID arrives as soon as an image has been taken. The event id is recorded in the log files and submitted to iXCapture to tag the file names correctly.

   The EGM96 option is switched on, by default. This means that the altitudes are referenced to the EGM96 geoid. If this option is switched off, displayed altitudes will be referenced to the WGS84 ellipsoid.

9.7.2. Settings for GSOF in AVX210

The following GSOF messages need to be transmitted:

The following NMEA message needs to be transmitted:

Hint

Background information: NMEA altitudes are referenced to the EGM96 geoid. Most often, the planned altitudes for the lines of flight are also referenced to the EGM96. GSOF Message 9, however, is referenced to the WGS84 ellipsoid. In most cases, the flight has to be done on EGM96 altitudes. Therefore, NMEA GGA needs to know the difference between EGM96 and WGS84 altitudes.

9.8. Setting up NMEA

9.8.1. Setting up NMEA GPS in SensorHandler

Defining the button to connect to GPS NMEA

1. In the main sensor list, right click on the button where you want to place the GPS NMEA connection.

   

2. Select GPS / NMEA Serial or UDP.

3. The button is now connected with GPS NMEA.

   

Hint

Remember to define the port (COM or TCP) through which the device can be reached.

9.8.2. Settings for NMEA in SensorHandler for TCP/IP or UDP

NMEA settings in SensorHandler fro TCP/IO or UDP

1. Populate one of the buttons with GPS NMEA handler.

   

2. In SensorHandler, click on the Ethernet button to check the IP address and port.

   
3. The standard IP address is 192.168.53.100

   The standard port for all data is 5018
   

4. Open the NMEA dialog by clicking on the GPS NMEA serial or UDP button in SensorHandler.

5. Then click Settings button.

   
6. By default, navigation data enters via TCP/IP. In this case, select the first option.

   If data enters via UDP, then select the second option.

   If data enters through a serial port, then the settings will be disregarded by the software.
   

   The standard case is that navigation data from this IMU is used for navigation. So, by default, select the first option.

9.8.3. Settings for NMEA in AVX210

If NMEA is the protocol, then use the settings shown below:

9.8.4. Settings NMEA for NOVATEL

To synchronize PhaseOne image line and image ID with the image names you need to log MARKTIME sentences:

MARKTIME ICOM1 0 66.5 FINESTEERING 2137 131289.096 02004000 292e1599017.999999999 VALID

This allows SensorHandler and iXCapture to synchronize the event id, line id and image id. The image file name then can also contain the line and image id.

9.9. Using the SOMAG mount handler

9.9.1. The two main configurations

Important

To control the SOMAG mount this question must be answered: which device controls the mount?

Is it a) the Flight Management system or b) the INSS?

If using POS AV, then a) and b) can both be applied.

If using Novatel, then only a) is possible.

1 POS AV or any other INSS sends position data to the FMS. This is usually done by ethernet but it can also be done by serial communication.		1 POS AV sends position data to the FMS. The FMS sends freeze / unfreeze to POS AV
2 The FMS is connected to the mount by a serial port. The FMS does the whole control of the mount: Changing to STAB and MAN before and after the line Sending pitch, roll and yaw corrections to the mount Reading the mount angles		2 POS AV is connected to the mount. POS AV fully controls the mount: Changing to STAB and MAN before and after the line Sending pitch, roll and yaw corrections to the mount Reading the mount angles
No mount angles are logged.		The mount angles can be logged on POS AV.

Configuration 1: Settings for the mount controlled by FMS

1. One of the buttons needs to be populated with the INSS being used (select one of those):

   

2. In SensorHandler, select the SOMAG_V2 on one of the buttons:

   

3. In SensorHandler, click on COM ports to define the com port the mount is connected to:

   

4. In the list, select the SOMAG_V2.

5. Then select the com port and baud 4 by clicking the button on the left.

   

6. Set Baud rate to 115’200

Configuration 2: Settings for the mount controlled by POS AV

1. Since the mount is controlled by POS AV, only the POS AV is required on a button (no SOMAG driver has to be selected):

   

2. In SensorHandler, click on the Ethernet button:

   

3. In one of the lists, select Applanix POS AV. Set the IP Address and display port:

   

4. Click on the Applanix POS AV button

   

   and then on the Settings button

   

5. Enter the following settings:

   

9.9.2. Basic modes of operation

This handler is used to control all the gyro mounts of the SOMAG AG Jena, running Protocol Version 2.0 .

In standard mode, the mount will be set to STAB mode before the line of flight starts and will be set to MAN mode after the line has been finished or when the line is left. The following angles need to be known to drive the mount accurately to the needed position:

• pitch, roll, heading angles coming from the IMU

• ground track heading coming from the GPS

• actual yaw angle of the mount

• the desired heading angle the mount should to be driven to. This heading angle can either be the heading of the planned line of flight or of the ground track.

For special cases (like testing the mount), the automatic control of the mount can be switched off:

After switching off the automatic mode, the mount won’t switch between MAN and STAB mode automatically. This mode is mostly used for testing system components like communication and behavior of the mount.

9.9.3. Pre-flight settings

	By default, heading corrections are switched ON. This means that the IMU yaw angle will be corrected in accordance with the received IMU angles. SensorHandler requires the actual yaw of the gimbal in order to calculate the amount of correction for accurate yaw positioning of the mount. Here, you set the time intervals in which actual gimbal angles are sent to SensorHandler. Normally, a value of 100 milliseconds is used. Select the method for heading correction: Heading correction in STAB mode: this is the default. The mount is set to STAB mode at the start of the line and to MAN mode after having left the line. Heading correction in MAN mode: in this mode, the mount’s heading correction is carried out only by SensorHandler. No correction will be performed by the mount. This mode can be useful for ground tracks with short and intense changes in the heading (e.g. flying along a river or road by helicopter). Set drift to Planned Heading: this is the default. TOPOFLIGHT NAVIGATOR sends the line’s heading to SensorHandler. SensorHandler then sends small corrections to the mount to accurately align it with the line’s heading. Set drift to Ground Track: the yaw angle of the mount will be directed towards the ground track. The following sketch illustrates the distinction between the modes Set Drift to Ground Track (on the left) and Set Drift to Planned Heading (right):
	The default position is switched ON. This means that roll and pitch angles coming from the IMU are used to increase the accuracy of the mount’s stabilization process during flight.
	In the edit fields, you define how many seconds before the start of the line of flight the mount will go into STAB mode and how many seconds after the end of the line of flight the mount will switch back to MAN mode.

9.9.4. Automatic transition between STAB and MAN mode

	While on the line of flight the mount is automatically set to STAB mode
	After having left the line of flight the mount is automatically switched back to MAN mode

9.9.5. Manual transition between STAB and MAN mode

	switches back to automatic mode
	sets the STAB mode for all axes (roll, pitch, yaw)
	STAB mode is switched off and MAN mode is activated
	When the FMS control is switched OFF the mount can only be manually driven with using the SOMAG app. In this case, no commands from SensorHandler will be received. When the FMS control is switched ON the mount is driven only by SensorHandler. No commands from the SOMAG app will be received.

9.9.6. For system integrators: COM port settings

The SOMAG mount and SensorHandler communicate through serial communication, requiring accurate configuration of the corresponding COM port settings.

COM port configuration

1. Right click on a free button and add Platform SOMAG_V2 to the sensor list.

2. Click on COM ports button:

   

3. In the COM ports dialog select a combo box and the SOMAG_V2 driver.

4. Select the correct COM port.

   

5. These are the correct settings:

   

Tip for system Integrators

Important

Read the section below on how to verify the proper functionality of SensorHandler in conjunction with the SOMAG mount!

Often, when integrating a system, you have the mount on the table but do not yet have an IMU available. Switch the mount without a connected IMU to STAB mode. You will notice that the mount moves slightly to the end stops (it does not really stabilize). But you can check if SensorHandler and mount behave correctly.

You can perform this system check by forcing SensorHandler to send the mount gimbal angles back to the mount as simulated IMU values. Then the mount will be stabilized on the table. Do the following:

Verifying proper functionality of SensorHandler and SOMAG mount

1. In SensorHandler click Settings / Advanced Options.

   

2. On the top some tabs appear:

   

3. Select the tab Test2.

   

4. Enable the option to send the gimbal values back to the gimbal as IMU values.

   

5. Fly a line in simulation mode. The mount should be stabilized now, confirming the accurate communication between the mount and SensorHandler.

9.10. Setting up ITRES sensor handling

This chapter explains how to connect an ITRES sensor to SensorHandler.

Installation of ITRES sensor in SensorHandler

1. Attach ITRES sensor to one of SensorHandler’s buttons. Right click on the next free button in the sensor list to add ITRES sensor to one of the free buttons.

   

2. In the popup menu select camera/ITRES.

   

3. The ITRTES sensor interface is now visible.

   

4. Click on the Ethernet button to define the connection to ITRES.

   

5. In the next free list box select ITRES and set the IP address and port.

   

6. Click on ITRES button.

   

7. In ITRES window click on the Settings button.

   

8. Define the following values:

   • how many seconds before the line of flight the sensor starts

   • how many seconds after the line of flight the sensor stops.

   
9. Starting ITRES sensor for production

   At system start up click on the red button on the right side. After successfully connecting, all lights turn green.
   

9.11. Setting up Robincop sensor handling

	As the airplane is aligned to the flight line and passed the defined time, an Acquire dark frame command is sent to the system.
	As the airplane passes this time marker, Navigator will be informed that the airplane approaches the first point. This command is not used right now.
	As the airplane passes this time marker, the start logging command will be sent to the system.
	As the airplane passes this time marker, an Acquire dark frame command will be sent to the system followed by a stop logging command.
	When the airplane leaves the corridor (before it reached the end of the line) and does not enter within the defined time then a stop logging command will be sent to the system.