Difference between revisions of "Device"
From Zenitel Wiki
m (Text replacement - "<br\>" to "<br />") |
|||
Line 1: | Line 1: | ||
+ | {{A}} | ||
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. | 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. | ||
Revision as of 15:17, 21 February 2017
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 (AlphaVision) etc. |
65 | 0x41 | The AlphaCom Intercom Exchange - Master AMC This is the device address for messages to/from the exchange. |
66 - 68 | 0x42 - 0x44 | AlphaCom multi-module slave AMCs.
|
69 | 0x45 | (Reserved more slaves) |
128 - 197 | 0x80 - 0xC3 | (Future use) |
196 | 0xC4 | (OPC server 2 PC) |
197 | 0xC5 | SIPD (SIPD also acts as an virtual AlphaNet node, this is how SIP trunks are configured now) |
198 | 0xC6 | ABSD_Billing |
199 | 0xC7 | (OPC server 1 PC) |
200 | 0xC8 | Bitbucket - valid “ignore” address 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 |
0xD0 - 0xFF |
Broadcast - 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. - It’s up to each connected device to actually handle or ignore the broadcast. - Broadcast to ALL devices is by convention device 0xFF. - There is currently no pre-defined use of other broadcast addresses. They may be used to address groups of devices. Numbers above 210 are used with System Status (Event Type) for reporting related to non-device objects. |