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.3.3 CMD_DATA_IND
This telegram indicates the reception of data sent by the previously connected device. This
indication message is the result of a data request (
CMD_DATA_REQ
) sent to the associated
device within a connection.
The
CMD_DATA_IND
returns the
FS_BTMAC
of the sending device, the RSSI value of the re-
ceived data packet and the data received via the RF-interface, which can be found in the
payload. The RSSI value is printed in two’s complement notation.
Format:
Start signal Command Length BTMAC RSSI Payload CS
0x02 0x84 2 Bytes 6 Bytes 1 Byte (Length - 7) Bytes 1 Byte
7.3.4 CMD_SETBEACON_REQ
This command is used to place user data in the scan response packet. The data is broad-
casted frequently without acknowledgement and security. No connection is needed for this
mode of operation.
It can be received by any scanning Proteus-III with Beacon-function enabled (see
RF_BeaconFlags
).
The receiving module will output a
CMD_BEACON_IND
indication message containing the trans-
mitted data. See chapter
5.5
for more information.
Choosing 0x00 as Length and leaving the Payload field empty will remove the data from the
scan response packet. The number of payload data Bytes is limited to 19.
Format:
Start signal Command Length Payload CS
0x02 0x0C 2 Bytes Length Bytes 1 Byte
Response (
CMD_SETBEACON_CNF
):
Start signal Command | 0x40 Length Status CS
0x02 0x4C 0x01 0x00 1 Byte 1 Byte
Status:
0x00: Request received, will place data now
0x01: Operation failed
0xFF: Operation not permitted
7.3.5 CMD_BEACON_IND
This telegram indicates the reception of data Bytes that have been transmitted in a beacon-
packet. This data can only be received, when the module is in
ACTION_SCANNING
mode and
the beacon-function is enabled (see
RF_BeaconFlags
).
The data received via the RF-interface can be found in the payload of the
CMD_BEACON_IND
telegram. Besides this, the
FS_BTMAC
of the sending device and the RSSI value of the data
packet are output as well. The RSSI value is output in two’s complement notation.
Format:
Proteus-III reference manual version 0.11 © November 2019
www.we-online.com/wireless-connectivity 73