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
10 Peripheral only mode
The Proteus-III implements a new feature that allows the easy integration of the Proteus-III
BLE module to an already existing host. The peripheral only mode offers a plug and play
installation without previous configuration of the Proteus-III. It is tailored for easy communi-
cation with mobile BLE devices like smart phones.
The peripheral only mode is a special operation mode, that uses the user settings and the
peripheral functions of the normal mode described in the previous chapters. It has to be
enabled during the module start-up and contains the following key features:
• Peripheral only functions: The Proteus-III only contains the functions of a peripheral
device. Thus, it is advertising until another BLE enabled device connects to it. In this
case, the UART of the Proteus-III is enabled, the LED_2 pin shows that the channel
is open and bidirectional data transmission can start. As soon as the connection is
closed, the UART is disabled again to save power. Since all central functions are no
longer valid, the module cannot initiate any connection or run scans.
• Transparent UART interface: The serial interface of the Proteus-III is no longer driven
by commands. This means, when the UART of the module is enabled (i.e. only when a
channel is open, indicated by both LEDs active), data sent to the UART is transmitted
by the Proteus-III to the connected BLE enabled device. On the other hand, all data
received by radio is send from the Proteus-III to the connected host without additional
header Bytes. The UART is only running, when a channel is open. Thus, power is
saved during the advertising period. Depending on the configured connection interval,
only one packet per interval is allowed to be transmitted. Since the commands of
the command interface are no longer valid, a Proteus-III cannot be configured when
running in peripheral only mode.
• Pairing: The default security mode is the static passkey pairing method (see
RF_SecFlagsPerOnly
), with the default key "123123". The bonding feature is enabled
by default.
10.1 Reasons to use the peripheral only mode
The Proteus-III peripheral only mode equips custom applications with a BLE interface (to be
accessible by other BLE devices) without installation effort.
To setup a connection to the Proteus-III in peripheral only mode the central device has to
insert the Proteus-III’s static passkey. As soon as the channel to a connected BLE central
device is open, the LED_2 pin switches on to signalize that data can be exchanged now.
When the connection was shut down by the BLE central device, the LED_2 pin switches off
again.
Due to the transparent UART interface, data can be exchanged without additional headers.
Furthermore, the peripheral only mode allows an energy efficient operation of the BLE inter-
face, since the UART is only enabled when it is really used.
10.2 Restrictions
In peripheral only mode, it is not possible to use the security modes "Lesc pass key" and
"Lesc numeric comparison", as these security features require to output the LESC key on
the UART.
Proteus-III reference manual version 0.11 © November 2019
www.we-online.com/wireless-connectivity 162