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
79
CONN-GUIDE-BT730_v0.9
 nnn shall be a decimal number with at least one digit.
 The backspace character is not supported.
 All OBEX commands are case sensitive.
 OBEX Commands shall not exceed 32 characters in total.
 While an OBEX session is open, the host shall not deassert the modules UART_CTS line and
conversely the host MUST always be ready to accept data.
 When Unicode data is transmitted, it shall be assumed that the most significant byte is transmitted
first.
 If an OBEX command is expecting a Unicode string as a parameter and the host has an ASCII
string, the string shall be expanded with a 0 byte in the most significant position.
9.2 OBEX Push related AT Commands
9.2.1 AT+OPS<bd_addr>
This command is used to establish a connection to an Obex Push server profile in a
peer device with Bluetooth address <bd_addr>.
9.2.2 ATSn=m
The following values of n are relevant to OBEX operation: 582. A description of these
values is given on page 18 TBC.
9.3 OBEX Push related Subcommands
This section describes Obex Push-related subcommands that the host can use to control the OBEX Push
session.
9.3.1 PUT <filename> length(Send file)
This OBEX subcommand is used to send a file to the obex server.
The length of <filename> shall not exceed 24 characters.
The length value is inserted into the OBEX length header field.
There is some ambiguity as to how the first obex PUT packet is formed with respect to
the ‘Body’header. The OBEX specification does not prohibit the first ‘Body’ header to be empty, neither
does it say that it must NOT be empty. If the first body is NOT empty when sending a file to a Nokia6820
phone then it seems to confuse it. Hence Laird sends out an empty ‘Body’ header by default as does the
Windows PC based Widcomm Bluetoothstack.
To cater for future devices which NEED the first ‘Body’ header to be non-empty, a new S Register582 has
been added to allow a host to have control over how the first body header is constructed.
The new S register 582 takes values in the range 0 to 1. The default value is 0 which implies that the first
‘Body’ header in the PUT obex packet is empty. A value of 1 forces that ‘Body’ header to have one byte of
data – and in this case when the module prompts the host for a length value it shall respond accordingly.
Hopefully the default value of zero suffices for all occasions but, in case it does not, we provide the
control to modify the packet as required.