A: The REEMAN Hot Wheels WBOT11B is a compact autonomous mobile robot chassis designed for secondary development and customized robot integration. It combines autonomous navigation, intelligent obstacle avoidance, and open development interfaces in a modular mobile platform.

A: REEMAN robot chassis platforms support HTTP API, Android SDK, RS232 serial communication, and local MQTT. Local MQTT requires REEMAN's Android-based AMR software. Supported commands and available data vary by interface. Developers should confirm the applicable software configuration and interface documentation for the WBOT11B.

A: Yes. Supported navigation operations include sending the robot to predefined waypoints or coordinates, pausing and resuming navigation, canceling tasks, and returning to the charging dock. Available functions depend on the interface and software configuration.

A: Depending on the interface, available information may include robot position, orientation, navigation status, charging status, emergency-stop state, current map, and target waypoint. Not all fields are available through every interface. In the documented configuration, HTTP API and MQTT do not provide battery information or obstacle/blockage status.

A: No. The standard REEMAN SDK does not expose raw camera streams used for navigation and obstacle avoidance. Customers requiring custom AI vision processing can evaluate integration of a separate camera and compatible application software.

A: Hot Wheels combines Laser SLAM and V-SLAM technologies with multi-sensor fusion to support autonomous localization, indoor mapping, route planning, and navigation. It does not require magnetic strips or floor-mounted navigation markers for normal SLAM-based navigation.

A: Yes. The chassis combines Laser sensing, 3D vision, and multiple sensors to detect obstacles and adjust its travel route. Its published Laser detection range is 25 m, with a 270-degree scanning angle. Actual detection performance depends on the environment and obstacle characteristics.

A: The WBOT11B supports a maximum payload of 60 kg, including the weight of integrated upper structures and equipment. Its dimensions are 450 × 450 × 317 mm, and the chassis weight is approximately 28 kg. Load distribution and stability should be evaluated during integration.

A: Yes. Initial mapping, waypoint configuration, and synchronization require a local network. Once setup is complete, preconfigured local navigation tasks can operate without public internet or LAN connectivity using the onboard REEMAN Android AGV software. Remote API commands and network-dependent elevator integration still require their corresponding connections.

A: REEMAN's navigation tools support map configuration, waypoint setup, virtual wall settings, and robot management. Initial setup and synchronization can be completed over a private local network without public internet. Available remote management features depend on the installed software and network configuration.

A: Yes. REEMAN supports map export, backup, and transfer between compatible robots of the same model. Map restoration and import procedures should follow the relevant chassis model's user manual and software configuration.

A: Yes. REEMAN's multi-robot scheduling system supports task assignment, coordinated navigation, and shared route management. In standard configurations, a robot executes queued tasks in the order received, while the scheduling platform can assign tasks to available or designated robots. Customized priority strategies require project-specific evaluation.

A: REEMAN's robot chassis software supports automatic return to the charging dock, docking, and charging. The default low-battery return threshold in REEMAN's AMR software is 20% and can be configured down to 10%. Charging dock compatibility and the applicable hardware configuration should be confirmed for the WBOT11B.

A: The published operating time is approximately 4–6 hours with a 25.6 V / 27 Ah battery. Actual runtime depends on payload, operating speed, travel conditions, and the power consumption of integrated equipment.

A: Optional elevator and access control integration is available for cross-floor navigation. Compatibility depends on the building's elevator control system, communication infrastructure, and project configuration. Network-dependent elevator control requires the relevant connection to remain available.

A: Yes. Its modular chassis and open development interfaces support integration with suitable upper structures, external equipment, and application software. Customization should account for payload capacity, mounting dimensions, center of gravity, power requirements, and interface compatibility.