User's Manual

Class 1 Bluetooth v2.0 Module
User’s Guide
Americas: [phone] Option 2
Europe: [phone]
Hong Kong: [phone]
www.lairdtech.com/bluetooth
82
CONN-GUIDE-BT730_v0.9
In addition, values in the range 050 to 099 and 250 to 299 inclusive are specific to this
Laird application and are defined as per the table below.
Response
Code
‘nnn’
(Laird Technologies Specific) Definition
050
Syntax Error / Command Unrecognized
051
Server sent unexpected information in OBEX packet
052
OBEX connection fail, because it is unauthorized
053
Memory allocation failure (Please contact Ezurio with details)
055
Unicode File/Folder name length cannot be an odd value
056
Command not recognized
090
An XML parsing error occurred (while processing response to DIR command)
099
The Bluetooth connection has unexpected been dropped (i.e., remote out of range etc.)
250
GET procedure was aborted
9.4.1 nnn OBX
This OBEX response is used to convey the outcome of a subcommand to the host where ‘nnn’ is a fixed
three digit decimal number as defined in the irDA specification and map to HTTP status codes.
For example, a value of n=200 implies successful operation, any other value usually conveys an error as
described in the irDA specification (except the range 050 to 099 inclusive and 250 to 299 inclusive).
Note: When a Bluetooth OBEX session is established, we will be specifying v1.0 in
the header packets by default.
9.5 OBEX Push Line Multiplexing Commands
When transferring an object, the single serial interface between the host and the module is used to send
and receive data and commands. This means a scheme is required to unambiguously determine when a
byte on the line corresponds to a command or data belonging to a file.
The module uses negotiated multiplexing to achieve this, and commands are used to toggle the line
between command and data mode.
This scheme is symmetrical and the commands for toggling the state of the line are relevant for both
direction. The only difference being that the terminator is <cr> in the host to module direction and <crlf> in
the reverse direction.
The commands are described in the following sub sections.
9.5.1 #
This command is used to ask the other end how many bytes of a filename or object it will send next.
9.5.2 >
This command is used to inform the other end that it is safe to send the number of bytes belonging to a
filename or object as indicated in the most recent # command.