When receiving messages if the MessageID is not 0xffff ffff, then verify that the MessageID indicated Data in the message is the MessageID that the client sent to the server with the most recent Data Data, DataEND or message. Trigger If the MessageIDs do not match, the client shall clear any responses already buffered and discard the Data offending message. Data When the client sends or if there are any whole or partial server messages that have Data, DataEND Trigger been validated per rules and and buffered they shall be cleared. When the client receives or it shall clear any whole or partial server messages Interrupted AsyncInterrupted that have been validated per rules and . If the client initially detects it shall also discard any further or messages AsyncInterrupted Data DataEND from the server until is encountered. Interrupted If the client detects before it detects the client shall not send any further Interrupted AsyncInterrupted, messages until is received. AsyncInterrupted Clients shall maintain a MessageID count that is initially set to 0xffff ff00. When clients send or Data, DataEND messages, they shall set the message parameter field of the message header to the current MessageID and Trigger increment the MessageID by two in an unsigned 32-bit sense (permitting wrap-around). The MesssageID is reset to 0xffff ff00 after device clear, and when the connection is initialized. After interrupted error processing is complete, the client resumes normal operation.
When receiving Data messages if the MessageID is not 0xffff ffff, then verify that the MessageID indicated in the Data message is the MessageID that the client sent to the server with the most recent Data, DataEND or Trigger message. If the MessageIDs do not match, the client shall clear any Data responses already buffered and discard the offending Data message. When the client sends Data, DataEND or Trigger if there are any whole or partial server messages that have been validated per rules and and buffered they shall be cleared. When the client receives Interrupted or AsyncInterrupted it shall clear any whole or partial server messages that have been validated per rules and . If the client initially detects AsyncInterrupted it shall also discard any further Data or DataEND messages from the server until Interrupted is encountered. If the client detects Interrupted before it detects AsyncInterrupted, the client shall not send any further messages until AsyncInterrupted is received. Clients shall maintain a MessageID count that is initially set to 0xffff ff00. When clients send Data, DataEND or Trigger messages, they shall set the message parameter field of the message header to the current MessageID and increment the MessageID by two in an unsigned 32-bit sense (permitting wrap-around). The MesssageID is reset to 0xffff ff00 after device clear, and when the connection is initialized. After interrupted error processing is complete, the client resumes normal operation.
IVI-6.1_HiSLIP-1.1-2011-02-24.docx