▼Nindustrial | |
Nbyte_array | |
Ncomms_fault_handler | |
Njoint_data | |
▼Njoint_feedback | |
NValidFieldTypes | |
Njoint_feedback_message | |
▼Njoint_message | |
NSpecialSeqValues | Enumeration of special sequence values that signal the end of trajectory or an immediate stop |
Njoint_traj | |
▼Njoint_traj_pt | |
NSpecialSeqValues | |
▼Njoint_traj_pt_full | |
NSpecialSeqValues | |
NValidFieldTypes | |
Njoint_traj_pt_full_message | |
Njoint_traj_pt_message | |
Nlog_wrapper | Contains macro that wrap standard logging calls. Wrapping logging calls allows libraries to be used inside and outside the ROS framework |
Nmessage_handler | |
Nmessage_manager | |
Nping_handler | |
Nping_message | |
▼Nrobot_status | |
NRobotModes | Enumeration mirrors industrial_msgs/RobotMode definition |
NTriStates | Enumeration mirrors industrial_msgs/TriState definition. NOTE: The TS prefix is needed because the ON and TRUE value collide with other defined types on some systems |
Nrobot_status_message | |
Nshared_types | Contains platform specific type definitions that guarantee the size of primitive data types |
Nsimple_comms_fault_handler | |
▼Nsimple_message | |
NCommTypes | Enumeration of communications types (supported by all platforms) |
NReplyTypes | Enumeration of reply types (supported by all platforms). In cases of success or failure, the return data should include the relevant return info |
NStandardMsgTypes | Enumeration of standard message types (supported by all platforms). In addition, each robot interface will support it's own message types |
Nsimple_serialize | |
▼Nsimple_socket | |
NStandardSocketPorts | Enumeration of standard socket ports (supported by all platforms). These are defined for convenience. Other ports may be used. Additional ports for application specific needs may also be defined |
Nsmpl_msg_connection | |
Ntcp_client | |
Ntcp_server | |
Ntcp_socket | |
Ntyped_message | |
Nudp_client | |
Nudp_server | |
Nudp_socket |