What can drive an arm,
and on what evidence
Palletizer is software. The one path to an arm is the safety gate and a RobotAdapter that passes the contract suite. One adapter exists, for Universal Robots. It has run against URSim — UR's own controller software, in a container — and never against a physical arm. Every other entry below is a cited specification the planner and gate reason about, with nothing that can drive it. Nothing is validated on hardware. Nothing is certified.
- certified
- third-party functional-safety assessment of an installation, with certificate reference
- community
- an adapter that passes the contract suite against a simulator
- profile
- a cited published specification; no adapter exists, so it is modelled for planning and reach checks only
- validated
- recorded end-to-end run on physical hardware, with firmware range and test report
| Arm | Payload | Reach | Tier | Adapter and evidence |
|---|---|---|---|---|
FANUC M-410iC/185 FANUC M-410iC/185 published specification (payload 185 kg, reach 3143 mm), 4-axis palletizing configuration | 185 kg | 3143 mm | profile | No adapter. Planning and reach checks only. |
KUKA KR 700 PA (KR FORTEC PA) KUKA KR FORTEC PA family published specification, palletizing variant | 700 kg | 3320 mm | profile | No adapter. Planning and reach checks only. |
Universal Robots UR10e Universal Robots UR10e published specification (payload 12.5 kg, reach 1300 mm, pose repeatability ±0.05 mm per ISO 9283) | 12.5 kg | 1300 mm | community | palletizer_full.hardware.universal_robots.UniversalRobotsAdapter
|
Validated: none. Certified: none. Repeatability is not placement accuracy.
| generic bag fork | fork | 50 kg | profile | representative vendor-neutral fork envelope; not a specific product |
| generic parallel clamp | mechanical parallel | 40 kg | profile | representative vendor-neutral clamp envelope; not a specific product |
| generic 4-zone vacuum head | vacuum | 25 kg | profile | representative vendor-neutral vacuum end-of-arm-tool envelope; not a specific product and not validated on hardware |
docker compose -f docker-compose.ursim.yml up -d palletizer robot verify --host 127.0.0.1
The adapter contract suite against URSim, ending with the gate refusing the same plan after it was mutated. What a VALIDATED record needs is in ROBOT_INTEGRATION.md.
The ROS 2 bridge, the OPC UA gateway, the legacy URScript sender and the AI correction path are quarantined: each refuses before it sends anything, and a test fails the build if a new motion sender appears. The construction planner is experimental and in no paid plan.
A pilot starts from a plan you made on your own SKUs, and runs against your controller's software.
Request a pilot