Würth Elektronik PROTEUS-II REFERENCE MANUAL
PROTEUS-II REFERENCE MANUAL
2608011024010
2608011124010
VERSION 1.10
DECEMBER 21, 2020
Revision history
Manual
versionFWversionHWversion
1.1 1.1.0 2.1
1.2 1.1.0 2.1
1.3 1.1.0 2.1
1.4 1.1.0 2.1
Notes Date
• Initial release
• Description of the new peripheral only
mode function in chapter
• Corrected
chapter
• Updated description of firmware update
using the OTA bootloader
• Added chapter
chapter
• Updated references to new AppNote name
structure. Updated important notes, legal
notice & license terms chapters.
CMD_SET_CNF
8
Reference design
Information for Ex protection
10
message in
and
November
2018
January
2019
March 2019
June 2019
1.5 1.1.0 2.1
1.6 1.1.0 2.1
1.7 1.1.0 2.1
• Corrected information on brownout and
maximum TX power in chapter
specifications
• Updated label in chapter
labeling information
• Corrected example of DTM RX test in
chapter
• Updated address of Division Wireless
Connectivity & Sensors location
• Removed -30dBm as valid
value
• Correction of Value amount of inductivity
for ex protection
CMD_DTM_REQ
General
Electrical
RF_TXPower
October
2019
December
2019
February
2020
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 1
Manual
versionFWversionHWversion
Notes Date
• Added Declaration of conformity for Japan.
1.8 1.1.0 2.1
1.9 1.1.0 2.1
1.10 3.5.0 2.1
• Limitation of the
maximum of 31 bytes
• Added Annex
Information
host integration
• Updated Declaration of EU conformity to
latest Version of EN 300 328 after
successfully passing corresponding delta
test in chapter
information
• Added package name in chapter
Footprint WE-FP-4
• Updated Declaration of EU conformity
Regulatory compliance information
RF_DeviceName
Additional CRC8
and
Example codes for
Regulatory compliance
.
.
to a
.
June 2020
October
2020
December
2020
? For firmware history see chapter
Firmware history
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 2
Abbreviations and abstract
Abbreviation Name Description
BTMAC
CS Checksum Byte wise XOR combination of the preceding fields.
DTM Direct test mode Mode to test Bluetooth®specific RF settings.
GAP
I/O Input/output Pinout description.
LPM Low power mode Mode for efficient power consumption.
MAC MAC address of the module.
MTU
Payload The intended message in a frame / package.
RF Radio frequency Describes wireless transmission.
RSSI
Soft device Operating system used by the nRF52 chip.
User settings
Generic Access
Profile
Maximum
transmission unit
Receive Signal
Strength Indicator
Bluetooth®conform MAC address of the module used
on the RF-interface.
The GAP provides a basic level of functionality that all
Bluetooth®devices must implement.
Maximum packet size of the Bluetooth®connection.
The RSSI indicates the strength of the RF signal. Its
value is always printed in two’s complement notation.
Settings to configure the module. Any relation to a
specific entry in the user settings is marked in a
special font and can be found in chapter8.
Universal
UART
[HEX] 0xhh Hexadecimal
Asynchronous
Receiver
Transmitter
Allows the serial communication with the module.
All numbers beginning with 0x are hexadecimal
numbers. All other numbers are decimal, unless
stated otherwise.
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 3
Contents
1. Introduction 10
1.1. Operational description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.1. Key features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1.2. Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2. Block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.3. Ordering information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2. Electrical specifications 14
2.1. Recommended operating conditions . . . . . . . . . . . . . . . . . . . . . . 14
2.2. Absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.3. Power consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.1. Static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.3.2. Dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.4. Radio characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.5. Pin characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
3. Pinout 21
4. Quick start 24
4.1. Minimal pin configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.2. Power up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.3. Quickstart example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
5. Functional description 29
5.1. State indication using the LED pins . . . . . . . . . . . . . . . . . . . . . . . 31
5.2. Sleep mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
5.3. Identification of a Proteus-II device on the radio . . . . . . . . . . . . . . . . 32
5.4. Connection based data transmission, with or without security . . . . . . . . 32
5.4.1. Further information for a secure connection setup . . . . . . . . . . 33
5.4.1.1. Just works mode . . . . . . . . . . . . . . . . . . . . . . . . . . 33
5.4.1.2. StaticPasskey mode . . . . . . . . . . . . . . . . . . . . . . . . 36
5.4.1.3. Bonding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.5. Unidirectional connectionless data transmission using Beacons . . . . . . . 43
5.6. Energy-efficient distance estimation solutions . . . . . . . . . . . . . . . . . 44
5.7. Configure the module for low power consumption . . . . . . . . . . . . . . . 45
5.8. Start the direct test mode (DTM) . . . . . . . . . . . . . . . . . . . . . . . . 45
5.9. Using the 2MBit phy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
6. Host connection 48
6.1. Serial interface: UART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
7. The command interface 49
7.1. Scan for other modules in range . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.1. CMD_SCANSTART_REQ . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.2. CMD_SCANSTOP_REQ . . . . . . . . . . . . . . . . . . . . . . . . 51
7.1.3. CMD_GETDEVICES_REQ . . . . . . . . . . . . . . . . . . . . . . . 52
7.1.3.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
7.1.4. CMD_RSSI_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 4
7.2. Setup connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.1. CMD_CONNECT_REQ . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.2. CMD_CONNECT_IND . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.3. CMD_SECURITY_IND . . . . . . . . . . . . . . . . . . . . . . . . . 55
7.2.4. CMD_CHANNELOPEN_RSP . . . . . . . . . . . . . . . . . . . . . 56
7.2.5. CMD_DISCONNECT_REQ . . . . . . . . . . . . . . . . . . . . . . 56
7.2.6. CMD_DISCONNECT_IND . . . . . . . . . . . . . . . . . . . . . . . 57
7.2.7. CMD_PHYUPDATE_REQ . . . . . . . . . . . . . . . . . . . . . . . 57
7.2.8. CMD_PHYUPDATE_IND . . . . . . . . . . . . . . . . . . . . . . . . 58
7.2.9. CMD_PASSKEY_REQ . . . . . . . . . . . . . . . . . . . . . . . . . 58
7.2.10. CMD_PASSKEY_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.2.11. CMD_GETBONDS_REQ . . . . . . . . . . . . . . . . . . . . . . . . 59
7.2.11.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
7.2.12. CMD_DELETEBONDS_REQ . . . . . . . . . . . . . . . . . . . . . 60
7.2.12.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
7.2.12.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
7.3. Transmit and receive data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
7.3.1. CMD_DATA_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
7.3.2. CMD_TXCOMPLETE_RSP . . . . . . . . . . . . . . . . . . . . . . 62
7.3.3. CMD_DATA_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.3.4. CMD_SETBEACON_REQ . . . . . . . . . . . . . . . . . . . . . . . 63
7.3.5. CMD_BEACON_IND . . . . . . . . . . . . . . . . . . . . . . . . . . 63
7.4. Configuring the module and modifying the device settings . . . . . . . . . . 65
7.4.1. CMD_SET_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
7.4.1.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7.4.1.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
7.4.2. CMD_GET_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.4.2.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
7.5. Manage the device state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.5.1. CMD_GETSTATE_REQ . . . . . . . . . . . . . . . . . . . . . . . . 68
7.5.1.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
7.5.2. CMD_RESET_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.5.3. CMD_SLEEP_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
7.5.4. CMD_SLEEP_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
7.5.5. CMD_FACTORYRESET_REQ . . . . . . . . . . . . . . . . . . . . . 70
7.5.6. CMD_UARTDISABLE_REQ . . . . . . . . . . . . . . . . . . . . . . 71
7.5.7. CMD_UARTENABLE_IND . . . . . . . . . . . . . . . . . . . . . . . 72
7.5.8. CMD_BOOTLOADER_REQ . . . . . . . . . . . . . . . . . . . . . . 72
7.6. Run the Bluetooth®test modes . . . . . . . . . . . . . . . . . . . . . . . . . 74
7.6.1. CMD_DTMSTART_REQ . . . . . . . . . . . . . . . . . . . . . . . . 74
7.6.2. CMD_DTM_REQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
7.6.2.1. Example: Transmission, 16 times 0x0F, channel 0 . . . . . . . 76
7.6.2.2. Example: Receiver, channel 0 . . . . . . . . . . . . . . . . . . . 76
7.6.2.3. Example: Transmission, carrier test, channel 0 . . . . . . . . . 77
7.6.2.4. Example: Set TX power to -4 dBm . . . . . . . . . . . . . . . . 77
7.7. Other messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.7.1. CMD_ERROR_IND . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
7.8. Message overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 5
8. UserSettings - Module configuration values 83
8.1. FS_DeviceInfo: Read the chip type and OS version . . . . . . . . . . . . . . 83
8.1.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
8.2. FS_FWVersion: Read the firmware version . . . . . . . . . . . . . . . . . . 85
8.2.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
8.3. FS_MAC: Read the MAC address . . . . . . . . . . . . . . . . . . . . . . . . 86
8.3.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8.4. FS_BTMAC: Read the Bluetooth conform MAC address . . . . . . . . . . . 87
8.4.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
8.5. FS_SerialNumber: Read the serial number of the module . . . . . . . . . . 88
8.5.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
8.6. RF_DeviceName: Modify the device name . . . . . . . . . . . . . . . . . . . 89
8.6.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.6.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
8.7. RF_StaticPasskey: Modify the static passkey . . . . . . . . . . . . . . . . . 91
8.7.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.7.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
8.8. RF_SecFlags: Modify the security settings . . . . . . . . . . . . . . . . . . . 92
8.8.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.8.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.9. RF_SecFlagsPerOnly: Modify the security settings (Peripheral only mode) . 95
8.9.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.9.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.10. RF_ScanFlags: Modify the scan behavior . . . . . . . . . . . . . . . . . . . 96
8.10.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.10.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.11. RF_BeaconFlags: Interprete the advertising data . . . . . . . . . . . . . . . 98
8.11.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.11.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.12. RF_AdvertisingTimeout: Modify the advertising timeout . . . . . . . . . . . 100
8.12.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.12.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.13. RF_ScanFactor: Modify the scan factor . . . . . . . . . . . . . . . . . . . . 101
8.13.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.13.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.14. RF_ScanTiming: Modify the scan timing . . . . . . . . . . . . . . . . . . . . 102
8.14.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.14.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
8.15. RF_ConnectionTiming: Modify the connection timing . . . . . . . . . . . . . 104
8.15.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.15.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
8.16. RF_TXPower: Modify the output power . . . . . . . . . . . . . . . . . . . . . 107
8.16.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.16.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
8.17. RF_SPPBaseUUID: Configure the SPP base UUID . . . . . . . . . . . . . . 108
8.17.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.17.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
8.18. RF_Appearance: Configure the appearance of the device . . . . . . . . . . 110
8.18.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 6
8.18.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
8.19. UART_BaudrateIndex: Modify the UART speed . . . . . . . . . . . . . . . . 111
8.19.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
8.19.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
8.20. UART_Flags: Configure the UART . . . . . . . . . . . . . . . . . . . . . . . 113
8.20.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.20.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
8.21. CFG_Flags: Configure the module . . . . . . . . . . . . . . . . . . . . . . . 115
8.21.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
8.21.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
8.22. DIS_ManufacturerName: Configure the manufacturer name . . . . . . . . . 117
8.22.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
8.22.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
8.23. DIS_ModelNumber: Configure the model number . . . . . . . . . . . . . . . 119
8.23.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
8.23.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
8.24. DIS_SerialNumber: Configure the serial number . . . . . . . . . . . . . . . 120
8.24.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
8.24.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
8.25. DIS_HWVersion: Configure the HW version . . . . . . . . . . . . . . . . . . 121
8.25.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
8.25.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
8.26. DIS_SWVersion: Configure the SW version . . . . . . . . . . . . . . . . . . 122
8.26.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
8.26.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
8.27. DIS_Flags: Configure the device information service . . . . . . . . . . . . . 123
8.27.1. Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
8.27.2. Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
9. Timing parameters 127
9.1. Reset and sleep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.2. Bluetooth LE timing parameters . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.3. Connection establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
9.4. Connection based data transmission . . . . . . . . . . . . . . . . . . . . . . 128
10.Peripheral only mode 129
10.1. Reasons to use the peripheral only mode . . . . . . . . . . . . . . . . . . . 129
10.2. How to use the peripheral only mode . . . . . . . . . . . . . . . . . . . . . . 129
10.3. More information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
10.3.1. Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
10.3.2. UART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
11.Customizing the Proteus-II 131
11.1. DIS - Device information service . . . . . . . . . . . . . . . . . . . . . . . . 131
11.2. UUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
11.3. Appearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
12.Custom firmware 132
12.1. Custom configuration of standard firmware . . . . . . . . . . . . . . . . . . 132
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 7
12.2. Customer specific firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
12.3. Customer firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
12.4. Contact for firmware requests . . . . . . . . . . . . . . . . . . . . . . . . . . 133
13.Firmware update 134
13.1. Firmware flashing using the SWD interface . . . . . . . . . . . . . . . . . . 134
13.2. Firmware update using the Proteus-II OTA bootloader . . . . . . . . . . . . 134
13.2.1. Firmware update steps using the Nordic nRF Toolbox app . . . . . 136
14.Firmware history 138
15.Design in guide 139
15.1. Advice for schematic and layout . . . . . . . . . . . . . . . . . . . . . . . . . 139
15.2. Dimensioning of the micro strip antenna line . . . . . . . . . . . . . . . . . . 141
15.3. Antenna solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
15.3.1. Wire antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
15.3.2. Chip antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
15.3.3. PCB antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
15.3.4. Antennas provided by Würth Elektronik eiSos . . . . . . . . . . . . 144
15.3.4.1. 2600130021 - Himalia - 2.4 GHz dipole antenna . . . . . . . . 144
16.Reference design 145
16.1. Schematic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
16.2. Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
17.Manufacturing information 148
17.1. Moisture sensitivity level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
17.2. Soldering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
17.2.1. Reflow soldering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
17.2.2. Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
17.2.3. Other notations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
17.3. ESD handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
17.4. Safety recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
18.Physical dimensions 152
18.1. Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
18.2. Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
18.3. Module drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
18.4. Footprint WE-FP-4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
18.5. Antenna free area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
19.Marking 155
19.1. Lot number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
19.2. General labeling information . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
20.Information for Ex protection 157
21.Bluetooth SIG listing/qualification 158
21.1. Qualification steps when referencing the Proteus-II . . . . . . . . . . . . . . 158
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 8
22.Regulatory compliance information 160
22.1. Important notice EU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
22.2. Important notice FCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
22.3. Conformity assessment of the final product . . . . . . . . . . . . . . . . . . 160
22.4. Exemption clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
22.5. EU Declaration of conformity . . . . . . . . . . . . . . . . . . . . . . . . . . 161
22.6. FCC Compliance Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
22.7. IC Compliance Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
22.8. ARIB Declaration of conformity . . . . . . . . . . . . . . . . . . . . . . . . . 163
22.8.1. Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
22.8.2. Certified antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
22.9. FCC and IC requirements to OEM integrators . . . . . . . . . . . . . . . . . 164
22.9.1. Pre-certified antennas . . . . . . . . . . . . . . . . . . . . . . . . . 165
23.Important notes 166
23.1. General customer responsibility . . . . . . . . . . . . . . . . . . . . . . . . . 166
23.2. Customer responsibility related to specific, in particular safety-relevant ap-
plications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
23.3. Best care and attention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
23.4. Customer support for product specifications . . . . . . . . . . . . . . . . . . 166
23.5. Product improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
23.6. Product life cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
23.7. Property rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
23.8. General terms and conditions . . . . . . . . . . . . . . . . . . . . . . . . . . 167
24.Legal notice 168
24.1. Exclusion of liability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
24.2. Suitability in customer applications . . . . . . . . . . . . . . . . . . . . . . . 168
24.3. Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
24.4. Usage restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
25.License terms 170
25.1. Limited license . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
25.2. Usage and obligations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
25.3. Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
25.4. Firmware update(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
25.5. Disclaimer of warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
25.6. Limitation of liability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
25.7. Applicable law and jurisdiction . . . . . . . . . . . . . . . . . . . . . . . . . . 172
25.8. Severability clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
25.9. Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
A. Additional CRC8 Information 175
A.1. Example CRC8 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . 175
A.2. CRC8 Test Vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
B. Example codes for host integration 176
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 9
1. Introduction
1.1. Operational description
The Proteus-II exists in two variants, one variant with integrated PCB-antenna, and the other
variant with 50Ω connection to an external antenna. For the general functionality there is no
difference between the variants.
The Proteus-II module is a radio sub module/device for wireless communication between devices such as control systems, remote controls, sensors etc. . On the basis of Bluetooth®LE 5
it offers a fast and secure data transmission of data packages between two or more parties
(point to point topology). A serial interface (UART) is available for communication with the
host system.
The Proteus-II uses the Bluetooth®LE standard to provide general data transmission between several devices. The standard itself offers a wide range of configurations and possibilities to suit and optimize sophisticated customer applications. To fulfill the needs and
specifications of such applications a tailored firmware can be developed on the basis of the
Proteus-II hardware. This includes the connection and communication to custom sensors,
custom Bluetooth®LE profiles, timing configurations, security configuration as well as power
consumption optimizations.
1.1.1. Key features
The Proteus-II offers the following key features that are described in the manual in more
detail:
SPP-like connection-based secured data transmission: The Proteus-II firmware imple-
ments an SPP-like Bluetooth®LE profile that allows the bidirectional data transmission
between several Proteus-II and/or to other Bluetooth®LE devices implementing the
AMBER SPP profile. Any module in the network can initiate connection setup. Secured
connections allow the transmission of encrypted data (user-defined key or pairing).
Fast sensor data transmission via Beacons: The Proteus-II supports the transmission and
reception of Beacons. Beacons are fast broadcast messages that allow the energyefficient unidirectional transmission of data. Especially in sensor networks, this feature
is suitable for the frequent transmission of measurement data as it removes the need
for connection-based communication and therefore is more energy efficient.
Advanced customization capabilities: The configurable Device Information Service (DIS),
the UUID and the appearance of the Bluetooth®LE profile, enable to personalize the
Proteus-II to fuse with the user’s end product.
Low power position sensing solutions: The current TX power of any Proteus-II is always
transmitted with each advertising packet when the module is in command mode. With
this, distance estimation and position sensing solutions can be realized conveniently
by performing a passive scan.
Fast serial interface: The Proteus-II offers a UART-interface to communicate with a host
using a user-defined baud rate and a simple command interface.
Latest microprocessor generation provided by Nordic Semiconductor nRF52 series:
The heart of the Proteus-II is a Bluetooth®LE chip of the nRF52 series offering high
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 10
performance values combined with low power consumption. It is a 32 Bit ARM CortexM4F CPU with 512kB flash + 64kB RAM and up to 4dBm output power.
Bluetooth®5 stack: The Bluetooth®5 stack enables fast and energy efficient data trans-
mission using state-of-the-art technology of Nordic Semiconductors.
High throughput mode: The Proteus-II contains the so called "High throughput mode" that
allows to send up to 4 data packets per connection interval. This increases significantly the throughput. This mode and its usage is described in Proteus-II - Application Note 4".
All Bluetooth®LE roles supported: The integrated Bluetooth®LE stack supports all Bluetooth®LE
roles. Depending on the current state of operation the Proteus-II firmware automatically switches its role to execute the user’s instructions.
Flexible wired interfacing: If custom hardware does not support UART communication or
in case of a host less implementation, the Proteus-II is equipped with extra pins suited
for custom device/sensor connection. With help of these, a tailored firmware can be
developed which is optimized to the customer’s needs. The pins can be configured to
various functions such as UART, SPI, I2C, ADC, PWM, NFC and GPIO.
OTA firmware update: The Proteus-II firmware provides over the air firmware update ca-
pabilities. Firmware updates can be applied using the Nordic Apps for cell phones.
Peripheral only mode: The Proteus-II firmware provides the "peripheral only" operation
mode (see chapter10), that allows the easy adaption of already existing custom hardware with the Bluetooth®LE interface. By default, this mode offers the static passkey
pairing method with bonding and a transparent UART interface. With this, custom hardware can be accessed by mobile Bluetooth®LE devices (like smart phones including
a custom App) using an authenticated and encrypted Bluetooth®LE link without the
need of configuring the module.
1.1.2. Connectivity
The Bluetooth®LE standard allows to setup a network with various Bluetooth®LE devices
from different manufacturers. To be able to communicate with Proteus-II devices, the AMBER SPP-like profile must be known and implemented by all network participants. Thus
arbitrary Bluetooth®LE devices (like iOS or Android devices) must implement this profile,
too. To do so, the Proteus-II application note 1 contains the design data of the AMBER
SPP-like profile.
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 11
1.2. Block diagram
Figure 1: Block diagram of the module with internal PCB antenna and antenna pad
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 12
1.3. Ordering information
WE order code Former order code Description
2608011024010 AMB2623-TR
2608011124010 AMB2623-1-TR Bluetooth®Smart Module with RF pad, Tape & Reel
2608011024019 AMB2623-DEV Development Kit including 3×AMB2623
2608011124019 AMB2623-1-DEV Development Kit including 3×AMB2623-1
Table 1: Ordering information
Bluetooth®Smart Module with integrated antenna,
Tape & Reel
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 13
2. Electrical specifications
As not otherwise stated measured on the evaluation board Proteus-II-EV with T=25°C,
VDDS=3V, f=2.44GHz, internal DC-DC converter in use.
2.1. Recommended operating conditions
Description Min. Typ. Max. Unit
Ambient temperature -40 25 85 °C
Supply voltage (VDDS) 1.8 3 3.6 V
Supply rise time (0V to ≥ 1.7V) 60 ms
Table 2: Recommended operating conditions
The on-chip power-on reset circuitry may not function properly for rise times
longer than the specified maximum.
A step in supply voltage of 300 mV or more, with rise time of 300 ms or less,
within the valid supply range, may result in a system reset.
An instable supply voltage may significantly decrease the radio performance
and stability.
2.2. Absolute maximum ratings
Description Min. Typ. Max. Unit
Supply voltage (VDD) -0.3 +3.9 V
Voltage on any digital pin, VDD≤3.6V -0.3 VDD+0.3 V
Voltage on any digital pin, VDD≥3.6V -0.3 3.9 V
Input RF level 10 dBm
Flash endurance 10 000 Write/erase cycles
Table 3: Absolute maximum ratings
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 14
2.3. Power consumption
2.3.1. Static
Continuous test mode
TX current consumption at +4 dBm
TX current consumption at 0 dBm
RX current consumption
Sleep (system off mode)
TX current consumption at +4 dBm
TX current consumption at 0 dBm
RX current consumption
Min. Typ. Max. Unit
1
7.5
5.3
5.4
1
1
mA
mA
mA
0.4 µA
2
11
8
8
2
2
mA
mA
mA
Table 4: Power consumption for 100% transmission/reception
Due to the Bluetooth®LE time slot operation, the real operating currents are
reduced significantly and depend on the user selectable advertising and connection interval settings.
1
Transmitter only with DC/DC converter from nRF52 data sheet.
2
Full module power consumption.
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 15
Figure 2: TX Current consumption vs. VCC
2.3.2. Dynamic
Besides the static TX, RX, idle and sleep current the average current is of interest. Here an
example for a typical behavior of a peripheral device in advertising mode (see Figure3and
Figure4). Currents and state durations are dependent on the configuration of the module.
In this state the module transmits the advertising packets on the 3 advertising channels.
Nordic Semiconductor provides an online tool calculating the average current of a Bluetooth
connection. It can be accessed at https://devzone.nordicsemi.com/power/ .
®
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 16
Figure 3: Current consumption calculation in advertising mode with 40ms advertising inter-
val, UART disabled
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 17
Figure 4: Measured Proteus-II transient current consumption in advertising mode with 40ms
advertising interval, excerpt of 5ms
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 18
2.4. Radio characteristics
50Ω conducted measurements from nRF52 data sheet
Description Min. Typ. Max. Unit
Output power -40 +3 +4 dBm
Input sensitivity (≤ 37 Bytes, BER=1E-3) -92
RSSI accuracy valid range (±2dB) -90 -20 dBm
Enable TX or RX delay 140 µs
Enable TX or RX delay (fast mode) 40 µs
Disable TX delay 6 µs
Disable RX delay 0 µs
Table 5: Radio parameters
1
dBm
Output power
RF_TXPower
= 4 Min. Typ. Max. Unit
Proteus-II external antenna (50Ω conducted) 3 4 dBm
Proteus-II integrated pcb antenna (e.i.r.p.) -2 0 dBm
Table 6: Output power
1
nRF52832 Rev.1, with build code CIAA-B00, CSP package, in DC/DC Mode
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 19
2.5. Pin characteristics
Measurements from nRF52 data sheet
Description
Input high voltage
Input low voltage
Current at VSS+0.4 V, output set low, standard
drive, VDD ≥1.7V
Current at VSS+0.4 V, output set low, high drive,
VDD ≥ 2.7 V
Current at VSS+0.4 V, output set low, high drive,
VDD ≥ 1.7 V
Current at VDD-0.4 V, output set high, standard
drive, VCC ≥1.7V
Current at VDD-0.4 V, output set high, high
drive, VDD ≥ 2.7 V
Current at VDD-0.4 V, output set high, high
drive, VDD ≥ 1.7 V
Internal pull-up resistance
Internal pull-down resistance
Min. Typ. Max. Unit
0.7 ×VCC VCC V
VSS 0.3 ×VCC V
1 2 4 mA
6 10 15 mA
3 mA
1 2 4 mA
6 9 14 mA
3 mA
13 kΩ
13 kΩ
Table 7: Pin characteristics
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 20
3. Pinout
GND
WAKE_UP
/CTS
/RTS
LED_2
LED_1
URXD
UTXD
OP_MODE
VDD
BOOT
/RESET
SWDIO
SWDCLK
ANT
17
12
11
8
7
1
GND
RESERVED
Figure 5: Pinout (top view)
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 21
No µC Pin Designation I/O Description
Antenna connection in case of module variant
1 ANT RF
with external antenna. In case of module with
integrated antenna, do not connect.
2 GND Supply Ground
3 SWDCLK Input
4 SWDIO Input
5 P0.21 /RESET Input
Serial wire clock. Uses internal pull down resistor. Do not connect if not needed.
Serial wire input/output. Uses internal pull up resistor. Do not connect if not needed.
Reset pin. A low signal resets the module. Uses
internal pull up resistor.
Boot pin. A low signal during and short after re-
6 P0.05/AIN3 BOOT Input
set starts the module in OTA bootloader mode.
Uses internal pull up resistor1. Do not connect if
not needed.
7 VDD Supply Supply voltage
Operation mode pin with internal pull down resis-
8 P0.10/NFC22OP_MODE Input
tor1during start-up. Low level or open: Normal
Mode. High level: Peripheral only Mode. Do not
connect if not needed.
9 P0.09/NFC12RESERVED I/O Do not connect.
10 P0.00/XL1
3
LED_1 Output
Indicates the module state (active high). Do not
connect if not needed.
11 P0.01/XL2
3
LED_2 Output
Indicates the module state (active high). Do not
connect if not needed.
12 P0.02/AIN0 UTXD Output UART(Transmission)
13 P0.03/AIN1 URXD Input
14 P0.04/AIN2 /RTS Output
15 P0.28/AIN4 /CTS Input
UART (Reception). Uses internal pull up resistor1.
Only used if flow control is enabled. Do not connect if not needed.
Only used if flow control is enabled. Do not connect if not needed.
Wake-up will allow leaving the system-off mode
16 P0.29/AIN5 WAKE_UP Input
or re-enabling the UART. Uses internal pull up
resistor1. Do not connect if not needed.
17 GND Supply Ground
Table 8: Pinout
1
Internal pull ups or pull downs are configured at startup by the firmware installed in the SoC. The pull up on
the /RESET pin cannot be disabled by firmware.
2
NFC pins available for NFC function in custom firmware. The standard firmware of Proteus-II does not
implement this function.
3
Pins available to connect an external crystal in custom firmware. The standard firmware of Proteus-II does
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 22
not implement this function.
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 23
4. Quick start
4.1. Minimal pin configuration
In factory state the modules are immediately ready for operation; the following pins are required in the minimal configuration:
VDD, GND, UTXD, URXD, /RESET
If the flow control is enabled additionally the pins /RTS and /CTS shall be connected.
We recommend to additionally have the pins SWDIO and SWDCLK accessible in order to
support a fail-safe firmware update. A standard socket on the customer’s PCB for connecting a flash adapter can be useful for debugging purposes (e.g. a JTAG 2*10 pin header with
2.54mm pin-to-pin distance).
Implementing the fail-safe firmware update method using the SWD interface is
recommended. Without having the SWD interface available a fail-safe firmware
update on a customer PCB cannot be guaranteed.
If the module has to be connected to a PC, a converter (TTL to RS-232 or TTL to USB) has
to be used. See chapter3for details on all pins. Please refer to the Proteus-II-EV schemes
for a reference design.
The logic level of the module is based on 3V. A 5V logic level must not be
connected directly to the module.
4.2. Power up
After powering the module the /RESET pin shall be hold for another ∆t of 1ms after the VDD
is stable to ensure a safe start-up. The module will send a
"ready for operation" after the /RESET pin was released.
Applying a reset (e.g. a host temporarily pulling the /RESET pin down for at
least 1ms and releasing it again) after the VCC is stable will also be sufficient.
CMD_GETSTATE_CNF
to indicate
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 24
Figure 6: Power up
4.3. Quickstart example
This section describes how to quick start the data transmission between two Proteus-II modules. The goal is to setup a connection between module A and module B, transmit some
data and close the connection again.
In this section, all packet data from or to the modules is given in hexadecimal notation. For
quick testing, a pair of Proteus-II-EV is recommended.
Connect the two devices (modules, EV-boards or USB dongles) to a PC. A terminal program, for example hterm, is used to perform the communication via COM ports. The two
corresponding COM ports have to be selected and opened with a default configuration of
115200 Baud, 8 data Bits, 1 stop Bit and parity set to none (8n1).
To reproduce the following sequence, note that, the
is different, thus it has to be replaced it in the commands below. In addition, the
checksum has to be adjusted, when adapting any command. The command
structure and checksum calculation is described in chapter8.
Note that the module goes to
after
RF_AdvertisingTimeout
CMD_SLEEP_CNF
default value is 0s, which means that it will run forever.
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 25
. In addition, the UART is disabled in
ACTION_SLEEP
seconds. The module will indicate this using a
mode if no connection is setup
FS_BTMAC
ACTION_SLEEP
of every module
mode. The
Connection setup and first data transmission
1. Power-up the modules and make their UARTs accessible by the host(s) (115200 Baud,
8n1). After the power-up or after reset the following sequence is sent from the module.
Info Module A Module B
⇐ Response
started in
⇐ Response
started in
2. Request the
Info Module A Module B
⇒ Request
⇐ Response
module A is 0x55 0x00 0x00 0xDA 0x18 0x00
⇒ Request
⇐ Response
module B is 0x11 0x00 0x00 0xDA 0x18 0x00
3. Connect module A to module B via Bluetooth®.
CMD_GETSTATE_CNF
ACTION_IDLE
CMD_GETSTATE_CNF
ACTION_IDLE
FS_BTMAC
CMD_GET_REQ
CMD_GET_CNF:FS_BTMAC
CMD_GET_REQ
CMD_GET_CNF:FS_BTMAC
mode.
mode.
of both modules.
with settings index 4 02 10 01 00 04 17
with settings index 4 02 10 01 00 04 17
: Module A
: Module B
of
of
02 41 02 00 01 01 41
02 41 02 00 01 01 41
02 50 07 00 00 55 00
00 DA 18 00 C2
02 50 07 00 00 11 00
00 DA 18 00 86
This example is taken from an older firmware. Using newer firmwares with the
optional Bluetooth®4.2 feature "LE Packet Length Extension", the maximum
supported payload per packet may be higher than 0x13.
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 26
Info Module A Module B
⇒ Request
module B
⇐ Response
understood, try to connect now
⇐ Indication
connection established successfully to module
with
FS_BTMAC
⇐ Indication
connection established successfully to module
with
FS_BTMAC
⇐ Indication
opened successfully to module with
0x11 0x00 0x00 0xDA 0x18 0x00 and maximum
payload size of 0x13 (19 Bytes) per packet
⇐ Indication
opened successfully to module with
0x55 0x00 0x00 0xDA 0x18 0x00 and maximum
payload size of 0x13 (19 Bytes) per packet
CMD_CONNECT_REQ
CMD_CONNECT_CNF
CMD_CONNECT_IND
0x11 0x00 0x00 0xDA 0x18 0x00
CMD_CONNECT_IND
0x55 0x00 0x00 0xDA 0x18 0x00
CMD_CHANNELOPEN_RSP
CMD_CHANNELOPEN_RSP
with
FS_BTMAC
: Request
: Physical
: Physical
: Channel
FS_BTMAC
: Channel
FS_BTMAC
of
02 06 06 00 11 00 00
DA 18 00 D1
02 46 01 00 00 45
02 86 07 00 00 11 00
00 DA 18 00 50
02 86 07 00 00 55 00
00 DA 18 00 14
02 C6 08 00 00 11 00
00 DA 18 00 13 C3
02 C6 08 00 00 55 00
00 DA 18 00 13 87
4. Once the connection is active, data can be sent in each direction. Let us send a string
"ABCD" from module B to module A.
The RSSI values will be different in your tests.
Info Module A Module B
⇒ Request
module A
⇐ Response
send data now
⇐ Indication
"ABCD" from
0x18 0x00 with RSSI of 0xCA (-54dBm)
⇐ Response
transmitted successfully
CMD_DATA_REQ
CMD_DATA_CNF
CMD_DATA_IND
FS_BTMAC
CMD_TXCOMPLETE_RSP
: Send "ABCD" to
: Request received,
: Received string
0x11 0x00 0x00 0xDA
: Data
02 04 04 00 41 42 43
44 06
02 44 01 00 00 47
02 84 0B 00 11 00
00 DA 18 00 CA 41
42 43 44 90
02 C4 01 00 00 C7
5. Reply with "EFGH" to module B.
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 27
Info Module A Module B
⇒ Request
module B
⇐ Response
send data now
⇐ Indication
"EFGH" from
0x18 0x00 with RSSI of 0xC1 (-63dBm)
⇐ Response
transmitted successfully
6. Now module A closes the connection, so both modules will get a disconnect indication.
Info Module A Module B
⇒ Request
⇐ Response
received, disconnect now
⇐ Indication
closed
CMD_DATA_REQ
CMD_DATA_CNF
CMD_DATA_IND
FS_BTMAC
CMD_TXCOMPLETE_RSP
CMD_DISCONNECT_REQ
CMD_DISCONNECT_CNF
CMD_DISCONNECT_IND
: Send "EFGH" to
: Request received,
: Received string
0x55 0x00 0x00 0xDA
02 04 04 00 45 46 47
48 0E
02 44 01 00 00 47
: Data
: Disconnect 02 07 00 00 05
: Request
: Connection
02 C4 01 00 00 C7
02 47 01 00 00 44
02 87 01 00 16 92
02 84 0B 00 55 00
00 DA 18 00 C1 45
46 47 48 D7
⇐ Indication
closed
CMD_DISCONNECT_IND
: Connection
02 87 01 00 13 97
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 28
5. Functional description
The Proteus-II module acts as a slave and can be fully controlled by an external host that
implements the command interface. 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 Proteus-II can operate in different states. Depending on the active state several commands of the command interface (see chapter7) are permitted to modify the state, configure
the module or transmit data over the radio interface. An overview of the different states and
the corresponding allowed commands can be found in Figure7.
When the Proteus-II is powered up, it starts in
advertises (Bluetooth®LE role "peripheral"), such that other devices in range (Bluetooth®LE
role "central" or "observer") can detect it and connect to it. If no connection was setup after
RF_AdvertisingTimeout
advertising.
The
ACTION_IDLE
stops advertising and scans for other advertising modules in range (Bluetooth®LE role "central").
When leaving the
in
ACTION_IDLE
The
ACTION_CONNECTED
other module (Bluetooth®LE role "peripheral") or by setting up a connection itself (Bluetooth®LE
role "central"). In this case it stops advertising and data can be transmitted and received
to/from the connected module. This state remains active as long as the module does not
disconnect itself (e.g. due to a timeout), no disconnection request from the connected device
is received.
When disconnecting, the module goes to
state also allows to switch to
ACTION_SCANNING
state and starts advertising again.
seconds, the module goes to
state with the corresponding command, the module is
state can be entered either by getting a connection request from an-
ACTION_IDLE
ACTION_IDLE
ACTION_SCANNING
state and starts advertising again.
state. In this state the module
ACTION_SLEEP
state which will stop
state, where the module
Proteus-II reference manual version 1.10 © December 2020
www.we-online.com/wireless-connectivity 29
Loading...