:: PHUA Haptic Interface ::

phua_haptic_interface

Program description:

This package provides an application (and ROS node) to perform haptic control over the LAR humanoid robot.

The application was designed to support three distinct haptic demonstrations and is internally separated into threads to take advantage of all available processing power and haptic joystick’s libraries, and it also possesses a custom built graphical user interface.
The haptic demonstrations detail three different approaches for haptic signals integration on teleoperation events and also on enriched data logging applications.

• A workspace limitations demonstration tries to ensure that the operator does not perform incorrect motions by avoiding workspace limitations, virtualized as haptic objects.
• An object interaction demonstration placed the teleoperated robot interacting with a real world object.
• A leg balancing demonstration tries to show the usefulness of haptic signalling in balance applications.

The application provides control over the robot using a SensAble PHANToM OMNI haptic joystick over an RS232 connection using the HITEC BSI protocol.
The interface allows the user to select the limbs or limb groups he wants to command and a set of preferences for each type of command strategies.

Program usage:

Calling the application without arguments will force the program to use the standard USB port /dev/ttyUSB0. If the user wishes to use another port, calling the apllication with the path to the selected port will force the program to use it.

If this aspect is of no importance, and the user only wishes to see the program interface and test functions, calling the aplication with the flag "--debug" will force the program to ignore servomotor communication and joystick initialization routines.

There is also a "--help" flag that prints to the console a help text for common issues and program usage.

ROS functionalities:

This node publishes the four PHANToM frames:

• Default frame.
• World oriented frame.
• Wrist frame.
• Pen tip frame.

For RViz, the node publishes a marker array with the relevant constructions. For a final version, different marker arrays for different demonstrations are recommended.