Get at least one ACK per request during response period.
D7A_RESP_ALL_ON_DATA
Same as D7A_RESP_ALL, but responders respond only if upper layer payload is available It is suitable for cases when the smart addressing (queries) is used.
D7A_RESP_NO_RPT
No response requested, repeat the number of times defined in the SEL configuration file.
D7A_RESP_ANY_ON_DATA
Same as D7A_RESP_ANY, but responders respond only if upper layer payload is available It is suitable for cases when the smart addressing (queries) is used.
D7A_RESP_PREFERRED
Get at least one acknowledgement per request during response period.
Stick to a single responder when possible
D7A_RESP_PREFERRED_ON_DATA
Same as D7A_RESP_PREFERRED, but responders respond only if upper layer payload is available It is suitable for cases when the smart addressing (queries) is used.
Single request, try once (context cleaned upon completion) Suitable for low QoS or QoS managed by the application.
D7A_RETRY_ONESHOT_RETRY
Single request, retry 3 times (context cleaned upon completion) Suitable for higher QoS or QoS managed by the application.
D7A_RETRY_FIFO_FAST
FIFO mode with fast retry pattern (context kept on completion) Suitable for periodic frequent chart-type ActP notifications (< ~10s between messages)
D7A_RETRY_FIFO_SLOW
FIFO mode with slow retry pattern (context kept on completion) Suitable for periodic unfrequent chart-type ActP notifications (> ~10s between messages)
D7A_RETRY_SINGLE_FAST
Single ("last-is-best") mode with fast retry pattern (context kept on completion) Suitable for periodic frequent state-type ActP notifications (< ~10s between messages)
D7A_RETRY_SINGLE_SLOW
Single ("last-is-best") mode with slow retry pattern (context kept on completion) Suitable for periodic unfrequent state-type ActP notifications (> ~10s between messages)
D7A_RETRY_ONESHOT_STICKY
Single request, retry 8 times or more (context cleaned upon completion) Suitable for rare ActP notifications with higher priority (revision, etc).
Suitable for application requests where the QoS is managed by the stack or the completion is not expected synchronously (could be very long)
This site uses cookies to store information on your computer.
By continuing to use our site, you consent to our cookies.
If you are not happy with the use of these cookies, please review our
Cookie Policy
to learn how they can be disabled.
By disabling cookies, some features of the site will not work.
Access Warning
You do not have the correct permissions to perform this operation.