common:connectorpinouts_connectionoptions

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
Next revisionBoth sides next revision
common:connectorpinouts_connectionoptions [2017/09/06 19:51] – Pedro Ramilocommon:connectorpinouts_connectionoptions [2018/02/15 11:07] – Pedro Ramilo
Line 2: Line 2:
  
 All Seed Robotics models come standard with USB interface and one main interface (the main connector), with a logical interface selected by the customer: One Wire TTL, Full Duplex TTL or RS485.\\ All Seed Robotics models come standard with USB interface and one main interface (the main connector), with a logical interface selected by the customer: One Wire TTL, Full Duplex TTL or RS485.\\
-In addition an [[dh4d:bluetooth| Optional Bluetooth Module]] can be installed on the unit and connects to any terminal that supports the Bluetooth SPP (Serial Port) Profile.+In addition an [[eros:bluetooth_module| Optional Bluetooth Module]] can be installed on the unit and connects to any terminal that supports the Bluetooth SPP (Serial Port) Profile.
  
 Below we detail the connector types for the units and connection diagrams with the most commonly used tools. Below we detail the connector types for the units and connection diagrams with the most commonly used tools.
  
-==== About Supplying Power ====+==== Supplying Power ====
  
-External power must **always be supplied through the main connector port** (the one with the 3 pin or 4 pin connector).\\ +External power must **always be supplied through the main connector port** (the one with the 3 pin or 4 pin connector on the back of the unit).\\ 
-**If you intend on using other interfaces for control (such as USB or Bluetooth), power must still be applied through this connector on the VDD and GND pins.**+**If you intend on using other interfaces for control such as USB or Bluetooth, power must still be applied through this connector on the VDD and GND pins.**
  
 Acceptable voltage range is typically 9V~24V. Please refer to the documentation of your specific model for the exact voltage range accepted. Acceptable voltage range is typically 9V~24V. Please refer to the documentation of your specific model for the exact voltage range accepted.
  
  
-==== Main Connector: One Wire Serial TTL Interface ====+==== Main Connector: One Wire TTL UART Interface ====
  
-The One Wire TTL Serial interface enables daisy chained connection of multiple units. +The One Wire TTL Serial (UART) interface enables daisy chained connection of multiple units. 
-This interface operates natively at 3.3V but it is tolerant to 5V or higher voltages making it compatible with virtually all devices operating at TTL level.+This interface operates natively at 3.3V but it is tolerant to 5V, for interfacing with devices with 5V TTL logic.
  
 This interface option is directly compatible with Robotis Dynamixel AX, MX series of servos. It can also connect to XL and XM series of servos provided you create a necessary adapter cable or board to connect them. This interface option is directly compatible with Robotis Dynamixel AX, MX series of servos. It can also connect to XL and XM series of servos provided you create a necessary adapter cable or board to connect them.
  
-It is important to note that this connection uses only 1 wire for DATA, which means a special adapter is required to control the line switching between RX and TX.\\+It is important to note that this connection uses only 1 wire for DATA, which means a special adapter (or appropriate code for switching TX/RX on and off) is required to control the line switching between RX and TX. The unit already includes the necessary pull-up (10KOhm) on the DATA line.\\
 The most common adapters and connection methods are shown below. The most common adapters and connection methods are shown below.
  
-__**Robotis USB2Dynamixel and SMPS2Dynamixel:**__+__**Seed Robotis PC Interface Board + Power Interface Board:\\ 
 +(Using Robotis SMPS2Dynamixel + USB2Dynamixel or U2D2)**__
  
-{{:common:connect-using-usb2dyn.jpg?direct&400|}}+{{:common:connect-using-robotis-usb2dynamixel-and-u2d2_onewirettl.jpg?direct&400|}}
  
 __**Xevel Labs USB2AX:**__ __**Xevel Labs USB2AX:**__
Line 36: Line 37:
 {{:common:connect-to-existing-dynamixel-chain.jpg?direct&400|}} {{:common:connect-to-existing-dynamixel-chain.jpg?direct&400|}}
  
-__**Connector pinout for TTL signal level interface:**__+__**Connector pinout for One Wire TTL UART signal level interface:**__
  
 {{:dh4d:connector-pinout-one-wire-ttl.png?direct&300|}} {{:dh4d:connector-pinout-one-wire-ttl.png?direct&300|}}
  
  
-==== Main Connector: RS485 Serial Interface ====+==== Main Connector: RS485 UART Serial Interface ====
  
 The RS485 interface uses a differential pair to operate in half duplex mode. The RS485 interface uses a differential pair to operate in half duplex mode.
Line 50: Line 51:
 **IMPORTANT: in RS485, even though communication is done through a differential pair, __GND must also be connected__ in common between the Seed Robotics unit and the MCU.** Failure to do so may result in unreliable communication and potential damage to the units. **IMPORTANT: in RS485, even though communication is done through a differential pair, __GND must also be connected__ in common between the Seed Robotics unit and the MCU.** Failure to do so may result in unreliable communication and potential damage to the units.
  
-__**Robotis USB2Dynamixel and SMPS2Dynamixel:**__+__**Seed Robotis PC Interface Board + Power Interface Board:\\ 
 +(Using Robotis SMPS2Dynamixel + USB2Dynamixel or U2D2)**__
  
-{{:common:connect-using-usb2dyn.jpg?direct&400|}}+{{:common:connect-using-robotis-usb2dynamixel-and-u2d2_rs485.jpg?direct&400|}}
  
 __**Connecting to an existing Dynamixel Servo Chain or Dynamixel based Robot:**__ __**Connecting to an existing Dynamixel Servo Chain or Dynamixel based Robot:**__
Line 58: Line 60:
 {{:common:connect-to-existing-dynamixel-chain.jpg?direct&400|}} {{:common:connect-to-existing-dynamixel-chain.jpg?direct&400|}}
  
-__**Connect to an RS485 converter:**__+__**Connect to a generic RS485 converter:**__
  
 The diagram below is generic: it is designed in a way to suit all major RS485 converters.\\ The diagram below is generic: it is designed in a way to suit all major RS485 converters.\\
 If you have any question regarding connection to your specific converter, please contact support@seedrobotics.com and we'll be happy to assist you. If you have any question regarding connection to your specific converter, please contact support@seedrobotics.com and we'll be happy to assist you.
  
-When selecting an RS485 converter, please observe the maximum baud rate of the converter. Bear in mind the default communication speed on the main port is 1Mbps. While it is possible to reduce it to a much lower value (115.2/57.6/9.6 kbps), we recommend 1Mbps or higher for best performance.+When selecting an RS485 converter, please observe the maximum baud rate of the converter. Bear in mind the default communication speed on the main port is 1Mbps. While it is possible to reduce it to a much lower value (115.2/57.6/9.6 kbps) for compatibility with a slower RS485 converter, we recommend 1Mbps or higher for best performance.
  
 {{:common:connect-via-rs485.jpg?direct&400|}} {{:common:connect-via-rs485.jpg?direct&400|}}
Line 80: Line 82:
 Failure to do so will result in the Actuators not responding and the hand not moving as they will not be powered. Failure to do so will result in the Actuators not responding and the hand not moving as they will not be powered.
  
-**IMPORTANT:** you can connect via Bluetooth even if your unit is already connected via any of the other ways shown above.+**IMPORTANT:** you can connect via USB even if your unit is already connected via any of the other ways shown above. The firmware is capable of receiving commands simultaneously from the main connector and the USB connector. This especially useful for **online** diagnostics and maintenance.
  
 {{:common:connect-via-usb.jpg?direct&400|}} {{:common:connect-via-usb.jpg?direct&400|}}
Line 93: Line 95:
  
 **IMPORTANT:** you can connect via Bluetooth even if your unit is already connected via any of the other ways shown above. The unit can simultaneously accept commands through the main port and the Bluetooth interface.\\ **IMPORTANT:** you can connect via Bluetooth even if your unit is already connected via any of the other ways shown above. The unit can simultaneously accept commands through the main port and the Bluetooth interface.\\
-This is especially convenient for **online diagnostics** and maintenance.+This is especially convenient for **online, wireless diagnostics** and maintenance.
  
 When connecting via Bluetooth, you must apply power through the Main Connector as shown in the diagram below.\\ When connecting via Bluetooth, you must apply power through the Main Connector as shown in the diagram below.\\
Line 101: Line 103:
  
 By default the firmware is configured to expose the Console over Bluetooth. This means that control using the Dynamixel protocol is not enabled by default on the Bluetooth port (although it can be enabled if required).\\ By default the firmware is configured to expose the Console over Bluetooth. This means that control using the Dynamixel protocol is not enabled by default on the Bluetooth port (although it can be enabled if required).\\
-For more information, see the [[eros:consolecommands|List of Console Commands (for EROS architecture)]].+For more information, see [[eros:bluetooth_module|Using the Bluetooth Interface Module]].
  
  

Copyright © 2015-2023 Seed Robotics Ltd

  • common/connectorpinouts_connectionoptions.txt
  • Last modified: 2022/12/21 18:59
  • by Pedro Ramilo