Difference between revisions of "Node"
From Zenitel Wiki
| Line 7: | Line 7: | ||
! style="background:#ffdead;" width="600" |Node Type | ! style="background:#ffdead;" width="600" |Node Type | ||
|- | |- | ||
| − | | align=right | 0 || align=right | 0x00 || | + | | align=right | 0 || align=right | 0x00 || Node 0 is interpreted by the exchange which receives it as “own node”, and it will replace the value 0 with it’s own node number before processing takes place. |
| + | Response messages will thus NOT contain any node 0 references | ||
|- | |- | ||
|align=right | 1 - 64 || align=right | 0x01 - 0x40 || External boxes. RIOs, PCs etc. | |align=right | 1 - 64 || align=right | 0x01 - 0x40 || External boxes. RIOs, PCs etc. | ||
Revision as of 23:17, 19 June 2007
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>.
<Node> is one byte.
| Value (decimal) | Value (Hex) | Node Type |
|---|---|---|
| 0 | 0x00 | Node 0 is interpreted by the exchange which receives it as “own node”, and it will replace the value 0 with it’s own node number before processing takes place.
Response messages will thus NOT contain any node 0 references |
| 1 - 64 | 0x01 - 0x40 | External boxes. RIOs, PCs etc. |