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

From NAMIC Wiki
Jump to: navigation, search
 
(13 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=
−
Bind message format is designed to bind any OpenIGTLink messages into a single message. All messages bound in a BIND message is called 'child messages.'
+
Bind message format is designed to bind any OpenIGTLink messages into a single message. Messages bound in a BIND message are called 'child messages.'
 
The BIND message format is useful, when one needs to care about synchronization of multiple messages (e.g. multi-channel sensors), or sending associative array (pairs of key string and value). The bind message format consists of the bind header section, which contains types and sizes of child messages, the child message name table section, and the child message body section.
 
The BIND message format is useful, when one needs to care about synchronization of multiple messages (e.g. multi-channel sensors), or sending associative array (pairs of key string and value). The bind message format consists of the bind header section, which contains types and sizes of child messages, the child message name table section, and the child message body section.
  
Line 13: Line 13:
 
| align="left" style="background:#e0e0e0;" | Description
 
| align="left" style="background:#e0e0e0;" | Description
 
|-
 
|-
−
| align="left" | NELEMENTS
+
| align="left" | NCMESSAGES
 
| align="left" | uint16
 
| align="left" | uint16
−
| align="left" | Number of elements
+
| align="left" | Number of child messages
 
|-
 
|-
 
| colspan=3 align="left" style="background:#e0e0e0;" |Bind Header Section  
 
| colspan=3 align="left" style="background:#e0e0e0;" |Bind Header Section  
Line 21: Line 21:
 
| align="left" | TYPE 0
 
| align="left" | TYPE 0
 
| align="left" | char[12]
 
| align="left" | char[12]
−
| align="left" | Data type (OpenIGTLink Device Type string)
+
| align="left" | Data type (OpenIGTLink Device Type string) for child message 0
 
|-
 
|-
 
| align="left" | DATA SIZE 0
 
| align="left" | DATA SIZE 0
 
| align="left" | uint 64
 
| align="left" | uint 64
−
| align="left" | Data size
+
| align="left" | Data size for child message 0
 
|-
 
|-
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
|-
 
|-
−
| align="left" | TYPE (NELEMENTS-1)
+
| align="left" | TYPE (NCMESSAGES-1)
 
| align="left" | char[12]
 
| align="left" | char[12]
−
| align="left" | Data type (OpenIGTLink Device Type string)
+
| align="left" | Data type (OpenIGTLink Device Type string) for child message (NCMESSAGES-1)
 
|-
 
|-
−
| align="left" | DATA SIZE  (NELEMENTS-1)
+
| align="left" | DATA SIZE  (NCMESSAGES-1)
 
| align="left" | uint 64
 
| align="left" | uint 64
−
| align="left" | Data size
+
| align="left" | Data size for child message (NCMESSAGES-1)
 
|-
 
|-
 
| colspan=3 align="left" style="background:#e0e0e0;" |NAME Table Section (NULL-separated values)
 
| colspan=3 align="left" style="background:#e0e0e0;" |NAME Table Section (NULL-separated values)
Line 45: Line 45:
 
| align="left" | NAME 0
 
| align="left" | NAME 0
 
| align="left" | char[*]
 
| align="left" | char[*]
−
| align="left" | Name
+
| align="left" | Name for child message 0
 
|-
 
|-
 
| align="left" | (null)
 
| align="left" | (null)
Line 53: Line 53:
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
|-
 
|-
−
| align="left" | NAME (NELEMENTS-1)
+
| align="left" | NAME (NCMESSAGES-1)
 
| align="left" | char[*]
 
| align="left" | char[*]
−
| align="left" | Name
+
| align="left" | Name for child message (NCMESSAGES-1)
 
|-
 
|-
 
| align="left" | (null)
 
| align="left" | (null)
Line 68: Line 68:
 
|-
 
|-
 
| align="left" | DATA 0
 
| align="left" | DATA 0
−
| align="left" | TYPE 0 [ SIZE 0 ]
+
| align="left" | TYPE 0 ( SIZE 0 )
−
| align="left" | Data array
+
| align="left" | Data array for child message 0
 +
|-
 +
| align="left" | (Padding*)
 +
| align="left" | uint8 or none
 +
| align="left" | padding to align DATA with WORD
 
|-
 
|-
 
| align="left" | DATA 1
 
| align="left" | DATA 1
−
| align="left" | TYPE 1 [ SIZE 1 ]
+
| align="left" | TYPE 1 ( SIZE 1 )
−
| align="left" | Data array
+
| align="left" | Data array for child message 1
 +
|-
 +
| align="left" | (Padding*)
 +
| align="left" | uint8 or none
 +
| align="left" | padding to align DATA with WORD
 
|-
 
|-
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
|-
 
|-
−
| align="left" | DATA (NELEMENTS-1)
+
| align="left" | DATA (NCMESSAGES-1)
−
| align="left" | TYPE (NELEMENTS-1) [SIZE (NELEMENTS -1)]
+
| align="left" | TYPE NCMESSAGE-1 (SIZE NCMESSAGE-1)
−
| align="left" | Data array
+
| align="left" | Data array for child message NCMESSAGE-1
 +
|-
 +
| align="left" | Padding*
 +
| align="left" | uint8 or none
 +
| align="left" | padding to align DATA with WORD
 
|-
 
|-
 
|}
 
|}
 +
*Padding field is inserted only if the previous field does not aligned with WORD border.
 +
 +
<font color="red">Feb 3, 2011: Padding fields are inserted in the data section. </font>
  
 
==GET_BIND==
 
==GET_BIND==
Line 92: Line 107:
 
| align="left style="background:#e0e0e0;" | Description
 
| align="left style="background:#e0e0e0;" | Description
 
|-
 
|-
−
| align="left" | NELEMENTS
+
| align="left" | NCMESSAGES
 
| align="left" | uint16
 
| align="left" | uint16
 
| align="left" | Number of elements
 
| align="left" | Number of elements
Line 101: Line 116:
 
| align="left" | char[12]
 
| align="left" | char[12]
 
| align="left" | Data type (OpenIGTLink device type string)
 
| align="left" | Data type (OpenIGTLink device type string)
−
|-
 
−
| align="left" | NAMELEN 0
 
−
| align="left" | uint 8
 
−
| align="left" | Name length
 
−
|-
 
−
| align="left" | SIZE 0
 
−
| align="left" | uint 16
 
−
| align="left" | Data length
 
 
|-
 
|-
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
|-
 
|-
−
| align="left" | TYPE (NELEMENTS-1)
+
| align="left" | TYPE (NCMESSAGES-1)
−
| align="left" | uint8
+
| align="left" | char[12]
−
| align="left" | Data type (0: string, 1: scalar, 2: vector)
+
| align="left" | Data type (OpenIGTLink device type string)
 
|-
 
|-
−
| align="left" | NAMELEN (NELEMENTS-1)
+
| colspan=3 align="left" style="background:#e0e0e0;" |NAME Table
−
| align="left" | uint 8
 
−
| align="left" | Name length
 
 
|-
 
|-
−
| align="left" | SIZE (NELEMENTS-1)
+
| align="left" | NAME_TABLE_SIZE
−
| align="left" | uint 16
+
| align="left" | uint16
−
| align="left" | Data length
+
| align="left" | Size of name table (including the padding)
−
|-
 
−
| colspan=3 align="left" style="background:#e0e0e0;" |NAME Table
 
 
|-
 
|-
 
| align="left" | NAME 0
 
| align="left" | NAME 0
 
| align="left" | char[NAMELEN]
 
| align="left" | char[NAMELEN]
 
| align="left" | Name
 
| align="left" | Name
 +
|-
 +
| align="left" | NULL
 +
| align="left" | uint 8
 +
| align="left" | Separator
 
|-
 
|-
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
|-
 
|-
−
| align="left" | NAME (NELEMENTS-1)
+
| align="left" | NAME (NCMESSAGES-1)
−
| align="left" | char[NAMELEN (NELEMENTS-1)]
+
| align="left" | char[NAMELEN (NCMESSAGES-1)]
 
| align="left" | Name
 
| align="left" | Name
 +
|-
 +
| align="left" | NULL
 +
| align="left" | uint 8
 +
| align="left" | Separator
 
|-
 
|-
 
|}
 
|}
  
 
==STT_BIND==
 
==STT_BIND==
 +
GET_BIND is used to request the receiver for associative array data. If a GET_BIND message does not have a body, it requests all data.
  
 
{| border="1" cellpadding="5" cellspacing="0" align="center"
 
{| border="1" cellpadding="5" cellspacing="0" align="center"
Line 154: Line 166:
 
<center>or </center>
 
<center>or </center>
  
−
GET_BIND is used to request the receiver for associative array data. If a GET_BIND message does not have a body, it requests all data.
 
  
 
{| border="1" cellpadding="5" cellspacing="0" align="center"
 
{| border="1" cellpadding="5" cellspacing="0" align="center"
Line 166: Line 177:
 
| align="left" | Minimum interval between message (ns). Same format as [[OpenIGTLink/Timestamp|TimeStamp]]
 
| align="left" | Minimum interval between message (ns). Same format as [[OpenIGTLink/Timestamp|TimeStamp]]
 
|-
 
|-
−
| align="left" | NELEMENTS
+
| align="left" | NCMESSAGES
 
| align="left" | uint16
 
| align="left" | uint16
 
| align="left" | Number of elements
 
| align="left" | Number of elements
Line 175: Line 186:
 
| align="left" | char[12]
 
| align="left" | char[12]
 
| align="left" | Data type (OpenIGTLink device type string)
 
| align="left" | Data type (OpenIGTLink device type string)
−
|-
 
−
| align="left" | SIZE 0
 
−
| align="left" | uint 16
 
−
| align="left" | Data length
 
 
|-
 
|-
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
|-
 
|-
−
| align="left" | TYPE (NELEMENTS-1)
+
| align="left" | TYPE (NCMESSAGES-1)
−
| align="left" | uint8
+
| align="left" | char[12]
 
| align="left" | Data type (0: string, 1: scalar, 2: vector)
 
| align="left" | Data type (0: string, 1: scalar, 2: vector)
−
|-
 
−
| align="left" | SIZE (NELEMENTS-1)
 
−
| align="left" | uint 16
 
−
| align="left" | Data length
 
 
|-
 
|-
 
| colspan=3 align="left" style="background:#e0e0e0;" |NAME Table Section (NULL-separated values)
 
| colspan=3 align="left" style="background:#e0e0e0;" |NAME Table Section (NULL-separated values)
Line 206: Line 209:
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
| colspan=3 align="left" style="background:#f0f0f0;"|...
 
|-
 
|-
−
| align="left" | NAME (NELEMENTS-1)
+
| align="left" | NAME (NCMESSAGES-1)
 
| align="left" | char[*]
 
| align="left" | char[*]
 
| align="left" | Name
 
| align="left" | Name
Line 243: Line 246:
  
 
=Contributors=
 
=Contributors=
−
Junichi Tokuda, Yuichiro Hayashi
+
Junichi Tokuda
  
 
=Comments=
 
=Comments=

Latest revision as of 04:44, 30 November 2011

Home < OpenIGTLink < ProtocolV2 < Type < Bind

<< Version 2 Index Page

Summary

Bind message format is designed to bind any OpenIGTLink messages into a single message. Messages bound in a BIND message are called 'child messages.' The BIND message format is useful, when one needs to care about synchronization of multiple messages (e.g. multi-channel sensors), or sending associative array (pairs of key string and value). The bind message format consists of the bind header section, which contains types and sizes of child messages, the child message name table section, and the child message body section.

Message Types

BIND

Data Type Description
NCMESSAGES uint16 Number of child messages
Bind Header Section
TYPE 0 char[12] Data type (OpenIGTLink Device Type string) for child message 0
DATA SIZE 0 uint 64 Data size for child message 0
...
TYPE (NCMESSAGES-1) char[12] Data type (OpenIGTLink Device Type string) for child message (NCMESSAGES-1)
DATA SIZE (NCMESSAGES-1) uint 64 Data size for child message (NCMESSAGES-1)
NAME Table Section (NULL-separated values)
NAME_TABLE_SIZE uint16 Size of name table (including the padding)
NAME 0 char[*] Name for child message 0
(null) uint8 separator
...
NAME (NCMESSAGES-1) char[*] Name for child message (NCMESSAGES-1)
(null) uint8 separator
Padding* uint8 or none padding to align DATA with WORD
Data Section
DATA 0 TYPE 0 ( SIZE 0 ) Data array for child message 0
(Padding*) uint8 or none padding to align DATA with WORD
DATA 1 TYPE 1 ( SIZE 1 ) Data array for child message 1
(Padding*) uint8 or none padding to align DATA with WORD
...
DATA (NCMESSAGES-1) TYPE NCMESSAGE-1 (SIZE NCMESSAGE-1) Data array for child message NCMESSAGE-1
Padding* uint8 or none padding to align DATA with WORD
  • Padding field is inserted only if the previous field does not aligned with WORD border.

Feb 3, 2011: Padding fields are inserted in the data section.

GET_BIND

GET_BIND is used to request the receiver for associative array data. If a GET_BIND message does not have a body, it requests all data.

Data Type Description
NCMESSAGES uint16 Number of elements
Bind Header Section
TYPE 0 char[12] Data type (OpenIGTLink device type string)
...
TYPE (NCMESSAGES-1) char[12] Data type (OpenIGTLink device type string)
NAME Table
NAME_TABLE_SIZE uint16 Size of name table (including the padding)
NAME 0 char[NAMELEN] Name
NULL uint 8 Separator
...
NAME (NCMESSAGES-1) char[NAMELEN (NCMESSAGES-1)] Name
NULL uint 8 Separator

STT_BIND

GET_BIND is used to request the receiver for associative array data. If a GET_BIND message does not have a body, it requests all data.

Data Type Description
RESOL uint64 Minimum interval between message (ns). Same format as TimeStamp
or


Data Type Description
RESOL uint64 Minimum interval between message (ns). Same format as TimeStamp
NCMESSAGES uint16 Number of elements
Bind Header Section
TYPE 0 char[12] Data type (OpenIGTLink device type string)
...
TYPE (NCMESSAGES-1) char[12] Data type (0: string, 1: scalar, 2: vector)
NAME Table Section (NULL-separated values)
NAME_TABLE_SIZE uint16 Size of name table (including the padding)
NAME 0 char[*] Name
(null) uint8 separator
...
NAME (NCMESSAGES-1) char[*] Name
(null) uint8 separator

STP_BIND

Data Type Description

RTS_BIND

Data Type Description
Status 8 bit unsigned 0: Success 1: Error

Implementations

Contributors

Junichi Tokuda

Comments

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