Installers Guide to the Bose® Serial interface June 28, 2011
Bose Confidential Information Page 10/42 Do Not Redistribute
Table 4-2 Packet Status Flags
0 - No Error
1 - Error has occurred. Payload contains the
error information.
(See Section 5.3.3 Error Packets
0 - This is not a notification packet
1 - This is a notification packet
(See Section 5.3.4 Notification Packets.)
0 - For packets sent by the Client
1 - For packets sent by the Console
4.1.2.1 The Error Bit
On packets from the Console, the Error bit and Notification bit will never both be set. If the Error
bit is set, a protocol error has occurred (See section 5.3.3 Error Packets ).
The only protocol error possible on a debugged Client would be due to packet data corruption,
loss, or timeout. When the Console sends an error packet indicating corruption, the Client should
simply retry the command.
4.1.2.2 The Notification Bit
The Console occasionally sends Notification packets to indicate internal Console states, which
are normally not of interest to the Client. Thus if the Notification flag (bit 3) is set, then the packet
contents should normally be ignored by the Client. One Notification packet that could be useful to
a Client is notification that a key has been pressed on the Console or a remote. This notification
packet is only sent if the Client has enabled Key Press notifications (See section 5.3.4.1 Key
Press Notification Packets).
4.1.3 OpCode
The Operation code is always two bytes and indicates the operation requested of the Console.
See the value listed for individual commands in section 6 Client Commands and Console
Responses.
4.1.4 Payload
Content and length varies. See individual commands in section 6 Client Commands and Console
Responses for details.
To Next Page
Loading...
Need help?
General
