Preparing the published article.
AUBO: iS Collaborative Robots and ARCS Development Tools
Compare AUBO iS robot configurations, controller compatibility and AuboStudio/SDK resources, with a practical plan for application integration and acceptance.
Company and documented robot platform
AUBO develops collaborative robot arms and the ARCS robot operating system. Its official developer portal brings together hardware manuals, AuboStudio documentation, application guides and SDK resources. This profile uses the AUBO brand because English legal-name wording differs between the reviewed manual and portal footer. Confirm the exact contracting entity on the commercial documents. AUBO developer portal.
iS family and controller compatibility
The current iS hardware manual describes six-axis collaborative arms across several payload classes. It explicitly distinguishes the iS35, which uses the AUBO-CB-iS-H controller, from the other listed iS arms compatible with AUBO-CB-iS and AUBO-CB-iS(CE). Check this pairing before reusing an existing controller or comparing quotations. A family name alone does not establish interchangeable control hardware. iS robot-arm manual.
Choosing the exact arm
The manual's iS7 table lists a 7 kg payload and 886.5 mm maximum working radius. Select from the model-specific table and drawing rather than combining the largest figures from the overall family. Calculate the total mounted load, inspect the required poses and confirm the effect of tool offsets. Ask the supplier to identify any optional environmental protection and the limits of the complete installed configuration.
AuboStudio and development resources
AUBO publishes AuboStudio user and plugin-development materials. Its SDK guide includes C++, Python and Java examples, together with JSON-RPC, RTDE and script-protocol documentation. These resources support integration work; they do not guarantee that an existing programme will run unchanged across controller and software versions. Establish the compatible firmware, SDK release and operating environment before development begins. SDK guide.
Application integration and evidence
The developer portal links guides for welding, industrial buses, vision and force control. Treat these as technical resources, not proof of a named customer's installation. Request a comparable reference or a supervised trial for the intended task. Define how the robot will obtain part positions, command tooling, exchange machine state and record process results, with responsibility assigned for every interface.
Commissioning and operating workflow
Prepare drawings of the cell, tooling, fixtures and access points. Agree how the programme deals with missing parts, obstructed paths, lost communications and a stopped upstream machine. Have the complete application assessed with its actual workpieces and tools. Record operator access, restart and maintenance procedures; do not treat the collaborative label as a substitute for checking the working installation.
Acceptance and software maintenance
Measure successful task completion, output quality, cycle variation and operator intervention across the expected product mix. Verify that programmes and configuration can be backed up and restored using the agreed process. Retain a version list for the controller, SDK, plugins and external application. Clarify update support, spare modules, training and ownership of any custom integration code.
Sources and enquiry preparation
Primary sources were reviewed on 11 September 2026, including the actual public hardware manual. Specifications above refer to identified models and controller pairings. Prepare the payload and pose requirements, part samples, tool interfaces, software environment and acceptance criteria. Ask for a proposal that separates robot hardware, controller, options, development work and ongoing support.