industrial_msgs

Summary

industrial_msgs
Version:

0.4.3

Description:

The industrial message package containes industrial specific messages definitions. This package is part of the ROS-Industrial program.

Maintainers:
  • Shaun Edwards <sedwards AT swri DOT org>
Licenses:
  • BSD
Urls:
Authors:
  • Shaun M. Edwards
BuildDepends:
BuildtoolDepends:
 
BuildExportDepends:
 
ExecDepends:

Types

Message types

industrial_msgs/ServiceReturnCode
Field:
  • val (int8) –
Constant:
  • SUCCESS (int8):1
  • FAILURE (int8):-1

Service return codes for simple requests. All ROS-Industrial service replies are required to have a return code indicating success or failure Specific return codes for different failure should be negative.

# Service return codes for simple requests.  All ROS-Industrial service
# replies are required to have a return code indicating success or failure
# Specific return codes for different failure should be negative.
int8 val

int8 SUCCESS = 1
int8 FAILURE = -1
industrial_msgs/DeviceInfo
Field:
  • model (string) –
  • serial_number (string) –
  • hw_version (string) –
  • sw_version (string) –
  • address (string) –

Device info captures device agnostic information about a piece of hardware. This message is meant as a generic as possible. Items that don’t apply should be left blank. This message is not meant to replace diagnostic messages, but rather provide a standard service message that can be used to populate standard components (like a GUI for example)

# Device info captures device agnostic information about a piece of hardware.
# This message is meant as a generic as possible.  Items that don't apply should
# be left blank.  This message is not meant to replace diagnostic messages, but
# rather provide a standard service message that can be used to populate standard
# components (like a GUI for example)

string model
string serial_number
string hw_version
string sw_version
string address
industrial_msgs/TriState
Field:
  • val (int8) –
Constant:
  • UNKNOWN (int8):-1
  • TRUE (int8):1
  • ON (int8):1
  • ENABLED (int8):1
  • HIGH (int8):1
  • CLOSED (int8):1
  • FALSE (int8):0
  • OFF (int8):0
  • DISABLED (int8):0
  • LOW (int8):0
  • OPEN (int8):0

The tri-state captures boolean values with the additional state of unknown

# The tri-state captures boolean values with the additional state of unknown

int8 val

# enumerated values

# Unknown or unavailable 
int8 UNKNOWN=-1  

# High state                       
int8 TRUE=1
int8 ON=1
int8 ENABLED=1
int8 HIGH=1
int8 CLOSED=1

# Low state
int8 FALSE=0
int8 OFF=0
int8 DISABLED=0
int8 LOW=0
int8 OPEN=0
industrial_msgs/RobotStatus
Field:

The RobotStatus message contains low level status information that is specific to an industrial robot controller

The header frame ID is not used

# The RobotStatus message contains low level status information 
# that is specific to an industrial robot controller

# The header frame ID is not used
Header header

# The robot mode captures the operating mode of the robot.  When in
# manual, remote motion is not possible.
industrial_msgs/RobotMode mode

# Estop status: True if robot is e-stopped.  The drives are disabled
# and motion is not possible.  The e-stop condition must be acknowledged
# and cleared before any motion can begin.
industrial_msgs/TriState e_stopped

# Drive power status: True if drives are powered.  Motion commands will 
# automatically enable the drives if required.  Drive power is not requred
# for possible motion
industrial_msgs/TriState drives_powered

# Motion enabled: Ture if robot motion is possible.
industrial_msgs/TriState motion_possible

# Motion status: True if robot is in motion, otherwise false
industrial_msgs/TriState in_motion

# Error status: True if there is an error condition on the robot. Motion may
# or may not be affected (see motion_possible)
industrial_msgs/TriState in_error

# Error code: Vendor specific error code (non zero indicates error)
int32 error_code
industrial_msgs/RobotMode
Field:
  • val (int8) –
Constant:
  • UNKNOWN (int8):-1
  • MANUAL (int8):1
  • AUTO (int8):2

The Robot mode message encapsulates the mode/teach state of the robot Typically this is controlled by the pendant key switch, but not always

# The Robot mode message encapsulates the mode/teach state of the robot
# Typically this is controlled by the pendant key switch, but not always

int8 val

# enumerated values
int8 UNKNOWN=-1                 # Unknown or unavailable         
int8 MANUAL=1 			 # Teach OR manual mode
int8 AUTO=2                     # Automatic mode
industrial_msgs/DebugLevel
Field:
  • val (uint8) –
Constant:
  • DEBUG (uint8):5
  • INFO (uint8):4
  • WARN (uint8):3
  • ERROR (uint8):2
  • FATAL (uint8):1
  • NONE (uint8):0

Debug level message enumeration. This may replicate some functionality that alreay exists in the ROS logger. TODO: Get more information on the ROS Logger.

# Debug level message enumeration.  This may replicate some functionality that
# alreay exists in the ROS logger.
# TODO: Get more information on the ROS Logger.
uint8 val

uint8 DEBUG = 5
uint8 INFO = 4
uint8 WARN = 3
uint8 ERROR = 2
uint8 FATAL = 1
uint8 NONE = 0 

Service types

industrial_msgs/StartMotion
Field (Response):
 

Resume current robot motion (e.g. after stop_motion or robot fault)

# Resume current robot motion (e.g. after stop_motion or robot fault) 
---
industrial_msgs/ServiceReturnCode code
industrial_msgs/StopMotion
Field (Response):
 

Stops current robot motion. Motion resumed by using start_motion service or by sending a new motion command

# Stops current robot motion.  Motion resumed by using start_motion service
# or by sending a new motion command

---
industrial_msgs/ServiceReturnCode code
industrial_msgs/CmdJointTrajectory
Field (Request):
 
Field (Response):
 
Send a JointTrajectory command to the robot.
  • duplicates functionality of the joint_path_command topic
  • provides a response-code to verify command was received
  • returns when trajectory is sent to robot, not when motion completed
  • return code may NOT indicate successful transfer to robot
# Send a JointTrajectory command to the robot.
#   - duplicates functionality of the joint_path_command topic
#   - provides a response-code to verify command was received
#   - returns when trajectory is sent to robot, not when motion completed
#   - return code may NOT indicate successful transfer to robot

trajectory_msgs/JointTrajectory trajectory
---
industrial_msgs/ServiceReturnCode code
industrial_msgs/SetDrivePower
Field (Request):
 
  • drive_power (bool) –
Field (Response):
 

Direct method of turning drive power on and off NOTE: Motion commands will automatically to this if drive power is not on and a motion command is received.

# Direct method of turning drive power on and off
# NOTE: Motion commands will automatically to this if
# drive power is not on and a motion command is received.

bool drive_power
---
industrial_msgs/ServiceReturnCode code
industrial_msgs/SetRemoteLoggerLevel
Field (Request):
 
Field (Response):
 

Sets logging level for a remote device that is attached to ROS via some communications link. This service is meant to set the log level on the device directly so that the comms link is not overloaded with messages.

# Sets logging level for a remote device that is attached to
# ROS via some communications link.  This service is meant to
# set the log level on the device directly so that the comms
# link is not overloaded with messages.

industrial_msgs/DebugLevel level
---
industrial_msgs/ServiceReturnCode code
industrial_msgs/GetRobotInfo
Field (Response):
 

The Get Robot Info service returns vendor specific information about the robot(s) connected by the driver

# The Get Robot Info service returns vendor specific information about
# the robot(s) connected by the driver

---
industrial_msgs/DeviceInfo controller
industrial_msgs/DeviceInfo[] robots
industrial_msgs/ServiceReturnCode code