Reference Manual
Table Of Contents
- Introduction
- Electrical specifications
- Pinout
- Quick start
- Functional description
- State indication using the LED pins
- Sleep mode
- Identification of a Proteus-III device on the radio
- Connection based data transmission, with or without security
- Unidirectional connectionless data transmission using Beacons
- Energy-efficient distance estimation solutions
- Configure the module for low power consumption
- Start the direct test mode (DTM)
- Using the 2 MBit and LE Coded phy
- Connection setup using LE Coded phy
- Host connection
- The command interface
- Scan for other modules in range
- Setup connections
- Transmit and receive data
- Configuring the module and modifying the device settings
- Manage the device state
- Run the Bluetooth test modes
- Switching GPIOs by remote control
- Other messages
- Message overview
- UserSettings - Module configuration values
- FS_DeviceInfo: Read the chip type and OS version
- FS_FWVersion: Read the firmware version
- FS_MAC: Read the MAC address
- FS_BTMAC: Read the BLE conform MAC address
- FS_SerialNumber: Read the serial number of the module
- RF_DeviceName: Modify the device name
- RF_StaticPasskey: Modify the static passkey
- RF_SecFlags: Modify the security settings
- RF_SecFlagsPerOnly: Modify the security settings (Peripheral only mode)
- RF_ScanFlags: Modify the scan behavior
- RF_BeaconFlags: Interprete the advertising data
- RF_AdvertisingTimeout: Modify the advertising timeout
- RF_AdvertisingFlags: Configure the advertising packet
- RF_ScanFactor: Modify the scan factor
- RF_ScanTiming: Modify the scan timing
- RF_ConnectionTiming: Modify the connection timing
- RF_TXPower: Modify the output power
- RF_SPPBaseUUID: Configure the SPP base UUID
- RF_Appearance: Configure the appearance of the device
- UART_ConfigIndex: Modify the UART speed
- CFG_Flags: Configure the module
- DIS_ManufacturerName: Configure the manufacturer name
- DIS_ModelNumber: Configure the model number
- DIS_SerialNumber: Configure the serial number
- DIS_HWVersion: Configure the HW version
- DIS_SWVersion: Configure the SW version
- DIS_Flags: Configure the device information service
- Timing parameters
- Peripheral only mode
- Remote GPIO control
- Customizing the Proteus-III
- Custom firmware
- Firmware update
- Firmware history
- Design in guide
- Reference design
- Manufacturing information
- Physical dimensions
- Marking
- Bluetooth SIG listing/qualification
- Regulatory compliance information
- Important notes
- Legal notice
- License terms
7 The command interface
The module acts as a slave and can be fully controlled by an external host. The configuration
as well as the operation of the module can be managed by predefined commands that are
sent as telegrams over the UART interface of the module.
The commands of the command interface can be divided into 3 groups:
• Requests: The host requests the module to trigger any action, e.g. in case of the
request
CMD_RESET_REQ
the host asks the module to perform a reset.
• Confirmations: On each request, the module answers with a confirmation message
to give a feedback on the requested operation status. In case of a
CMD_RESET_REQ
,
the module answers with a
CMD_RESET_CNF
to tell the host whether the reset will be
performed or not.
• Indications and Responses: The module indicates spontaneously when a special event
has occurred. The
CMD_CONNECT_IND
indicates for example that a connection has been
established.
Start signal Command Length Payload CS
0x02 1 Byte 2 Byte, LSB first Length Bytes 1 Byte
Start signal: 0x02 (1 Byte)
Command: One of the predefined commands (1 Byte).
Length: Specifies the length of the data that follows. Length is a 16 Bit field with LSB first.
Payload: Variable number (defined by the length field) of data or parameters.
Checksum: Byte wise XOR combination of all preceding Bytes including the start signal,
i.e. 0x02 ˆ Command ˆ Length ˆ Payload = CS
If the transmission of the UART command has not finished within the packet
transmission duration (depending on the currently selected UART Baud rate +
5ms after having received the start signal), the module will discard the received
Bytes and wait for a new command. This means that the delay between 2
successive Bytes in a frame must be kept as low as possible.
Please note that the different commands are only valid in specific module s-
tates (see Figure
7
). If a command is not permitted in the current state, the
command confirmation returns "Operation not permitted" as a response.
Proteus-III reference manual version 0.11 © November 2019
www.we-online.com/wireless-connectivity 59