Client response hooks
The hooks that deliver answers to the requests your application sent.
Match a response hook to its request by the invoke id and the peer it came from. A confirmed request normally ends in a SimpleAck, Error, Reject, Abort or Timeout, or, for a service that returns data, in a raw response you decode yourself. A ReadPropertyMultiple can produce several Error hook calls (one per failed property) alongside its data, and BACnetStack_Reset() abandons pending requests without a Timeout. The I-Am and I-Have hooks deliver unsolicited announcements and carry no invoke id.
Functions
Section titled “Functions”| Function | Summary |
|---|---|
BACnetStack_RegisterHookIAm() |
Registers a hook the stack calls when an I-Am is received, delivering the announcing device’s identity and communication parameters. |
BACnetStack_RegisterHookIHave() |
Registers a hook the stack calls when an I-Have is received, delivering the object identity found in response to a previously sent Who-Has. |
BACnetStack_RegisterHookError() |
Registers a hook the stack calls when an error is reported for a confirmed request this client sent. |
BACnetStack_RegisterHookReject() |
Registers a hook the stack calls when a Reject PDU is received in response to a confirmed request this client sent. |
BACnetStack_RegisterHookAbort() |
Registers a hook the stack calls when an Abort PDU is received for a confirmed request this client sent. |
BACnetStack_RegisterHookSimpleAck() |
Registers a hook the stack calls when a SimpleACK is received in response to a confirmed request this client sent (a request that has no data to return beyond acknowledging success). |
BACnetStack_RegisterHookTimeout() |
Registers a hook the stack calls when a confirmed request this client sent finally times out. |