Difference between revisions of "Device"
From Zenitel Wiki
Line 2: | Line 2: | ||
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'''>. <br> | 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'''>. <br> | ||
− | <'''Device'''> is one byte. | + | <'''Device'''> is one byte. Note that devices can both be physical boxes (e.g. RIO) or a function (Router).<br> |
− | Note that devices can both be physical boxes (e.g. RIO) or a function (Router).<br> | ||
{| border="1" | {| border="1" |
Revision as of 14:07, 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. |