Airsight NextCore RN50 User manual
NextCore RN50 User Guide
Version 1.1
1 Revisions 3
1.1 Documentation 3
1.2 Software 3
1.3 Hardware 3
2 Introduction 4
3 Disclaimer 5
4 List of Items 5
4.1 Nextcore RN50 5
4.2 M600 Mounting Kit 5
4.3 Custom Pelican Hard Case 5
5 M600 Installation 6
5.1 Recommend Tools 6
5.2 M600 Configuration 6
5.2.1 Vibration Isolators 6
5.2.2 Power Installation 7
5.2.3 API Configuration 8
5.2.3.1 Cable Installation 8
5.2.3.2 API Settings Configuration 9
6 NextCore Installation 10
6.1 Standard Installation Workflow 10
6.2 Attaching the M600 mount kit 11
6.3 Antenna Installation 12
6.4 Mechanical Drawings 13
6.5 RN50 Pinout 13
6.6 Mounting the payload to an M600 14
7 Mission Planning 15
7.1 Manual vs Grid Flights 15
7.2 Key Considerations 15
7.3 Suggested operating parameters 17
7.4 Flight Planning with DJI GS Pro 18
7.4.1 Grid mission setup 18
8 Operating Payload 20
8.1 Standard Data Capture Workflow 20
8.2 Data Capture 20
8.2.1 Manual Capture 20
Version 1.1
NextCore RN50 User Guide
1
8.2.2 Auto Capture 21
8.3 Status Description 21
8.3.1 Led Status 22
8.3.2 Oled Status 22
9 NextCore Software 23
9.1 Basic information 23
9.1.1 Installation 23
9.1.2 Calibration 23
9.1.3 Data Management 23
9.1.4 Initial Interface 24
9.2 Live Telemetry & Data Download 24
9.3 Payload USB Control 24
9.4 Batch Process 24
9.5 Process Dataset 25
9.5.1 Standard Data Processing Workflow 25
9.5.2 Post Processing 26
9.5.3 Flight Line Selection 28
9.5.4 Fusion Settings 30
9.5.4.1 Fusion 32
9.5.4.2 Combined Decimation: 32
9.5.5 Export Settings 33
9.5.5.1 Export Paths 33
9.5.5.2 Export Options 33
9.5.5.3 Export Projections 34
9.5.5.4 Export Outputs 34
10 Additional Attachments 35
10.1 RGB Camera 35
11 Troubleshooting 36
11.1 Hardware OLED Errors 36
11.1.1 Line 1 36
11.1.2 Line 2 36
11.1.3 Line 3 37
11.1.4 Line 4 37
11.2 Flight Operation FAQ 39
11.3 Warranty Information 40
Version 1.1
NextCore RN50 User Guide
2
1 Revisions
This section outlines the changelog of the RN50 product.
1.1 Documentation
Version
Change Log
Description
1.1
Initial User Guide release
1.2 Software
Version
Change Log
Description
3.1.7124.2188
Initial Nextcore release
1.3 Hardware
Hardware
Version
Firmware
Change Log
Description
1.0.1
3.1.603
Initial RN50 release
Version 1.1
NextCore RN50 User Guide
3
2 Introduction
Congratulations on the purchase of your NextCore RN50
LiDAR Scanning unit. This guide is designed to demonstrate the
proper use for creating LiDAR point clouds using your
NextCore RN50 Platform attached to the DJI m600 UAV.
The guide assumes that you are an experienced operator of
UAV equipment and are familiar with the operations of the DJI
m600. You must operate in accordance with DJI m600 User
Guide at all times. In order to ensure your unit performs to its
specifications and remains operable, it is important that you
read through this User Guide carefully.
If you are in doubt regarding the contents of this user guide it is
important that you contact your distributor for clarification or
further training.
Thank you for your purchase, the staff at NextCore wish you all
the best in the operation of your unit.
Kind Regards,
Nick Smith
Chief Executive Officer
Version 1.1
NextCore RN50 User Guide
4
3 Disclaimer
NextCore accepts no liability for damage or injury or any legal responsibility incurred directly
or indirectly from the use of this product or data created. The user shall observe the operating
guidelines of this unit and the guidelines of the equipment it is attached to at all times.
4 List of Items
4.1 Nextcore RN50
1x Payload
1x Power Adapter
1x 64GB USB Thumb Drive
4.2 M600 Mounting Kit
1x M600 Mounting Kit
1x Power and API Adapter
2x Antenna Booms
4x Vibration Isolators
4.3 Custom Pelican Hard Case
1x 1615 Air Pelican Hard Case
1x RN50 Tool Kit
Version 1.1
NextCore RN50 User Guide
5
5 M600 Installation
5.1 Recommend Tools
- M2 Hex Driver
- M2.5 Hex Driver
- Thread Locker (either mid or high strength depending, recommended Loctite Blue 243)
5.2 M600 Configuration
The Nextcore RN50 has been designed to suit the DJI M600 product. Whilst the RN50 is not
dependent on this product and can be used on other UAV’s please make sure to follow the
recommended user guide of both the desired UAV and the Nextcore product.
The following is an explanation on how to configure the M600 to carry the Nextcore product
and how to configure the DJI API port to enable the auto-capture feature. This section
assumes that you have the Nextcore RN50 M600 mounting kit. Please refer to the DJI M600
user guide and recommended specifications for more details.
5.2.1 Vibration Isolators
Version 1.1
NextCore RN50 User Guide
6
The M600 comes stock with a rigid mounting system. In order to attach the NextCore RN50
system to your M600, a set of vibration isolators are included in the mounting kit. These will
replace the rigid mounts of the M600. You can reuse the screws from your rigid mounts for
your vibration isolation mounts. Always remember to apply blue thread locker to these as they
can stay on your M600 and do not need to be removed with each install. The vibration isolators
tube mounting points are the same width and diameter as the rigid mounts and can be left on
your M600.
5.2.2 Power Installation
The NextCore RN50 system is designed to take power from the UAV. This reduces payload
weight and increases flight time compared to an integrated battery system. As such an inline
connector is provided with the system. The RN50 takes a 6S-LIPO input (20-26.2v). On the
M600 this can be tapped into via the XT30 connector between the M600 battery pack and the
landing gear. Simply add the inline connector. This can be left on the drone when the RN50 is
not attached to the system.
Note: Please ensure the power harness is clear from the landing retract system, if the wires
get caught in the mechanism it could cause a short fatally damaging both UAV and payload.
Version 1.1
NextCore RN50 User Guide
7
5.2.3 API Configuration
As part of the M600 mounting kit, an optional API connector is provided. This connector is for
the DJI A3 flight controller. This connection will enable the auto start capture feature of the
RN50 unit. This will start the capture of the system on flight arm and disarm (take off and land).
This cable and associated A3 setting can be left attached to the system and will not impede
with regular flight operations.
5.2.3.1 Cable Installation
Version 1.1
NextCore RN50 User Guide
8
Note: Do NOT use the Vcc pin. You might damage your payload onboard computer, A3 or
both.
To install this cable first remove the M600 top cover. This will expose the A3 flight controller.
Attach the provided Futaba servo connector to the API port of the A3. This connector should
be orientated so that the white lead is in position 1, red lead is in position 2 and the black
grounded lead is in position 3. Please note that the wrong orientation of this cable can cause
irreversible damage to the RN50 unit. The other end of this can be fed through the M600
frame to be exposed at the bottom ports of the system. This Futaba servo connector can then
be used in conjunction with the provided RN50 Molex connector.
5.2.3.2 API Settings Configuration
The API settings on the A3 will also need to be enabled to allow for API control of the payload.
Using DJI assistant 2, enable the API output under the SDK tab. The GPS output should also be
changed to 10Hz. Refer to the DJI A3 manual on how to upload these settings.
Note: Updating A3 firmware can cause the loss of settings and you may need to enable them
again.
Version 1.1
NextCore RN50 User Guide
9
6 NextCore Installation
6.1 Standard Installation Workflow
Note: Steps 1 and 2 of the standard installation workflow only need to be done on the initial
integration of the unit and can be left on the M600.
This section outlines how to install the NextCore RN50 onto an M600. The RN50 is designed
to fit onto the existing rail system of the M600 unit. Please make sure that the vibration
isolation mounts are attached to the M600 before continuing with this step. The API cable
should already be installed if you want to use the auto capture feature. Your RN50 system
should arrive with the M600 mounting system already assembled on the payload. If this is not
the case or you have bought the mounting solution after the initial unit please follow the next
step. If your mounting solution is attached you can go straight to the M600 mounting section.
Version 1.1
NextCore RN50 User Guide
10
6.2 Attaching the M600 mount kit
To assemble the mounting kit attach the aluminium mounting wings to both the centre 25mm
carbon fibre antenna boom and the 12mm carbon fibre mounting rails. Four 12mm tube
clamps are provided alongside eight M3x12 are provided to clamp positions (A). Two 25mm
tube clamps with M3x15 are provided for clamping position (B).
When assembling the M600 mounting kit it is important to make sure that the middle antenna
section is centred between the two wings. This will increase the accuracy of the IMU as it
depends on the fixed position of the primary antenna as seen in B. It is also important to centre
the 12mm clamps over the front wing of the RN50 as seen in A. The centre of mass is towards
the Lidar so mounting the tube clamps over the centre of mass will improve flight efficiency
and stability of the UAV. The easiest way to assemble this mounting kit is to first attach the two
mounting wings to the payload with the provided M3x20 screws as seen in C. Make sure that
these are hand tight and that thread locker is applied. Then attach the 25mm antenna boom
and then the 12mm mounting rails.
Version 1.1
NextCore RN50 User Guide
11
6.3 Antenna Installation
The NextCore RN50 system operates a dual antenna system in order to reliably define its
orientation. In order for this to happen two antennas need to be attached to the payload
system. The M600 mounting solution comes with mountable booms suitable for the M600
profile. Using the M600 mounting kit you need to attach the antennas attached to the carbon
fibre extension tubes. This is attached to a slip ring tube connector. This is a keyed connector,
when attaching the booms make sure that the antennas are facing the sky. In order to connect
the antenna to the payload two SMA breakouts on the top of the unit. It is important to
connect the forward antenna (Lidar side) to the primary connector and the back antenna to the
secondary antenna. Antennas are colour coded in order to avoid confusion. To follow the DJI
standard of orientation colouring the primary antenna is red whilst the secondary antenna is
green.
The antennas may be removed while the payload is installed on an M600, which allows for easy
transportation of the system.
Note: If antenna connections are around the wrong way it will result in an incorrect heading
leaving data capture invalid. Also the offsets from the RN50 unit to the antennas is very
specifically calibrated, changing this geometry will cause data issues.
Version 1.1
NextCore RN50 User Guide
12
6.4 Mechanical Drawings
The RN50 is connected to the M600 Mounting Kit through four M3 mounting holes located on
the top of the product. Screws must penetrate the RN50 with at least 15mm of thread from
the top of the plastic.
6.5 RN50 Pinout
Pin
Function
1
VCC
2
GND
3
NC
4
API UART RXD
5
API UART TXD
6
Signal GND
Version 1.1
NextCore RN50 User Guide
13
The RN50 has a Molex Nano-Fit 105310 series connector. This connector is provided with
each purchase. Only use provided NextCore cabling when powering the payload. API
connections only apply to the A3 API auto-capture feature of the product. If this feature is not
desired then use only the power connector and not the dual power and API connector.
Note: Attaching a connector with the incorrect pinout can cause permanent damage to the
system.
6.6 Mounting the payload to an M600
To attach the unit to the M600 using the 12mm rails provided in the mounting kit. This will fit
into the vibration isolators circular opening. The best practice is to undo all clamps, insert one
side of the payload into the vibration isolators and then slide forward them back into the
opposite side. Once the payload is within the vibration isolators centre the payload so that the
small indicator lines on the 12mm tube rails fit within the circular clamps. Make sure to tighten
the vibration isolator clamps on all four corners. Apply thread locker to these to ensure that
the vibrations caused by the UAV will not loosen the screws.
Version 1.1
NextCore RN50 User Guide
14
7 Mission Planning
7.1 Manual vs Grid Flights
It is highly recommended to fly any data capture mission with a set grid mission. Grid missions
ensure that all desired areas will be covered. It also reduces IMU error due to the somewhat
uniform nature of the flight characteristics. It is still possible to fly the unit in manual mode.
This may be done to get a higher point density over a key object or area. If flying in manual
mode please keep the UAV steady with a constant velocity and direction if possible.
7.2 Key Considerations
The key to getting good datasets is ensuring that the area to be scanned is well covered by the
flight. Getting good coverage means thinking about the aspect of the LiDAR sensor and making
sure you scan via lines that are parallel to features you want to extract.
A good flight is of at least a moderate duration >7 mins (this allows time for filters to settle and
produce better data). Each flight should include a few slow manoeuvres with pitch and roll in
each direction consistently for a few seconds. This may be a simple box pattern once up to
flight altitudes. This helps the filters settle and learn the pitch/roll offsets.
Smooth flight lines are required for a good dataset, preferably automated with a consistent speed.
Flight speed – the faster the flight speed the lower the point density, but good point density
can be produced up to a speed of 10m/s. Generally, it will be better to fly more flight lines at a
higher speed than slower sparser flight lines. Normal flight profiles do not require speeds
<5m/s, unless high density or vegetation penetration is required.
Flight line spacing should generally be as close as possible. Normally flight line spacing should
be around the flight height (circa 25-50m). If there is more vegetation or specific features to be
detected then flight lines should be closer together.
Version 1.1
NextCore RN50 User Guide
15
Flight height must be higher than obstacles around. Best practice for ensuring safe operation is
to fly a smaller drone (DJI Phantom 4, or DJI Mavic) and check for clearance at set altitudes. A
good dataset can be collected between 20m and 50m, usually, about 30-40m is best choice.
Flying lower concentrates data directly underneath the flight lines, but gets better side aspect
on vegetation and structures. Flying higher gets a more vertical aspect and better vegetation
penetration (esp off flight line centre), but flying too high can induce ranging errors and induce
IMU errors. 80m is a maximum altitude to get LiDAR returns.
Yawing should be avoided for the most part, mission grids should be flown with a consistent
heading (no yaw at end of lines). If for coverage reasons two aspects are required, do a grid
with one heading and then another grid at 90 degrees, with one yaw change between the two.
If including yaw during a manual flight, smooth consistent changes are preferred.
Optimal flight operation utilises the following parameters:
●Consistent flight height (AGL)
●Consistent UAV heading
In order to achieve this NextCore recommends flight mission planners that allow for terrain
following and single directional orientation. The NextCore team use the app Drone Harmony
https://droneharmony.com/ for mission planning, though other applications may be suitable.
Version 1.1
NextCore RN50 User Guide
16
*A typical flight mission setup using Drone harmony to follow the terrain and maintain one
heading orientation during a flight.
Wind is a factor that can affect the accuracy of the data. Wind will cause the UAV to move
erratically to maintain a constant flight line on a grid mission. This erratic movement has an
effect on the accuracy of the data and should be avoided if maximum accuracy is desired.
Smooth consistent wind is not as problematic as gusty turbulent wind which will cause more
motion from the UAV.
Rain should be avoided as exposure to moisture may reduce the lifespan of the unit and void
the warranty.
Available Light is not a concern. The RN50 can effectively be used at night and any time of day
regardless of light availability. Consideration should be given to capturing data when the sun is
low (sunrise and sunset) as direct sunlight into the sensor may produce false points.
7.3 Suggested operating parameters
Parameter
Recommended
Maximum
Flight Height AGL (m)
<40 metres
80 metres
Line Spacing (m)
<30 metres
50 metres
Flight Speed (m/s)
5 m/s
10 m/s
Wind Speed (m/s)
Calm
<10 m/s (gust)
Version 1.1
NextCore RN50 User Guide
17
7.4 Flight Planning with DJI GS Pro
An example mission setup is shown using the popular flight planning software DJI GS Pro. All
screenshots are from DJI GS Pro version 20.5 (8664) and are correct for that firmware version.
DJI GS pro is very common amongst photogrammetry missions and these settings can be
adapted to Lidar missions. This is am example data capture and is to be used only as a guide for
mission planning. Mission planning is very dependent on the desired deliverables needed. It is
best to practice with the RN50 on smaller datasets under different mission setting to
understand what settings are appropriate for the desired mission.
7.4.1 Grid mission setup
Start a new 3d mapping grid mission on the DJI GS pro app. Set the desired mission fence and
area. The camera mode is recommended as A7 or an equivalent camera. Make sure to change
the capture mode to ‘Capture at Equal Dist. Interval '. The height of the mission should be
within the recommended flight height. For this mission the height is 40m AGL. Flight speed is
controlled by the front overlap percentage of the advanced setting.
Version 1.1
NextCore RN50 User Guide
18
Under the advanced settings tab of the application ensure that the front overlap ratio is such
that your flight speed is within the recommended parameters. The side overlap is chosen to a
percentage in order to make sure that the distance between flight lines are within the
recommended spacing. For this mission the desired flight line spacing was 40m. Always change
the course angle to give the longest possible flight lines. This will reduce mission time and
increase IMU filter accuracies.
Version 1.1
NextCore RN50 User Guide
19
Table of contents
