Difference between revisions of "OpenIGTLink/ProtocolV2/Type/SensorData"

From NAMIC Wiki
Jump to: navigation, search
 
(26 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
[[OpenIGTLink/ProtocolV2/Draft | << Version 2 Draft Page]]
+
[[OpenIGTLink/ProtocolV2/Index | << Version 2 Index Page]]
  
 
=Summary=
 
=Summary=
−
SDATA 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.
+
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=
 
=Message Types=
Line 13: Line 13:
 
| align="left" style="background:#e0e0e0;" | Description
 
| align="left" style="background:#e0e0e0;" | Description
 
|-
 
|-
−
| align="left" | NSENSORS
+
| align="left" | LARRAY
−
| align="left" | uint16
+
| align="left" | uint8
−
| align="left" | Number of sensors
+
| align="left" | Length of array (0-255)
−
|-
 
−
| colspan=3 align="left" style="background:#e0e0e0;" |FORMAT 0
 
 
|-
 
|-
−
| align="left" | LARRAY 0
+
| align="left" | STATUS
 
| align="left" | uint8
 
| align="left" | uint8
−
| align="left" | Length of array (0-255)
+
| align="left" | Sensor status (Reserved)
 
|-
 
|-
−
| align="left" | UNIT 0
+
| align="left" | UNIT
 
| align="left" | uint64
 
| align="left" | uint64
 
| align="left" | See [[OpenIGTLink/ProtocolV2/Unit| 64-bit UNIT field]].
 
| align="left" | See [[OpenIGTLink/ProtocolV2/Unit| 64-bit UNIT field]].
 
|-
 
|-
−
| align="left" | NAMELEN 0
+
| align="left" | DATA
−
| align="left" | uint8
+
| align="left" | float64[LARRAY]
−
| align="left" | Name length
 
−
|-
 
−
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
−
|-
 
−
| colspan=3 align="left" style="background:#e0e0e0;" |FORMAT (NSENSORS-1)
 
−
|-
 
−
| align="left" | LARRAY (NSENSORS-1)
 
−
| align="left" | int8
 
−
| align="left" | Length of array (0-255)
 
−
|-
 
−
| align="left" | UNIT (NSENSORS-1)
 
−
| align="left" | int64
 
−
| align="left" | see [[OpenIGTLink/ProtocolV2/Unit| 64-bit UNIT field]].
 
−
|-
 
−
| align="left" | NAMELEN (NSENSORS-1)
 
−
| align="left" | uint8
 
−
| align="left" | Name length
 
−
|-
 
−
| colspan=3 align="left" style="background:#e0e0e0;" |NAME Table
 
−
|-
 
−
| align="left" | NAME 0
 
−
| align="left" | char[NAMELEN]
 
−
| align="left" | Name
 
−
|-
 
−
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
−
|-
 
−
| align="left" | NAME (NSENSORS-1)
 
−
| align="left" | char[NAMELEN (NSENSORS-1)]
 
−
| align="left" | Name
 
−
|-
 
−
| align="left" | Padding*
 
−
| align="left" | uint8 or none
 
−
| align="left" | padding to align DATA with WORD
 
−
|-
 
−
| colspan=3 align="left" style="background:#e0e0e0;" |DATA
 
−
|-
 
−
| align="left" | DATA 0
 
−
| align="left" | float64[LARRAY 0]
 
 
| align="left" | value array for sensor 0
 
| align="left" | value array for sensor 0
−
|-
 
−
| align="left" | DATA 1
 
−
| align="left" | float64[LARRAY 1]
 
−
| align="left" | value array for sensor 1
 
−
|-
 
−
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
−
|-
 
−
| align="left" | DATA (NSENSORS-1)
 
−
| align="left" | float64[LARRAY (NSENSORS-1)]
 
−
| align="left" | value array for sensor (NSENSORS-1)
 
 
|-
 
|-
 
|}
 
|}
  
−
In C/C++, the size of padding is determined by:
 
−
((NAMELEN0 + NAMELEN1 + ... ) % 2 == 0) ? 0 : 1
 
  
 +
===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:
  
−
===Examples===
 
−
====Sending 3-axis position====
 
−
A device with 3-axis force (N), 3-axis torque (N*m) and 3-axis acceleration (m/s^2) sensors is sending data to a data logger program. The names of the sensors are "FORCE", "TORQUE", and "ACCEL." The message structure may be as follows:
 
 
{| border="1" cellpadding="5" cellspacing="0" align="center"
 
{| border="1" cellpadding="5" cellspacing="0" align="center"
 
|-
 
|-
Line 94: Line 42:
 
| align="left" style="background:#e0e0e0;" | Value
 
| align="left" style="background:#e0e0e0;" | Value
 
|-
 
|-
−
| align="left" | NSENSORS
+
| align="left" | LARRAY
−
| align="left" | uint16
 
−
| align="left" | 3
 
−
|-
 
−
| align="left" | LARRAY 0
 
 
| align="left" | uint8
 
| align="left" | uint8
 
| align="left" | 3
 
| align="left" | 3
 
|-
 
|-
−
| align="left" | UNIT 0
+
| align="left" | STATUS
−
| align="left" | uint64
 
−
| align="left" | 00000010 11000000 00000000 00000000 00000000 00000000 00000000 00000000
 
−
|-
 
−
| align="left" | NAMELEN0
 
−
| align="left" | int8
 
−
| align="left" | 5
 
−
|-
 
−
| align="left" | LARRAY 1
 
 
| align="left" | uint8
 
| align="left" | uint8
−
| align="left" | 3
+
| align="left" | 0
 
|-
 
|-
−
| align="left" | UNIT1
+
| align="left" | UNIT
 
| align="left" | uint64
 
| align="left" | uint64
 
| align="left" | 00000010 11000000 00010000 00000000 00000000 00000000 00000000 00000000  
 
| align="left" | 00000010 11000000 00010000 00000000 00000000 00000000 00000000 00000000  
 
|-
 
|-
−
| align="left" | NAMELEN1
+
| align="left" | DATA
−
| align="left" | int8
 
−
| align="left" | 6
 
−
|-
 
−
| align="left" | LARRAY 2
 
−
| align="left" | uint8
 
−
| align="left" | 3
 
−
|-
 
−
| align="left" | UNIT 2
 
−
| align="left" | uint64
 
−
| align="left" | 00000000 01000000 00111101 00000000 00000000 00000000 00000000 00000000
 
−
|-
 
−
| align="left" | NAMELEN2
 
−
| align="left" | int8
 
−
| align="left" | 5
 
−
|-
 
−
| align="left" | NAME 0
 
−
| align="left" | char[5]
 
−
| align="left" | "FORCE"
 
−
|-
 
−
| align="left" | NAME 1
 
−
| align="left" | char[6]
 
−
| align="left" | "TORQUE"
 
−
|-
 
−
| align="left" | NAME 2
 
−
| align="left" | char[5]
 
−
| align="left" | "ACCEL"
 
−
|-
 
−
| align="left" | DATA 0
 
−
| align="left" | double[3]
 
−
| align="left" | {0.0, 0.0, 0.0}
 
−
|-
 
−
| align="left" | DATA 1
 
−
| align="left" | double[3]
 
−
| align="left" | {0.0, 0.0, 0.0}
 
−
|-
 
−
| align="left" | DATA 2
 
 
| align="left" | double[3]
 
| align="left" | double[3]
 
| align="left" | {0.0, 0.0, 0.0}
 
| align="left" | {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 [[OpenIGTLink/ProtocolV2/Type/Bind|BIND message description page]] for detail.
  
 
==GET_SENSOR==
 
==GET_SENSOR==
Line 170: Line 73:
 
|}
 
|}
  
 +
==STT_SENSOR==
 +
 +
{| border="1" cellpadding="5" cellspacing="0" align="center"
 +
|-
 +
| align="left" style="background:#e0e0e0;" | Data
 +
| align="left" style="background:#e0e0e0;" | Type
 +
| align="left" style="background:#e0e0e0;" | Description
 +
|-
 +
|}
  
−
==STT_SENSOR==
+
<center> or </center>
  
−
N/A
+
{| border="1" cellpadding="5" cellspacing="0" align="center"
 +
|-
 +
| align="left" style="background:#e0e0e0;" | Data
 +
| align="left" style="background:#e0e0e0;" | Type
 +
| align="left" style="background:#e0e0e0;" | Description
 +
|-
 +
| align="left" | RESOL
 +
| align="left" | uint64
 +
| align="left" | Minimum interval between message (ns). Same format as [[OpenIGTLink/Timestamp|TimeStamp]]
 +
|-
 +
|}
  
 
==STP_SENSOR==
 
==STP_SENSOR==
  
−
N/A
 
  
 +
{| border="1" cellpadding="5" cellspacing="0" align="center"
 +
|-
 +
| align="left style="background:#e0e0e0;" | Data
 +
| align="left style="background:#e0e0e0;" | Type
 +
| align="left style="background:#e0e0e0;" | Description
 +
|-
 +
|}
  
 
==RTS_SENSOR==
 
==RTS_SENSOR==
  
−
N/A
+
{| border="1" cellpadding="5" cellspacing="0" align="center"
 +
|-
 +
| align="left style="background:#e0e0e0;" | Data
 +
| align="left style="background:#e0e0e0;" | Type
 +
| align="left style="background:#e0e0e0;" | Description
 +
|-
 +
| align="left" | Status
 +
| align="left" | 8 bit unsigned
 +
| align="left" | 0: Success 1: Error
 +
|-
 +
|}
  
 
=Implementations=
 
=Implementations=

Latest revision as of 04:44, 30 November 2011

Home < OpenIGTLink < ProtocolV2 < Type < SensorData

<< Version 2 Index Page

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
or
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

Comments

Retrieved from "https://www.na-mic.org/w/index.php?title=OpenIGTLink/ProtocolV2/Type/SensorData&oldid=72185"