Project Developer Edition Professional Edition Mapping Area 150m×150m 500m×500m Usage Time 1.5-hour looped use Unlimited time Upgrade Service No upgrade service Continuous functionality iteration Support Service None (but will answer online questions and compile FAQs) Full lifecycle Specification For more information, refer to the datasheet. Max mapping area 500000m2 ~ 1200000m2 Map resolution 1cm、2.5cm、5cm（Optional） Real-time localization deviation（typ） ± 5mm,± 1° localization stability Our robot can function well even with a 50% change in map Maximum distance range 50m（typical value, specific depending on radar selection） Sample frequency 10 ~ 20Hz Localization output frequency 20 ~ 100Hz Basic hardware resource requirements and assessment Description Description Details Supported processor chip types Intel x86 x64 series chips, ARMV7/V8 series chips Supported operating systems Ubuntu 18.04, 20.04 Hardware interface requirements 1 × USB2.0 for authorization box, 1 × Ethernet port, 1 × serial port or 1 × USB for LiDAR + 1 × power interface (specific details in radar datasheet), Note: Ethernet port at 100 Mbps is sufficient; USB port not recommended due to potential signal interference CPU usage RK3399: up to 2 × A72 + 2 × A53, Intel Celeron J3455: up to 2.5 cores (actual assessment results prevail) Memory usage Mapping mode: 5cm resolution avg. 2GB, Localization mode: 5cm resolution, 250,000 sqm map max. 2.5GB (increases with mapping area and resolution) Disk space usage 15GB total (5GB for logs, 10GB for core dumps) Software interfaces Subscribe to ROS TOPIC /odom (optional, provided by user), Note: ROS TOPIC must be in standard nav_msgs/Odometry format with publishing frequency >50Hz (100Hz recommended)
