Difference between revisions of "OpenIGTLink/ProtocolV2/Type/Bind"
From NAMIC Wiki
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[OpenIGTLink/ProtocolV2/ | + | [[OpenIGTLink/ProtocolV2/Index | << Version 2 Index Page]] |
=Summary= | =Summary= | ||
| Line 150: | Line 150: | ||
==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 165: | Line 166: | ||
<center>or </center> | <center>or </center> | ||
| − | |||
{| border="1" cellpadding="5" cellspacing="0" align="center" | {| border="1" cellpadding="5" cellspacing="0" align="center" | ||
| Line 186: | 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) | ||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| colspan=3 align="left" style="background:#f0f0f0;"|... | | colspan=3 align="left" style="background:#f0f0f0;"|... | ||
|- | |- | ||
| align="left" | TYPE (NCMESSAGES-1) | | align="left" | TYPE (NCMESSAGES-1) | ||
| − | | align="left" | | + | | align="left" | char[12] |
| align="left" | Data type (0: string, 1: scalar, 2: vector) | | align="left" | Data type (0: string, 1: scalar, 2: vector) | ||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| 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 254: | Line 246: | ||
=Contributors= | =Contributors= | ||
| − | Junichi Tokuda | + | Junichi Tokuda |
=Comments= | =Comments= | ||
Latest revision as of 04:44, 30 November 2011
Home < OpenIGTLink < ProtocolV2 < Type < BindContents
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 |
| 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
