Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dh4d:home [2017/08/17 12:28] – Pedro Ramilo | dh4d:home [2023/05/12 18:11] (current) – SeedR KB Admin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== SR-RH4D Hand ===== | + | ===== RH4D Advanced Manipulator |
{{: | {{: | ||
Line 5: | Line 5: | ||
The [[http:// | The [[http:// | ||
- | |||
- | The hand uses the latest **EROS Architecture** for electronics and software comprised of one main processor - ARM Cortex M4 - and 4x dedicated ATMEGA processors (one on each smart actuator), for distributed and scalable processing of low level motion control. | ||
The unit is capable of receiving commands simultaneously from multiple interfaces: main connector (RS485 or TTL), USB and optionally Bluetooth. | The unit is capable of receiving commands simultaneously from multiple interfaces: main connector (RS485 or TTL), USB and optionally Bluetooth. | ||
- | |||
- | To **control the unit and query its status, the unit exposes Control Tables** (a memory-mapped kind of abstraction) where you can write to specific addresses to control the unit or read from other addresses to get real time status information.\\ | ||
- | A full query cycle usually takes less than 5ms (average 3ms), **enabling closed loop control frequencies of up to 200~250 Hz.** | ||
- | |||
- | Reading and writing the control table is done using the Robotis Dynamixel Protocol (a Serial protocol) or through the Seed Robotics own Text protocol.\\ | ||
- | **Users of Robotis products** should also know that the Control table works under the **Dynamixel 1.0 protocol (AX, MX series) and optionally under the Dynamixel 2 protocol**, for compatibility with the Robotis XM and Pro series.\\ | ||
- | Such flexibility makes the units directly compatible with Robotis Dynamixel based assemblies and frameworks such as Robotis OP/OP2 fremwork, Dynamixel SDK, ROS, PyPot and others.\\ | ||
- | === NOTICE: Change from the Ares to Eros Architecture | + | ==== Getting Started ==== |
- | As of March 1st 2017, we began shipping the RH4D with the new, scalable Eros Architecture.\\ | + | * [[dh4d: |
- | While the external interfaces remain mostly the same, the new architectore is more scalable | + | * [[common: |
- | Information about the transition in the document | + | * [[rh4d:DynamixelIDsandCOMMsettings|Dynamixel Protocol: Default IDs and Communication Settings]] |
- | In the interest of organization, | + | |
- | __The present document, details instructions for the units using the EROS architecture.__ | + | |
+ | ==== Command and Control Architecture ==== | ||
- | ==== Getting Started ==== | + | * [[eros: |
+ | * [[dynamixel: | ||
+ | * [[seedstpprotocol: | ||
- | * [[dh4d: | + | === The Console === |
+ | EROS units expose a Serial Console through which you can perform a number of queries, obtain real time diagnostics and also control the unit. | ||
- | ==== Testing your Unit ==== | + | By default the firmware exposes the Serial Console on the USB Virtual Serial Port and on the Bluetooth interface (if optionally installed).\\ |
- | * [[dynamixel: | + | Use of the Console can be done simultaneously while controlling your unit through |
- | * Using the Darwin-OP Framework: [[dh4d: | + | |
- | === Command and Control Architecture === | ||
- | |||
- | * [[eros: | ||
- | * [[dynamixel: | ||
- | * [[seedstpprotocol: | ||
* [[eros: | * [[eros: | ||
Line 57: | Line 45: | ||
=== In-depth information === | === In-depth information === | ||
- | * [[dh4d:connector_pinouts|Connector Pinouts and Part numbers]] | + | * [[common:connectorpinouts_connectionoptions|Connector Pinouts and Part numbers]] |
Line 78: | Line 66: | ||
* [[eros: | * [[eros: | ||
- | * [[eros:actuators: | + | * [[eros:seedactuators: |
* [[dh4d: | * [[dh4d: | ||
Line 85: | Line 73: | ||
* [[dh4d: | * [[dh4d: | ||
* [[dh4d: | * [[dh4d: | ||
+ | |||
+ | |||
+ | '' | ||
+ | There' | ||
+ | |||
**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. | **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. | ||
** | ** | ||
Copyright © 2015-2023 Seed Robotics Ltd