Actions

Difference between revisions of "Device"

From Zenitel Wiki
m (1 revision imported)
 
(43 intermediate revisions by 9 users not shown)
Line 1: Line 1:
−
All data messages are addressed to a device.  A device is always related to (owned by) a [[node]].<br>
+
{{A}}
−
A full device address consists of <node> <device>.<br>
+
Examples of '''device''' types are AlphaCom [[module]], [[RIO]], [[AlphaPro]], [[AlphaVision]]. 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.
−
<Node> is one byte.<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. Note that devices can both be physical boxes (e.g. RIO) or a function (Router).<br>
 +
 
 +
{| border="1"
 +
! style="background:#ffdead;" width="100" |Value (decimal)
 +
! style="background:#ffdead;" width="100" |Value (Hex)
 +
! style="background:#ffdead;" width="600" |Device Function
 +
|-
 +
| align=right | 0 || align=right | 0x00 || Invalid device (reserved NULL value)
 +
|-
 +
| align=right | 1 - 64 || align=right | 0x01 - 0x40 || '''External boxes'''.  [[RIO|RIOs]], PCs ([[AlphaVision]]) 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 [[MultiModule|multi-module]] slave AMCs.
 +
* 66 = Slave 1
 +
* 67 = Slave 2
 +
* 68 = Slave 3
 +
|-
 +
| align=right | 69 || align=right | 0x45 || (Reserved more slaves)
 +
|-
 +
| align=right | 128 - 197 || align=right | 0x80 - 0xC3 || (Future use)
 +
|-
 +
| align=right | 196 || align=right | 0xC4 || ([[OPC Server|OPC server 2]] PC)
 +
|-
 +
| align=right | 197 || align=right | 0xC5 || [[SIPD]] (SIPD also acts as an virtual AlphaNet [[node]], this is how SIP trunks are configured now)
 +
|-
 +
| align=right | 198 || align=right | 0xC6 || [[ABSD_Billing]]
 +
|-
 +
| align=right | 199 || align=right | 0xC7 || ([[OPC Server|OPC server 1]] PC)
 +
|-
 +
| 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.<br>
 +
Numbers above 210 are used with [[System Status (Event Type)]] for reporting related to non-device objects.
 +
|-
 +
|}
 +
<br>
 +
<br>
 +
 
 +
[[Category: AMC Software]]
 +
[[Category:AlphaNet]]

Latest revision as of 13:46, 5 February 2018

AlphaCom icon 300px.png

Examples of device types are AlphaCom module, RIO, AlphaPro, AlphaVision. 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.
  • 66 = Slave 1
  • 67 = Slave 2
  • 68 = Slave 3
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.



Retrieved from "https://wiki.zenitel.com/w/index.php?title=Device&oldid=2473"