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
80
CONN-GUIDE-BT730_v0.9
9.3.2 PUT –nnnlength(Send file)
This OBEX subcommand is used to send a file to the OBEX push server where the filename is in
UNICODE text and the filename is –nnn bytes long.
The length value is inserted into the OBEX length header field.
See comment above with regards to S Reg 582 TBC.
9.3.3 ABORT(Abort current OBEX command)
This OBEX subcommand is used to abort a file transfer where appropriate.
To abort a PUT session, please send 0 when the module prompts for a length value.
9.3.4 QUIT ( Terminate the OBEX Push session)
This OBEX subcommand is used to terminate the OBEX push session and also results in the Bluetooth
connection being terminated.
9.3.5 MAX(Max outgoing OBEX packet size)
This OBEX subcommand is used to get the maximum obex packet size tolerated by server and can be
used by the host to optimize the data throughput.
9.3.6 WHO(Identify current profile)
This OBEX subcommand is used to identify the current profile. 0 means Obex Push and 1 means FTP.
9.4 OBEX Push Related Subresponses
All Obex Push-related sub responses sent from the module to the host are 11 characters long in the
following format:
<cr><lf>nnn AAA<cr><lf>.
The characters nnn shall be decimal digits ‘0’ to ‘9’, then there is a space character and finally a 3
character word followed by <cr><lf>.
The <cr><lf> envelope plus the fixed length hopefully makes the parsing task in the host much simpler.
Values for ‘nnn’ are as specified for HTTP status codes and reproduced from the OBEX specification as
indicated in Table 9-1.
Table 9-1: OBEX response and HTTP status codes
OBEX Response
Code
HTTP Status
Code
Definition
0x00to 0x0F
None
Reserved
0x10(0x90)
100
Continue
0x20(0xA0)
200
OK, Success
0x21(0xA1)
201
Created
0x22(0xA2)
202
Accepted
0x23(0xA3)
203
Non-Authoritative Information