Difference between revisions of "OpenIGTLink/ProtocolV2/Type/SensorData"
From NAMIC Wiki
(→SENSOR) |
(→SENSOR) |
||
Line 25: | Line 25: | ||
| align="left" | See [[OpenIGTLink/ProtocolV2/Unit| 64-bit UNIT field]]. | | align="left" | See [[OpenIGTLink/ProtocolV2/Unit| 64-bit UNIT field]]. | ||
|- | |- | ||
− | | align="left" | | + | | align="left" | DATA |
| align="left" | float64[LARRAY] | | align="left" | float64[LARRAY] | ||
| align="left" | value array for sensor 0 | | align="left" | value array for sensor 0 |
Revision as of 19:10, 3 February 2011
Home < OpenIGTLink < ProtocolV2 < Type < SensorDataContents
Summary
SENSOR is a message type, which is used to transfer sensor reading, 3-axis position, velocity, acceleration, angle, angle velocity and angle acceleration. The message format is intended for manipulator control and various types of sensors.
Message Types
SENSOR
Data | Type | Description |
LARRAY | uint8 | Length of array (0-255) |
STATUS | uint8 | Sensor status (Reserved) |
UNIT | uint64 | See 64-bit UNIT field. |
DATA | float64[LARRAY] | value array for sensor 0 |
Examples
Sending 3-axis troque
A device with 3-axis torque (N*m) sensor is sending data to a data logger program. The following table shows example data format to send 3-axis torque:
Data | Type | Value |
LARRAY | uint8 | 3 |
STATUS | uint8 | 0 |
UNIT | uint64 | 00000010 11000000 00010000 00000000 00000000 00000000 00000000 00000000 |
DATA | double[3] | {0.0, 0.0, 0.0} |
Sending 3-axis force, troque and acceleration
By binding SENSOR data using BIND type, values from multiple types of sensors can be transferred simultaneously. See BIND message description page for detail.
GET_SENSOR
Data | Type | Description |
STT_SENSOR
Data | Type | Description |
Data | Type | Description |
RESOL | uint64 | Minimum interval between message (ns). Same format as TimeStamp |
STP_SENSOR
Data | Type | Description |
RTS_SENSOR
Data | Type | Description |
Status | 8 bit unsigned | 0: Success 1: Error |
Implementations
The TDATA message type is implemented in the following source code.
Contributors
Junichi Tokuda, Yuichiro Hayashi