Difference between revisions of "OpenIGTLink/ProtocolV2/Type/Capability"
| Line 33: | Line 33: | ||
Number of type names '''N''' is calculated by (Body size) / 12. | Number of type names '''N''' is calculated by (Body size) / 12. | ||
| − | == | + | ==GET_CAPABIL== |
{| border="1" cellpadding="5" cellspacing="0" align="center" | {| border="1" cellpadding="5" cellspacing="0" align="center" | ||
|- | |- | ||
| Line 42: | Line 42: | ||
|} | |} | ||
| − | == | + | ==STT_CAPABIL== |
N/A | N/A | ||
| − | == | + | ==STP_CAPABIL== |
N/A | N/A | ||
Revision as of 03:48, 30 June 2010
Home < OpenIGTLink < ProtocolV2 < Type < CapabilityContents
Summary
The CAPABILITY data type lists the names of message types that the receiver can interpret. Although the OpenIGTLink protocol guarantees that any receiver can at least skip messages with unknown type and continue to interpret the following messages, it is a good idea to get the capability information at system startup to ensure application-level compatibility of various devices. In a CAPABILITY message type, each message type name comes with format version number. If the receiver can interpret multiple versions for a certain message type, they should be listed as independent types.
Message Types
CAPABILITY
| Data | Type | Description |
| TYPE_0 | unsigned char [12] | Type name #0 |
| Type_1 | unsigned char [12] | Type name #1 |
| ... | ... | ... |
| Type_(N-1) | unsigned char [12] | Type name #N-1 |
Number of type names N is calculated by (Body size) / 12.
GET_CAPABIL
| Data | Type | Description |
STT_CAPABIL
N/A
STP_CAPABIL
N/A
Implementations
POSITION type is implemented in the following files:
Contributors
This message was originally proposed in version 1.
