Host application shall be able to deactivate the transmission trigger timer for application-triggered and change-of-state connections

Usually, connections of type "application triggered" or "change-of-state" produce process data frames on the network autonomuously (keep alive frames) based on the API (accepted packet interval) even if the host application does not provide new data to the protocol stack. This avoids connection timeouts in case the host application is not "fast" enough to provided new data in time.

E.g. CIP-Safety applications shall have the possibility to deactivate this behavior as they do not want "keep-alive" frames to show up on the network. When deactivated, process data frames shall only be sent when the host application provides new data to the protocol stack. This applies to connections of type application-triggered and change-of-state only.