The ARES architecture is the first architecture of Electronics and Software for the Seed Robotics RH4D/DH4D units. All units manufactured before March 2017 use this architecture, when we made the transition to EROS.

In the interest of maintaining the documentation organized, we have moved all the ARES architecture information to this separate page.

While most of the external control remains similar to both architectures there several particularities of ARES that justify maintaining a separate section for it.

• Unpacking and Mechanical Assembly

• Add support for RH4D in Robotis/Roboplus Dynamixel Wizard
• Using the Darwin-OP Framework: Operation with the Darwin-OP Framework

• Dynamixel Protocol: Default IDs and Communication Settings
• Controlling the unit using the Dynamixel Protocol (main connector interface)
• Controlling the unit using Seed Robotics Simple Text Protocol (STP) (USB and Bluetooth connections)
• RH4D Control Tables

• USB Interface: Console for Control and Diagnostics
• Bluetooth Interface: Console for Control and Diagnostics (optional)
• List of RH4D Console Commands

• Configuring the SR-DH4D for 1023 (10bit) or 4095 (12bit) position resolution

• Operation with the Darwin-OP Framework
• Operation with ROS, PyPot and other Frameworks
• Current sensing and Force estimation: how it works and how to take advantage of it

• Connector Pinouts and Part numbers

• RH4D 3D Files download

Legal notice: Seed Robotics makes the 3D CAD files available to its customers only (entities who have purchased or ordered Seed Robotics products), for the sole purposes of building simulations and assessing dimensions and mechanical characteristics.
Seed Robotics retains all Copyrights and Intellectual property rights pertaining to the material hereby being distributed and does not make any warranty as to its accuracy or fitness for purpose. The publishing of this material, does not constitute a waiver of any of Seed Robotics copyrights and intellectual property rights and does not grant the user any distribution, transfer, ownership or any other rights other than ones explicitly authorized in this notice.

• Software troubleshooting
• Hardware troubleshooting
• Dynamics Troubleshooting: You've assembled the Hand on your Robot and there was a change in its Dynamics

• Ares units: Upgrading your Firmware

• LED Error codes
• Maintaining your Unit in top working condition

• Technical Specifications [ Placeholder ]
• Warranty and Support [ Placeholder ]

Please note: [ Placeholder ] sections are either Beta or currently in the process of migration from paper form to our Knowledge Base. If you require any of this information while we build the Knowledge Base, please contact our technical support by email.