Accept and ignore subsequent synchronous messages until it finds the synchronous DeviceClearComplete message. Send message back to the client (after the above steps are complete and it has DeviceClearAcknowledge received the device clear complete message). Resume normal operation. If at any time during device management either the client or server encounter a poorly formed message they shall send a message and do the processing. FatalError FatalError If at any time during the device clear management the client or server determines that the other device is not responding in a timely fashion, it shall send a message and do the processing. The FatalError FatalError determination of an appropriate time may vary with the application, 40 to 120 seconds are reasonable values. Feature Negotiation During device clear, the features listed in Table 24 are negotiated between the client and server. The features are specified through a feature bitmap that is sent in the control code of three different messages. The feature negotiation occurs in three steps: The server proposes values that it prefers with the message. AsyncDeviceClearAcknowledge The client indicates values that it requests in the messge. DeviceClearComplete The server indicates the values that both client and server will use in the message. DeviceClearAcknowledge The server shall identify the default values it prefers for the features in the message. AsyncDeviceClearAcknowledge Servers shall support any such capabilities that it requests. The server shall accept the value proposed by the client in the message if it is capable of DeviceClearComple supporting them. The client shall use the values specified by the server in the message. DeviceClearAcknowledge Note that the has the server preferred feature specified in it. InitializeResponse Features negotiated during device clear Control Code Bit Position Name Meaning 0 Overlapped False- Synchronized mode True - Overlapped mode
Accept and ignore subsequent synchronous messages until it finds the synchronous DeviceClearComplete message. Send DeviceClearAcknowledge message back to the client (after the above steps are complete and it has received the device clear complete message). Resume normal operation. If at any time during device management either the client or server encounter a poorly formed message they shall send a FatalError message and do the FatalError processing. If at any time during the device clear management the client or server determines that the other device is not responding in a timely fashion, it shall send a FatalError message and do the FatalError processing. The determination of an appropriate time may vary with the application, 40 to 120 seconds are reasonable values. Feature Negotiation During device clear, the features listed in Table 24 are negotiated between the client and server. The features are specified through a feature bitmap that is sent in the control code of three different messages. The feature negotiation occurs in three steps: The server proposes values that it prefers with the AsyncDeviceClearAcknowledge message. The client indicates values that it requests in the DeviceClearComplete messge. The server indicates the values that both client and server will use in the DeviceClearAcknowledge message. The server shall identify the default values it prefers for the features in the AsyncDeviceClearAcknowledge message. Servers shall support any such capabilities that it requests. The server shall accept the value proposed by the client in the DeviceClearComple message if it is capable of supporting them. The client shall use the values specified by the server in the DeviceClearAcknowledge message. Note that the InitializeResponse has the server preferred feature specified in it. Features negotiated during device clear Control Code Bit Position Name Meaning 0 Overlapped False- Synchronized mode True - Overlapped mode
IVI-6.1_HiSLIP-1.1-2011-02-24.docx