FlyCore Quick Start Guide

Preparations and Safety Notices

Hardware Power Supply Requirements and Electrostatic Discharge Safety Precautions

Before performing any hardware operation, be sure to carefully read and follow the requirements below:

Strict power supply requirements:

This system is recommended to use a 19V DC power supply. Connecting a voltage that is too high or too low can very easily cause irreversible damage to the mainboard and core components. The system's power supply range is 15V to 28V, and the startup peak current is approximately 5A.

Electrostatic discharge (ESD) protection:

When working with the hardware, be sure to take electrostatic discharge precautions and have knowledge of electronics. It is strongly recommended that you always wear a grounded wrist strap and use an electrostatic discharge mat during operation, because electrostatic discharge issues can very easily cause unexpected hardware damage or system abnormalities for developers.

Initial power-on procedure:

Factory Calibration Notes and Installation Precautions for Sensors (LiDAR and Vision)

The system is supplied from the factory with a calibrated configuration. The relative positions of the LiDAR and vision system have been determined and factory-tested, so the system can be installed directly on a UAV for use. However, the following principles must be strictly followed during airframe adaptation and installation:

Keep the field of view (FOV) unobstructed: Both the LiDAR and vision camera rely on a specific effective field of view for perception calculations. Ensure that the camera's and LiDAR's fields of view are not significantly obstructed.

Do not move components or alter their relative positions without authorization:

Do not remove the LiDAR or perception camera until you sufficiently understand the system's operating principles. If you need to adapt the system for installation on your own UAV and have additional requirements for the placement of the LiDAR and perception camera, or if the vision camera and LiDAR have been removed or moved even slightly, recalibration is required; otherwise, positioning accuracy will be severely affected. If their positions change significantly, contact presales personnel to request the technical support documentation for sensor calibration.

International Sales and After-Sales Contacts

For sensor calibration documentation and other pre-sales or after-sales assistance, use the following international contact channels:

• Email: lixinyuan@amovlab.com or shudajun@amovlab.com
• WhatsApp: +86 13088068247
• YouTube: ROBOSN and AMOVLAB
• GitHub: AMOVLAB open-source projects
• After-sales service: Visit the AMOVLAB official website for complete international after-sales service terms.

Hardware Connections and System Startup

System Hardware Power Supply Instructions

Note: Before plugging the adapter into the power supply, connect all power cables to prevent sparking when inserting the terminals from damaging the equipment.

System Network Connection Instructions

Locate the Ethernet port on the board and connect it directly to the computer using an Ethernet cable. Before connecting, ensure that the computer's network IP is set to a static address and is on the same subnet as the device (that is, the 192.168.1.X subnet).

The system's internal IP addresses are assigned as follows. The PC settings must not conflict with any of these IP addresses.

If the version you purchased includes the LQ-10 video and data transmission link, you can connect directly to the Ethernet port on the remote controller or the LQ-10 ground unit. Connect the PC's Ethernet port directly to the device's Ethernet port and ensure that they are on the same subnet (that is, the 192.168.1.X subnet). If the device can ping 192.168.1.66 or 192.168.1.88, it has joined the same network. You can read the Using the LQ-10 Accessory section directly to learn how to use it.

Configure the PC's IP address as follows (using Windows as an example):

The following figure shows an example of configuring a static IPv4 address for Ethernet in Windows.

After completing the settings, run the following at the command line:

ipconfig, to confirm whether the settings have taken effect.

Fusion Positioning System Test

Log In to the Mapping and Positioning Onboard Computer's Web Console

- Open a browser

- Enter the Web address: 192.168.1.88:18080

- Login account: root

- Password: root

Note: After UAV integration is completed, it is recommended to log in as a non-root user to mitigate security risks. The root user is intended primarily for initial debugging.

Account: Any non-root string

Password: user

View Real-Time Operating Status

After successfully logging in to the Web interface, you can use the console to view the fusion positioning system's current position and attitude information, information about surrounding obstacles detected by the LiDAR, trajectory information while moving, and other data in real time.

After logging in as the root user, you can start, stop, or restart the algorithm.

Users primarily interact visually with the BSA_SLAM software through this console. For detailed instructions, refer to the corresponding manual:

BSA_SLAM_API Manual

Algorithm Start/Stop Control and Basic Positioning Data Verification

After successfully logging in, try obstructing the LiDAR's field of view with an object on a horizontal plane at a slightly greater distance (more than 30cm), and check whether the LiDAR view on the real-time status page matches the actual environment. Then gently move the FlyCore system and check whether the pose output is abnormal.

Visual Odometry (vehicle_visual_odometry) Data Reception Verification

Connect the flight controller to the computer using a Type-C data cable, and open the QGroundControl (QGC) ground station.

Enter uorb status in the terminal and check whether the vehicle_visual_odometry topic is present on the flight controller.

Verify the data:

In QGC, open the "MAVLink Inspector" page. Move the aircraft by hand and observe the vehicle_local_position data:

When moving forward, the x-axis value increases.

When moving right, the y-axis value increases.

When moving down, the z-axis value increases.

Fusion Positioning Data Verification:

Carry the device around the site in a complete loop while observing the data in the Web interface, and confirm whether the device can accurately recognize and return to the origin coordinates.

Recognition and Planning Computer Login and Communication Test

RK3588 SSH Login

RK3588 Default Login

The default RK3588 login information is as follows:

IP address: 192.168.1.66

Username: amov

Password: amov

Protocol: SSH

Recommended method: Log in using MobaXterm. Users can download MobaXterm from the following link:

MobaXterm Download Link

Open MobaXterm, select the SSH protocol, enter 192.168.1.66 in the Host field, and enter amov in the Username field.

When prompted after connecting, enter the password amov to access the RK3588 system.

Optional method: Log in using the command line.

Enter the following in Windows CMD, PowerShell, or a Linux terminal:

ssh amov@192.168.1.66

When prompted, enter the password amov.

After login succeeds, a command prompt similar to amov@amov:~$ should appear in the terminal.

Communication Verification with the Flight Control Computer

Confirm Flight Controller Parameters

Before configuring the parameters, you can download the QGC ground station from the following link:

QGC Download Link

In QGC, open the "Parameters" page, then search for and confirm the following parameters.

MAV_2_CONFIG = TELEM3

SER_TEL3_BAUD = 115200

Note: The parameters above assume the default wiring. If TELEM2 or another interface is actually used, modify the corresponding MAVLink instance and serial port baud rate parameters according to the actual wiring.

Verify the Serial Port on the RK3588

After logging in to the RK3588, set the corresponding serial port baud rate. The default serial port example is /dev/ttyS6:

Enter: sudo stty -F /dev/ttyS6 115200

View Serial Port Data

Run the following command to view the serial data stream in hexadecimal format:

Enter: sudo cat /dev/ttyS6 | xxd

Normal behavior:

The terminal continuously outputs hexadecimal data, indicating that the RK3588 has received data sent by the flight controller.

Reference documents are listed below:

BSASLAM console reference documents:

• Console User Guide
• System Structure Installation Guide
• User Payload Integration Guide