QUANTUM-SYSTEMS FAQ

No search

TRINITY

Aircraft
Specifications
Dimensions and Masses
Trinity F90+
Maximum take-off mass: 5.5 kg
Wing span: 2.394 m
Fuselage length: 1.491 m
Maximum payload capacity: 1.0 kg
Transport case dimensions: 1002x830x270 mm
Total weight with equipment and packaging: ... kg
Trinity PRO
Maximum take-off mass: 5.75 kg
Wing span: 2.394 m
Fuselage length: 1.491 m
Maximum payload capacity: 1.0 kg
Transport case dimensions: 1002x830x270 mm
Total weight with equipment and packaging: ... kg
Performance
Trinity F90+
Maximum flight time (default): 60 min
Maximum flight time (unlocked): 90+ min
Design cruise speed: 17 m/s
Maximum cruise speed: 18 m/s (with Qube240 / Oblique)
Maximum wind tolerance hover: 9 m/s
6 m/s (Qube240 / Oblique)
Maximum wind tolerance cruise: 12 m/s
Maximum transition altitude: 40 m
Maximum take-off altitude: 4000 m
Maximum flight altitude: 4500 m
Trinity Pro
Maximum flight time (default): 60 min
Maximum flight time (unlocked): 90+ min
Design cruise speed: 17 m/s
Maximum cruise speed: 18 m/s (with Qube240 / Oblique)
Maximum wind tolerance hover: 11 m/s
8 m/s (Qube240 / Oblique)
Maximum wind tolerance cruise: 12.9 m/s (locked)
14 m/s (unlocked)
Maximum transition altitude: 60 m (transition)
80 m (retransition)
Maximum take-off altitude: 4800 m
Maximum flight altitude: 5500 m
GNSS receivers of Trinity and iBase and used GNSS networks

Type:  Information       Solved problems: 0       Updated: 2023-09-29

The Trinity and the iBase use the Ublox ZED-F9P. It supports GPS, GLONASS, Galileo and Beidou satellite systems.

Operation
General
Rotating propeller hit the ground or an object.

Type:  Damage       Solved problems: 0       Updated: 2023-09-14

You should replace the propeller. Even there is no visible damage, the propeller can be damaged. Because of the rotating force while flying, the propeller can break which would lead to a crash of the drone. To replace the propeller please follow our repair manual which you can find below. 
 

Video

Actuator Malfunction is shown in QBase during Preflight Check

Type:  Damage       Solved problems: 25       Updated: 2023-09-29

The most likely reason is a incorrectly aligned tilt mechanism. One of the three motors is not going to the correct position due to a skipped tooth on the servo belt.
1. Please identify the motor(s) that is not tilting up to the correct position. An incorrectly aligned motor is only tilting up to ∼30° instead of ∼45° or will never reach horizontal position.
2. If the tools are available please follow the attached instructions for recalibrating the corresponding tilt servo.

PDF

3. If the tools are not available please follow the attached instructions in order to realign the motors. Depending on your serial numbers different instructions apply.
Serial Number 620 or higher:

PDF

Serial Number below 620:


PDF

Trinity deviates much from the planned flight path

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-29

A deviation from the planned flight path can be caused by multiple problems:

  1. Wind conditions differ from the conditions during planning - If the wind direction or magnitude changes, the autopilot has to adjust the flight path accordingly. You can also simulate different wind conditions in QBase to see the effects on flight. If there is high crosswind, the Trinity will fly the turns as 'teardrop' shape in order to align correctly with the next flight leg before the leg is entered. If there is high tail wind, the Trinity will not be able to climb as fast as simulated, which might result in reduced altitude over ground.
  2. The altitude model is not correct - if the altitude model differs from the real altitudes, great offsets in flight altitude to the planned flight may arise. If you notice the Trinity flying much lower than planned, please initiate coming home or even immediate retransition if the situation is critical.

Weather
Legal
Battery
Specifications
Trinity F90+
Mass: ... kg
Charging time: 1.0 - 1.5 h
Cell setup: 6S4P
Cell type: Lithium ion
Design life: 150 cycles
Nominal voltage
(single cell): 		3.6 V
Nominal voltage
(total): 		21.6 V
Max. voltage
(single cell): 		4.17 V
Max. voltage
(total): 		25.0 V
Rated capacity
(single cell): 		3,000 mAh
Rated capacity
(total): 		12,000 mAh
Trinity PRO
Mass: ... kg
Charging time: 1.0 - 1.5 h
Cell setup: 6S4P
Cell type: Lithium ion
Design life: 150 cycles
Nominal voltage
(single cell): 		3.6 V
Nominal voltage
(total): 		21.6 V
Max. voltage
(single cell): 		4.17 V
Max. voltage
(total): 		25.0 V
Rated capacity
(single cell): 		3,000 mAh
Rated capacity
(total): 		12,000 mAh
Safety Instructions
Charging
Charging Trinity battery in a car

Type:  Information       Solved problems: 0       Updated: 2023-09-14

The battery charger of the Trinity has a 12 V DC input. It is delivered including 12 V power clamps which can be connected to a car battery. The allowable DC input is 11-18 V, the allowable AC input is 100-240 V. Since the Trinity batteries have a high capacity, please make sure you don't drain your car battery empty during charge.
 

BID incompatible is shown in the Charger

Type:  Malfunction       Solved problems: 6       Updated: 2023-09-29

Please try to reset the BID chip of the battery.
Firmware and Software can be found here.
Instruction:

PDF

What is the maximum charging cycle of the battery?

Type:  Information       Solved problems: 1       Updated: 2023-09-18

The maximum charging cycles and the linked warranty are defined in the user manual.

After 150 charging cycles it is recommended to exchange the UAV Battery pack. In order to check the amount of charging cycles please check the BID Info menu on the charger – therefore, the battery must be connected to the charger.

The battery will age over time. Therefore, the warranty of the complete UAV system expires when batteries with more than 150 charging cycles are used.

Batteries itself are not covered as part of the standard warranty (see chapter 2.2.4)

Disposal
Operation
Does the Trinity automatically return home due to low battery?

Type:  Information       Solved problems: 0       Updated: 2023-09-14

Yes, the Trinity F90+ permanently compares the remaining battery capacity with the remaining flight time. An automatic coming home due to battery (Battery Critical) is initiated if the remaining capacity is required for a safe coming home, retransition and landing.

Repair
Rotating propeller hit the ground or an object.

Type:  Damage       Solved problems: 0       Updated: 2023-09-14

You should replace the propeller. Even there is no visible damage, the propeller can be damaged. Because of the rotating force while flying, the propeller can break which would lead to a crash of the drone. To replace the propeller please follow our repair manual which you can find below. 
 

Video

My Trinity crashed and was destroyed. How can I get a replacement?

Type:  Damage       Solved problems: 0       Updated: 2023-02-03

If your Trinity has still been under warranty and the crash was caused by a technical malfunction, your Trinity will probably be replaced. Please be aware that your local reseller is responsible for the replacement according to the local warranty regulations of your country. If the Trinity is not covered under warranty, the main body and rear part can be purchased as 'Fly kit' at a reduced price. Wings, elevator and battery are always available as normal spare parts.
 

Packaging and Transport
QBase
General
Mission
Wrong Direction is shown in QBase and the take-off is aborted

Type:  Error       Solved problems: 0       Updated: 2023-09-14

Wrong Direction is shown if the Trinity F90+ is not able to turn into the transition cone as previously defined in Qbase due to crosswind. The transition cone shows the allowed transition direction.
In order to make sure to prevent a start abort due to Wrong Direction please plan the transition direction facing headwind (if possible) and open the transition cone as wide as safely possible. Make sure the transition direction is free of obstacles.

What are the features of QBase Pro and how to activate it?

Type:  Information       Solved problems: 0       Updated: 2023-09-14

  1. The 3D viewer is a pro feature of QBase and disabled in the light version. The SRTM data it self is available but the 3D view in Qbase is not avaiable.
  2. The kml import manager is also a feature that is only available in the QBase Pro Version.

To activate:

Please create an account in the main menu under Settings 🠖 Account. Then connect a Trinity via magnetic USB while logged in QBase. This enables the pro features for your account. The pro status will be permanent. It is not linked to a UAV serial number, so any Trinity can be used to activate the pro version and multiple accounts can be activated with the same Trinity. There are no costs linked to an account creation or activation. The account feature is necessary for us to make sure only Trinity customers can use the licensed pro features of QBase.

Settings
Trinity deviates much from the planned flight path

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-29

A deviation from the planned flight path can be caused by multiple problems:

  1. Wind conditions differ from the conditions during planning - If the wind direction or magnitude changes, the autopilot has to adjust the flight path accordingly. You can also simulate different wind conditions in QBase to see the effects on flight. If there is high crosswind, the Trinity will fly the turns as 'teardrop' shape in order to align correctly with the next flight leg before the leg is entered. If there is high tail wind, the Trinity will not be able to climb as fast as simulated, which might result in reduced altitude over ground.
  2. The altitude model is not correct - if the altitude model differs from the real altitudes, great offsets in flight altitude to the planned flight may arise. If you notice the Trinity flying much lower than planned, please initiate coming home or even immediate retransition if the situation is critical.

Waypoints
Saved Missions
Post Processing
Files
Where to find Flylogs and Logfiles of the Trinity F90+ and Pro

Type:  Information       Solved problems: 0       Updated: 2023-09-29

Trinity F90+

  1. Connect your Trinity to your computer via USB and wait for the connection to be established.
  2. Open QBase
  3. Click on "Tools --> SD Card". Your computer will open an explorer window with the Trinity's internal SD card. Logfiles and flylogs will be listed named "LOG_XXXX.BIN" and "FLY_XXXX.BIN" with "XXXX" representing a number. Logfile and flylog of the same flight will have the same number. Numbers are counted up consecutive, meaning the highest number refers to the latest flight.

Trinity Pro

  1. Connect the battery to the main body.
  2. Connection of the main body
    1. Connect the main body of the UAV to your computer, laptop or tablet via the USB-C connection.
      Open 10.41.1.1 in your browser
    2. Connect the main body of the UAV to your computer, laptop or tablet via the WIFI connection. Please connect to the Trinity Pro via WiFi. Network: QS_Trinity_X Password: 1234567890 Open 10.41.2.1 in your browser
  3. An online interface will be opened in the browser.
  4. Open the first tab LOGS to show all the logs stored on the Trinity Pro. The logs are ordered according to the date.
  5. Please download the corresponding log by selecting it. A log indicating a flight is marked with PFC - the download includes the payload Log (.PLD) and the LogFile (.FMU) with their corresponding preflight recording (.PLD_PRE and .FMU_PRE)
  6. Save the files on your computer.

Reference data / Rinex Data Issues during post-processing

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

At first please look if you have the right reference data used (same date and time). The time of the flight data should be included in the time of the reference data recorded. There are several sources where you can find additional reference data, see attached.

Please make sure that the reference data is recorded with 1Hz.

Please also make sure that the file format of the reference data is standard Rinex file.

Furthermore, the reference data should be recorded within a 50 km radius around the flight area (closer is better).

PPK Files
Flylogs
Propeller
CSV
KML
Error Messages
Wrong Direction is shown in QBase and the take-off is aborted

Type:  Error       Solved problems: 0       Updated: 2023-09-14

Wrong Direction is shown if the Trinity F90+ is not able to turn into the transition cone as previously defined in Qbase due to crosswind. The transition cone shows the allowed transition direction.
In order to make sure to prevent a start abort due to Wrong Direction please plan the transition direction facing headwind (if possible) and open the transition cone as wide as safely possible. Make sure the transition direction is free of obstacles.

Payload
Sony UMC
Specifications
Sensor type: CMOS RGB
Sensor size: APS-C
Sensor resolution: 20.4 MP
Focal length: 16 mm (default)
20 mm
Aperture: f2.8 - f22 (16 mm)
f2.8 - f16 (20 mm)
Field of view: 71.9° x 51.4° (16 mm)
60.2° x 42.1° (20 mm)
Max. shutter speed: 1/4000 s
Max. ISO: 16000
Safe min. trigger interval: 1.1 s
Image type: JPEG File Interchange Format (.jpg)
Image size: ~8.1 MB
General
Settings
Operation
QBase does not detect the camera

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

The Trinity main body does not communicate with the camera directly, only with the Payload Management Board (PMB) - which is the PCB integrated into the payload compartment.

  1. Please check whether the PMB is detected. Please click on the grey camera symbol in the QBase header. A menu will expand. Click on 'PMB technical data' to display the PMB data. If every value just reads zero, the PMB is not detected. Otherwise only the camera is not detected.
  2. If the PMB is not detected
    Check if the Trinity is detected at all. If there is still not connection to the PMB, try to reflash the firmware of the PMB via USB
  3. If the PMB is detected but the camera is not detected
    Please refer the corresponding entries in the camera sections.

Sony UMC is not detected at startup

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-22

Camera is not recognized on Trinity start up

1. Loose connection between the main and payload compartment

  • Connect the payload compartment to the UAV main body.
  • Connect the battery to the main and establish the modem connection to QBase.
  • Please check if the payload compartment is detected in QBase:
  • Select the camera symbol in the header section and open the dropdown window.
  • Is all sensor data green?
  • YES: connection between the main and the payload Compartment is okay. Continue with step
  • NO: please again update the latest PMB firmware (see chapter 7.5.4).

2. SD card format

  • Formatting the SD card via the windows directory
    (first quick format, if this is not successful: hard format).
  • Camera recognized after formatting?
  • YES: it was a SD card issue and the problem is solved.

3. Loose connection between the payload management board and the camera

  • Unplug the micro USB from the camera
  • Connect a micro USB cable to the Sony UMC and connect the cable to your computer.
  • Connect the payload compartment to the main body.
  • Connect the UAV battery to the main body.
  • Open camera control manager:
    https://www.sony.net/Products/CameraSystem/CA/UMC_S3C/
  • Please trigger the camera via the camera control manager.
  • Please change the folder from SD card to any directory on your computer to write the picture to the computer instead of the SD card.
  • Please trigger the camera
  • Is the picture saved on the computer?
  • YES: No connection issue between the payload management board and the camera. Must be an issue between the camera and the SD card (see step 4.).

4. Loose Connection between camera and SD card

  • See step 3, but please select SD card instead of computer as the folder when taking a picture via the camera control manager (the picture needs to be written to the SD card).
  • Is the picture saved on the SD card?
  • YES: No connection issue between the camera and the SD card. Please try to setup the UAV incl. payload again.
  • NO: Are all connections on the SD card PCB in place?
  •  YES: Please contact the Quantum-Systems Support

Sony RX1 RII
Specifications
Sensor type: CMOS RGB
Sensor size: Full frame
Sensor resolution: 42.4 MP
Focal length: 35 mm
Aperture: f2 - f22
Field of view: 54.3° x 37.8°
Max. shutter speed: 1/4000 s
Max. ISO: 25600
Safe min. trigger interval: 1.4 s
Image type: JPEG File Interchange Format (.jpg)
Image size: ~32 MB
General
Settings
Sony RX1 is not recognized

Type:  Malfunction       Solved problems: 11       Updated: 2023-09-25

Please check whether the PMB is detected Therefore, please see solution QBase does not detect the camera.

In case the Sony RX1 is not detected (grey ) in Qbase here are the common causes of failure:

  1. The camera should be always remain switched on
  2. Make sure the Manual Mode M is selected with the control wheel on top of the Camera.
  3. The required root folders were formatted from the SD card:
    1. Insert the SD card into the camera
    2. Directly power the camera via the Sony battery and turn on the camera
    3. Please confirm the start-up dialogue on the camera to reconfigure the root folders on the SD card
    4. Remove the battery without turning the camera off on the on-off switch
    5. Reinsert the battery dummy

Operation
QBase does not detect the camera

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

The Trinity main body does not communicate with the camera directly, only with the Payload Management Board (PMB) - which is the PCB integrated into the payload compartment.

  1. Please check whether the PMB is detected. Please click on the grey camera symbol in the QBase header. A menu will expand. Click on 'PMB technical data' to display the PMB data. If every value just reads zero, the PMB is not detected. Otherwise only the camera is not detected.
  2. If the PMB is not detected
    Check if the Trinity is detected at all. If there is still not connection to the PMB, try to reflash the firmware of the PMB via USB
  3. If the PMB is detected but the camera is not detected
    Please refer the corresponding entries in the camera sections.

Sony RX1 is not recognized

Type:  Malfunction       Solved problems: 11       Updated: 2023-09-25

Please check whether the PMB is detected Therefore, please see solution QBase does not detect the camera.

In case the Sony RX1 is not detected (grey ) in Qbase here are the common causes of failure:

  1. The camera should be always remain switched on
  2. Make sure the Manual Mode M is selected with the control wheel on top of the Camera.
  3. The required root folders were formatted from the SD card:
    1. Insert the SD card into the camera
    2. Directly power the camera via the Sony battery and turn on the camera
    3. Please confirm the start-up dialogue on the camera to reconfigure the root folders on the SD card
    4. Remove the battery without turning the camera off on the on-off switch
    5. Reinsert the battery dummy

Rainpoo Oblique D2M
Specifications
Sensor type: CMOS RGB
Sensor size: APS-C
Spectrum: RGB / visible
Number of sensors: 5 (4 x oblique, 1 x nadir)
Sensor format: 3:2
Sensor resolution: 5 x 26 MP
Focal length: 25 mm (nadir)
35 mm (oblique)
Aperture: f5.6
Field of view: 50° x 35° (nadir)
37° x 25° (oblique)
Max. shutter speed: ... s
Max. ISO: 1600
Safe min. trigger interval: 0.9 s
Image type: JPEG File Interchange Format (.jpg)
Image size: 5 x ~... MB
General
Settings
Operation
Rededge-P
Specifications
Sensor type: Multi spectral
Sensor size: 5.02 x 3.75 mm (multispectral)
8.5 x 7.09 mm (panchromatic)
Sensor format: 4:3 (multispectral)
6:5 (panchromatic)
Sensor resolution: 1.58 MP (per multispectral band)
5.1 MP (panchromatic)
Sensor spectrum
(center/bandwidth): 		blue 475/32 nm
green 560/27 nm
red 668/14 nm
red-edge 717/12 nm
near-IR 842/57 nm
pan 634.5/463 nm
Focal length: 5.5 mm (multispectral)
10.3 mm (panchromatic)
Max. aperture: f2.8 (multispectral)
f4.5 (panchromatic)
Field of view: 49.6° x 38.3° (multispectral)
44.5° x 37.7° (panchromatic)
Image type: Tagged Image File Format (.tiff)
Image size: 5 x ~3.1 MB (multispectral)
~9.9 MB
General
Settings
Operation
QBase does not detect the camera

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

The Trinity main body does not communicate with the camera directly, only with the Payload Management Board (PMB) - which is the PCB integrated into the payload compartment.

  1. Please check whether the PMB is detected. Please click on the grey camera symbol in the QBase header. A menu will expand. Click on 'PMB technical data' to display the PMB data. If every value just reads zero, the PMB is not detected. Otherwise only the camera is not detected.
  2. If the PMB is not detected
    Check if the Trinity is detected at all. If there is still not connection to the PMB, try to reflash the firmware of the PMB via USB
  3. If the PMB is detected but the camera is not detected
    Please refer the corresponding entries in the camera sections.

Rededge-MX
Specifications
Sensor type: Multi spectral
Sensor size: ...
Sensor resolution: ...
Focal length: ... mm
Max. aperture: ...
Field of view: ...
Image type: Tagged Image File Format (.tiff)
Image size: ... MB
General
Settings
Operation
QBase does not detect the camera

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

The Trinity main body does not communicate with the camera directly, only with the Payload Management Board (PMB) - which is the PCB integrated into the payload compartment.

  1. Please check whether the PMB is detected. Please click on the grey camera symbol in the QBase header. A menu will expand. Click on 'PMB technical data' to display the PMB data. If every value just reads zero, the PMB is not detected. Otherwise only the camera is not detected.
  2. If the PMB is not detected
    Check if the Trinity is detected at all. If there is still not connection to the PMB, try to reflash the firmware of the PMB via USB
  3. If the PMB is detected but the camera is not detected
    Please refer the corresponding entries in the camera sections.

Altum
Specifications
Sensor type: Multi spectral
Sensor size: ... mm (multispectral)
... mm (thermal)
... mm (panchromatic)
Sensor format: ... (multispectral)
... (thermal)
... (panchromatic)
Sensor resolution: ... MP (per multispectral band)
... MP (thermal)
... MP (panchromatic)
Sensor spectrum
(center/bandwidth): 		blue 475/32 nm
green 560/27 nm
red 668/14 nm
red-edge 717/12 nm
near-IR 842/57 nm
thermal ... mm
pan 634.5/463 nm
Focal length: ... mm (multispectral)
... mm (thermal)
... mm (panchromatic)
Max. aperture: ... (multispectral)
... (thermal)
... (panchromatic)
Field of view: ...° x ...° (multispectral)
...° x ...° (thermal)
...° x ...° (panchromatic)
Image type: Tagged Image File Format (.tiff)
Image size: 5 x ~... MB (multispectral)
~... MB (thermal)
~... MB (panchromatic)
General
Settings
Operation
QBase does not detect the camera

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

The Trinity main body does not communicate with the camera directly, only with the Payload Management Board (PMB) - which is the PCB integrated into the payload compartment.

  1. Please check whether the PMB is detected. Please click on the grey camera symbol in the QBase header. A menu will expand. Click on 'PMB technical data' to display the PMB data. If every value just reads zero, the PMB is not detected. Otherwise only the camera is not detected.
  2. If the PMB is not detected
    Check if the Trinity is detected at all. If there is still not connection to the PMB, try to reflash the firmware of the PMB via USB
  3. If the PMB is detected but the camera is not detected
    Please refer the corresponding entries in the camera sections.

Recording to a USB drive with the Micasense Altum

Type:  Information       Solved problems: 0       Updated: 2023-09-14

Using the USB stick for the Altum to take images will cause severe interference with the GNSS receiver of the Trinity, which can lead to a crash. Please always use the SD card adapter for storing images.

Altum PT
Specifications
Sensor type: Multi spectral
Sensor size: ... mm (multispectral)
... mm (thermal)
... mm (panchromatic)
Sensor format: ... (multispectral)
... (thermal)
... (panchromatic)
Sensor resolution: ... MP (per multispectral band)
... MP (thermal)
... MP (panchromatic)
Sensor spectrum
(center/bandwidth): 		blue 475/32 nm
green 560/27 nm
red 668/14 nm
red-edge 717/12 nm
near-IR 842/57 nm
thermal ... mm
pan 634.5/463 nm
Focal length: ... mm (multispectral)
... mm (thermal)
... mm (panchromatic)
Max. aperture: ... (multispectral)
... (thermal)
... (panchromatic)
Field of view: ...° x ...° (multispectral)
...° x ...° (thermal)
...° x ...° (panchromatic)
Image type: Tagged Image File Format (.tiff)
Image size: 5 x ~... MB (multispectral)
~... MB (thermal)
~... MB (panchromatic)
General
Settings
Operation
QBase does not detect the camera

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

The Trinity main body does not communicate with the camera directly, only with the Payload Management Board (PMB) - which is the PCB integrated into the payload compartment.

  1. Please check whether the PMB is detected. Please click on the grey camera symbol in the QBase header. A menu will expand. Click on 'PMB technical data' to display the PMB data. If every value just reads zero, the PMB is not detected. Otherwise only the camera is not detected.
  2. If the PMB is not detected
    Check if the Trinity is detected at all. If there is still not connection to the PMB, try to reflash the firmware of the PMB via USB
  3. If the PMB is detected but the camera is not detected
    Please refer the corresponding entries in the camera sections.

QUBE 240
Specifications
Sensor type: LiDAR
Sensor size: ...
Shots / second: 240,000
Wave length: 905 nm
Laser class: 1 (eye safe)
Field of view: 70° (horizontal)
Number of echoes: up to 3
Maximum range: 140 m
Precision: 1.8 - 2.5 cm
Accuracy: 3 cm
Mass (integrated): 935 g
General
Settings
STAT LED on Qube240 not turning solid on startup

Type:  Malfunction       Solved problems: 1       Updated: 2023-09-29

There could be several issues leading to the STAT LED not turning solid orange, all with the background of a disturbed GNSS reception.
1. A loose GNSS cable. Please check both ends of your GNSS cable both to the Qube240 and the GNSS antenna.
2. A damaged GNSS cable. It could've been damaged during transportation. If you can, try another GNSS cable.
3. Not enough satellite reception. This can have multiple reasons. Start by clearing the sky view from the antenna (ie. stay away from the system when it starts). Avoid having large masks around your location (tall trees, buildings, etc). Lastly, check the sky map by connecting to your system using Ethernet. You can find the procedure to connect to the Applanix board in the Qube User Manual below. Then, navigate to the sky map and verify you have enough satellites. There is a minimal requirement of 4 satellites to get to a ready state.

PDF

Operation
QBase does not detect the camera

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

The Trinity main body does not communicate with the camera directly, only with the Payload Management Board (PMB) - which is the PCB integrated into the payload compartment.

  1. Please check whether the PMB is detected. Please click on the grey camera symbol in the QBase header. A menu will expand. Click on 'PMB technical data' to display the PMB data. If every value just reads zero, the PMB is not detected. Otherwise only the camera is not detected.
  2. If the PMB is not detected
    Check if the Trinity is detected at all. If there is still not connection to the PMB, try to reflash the firmware of the PMB via USB
  3. If the PMB is detected but the camera is not detected
    Please refer the corresponding entries in the camera sections.

The t04 file is corrupted or missing.

Type:  Malfunction       Solved problems: 5       Updated: 2023-09-14

In case the t04 is not on the USB stick or is corrupted it can most likely be retrieved from the internal Applanix storage.

  1. Please connect the Qube240 to the Applanix interface according to chapter 5.4 of the Qube240 manual
  2. On the Applanix page:
    🠖 In the menu on the left side, select Data Logging.
    🠖 Click on /Internal and browse the daily folder to find the record with the name corresponding to your date of acquisition. Please note that time is in UTC reference.
    🠖 Click on the file name to start downloading the file and save it in your project folder.
    PDF

In order to prevent the issue in the future please

  1. make sure not to unplug the battery from the Trinity before the blinking sequence of the Qube240 is finished after the flight.
  2. To have the Qube240 USB stick formatted to NTFS format.
  3. to use the 128 GB Samsung USB stick that was provided with the Qube240.

STAT LED on Qube240 not turning solid on startup

Type:  Malfunction       Solved problems: 1       Updated: 2023-09-29

There could be several issues leading to the STAT LED not turning solid orange, all with the background of a disturbed GNSS reception.
1. A loose GNSS cable. Please check both ends of your GNSS cable both to the Qube240 and the GNSS antenna.
2. A damaged GNSS cable. It could've been damaged during transportation. If you can, try another GNSS cable.
3. Not enough satellite reception. This can have multiple reasons. Start by clearing the sky view from the antenna (ie. stay away from the system when it starts). Avoid having large masks around your location (tall trees, buildings, etc). Lastly, check the sky map by connecting to your system using Ethernet. You can find the procedure to connect to the Applanix board in the Qube User Manual below. Then, navigate to the sky map and verify you have enough satellites. There is a minimal requirement of 4 satellites to get to a ready state.

PDF

High Noise in the point cloud

Type:  Information       Solved problems: 0       Updated: 2023-09-14

Depending on the angle that the laser beams hit the ground the noise might be more or less. The steeper the angle the more accurate is the point cloud.
The noise of the point cloud can be reduced  by reducing the scanning angle in e.g. Cloud Compare.

Spikes in the point cloud

Type:  Information       Solved problems: 0       Updated: 2023-09-14

With certain sun ray orientations, bouncing off planar surfaces such as tin roofs that you can have in the urban areas, incoming photons will reach the encoder generating errors. These point panaches tend to occur when the sun has specific orientations – low in the horizon usually.

Holes in point cloud

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

Please make sure the USB stick has enough space prior to the mission. The LOG LED will be green if the space available is > 30 GB. The fact that there is less and less space on the USB drive probably slows down the writing speed from the lidar to the memory. As a consequence, these error messages could come up. Possible gaps in flights are unfortunately not recoverable

What is the process for the calibration of the Qube240?

Type:  Information       Solved problems: 1       Updated: 2023-09-29

Please provide the following data to have the data evaluated and the calibration file of the Qube20 adjusted. The Qube240 re calibration is recommended on a yearly basis.

  • raw lidar data (.lvx, .ys, .T04)
  • base station rinex file (.23O) with processed coordinates (lat, long, height, frame, epoch)
  • validated ground control check points with associated projection (Easting/Northing/elevation/frame/epoch) – taken on planar surfaces (no edges), preferentially hard surfaces like concrete or bitumen with no overhanging vegetation. Ideally control points should be spread out over the area of the health check to help assess the accuracy over the entire perimeter.
  • flight scene should contain 3d objects such as building (centered on the flight)
  • flight plan to be completed at 90mAGL with at least one ‘central’ flight line completed at 120mAGL.
  • flight pattern is done according to chapter 8.1 in the manual.
    PDF

Transmission
RC Transmitter
Specifications
Model: Multiplex Cockpit SX 9
Frequency: 2400 - 2483.5 MHz
Output power: 100 mW
General
Settings
Operation
Ground Modem
Specifications
Model: Microhard n2420
Frequency: 2400 - 2483.5 MHz
Output power: 100 mW
FCC ID: NS911P31
General
Settings
Operation
USB Connection
Operation
QBase does not connect with the Trinity via USB

Type:  Error       Solved problems: 10       Updated: 2023-01-24

This can have multiple reasons:
1. A previous firmware update was unsuccessful. In that case, the Trinity will probably not power up at all. To fix this, please repeat the firmware update according to the instructions in the Trinity F90+ manual in chapter 7.5.3. It will be possible even if the Trinity is not detected before the update.
2. The flight controller did not boot in USB mode. If the battery is attached to the main body before the USB connection is established, the autopilot will boot in normal mode instead than USB mode. That way, it will not be recognized via USB. Please disconnect the battery and USB and connect the USB cable again.
3. The USB connection is unstable. Check if the contact surfaces of the magnetic plugs are clean. Attach the magnetic plug first and the USB-A plug to the computer afterwards to prevent connection loss during plugging. Try another USB cable. Check if the micro-USB-B to magnetic-USB adapter is plugged into the main body correctly. Slightly press it down to ensure it fully sits in the micro-USB socket.
4. In some cases, Windows assigns the Trinity to a COM port already in use. In this case the COM port must be changed. To do so open the device manager --> Ports (COM&LPT) and right click on USB Serial Port and choose Properties. Switch to the Port Settings tab and click Advanced. A new window will open where you can choose a different COM port.
5. Please reinstall the driver according to the Trinity F90+ manual chapter 7.1.3

Remote ID
What is the difference between Remote ID and ADS-B?

Type:  Information       Solved problems: 0       Updated: 2023-09-14

The difference between the ADS-B transponder and the Remote ID is that the ADS-B transponder sends out an ADS-B signal which is a signal dedicated for aviation monitoring, especially for commercial and manned aircraft. This ensures that the Trinity can be seen by the aviation authorities.
The Remote ID sends a 2.4 GHz WiFi based signal which is working via app. Individuals have the possibility to see the drones that are around which will be required by the EU legislation from beginning of 2023.

Specifications
Trinity F90+
Compliance: FAA 14 CFR Part 89
EU CIR 2019/947
Mass: ... g
Output power: ... mW
Output frequency: ... MHz
Trinity Pro
Compliance: FAA 14 CFR Part 89
EU CIR 2019/947
Mass: ... g
Output power: ... mW
Output frequency: ... MHz
Operation
Settings
Remote ID settings

Type:  Information       Solved problems: 1       Updated: 2023-01-27

To change the Remote ID settings a connection via the QBase modem must be established. 

Operator ID: Only use those an operator ID provided by the authorities. Flight Description: Please insert the aim of the flight.
Technical data: Power: 20 mW Frequency: 2.4 GHz (Wifi)

Please see Trinity F90+ manual chapter 7.2.1

ADS-B
What is the difference between Remote ID and ADS-B?

Type:  Information       Solved problems: 0       Updated: 2023-09-14

The difference between the ADS-B transponder and the Remote ID is that the ADS-B transponder sends out an ADS-B signal which is a signal dedicated for aviation monitoring, especially for commercial and manned aircraft. This ensures that the Trinity can be seen by the aviation authorities.
The Remote ID sends a 2.4 GHz WiFi based signal which is working via app. Individuals have the possibility to see the drones that are around which will be required by the EU legislation from beginning of 2023.

Specifications
Ping 5S
Mass: 15 g
Output power: 5000 mW
Output frequency: 1090 MHz
Operation
Settings
Data Processing
Photogrammetry General
The processing results differ in AgiSoft and Pix4D.

Type:  Error       Solved problems: 0       Updated: 2023-09-14

The CSV file containing the coordinates, angles and accuracies is different between AgiSoft and Pix4D. When creating the CSV during the post processing process in QBase the output needs to be selected (Pix4D or AgiSoft).
If this does not help, please compare the CSV's generated for Agisoft and Pix4D regarding geotags and accuracies. If they are identical, the problem is caused by some settings or the workflow of your photogrammetry software. If not, please contact your local reseller for help.
You can also try to use the geotagged images without an additional CSV to see if it improves the result.
 

Images
SD Card
Reference Stations
Cloudstation & Pospac
High Noise in the point cloud

Type:  Information       Solved problems: 0       Updated: 2023-09-14

Depending on the angle that the laser beams hit the ground the noise might be more or less. The steeper the angle the more accurate is the point cloud.
The noise of the point cloud can be reduced  by reducing the scanning angle in e.g. Cloud Compare.

Spikes in the point cloud

Type:  Information       Solved problems: 0       Updated: 2023-09-14

With certain sun ray orientations, bouncing off planar surfaces such as tin roofs that you can have in the urban areas, incoming photons will reach the encoder generating errors. These point panaches tend to occur when the sun has specific orientations – low in the horizon usually.

Holes in point cloud

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

Please make sure the USB stick has enough space prior to the mission. The LOG LED will be green if the space available is > 30 GB. The fact that there is less and less space on the USB drive probably slows down the writing speed from the lidar to the memory. As a consequence, these error messages could come up. Possible gaps in flights are unfortunately not recoverable

CloudStation error message C0x000105 when opening CloudStation.

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

This can be caused by your firewall preventing you from reaching the license server. Open ports 5053, 5522 and 5479 in the firewall settings and try again. 

What is the process for the calibration of the Qube240?

Type:  Information       Solved problems: 1       Updated: 2023-09-29

Please provide the following data to have the data evaluated and the calibration file of the Qube20 adjusted. The Qube240 re calibration is recommended on a yearly basis.

  • raw lidar data (.lvx, .ys, .T04)
  • base station rinex file (.23O) with processed coordinates (lat, long, height, frame, epoch)
  • validated ground control check points with associated projection (Easting/Northing/elevation/frame/epoch) – taken on planar surfaces (no edges), preferentially hard surfaces like concrete or bitumen with no overhanging vegetation. Ideally control points should be spread out over the area of the health check to help assess the accuracy over the entire perimeter.
  • flight scene should contain 3d objects such as building (centered on the flight)
  • flight plan to be completed at 90mAGL with at least one ‘central’ flight line completed at 120mAGL.
  • flight pattern is done according to chapter 8.1 in the manual.
    PDF

Agisoft
Pix4D
Equipment
iBase
Settings
Operation
Accuracy when processing with iBase file.

Type:  Information       Solved problems: 8       Updated: 2023-07-28

The iBase is a GNSS receiver with the normal absolut GNSS accuracy of 1-2 meters. 
If the iBase is only positioned on the ground the position of the iBase is able to determine its own position within this accuracy. 
When only taking the iBase file the absolute accuracy will then be within the accuracy of 1-2 meters. The relative accuracy will be independent of this within 2-3 cm (depending on camera and GSD). 
The best way to use the iBase is setting the iBase up on a known point - a point with exact coordinates which have been measured previously.
These coordinates can then be used in QBase post-processing together with the iBase file.
The entire PPK post processing will then be referred to these exact coordinates. 

GNSS receivers of Trinity and iBase and used GNSS networks

Type:  Information       Solved problems: 0       Updated: 2023-09-29

The Trinity and the iBase use the Ublox ZED-F9P. It supports GPS, GLONASS, Galileo and Beidou satellite systems.

Reference data / Rinex Data Issues during post-processing

Type:  Malfunction       Solved problems: 0       Updated: 2023-09-14

At first please look if you have the right reference data used (same date and time). The time of the flight data should be included in the time of the reference data recorded. There are several sources where you can find additional reference data, see attached.

Please make sure that the reference data is recorded with 1Hz.

Please also make sure that the file format of the reference data is standard Rinex file.

Furthermore, the reference data should be recorded within a 50 km radius around the flight area (closer is better).

No data is written to the iBase

Type:  Malfunction       Solved problems: 2       Updated: 2023-02-03

If the iBase is not recording please check the following options: 
1. Is the LED turning green If not please check the power supply. If yes please continue with step 2. 
2. Does the LED start blinking indicating the logging is successful If not please check step 3; if yes please check step 4. 
3. Is the antenna connected to the iBase properly Is the antenna pin damaged 
4.  Does the iBase SD card contain the config.txt file in the root directory This is mandatory.
 

Charger
Settings
Operation
Charging Trinity battery in a car

Type:  Information       Solved problems: 0       Updated: 2023-09-14

The battery charger of the Trinity has a 12 V DC input. It is delivered including 12 V power clamps which can be connected to a car battery. The allowable DC input is 11-18 V, the allowable AC input is 100-240 V. Since the Trinity batteries have a high capacity, please make sure you don't drain your car battery empty during charge.
 

BID incompatible is shown in the Charger

Type:  Malfunction       Solved problems: 6       Updated: 2023-09-29

Please try to reset the BID chip of the battery.
Firmware and Software can be found here.
Instruction:

PDF

Miscellaneous
Where can I find the latest manuals?

Type:  Information       Solved problems: 0       Updated: 2023-07-31

All the latest manuals are downloaded with the current QBase installer. All relevant user manuals are stored locally on your computer in Documents - QBase - Manual. 

Log Files cannot be unzipped

Type:  Error       Solved problems: 1       Updated: 2023-09-04

In case the downloaded log files cannot be unzipped please follow the steps as below.

  1. Please download the WinSCP tool: https://winscp.net/eng/download.php
  2. Please connect the battery to the Trinity Pro and connect the Trinity Pro to your computer via USB-C.