End Effectors

Table of contents:

• Tool Interfaces: Version 1: RC servos or Version 2: Dynamixel servos
• End Effectors
• See also

Tool Interfaces

Version 1

The end point of the standard Dexter robot hardware is a replaceable "tool interface" It has a shape which makes it easy for other tools to be clicked on and off. There are spring loaded connectors, sometimes called "pogo pins" at the end for electrical connection, and space for a Tinyduino if additional processing of the signals is needed.

The signals available to the end effector include power, ground, and whatever signals the main board has been configured to produce. Early versions were wired to USB connection. Later version bring out the AUX1 and AUX2 GPIO pins from the FPGA via J20 and J21. These pins can be configured to produce different signals.

Dexter.move_all_joints(0, 0, 0, 0, 0)
make_ins("S", "GripperMotor", 1), //Digital output pin. 0 = off 1 = 5v pin 7 of connector J19 on bottom of PCB. TODO: Verify this?

• There two IO pins on the white connectors in the upper right on the back of the motor board. AUX1 and AUX2 GPIO pins from the FPGA via J20 and J21. On Dexter HD, the J20 pins are brought out to the end effector as the "green" and "blue" wires. Green is the top pin on J20, and blue is the bottom.

In the original firmware, these were connected to the EERoll and EESpan SetParameter commands. Dexter.move_all_joints(0, 0, 0, 0, 0)
make_ins("S", "EERoll", 512), //PWN pin. Integer range of 0-512

In commit 42df0e01285ef8b67764ed53f3cc697df44d4d93, Roll and Span were changed to instead expect Dynamixel servos. However, the wires can still be set manually via the W oplet, at address 64-66.

W oplet address 64:

Bit	Wire	Function
6, 7	Blue	6,7 Mode 0,0 GPIO (see bits 0, 1) 0,1 PWM High speed (not for servos) 1,0 RC PWM For standard servos 1,1 Dynamixel
4, 5	Green	4,5 Mode 0,0 GPIO (see bits 2, 3) 0,1 PWM High speed (not for servos) 1,0 RC PWM For standard servos
3	Green	Output level: When Tristate is 0 and mode GPIO, 0=low, 1=high
2	Green	Tristate 0=output, 1=input
1	Blue	Output level: When Tristate is 0 and mode GPIO, 0=low, 1=high
0	Blue	Tristate: 0=output, 1=input

In PWM modes, the associated tristate bit must be zero, and the duty cycle is set via W 65 _dutycycle_ or W 66 _dutycycle_. Instead of EESpan use W 65 _dutycycle_ and for EERoll, W 66 _dutycycle_ The dutycycle value should be 591*degrees+1142000

Version 2

The standard going forward will be a new tool interface which incorporates 2 Dynamixel XL-320 servos and a Tinyscreen+ (ARM based, small OLED screen, 4 buttons, lots of IO). One FPGA IO pin will be configured to send and receive data via the Dynamixel protocol 2.0. This requires an update to the FPGA image.
Dexter.move_all_joints(0, 0, 0, 0, 0)
make_ins("S", "ServoSet2X", 2, char1 + char2<<8, char3+char4<<8)
The Tinyscreen+ will listen on the servo bus and may return data there or via the dedicated return data line.

To move the Dynamixel servos,

Signals from the Dexter Motor Control PCB to the Tool Interface:

• Ground (J25 pin 1, top pin)
• Logic power +5 Volts (J25 pin 2, the bottom pin). Note: Although out of spec, this actually appears to work very well as a power supply for the servos, making the next signal unnecessary.
• Supply power (18V DC from AC adapter J25?), regulated to Servo power voltage (6 - 8.75V) at the interface by the servo power supply board See: Parts, source, Schematic and PCB design. Note: The +5 supply line appears to work fine.
• Servo data bus, bidirectional. AUX1 via J20 (bottom pin, on bottom connector left side of motor board)
• Return serial data. AUX2 via J21?
• The Dexter HD has 1 additional wire which could be used for the servo power (6 - 8.75V) if we want to route that separately from the main supply power.

Note: J20 and J21 accept TE Connectivity part 2-179694-2 ^ ^ ^ . A 2 position, 2mm, IDC, AMP CT connector. While this is an IDC part, the crimp head cost is insain even without the crimp handle so manually pressing it in with round nose tweezers or just soldering the wire on maybe the practical choice.

Multiple signals are available from the Tinyscreen+ for many different purposes. A PCB to breakout those signals and make them accessible to end effectors via "spring loaded contacts" (pogos) is being designed. Schematic and PCB

End effectors:

for the Original Tool Interface

• http://hdrobotic.com/dexter-community/#!/grippers:marker-holder Simple Marker / Pen holder used to write or draw via DDE's DXF.init_drawing and txt.string_to_line functions. Hint: This functionality should allow Dexter to 3D print in the future.
• http://www.appropedia.org/User:Zsarnold#Enterprise See "Semester 2" A Mantis gripper was adapted to Dexter for a great demo of removing parts from a 3D printer. Mantis Gripper Design and Dexter adapter files. Demo setup: Video, Images, and DDE code.

New Servo Tool Interface

• n/a

See also:

• Current Tool Interface CAD files (note: this will be replaced): OnShape, STL There is room in the body for wiring and a Tinyduino interface device which can be attached with slightly longer bolts.
• http://hdrobotic.com/dexter-community/#!/grippers Our forum section for grippers.
• https://www.eng.yale.edu/grablab/openhand/ These are good designs for open source grippers. They do NOT have the exact tool interface for Dexter, but could be adapted, or the tool interface part can be replace.