This FAQ covers how IR ports are addressed on the TCP API. For more information about the APIs, or for information about our HTTP API please refer to the APIs in our downloads section.
All of our networked Infrared (IR) products have individually addressable IR outputs. IR ports are addressed within the IR code format by the <module> and <connector> fields.
IR codes follow the following format:
sendir,<module>,<connector>,...
The example IR code below has a <module> of 2 and a <connector> of 1. The module and connector fields have been underlined respectively:
sendir,2:1,1,38000,10,1,500,500
GC-100-06:
The GC-100-06 has IR ports on module 2. The module has 3 connectors.
Valid <module>:<connector> values:
- 2:1
- 2:2
- 2:3
GC-100-12/18/18R:
The GC-100-12/18/18R units have IR ports on modules 4 and 5. Each module has 3 connectors.
Valid <module>:<connector> values:
- 4:1
- 4:2
- 4:3
- 5:1
- 5:2
- 5:3
iTach IP2IR/iTach WF2IR:
The iTach family has IR ports on module 1. The module has 3 connectors.
valid <module>:<connector> values:
- 1:1
- 1:2
- 1:3
iTach Flex IP/iTach Flex WF:
The iTach Flex family has IR ports on module 1. The module has up to 3 connectors.
valid <module>:<connector> values:
- 1:1
- 1:2
- 1:3
Note: The Flex can be configured for a single IR output mode. In that mode all IR commands, regardless of connector value, will go out on the single IR emitter/blaster.
Global Connect Infrared Module:
Each Global Connect IR module has IR ports on module 1. The module has 3 connectors.
valid <module>:<connector> values:
- 1:1
- 1:2
- 1:3
0 Comments