Difference between revisions of "Device"
From Zenitel Wiki
Line 9: | Line 9: | ||
! style="background:#ffdead;" width="600" |Device Function | ! style="background:#ffdead;" width="600" |Device Function | ||
|- | |- | ||
− | | align= | + | | align=right | 0 || align=right | 0x00 || Invalid device (reserved NULL value) |
|- | |- | ||
− | | align= | + | | align=right | 1 - 64 || align=right | 0x01 - 0x40 || External boxes. RIOs, PCs etc. |
+ | |- | ||
+ | | align=right | 65 || align=right | 0x41 || The AlphaCom Intercom Exchange - Master AMC<br\>This is the device address for messages to/from the exchange. | ||
+ | |- | ||
+ | | align=right | 66 - 68 || align=right | 0x42 - 0x44 || AlphaCom multi-module slave AMCs. <br\>(Can NOT be controlled via the AlphaCom data protocol) | ||
+ | |- | ||
+ | | align=right | 69 || align=right | 0x45 || (Reserved more slaves) | ||
+ | |- | ||
+ | | align=right | 128 - 199 || align=right | 0x80 - 0xC7 || (Future use) | ||
+ | |- | ||
+ | | align=right | 200 || align=right | 0xC8 || Bitbucket - valid “ignore” address<br\>Use as message source if you don’t want a response. | ||
+ | |- | ||
+ | | align=right | 201 - 202 || align=right | 0xC9 - 0xCA || (Future use) | ||
+ | |- | ||
+ | | align=right | 203 || align=right | 0xCB || AlphaPro PC | ||
+ | |- | ||
+ | | align=right | 204 || align=right | 0xCC || Data router (used with ISO1745) | ||
+ | |- | ||
+ | | align=right | 205 || align=right | 0xCD || Audio Path Router (used in AlphaNet) | ||
+ | |- | ||
+ | | align=right | 206 || align=right | 0xCE || TouchLine command interpreter (TL exchanges only) | ||
+ | |- | ||
+ | | align=right | 208 - 255 <br\><br\><br\><br\><br\><br\>||align=right | 0xD0 - 0xFF <br\><br\><br\><br\><br\><br\>|| Broadcast<br\>- When an external device sends a message addressed to <node><broadcast>, the addressed <node> exchange will send this message out on all it’s ports with the Broadcast option enabled. <br\>- It’s up to each connected device to actually handle or ignore the broadcast. <br\>- '''Broadcast to ALL devices is by convention device 0xFF'''.<br\>- There is currently no pre-defined use of other broadcast addresses. They may be used to address groups of devices. | ||
+ | |||
|- | |- | ||
|} | |} |
Revision as of 14:36, 22 June 2007
Examples of device types are AlphaCom module, RIO, AlphaPro, Control Handler. All such devices have a unique device address when interconnected. The AlphaCom and AlphaPro have fixed device address, while the device address of e.g. a RIO is configured (inside the RIO) for the particular application.
All ACDP data messages are addressed to a device. A device is always related to (owned by) a node. A full device address consists of <node> <device>.
<Device> is one byte. Note that devices can both be physical boxes (e.g. RIO) or a function (Router).
Value (decimal) | Value (Hex) | Device Function |
---|---|---|
0 | 0x00 | Invalid device (reserved NULL value) |
1 - 64 | 0x01 - 0x40 | External boxes. RIOs, PCs etc. |
65 | 0x41 | The AlphaCom Intercom Exchange - Master AMC<br\>This is the device address for messages to/from the exchange. |
66 - 68 | 0x42 - 0x44 | AlphaCom multi-module slave AMCs. <br\>(Can NOT be controlled via the AlphaCom data protocol) |
69 | 0x45 | (Reserved more slaves) |
128 - 199 | 0x80 - 0xC7 | (Future use) |
200 | 0xC8 | Bitbucket - valid “ignore” address<br\>Use as message source if you don’t want a response. |
201 - 202 | 0xC9 - 0xCA | (Future use) |
203 | 0xCB | AlphaPro PC |
204 | 0xCC | Data router (used with ISO1745) |
205 | 0xCD | Audio Path Router (used in AlphaNet) |
206 | 0xCE | TouchLine command interpreter (TL exchanges only) |
208 - 255 <br\><br\><br\><br\><br\><br\> | 0xD0 - 0xFF <br\><br\><br\><br\><br\><br\> | Broadcast<br\>- When an external device sends a message addressed to <node><broadcast>, the addressed <node> exchange will send this message out on all it’s ports with the Broadcast option enabled. <br\>- It’s up to each connected device to actually handle or ignore the broadcast. <br\>- Broadcast to ALL devices is by convention device 0xFF.<br\>- There is currently no pre-defined use of other broadcast addresses. They may be used to address groups of devices. |