Resource Center

Products covered

Covers Yunchi S2, Fengxing M3, the Modular Chassis Platform, the Embodied AI Platform, the Mobile Manipulation Robot, the Material Handling Exoskeleton, the Dedicated Trailer and the Industrial Scanner.

What each manual covers

• Product overview, typical applications, main functions, machine structure and available options.
• Dimensions, mass, payload, speed, range, ingress protection, communication and environmental requirements.
• Sensors, charging method, interface capabilities, accessories and transport packaging.
• Safety warnings, prohibited actions, maintenance intervals and the limited warranty.

Version identification

Check the model, hardware version and release date before downloading. Interfaces, parts and software can differ between batches, and project delivery documents take precedence over public manuals.

Before you start

• Check the packaging, machine, accessories, battery and charger for damage.
• Confirm that routes, power, wireless coverage, lighting and safety zones meet the requirements.
• Have the administrator account, device serial numbers and the details of any business system you need to connect.

First-time setup

Work through power-on self-test, device activation, network connection, time sync, map creation, charging-dock calibration, speed limits and geofencing in order.

First task

Set a start point and a destination, check the route, obstacle avoidance, emergency stop, remote takeover and low-battery return, then run a trial with a light payload and confirm the task record.

Software categories

• Robot firmware, sensor firmware and safety-control components.
• Device configuration tools, a debugging client, log export and diagnostics.
• A cloud scheduling platform, an on-site management console and mobile assistant tools.

Release notes

Every release lists its date, supported models, functional changes, fixes, known limitations and compatibility requirements. Production sites should stay on stable releases.

Upgrade requirements

Back up maps and configuration before upgrading, keep the battery and network stable, and validate tasks, charging, interfaces and safety on a test unit before rolling out in batches. If an upgrade fails, stop and contact technical support.

Scope

• SDKs, sample programs, data structures, communication protocols and development-environment setup.
• Robot description files, coordinate frames, simulation models and basic control examples.
• Tasks, maps, device status, alerts, charging and remote control.

Development workflow

Work through authentication, status reads, a test task, error handling, speed limits and emergency-stop validation before connecting a business system, and test all custom code in isolation.

Safety boundaries

Development resources are not a way around the machine's safety limits. Your code should handle loss of connection, timeouts, duplicate commands, invalid coordinates and control conflicts, and keep manual takeover available.

Core interfaces

• Device lookup, online status, battery, position, mode and health.
• Task creation, cancellation, pause, resume, priority and execution results.
• Maps, waypoints, routes, no-go zones, speed-limit zones and charging positions.
• Access control, elevators, turnstiles, call terminals, scanners and third-party scheduling.

Authentication and security

Give each integration its own credentials and the least privilege it needs; production credentials must never ship in front-end code. Enable HTTPS, origin restrictions, request signing, timestamps and an audit trail.

Stability requirements

Callers should handle rate limiting, timeouts, retries, idempotency, duplicate callbacks and delayed state. Error codes, fields and version changes follow the current interface documentation.

Common topics

• Network connectivity, localisation drift, map updates, blocked paths and task errors.
• Charging failures, battery alerts, falling range, wheel wear and loose structures.
• Sensor cleaning, log export, remote diagnostics, firmware updates and spare-part replacement.

Troubleshooting

Start with the alert time, device state and what changed on site, then check power, network, sensors, maps and task configuration. Keep the logs and site photos, and verify one item at a time.

Maintenance

Keep daily, weekly and periodic maintenance records. High-utilisation sites should shorten the inspection interval for wheels, brakes, fasteners, charging contacts and battery health.