Documentation/FlyCore i225U WikiEnglish · V1
Browse documentation
System Overview

FlyCore Specifications

( )PPS (pulse per second signal) is used for microsecond level time synchronization across multiple sensors and requires input from an external GNSS/timing source.

3 min read · English documentation

System Specifications

Parameter Specification
Effective Sensing Distance ≥5m @ 90% reflectivity @100 klx
Sensing Blind Zone ≤ 30cm (determined by the actual sensor layout)
Effective Sensing Range ≥ 180° (determined by the actual sensor layout)
Sensing Resolution ≤ 5cm
Perception Output Frame Rate ≥ 10Hz
Camera Type Stereo camera
LiDAR Type MID360
RTK Support Yes
IMU Support Yes
Output Frame Rate ≥ 10Hz
Pose Estimation Localization Output Interval Jitter ≤ 10ms
Pose Estimation Static Error ±5cm @ ±1° (5min @ CEP95)
Pose Estimation Dynamic Error ±15cm @ ±3° (5min @ CEP95)
Pose Estimation Static Drift Rate 10cm/h @ 1°/h
Pose Estimation Localization Response Latency 200ms
Pose Estimation Recommended Maximum Prior Map Extent 100m × 20m × 50m
Pose Estimation Absolute Deviation ≤ 50% (with the global localization source taken as 100%)
Pose Estimation Initialization Time ≤ 20S
Pose Estimation Maximum Allowable Motion Speed 5m/s
Typical Supported Environment: Underground Garage Supported
Typical Supported Environment: Warehouse Supported
Typical Supported Environment: Office Supported
Typical Supported Environment: Karst Cave Supported
Typical Supported Environment: Indoor-Outdoor Transition Supported
Typical Supported Environment: Outdoors Supported (multiple feature points)

Hardware Specifications

Product Hardware Module Parameter Specification
FlyCore Perception CPU Maximum Frequency (P-core) 4.8 GHz
FlyCore Perception CPU Maximum Frequency (E-core) 3.8 GHz
FlyCore Perception CPU Maximum Frequency (LE-core) 2.4 GHz
FlyCore Perception CPU GPU Intel® Graphics@2 GHz
FlyCore Perception CPU NPU 12 TOPS@INT8
FlyCore Perception CPU TDP 15W
FlyCore Perception CPU Memory 16GB@LPDDR5
FlyCore Perception CPU Storage 256GB@2242, NVMe (PCIe 3.0 ×2)
FlyCore Command and Control CPU Model RK3588L
FlyCore Command and Control CPU Maximum Frequency 2.4 GHz
FlyCore Command and Control CPU GPU ARM Mali-G610 MP4
FlyCore Command and Control CPU NPU 6 TOPS@INT8
FlyCore Command and Control CPU Maximum Power Consumption 12W
FlyCore Command and Control CPU Memory 16GB@LPDDR4X
FlyCore Command and Control CPU Storage 128GB@eMMC
FlyCore Other Hardware Number of Perception Camera Channels 4 channels
FlyCore Other Hardware Clock Synchronization Output IEEE 1588-2008
FlyCore Other Hardware Clock Synchronization Signal PPS(*)
FlyCore Environmental and Electrical Operating Temperature Range -10-50 ℃ (using the standard heatsink with good ventilation)
FlyCore Environmental and Electrical Humidity Range 0~90%RH (non-condensing)
FlyCore Environmental and Electrical Input Voltage 19~27V
FlyCore Environmental and Electrical Rated Input Current 5A
FlyCore Structure Mechanical Dimensions 120 × 93 mm
FlyCore Environmental and Electrical Maximum Design Power Consumption (excluding external outputs) 40W
FlyCore Environmental and Electrical External Power Supply 12V@3A
FlyCore Environmental and Electrical External Power Supply 5V@2A
FlyCore Environmental and Electrical External Power Supply 3.3V@1A
FlyCore External Interfaces Integrated External Interfaces 100 Mbps Ethernet ×2, command and control serial ports ×2
FlyCore External Interfaces Perception Camera Interface MIPI 2-lane ×4
FlyCore External Interfaces Onboard IMU Interface SPI ×1
FlyCore External Interfaces Gimbal Interface Serial port ×1
FlyCore External Interfaces MIPI 4-lane ×1
FlyCore External Interfaces USB 2.0 ×1
FlyCore External Interfaces USB-C (combined data/display) USB 3.0 ×2, DP
FlyCore External Interfaces GNSS Interface Serial port ×1
FlyCore External Interfaces PPS Input ×1(*)
FlyCore External Interfaces Flight Controller and Video/Data Transmission Interface Serial port ×1
FlyCore External Interfaces 100 Mbps Ethernet ×1

(*)PPS (pulse-per-second signal) is used for microsecond-level time synchronization across multiple sensors and requires input from an external GNSS/timing source.