1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
[Back to Index](/Documents/Protocol/index.md)
Capability Message
==================
- Protocol Version: 3.0
- Release Date: January 20, 2017
Summary
=======
The CAPABILITY 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 | uint8[12] | Type name #0
... | ... |
TYPE_(N_TYPE)| uint8[12] | Type name #(N_TYPE)
* Number of type names (N_TYPE) is calculated by BODY_SIZE / 12.
GET_CAPABIL
-----------
Data | Type | Description
--------------|---------------|-------------------------------------------------
| |
STT_CAPABIL
-----------
N/A
STP_CAPABIL
-------------------
N/A
RTS_CAPABIL
-------------------
N/A
Implementations
===================
* [igtlCapabilityMessage.h](/Source/igtlCapabilityMessage.h)
* [igtlCapabilityMessage.cxx](/Source/igtlCapabilityMessage.cxx)
Contributors
===================
Junichi Tokuda
|
