01
Mobility envelope
Wheel layout, payload, speed, grade and duty cycle define motor, gearbox and drive requirements.
Applications
Application hardware
AMR, AGV & Mobile Robots
Review AMR and AGV subsystem needs across drive hardware, power and charging support, sensing interfaces, safety circuits, harnesses and controlled engineering files.
AI-generated editorial scene for AMR and AGV hardware planning.
Application architecture
Build the mobile platform from the duty cycle outward.
Payload, route profile and runtime set the drive and energy envelope; docking, perception, safety and service wiring must then fit the same chassis.
02
Energy & docking
Battery voltage, peak current, BMS, charger and docking contacts must operate as one charge path.
03
Perception stack
LiDAR, cameras, safety scanners and host compute need defined fields of view, interfaces and mounting.
04
Safety boundary & electrical serviceability
Serviceable electrical routing, E-stop, bumper, scanner, safety I/O and STO responsibilities must be assigned before integration.
Featured decision / mobile-base envelope
Set the drive and energy envelope before selecting the hardware.
Drive sizing and battery architecture are coupled through payload, route, acceleration, grade, runtime and regenerative behavior. Resolve that boundary before narrowing motors, drives, BMS or charging hardware.
Integration decisions
Keep the interfaces in view as you narrow the hardware.
Wheel-to-drive chain
Match motor, gearbox, wheel diameter, feedback and drive limits to the route duty cycle.
Load · speed · ratio · wheel diameterCharge path ownership
Define BMS, charger, docking contacts, pre-charge and protection responsibilities together.
Voltage · current · BMS · dockingPerception and safety separation
Keep navigation sensing distinct from safety-rated devices and document each stop path.
LiDAR · scanner · E-stop · STOChoose a hardware path
Use the path that matches the decision you need to make next.
Select defined mobile-base hardware
Use published motors, reducers, sensors and feedback components when the operating envelope is known.
Browse mobile robot hardwareBuild chassis-specific electrical routing
Use custom harness and cable work when battery, sensor and communication routes depend on the chassis.
Review custom electrical buildsReview the mobile-base interfaces together
Use an engineering review when drive, power, docking, sensing and safety decisions are still coupled.
Describe the AMR platformPrepare your request
Share the inputs you already know.
- Payload, wheel layout, target speed and route profile
- Drive motor, gearbox and controller concept
- Battery voltage, capacity, peak current and BMS interface
- Charger, docking and contact arrangement
- LiDAR, camera, scanner and host-compute stack
- Required drawings, wiring, pinout or STEP/STP files
- Robot dimensions, payload, wheel layout and target speed
- Drive motor, gearbox and motor-driver architecture
- Charger model, docking method and contact arrangement
- LiDAR, camera, ToF, safety scanner and bumper devices
- Jetson Orin, x86 industrial PC or other host platform
- Required wiring diagram, interface map, datasheet or STEP/STP files
What this review can produce
Turn the open decisions into a reviewable next step.
- A mobile-base hardware path tied to the stated duty cycle
- Open drive, power, docking, sensing and safety decisions
- Chassis-specific harness or interface work that needs review
- A controlled document list for the next packaging decision
What this page does not cover
This page is not the right path for certified machine-level safety validation, autonomous navigation validation, fleet software deployment or a complete deployed AMR without customer-side system integration and validation.
Controlled engineering files
AMR file requests should identify the chassis, battery/BMS, charger or docking hardware, sensor models and the exact mounting or wiring decision the document must support.
Engineering review
Define the AMR hardware envelope for engineering review.
Start with the mobile base envelope, payload, voltage platform and the drive, charging or sensor interfaces already selected. A block diagram or equipment list is enough for an initial gap review.