Difference between revisions of "COMMAND RESPONSE"
From Zenitel Wiki
| Line 10: | Line 10: | ||
|align=center|1||[[UINT2]]||colspan="3"|The message_id that this message is a response to.<br\>Example: 0x0065 if this message is a response to [[CANCEL_MAIL]]. | |align=center|1||[[UINT2]]||colspan="3"|The message_id that this message is a response to.<br\>Example: 0x0065 if this message is a response to [[CANCEL_MAIL]]. | ||
|- | |- | ||
| − | |align=center|2||[[UINT1]]||colspan="3"|Command status, possible values are: <br\>1 = Command performed successfully. <br>2 = Target was busy, no queuing. <br\>3 = Internal resource was busy, no queuing. <br\>4 = Access not allowed. <br\>5 = Target busy, command queued. <br\>6 = Target HW failed/not present. | + | |align=center|2||[[UINT1]]||colspan="3"|Command status, possible values are: <br\>1 = Command performed successfully. <br>2 = Target was busy, no queuing. <br\>3 = Internal resource was busy, no queuing. <br\>4 = Access not allowed. (OPC no license)<br\>5 = Target busy, command queued. <br\>6 = Target HW failed/not present (OPC dual registration of same OPC device from different nodes). |
|- | |- | ||
|align=center|3||[[UINT4]]||colspan="3"|Command response options: <br\>Additional information about the execution of the message. Interpretation of this field is dependent on the message id, see separate descriptions under each message having this message as response. | |align=center|3||[[UINT4]]||colspan="3"|Command response options: <br\>Additional information about the execution of the message. Interpretation of this field is dependent on the message id, see separate descriptions under each message having this message as response. | ||
Revision as of 09:04, 6 September 2010
| COMMAND_RESPONSE | 0x0066 | 102 | AMC 07.00 | |
|---|---|---|---|---|
| General response message to messages introduced in AMC07.00 or newer messages.<br\>(COMMAND_RESPONSE is used rather than dedicated XXX_ACK and XXX_NAK messages ) | ||||
| 1 | UINT2 | The message_id that this message is a response to.<br\>Example: 0x0065 if this message is a response to CANCEL_MAIL. | ||
| 2 | UINT1 | Command status, possible values are: <br\>1 = Command performed successfully. 2 = Target was busy, no queuing. <br\>3 = Internal resource was busy, no queuing. <br\>4 = Access not allowed. (OPC no license)<br\>5 = Target busy, command queued. <br\>6 = Target HW failed/not present (OPC dual registration of same OPC device from different nodes). | ||
| 3 | UINT4 | Command response options: <br\>Additional information about the execution of the message. Interpretation of this field is dependent on the message id, see separate descriptions under each message having this message as response. | ||