
www.national.com
34
L
12.0 Command Interface
The LMX9830 offers Bluetooth functionality in either a self
contained slave functionality or over a simple command
interface. The interface is listening on the UART interface.
The following sections describe the protocol transported on
the UART interface between the LMX9830 and the host in
command mode (see Figure 23). In Transparent mode, no
data framing is necessary and the device does not listen
for commands.
12.1 FRAMING
The connection is considered “Error free”. But for packet
recognition and synchronization, some framing is used.
All packets sent in both directions are constructed per the
model shown in Table 25.
12.1.1 Start and End Delimiter
The “STX” char is used as start delimiter: STX = 0x02. ETX
= 0x03 is used as end delimiter.
12.1.2 Packet Type ID
This byte identifies the type of packet. See Table 26 for
details.
12.1.3 Opcode
The opcode identifies the command to execute. The
opcode values can be found within the “LMX9830 Software
User’s Guide”
included within the LMX9830 Evaluation
Board.
12.1.4 Data Length
Number of bytes in the Packet Data field. The maximum
size is defined with 333 data bytes per packet.
12.1.5 Checksum:
This is a simple Block Check Character (BCC) checksum of
the bytes “Packet type”, “Opcode” and “Data Length”. The
BCC checksum is calculated as low byte of the sum of all
bytes (e.g., if the sum of all bytes is 0x3724, the checksum
is 0x24).
.
Figure 23. Bluetooth Functionality
LMX9830
UART
Existing device
without Bluetooth
capabilities
UART
Table 25. Package Framing
Start
Delimiter
Packet
Type ID
Opcode
Data Length
Checksum
Packet Data
End
Delimiter
1 Byte
1 Byte
1 Byte
2 Bytes
1 Byte
<Data Length> Bytes
1 Byte
- - - - - - - - - - - - - Checksum - - - - - - - - - - - - -
Table 26. Packet Type Identification
ID
Direction
Description
0x52
‘R’
REQUEST
(REQ)
A request sent to the Bluetooth module.
All requests are answered by exactly one confirm.
0x43
‘C’
Confirm
(CFM)
The Bluetooth modules confirm to a request.
All requests are answered by exactly one confirm.
0x69
‘i’
Indication
(IND)
Information sent from the Bluetooth module that is not a direct confirm to a request.
Indicating status changes, incoming links, or unrequested events.
0x72
‘r’
Response
(RES)
An optional response to an indication.
This is used to respond to some type of indication message.