ZhilianhaiFlexiv: Rizon Adaptive Robots, Force Control and Development Tools
Company and development
Flexiv develops and manufactures adaptive robots that combine robotics, force control and artificial intelligence. Its company history records a 2016 founding in Santa Clara, California, with operations subsequently established across several regions. Rizon, Elements and RDK are parts of the same supplier’s hardware and software portfolio, rather than separate companies.
Current Rizon configurations
The current Rizon comparison lists seven-axis Rizon 4 and Rizon 10 arms, together with configurations that add a force/torque sensor. It specifies 4 kg and 10 kg payload classes respectively. The sensor-equipped configurations have different listed reach and weight. Confirm the exact variant and tooling arrangement in the quotation before applying a specification to a planned workcell.
Force control and system components
Flexiv presents Rizon as a platform for combined motion and force control, using its Hesper controller. The product page distinguishes the arm’s IP65 rating from the controller’s IP20 rating. The complete installation therefore needs an environmental assessment that includes the controller, connections and end-of-arm tooling; the arm rating should not be extended to every component in the cell.
Programming and custom development
Flexiv Elements provides visual programming and robot operation, while the RDK offers APIs for customised applications. Flexiv’s current IDE description identifies C++ and Python development and a ROS 2 package. Its RDK page describes real-time sensor and control data exchange at 1 kHz. That interface rate is not a workpiece processing rate or proof of complete application latency.
Version and integration boundaries
Older Rizon brochures use model names and reach figures that differ from the current comparison page. Record the hardware generation, sensor option, controller and software version with each offer. For an existing line, ask the integrator to specify supported communications, equipment interfaces, calibration and update responsibilities. An available development API does not mean a finished connector for every external machine.
Questions for an application trial
Use representative parts and tools to test the intended contact task, including position variation and recovery after an unsuccessful attempt. Agree acceptable contact forces, output quality and cycle time, then measure all three together. Record operator intervention, calibration effort and part rejection alongside successful cycles. A force-control demonstration should be judged against the actual process, not only the robot’s ability to follow a surface.
Delivery and maintenance scope
Separate the robot package from application engineering, fixtures, tooling, vision and commissioning. Request a written training plan, spare-parts process and software support period from the supplier or integrator responsible for the site. Confirm how saved programs, configuration data and calibration records will be handed over, and how production can resume after a controller replacement or software change.