| submitted | available | document details (if available) | source link |
|---|---|---|---|
| February 11 2018 |
| various | Users Integration Manual | Users Manual | 4.65 MiB | / February 11 2018 |
AMB2623 REFERENCE MANUAL VERSION 1.0 JULY 18, 2018 Revision history Manual version FW version HW version Notes 1.0 0.2.7 2.1 Initial release
For rmware history see chapter Firmware history Date July 2018 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 1 Abbreviations and abstract Abbreviation Name BTMAC CS BLE BT DTM GAP I/O LPM MAC MTU Payload RF RSSI Soft device User settings UART Checksum Bluetooth Low Energy Bluetooth Direct test mode Generic Access Prole Input/output Low power mode Maximum transmission unit Radio frequency Receive Signal Strength Indicator Universal Asynchronous Receiver Transmitter Description Bluetooth conform MAC address of the module used on the RF-interface. Byte wise XOR combination of the preceding elds. According to Bluetooth 4.2 specication. According to Bluetooth specication. Mode to test Bluetooth specic RF settings. The GAP provides a basic level of functionality that all Bluetooth devices must implement. Pinout description. Mode for efcient power consumption. MAC address of the module. Maximum packet size of the Bluetooth connection. The intended message in a frame / package. Describes wireless transmission. The RSSI indicates the strength of the RF signal. Its value is always printed in twos complement notation. Operating system used by the nRF52 chip. Settings to congure the module. Any relation to a specic entry in the user settings is marked in a special font and can be found in chapter 8. Allows the serial communication with the module.
[HEX] 0xhh Hexadecimal All numbers beginning with 0x are hexadecimal numbers. All other numbers are decimal, unless stated otherwise. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 2 Contents 1 Introduction 1.1 Operational description . 1.1.1 Key features . 1.1.2 Connectivity . 1.2 Block diagram . 1.3 Ordering information . 2 Electrical specications 2.1 Recommended operating conditions . 2.2 Absolute maximum ratings
. 2.3 Power consumption . 2.3.1 Static . 2.3.2 Dynamic . 2.4 Radio characteristics . 2.5 Pin characteristics . 3 Pinout 4 Quick start 4.1 Minimal pin conguration . 4.2 Power up . 4.3 Quickstart example . 5 Functional description 5.1 State indication using the LED pins . 5.2 Sleep mode . 5.3 Identication of an AMB2623 device on the radio . 5.4 Connection based data transmission, with or without security . 5.4.1 Further information for a secure connection setup . Just works mode . StaticPasskey mode . Bonding . 5.5 Unidirectional connectionless data transmission using Beacons . 5.6 Energy-efcient distance estimation solutions . 5.7 Congure the module for low power consumption . 5.8 Start the direct test mode (DTM)
. 5.9 Using the 2MBit phy . 5.4.1.1 5.4.1.2 5.4.1.3 6 Host connection 6.1 Serial interface: UART . 7 The command interface 7.1 Scan for other modules in range . 7.1.1 CMD_SCANSTART_REQ . 7.1.2 CMD_SCANSTOP_REQ . 7.1.3 CMD_GETDEVICES_REQ . Example 1 . 7.1.4 CMD_RSSI_IND . 7.1.3.1 9 9 9 10 11 11 12 12 12 13 13 13 16 17 18 20 20 20 21 25 27 27 28 28 29 29 32 35 40 41 42 42 44 45 45 46 47 47 47 48 49 49 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 3 7.2.11.1 7.2.12.1 7.2.12.2 7.2 Setup connections . 7.2.1 CMD_CONNECT_REQ . 7.2.2 CMD_CONNECT_IND . 7.2.3 CMD_SECURITY_IND . 7.2.4 CMD_CHANNELOPEN_RSP . 7.2.5 CMD_DISCONNECT_REQ . 7.2.6 CMD_DISCONNECT_IND . 7.2.7 CMD_PHYUPDATE_REQ . 7.2.8 CMD_PHYUPDATE_IND . 7.2.9 CMD_PASSKEY_REQ . 7.2.10 CMD_PASSKEY_IND . 7.2.11 CMD_GETBONDS_REQ . Example 1 . 7.2.12 CMD_DELETEBONDS_REQ . Example 1 . Example 2 . 7.3 Transmit and receive data . 7.3.1 CMD_DATA_REQ . 7.3.2 CMD_TXCOMPLETE_RSP . 7.3.3 CMD_DATA_IND . 7.3.4 CMD_SETBEACON_REQ . 7.3.5 CMD_BEACON_IND . 7.4 Conguring the module and modifying the device settings . 7.4.1 CMD_SET_REQ . Example 1 . Example 2 . 7.4.2 CMD_GET_REQ . Example 1 . 7.5 Manage the device state . 7.5.1 CMD_GETSTATE_REQ . Example 1 . 7.5.2 CMD_RESET_REQ . 7.5.3 CMD_SLEEP_REQ . 7.5.4 CMD_SLEEP_IND . 7.5.5 CMD_FACTORYRESET_REQ . 7.5.6 CMD_UARTDISABLE_REQ . 7.5.7 CMD_UARTENABLE_IND . 7.5.8 CMD_BOOTLOADER_REQ . 7.6 Run the Bluetooth test modes . 7.6.1 CMD_DTMSTART_REQ . 7.6.2 CMD_DTM_REQ . Example: Transmission, 16 times 0x0F, channel 0 . Example: Receiver, 0x0F, channel 0 . Example: Transmission, carrier test, channel 0 . Example: Set TX power to -4 dBm . 7.7 Other messages . 7.7.1 CMD_ERROR_IND . 7.8 Message overview . 7.6.2.1 7.6.2.2 7.6.2.3 7.6.2.4 7.4.1.1 7.4.1.2 7.4.2.1 7.5.1.1 51 51 51 51 52 52 53 53 54 54 55 55 55 56 56 57 58 58 58 59 59 59 61 61 62 62 63 63 64 64 64 65 65 66 66 67 68 68 70 70 70 72 72 73 73 75 75 76 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 4 8 UserSettings - Module conguration values 8.10 RF_ScanFlags: Modify the scan behavior 8.1 FS_DeviceInfo: Read the chip type and OS version . 8.1.1 Example 1 . 8.2 FS_FWVersion: Read the rmware version . 8.2.1 Example 1 . 8.3 FS_MAC: Read the MAC address . 8.3.1 Example 1 . 8.4 FS_BTMAC: Read the BLE conform MAC address . 8.4.1 Example 1 . 8.5 FS_SerialNumber: Read the serial number of the module . 8.5.1 Example 1 . 8.6 RF_DeviceName: Modify the device name . 8.6.1 Example 1 . 8.6.2 Example 2 . 8.7 RF_StaticPasskey: Modify the static passkey . 8.7.1 Example 1 . 8.7.2 Example 2 . 8.8 RF_SecFlags: Modify the security settings . 8.8.1 Example 1 . 8.8.2 Example 2 . 8.9 RF_SecFlagsPerOnly: Modify the security settings (Peripheral only mode) . 8.9.1 Example 1 . 8.9.2 Example 2 . 8.10.1 Example 1 . 8.10.2 Example 2 . 8.11 RF_BeaconFlags: Interprete the advertising data . 8.11.1 Example 1 . 8.11.2 Example 2 . 8.12.1 Example 1 . 8.12.2 Example 2 . 8.13.1 Example 1 . 8.13.2 Example 2 . 8.14 RF_ScanTiming: Modify the scan timing . 8.14.1 Example 1 . 8.14.2 Example 2 . 79 79 80 81 81 82 82 83 83 84 84 85 85 85 87 87 87 88 89 89 91 91 91 92 92 92 94 95 95 96 96 96 97 97 97 98 99 99 8.15 RF_ConnectionTiming: Modify the connection timing . 100 8.15.1 Example 1 . 101 8.15.2 Example 2 . 101
. 102 8.16.1 Example 1 . 102 8.16.2 Example 2 . 102 8.17 RF_SPPBaseUUID: Congure the SPP base UUID . 103 8.17.1 Example 1 . 103 8.17.2 Example 2 . 103 8.18 RF_Appearance: Congure the appearance of the device . 105 8.18.1 Example 1 . 105 8.12 RF_AdvertisingTimeout: Modify the advertising timeout 8.13 RF_ScanFactor: Modify the scan factor 8.16 RF_TXPower: Modify the output power AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 5 8.18.2 Example 2 . 105 8.19 UART_BaudrateIndex: Modify the UART speed . 106 8.19.1 Example 1 . 106 8.19.2 Example 2 . 107 8.20 UART_Flags: Congure the UART . 108 8.20.1 Example 1 . 108 8.20.2 Example 2 . 108 8.21 CFG_Flags: Congure the Module . 110 8.21.1 Example 1 . 110 8.21.2 Example 2 . 110 8.22 DIS_ManufacturerName: Congure the manufacturer name . 111 8.22.1 Example 1 . 111 8.22.2 Example 2 . 111 8.23 DIS_ModelNumber: Congure the model number . 112 8.23.1 Example 1 . 112 8.23.2 Example 2 . 112
. 113 8.24.1 Example 1 . 113 8.24.2 Example 2 . 113 8.25 DIS_HWVersion: Congure the HW version . 114 8.25.1 Example 1 . 114 8.25.2 Example 2 . 114 8.26 DIS_SWVersion: Congure the SW version . 115 8.26.1 Example 1 . 115 8.26.2 Example 2 . 115 8.27 DIS_Flags: Congure the Device Information Service . 116 8.27.1 Example 1 . 116 8.27.2 Example 2 . 116 8.24 DIS_SerialNumber: Congure the serial number 9 Timing parameters 120 9.1 Reset and sleep . 120 9.2 BLE timing parameters . 120 9.3 Connection establishment . 120 9.4 Connection based data transmission . 121 10 Peripheral only mode 122 10.1 Peripheral only mode . 122 10.2 Reasons to use the peripheral only mode . 122 10.3 How to use the peripheral only mode . 123 10.4 More information . 123 11 Customizing the AMB2623 125 11.1 DIS - Device information service . 125 11.2 UUID . 125 11.3 Appearance . 125 12 Firmware update 126 12.1 Firmware update using the SWD interface . 126 12.2 Firmware update using the AMB2623 OTA bootloader
. 126 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 6 13 Firmware history 128 14 Design in guide 129 14.1 Advice for schematic and layout . 129 14.2 Dimensioning of the micro strip antenna line . 131 14.3 Antenna solutions . 132 14.3.1 Wire antenna . 132 14.3.2 Chip antenna . 132 14.3.3 PCB antenna . 133 14.3.4 Antennas provided by Wrth Elektronik eiSos
. 134 AMB1981 - 868 MHz dipole antenna . 134 AMB1982 - 868 MHz magnetic base antenna . 135 AMB1926 - 2.4 GHz dipole antenna . 136 14.3.4.1 14.3.4.2 14.3.4.3 15 Manufacturing information 137 15.1 Moisture sensitivity level . 137 15.2 Soldering . 137 15.2.1 Reow soldering . 137 15.2.2 Cleaning . 139 15.2.3 Other notations . 139 15.3 ESD handling . 139 15.4 Safety recommendations . 140 16 Physical dimensions 141 16.1 Dimensions . 141 16.2 Weight . 141 16.3 Module drawing . 142 16.4 Footprint . 143 16.5 Antenna free area . 143 17 Marking 144 17.1 Lot number
. 144 17.2 General labeling information . 145 17.2.1 Example labels of Wrth Elektronik eiSos products . 145 18 Bluetooth SIG listing/qualication 18.1 Qualication steps when referencing the AMB2623 146
. 146 19 Regulatory compliance information 147 19.1 Important notice FCC . 147 19.2 Conformity assessment of the nal product
. 147 19.3 Exemption clause . 147 19.4 FCC Declaration of conformity . 148 19.5 IC Declaration of conformity . 148 19.6 FCC and IC requirements to OEM integrators . 148 19.7 Pre-certied antennas . 150 20 Important information 151 20.1 General customer responsibility . 151 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 7 20.2 Customer responsibility related to specic, in particular safety-relevant appli-
cations . 151 20.3 Best care and attention . 151 20.4 Customer support for product specications . 151 20.5 Product improvements . 152 20.6 Product life cycle . 152 20.7 Property rights . 152 20.8 General terms and conditions . 152 21 Legal notice 153 21.1 Exclusion of liability
. 153 21.2 Suitability in customer applications . 153 21.3 Trademarks . 153 21.4 Usage restriction . 153 22 License agreement for Wrth Elektronik eiSos GmbH & Co. KG connectivity 155 product rmware and software 22.1 Limited license . 155 22.2 Usage and obligations . 155 22.3 Ownership . 156 22.4 Firmware update(s)
. 156 22.5 Disclaimer of warranty . 156 22.6 Limitation of liability
. 157 22.7 Applicable law and jurisdiction . 157 22.8 Severability clause . 157 22.9 Miscellaneous
. 157 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 8 1 Introduction 1.1 Operational description The AMB2623 exists in two variants, the AMB2623 with integrated PCB-antenna, and the AMB2623 -1 with 50 connection to an external antenna. For the general functionality there is no difference between the variants. The AMB2623 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 5 it offers a fast and secure data transmission of small data packages (up to 243 Bytes) between two or more parties (point to point topology). A serial interface (UART) is available for communication with the host system. The AMB2623 uses the BLE standard to provide general data transmission between several devices. The standard itself offers a wide range of congurations and possibilities to suit and optimize sophisticated customer applications. To fulll the needs and specications of such applications a tailored rmware can be developed on the basis of the AMB2623 hardware. This includes the connection and communication to custom sensors, custom BLE proles, timing congurations, security conguration as well as power consumption optimizations. 1.1.1 Key features The AMB2623 offers the following key features that are described in the manual in more detail:
SPP-like connection-based secured data transmission: The AMB2623 rmware imple-
ments an SPP-like BLE-prole that allows the bidirectional data transmission between several AMB2623 and/or to other BLE devices implementing the AMBER SPP prole. Any module in the network can initiate connection setup. Secured connections allow the transmission of encrypted data (user-dened key or pairing). Fast sensor data transmission via Beacons: The AMB2623 supports the transmission and reception of Beacons. Beacons are fast broadcast messages that allow the energy-
efcient 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 efcient. Advanced customization capabilities: The congurable Device Information Service (DIS), the UUID and the appearance of the BLE prole, enable to personalize the AMB2623 to fuse with the users end product. Low power position sensing solutions: The current TX power of any AMB2623 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 AMB2623 offers a UART-interface to communicate with a host using a user-dened baud rate and a simple command interface. Latest microprocessor generation provided by Nordic Semiconductor nRF52 series:
The heart of the AMB2623 is a BLE-chip of the nRF52 series offering high performance values combined with low power consumption. It is a 32 Bit ARM Cortex-M4F CPU with 512kB ash + 64kB RAM and up to 4dBm output power. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 9 Bluetooth 5 stack: The Bluetooth 5 stack enables fast and energy efcient data transmis-
sion using state-of-the-art technology of Nordic Semiconductors. All BLE roles supported: The integrated BLE stack supports all BLE roles. Depending on the current state of operation the AMB2623 rmware automatically switches its role to execute the users instructions. Flexible wired interfacing: If custom hardware does not support UART communication or in case of a host less implementation, the AMB2623 is equipped with extra pins suited for custom device/sensor connection. With help of these, a tailored rmware can be developed which is optimized to the customers needs. The pins can be congured to various functions such as UART, SPI, I2C, ADC, PWM, NFC and GPIO. OTA rmware update: The AMB2623 rmware provides over the air rmware update ca-
pabilities. Firmware updates can be applied using the Nordic Apps for cell phones. Peripheral only mode: The AMB2623 rmware (version 3.0.0 or newer) provides the "pe-
ripheral only" operation mode (see chapter 10), that allows the easy adaption of al-
ready existing custom hardware with the BLE 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 BLE devices (like smart phones in-
cluding a custom App) using an authenticated and encrypted BLE link without the need of conguring the module. 1.1.2 Connectivity The BLE standard allows to setup a network with various BLE devices from different manu-
facturers. To be able to communicate with AMB2623 devices, the AMBER SPP-like prole must be known and implemented by all network participants. Thus arbitrary BLE devices
(like iOS or Android devices) must implement this prole, too. To do so, the AMB2623 appli-
cation note 1 contains the design data of the AMBER SPP-like prole. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 10 1.2 Block diagram Figure 1: Block diagram 1.3 Ordering information WE order code Former order code Description 2608011024010 AMB2623 -TR 2608011124010 2608011024011 2608011124011 AMB2623 -1-TR AMB2623 AMB2623 -1 Bluetooth Smart Module with integrated antenna, Tape & Reel Bluetooth Smart Module with RF pad, Tape & Reel Same as AMB2623 -TR, but not Tape & Reel Same as AMB2623 -1-TR, but not Tape & Reel Table 1: Ordering information AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 11 2 Electrical specications As not otherwise stated measured on the evaluation board AMB2623 -EV with T=25C, VDDS=3V, f=2.44GHz, internal DC-DC converter in use. 2.1 Recommended operating conditions Description Ambient temperature Supply voltage (VDDS) Supply rise time (0V to 1.7V) Min. Typ. Max. Unit C
-40 V 1.8 ms 85 3.6 60 25 3 Table 2: Recommended operating conditions The on-chip power-on reset circuitry may not function properly for rise times longer than the specied 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 or erroneous behav-
ior. An instable supply voltage may signicantly decrease the radio performance and stability. 2.2 Absolute maximum ratings Description Supply voltage (VDD) Voltage on any digital pin, VDD3.6V Voltage on any digital pin, VDD3.6V Input RF level Flash endurance Typ. Min.
-0.3
-0.3
-0.3 Max.
+3.9 VDD+0.3 3.9 10 Unit V V V dBm 10 000 Write/erase cycles Table 3: Absolute maximum ratings AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 12 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 mA mA mA A mA mA mA 7.51 5.31 5.41 0.4 112 82 82 Table 4: Power consumption for 100% transmission/reception Due to the BLE time slot operation, the real operating currents are reduced signicantly and depend on the user selectable advertising and connection interval settings. 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 Figure 2 and Figure 3). Currents and state durations are dependent on the conguration 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/ . 1Transmitter only with DC/DC converter from nRF52 data sheet. 2Full module consumption. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 13 Figure 2: Current consumption calculation in advertising mode with 40ms advertising inter-
val, UART disabled AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 14 Figure 3: Measured AMB2623 transient current consumption in advertising mode with 40ms advertising interval, excerpt of 5ms AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 15 2.4 Radio characteristics 50 conducted measurements from nRF52 data sheet Description Output power Input sensitivity ( 37 Bytes, BER=1E-3) RSSI accuracy valid range (2dB) Enable TX or RX delay Enable TX or RX delay (fast mode) Disable TX delay Disable RX delay
+5
-90
+3
-921 Min. Typ. Max. Unit
-40 dBm dBm dBm s s s s 140 40 6 0
-20 Table 5: Radio parameters Output power RF_TXPower = 4 Min. Typ. Max. Unit AMB2623 -1 (50 conducted) dBm dBm AMB2623 (e.i.r.p.) 3
-2 5 0 Table 6: Output power 1nRF52832 Rev.1, with build code CIAA-B00, CSP package, in DC/DC Mode AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 16 2.5 Pin characteristics Measurements from nRF52 data sheet Description Input high voltage Input low voltage Min. Typ. 0.7 VCC VSS Max. VCC 0.3 VCC 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 1 6 3 1 6 3 Table 7: Pin characteristics 4 15 4 14 2 10 2 9 13 13 Unit V V mA mA mA mA mA mA k k AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 17 3 Pinout Figure 4: Pinout (top view) AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 18 GNDAIN5AIN4AIN2AIN1AIN0XL2XL1NFC1NFC2VDDAIN3RESETSWDIOSWDCLKGNDRF171211871 No C Pin Designation I/O RF RF Description Antenna connection. Only applicable for module variant with external Antenna (e.g. AMB2623 -1). Do not connect in case of modules with internal PCB antenna (e.g. AMB2623 ). GND Supply Ground SWDCLK Input SWDIO Input P0.21 RESET Input P0.05/AIN3 BOOT Input Serial wire clock (SWD Interface). Uses internal pull down resistor. Do not connect if not needed. Serial wire input/output (SWD Interface). 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-
set starts the module in OTA bootloader mode. Uses internal pull up resistor1. Do not connect if not needed. VDD Supply Supply voltage P0.10/NFC2 OPERATION MODE Input P0.09/NFC1 RESERVED I/O P0.00/XL1 LED_1 Output P0.01/XL2 LED_2 Output Operation mode pin with internal pull down resis-
tor1 during start-up. Low level or open: Normal Mode. High level: Peripheral only Mode. Do not connect if not needed. Do not connect. Indicates the module state (active high). Do not connect if not needed. Indicates the module state (active high). Do not connect if not needed. P0.02/AIN0 UART TX Output UART(Transmission) P0.03/AIN1 UART RX P0.04/AIN2 P0.28/AIN4 RTS CTS P0.29/AIN5 WAKE_UP UART (Reception). Uses internal pull up resis-
tor1. Input Output Only used if ow control is enabled. Do not con-
nect if not needed. Only used if ow control is enabled. Do not con-
nect if not needed. Wake-up will allow leaving the system-off mode or re-enabling the UART. Uses internal pull up resistor1. Do not connect if not needed. Input Input GND Supply Ground Table 8: Pinout 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 1Internal pull ups or pull downs are congured at startup by the rmware installed in the SoC. The pull up on the RESET pin cannot be disabled by rmware. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 19 4 Quick start 4.1 Minimal pin conguration In factory state the modules are immediately ready for operation; the following pins are re-
quired in the minimal conguration:
VDD, GND, UART TX, UART RX, RESET If the ow 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 rmware update. A standard socket on the customers PCB for con-
necting a ash 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-save rmware update method using the SWD interface is recommended. Without having the SWD interface available a fail-save rmware 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 chapter 3 for details on all pins. Please refer to the AMB2623 -EV schemes for a reference design. Implementing the fail-save rmware update method using the SWD interface is recommended. Without having the SWD interface available a fail-save rmware update on a customer PCB cannot be guaranteed. 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 VCC is stable to ensure a safe start-up. The module will send a CMD_GETSTATE_CNF to indicate
"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 sufcient. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 20 Figure 5: Power up 4.3 Quickstart example This section describes how to quick start the data transmission between two AMB2623 mod-
ules. 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 AMB2623 -EV is recommended. Connect the two devices (modules, EV-boards or USB dongles) to a PC. A terminal pro-
gram, 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 conguration of 115200 Baud, 8 data Bits, 1 stop Bit and parity set to none (8n1). To reproduce the following sequence, note that, the FS_BTMAC of every module 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 chapter 8. Note that the module goes to ACTION_SLEEP mode if no connection is setup after RF_AdvertisingTimeout seconds. The module will indicate this using a CMD_SLEEP_CNF. In addition, the UART is disabled in ACTION_SLEEP mode. The default value is 0s, which means that it will run forever. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 21 Connection setup and rst 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 Response CMD_GETSTATE_CNF: Module A started in ACTION_IDLE mode. Response CMD_GETSTATE_CNF: Module B started in ACTION_IDLE mode. 2. Request the FS_BTMAC of both modules. Info Request CMD_GET_REQ with settings index 4 Response CMD_GET_CNF: FS_BTMAC of module A is 0x55 0x00 0x00 0xDA 0x18 0x00 Request CMD_GET_REQ with settings index 4 Response CMD_GET_CNF: FS_BTMAC of module B is 0x11 0x00 0x00 0xDA 0x18 0x00 3. Connect module A to module B via Bluetooth. Module A Module B 02 41 02 00 01 01 41 02 41 02 00 01 01 41 Module B Module A 02 10 01 00 04 17 02 50 07 00 00 55 00 00 DA 18 00 C2 02 10 01 00 04 17 02 50 07 00 00 11 00 00 DA 18 00 86 This example is taken from an older rmware. Using newer rmwares with the optional BT 4.2 feature "LE Packet Length Extension", the maximum supported payload per packet may be higher than 0x13. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 22 Info Request CMD_CONNECT_REQ with FS_BTMAC of module B Response CMD_CONNECT_CNF: Request understood, try to connect now Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Module B Module A 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 C6 07 00 00 11 00 00 DA 18 00 13 C3 02 86 07 00 00 55 00 00 DA 18 00 14 02 C6 07 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 Request CMD_DATA_REQ: Send "ABCD" to module A Response CMD_DATA_CNF: Request received, send data now Indication CMD_DATA_IND: Received string
"ABCD" from FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 with RSSI of 0xCA (-54dBm) Response CMD_TXCOMPLETE_RSP: Data transmitted successfully 5. Reply with "EFGH" to module B. Module A 02 84 0B 00 11 00 00 DA 18 00 CA 41 42 43 44 90 Module B 02 04 04 00 41 42 43 44 06 02 44 01 00 00 47 02 C4 01 00 00 C7 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 23 Info Request CMD_DATA_REQ: Send "EFGH" to module B Response CMD_DATA_CNF: Request received, send data now Indication CMD_DATA_IND: Received string
"EFGH" from FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 with RSSI of 0xC1 (-63dBm) Response CMD_TXCOMPLETE_RSP: Data transmitted successfully Module B Module A 02 04 04 00 45 46 47 48 0E 02 44 01 00 00 47 02 84 0B 00 55 00 00 DA 18 00 C1 45 46 47 48 D7 02 C4 01 00 00 C7 6. Now module A closes the connection, so both modules will get a disconnect indication. Info Request CMD_DISCONNECT_REQ: Disconnect Response CMD_DISCONNECT_CNF: Request received, disconnect now Indication CMD_DISCONNECT_IND: Connection closed Indication CMD_DISCONNECT_IND: Connection closed Module A 02 07 00 00 05 02 47 01 00 00 44 02 87 01 00 16 92 Module B 02 87 01 00 13 97 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 24 5 Functional description The AMB2623 module acts as a slave and can be fully controlled by an external host that implements the command interface. The conguration as well as the operation of the mod-
ule can be managed by predened commands that are sent as telegrams over the UART interface of the module. The AMB2623 can operate in different states. Depending on the active state several com-
mands of the command interface (see chapter 7) are permitted to modify the state, congure the module or transmit data over the radio interface. An overview of the different states and the corresponding allowed commands can be found in Figure 6. When the AMB2623 is powered up, it starts in ACTION_IDLE state. In this state the module advertises (BLE role "peripheral"), such that other devices in range (BLE role "central" or "ob-
server") can detect it and connect to it. If no connection was setup after RF_AdvertisingTimeout seconds, the module goes to ACTION_SLEEP state which will stop advertising. The ACTION_IDLE state also allows to switch to ACTION_SCANNING state, where the module stops advertising and scans for other advertising modules in range (BLE role "central"). When leaving the ACTION_SCANNING state with the corresponding command, the module is in ACTION_IDLE state and starts advertising again. The ACTION_CONNECTED state can be entered either by getting a connection request from an-
other module (BLE role "peripheral") or by setting up a connection itself (BLE role "central"). In this case it stops advertising and data can be transmitted and received to/from the con-
nected 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 ACTION_IDLE state and starts advertising again. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 25 Figure 6: State overview AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 26 5.1 State indication using the LED pins The pins LED_1 and LED_2 of the AMB2623 can be used to determine the module s-
tate. The states described in Figure 6 result in the following pin behavior. The pins on the AMB2623 are active high. State ACTION_IDLE ACTION_SCANNING ACTION_CONNECTED ACTION_SLEEP ACTION_DTM BOOTLOADER waiting for connection BOOTLOADER connected, rmware update running LED_1 Blinking (On for 200ms, Off for 2800ms) Blinking (On for 1000ms, Off for 1000ms) LED_2 Off Off On Off Off On Off Off, On (as soon as the channel was opened successfully, see CMD_CHANNELOPEN_RSP) Off Off Off On Table 9: LED behavior of the AMB2623 5.2 Sleep mode Especially for battery-powered devices the ACTION_SLEEP mode (system-off mode) sup-
ports very low power consumption (<1A). It can be entered by sending the command CMD_SLEEP_REQ to the module. If allowed (due to the current operating state) the module will then send a CMD_SLEEP_CNF and then enter the ACTION_SLEEP mode. In ACTION_SLEEP mode the UART is disabled, so the module will not receive or transmit any data. To prevent leakage current, the host shall not pull the UART_RX to LOW level (as the module has an internal pull-up resistor enabled on this pin). To leave the ACTION_SLEEP mode and enter ACTION_IDLE state again, the module has to be woken up by applying a low signal to the WAKE_UP pin for at least 5ms before releasing the signal back to high. The module then restarts completely, so that all volatile settings are set to default. A CMD_GETSTATE_CNF will be send when the module is ready for operation. If the mod-
Please note that the WAKE_UP pin has a second function. ule is not in ACTION_SLEEP mode and the UART was disabled using the CMD_UARTDISABLE_REQ, the UART can be re-enabled by applying falling edge, holding the line low for at least 10ms before applying a rising edge and holding it high for at least 10ms. In this case the module answers with a CMD_UARTENABLE_IND message. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 27 5.3 Identication of an AMB2623 device on the radio The AMB2623 can be identied on the radio interface by its FS_BTMAC. This FS_BTMAC is a Bluetooth-conform MAC address, which is part of the data package sent during advertising in ACTION_IDLE mode. A FS_BTMAC has the size of 6 Bytes. In ACTION_SCANNING state a module listens to the data packets of all advertising modules in range and stores their FS_BTMAC to an internal data base. With help of a FS_BTMAC a connection to the corresponding device can then be established using the CMD_CONNECT_REQ command. To simplify the identication of AMB2623 devices on the RF-interface a short user-dened name (see RF_DeviceName) can be given to the module, which is also part of the advertising packet. The FS_BTMAC consists of FS_SerialNumber of the module. the company ID 0x0018DA followed by the 5.4 Connection based data transmission, with or without security In the BLE standard the transmission of data typically is connection based. A connection between two devices can be secured (with or without key exchange) or unsecured (default setting). In any case, each data packet transmitted is acknowledged on the link layer, such that it is resent as long as a packet is lost. The following lines describe how to run the con-
nection setup and data transmission using the AMB2623 . If module A is supposed to setup a connection with module B, module A can use the com-
mand CMD_CONNECT_REQ including the FS_BTMAC of module B. If the FS_BTMAC of module B is unknown, a scan can be run before by module A to discover all available modules in range. After sending the command CMD_CONNECT_REQ, the module answers with a CMD_CONNECT_CNF to signal that the request has been understood and the module now tries to establish the connection. If module B cannot be found on the air within a timeout, module A outputs a CMD_CONNECT_IND with "failed" as status. Otherwise, as soon as the physical connection has been set up suc-
cessfully, module A and B print a CMD_CONNECT_IND with the status of the successful connec-
tion and LED_1 turns on. Next some security and authentication messages will follow, like CMD_SECURITY_IND, if secu-
rity is enabled. After the physical connection has been setup successfully the modules exchange their ser-
vices. As soon as this has nished successfully, a CMD_CHANNELOPEN_RSP is given out to the UART indicating that the connection is ready for data transmission. Furthermore, LED_2 turns on. Now data can be transmitted in both directions using the command CMD_DATA_REQ. It is con-
rmed by a CMD_DATA_CNF (data will be processed) and a CMD_TXCOMPLETE_RSP (data trans-
mitted successfully). Each time data has been received a CMD_DATA_IND will be output containing the transmitted data. As soon as one module closes the connection using a CMD_DISCONNECT_REQ, both modules will inform their host by a CMD_DISCONNECT_IND message that the connection is no longer AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 28 If one module is no longer within range, the CMD_DISCONNECT_IND message is trig-
open. gered by a timeout. For an example on setting up an unsecured connection, see chapter 4.3. See also the AMB2623 application note 1 "advanced user guide" to get detailed information about the connection setup with foreign devices. 5.4.1 Further information for a secure connection setup The RF_SecFlags parameter of the module determines the security mode. If a certain se-
curity mode of an AMB2623 peripheral device is set, its security level has to be met by the connecting central device to be able to exchange data. As soon as the dened security level is not met by the central device, no access to the peripherals proles will be granted. When connecting from an AMB2623 to an AMB2623 , you shall not use differ-
ent security modes. To get further information about the secured connection setup, when using a foreign device (i.e. mobile phone with a custom APP), please refer to the AMB2623 application note 1 "advanced user guide". 5.4.1.1 Just works mode In case of the "Just works" mode, each time a connection is established, a new random key is exchanged in advance to be used for data encryption. Since no authentication will be performed, also devices without input and output capabilities (like keyboard or display) are able to connect to each other. Example: Secured connection with LE Legacy security method "Just Works" without bonding 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 Response CMD_GETSTATE_CNF: Module A started in ACTION_IDLE mode. Response CMD_GETSTATE_CNF: Module B started in ACTION_IDLE mode. 2. Request the FS_BTMAC of both modules. Module A Module B 02 41 02 00 01 01 41 02 41 02 00 01 01 41 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 29 Info Request CMD_GET_REQ with settings index 4 Response CMD_GET_CNF: FS_BTMAC of module A is 0x55 0x00 0x00 0xDA 0x18 0x00 Request CMD_GET_REQ with settings index 4 Response CMD_GET_CNF: FS_BTMAC of module B is 0x11 0x00 0x00 0xDA 0x18 0x00 Module B Module A 02 10 01 00 04 17 02 50 07 00 00 55 00 00 DA 18 00 C2 02 10 01 00 04 17 02 50 07 00 00 11 00 00 DA 18 00 86 3. Congure the parameter RF_SecFlags to use "Just Works" pairing method for BT se-
curity. Info Perform CMD_SET_REQ with settings index 12 and value 0x02 on module A Response CMD_SET_CNF (Module will restart to adopt the new value) Response CMD_GETSTATE_CNF Perform CMD_SET_REQ with settings index 12 and value 0x02 on module B Response CMD_SET_CNF (Module will restart to adopt the new value) Response CMD_GETSTATE_CNF 4. Connect module A to module B via Bluetooth. Module B Module A 02 11 02 00 0C 02 1F 02 51 01 00 00 52 02 41 02 00 01 01 41 02 11 02 00 0C 02 1F 02 51 01 00 00 52 02 41 02 00 01 01 41 This example is taken from an older rmware. Using newer rmwares with the optional BT 4.2 feature "LE Packet Length Extension", the maximum supported payload per packet may be higher than 0x13. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 30 Info Request CMD_CONNECT_REQ with FS_BTMAC of module B Response CMD_CONNECT_CNF: Request understood, try to connect now Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_SECURITY_IND, status 0x02
(encrypted link, pairing, no bonding), with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_SECURITY_IND, status 0x02
(encrypted link, pairing, no bonding), with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Module B Module A 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 88 07 00 02 11 00 00 DA 18 00 5C 02 C6 07 00 00 11 00 00 DA 18 00 13 C3 02 86 07 00 00 55 00 00 DA 18 00 14 02 88 07 00 02 55 00 00 DA 18 00 18 02 C6 07 00 00 55 00 00 DA 18 00 13 87 5. 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 Request CMD_DATA_REQ: Send "ABCD" to module A Response CMD_DATA_CNF: Request received, send data now Indication CMD_DATA_IND: Received string
"ABCD" from FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 with RSSI of 0xCA (-54dBm) Response CMD_TXCOMPLETE_RSP: Data transmitted successfully Module A 02 84 0B 00 11 00 00 DA 18 00 CA 41 42 43 44 90 Module B 02 04 04 00 41 42 43 44 06 02 44 01 00 00 47 02 C4 01 00 00 C7 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 31 6. Reply with "EFGH" to module B. Info Request CMD_DATA_REQ: Send "EFGH" to module B Response CMD_DATA_CNF: Request received, send data now Indication CMD_DATA_IND: Received string
"EFGH" from FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 with RSSI of 0xC1 (-63dBm) Response CMD_TXCOMPLETE_RSP: Data transmitted successfully Module B Module A 02 04 04 00 45 46 47 48 0E 02 44 01 00 00 47 02 84 0B 00 55 00 00 DA 18 00 C1 45 46 47 48 D7 02 C4 01 00 00 C7 7. Now module A closes the connection, so both modules will get a disconnect indication. Info Request CMD_DISCONNECT_REQ: Disconnect Response CMD_DISCONNECT_CNF: Request received, disconnect now Indication CMD_DISCONNECT_IND: Connection closed Indication CMD_DISCONNECT_IND: Connection closed Module A 02 07 00 00 05 02 47 01 00 00 44 02 87 01 00 16 92 Module B 02 87 01 00 13 97 8. You may want to perform a CMD_FACTORYRESET_REQ to restore default settings. 5.4.1.2 StaticPasskey mode In case of the "StaticPasskey" mode, a pass key has to be entered at the central side that has to match the pass key of the peripheral. Here the AMB2623 uses a static pass key in the peripheral role that is stored in the parameter RF_StaticPasskey. When using this method, the central device requests its host to enter the correct pass key (see CMD_PASSKEY_IND). In this case the pass key of the peripheral has to be entered on central side using the CMD_PASSKEY_REQ command. If the entered pass key is correct, the channel will be opened for data transmission. Otherwise, the connection will be rejected. Example: Secured connection with security method "StaticPasskey"
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 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 32 Info Response CMD_GETSTATE_CNF: Module A started in ACTION_IDLE mode. Response CMD_GETSTATE_CNF: Module B started in ACTION_IDLE mode. 2. Request the FS_BTMAC of both modules. Info Request CMD_GET_REQ with settings index 4 Response CMD_GET_CNF: FS_BTMAC of module A is 0x55 0x00 0x00 0xDA 0x18 0x00 Request CMD_GET_REQ with settings index 4 Response CMD_GET_CNF: FS_BTMAC of module B is 0x11 0x00 0x00 0xDA 0x18 0x00 Module A Module B 02 41 02 00 01 01 41 02 41 02 00 01 01 41 Module B Module A 02 10 01 00 04 17 02 50 07 00 00 55 00 00 DA 18 00 C2 02 10 01 00 04 17 02 50 07 00 00 11 00 00 DA 18 00 86 3. Congure the parameter RF_SecFlags to use "StaticPasskey" pairing method for BT security. Info Perform CMD_SET_REQ with settings index 12 and value 0x02 on module A Response CMD_SET_CNF (Module will restart to adopt the new value) Response CMD_GETSTATE_CNF Perform CMD_SET_REQ with settings index 12 and value 0x02 on module B Response CMD_SET_CNF (Module will restart to adopt the new value) Response CMD_GETSTATE_CNF 4. Connect module A to module B via Bluetooth. Module B Module A 02 11 02 00 0C 03 1E 02 51 01 00 00 52 02 41 02 00 01 01 41 02 11 02 00 0C 03 1E 02 51 01 00 00 52 02 41 02 00 01 01 41 This example is taken from an older rmware. Using newer rmwares with the optional BT 4.2 feature "LE Packet Length Extension", the maximum supported payload per packet may be higher than 0x13. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 33 Info Request CMD_CONNECT_REQ with FS_BTMAC of module B Response CMD_CONNECT_CNF: Request understood, try to connect now Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_PASSKEY_IND to ask for the pass key Answer with the CMD_PASSKEY_REQ and the pass key "123123"
Response CMD_PASSKEY_CNF: Pass key ok Indication CMD_SECURITY_IND, status 0x02
(encrypted link, pairing, no bonding), with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_SECURITY_IND, status 0x02
(encrypted link, pairing, no bonding), with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Module A 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 8D 07 00 00 11 00 00 DA 18 00 5B 02 0D 06 00 31 32 33 31 32 33 09 02 4D 01 00 00 4E 02 88 07 00 02 11 00 00 DA 18 00 5C 02 C6 07 00 00 11 00 00 DA 18 00 13 C3 Module B 02 86 07 00 00 55 00 00 DA 18 00 14 02 88 07 00 02 55 00 00 DA 18 00 18 02 C6 07 00 00 55 00 00 DA 18 00 13 87 5. 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. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 34 Info Request CMD_DATA_REQ: Send "ABCD" to module A Response CMD_DATA_CNF: Request received, send data now Indication CMD_DATA_IND: Received string
"ABCD" from FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 with RSSI of 0xCA (-54dBm) Response CMD_TXCOMPLETE_RSP: Data transmitted successfully 6. Reply with "EFGH" to module B. Info Request CMD_DATA_REQ: Send "EFGH" to module B Response CMD_DATA_CNF: Request received, send data now Indication CMD_DATA_IND: Received string
"EFGH" from FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 with RSSI of 0xC1 (-63dBm) Response CMD_TXCOMPLETE_RSP: Data transmitted successfully Module A 02 84 0B 00 11 00 00 DA 18 00 CA 41 42 43 44 90 Module B 02 04 04 00 41 42 43 44 06 02 44 01 00 00 47 02 C4 01 00 00 C7 Module B Module A 02 04 04 00 45 46 47 48 0E 02 44 01 00 00 47 02 84 0B 00 55 00 00 DA 18 00 C1 45 46 47 48 D7 02 C4 01 00 00 C7 7. Now module A closes the connection, so both modules will get a disconnect indication. Info Request CMD_DISCONNECT_REQ: Disconnect Response CMD_DISCONNECT_CNF: Request received, disconnect now Indication CMD_DISCONNECT_IND: Connection closed Indication CMD_DISCONNECT_IND: Connection closed Module A 02 07 00 00 05 02 47 01 00 00 44 02 87 01 00 16 92 Module B 02 87 01 00 13 97 8. You may want to perform a CMD_FACTORYRESET_REQ to restore default settings. 5.4.1.3 Bonding The SECFLAGS_BONDING_ENABLE ag in the RF_SecFlags user setting allows enabling the bonding feature. This feature stores the keys that are exchanged during the pairing phase in a connection setup. With this, subsequent connections to bonded devices can be estab-
lished without renegotiation. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 35 The commands CMD_GETBONDS_REQ and CMD_DELETEBONDS_REQ allow to display and remove certain or all entries of the list of bonded devices. Example: Secured connection with LE Legacy security method "Just Works" using bonding 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 Response CMD_GETSTATE_CNF: Module A started in ACTION_IDLE mode. Response CMD_GETSTATE_CNF: Module B started in ACTION_IDLE mode. 2. Request the FS_BTMAC of both modules. Info Request CMD_GET_REQ with settings index 4 Response CMD_GET_CNF: FS_BTMAC of module A is 0x55 0x00 0x00 0xDA 0x18 0x00 Request CMD_GET_REQ with settings index 4 Response CMD_GET_CNF: FS_BTMAC of module B is 0x11 0x00 0x00 0xDA 0x18 0x00 Module A Module B 02 41 02 00 01 01 41 02 41 02 00 01 01 41 Module B Module A 02 10 01 00 04 17 02 50 07 00 00 55 00 00 DA 18 00 C2 02 10 01 00 04 17 02 50 07 00 00 11 00 00 DA 18 00 86 3. Congure the parameter RF_SecFlags to use "Just Works with bonding" pairing method for BT security. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 36 Info Perform CMD_SET_REQ with settings index 12 and value 0x0A (Just works with SECFLAGS_BONDING_ENABLE ag set) on module A Response CMD_SET_CNF (Module will restart to adopt the new value) Response CMD_GETSTATE_CNF Perform CMD_SET_REQ with settings index 12 and value 0x0A (Just works with SECFLAGS_BONDING_ENABLE ag set) on module B Response CMD_SET_CNF (Module will restart to adopt the new value) Response CMD_GETSTATE_CNF 4. Connect module A to module B via Bluetooth. Module A Module B 02 11 02 00 0C 0A 17 02 51 01 00 00 52 02 41 02 00 01 01 41 02 11 02 00 0C 0A 17 02 51 01 00 00 52 02 41 02 00 01 01 41 This example is taken from an older rmware. Using newer rmwares with the optional BT 4.2 feature "LE Packet Length Extension", the maximum supported payload per packet may be higher than 0x13. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 37 Info Request CMD_CONNECT_REQ with FS_BTMAC of module B Response CMD_CONNECT_CNF: Request understood, try to connect now Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_SECURITY_IND, status 0x01
(encrypted link, bonding established), with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_SECURITY_IND, status 0x01
(encrypted link, bonding established), with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Module B Module A 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 88 07 00 01 11 00 00 DA 18 00 5F 02 C6 07 00 00 11 00 00 DA 18 00 13 C3 02 86 07 00 00 55 00 00 DA 18 00 14 02 88 07 00 01 55 00 00 DA 18 00 1B 02 C6 07 00 00 55 00 00 DA 18 00 13 87 5. Now module A closes the connection, so both modules will get a disconnect indication. Info Request CMD_DISCONNECT_REQ: Disconnect Response CMD_DISCONNECT_CNF: Request received, disconnect now Indication CMD_DISCONNECT_IND: Connection closed Indication CMD_DISCONNECT_IND: Connection closed Module A 02 07 00 00 05 02 47 01 00 00 44 02 87 01 00 16 92 Module B 02 87 01 00 13 97 6. Connect module A to module B a second time. Now, since both devices have been bonded before, the exchanged keys are reused. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 38 Info Request CMD_CONNECT_REQ with FS_BTMAC of module B Response CMD_CONNECT_CNF: Request understood, try to connect now Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CONNECT_IND: Physical connection established successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_SECURITY_IND, status 0x00
(encrypted link to bonded device), with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 Indication CMD_SECURITY_IND, status 0x00
(encrypted link to bonded device), with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Indication CMD_CHANNELOPEN_RSP: Channel opened successfully to module with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 and maximum payload size of 0x13 (19 Bytes) per packet Module B Module A 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 88 07 00 00 11 00 00 DA 18 00 5E 02 C6 07 00 00 11 00 00 DA 18 00 13 C3 02 86 07 00 00 55 00 00 DA 18 00 14 02 88 07 00 00 55 00 00 DA 18 00 1A 02 C6 07 00 00 55 00 00 DA 18 00 13 87 7. You may want to perform a CMD_FACTORYRESET_REQ to restore default settings. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 39 5.5 Unidirectional connectionless data transmission using Beacons Besides the connection-based type of data transmission described in the previous section there exists a second method that uses so called Beacons. In this case, a limited amount of user data can be placed in the BLE scan response packet, which is broadcasted frequently without acknowledgement and without security. If an AMB2623 is supposed to broadcast some data, the command CMD_SETBEACON_REQ can be used to place user data in the scan response packet. If a second AMB2623 , which has its Beacon-function (see RF_BeaconFlags) enabled, is in the operating state ACTION_SCANNING, then the scan response packet is requested as soon as an advertising packet from the beacon module has been detected. Filtering the beacon messages can be enabled or disabled using RF_BeaconFlags. After the reception of the scan response packet the included user data is interpreted and given out to the UART using a CMD_BEACON_IND message. To set the module into ACTION_SCANNING mode the command CMD_SCANSTART_REQ has to be used. Enable the Beacon-function before by setting the corresponding Bit in the RF_BeaconFlags parameter. This method is very suitable for sensor networks, which frequently send their data to data collectors. Especially when using a slow RF_ScanTiming mode, data can be transmitted in a more energy efcient way. Please check the settings RF_AdvertisingTimeout and the advertising inter-
val in RF_ScanTiming to congure the frequency and interval of transmissions which will have an inuence on the current consumption of the module. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 40 Info Reset both modules using RESET pin, CMD_GETSTATE_CNF Congure RF_BeaconFlags using CMD_SET_REQ to "beacon rx enabled, no lter"
CMD_SET_CNF from module B Module B reset such that the change in the user setting takes effect (CMD_GETSTATE_CNF) Activate scanning on module B Response CMD_SCANSTART_CNF CMD_SETBEACON_REQ, content "Hallo"
CMD_SETBEACON_CNF receiving multiple CMD_BEACON_IND
... Deactivate scanning on module B, CMD_SCANSTOP_REQ Response CMD_SCANSTOP_CNF Reset module A (disable sending beacons), CMD_RESET_REQ Response CMD_RESET_CNF Response CMD_GETSTATE_CNF Module A Module B 02 41 02 00 01 01 41 02 41 02 00 01 01 41 02 11 02 00 0E 01 1E 02 51 01 00 00 52 02 41 02 00 01 01 41 02 09 00 00 0B 02 49 01 00 00 4A 02 8C 0C 00 02 00 00 DA 18 00 B5 48 61 6C 6C 6F B1 02 8C 0C 00 02 00 00 DA 18 00 B1 48 61 6C 6C 6F B5
... 02 0A 00 00 08 02 4A 01 00 00 49 02 0C 05 00 48 61 6C 6C 6F 4D 02 4C 01 00 00 4F
... 02 00 00 00 02 02 40 01 00 00 43 02 41 02 00 01 01 41 5.6 Energy-efcient distance estimation solutions The AMB2623 advertising packet contains the TX power value of the transmitting device. This value in combination with the RSSI value of the received advertising packet can be used to estimate the distance between the modules. Using a suitable triangulation algorithm and multiple receivers or transmitters, a position can be approximated. The advertising packets can be received by performing a passive scan that will not request the scan response. Thus only one frame, instead of three frames, is transmitted per adver-
tising interval. Besides the FS_BTMAC of the sending module, the RSSI value and the TX power is output in format of a CMD_RSSI_IND message via UART when an advertising packet of another AM-
B2623 has been received. To enable this function, the corresponding Bit in the RF_BeaconFlags has to be set. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 41 5.7 Congure the module for low power consumption Depending on the application environment of the AMB2623 , the goal is to nd the optimal trade-off between the modules performance and its power consumption. Therefore, the main settings and operation modes that affect the current consumption are listed below:
CMD_SLEEP_REQ: This command puts the module into ACTION_SLEEP mode, where it consumes the lowest current (<1A). In this case, both the UART and the BLE interface are shut down. CMD_UARTDISABLE_REQ: This command disables the UART interface. It is enabled again as soon as the module is reset/woken or when the module outputs a message e.g. when a connection request has been received or the WAKE_UP pin of the module was used. RF_TXPower: This setting can be used to congure the output power of the module. Reducing the output power saves energy. RF_ScanTiming and RF_ScanFactor: These settings dene the timing behavior of the module, when advertising or scanning. The less often the module sends advertising packets or scans, the less current is consumed. RF_ConnectionTiming: This setting denes the timing behavior of the module during connection setup and an established connection. The less often the connected mod-
ules communicate with each other, the less current is consumed. The on-board nRF52 SoC is running in debug mode. This will not occur if the pins are connected as described in this manual. For optimum energy efciency a user and application specic rmware may be required. 5.8 Start the direct test mode (DTM) The direct test mode (DTM) enables the test functions described in Bluetooth Specication Version 4.0, Vol. 6, Part F. The purpose of DTM is to test the operation of the radio at the physical level, such as:
transmission power and receiver sensitivity frequency offset and drift modulation characteristics packet error rate inter modulation performance AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 42 Conformance tests of the nRF52 with the DTM application are carried out by dedicated test equipment. To get access to the test functions the CMD_DTMSTART_REQ shall be used rst. This command restarts the module in direct test mode. A CMD_GETSTATE_CNF message conrms that the DTM has been started successfully. Now the CMD_DTM_REQ can be used to start and stop the test functions. After a test has been started, it has to be stopped before a next test can be run. Example: Transmission test on channel 0 with Bit pattern 0x0F The goal of this example is to show how the DTM, and in specic the transmission/reception test, can be run. Here fore we need to connect two modules, start the transmission test on one module and start the reception test on the second module. In this section, all packet data from or to the modules is given in hexadecimal notation. All steps are described in the following:
First, restart the modules in DTM mode. Info Request CMD_DTMSTART_REQ to enable the DTM on module A Response CMD_DTMSTART_CNF: Request understood, try to start DTM now Indication CMD_GETSTATE_CNF: Restarted module with DTM enabled Request CMD_DTMSTART_REQ to enable the DTM on module B Response CMD_DTMSTART_CNF: Request understood, try to start DTM now Indication CMD_GETSTATE_CNF: Restarted module with DTM enabled Module A Module B 02 1D 00 00 1F 02 5D 01 00 00 5E 02 41 02 00 10 05 54 02 1D 00 00 1F 02 5D 01 00 00 5E 02 41 02 00 10 05 54 Now both modules are ready for the DTM. Start the transmission test rst. Info Request CMD_DTM_REQ to start the transmission test on module A with channel 0 and Bit pattern 16 times 0x0F Response CMD_DTM_CNF: Started test successfully Module A Module B 02 1E 04 00 02 00 10 01 0B 02 5E 03 00 00 00 00 5F Start the reception test. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 43 Info Request CMD_DTM_REQ to start the reception test on module B with channel 0 Bit pattern 0x0F Response CMD_DTM_CNF: Started test successfully Module A Module B 02 1E 04 00 01 00 00 01 18 02 5E 03 00 00 00 00 5F Stop both tests again. Info Request CMD_DTM_REQ to stop the transmission test Response CMD_DTM_CNF: Stopped test successfully Request CMD_DTM_REQ to stop the reception test Response CMD_DTM_CNF: Stopped test successfully, received 0x14FE (5374_dec) packets Module B Module A 02 1E 04 00 03 00 00 01 1A 02 5E 03 00 00 80 00 DF 02 1E 04 00 03 00 00 01 1A 02 5E 03 00 00 94 FE 35 During the time the reception and transmission tests were running 5374 data packets have been received by module B, which were transmitted by module A. 5.9 Using the 2MBit phy Bluetooth 5 allows to transmit data with 2 MBit data rate. Bluetooth connections must still be setup using the 1 MBit phy to be backward compatible to Bluetooth 4.x devices. As soon as a connection has been setup, the connection can be updated to the 2 MBit phy. To switch to 2 MBit phy after the connection has been setup the AMB2623 offers the com-
mand CMD_PHYUPDATE_REQ. As response to this request a CMD_PHYUPDATE_IND is returned from the AMB2623, that gives feedback if the connection was switched to the new phy, or if the connection partner rejected the request. Please note that the 2 MBit phy is an optional feature of Bluetooth 5 devices and therefore must not be supported. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 44 6 Host connection 6.1 Serial interface: UART The conguration in factory state of the UART is 115200 Baud without ow control and with data format of 8 data Bits, no parity and 1 stop Bit ("8n1"). The baud rate of the UART can be congured by means of the UserSetting UART_BaudrateIndex. The data format is xed to 8n1. The ow control can be enabled by means of the UserSetting UART_Flags. The output of characters on the serial interface runs with secondary priority. For this reason, short interruptions may occur between the outputs of individual successive Bytes. The host must not implement too strict timeouts between two Bytes to be able to receive packets that have interruptions in between. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 45 7 The command interface The module acts as a slave and can be fully controlled by an external host. The conguration as well as the operation of the module can be managed by predened 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. request CMD_RESET_REQ the host asks the module to perform a reset. in case of the Conrmations: On each request, the module answers with a conrmation 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 rst Length Bytes 1 Byte Start signal: 0x02 (1 Byte) Command: One of the predened commands (1 Byte). Length: Species the data length in the following and is limited to 120 Bytes (unless stated otherwise in the command description) in order to prevent buffer overow. Length is a 16 Bit eld with LSB rst. Payload: Variable number (dened by the length eld) 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 nished 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 specic module s-
tates (see Figure 6). If a command is not permitted in the current state, the command conrmation returns "Operation not permitted" as a response. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 46 7.1 Scan for other modules in range 7.1.1 CMD_SCANSTART_REQ This command starts the scan operation to nd other AMB2623 in range. All found devices that t the AMB2623 specication (i.e. devices that support AMBER SPP service UUID) are saved in an internal data base. Before outputting the data base content using the command CMD_GETDEVICES_REQ, the scan has to be stopped using CMD_SCANSTOP_REQ. Format:
Start signal Command 0x02 0x09 Length CS 0x00 0x00 0x0B Response (CMD_SCANSTART_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x49 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, will start scan now 0x01: Operation failed 0xFF: Operation not permitted 7.1.2 CMD_SCANSTOP_REQ This command stops the scan operation that was started using CMD_SCANSTART_REQ. It stores the detected AMB2623 FS_BTMAC addresses in an internal database, which can be output using the CMD_GETDEVICES_REQ. Format:
Start signal Command 0x02 0x0A Length CS 0x00 0x00 0x08 Response (CMD_SCANSTOP_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x4A 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, will stop scan now 0x01: Operation failed 0xFF: Operation not permitted AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 47 7.1.3 CMD_GETDEVICES_REQ This command returns the information about the devices found during the last scan oper-
ation. #Devices determines the number of devices that have been detected. The corre-
sponding information will be output one after the other in the eld behind #Devices in the CMD_GETDEVICES_CNF response. The RSSI and TXPower values are transmitted in the twos complement notation. Format:
Start signal Command 0x02 0x0B Length CS 0x00 0x00 0x09 Response (CMD_GETDEVICES_CNF):
Start signal Command | 0x40 0x02 0x4B Length Status 2 Bytes 1 Byte
#Devices Payload CS 1 Byte
(Length - 2) Bytes 1 Byte The Payload sequentially lists the data of the detected #Devices devices.
#Devices times the following telegram (see example below). It consists of BTMAC RSSI 6 Bytes 1 Byte TXPower Device name length 1 Byte 1 Byte Device name Device name length Bytes Status:
0x00: Request received 0x01: Operation failed 0xFF: Operation not permitted there are too many devices found to be output, the response of If CMD_GETDEVICES_REQ is split into several CMD_GETDEVICES_CNF messages. the The detected device name is the content of the device name eld of the re-
ceived advertising packet. Thus, in case of the "Complete Local Name" is too long to t into the device name eld of the advertising packet, this could be the
"Shortened Local Name" of the device. If RSSI = 0x80, there is no value available. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 48 If TXPower = 0x80, there is no value available. If Device name length = 0, then there is no device name available. 7.1.3.1 Example 1 Request for the FS_BTMAC of the devices found during the last scan. Start signal Command 0x02 0x0B Length CS 0x00 0x00 0x09 Response:
Start signal Command
| 0x40 Length Status
#Devices Payload CS 0x02 0x4B 0x1E 0x00 0x00 0x02 0x11 0x00 0x00 0xDA 0x18 0x00 0xE2 0x04 0x05 0x4D 0x4F 0x44 0x20 0x31 0x55 0x00 0x00 0xDA 0x18 0x00 0xE5 0x00 0x05 0x4D 0x4F 0x44 0x20 0x32 0x11 During the last scan two devices have been detected:
Device 1 with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00, RSSI value of 0xE2 (-30 dBm), TXPower of 0x04 (=+4 dBm) and device name of length 5 with the value of 0x4D4F442031 ("MOD 1"). Device 2 with FS_BTMAC 0x55 0x00 0x00 0xDA 0x18 0x00 and RSSI value of 0xE5 (-27 dBm), TXPower of 0x00 (0 dBm) and device name 0x4D4F442032 ("MOD 2") of length 5. 7.1.4 CMD_RSSI_IND This telegram indicates the reception of an advertising packet sent by another AMB2623 module. It can be used to realize a position sensing application. This data can only be received, when the module is in ACTION_SCANNING mode (passive scan is sufcient) and the corresponding Bit in the RF_BeaconFlags is set. Besides the FS_BTMAC, the RSSI value of the advertising packet and the transmission power of the sending device are output. Both, the RSSI value and the TX power are in twos AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 49 complement notation. The accuracy is 2dB when inside the RSSI range of -90 to -20 dBm. The value of the parameter TX power is read from the content of the received advertise packet. Format:
Start signal Command 0x02 0x8B Length BTMAC RSSI 1 Byte 2 Bytes 6 Byte TX Power CS 1 Byte 1 Byte AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 50 7.2 Setup connections 7.2.1 CMD_CONNECT_REQ This command tries to setup a connection to the AMB2623 , which is identied by the FS_BTMAC used in the command. After the module prints a CMD_CONNECT_CNF to conrm that the request was received, the indication message CMD_CONNECT_IND follows which de-
termines whether the connection request was accepted by the other device. In case of enabled security features (see the setting RF_SecFlags) a CMD_SECURITY_IND is output in addition. As soon as the connection setup has been completed and all services have been discovered successfully a CMD_CHANNELOPEN_RSP is printed by the UART. Now data may be sent using the CMD_DATA_REQ. Format:
Start signal Command Length BTMAC CS 0x02 0x06 0x06 0x00 6 Bytes 1 Byte Response (CMD_CONNECT_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x46 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, try to connect to the device with the FS_BTMAC 0x01: Operation failed 0xFF: Operation not permitted 7.2.2 CMD_CONNECT_IND This telegram indicates the connection status and the FS_BTMAC of the connected device. This indication message is the result of a connection request (CMD_CONNECT_REQ). Format:
Start signal Command Length Status BTMAC CS 0x02 0x86 0x07 0x00 1 Byte 6 Bytes 1 Byte Status:
0x00: Physical connection established successfully 0x01: Connection failed, e.g. due to a timeout (as dened by RF_ScanTiming) 7.2.3 CMD_SECURITY_IND This telegram indicates the security status and the FS_BTMAC of the connected device. This indication message is the result of a connection request (CMD_CONNECT_REQ). Format:
AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 51 Start signal Command Length Status BTMAC CS 0x02 0x88 0x07 0x00 1 Byte 6 Bytes 1 Byte Status:
0x00: Encrypted link to previously bonded device established 0x01: Bonding successful, encrypted link established 0x02: No bonding, pairing successful, encrypted link established 7.2.4 CMD_CHANNELOPEN_RSP This command is printed on the UART as soon as connection setup and service discovery has been completed successfully. Now data can be transmitted using the CMD_DATA_REQ. Next to the FS_BTMAC of the connected device, the maximum payload size that is supported by the link is part of this telegram. This indication message is the result of a connection request (CMD_CONNECT_REQ). Format:
Start signal Command Length Status BTMAC Max payload CS 0x02 0xC6 0x08 0x00 1 Byte 6 Bytes 1 Byte 1 Byte Status:
0x00: Success 7.2.5 CMD_DISCONNECT_REQ This command shuts down the existing connection. Thereafter the module prints a CMD_DISCONNECT_CNF to conrm that the request has been received, the indication mes-
sage CMD_DISCONNECT_IND follows which determines whether the disconnection operation has been performed successfully or not. Format:
Start signal Command 0x02 0x07 Length CS 0x00 0x00 0x05 Response (CMD_DISCONNECT_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x47 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, try to disconnect 0x01: Operation failed 0xFF: Operation not permitted AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 52 7.2.6 CMD_DISCONNECT_IND This telegram indicates that the connection has shut down successfully. This indication message is the result of a disconnection request (CMD_DISCONNECT_REQ). Format:
Start signal Command Length 0x02 0x87 0x01 0x00 Reason 1 Byte CS 1 Byte Reason:
0x08: Connection timeout 0x13: User terminated connection 0x16: Host terminated connection 0x3B: Connection interval unacceptable 0x3D: Connection terminated due to MIC failure (Not able to connect due to bad link quality, or connection request ignored due to wrong key) 0x3E: Connection setup failed 7.2.7 CMD_PHYUPDATE_REQ This commands allows to update the PHY of the current established connection. After the module prints a CMD_PHYUPDATE_CNF it tries to update the PHY. The result is indicated by CMD_PHYUPDATE_IND. The permissible options of the PHY are either 0x01 for 1MBit or 0x02 for 2MBit. Format:
Start signal Command Length PHY CS 0x02 0x1A 0x01 0x00 1 Byte 1 Byte Response (CMD_PHYUPDATE_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x5A 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received. Try to update PHY of current connection 0x01: Operation failed, e.g. due to invalid PHY 0xFF: Operation not permitted AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 53 7.2.8 CMD_PHYUPDATE_IND This command indicates that there was an attempt to update the PHY of the existing con-
nection. If the update was successful, the command also includes the new PHY for receiving and transmitting and also the BTMAC of the devices currently connected to. This command is the result of the CMD_PHYUPDATE_REQ. Format in case of success:
Status PHY Rx PHY Tx BTMAC 0x00 1 Byte 1 Byte 6 Bytes 1 Byte CS Start signal Command Length 0x02 0x9A 0x09 0x00 PHY Rx/PHY Tx:
0x01: Using 1 MBit PHY now 0x02: Using 2 MBit PHY now Format in case of failure:
Start signal Command Length 0x02 0x9A 0x02 0x00 Status 0x01 Info 1 Byte 1 Byte CS Info:
0x1A: Unsupported feature of remote device 7.2.9 CMD_PASSKEY_REQ When receiving a CMD_PASSKEY_IND during connection setup, the peripheral requests for a pass key to authenticate the connecting device. To answer this request the CMD_PASSKEY_REQ message has to be sent to the AMB2623 central including the passkey of the peripheral. The permissible characters of the passkey are ranging from 0x30 to 0x39 (both included) which are ASCII numbers (0-9). Format:
Start signal Command Length 0x02 0x0D 0x06 0x00 Pass key 6 Bytes CS 1 Byte Response (CMD_PASSKEY_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x4D 0x01 0x00 1 Byte 1 Byte Status:
0x00: Pass key accepted and pass key request answered 0x01: Operation failed, due to invalid pass key 0xFF: Operation not permitted AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 54 7.2.10 CMD_PASSKEY_IND Depending on the security settings of the peripheral, a passkey has to be entered on the central side to authenticate the central device. When such a pass key authentication request is received on the central side this CMD_PASSKEY_IND message is send to the host. In this case, the passkey has to be entered using the CMD_PASSKEY_REQ to successfully nish the connection procedure. Format:
Start signal Command Length Status BTMAC CS 0x02 0x8D 0x07 0x00 1 Byte 6 Bytes 1 Byte Status:
0x00: Success 7.2.11 CMD_GETBONDS_REQ This command requests the MAC addresses of all bonded devices. Format:
Start signal Command 0x02 0x0F Length CS 0x00 0x00 0x0D Response (CMD_GETBONDS_CNF):
Start signal Command | 0x40 0x02 0x4F Length Status 2 Bytes 1 Byte
#Devices Payload CS 1 Byte
(Length - 2) Bytes 1 Byte The Payload sequentially lists the data of the bonded #Devices devices.
#Devices times the following telegram (see example below). It consists of Bond_ID BTMAC 2 Bytes 6 Bytes Status:
0x00: Request successfully processed 0x01: Operation failed 0xFF: Operation not permitted If there are too many devices, the response of the CMD_GETBONDS_REQ is split into several CMD_GETBONDS_CNF messages. 7.2.11.1 Example 1 Request for the bonding data of the devices in database. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 55 Start signal Command 0x02 0x0F Length CS 0x00 0x00 0x0D Response:
Start signal Command
| 0x40 Length Status
#Devices Payload 0x02 0x4F 0x12 0x00 0x00 0x02 0x00 0x00 0x82 0x5C 0xA7 0xE2 0x87 0xD0 0x01 0x00 0x01 0x00 0x00 0xDA 0x18 0x00 CS 0x53 Two devices have been bonded before:
Device 1 (Bond_ID 0x0000) with FS_BTMAC 0x82 0x5C 0xA7 0xE2 0x87 0xD0 Device 2 (Bond_ID 0x0001) with FS_BTMAC 0x01 0x00 0x00 0xDA 0x18 0x00 7.2.12 CMD_DELETEBONDS_REQ This command removes the bonding information of all or single bonded devices. Enter Bond_ID to remove the bonding data of a certain Bond_ID. To remove all bonding data, choose Length equals 0 and leave Bond_ID empty. Format:
Start signal Command 0x02 0x0E Response (CMD_DELETEBONDS_CNF):
Length 2 Bytes 0 or 2 Bytes 1 Byte Bond_ID CS Start signal Command | 0x40 Length Status CS 0x02 0x4E 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request successfully processed 0x01: Operation failed (e.g. Bond_ID not found) 0xFF: Operation not permitted 7.2.12.1 Example 1 Request to remove all bonding data. Start signal Command 0x02 0x0E Length CS 0x00 0x00 0x0C Response:
AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 56 Start signal Command | 0x40 Length 0x02 0x4E 0x01 0x00 Status 0x00 CS 0x4D Successfully removed all bonding information. 7.2.12.2 Example 2 Request to remove the bonding of the device corresponding to Bond_ID 0. Start signal Command 0x02 0x0E Response:
Length CS 0x02 0x00 0x00 0x00 0x0E Bond_ID Start signal Command | 0x40 Length 0x02 0x4E 0x01 0x00 Status 0x00 CS 0x4D Successfully removed the bonding information. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 57 7.3 Transmit and receive data 7.3.1 CMD_DATA_REQ This command provides the simple data transfer between two connected modules. Trans-
mission takes place to the previously connected device(s). This command is suitable for transmission for a point-to-point connection. The number of payload data Bytes is negotiat-
ed during the connection phase. It can be maximal 243 Bytes, but at least 19 Bytes. When the data is processed by the module a CMD_DATA_CNF is output by the UART. Addition-
ally a CMD_TXCOMPLETE_RSP will follow as soon as the data has been sent. The receiving AMB2623 will get a CMD_DATA_IND message containing the transmitted pay-
load data. Format:
Start signal Command 0x02 0x04 Length 2 Bytes Length Bytes 1 Byte Payload CS Response (CMD_DATA_CNF):
Start signal Command | 0x40 0x02 0x44 Status:
0x00: Request received, will send data now Length 2 Bytes Length Bytes 1 Byte Status CS 0x01 + 0xXX: Operation failed + 0xXX maximum payload size (if it was exceeded) 0xFF: Operation not permitted 7.3.2 CMD_TXCOMPLETE_RSP This command is output to the UART as soon as the data, which was requested by a CMD_DATA_REQ has been transmitted successfully. Format:
Start signal Command Length Status CS 0x02 0xC4 0x01 0x00 1 Byte 1 Byte Status:
0x00: Data transmitted successfully 0x01: Data transmission failed AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 58 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 twos complement notation. Format:
Start signal Command 0x02 0x84 Length BTMAC RSSI 2 Bytes 6 Bytes 1 Byte (Length - 7) Bytes 1 Byte Payload CS 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 AMB2623 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 eld empty will remove the data from the scan response packet. The number of payload data Bytes is limited to 19. Format:
Start signal Command 0x02 0x0C Response (CMD_SETBEACON_CNF):
Length 2 Bytes Length Bytes 1 Byte Payload CS 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 twos complement notation. Format:
AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 59 Start signal Command 0x02 0x8C Length BTMAC RSSI 2 Bytes 6 Bytes 1 Byte (Length - 7) Bytes 1 Byte Payload CS AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 60 7.4 Conguring the module and modifying the device settings It is strongly recommended to have identical settings on all devices, which have to open a connection with each other or are to be used in Beacon mode. The modules parameters are stored in ash, but have a local copy in RAM. The ash param-
eters can be modied by the CMD_SET_REQ, read by the CMD_GET_REQ and retain their content even when resetting the module. 7.4.1 CMD_SET_REQ This command enables direct manipulation of the parameters in the modules settings in ash. The respective parameters are accessed by means of the corresponding settings in-
dex, which can be found in Table 17. Parameters of 2 or more Bytes have to be transferred with the LSB rst unless noted differ-
ently in the corresponding description. The modied parameters only take effect after a restart of the module. This may be done by a CMD_RESET_REQ if the module does not restart automatically. The ash memory used to store these settings has a limited count of write cycles. Try to avoid performing periodic CMD_SET_REQ as each command will use one write cycle. The validity of the specied parameters is not veried. result in device malfunction!
Incorrect values can To save the parameters in the ash memory of the module, the particular mem-
ory segment must rst be ushed entirely and then restored from RAM. If a reset occurs during this procedure, the entire memory area may be corrupted
(e.g. due to supply voltage uctuations). Recommendation:
the module with CMD_GET_REQ and only then apply a CMD_SET_REQ if required to avoid unnec-
essary ash cycles. First, verify the conguration of Format:
AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 61 Start signal Command 0x02 0x11 Length Settings index 2 Bytes 1 Byte Parameter CS
(Length - 1) Bytes 1 Byte Response (CMD_SET_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x51 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, settings set successfully 0x01: Operation failed due to invalid parameter 0x04: Serious error, when writing ash. Try to factory reset or re-ash the device 0xFF: Operation not permitted 7.4.1.1 Example 1 Setting the advertising time RF_AdvertisingTimeout to 180 seconds. Start signal Command Length Settings index Parameter CS 0xB4 0x00 0xA3 0x02 0x11 0x03 0x00 0x07 Response:
Start signal Command | 0x40 Length 0x02 0x51 0x01 0x00 Status CS 0x00 0x52 Setting was set successfully. 7.4.1.2 Example 2 Setting the static pass key RF_StaticPasskey to "123456". Start signal Command Length Settings index 0x02 0x11 0x07 0x00 0x12 CS 0x31 0x32 0x33 0x34 0x35 0x36 0x01 Parameter Response:
Start signal Command | 0x40 Length 0x02 0x51 0x01 0x00 Status CS 0x00 0x52 Setting was set successfully. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 62 7.4.2 CMD_GET_REQ This command can be used to query individual setting parameters in ash. The respective parameters are accessed by means of the corresponding settings index, which can be found in Table 17. Parameters of 2 or more Bytes have to be transferred with the LSB rst unless noted differ-
ently in the corresponding description. Read access to the memory area outside the setting is blocked. Format:
Start signal Command Length Settings index CS 0x02 0x10 0x01 0x00 1 Byte 1 Byte Response (CMD_GET_CNF):
Start signal Command | 0x40 0x02 0x50 Status:
Length Status 2 Bytes 1 Byte (Length - 1) Bytes 1 Byte Parameter CS 0x00: Request received, read out of setting successful 0x01: Operation failed 0xFF: Operation not permitted 7.4.2.1 Example 1 Request the current static pass key RF_StaticPasskey. Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x01 0x12 Response: The current RF_StaticPasskey in ash is "123123" (0x31 0x32 0x33 0x31 0x32 0x33). Start signal Command | 0x40 Length 0x02 0x50 0x07 0x00 Status 0x00 CS 0x31 0x32 0x33 0x31 0x32 0x33 0x55 Parameter Setting was read successfully. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 63 7.5 Manage the device state 7.5.1 CMD_GETSTATE_REQ This command returns the current state of the module. Please refer to chapter 5 for details on the states of the module. Format:
Start signal Command 0x02 0x01 Length CS 0x00 0x00 0x03 Response (CMD_GETSTATE_CNF):
Start signal Command
| 0x40 0x41 Length Module role 2 Bytes 1 Byte Module actions 1 Byte More info CS
(Length - 2) Bytes 1 Byte 0x02 Module role:
0x00: No role 0x01: Peripheral 0x02: Central 0x10: Direct test mode (DTM) Other: Reserved Module action:
0x00: No action 0x01: Idle (advertising) 0x02: Scanning 0x03: Connected (More info is the 6 Bytes FS_BTMAC address of the connected device) 0x04: Sleep (system-off mode) 0x05: Direct test mode 7.5.1.1 Example 1 Get the current state of the module. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 64 Start signal Command 0x02 0x01 Length CS 0x00 0x00 0x03 Response:
Start signal Command
| 0x40 Length Module role 0x02 0x41 0x08 0x00 0x02 Module actions 0x03 More info 0x11 0x00 0x00 0xDA 0x18 0x00 CS 0x99 The module is connected to another module with FS_BTMAC 0x11 0x00 0x00 0xDA 0x18 0x00. 7.5.2 CMD_RESET_REQ This command triggers a software reset of the module. Format:
Start signal Command 0x02 0x00 Length CS 0x00 0x00 0x02 Response (CMD_RESET_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x40 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, will perform reset now 0x01: Operation failed 0xFF: Operation not permitted 7.5.3 CMD_SLEEP_REQ This command is used to start the system-off mode (ACTION_SLEEP). After entering this mod-
e, the module has to be woken up using the WAKE_UP pin (apply a low signal at this for at least 5ms and release it to high again) before any other action can be performed. The UART interface as well as the BLE interface are shut down in this mode. For more details, please see also chapter 5.2. Format:
Start signal Command 0x02 0x02 Length CS 0x00 0x00 0x00 Response (CMD_SLEEP_CNF):
AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 65 Start signal Command | 0x40 Length Status CS 0x02 0x42 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, will go to sleep now 0x01: Operation failed 0xFF: Operation not permitted Please note that the WAKE_UP pin has a second function. If the mod-
ule is not in ACTION_SLEEP mode and the UART was disabled using the CMD_UARTDISABLE_REQ, the UART can be re-enabled by applying falling edge, holding the line low for at least 10ms before applying a rising edge and holding it high for at least 10ms. In this case the module answers with a CMD_UARTENABLE_IND message. 7.5.4 CMD_SLEEP_IND This indication is send by the module when the RF_AdvertisingTimeout has expired without a connection to the module. Format:
Start signal Command Length 0x02 0x82 0x01 0x00 Status 0x00 CS 1 Byte Status:
0x00: Advertising timeout detected, will go to sleep now 7.5.5 CMD_FACTORYRESET_REQ This command triggers a factory reset of the module. First, the default User Settings are restored, then the module is reset. Format:
Start signal Command 0x02 0x1C Length CS 0x00 0x00 0x1E Response (CMD_FACTORYRESET_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x5C 0x01 0x00 1 Byte 1 Byte Status:
AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 66 0x00: Request received, will perform factory reset now 0x01: Operation failed 0xFF: Operation not permitted To save the parameters in the ash memory of the module, the particular mem-
ory segment must rst be ushed entirely and then restored from RAM. If a reset occurs during this procedure (e.g. due to supply voltage uctuations), the entire memory area may be destroyed. During start-up of the device, the user settings memory is checked for consis-
tency. In case of inconsistency (e.g. the memory was erased) the device will perform a factory reset. This command also removes all bonding data. 7.5.6 CMD_UARTDISABLE_REQ It will be re-enabled when the module This command disables the UART of the module. has to send data to the host (e.g. data was received via RF or a state is indicated) or if the WAKE_UP pin is used (apply a falling edge, hold low for at least 10ms before applying a rising edge and hold high for at least 10ms). In this case, either the received data or a CMD_UARTENABLE_IND is transmitted by the module. Afterwards the UART will stay active until another CMD_UARTDISABLE_REQ or CMD_SLEEP_REQ or a timer triggered sleep event occurs. Format:
Start signal Command 0x02 0x1B Length CS 0x00 0x00 0x19 Response (CMD_UARTDISABLE_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x5B 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, will disable UART now 0x01: Operation failed 0xFF: Operation not permitted AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 67 We insistently recommend disabling the UART using this command only, if it is foreseeable that there will be no UART communication for several second-
s! Use cases could be during advertising phase to wait for connecting BLE devices or when broadcasting data via Beacons. Disabling the UART peripheral of the module results in a reduction of current consumption of about 1.15mA. Please note that the WAKE_UP pin has a second function. If the module is in ACTION_SLEEP mode, this pin wakes up the module by applying a low signal at this for at least 5ms and releasing it to high. In this case, the module answers with a CMD_GETSTATE_CNF. 7.5.7 CMD_UARTENABLE_IND This indication is shown when the UART of the module is re-enabled (after performing a CMD_UARTDISABLE_REQ followed by using the WAKE_UP pin). After receiving this message the UART can be used for any operation again. Format:
Start signal Command Length Status CS 0x02 0x9B 0x01 0x00 1 Byte 1 Byte Status:
0x00: UART has been re-enabled successfully 7.5.8 CMD_BOOTLOADER_REQ This command resets the module and starts the OTA bootloader. Please refer to chapter 12 on how to use the bootloader for a rmware update. Please note that you can only exit the bootloader mode by performing a hard-
ware reset using the respective pin. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 68 The bootloader mode will also be enabled if the rmware image is marked
"invalid" or if the BOOT pin logic level (set by the host) is set to start the bootloader during start-up of the module. Format:
Start signal Command 0x02 0x1F Length CS 0x00 0x00 0x1D Response (CMD_BOOTLOADER_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x5F 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, will start bootloader now 0x01: Operation failed 0xFF: Operation not permitted AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 69 7.6 Run the Bluetooth test modes The test modes "DTM" as specied by the Bluetooth SIG are dened in the Bluetooth Core specication v4.0 Volume 6. 7.6.1 CMD_DTMSTART_REQ This command restarts the module in direct test mode (DTM). When starting in DTM mode, a CMD_GETSTATE_CNF message follows which indicates that the test mode has been enabled successfully. Now the CMD_DTM_REQ can be used to start and stop various test modes. As soon as the module is reset, the DTM will be left again and normal operations can be performed. Performing a reset will leave the DTM and restart the module in the ACTION_IDLE state. Format:
Start signal Command 0x02 0x1D Length CS 0x00 0x00 0x1F Response (CMD_DTMSTART_CNF):
Start signal Command | 0x40 Length Status CS 0x02 0x5D 0x01 0x00 1 Byte 1 Byte Status:
0x00: Request received, will enable the direct test mode now 0x01: Operation failed 0xFF: Operation not permitted 7.6.2 CMD_DTM_REQ This command starts and stops various test modes. To be able to run these test modes, the DTM has to be enabled rst using the CMD_DTMSTART_REQ. After a test has been started, it has to be stopped rst before a next test can be run. The default TX power value is 0 dBm, the allowed range is from -40 up to +4 dBm in steps of 4dB (see chapter 8.16). The valid range for Channel (or Vendor option in case of Vendor Command = Carrier Test) is 0. 39. Format:
Start signal Command Length Command code Channel /
Vendor option Length /
Vendor command Payload CS 0x02 0x1E 0x04 0x00 Command code:
1 Byte 1 Byte 1 Byte 1 Byte 1 Byte AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 70 0x00: DTM reset (note: this command does not perform a module reset. 0x01: Start RX test 0x02: Start TX test 0x03: Stop last test Payload:
0x00: Bit pattern PRBS9 0x01: Bit pattern 0x0F 0x02: Bit pattern 0x55 0x03: Vendor specic Payload = Vendor specic (0x00, 0x01 or 0x02) Length / Vendor Command:
Length of the packet to send Channel:
Frequency = (2402 + Channel * 2) MHz to be used for RX/TX Payload = Vendor specic (0x03) Length / Vendor Command:
0x00: Carrier test 0x02: Set transmission power Vendor option:
(dependent on used "Vendor command") Frequency = (2402 + [Vendor option] * 2) MHz or
[Vendor option] := TXPower (in twos complement notation) in steps of 4dB Length Status 2 Bytes 1 Byte 0-2 Bytes 1 Byte Result CS Response (CMD_DTM_CNF):
Start signal Command | 0x40 0x02 0x5E Status:
0x00: Request received 0x01: Operation failed 0x03: Busy 0xFF: Operation not permitted Result:
0x0000: Test success 0x0001: Test failed 0x8000 + n: Received n packets during RX test AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 71 See also the example in chapter 5.8. 7.6.2.1 Example: Transmission, 16 times 0x0F, channel 0 Start the transmission test on channel 0 (2402 MHz). The packets consist of 16 times 0x0F:
Start signal Command Length Command code Channel /
Vendor option Length /
Vendor command Payload CS 0x02 0x1E 0x04 0x00 Response:
0x02 0x00 0x10 0x01 0x0B Start signal Command | 0x40 Length 0x02 0x5E 0x03 0x00 Status 0x00 Result CS 0x00 0x00 0x5F Test started successfully. Now stop the test again. Start signal Command Length Command code Channel /
Vendor option Length /
Vendor command Payload CS 0x02 0x1E 0x04 0x00 Response:
0x03 0x00 0x00 0x01 0x0B Start signal Command | 0x40 Length 0x02 0x5E 0x03 0x00 Status 0x00 Result CS 0x80 0x00 0xDF Test stopped successfully and received 0 packets. 7.6.2.2 Example: Receiver, 0x0F, channel 0 Start the reception test on channel 0 (2402MHz) with Bit pattern 0x0F:
Start signal Command Length Command code Channel /
Vendor option Length /
Vendor command Payload CS 0x02 0x1E 0x04 0x00 Response:
0x01 0x00 0x00 0x01 0x18 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 72 Start signal Command | 0x40 Length 0x02 0x5E 0x03 0x00 Status 0x00 Result CS 0x00 0x00 0x5F Test started successfully. In between we started the transmission test on a second module. When we stop RX test now, we can count the received packets from the transmitting module. Start signal Command Length Command code Channel /
Vendor option Length /
Vendor command Payload CS 0x02 0x1E 0x04 0x00 Response:
0x03 0x00 0x00 0x01 0x0B Start signal Command | 0x40 Length 0x02 0x5E 0x03 0x00 Status 0x00 Result CS 0x0E 0x67 0x36 Test stopped successfully and received 0x0E67 (3687) packets. 7.6.2.3 Example: Transmission, carrier test, channel 0 Start the carrier test on channel 0 (2402MHz). We need to use a vendor specic command:
Start signal Command Length Command code Channel /
Vendor option Length /
Vendor command Payload CS 0x02 0x1E 0x04 0x00 Response:
0x02 0x00 0x00 0x03 0x19 Start signal Command | 0x40 Length 0x02 0x5E 0x03 0x00 Status 0x00 Result CS 0x00 0x00 0x5F See the previous example to stop the test again. 7.6.2.4 Example: Set TX power to -4 dBm Set the TX power to -4dBm (0xFC in twos complement notation):
AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 73 Start signal Command Length Command code Channel /
Vendor option Length /
Vendor command Payload CS 0x02 0x1E 0x04 0x00 Response:
0x02 0xFC 0x02 0x03 0xE7 Start signal Command | 0x40 Length 0x02 0x5E 0x03 0x00 Status 0x00 Result CS 0x00 0x00 0x5F See the previous example to stop the test again. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 74 7.7 Other messages 7.7.1 CMD_ERROR_IND This indication is shown when the module entered an error state. Format:
Start signal Command Length Status CS 0x02 0xA2 0x01 0x00 1 Byte 1 Byte Status:
0x01: UART_COMMUNICATION_ERROR The UART had a buffer overow. Thus, UART TX and RX was aborted and UART has restarted. Please restart module if UART is still malfunctioning. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 75 7.8 Message overview Short description Chapter CMD_DATA_REQ CMD_SLEEP_REQ CMD_RESET_REQ CMD_CONNECT_REQ CMD_GETSTATE_REQ CMD_DISCONNECT_REQ Start signal CMD Message name 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x00 0x01 0x02 0x04 0x06 0x07 0x09 CMD_SCANSTART_REQ 0x0A CMD_SCANSTOP_REQ 0x0B CMD_GETDEVICES_REQ 0x0C CMD_SETBEACON_REQ 0x0D CMD_PASSKEY_REQ 0x0E CMD_DELETEBONDS_REQ 0x0F 0x10 0x11 0x1A CMD_PHYUPDATE_REQ 0x1B CMD_UARTDISABLE_REQ 0x1C CMD_FACTORYRESET_REQ Perform a factory reset 0x1D CMD_DTMSTART_REQ 0x1E CMD_DTM_REQ 0x1F Reset the module Request the current module state Go to sleep Send data to the connected device Setup a connection with another device Close the connection Start scan Stop scan Request the scanned/detected devices Place data in scan response packet Respond to a pass key request Delete bonding information Read the MACs of bonded devices Read the module settings in ash Modify the module settings in ash Update the PHY Disable the UART Enable the direct test mode Start/stop a test of the direct test mode Switch to the bootloader CMD_BOOTLOADER_REQ CMD_GETBONDS_REQ CMD_GET_REQ CMD_SET_REQ 7.5.2 7.5.1 7.5.3 7.3.1 7.2.1 7.2.5 7.1.1 7.1.2 7.1.3 7.3.4 7.2.9 7.2.12 7.2.11 7.4.2 7.4.1 7.2.7 7.5.6 7.5.5 7.6.1 7.6.2 7.5.8 Table 10: Message overview: Requests AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 76 Short description Chapter CMD_DATA_CNF CMD_SLEEP_CNF CMD_RESET_CNF CMD_CONNECT_CNF CMD_GETSTATE_CNF CMD_DISCONNECT_CNF Start signal CMD Message name 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 Reset request received 0x40 Return the current module state 0x41 Sleep request received 0x42 Data transmission request received 0x44 Connection setup request received 0x46 Disconnection request received 0x47 Scan started 0x49 CMD_SCANSTART_CNF Scan stopped 0x4A CMD_SCANSTOP_CNF Output the scanned/detected devices 0x4B CMD_GETDEVICES_CNF Data is placed in scan response packet 0x4C CMD_SETBEACON_CNF Received the pass key 0x4D CMD_PASSKEY_CNF Deleted bonding information 0x4E CMD_DELETEBONDS_CNF Return the MAC of all bonded devices 0x4F Return the requested module ash settings 0x50 Module ash settings have been modied 0x51 Update Phy request received 0x5A CMD_PHYUPDATE_CNF Disable UART request received 0x5B CMD_UARTDISABLE_CNF 0x5C CMD_FACTORYRESET_CNF Factory reset request received 0x5D CMD_DTMSTART_CNF 0x5E CMD_DTM_CNF 0x5F Enable the direct test mode now Test of direct test mode started/stopped Will switch to bootloader now CMD_BOOTLOADER_CNF CMD_GETBONDS_CNF CMD_GET_CNF CMD_SET_CNF 7.5.2 7.5.1 7.5.3 7.3.1 7.2.1 7.2.5 7.1.1 7.1.2 7.1.3 7.3.4 7.2.9 7.2.12 7.2.11 7.4.2 7.4.1 7.2.7 7.5.6 7.5.5 7.6.1 7.6.2 7.5.8 Table 11: Message overview: Conrmations AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 77 Chapter 7.5.4 7.3.3 7.2.2 7.2.6 7.2.3 7.1.4 7.3.5 7.2.10 7.2.8 7.5.7 7.7.1 7.3.2 7.2.4 CMD_DATA_IND CMD_SLEEP_IND CMD_CONNECT_IND CMD_SECURITY_IND CMD_DISCONNECT_IND Start signal CMD Message name 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x02 0x82 0x84 0x86 0x87 0x88 0x8B CMD_RSSI_IND 0x8C CMD_BEACON_IND 0x8D CMD_PASSKEY_IND 0x9A CMD_PHYUPDATE_IND 0x9B CMD_UARTENABLE_IND 0xA2 0xC4 0xC6 CMD_ERROR_IND Short description State will be changed to ACTION_SLEEP Data has been received Connection established Disconnected Secured connection established Advertising package detected Received Beacon data Received a pass key request PHY has been updated UART was re-enabled Entered error state Data has been sent CMD_TXCOMPLETE_RSP CMD_CHANNELOPEN_RSP Channel open, data transmission possible Table 12: Message overview: Indications AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 78 8 UserSettings - Module conguration values The settings described in this chapter are stored permanently in the modules ash memo-
ry. Depending on their corresponding permissions, their current values can be read out by the CMD_GET_REQ command or modied by the CMD_SET_REQ command. To do so the cor-
responding settings index is used, which can be found in the primary table of each setting description. These settings cannot be accessed (read, write) from the Peripheral only mode introduced in a follow-up chapter. The validity of the specied parameters is not veried. result in device malfunction. Incorrect values can After the modication of the non-volatile parameters, a reset will be necessary for the changes to be applied. 8.1 FS_DeviceInfo: Read the chip type and OS version Settings index Designation Permissible values Default value Permissions Number of Bytes 15 FS_DeviceInfo
-
-
read 12 This setting contains information about the chip type and the OS version. The value of FS_DeviceInfo is composed of the following 4 sub parameters (ordered by appearance in the response):
OS version Build code Package variant Chip ID 4 Bytes 4 Bytes 2 Bytes 2 Bytes OS version:
0x00A8 : Softdevice S132 6.0.0 Build code:
ASCII coded (see the following table 13) Package variant:
0x2000: QFN AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 79 0x2002: CI Chip ID:
0x00052832 : nRF52832 Packet variant QF QF CI Build code Package Flash size RAM size AAB0 ABB0 AABA, AAB0, AAB1, AAE0, AAE1 QFN48 QFN48 WLCSP 512 kB 256 kB 512 kB 64 kB 32 kB 64 kB Table 13: nRF52832 IC revision overview 8.1.1 Example 1 Request the device info of the module using CMD_GET_REQ with settings index 15 Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x0F CS 0x1C Response CMD_GET_CNF: Successfully read out the device info (with Byte order changed to MSB rst):
OS version = 0x0088 (Softdevice S132 2.0.1) Build code = 0x41414241 (AABA) Package variant = 0x2002 (CI) Chip ID = 0x00052832 Please note that LSB is transmitted rst in case of parameters with more than 1 Byte length. Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x0D 0x00 0x00 0x88 0x00 0x41 0x42 0x41 0x41 0x02 0x20 0x32 0x28 0x05 0x00 CS 0xE9 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 80 8.2 FS_FWVersion: Read the rmware version Settings index Designation Permissible values Default value Permissions Number of Bytes 1 FS_FWVersion
-
-
read 3 This setting contains the rmware version of the module. 8.2.1 Example 1 Request the rmware version of the module using CMD_GET_REQ with settings index 1 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x12 0x01 Response CMD_GET_CNF: Successfully read out the rmware version, for this example it is 0x000001 so "1.0.0" (with the parameter reverted to MSB rst). Start signal Command | 0x40 Length 0x02 0x50 0x04 0x00 Status 0x00 Parameter 0x00 0x00 0x01 CS 0x57 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 81 8.3 FS_MAC: Read the MAC address Settings index Designation Permissible values Default value Permissions Number of Bytes 3 FS_MAC
-
-
read 6 This setting contains the unique MAC address of the module. 8.3.1 Example 1 Request the MAC address of the module using CMD_GET_REQ with settings index 3 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x10 0x03 Response CMD_GET_CNF: Successfully read out the MAC address 0x55 0x93 0x19 0x6E 0x5B 0x87 Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x07 0x00 0x00 0x55 0x93 0x19 0x6E 0x5B 0x87 CS 0x38 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 82 8.4 FS_BTMAC: Read the BLE conform MAC address Settings index Designation Permissible values Default value Permissions Number of Bytes 4 FS_BTMAC
-
-
read 6 This setting contains the BLE conform MAC address of the module. The FS_BTMAC is intro-
duced and used to nd the respective device on the RF-interface. It consists of the company ID 0x0018DA followed by the FS_SerialNumber of the module. Please note that LSB is transmitted rst in all commands. 8.4.1 Example 1 Request the Bluetooth-conform MAC address of the module using CMD_GET_REQ with settings index 4 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x17 0x04 Response CMD_GET_CNF: Successfully read out the BLE conform MAC address 0x11 0x00 0x00 0xDA 0x18 0x00. Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x07 0x00 0x00 0x11 0x00 0x00 0xDA 0x18 0x00 CS 0x86 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 83 8.5 FS_SerialNumber: Read the serial number of the module Settings index Designation Permissible values Default value Permissions Number of Bytes 16 FS_SerialNumber
-
-
read 3 This setting contains the serial number of the module. 8.5.1 Example 1 Request the serial number of the module using CMD_GET_REQ with settings index 16 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x03 0x10 Response CMD_GET_CNF: Successfully read out the serial number, it is 0.0.11 Start signal Command | 0x40 Length 0x02 0x50 0x04 0x00 Status 0x00 Parameter 0x11 0x00 0x00 CS 0x57 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 84 8.6 RF_DeviceName: Modify the device name Settings index Designation 2 RF_DeviceName Permissible values See description Default value Permissions Number of Bytes
"A2623"
read/write 1-32 This parameter is using MSB rst notation. This parameter determines the name of the module, which is used in the advertising packets as well as in the Generic Access Prole (GAP). The permissible characters are in the range of 0x20 - 0x7E which are special characters (see ASCII table), alphabetic characters (a-z and A-Z), numbers (0-9) and whitespace. The maximum size of the device name that ts into an advertising packet is 5 Bytes. Thus longer device names will be shortened to 5 Bytes and declared as
"Shortened Local Name" in the advertising packet. The full device name can then be found in the GAP. 8.6.1 Example 1 Set the device name of the module to 0x4D 0x4F 0x44 0x20 0x31 = "MOD 1" using CMD_SET_REQ with settings index 2. Start signal Command Length Settings index Parameter 0x02 0x11 0x06 0x00 0x02 0x4D 0x4F 0x44 0x20 0x31 CS 0x40 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.6.2 Example 2 Request the device name of the module using CMD_GET_REQ with settings index 2:
Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x11 0x02 Response CMD_GET_CNF: Successfully read out the module as 0x41 0x32 0x36 0x32 0x33 =
"A2623". AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 85 Start signal Command | 0x40 Length 0x02 0x50 0x06 0x00 Status 0x00 Parameter CS 0x41 0x32 0x36 0x32 0x31 0x12 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 86 8.7 RF_StaticPasskey: Modify the static passkey Settings index Designation 18 RF_StaticPasskey Permissible values See description Default value Permissions Number of Bytes
"123123"
read/write 6 This setting determines the static pass key of the peripheral device used for authentication. If the static pass key security mode is enabled by the peripheral, this key must be entered in the central device. In case of an AMB2623 central, the command to enter this pass key during connection setup is the CMD_PASSKEY_REQ. The permissible characters are ranging from 0x30 to 0x39 (both included) which are ASCI-
I numbers (0-9). This is due to the fact that mobile phones prefer numbers only for the passkey. 8.7.1 Example 1 Set the static pass key of the module to 0x31 0x32 0x33 0x34 0x35 0x36 = "123456" using CMD_SET_REQ with settings index 18 Start signal Command Length Settings index Parameter 0x02 0x11 0x07 0x00 0x12 0x31 0x32 0x33 0x34 0x35 0x36 CS 0x01 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.7.2 Example 2 Request the static pass key of the module using CMD_GET_REQ with settings index 18 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x01 0x12 Response CMD_GET_CNF:Successfully read out the key as 0x31 0x32 0x33 0x34 0x35 0x36 =
"123456"
Start signal Command | 0x40 Length 0x02 0x50 0x07 0x00 Status 0x00 CS 0x31 0x32 0x33 0x34 0x35 0x36 0x52 Parameter AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 87 8.8 RF_SecFlags: Modify the security settings Settings index Designation 12 RF_SecFlags Permissible values See description Default value Permissions Number of Bytes 0 read/write 1 This 8-Bit eld congures security settings of the module. Chapter 5.4 contains further information about secure connections. When connecting from an AMB2623 to another AMB2623 , be sure that the same security mode is used. When connecting from a foreign device to an AMB2623 , the peripheral (AM-
B2623 ) determines the minimum security level needed for communication. So congure the RF_SecFlags of the peripheral to set the desired security level. When updating this user setting (like enabling bonding or changing the se-
curity mode) please remove all existing bonding data using the command CMD_DELETEBONDS_REQ. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 88 Bit no. Description 0x2 0x0 No security Just works Level 1.2 Security mode conguration. Depending on its value, different modes are chosen when setting up a secure connection. In rmware version 2.1.0 and newer the peripheral decides which is the minimum security level to access its data. Data is transmitted without authentication and encryption. Each time a connection is established, new random keys are exchanged in advance to use them for data encryption. This mode uses the "just works" method. For authentication, the RF_StaticPasskey is used. If the peripheral uses this method, the central device must enter the correct passkey to nalize the connection. Reserved others SECFLAGS_BONDING_ENABLE: If this Bit is set, bonding is enabled when using one of the pairing methods. Bonding data of up to 32 devices will be stored in the ash. Static pass key Level 1.3 0x3 2 : 0 3 15 : 4 Reserved 8.8.1 Example 1 Table 14: Security conguration ags Set the security ags to 0x0B, to use the static passkey pairing and with bonding enabled, using CMD_SET_REQ with settings index 12 Start signal Command Length Settings index 0x02 0x11 0x02 0x00 0x0C Parameter 0x0B CS 0x16 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.8.2 Example 2 Request the security ags of the module using CMD_GET_REQ with settings index 12 Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x0C CS 0x1F Response CMD_GET_CNF: Successfully read out the value 2, which means that the just works pairing mode is enabled. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 89 Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x52 0x02 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 90 8.9 RF_SecFlagsPerOnly: Modify the security settings (Peripheral only mode) Settings index Designation 44 RF_SecFlagsPerOnly Permissible values See description Default value Permissions Number of Bytes 11 read/write 1 Please refer to the setting RF_SecFlags for more details. 8.9.1 Example 1 Set the security ags to 0x02 to use the just works pairing, using CMD_SET_REQ with settings index 44 Start signal Command Length Settings index 0x02 0x11 0x02 0x00 0x2C Parameter 0x02 CS 0x3F Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.9.2 Example 2 Request the security ags of the module using CMD_GET_REQ with settings index 44 Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x2C CS 0x3F Response CMD_GET_CNF: Successfully read out the value 2, which means that the just works pairing mode is enabled. Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x52 0x02 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 91 8.10 RF_ScanFlags: Modify the scan behavior Settings index Designation 13 RF_ScanFlags Permissible values See description Default value Permissions Number of Bytes 0 read/write 1 This 8-Bit eld congures the scan behavior of the module. To use multiple settings, add the Bit numbers and choose the result as value for RF_ScanFlags. Bit no. Description 0 If this Bit is set, an active scan is performed when using CMD_SCANSTART_REQ. In this case, after receiving an advertising packet a scan request is send to the advertising module that returns a scan response containing additional information. For the communication of AMB2623 modules, active scanning is only needed when using Beacons. In this case, it is enabled automatically by the rmware. Please note that active scanning increases the current consumption. 15 : 1 Reserved 8.10.1 Example 1 Table 15: Scan conguration ags Set the scan ags to 0x01 to enable active scanning using CMD_SET_REQ with settings in-
dex 13 Start signal Command Length Settings index 0x02 0x11 0x02 0x00 0x0D Parameter 0x01 CS 0x1D Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.10.2 Example 2 Request the scan ags of the module using CMD_GET_REQ with settings index 13 Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x0D CS 0x1E Response CMD_GET_CNF: Successfully read out the value 0, which means that active scan is disabled. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 92 Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x50 0x00 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 93 8.11 RF_BeaconFlags: Interprete the advertising data Settings index Designation 14 RF_BeaconFlags Permissible values See description Default value Permissions Number of Bytes 0 read/write 1 This 8-Bit eld enables/disables the reception of Beacons. To use multiple settings, add the Bit numbers and choose the result as value for RF_BeaconFlags. Bit no. Description Enable/disable the reception of Beacons. To avoid too much trafc on the UART, we recommend to use the ltered version. 0x0 Reception of Beacons disabled. Receive all Beacons from AMB2623 devices in range. Each received packet is interpreted and output by the UART. In this case, active scanning is performed which increases the current consumption. To decrease the work load of the receiving module, use a sufciently high UART baud rate at the receiving device and slow advertising intervals at the sending devices. Same as 0x1 plus additional lter. This lter discards redundant packets that contain the same content. Reserved. 0x1 1 : 0 0x3 others 2 If this Bit is set, a CMD_RSSI_IND message is output each time when an advertising packet with AMBER SPP-like UUID is received. This feature can be used to realize a position sensing application, since the CMD_RSSI_IND contains the current TX power level and the current RSSI value besides the FS_BTMAC of the sending device. To decrease the work load of the receiving module, please use a sufciently high UART baud rate at the receiving device and slow advertising intervals at the sending devices. 15 : 3 Reserved. Table 16: Beacon conguration ags The internal database of the module may host the advertising data of 25 differ-
ent devices. If the data base is full, the oldest entry is removed. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 94 To avoid too much trafc the usage of slow advertising intervals is recommend-
ed. 8.11.1 Example 1 Set the Beacon ags to 0x04 using CMD_SET_REQ with settings index 14. Thus when an advertising packet with AMBER SPP-like UUID is received, a CMD_RSSI_IND message is printed. Start signal Command Length Settings index 0x02 0x11 0x02 0x00 0x0E Parameter 0x04 CS 0x1B Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.11.2 Example 2 Request the Beacon ags of the module using CMD_GET_REQ with settings index 14 Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x0E CS 0x1D Response CMD_GET_CNF: Successfully read out the value 3, which means that the reception of Beacons is enabled and double packets are ltered by the module. Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x53 0x03 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 95 8.12 RF_AdvertisingTimeout: Modify the advertising timeout Settings index Designation 7 RF_AdvertisingTimeout Permissible values 0 (innite),1 -
650 Default value Permissions Number of Bytes 0 read/write 2 This parameter denes the time in seconds after which the advertising of the module stops. If no peer connects before this timeout, advertising stops and the module goes to system-off mode. If the RF_AdvertisingTimeout is set to 0, the module advertises innitely. To ensure that the module sends a sufcient amount of advertising packets per RF_AdvertisingTimeout, please also check the RF_ScanTiming parameter, which denes the frequency of advertising packets. 8.12.1 Example 1 Set the advertising timeout parameter to 0x00 0xB4 (180s) using CMD_SET_REQ with settings index 7. Start signal Command Length Settings index 0x02 0x11 0x03 0x00 0x07 Parameter 0xB4 0x00 CS 0xA3 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.12.2 Example 2 Request the advertising timeout of the module using CMD_GET_REQ with settings index 7 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x14 0x07 Response CMD_GET_CNF: Successfully read out the value 0x00 0x00 = 0s, which indicates indenite advertising. Start signal Command | 0x40 Length 0x02 0x50 0x03 0x00 Status Parameter CS 0x00 0x00 0x00 0x51 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 96 8.13 RF_ScanFactor: Modify the scan factor Settings index Designation Permissible values Default value Permissions Number of Bytes 10 RF_ScanFactor 1 - 10 2 read/write 1 This parameter denes the factor between the scan window and the scan interval. See RF_ScanTiming for more information. Example: Lets assume that the scan window is 50ms, the RF_ScanFactor is 3, then the module scans for 50ms on a xed channel, enters a suspend mode (system-on mode) for 100ms (350ms - 50ms), switches the channel, again scans for 50ms and so on. The larger the RF_ScanFactor, the less time the module scans and thus the less power is consumed, but also the more difcult it is to detect other BLE devices on air. 8.13.1 Example 1 Set the scan factor to 0x03 using CMD_SET_REQ with settings index 10. Start signal Command Length 0x02 0x11 0x02 0x00 Settings index Parameter CS 0x18 0x0A 0x03 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.13.2 Example 2 Request the scan factor of the module using CMD_GET_REQ with settings index 10 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x19 0x0A Response CMD_GET_CNF: Successfully read out the value 2. Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x52 0x00 0x02 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 97 8.14 RF_ScanTiming: Modify the scan timing Settings index Designation Permissible values Default value Permissions Number of Bytes 9 RF_ScanTiming 0 - 5 1 read/write 1 The RF_ScanTiming enables the possibility to congure the timing behavior of the modules RF interface during advertising and scanning state. Using this parameter several predened congurations can be chosen, which include timing parameters, such as the frequency of advertising packets and the length of a scan window. The choice of the RF_ScanTiming primarily affects the latency of device detection on air as well as the current consumption. The lower the RF_ScanTiming, the faster the modules can nd each other for communication, but also the more power will be consumed. RF_ScanTiming Advertising interval [ms]
Scan window [ms]
Scan interval [ms]
Connection setup timeout [s]
0 20 25 2 41 31 1 40 250 1000 5000 50 312 1250 6250 51 10240 10240 Dened by the RF_ScanFactor. 1 2 2 5 20 35 Low Current consumption High
. Further information:
In ACTION_SCANNING mode, the scan interval denes the time after which the module switches channel to detect other BLE devices in range. See also RF_ScanFactor. In ACTION_SCANNING mode, the scan window denes the section of the scan interval, where the module is scanning. During the remaining time, the module enters a sus-
pend mode (system-on mode). See also RF_ScanFactor. In ACTION_IDLE mode, the advertising interval denes the time after which the module In between, the module enters a suspend periodically sends its advertising packet. mode (system-on mode). The connection setup timeout denes the time after which a connection request has to be answered by the peripheral. Please ensure that all members of a network support the same advertising and scan timing parameters. 1Mainly suitable for transmitting data using Beacons without consuming much energy. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 98 To ensure that the module is allowed to send a sufcient amount of advertising packets, please also check the RF_AdvertisingTimeout parameter. 8.14.1 Example 1 Set the scan timing parameter to 0x00 using CMD_SET_REQwith settings index 9. Start signal Command Length 0x02 0x11 0x02 0x00 Settings index Parameter CS 0x18 0x09 0x00 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.14.2 Example 2 Request the scan timing parameter of the module using CMD_GET_REQ with settings index 9 Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x09 CS 0x1A Response CMD_GET_CNF: Successfully read out the value 4. Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x54 0x04 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 99 8.15 RF_ConnectionTiming: Modify the connection timing Settings index Designation Permissible values Default value Permissions Number of Bytes 8 RF_ConnectionTiming 0 - 6 1 read/write 1 The RF_ConnectionTiming enables the possibility to congure the timing behavior of the modules RF interface during an established connection. Using this parameter several pre-
dened congurations can be chosen, which include the minimum and maximum connection interval, as well as the connection supervision timeout. The choice of the RF_ConnectionTiming primarily determines how rapidly the connection is established and data is transmitted. The lower the RF_ConnectionTiming, the more fre-
quently the connected devices communicate with each other and thus, the more power is consumed. RF_ConnectionTiming Minimum connection interval [ms]
Maximum connection interval [ms]
Connection supervision timeout [s]
Maximum throughput1
[kB/s]
0 8 30 4 1 20 75 4 2 50 3 4 5 200 750 2000 250 1000 2250 4000 4 8 25 15
-
6 8 8 4 Up to 10.4 Up to 8 Up to 3.2 Up to 1 Current consumption High
. Low High Further information:
The minimum and maximum connection interval parameters specify the borders of the connection interval as determined in the negotiation procedure between the central and the peripheral during connection setup. The connection interval denes the frequen-
cy of communication during connection setup and data transmission. If an AMB2623 module A (central) connects to an AMB2623 module B (peripheral), the connection interval settings of the central are used for connection setup. If both modules have different connection interval settings the peripheral requests the central to accept the peripherals settings after 5s. The central accepts these settings, and thus the periph-
erals connection interval is used. If now another BLE device (e.g. a smart phone) connects as central to an AMB2623 module (peripheral) and the connection interval settings do not coincide, the AMB2623 requests the smart phone to accept its settings after 5s. If the cell phone does not ac-
cept the settings, it will be requested a further 3 times with a delay of 10s. If the peripherals settings request have been rejected in all cases the connection will be shut down. If the smart phone itself requests to update the connection interval of the 1Measured with 921600 Baud UART baud rate, enabled ow control and payload size of 243Bytes between two AMB2623 modules in command mode. Please note that data transmission to/from mobile phones does not achieve this speed due to old mobile phone chips and BLE stacks. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 100 AMB2623 , the module accepts the request. Reversely, if an AMB2623 (central) con-
nects to another BLE device (peripheral) and the connection interval settings do not coincide, the AMB2623 accepts all requests of the peripheral to update the connection parameter settings. The connection supervision timeout denes the time after which an already established connection is considered as lost, when no further communication has occurred. Please ensure that all members (AMB2623 , cell phones and other BLE de-
vices) of a network use the same connection timing parameters to avoid con-
nection problems and changes of the connection interval during an opened connection. The minimal value of the minimum connection interval that is supported by iOS is 30ms!
8.15.1 Example 1 Set the connection timing parameter to 0x00 using CMD_SET_REQ with settings index 8. Start signal Command Length 0x02 0x11 0x02 0x00 Settings index Parameter CS 0x19 0x08 0x00 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.15.2 Example 2 Request the connection timing parameter of the module using CMD_GET_REQ with settings index 8 Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x08 CS 0x1B Response CMD_GET_CNF: Successfully read out the value 1. Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x51 0x01 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 101 8.16 RF_TXPower: Modify the output power Settings index Designation 17 RF_TXPower Permissible values See description Default value Permissions Number of Bytes 4 read/write 1 This setting determines the output power in dBm of the module. The value has to be entered in hexadecimal and as twos complement. The permissible values are listed in the following table. Permissible values
-30
-16
-20
-40
-12
-8
-4 0
+4 0xD8 0xE2 0xEC 0xF0 0xF4 0xF8 0xFC 0x00 0x04 Decimal [dBm]
Twos complemen-
t,hexadecimal 8.16.1 Example 1 Set the output power of the module to -8 dBm, which is 0xF8 in twos complement notation, using CMD_SET_REQ with settings index 17 Start signal Command Length Settings index Parameter 0x02 0x11 0x02 0x00 0x11 0xF8 CS 0xF8 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.16.2 Example 2 Request the output power of the module using CMD_GET_REQ with settings index 17 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x02 0x11 Response CMD_GET_CNF: Successfully read out the value 0x04 = 4dBm Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x54 0x04 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 102 8.17 RF_SPPBaseUUID: Congure the SPP base UUID Settings index Designation 26 RF_SPPBaseUUID Permissible values See description Default value Permissions Number of Bytes 0x6E400000C352 11E5953D0002 A5D5C51B read/write 16 The AMBER SPP-like prole consists of the 16 Bytes base UUID 0x6E40xxxx-C352-11E5-
953D-0002A5D5C51B plus the 2 Bytes UUIDs for the underlying characteristics:
Characteristic Primary service TX_CHARACTERISTIC RX_CHARACTERISTIC 2 Bytes UUID 0x0001 0x0002 0x0003 With this the TX characteristic can be identied by the resulting 16 Bytes UUID 0x6E400002-
C352-11E5-953D-0002A5D5C51B on the radio. With help of the RF_SPPBaseUUID parameter we have to possibility to update the 16Byte base UUID of the AMBER SPP-like prole. 8.17.1 Example 1 Set the base UUID to 0xEFEEEDEC-EBEA-E9E8-E7E6-E5E4E3E2E1E0 using CMD_SET_REQ with settings index 26 Start signal Command Length Settings index Parameter 0x02 0x11 0x11 0x00 0x1A 0xE0 0xE1 0xE2 0xE3 0xE4 0xE5 0xE6 0xE7 0xE8 0xE9 0xEA 0xEB 0xEC 0xED 0xEE 0xEF CS 0x18 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.17.2 Example 2 Request the base UUID of the module using CMD_GET_REQ:
Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x09 0x1A Response CMD_GET_CNF: Successfully read out the value 0x6E400000-C352-11E5-953D-
0002A5D5C51B. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 103 Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x11 0x00 0x00 0x1B 0xC5 0xD5 0xA5 0x02 0x00 0x3D 0x95 0xE5 0x11 0x52 0xC3 0x00 0x00 0x40 0x6E CS 0x0C AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 104 8.18 RF_Appearance: Congure the appearance of the device Settings index Designation Permissible values Default value Permissions Number of Bytes 25 RF_Appearance 0-65535 0 read/write 2 The user setting RF_Appearance species the appearance of the Bluetooth devices. Its a 2 Bytes eld dened by the Bluetooth SIG. Please check the Bluetooth Core Specica-
tion:Core Specication Supplement, Part A, section 1.12 for permissible values. 8.18.1 Example 1 Set the appearance to "Generic computer" (0x0080) using CMD_SET_REQ with settings in-
dex 25 Start signal Command Length 0x02 0x11 0x03 0x00 Settings index Parameter CS 0x80 0x00 0x89 0x19 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.18.2 Example 2 Request the RF_Appearance using CMD_GET_REQ:
Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x19 CS 0x0A Response CMD_GET_CNF: Successfully read out the value 0x0000, meaning that the appear-
ance is unknown. Start signal Command | 0x40 Length 0x02 0x50 0x03 0x00 Status Parameter CS 0x00 0x00 0x00 0x51 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 105 8.19 UART_BaudrateIndex: Modify the UART speed Settings index Designation 11 UART_BaudrateIndex Permissible values See description Default value Permissions Number of Bytes 3 read/write 1 This parameter denes the baud rate used by the modules UART. The permissible values are listed in the following table. UART_BaudrateIndex 0 1 2 3 4 5 6 Rate [Baud]
9600 19200 38400 115200 230400 460800 921600 Permissible values The ow control pins RTS and CTS can be enabled using the user setting UART_Flags. For UART_BaudrateIndex 5 and 6 the ow control pins are enabled independent of the UART_Flags. For baud rates faster than 230400 Baud, the ow control pins RTS and CTS are enabled. The evaluation board AMB2623 -EV version 2.0 does not provide the connec-
tion between the ow control pins of the module and the evaluation boards USB port. Thus in this version of the AMB2623 -EV the ow control can be on-
ly used, if the on-board UART is disconnected (remove respective jumpers on JP2) and all UART lines ( UART RX, UART TX, RTS and CTS) are connected to an external FTDI cable. After changing the baud rate using the CMD_SET_REQ the module restarts us-
ing the new baud rate. Therefore dont forget to update the baud rate of the connected host to be able to further use the modules UART. Please note that due to the HF-activity of the chip, single Bytes on the UART can get lost, when using a very fast UART data rate. In case of corrupted UART communication the module cannot interpret the sent request and thus does not return a conrmation. 8.19.1 Example 1 Set the baud rate index to 0x04 (230400 Baud) using CMD_SET_REQ with settings index 11 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 106 Start signal Command Length Settings index Parameter 0x02 0x11 0x02 0x00 0x0B 0x04 CS 0x1E Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.19.2 Example 2 Request the baud rate index of the module using CMD_GET_REQ with settings index 11 Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x18 0x0B Response CMD_GET_CNF: Successfully read out the value 0x03, which equals 115200 Baud. Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x53 0x03 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 107 8.20 UART_Flags: Congure the UART Settings index 27 Designation UART_Flags Permissible values 0,1 Default value Permissions Number of Bytes 0 read/write 1 The user setting UART_Flags species whether the UART uses ow control or not. Bit no. Description 0 1-7 Set this Bit to 1 to enable the ow control pins RTS and CTS. Reserved. For baud rates faster than 230400 Baud, the ow control pins RTS and CTS are enabled. The evaluation board AMB2623 -EV version 2.0 does not provide the connec-
tion between the ow control pins of the module and the evaluation boards USB port. Thus in this version of the AMB2623 -EV the ow control can be on-
ly used, if the on-board UART is disconnected (remove respective jumpers on JP2) and all UART lines ( UART RX, UART TX, RTS and CTS) are connected to an external FTDI cable. 8.20.1 Example 1 Enable the ow control using CMD_SET_REQ with settings index 27 Start signal Command Length Settings index Parameter 0x02 0x11 0x02 0x00 0x1B 0x01 CS 0x0B Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.20.2 Example 2 Request the UART_Flags using CMD_GET_REQ:
Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x08 0x1B Response CMD_GET_CNF: Successfully read out the value 0x00, meaning that the ow control is disabled. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 108 Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x50 0x00 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 109 8.21 CFG_Flags: Congure the Module Settings index 28 Designation CFG_Flags Permissible values 0,1 Default value Permissions Number of Bytes 0 read/write 2 The user setting CFG_Flags species whether the module uses high-throughput mode or not. Bit no. Description 0 1-7 Set this Bit to 1 to enable the high-throughput mode. Reserved. The high-throughput mode and its usage is described in out "AMB2623 - Ap-
plication Note 4". 8.21.1 Example 1 Enable the high-throughput mode using CMD_SET_REQ with settings index 28 Start signal Command Length Settings index Parameter CS 0x01 0x00 0x0D 0x02 0x11 0x03 0x00 0x1C Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.21.2 Example 2 Request the CFG_Flags using CMD_GET_REQ:
Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x1C CS 0x0F Response CMD_GET_CNF: Successfully read out the value 0x00, meaning that the high-throughput mode is disabled. Start signal Command | 0x40 Length 0x02 0x50 0x03 0x00 Status Parameter CS 0x00 0x00 0x00 0x51 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 110 8.22 DIS_ManufacturerName: Congure the manufacturer name Settings index Designation 20 DIS_ManufacturerName Permissible values See description Default value Permissions Number of Bytes
"Default"
read/write 1-64 The user setting DIS_ManufacturerName species the content of the manufacturer name eld of the Device Information Service. The permissible characters are in the range of 0x20 - 0x7E which are special characters (see ASCII table), alphabetic characters (a-z and A-Z), numbers (0-9) and whitespace. To add the content of the DIS_ManufacturerName to the DIS prole, please set the corresponding Bit in the DIS_Flags. 8.22.1 Example 1 Set the manufacturer name to "Manufacturer1" using CMD_SET_REQ with settings index 20 Start signal Command Length Settings index Parameter 0x02 0x11 0x0E 0x00 0x14 0x4D 0x61 0x6E 0x75 0x66 0x61 0x63 0x74 0x75 0x72 0x65 0x72 0x31 CS 0x0F Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.22.2 Example 2 Request the manufacturer name of the DIS prole using CMD_GET_REQ:
Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x07 0x14 Response CMD_GET_CNF: Successfully read out the value "Default". Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x08 0x00 0x00 0x44 0x65 0x66 0x61 0x75 0x6C 0x74 CS 0x11 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 111 8.23 DIS_ModelNumber: Congure the model number Settings index Designation 21 DIS_ModelNumber Permissible values See description Default value Permissions Number of Bytes
"Default"
read/write 1-64 The user setting DIS_ModelNumber species the content of the model number eld of the De-
vice Information Service. The permissible characters are in the range of 0x20 - 0x7E which are special characters (see ASCII table), alphabetic characters (a-z and A-Z), numbers (0-9) and whitespace. To add the content of the DIS_ModelNumber to the DIS prole, please set the corresponding Bit in the DIS_Flags. 8.23.1 Example 1 Set the model number to "Model1" using CMD_SET_REQ with settings index 21 Start signal Command Length Settings index Parameter 0x02 0x11 0x07 0x00 0x15 0x4D 0x6F 0x64 0x65 0x6C 0x31 CS 0x7F Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.23.2 Example 2 Request the model number of the DIS prole using CMD_GET_REQ:
Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x06 0x15 Response CMD_GET_CNF: Successfully read out the value "Default". Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x08 0x00 0x00 0x44 0x65 0x66 0x61 0x75 0x6C 0x74 CS 0x11 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 112 8.24 DIS_SerialNumber: Congure the serial number Settings index Designation 22 DIS_SerialNumber Permissible values See description Default value Permissions Number of Bytes
"Default"
read/write 1-64 The user setting DIS_SerialNumber species the content of the serial number eld of the De-
vice Information Service. The permissible characters are in the range of 0x20 - 0x7E which are special characters (see ASCII table), alphabetic characters (a-z and A-Z), numbers (0-9) and whitespace. To add the content of the DIS_SerialNumber to the DIS prole, please set the corresponding Bit in the DIS_Flags. 8.24.1 Example 1 Set the serial number to "1.2.3" using CMD_SET_REQ with settings index 22 Start signal Command Length Settings index Parameter 0x02 0x11 0x06 0x00 0x16 0x31 0x2E 0x32 0x2E 0x33 CS 0x33 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.24.2 Example 2 Request the serial number of the DIS prole using CMD_GET_REQ:
Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x05 0x16 Response CMD_GET_CNF: Successfully read out the value "Default". Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x08 0x00 0x00 0x44 0x65 0x66 0x61 0x75 0x6C 0x74 CS 0x11 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 113 8.25 DIS_HWVersion: Congure the HW version Settings index Designation 23 DIS_HWVersion Permissible values See description Default value Permissions Number of Bytes
"Default"
read/write 1-16 The user setting DIS_HWVersion species the content of the hardware version eld of the De-
vice Information Service. The permissible characters are in the range of 0x20 - 0x7E which are special characters (see ASCII table), alphabetic characters (a-z and A-Z), numbers (0-9) and whitespace. To add the content of the DIS_HWVersion to the DIS prole, please set the corresponding Bit in the DIS_Flags. 8.25.1 Example 1 Set the hardware version to "1.2.3" using CMD_SET_REQ with settings index 23 Start signal Command Length Settings index Parameter 0x02 0x11 0x06 0x00 0x17 0x31 0x2E 0x32 0x2E 0x33 CS 0x32 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.25.2 Example 2 Request the hardware version of the DIS prole using CMD_GET_REQ:
Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x04 0x17 Response CMD_GET_CNF: Successfully read out the value "Default". Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x08 0x00 0x00 0x44 0x65 0x66 0x61 0x75 0x6C 0x74 CS 0x11 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 114 8.26 DIS_SWVersion: Congure the SW version Settings index Designation 24 DIS_SWVersion Permissible values See description Default value Permissions Number of Bytes
"Default"
read/write 1-16 The user setting DIS_SWVersion species the content of the software version eld of the De-
vice Information Service. The permissible characters are in the range of 0x20 - 0x7E which are special characters (see ASCII table), alphabetic characters (a-z and A-Z), numbers (0-9) and whitespace. To add the content of the DIS_SWVersion to the DIS prole, please set the corresponding Bit in the DIS_Flags. 8.26.1 Example 1 Set the software version to "1.2.3" using CMD_SET_REQ with settings index 24 Start signal Command Length Settings index Parameter 0x02 0x11 0x06 0x00 0x18 0x31 0x2E 0x32 0x2E 0x33 CS 0x3D Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.26.2 Example 2 Request the software version of the DIS prole using CMD_GET_REQ:
Start signal Command Length Settings index 0x02 0x10 0x01 0x00 0x18 CS 0x0B Response CMD_GET_CNF: Successfully read out the value "Default". Start signal Command | 0x40 Length Status Parameter 0x02 0x50 0x08 0x00 0x00 0x44 0x65 0x66 0x61 0x75 0x6C 0x74 CS 0x11 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 115 8.27 DIS_Flags: Congure the Device Information Service Settings index Designation Permissible values Default value Permissions Number of Bytes 19 DIS_Flags 0-255 0 read/write 1 The user setting DIS_Flags species the content of the Device Information Service. To add a specic eld, like DIS_ModelNumber to the Device Information Service, the corresponding Bit has to be set in the DIS_Flags. Bit no. Description 0 1 2 3 4 5-7 Set this Bit to 1 to add the DIS_ManufacturerName to the Device Information Service. Set this Bit to 1 to add the DIS_ModelNumber to the Device Information Service. Set this Bit to 1 to add the DIS_SerialNumber to the Device Information Service. Set this Bit to 1 to add the DIS_HWVersion to the Device Information Service. Set this Bit to 1 to add the DIS_SWVersion to the Device Information Service. Reserved. 8.27.1 Example 1 Add the manufacturer name and model number (Bit0|Bit1 = 0x03) to the Device Information Service using CMD_SET_REQ with settings index 19 Start signal Command Length 0x02 0x11 0x02 0x00 Settings index Parameter CS 0x01 0x13 0x03 Response CMD_SET_CNF: Successfully modied the setting. Start signal Command | 0x40 Length Status CS 0x52 0x02 0x51 0x01 0x00 8.27.2 Example 2 Request the DIS_Flags using CMD_GET_REQ:
Start signal Command Length 0x02 0x10 0x01 0x00 Settings index CS 0x00 0x13 Response CMD_GET_CNF: Successfully read out the value 0x00, meaning that the Device Information Service is disabled, since no eld was added. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 116 Start signal Command | 0x40 Length 0x02 0x50 0x02 0x00 Status Parameter CS 0x00 0x50 0x00 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 117 Settings index Designation Summary 1 2 3 4 7 8 9 10 11 12 13 14 15 16 17 FS_FWVersion RF_DeviceName FS_MAC FS_BTMAC Version of the rmware Name of the module MAC address of the module BLE conform MAC address of the module RF_AdvertisingTimeout RF_ConnectionTiming RF_ScanTiming RF_ScanFactor Time [s] after advertising stops. LSB rst Module connection timing conguration Module advertising and scanning timing conguration Factor between scan interval and scan window UART_BaudrateIndex Baud rate of the UART RF_SecFlags RF_ScanFlags RF_BeaconFlags FS_DeviceInfo FS_SerialNumber RF_TXPower Security settings of the module Scan settings of the module Beacon settings of the module Information about the chip Serial number of the module Output power
[dBm] Twos complement Permissible values Default value
-
-
See de-
scription
"A2623"
-
-
0 (innite), 1 - 65535 0 - 6 0 - 5 1 - 10 See de-
scription See de-
scription See de-
scription See de-
scription
-
-
See de-
scription
-
-
0 1 1 2 3 0 0 0
-
-
4 Permissions of Number Bytes read read /
write read read read /
write read /
write read /
write read /
write read /
write read /
write read /
write read /
write read read read /
write 3 1-32 6 6 2 1 1 1 1 1 1 1 12 3 1 Table 17: Table of settings (Part 1) AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 118 Settings index Designation Summary RF_StaticPasskey 6 digit pass key Permissible values Default value See de-
scription
"123123"
18 19 20 21 22 23 24 25 26 27 28 44 DIS_Flags Flags for the DIS 0 - 255 0 DIS_ManufacturerName Manufacturer name eld of the DIS DIS_ModelNumber DIS_SerialNumber DIS_HWVersion DIS_SWVersion Model number eld of the DIS Serial number eld of the DIS HW version eld of the DIS SW version eld of the DIS RF_Appearance Appearance RF_SPPBaseUUID Base UUID of the AMBER SPP-like prole UART_Flags UART Flags CFG_Flags CFG Flags RF_SecFlagsPerOnly Security settings of the module
(peripheral only mode only) See de-
scription See de-
scription See de-
scription See de-
scription See de-
scription 0-65535 See de-
scription 0,1 0,1 See de-
scription
"Default"
"Default"
"Default"
"Default"
"Default"
0 See de-
scrip-
tion 0 0 11 Permissions of Number Bytes read /
write read /
write read /
write read /
write read /
write read /
write read /
write read /
write read /
write read /
write read /
write read /
write 6 1 1-64 1-64 1-64 1-16 1-16 2 16 1 2 1 Table 18: Table of settings (Part 2) AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 119 9 Timing parameters 9.1 Reset and sleep After power-up, resetting the module or waking the module from sleep a CMD_GETSTATE_CNF is sent to the serial interface as soon as the module is ready for operation. Description Ready after reset/sleep Typ. Unit 4 ms 9.2 BLE timing parameters The timing parameters for sending advertising packets or scanning are determined by the user settings RF_ScanTiming, RF_ScanFactor and RF_AdvertisingTimeout. Using these settings, the advertising interval, the advertising timeout, the scan interval and the scan window can be congured. Furthermore, the user setting RF_ConnectionTiming allows to congure the timing parameters used during connection setup and connection retention, as well as the connection interval and the connection supervision timeout. 9.3 Connection establishment The time needed to establish a connection sums up as the time needed to detect the select-
ed peripheral on air and the time needed for connection parameter negotiation and service discovery. 1. Peripheral detection To establish a connection, the initiating device (central) waits for an advertising packet, which was sent by the peripheral to which it wants to connect to. As soon as such an advertising packet has been received, the central sends a connection request to the chosen peripheral. The time needed to receive this advertising packet strongly depends on the advertising interval of the peripheral as well as on the scan interval and scan window of the central (see RF_ScanTiming). 2. Connection parameter negotiation After the connection request has been sent the central and peripheral negotiate the timing and security parameters of the connec-
tion. To nish this procedure and discover the services of the peripheral several messages have to be sent, whereby only one is sent per connection interval (see RF_ConnectionTiming). Connection type Estimated number of exchanged messages Negotiation time for a connection interval of 50ms Unsecured connection Secured connection using the pairing method Secured connection to already bonded device 12-14 22-24 19-20 600-700ms 1100-1200ms 950-1000ms AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 120 Knowing the connection interval and the number of messages that will be sent, the time necessary to setup a connection can be estimated by multiplying the number of messages with the connection interval. In case the Device Information Service is enabled, the number of messages and thus the timing of the connection setup may be increased. 9.4 Connection based data transmission After setting up a connection, data can be transmitted using the CMD_DATA_REQ. It buffers the data in the module and sends it with the next connection interval event. As soon as the data has been transmitted successfully, a CMD_TXCOMPLETE_RSP is returned by the UART. The time needed for this coincides with the connection interval that was negotiated during connection setup. The RF_ConnectionTiming parameter denes the minimum and maximum connection interval, which is supported by the module. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 121 10 Peripheral only mode The version 3.0.0 of the AMB2623 implements a new feature that allows the easy integration of the AMB2623 BLE module to an already existing host. The peripheral only mode offers a plug and play installation without previous conguration of the AMB2623 . It is tailored for easy communication with mobile BLE devices like smart phones. 10.1 Peripheral only mode 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 AMB2623 only contains the functions of a peripheral. Thus, it is advertising until another BLE device connects to it. In this case, the UART of the AMB2623 is enabled, the LED_2 pin shows that the channel is open and bidi-
rectional 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 AMB2623 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 AMB2623 to the connected BLE device. On the other hand, all data received by RF is send from the AMB2623 to the connected host without additional header Bytes. Please have in mind that the connecting smart phone must support and initiate larger MTU sizes when payload sizes of more than 19 Bytes shall be used. Additional Bytes will be discarded without notice to the host. The data sent to the UART is buffered in the AMB2623 up to a maximum payload depending on of the current channel MTU. When no new Byte was received for 20ms, the data will be transmitted by RF to the connected BLE device. The UART is only running, when a channel is open. Thus, power is saved during the advertising period. Depending on the congured connection interval, only one packet per interval is allowed to be transmitted. Since the commands of the command interface are no longer valid, a AMB2623 cannot be congured 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.2 Reasons to use the peripheral only mode The AMB2623 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 AMB2623 in peripheral only mode the central device has to insert the AMB2623 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. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 122 Due to the transparent UART interface, data can be exchanged without additional headers. Furthermore, the peripheral only mode allows an energy efcient operation of the BLE inter-
face, since the UART is only enabled when it is really used. 10.3 How to use the peripheral only mode The peripheral only mode is enabled, when a high signal is present on the OPERATION MODE pin during device start-up or reset. No conguration of the module is needed for this operating mode. The module shall be set to factory settings if recongured before so it uses the default user settings. In this case, the UART uses 115200 Baud 8n1 and static passkey pairing is used as authentication method. If a conguration of the module is still needed (e.g. when another UART baud rate needs to be chosen), the module has to be started in normal mode and the CMD_SET_REQ may be used to update the user settings. The user shall not change any other of the user settings but the following parameters:
UART_BaudrateIndex (change the UART baud rate, default value "115200") UART_Flags (enable or disable the ow control) RF_StaticPasskey (change the default static passkey, default value "123123") Only changes (in comparison to the factory settings) in the parameters UART_BaudrateIndex, UART_Flags and RF_StaticPasskey are allowed. In case the module has been congured with other non-default user settings, while the command mode was used, a CMD_FACTORYRESET_REQ is mandatory before ac-
tivating the peripheral only mode. On the central side (e.g. smart phone), the AMBER SPP like prole has to be implemented in a customer application. For more information, see the "AMB2623 Advanced developer guide" and the application note AMB2623 _AN003 that explains the general connection. 10.4 More information The maximum payload supported by an open channel depends on the connected cen-
tral device. The AMB2623 supports up to 243 Bytes payload (corresponding to a MTU of 247 Byte), which may be negotiated by the central device (using a MTU request). If no MTU request is requested by the connecting central device the value of 19 Bytes payload per packet and connection interval as given by the BT 4.0 standard is used
(compatibility mode to BLE 4.0 devices). Data received by the AMB2623 s UART, that exceeds the maximum payload size of the open channel, is discarded. In peripheral only mode, (due to the deactivated commands) the AMB2623 cannot inform its host about the maximum payload size or of payload discarding. The connecting device could implement a function to inform the host behind the AM-
B2623 which MTU the channel is capable of. Until this message is received, the host shall assume a payload capability of up to 19 Byte. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 123 In peripheral only mode a new 8-digit device name is automatically generated by the FS_BTMAC. In case of the FS_BTMAC equals 0x0018DA123456 the device name is "A-
123456". This is a workaround for iOS, which does not allow access to the BTMAC for received BT frames. The content of the advertising packet was changed in peripheral only mode. The TX power information block was removed, as the device name was extended to 8 digits. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 124 11 Customizing the AMB2623 11.1 DIS - Device information service Besides the AMBER SPP-like prole for data transmission, the AMB2623 contains the so called Device Information Service. This prole exposes manufacturer information about a device and is used to personalize the AMB2623 to fuse with the custom product. The De-
vice Information Service is a standard BLE prole that is recognized by all devices with Bluetooth capabilities. It contains the following elds, that can only be modied by updating the respective user setting using the CMD_SET_REQ command:
Field name User setting Maximum length Manufacturer Name String DIS_ManufacturerName Model Number String Serial Number String Hardware Revision String Software Revision String DIS_ModelNumber DIS_SerialNumber DIS_HWVersion DIS_SWVersion 64 64 64 16 16 Furthermore, the user setting DIS_Flags denes which of the described DIS elds are nally placed in the DIS prole. Thus after adding content to the a DIS eld user setting, like DIS_ManufacturerName, the user setting DIS_Flags has to be adapted such that the content is added to the prole. 11.2 UUID The UUID is a unique number identifying a BLE prole and thus describing its functions. The AMB2623 using its standard UUID is compatible to all devices that implement the AMBER SPP-like prole, whichever device it is integrated. To suspend this interoperability, the user setting RF_SPPBaseUUID can be used to modify the UUID of the AMBER SPP-like prole. With this, a new custom SPP-like prole is dened that is solely known to those that chose the new UUID. To generate a custom UUID the Bluetooth SIG recommends to use the tool:
http://www.uuidgenerator.net/
11.3 Appearance The appearance of the Bluetooth device is a 2 Bytes value dened by the Bluetooth SIG. It can be congured by adapting the parameter RF_Appearance. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 125 12 Firmware update The AMB2623 offers two possibilities of updating its rmware, namely wired or wireless. The rmware of the AMB2623 consists of 3 parts, the OTA-bootloader, the Softdevice and the application. Ensure that after updating the rmware all parts are still existent. 12.1 Firmware update using the SWD interface To update the rmware of the AMB2623 the SWD interface of the module and a supported asher hardware (such as SEGGER J-Link plus) can be used. Therefore the pins GND, VCC, RESET, SWDIO and SWDCLK of the module have to be accessible and connected to the asher hardware accordingly (corresponding documentation of asher has to be read for further information). After the connection of a ash adapter to this SWD interface, the new rmware can be ashed using the corresponding PC software nrfjprog.exe available directly from Nordic Semiconductor. nrfjprog.exe - -family NRF52 - -chiperase - -program AMB2623 .hex For this reason a .hex-le can be provided, which contains all rmware parts (bootload-
er, Softdevice, application). The name of the hex le has to be adopted accordingly in the command line above. This is the only method by which the module could be recovered in the event of a serious software fault or corrupted memory. This method is fail-safe. 12.2 Firmware update using the AMB2623 OTA bootloader The second method offers a possibility to update the rmware over the air (OTA). Therefore, the Nordic nRF52 BLE DFU Bootloader is integrated into the AMB2623 s rmware, which will communicate over the BLE interface. The OTA bootloader mode is a distinct operating mode besides the normal operating modes mentioned before. For this reason, a .zip-le can be provided, which contains all (bootloader, Softdevice, application) parts of the rmware in an encrypted and authenticated package. To start the bootloader, one of the following two conditions has to be satised:
1. send the command CMD_BOOTLOADER_REQ to the module to restart in bootloader mode 2. during a reset and while restarting, a low signal has to be present on the BOOT pin of the module to start it in bootloader mode The bootloader mode has started successfully if LED_1 has turned on. After the bootloader has started successfully, the module goes into the advertising mode AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 126 using the name "DFU2623". Now, any BLE device hosting an application that understands the commands of the Nordic nRF52 BLE DFU Bootloader can connect in order to update the AMB2623 rmware. The DFU application of the AMB2623 Toolbox App is such an application. For more details, please refer to the AMB2623 Toolbox Quick Start Guide. As an alternative, the plain Apps from Nordic Semiconductor "nRF Toolbox" can be used. Version of the rmware before the update 1.0.0 - 1.1.0 1.0.0 - 1.1.0 2.1.0 2.1.0, 3.X.X Version of the new rmware 1.0.0 - 1.1.0 2.1.0 2.1.0 3.X.X Version of the AMB2623 Toolbox App
(Android) 1.16.2, 1.18.4 Not supported, due to S132 update and bootloader changes 1.18.4 1.18.4 or Nordic nRF Toolbox 2.2.1 Table 19: Compatibility matrix As soon as a connection has been set up, LED_1 turns off again and LED_2 turns on. The implemented Nordic nRF52 BLE DFU bootloader uses a dual bank method to update the rmware. Thus, the old rmware is only replaced once the new rmware has been transferred successfully. This prevents the module from being ashed with a faulty rmware. An OTA rmware update will take several minutes to be performed, the duration is also dependant how much of the rmware shall be updated (application only or complete update). The max connection interval of the update service is set to 30ms. Please check whether your mobile supports this speed. This method is only applicable if the AMB2623 still contains an intact boot-
loader. In order to be able to recover a faulty module, we recommend to have access to the relevant JTAG pins required to perform a wired rmware update. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 127 13 Firmware history Version 0.x.x "Engineering"
Pre-Release for test run Version 1.0.0 "Release"
First production release AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 128 14 Design in guide 14.1 Advice for schematic and layout For users with less RF experience it is advisable to closely copy the relating evaluation board with respect to schematic and layout, as it is a proven design. The layout should be conducted with particular care, because even small deciencies could affect the radio performance and its range or even the conformity. The following general advice should be taken into consideration:
A clean, stable power supply is strongly recommended. Interference, especially oscil-
lation can severely restrain range and conformity. Variations in voltage level should be avoided. LDOs, properly designed in, usually deliver a proper regulated voltage. Blocking capacitors and a ferrite bead in the power supply line can be included to lter and smoothen the supply voltage when necessary. No xed values can be recommended, as these depend on the circumstances of the application (main power source, interferences etc.). Frequently switching the module on and off, especially with a slowly changing voltage level of the power supply, can lead to erratic behavior, in rare cases even as far as damaging the module or the rmware. The use of an external reset IC can solve this matter and shall be considered especially in battery operated scenarios. Elements for ESD protection should be placed on all pins that are accessible from the outside and should be placed close to the accessible area. For example, the RF-pin is accessible when using an external antenna and should be protected. ESD protection for the antenna connection must be chosen such as to have a minimum effect on the RF signal. For example, a protection diode with low capacitance such as the LXES15AAA1-100 or a 68 nH air-core coil connecting the RF-line to ground give good results. Placeholders for optional antenna matching or additional ltering are recommended. The antenna path should be kept as short as possible. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 129 Again, no xed values can be recommended, as they depend on the inuenc-
ing circumstances of the application (antenna, interferences etc.). Figure 7: Layout To avoid the risk of short circuits and interference there should be no routing under-
neath the module on the top layer of the baseboard. On the second layer, a ground plane is recommended, to provide good grounding and shielding to any following layers and application environment. In case of integrated antennas it is required to have areas free from ground. This area should be copied from the evaluation board. The area with the integrated antenna must overlap with the carrier board and should not protrude, as it is matched to sitting directly on top of a PCB. Modules with integrated antennas should be placed with the antenna at the edge of It should not be placed in the middle of the main board or far away the main board. from the edge. This is to avoid tracks beside the antenna. Filter and blocking capacitors should be placed directly in the tracks without stubs, to achieve the best effect. Antenna matching elements should be placed close to the antenna / connector, block-
ing capacitors close to the module. Ground connections for the module and the capacitors should be kept as short as possible and with at least one separate through hole connection to the ground layer. ESD protection elements should be placed as close as possible to the exposed areas. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 130 Figure 8: Placement of the module with integrated antenna 14.2 Dimensioning of the micro strip antenna line The antenna track has to be designed as a 50 feed line. The width W for a micro strip can Figure 9: Dimensioning the antenna feed line as micro strip be calculated using the following equation:
W = 1.25
5.98 H 50 e
r +1.41 87
Tmet
(1) Example:
A FR4 material with r=4.3, a height H = 1000 m and a copper thickness of Tmet= 18 m will lead to a trace width of W 1.9 mm. To ease the calculation of the micro strip line (or e.g. a coplanar) many calculators can be found in the internet. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 131 As rule of thumb a distance of about 3W should be observed between the micro strip and other traces / ground. The micro strip refers to ground, therefore there has to be the ground plane underneath the trace. Keep the feeding line as short as possible. 14.3 Antenna solutions There exist several kinds of antennas, which are optimized for different needs. Chip anten-
nas are optimized for minimal size requirements but at the expense of range, PCB antennas are optimized for minimal costs, and are generally a compromise between size and range. Both usually t inside a housing. Range optimization in general is at the expense of space. Antennas that are bigger in size, so that they would probably not t in a small housing, are usually equipped with a RF con-
nector. A benet of this connector may be to use it to lead the RF signal through a metal plate (e.g. metal housing, cabinet). As a rule of thumb a minimum distance of /10 (which is 3.5 cm @ 868 MHz and 1.2 cm @
2.44 GHz) from the antenna to any other metal should be kept. Metal placed further away will not directly inuence the behavior of the antenna, but will anyway produce shadowing. Keep the antenna away from large metal objects as far as possible to avoid electromagnetic eld blocking. In the following chapters, some special types of antenna are described. 14.3.1 Wire antenna An effective antenna is a /4 radiator with a suiting ground plane. The simplest realization is a piece of wire. Its length is depending on the used radio frequency, so for example 8.6 cm 868.0 MHz and 3.1 cm for 2.440 GHz as frequency. This radiator needs a ground plane at its feeding point. Ideally, it is placed vertically in the middle of the ground plane. As this is often not possible because of space requirements, a suitable compromise is to bend the wire away from the PCB respective to the ground plane. The /4 radiator has approximately 40 input impedance, therefore matching is not required. 14.3.2 Chip antenna There are many chip antennas from various manufacturers. The benet of a chip antenna is obviously the minimal space required and reasonable costs. However, this is often at the expense of range. For the chip antennas, reference designs should be followed as closely as possible, because only in this constellation can the stated performance be achieved. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 132 14.3.3 PCB antenna PCB antenna designs can be very different. The special attention can be on the miniaturiza-
tion or on the performance. The benets of the PCB antenna are their small / not existing (if PCB space is available) costs, however the evaluation of a PCB antenna holds more risk of failure than the use of a nished antenna. Most PCB antenna designs are a compromise of range and space between chip antennas and connector antennas. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 133 14.3.4 Antennas provided by Wrth Elektronik eiSos 14.3.4.1 AMB1981 - 868 MHz dipole antenna Figure 10: AMB1981: 868 MHz dipole-antenna Ideally suited for applications where no ground plane is available. The AMB1981 antenna can be also used for 902MHz - 928MHz range. Value 868 853 - 883 0.5 wave 2.0 50 SMA (Male) Specication Center frequency [MHz]
Frequency range [MHz]
Wavelength VSWR Impedance []
Connector Dimensions (L x d) [mm] 142 x 10 Peak Gain [dBi]
Operating Temp. [C]
-2.3
-30 - +80 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 134 14.3.4.2 AMB1982 - 868 MHz magnetic base antenna Well suited for applications where the RF is lead through a metal wall that could serve as ground plane to the antenna. Figure 11: AMB1982: 868 MHz magnet foot antenna with 1.5 m antenna cable The AMB1982 is a kind of /4 radiator and therefore needs a ground plane at the feeding point. Value 824 - 894 2.0 Vertical 505 SMA (Male) Specication Frequency range [MHz]
VSWR Polarisation Impedance []
Connector Dimensions (L x d) [mm] 89.8 x 27 Weight [g]
Operating Temp. [C]
505
-30 - +60 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 135 14.3.4.3 AMB1926 - 2.4 GHz dipole antenna Figure 12: AMB1926: 2.4 GHz dipole-antenna Ideally suited for applications where no ground plane is available. Value 2.4 - 2.5 50 2.0 Vertical Omni 2.5 Polyurethane Specication Frequency Range [GHz]
Impedance []
VSWR Polarization Radiation Gain [dBi]
Antenna Cover Dimensions (L x d) [mm] 140 x 14 Weight [g]
Connector Operating Temp. [C]
25 SMA plug
-20 - +65 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 136 15 Manufacturing information 15.1 Moisture sensitivity level This wireless connectivity product is categorized as JEDEC Moisture Sensitivity Level 3 (MSL3), which requires special handling. More information regarding the MSL requirements can be found in the IPC/JEDEC J-STD-020 standard on www.jedec.org. More information about the handling, picking, shipping and the usage of moisture/reow and/or process sensitive products can be found in the IPC/JEDEC J-STD-033 standard on www.jedec.org. 15.2 Soldering 15.2.1 Reow soldering Attention must be paid on the thickness of the solder resist between the host PCB top side and the modules bottom side. Only lead-free assembly is recommended according to JEDEC J-STD020. Prole feature Preheat temperature Min Preheat temperature Max Preheat time from TS M in to TS M ax Ramp-up rate (TL to TP ) Liquidous temperature Time tL maintained above TL Peak package body temperature Time within 5C of actual preak temperature Ramp-down Rate (TP to TL) Time 20C to TP TS M in TS M ax tS TL tL TP tP Value 150C 200C 60 - 120 seconds 3C / second max. 217C 60 - 150 seconds see table below 20 - 30 seconds 6C / second max. 8 minutes max. Table 20: Classication reow soldering prole, Note: refer to IPC/JEDEC J-STD-020E AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 137 Package thickness
< 1.6mm 1.6mm - 2.5mm
> 2.5mm Volume mm3
<350 260C 260C 250C Volume mm3 350-2000 260C 250C 245C Volume mm3
>2000 260C 245C 245C Table 21: Package classication reow temperature, PB-free assembly, Note: refer to IPC/-
JEDEC J-STD-020E It is recommended to solder this module on the last reow cycle of the PCB. For solder paste use a LFM-48W or Indium based SAC 305 alloy (Sn 96.5 / Ag 3.0 / Cu 0.5 / Indium 8.9HF /
Type 3 / 89%) type 3 or higher. The reow prole must be adjusted based on the thermal mass of the entire populated PCB, heat transfer efciency of the reow oven and the specic type of solder paste used. Based on the specic process and PCB layout the optimal soldering prole must be adjusted and veried. Other soldering methods (e.g. vapor phase) have not been veried and have to be validated by the customer at their own risk. Rework is not recommended. Figure 13: Reow soldering prole After reow soldering, visually inspect the board to conrm proper alignment AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 138 TimeTemperatureTptptLtSTs maxTs minTC 5CTL25Time 25C to PeakPreheat AreaMax. Ramp Up RateMax. Ramp Down Rate 15.2.2 Cleaning Do not clean the product. Any residue cannot be easily removed by washing. Use a "no clean" soldering paste and do not clean the board after soldering. Do not clean the product with water. Capillary effects can draw water into the gap between the host PCB and the module, absorbing water underneath it. If water is trapped inside, it may short-circuit adjoining pads. The water may also destroy the label and ink-jet printed text on it. Cleaning processes using alcohol or other organic solvents may draw solder ux residues into the housing, which wont be detected in a post-wash inspection. The solvent may also destroy the label and ink-jet printed text on it. Do not use ultrasonic cleaning as it will permanently damage the part, particularly the crystal oscillators. 15.2.3 Other notations Conformal coating of the product will result in the loss of warranty. The RF shields will not protect the part from low-viscosity coatings. Do not attempt to improve the grounding by forming metal strips directly to the EMI covers or soldering on ground cables, as it may damage the part and will void the warranty. Always solder every pad to the host PCB even if some are unused, to improve the mechanical strength of the module. The part is sensitive to ultrasonic waves, as such do not use ultrasonic cleaning, weld-
ing or other processing. Any ultrasonic processing will void the warranty. 15.3 ESD handling This product is highly sensitive to electrostatic discharge (ESD). As such, always use prop-
er ESD precautions when handling. Make sure to handle the part properly throughout all stages of production, including on the host PCB where the module is installed. For ESD ratings, refer to the module series maximum ESD section. For more information, refer to the relevant chapter 2. Failing to follow the aforementioned recommendations can result in severe damage to the part. the rst contact point when handling the PCB is always between the local GND and the host PCB GND, unless there is a galvanic coupling between the local GND (for example work table) and the host PCB GND. Before assembling an antenna patch, connect the grounds. While handling the RF pin, avoid contact with any charged capacitors and be careful when contacting any materials that can develop charges (for example coaxial cable with around 50-80 pF/m, patch antenna with around 10 pF, soldering iron etc.) AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 139 Do not touch any exposed area of the antenna to avoid electrostatic discharge. Do not let the antenna area be touched in a non ESD-safe manner. When soldering, use an ESD-safe soldering iron. 15.4 Safety recommendations It is your duty to ensure that the product is allowed to be used in the destination country and within the required environment. Usage of the product can be dangerous and must be tested and veried by the end user. Be especially careful of:
Use in areas with risk of explosion (for example oil reneries, gas stations). Use in areas such as airports, aircraft, hospitals, etc., where the product may interfere with other electronic components. It is the customers responsibility to ensure compliance with all applicable legal, regulatory and safety-related requirements as well as applicable environmental regulations. Disassem-
bling the product is not allowed. Evidence of tampering will void the warranty. Compliance with the instructions in the product manual is recommended for correct product set-up. The product must be provided with a consolidated voltage source. The wiring must meet all applicable re and security prevention standards. Handle with care. Avoid touching the pins as there could be ESD damage. Be careful when working with any external components. When in doubt consult the technical documentation and relevant standards. Always use an antenna with the proper characteris-
tics. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 140 16 Physical dimensions 16.1 Dimensions 16.2 Weight Dimensions 11 x 8 x 1.8 mm Table 22: Dimensions Weight
<1g Table 23: Weight AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 141 16.3 Module drawing Figure 14: Module dimensions [mm]
AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 142 8,00,32,00,211,00,33,41,27,26,01,00,81781112171,2 16.4 Footprint Figure 15: Footprint [mm]
16.5 Antenna free area To avoid inuence and mismatching of the antenna the recommended free area around the antenna should be maintained. As rule of thumb a minimum distance of metal parts to the antenna of /10 should be kept (see gure 15). Even though metal parts would inuence the characteristic of the antenna, but the direct inuence and matching keep an acceptable level. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 143 7,21,13,46,01,201,90,59,01,51,20,81,23,236,0no metall 17 Marking 17.1 Lot number The 15 digit lot number is printed in numerical digits as well as in form of a machine readable bar code. It is divided into 5 blocks as shown in the following picture and can be translated according to the following table. Figure 16: Lot number structure Block Information 1 2 3 4 5 eiSos internal, 3 digits eiSos internal, 2 digits Hardware version, 3 digits Date code, 4 digits Firmware version, 3 digits Example(s) 439 01 V2.4 = 024, V12.2 = 122 1703 = week 03 in year 2017, 1816 = week 16 in year 2018 V3.2 = 302, V5.13 = 513 Table 24: Lot number details As the user can perform a rmware update the printed lot number only shows the factory delivery state. The currently installed rmware can be requested from the module using the corresponding product specic command. The rmware version as well as the hardware version are restricted to show only major and minor version not the patch identier. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 144 17.2 General labeling information The module labels may include the following elds:
Manufacturer WE or Wrth Elektronik Article number and/or article alias Serial number or MAC address Certication numbers (CE, FCC ID, IC, ARIB,...) Barcode or 2D code containing the serial number or MAC address The serial number includes the product ID (PID) and an unique 6 digit number. The rst 1 to 3 digits represent the PID, then the "." marks the start of the 6 digit counter to create a unique product marking. In case of small labels, the 3 byte manufacturer identier (0x0018DA) of the MAC address is not printed on the labels. The 3 byte counter printed on the label can be used with this 0018DA to produce the full MAC address by appending the counter after the manufacturer identier. 17.2.1 Example labels of Wrth Elektronik eiSos products AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 145 18 Bluetooth SIG listing/qualication Each product containing intellectual property of the Bluetooth Special Interest Group (SIG) must be qualied by the SIG to obtain the corresponding Declaration ID. Every new Bluetooth design must pass the qualication process, even when linking to a Bluetooth design that is already qualied. To go through the qualication process each company must register as a member of the Bluetooth SIG:
https://www.bluetooth.org/login/register/
Due to the qualication of the AMB2623 as end product no further Bluetooth tests are required. Thus, except of the purchase of the Declaration ID, no retesting costs are incurred. The fees for the Declaration ID depend on your membership status:
https://www.bluetooth.org/en-us/test-qualication/qualication-overview/fees Please refer to the testing laboratory of your choice for further more detailed information regarding the qualication of your product. 18.1 Qualication steps when referencing the AMB2623 Due to the qualication of the AMB2623 as end product, it can be referenced when starting the qualication process of your product integrating the AMB2623 . To perform the qualica-
tion process in a row, please purchase a Declaration ID before starting the new qualication, either through invoicing or credit card payment. To do so, please perform the following steps:
1. Go to https://www.bluetooth.org/tpg/QLI_SDoc.cfm . 2. Go to "Manage Declarations IDs" . 3. Then push the "Purchase a Declaration ID" button and ll the form. Please note that you can nish the qualication process once the invoice for the Declaration ID is paid. To perform the qualication process of your product, please go through the following steps:
1. Go to https://www.bluetooth.org/tpg/QLI_SDoc.cfm . 2. Select option "Start the Bluetooth Qualication Process with NO Required Testing". 3. Enter the QDID (see above) and select the corresponding AMB2623 entry. 4. Select your pre-paid Declaration ID (it can be selected as soon as the Declaration ID has been paid). 5. Follow the subsequent steps to nish the qualication process. After nishing the process, your product will be listed on the Bluetooth website. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 146 19 Regulatory compliance information 19.1 Important notice FCC The use of RF frequencies is limited by national regulations. The AMB2623 has been de-
signed to comply with the FCC Part 15. The AMB2623 can be operated without notication and free of charge in the area of the Unites States of America. However, according to the FCC Part 15, restrictions (e.g. in terms of maximum allowed RF power and antenna) may apply. 19.2 Conformity assessment of the nal product The AMB2623 is a subassembly. It is designed to be embedded into other products (prod-
ucts incorporating the AMB2623 are henceforward referred to as "nal products"). It is the responsibility of the manufacturer of the nal product to ensure that the nal product is in compliance with the essential requirements of the underlying national radio regulations. The conformity assessment of the subassembly AMB2623 carried out by Wrth Elektronik eiSos does not replace the required conformity assessment of the nal product. 19.3 Exemption clause Relevant regulation requirements are subject to change. Wrth Elektronik eiSos does not guarantee the accuracy of the before mentioned information. Directives, technical standards, procedural descriptions and the like may be interpreted differently by the national authori-
ties. Equally, the national laws and restrictions may vary with the country. In case of doubt or uncertainty, we recommend that you consult with the authorities or ofcial certication organizations of the relevant countries. Wrth Elektronik eiSos is exempt from any respon-
sibilities or liabilities related to regulatory compliance. Notwithstanding the above, Wrth Elektronik eiSos makes no representations and war-
ranties of any kind related to their accuracy, correctness, completeness and/or usability for customer applications. No responsibility is assumed for inaccuracies or incompleteness. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 147 19.4 FCC Declaration of conformity FCC ID: R7TAMB2623 This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and
(2) this device must accept any interference received, including interference that may cause undesired operation.
(FCC 15.19) Modications (FCC 15.21) Changes or modications for this equipment not expressly approved by Wrth Elektronik eiSos may void the FCC authorization to operate this equipment. 19.5 IC Declaration of conformity Certication Number: 5136A-AMB2623 This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. Le prsent appareil est conforme aux CNR dIndustrie Canada applicables aux appareils radio exempts de licence. Lexploitation est autorise aux deux conditions suivantes : (1) lappareil ne doit pas produire de brouillage, et (2) lutilisateur de lappareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible den compromettre le fonctionnement. 19.6 FCC and IC requirements to OEM integrators This module has been granted modular approval. OEM integrators for host products may use the module in their nal products without additional FCC/IC (Industry Canada) certica-
tion if they meet the following conditions. Otherwise, additional FCC/IC approvals must be obtained. The host product with the module installed must be evaluated for simultaneous transmission requirements. The users manual for the host product must clearly indicate the operating requirements and conditions that must be observed to ensure compliance with current FCC/IC RF exposure guidelines. To comply with FCC/IC regulations limiting both maximum RF output power and human exposure to RF radiation, the maximum antenna gain including cable loss in a mobile-
only exposure condition must not exceed 2dBi. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 148 A label must be afxed to the outside of the host product with the following statements:
This device contains FCCID: R7TAMB2623 This equipment contains equipment certied under ICID: 5136A-AMB2623 The nal host / module combination may also need to be evaluated against the FC-
C Part 15B criteria for unintentional radiators in order to be properly authorized for operation as a Part 15 digital device. If the nal host / module combination is intended for use as a portable device (see classications below) the host manufacturer is responsible for separate approvals for the SAR requirements from FCC Part 2.1093 and RSS-102. OEM requirements:
The OEM must ensure that the following conditions are met. End users of products, which contain the module, must not have the ability to alter the rmware that governs the operation of the module. The agency grant is valid only when the module is incorporated into a nal product by OEM integrators. The end-user must not be provided with instructions to remove, adjust or install the module. The Original Equipment Manufacturer (OEM) must ensure that FCC labeling require-
ments are met. This includes a clearly visible label on the outside of the nal product. Attaching a label to a removable portion of the nal product, such as a battery cover, is not permitted. The label must include the following text:
Contains FCC ID: R7TAMB2623 The enclosed device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(i.) this device may not cause harmful interference and
(ii.) this device must accept any interference received, including interference that may cause undesired operation. When the device is so small or for such use that it is not practicable to place the s-
tatement above on it, the information required by this paragraph shall be placed in a prominent location in the instruction manual or pamphlet supplied to the user or, alter-
natively, shall be placed on the container in which the device is marketed. However, the FCC identier or the unique identier, as appropriate, must be displayed on the device. The user manual for the end product must also contain the text given above. Changes or modications not expressly approved could void the users authority to operate the equipment. The OEM must ensure that timing requirements according to 47 CFR 15.231(a-c) are met. The OEM must sign the OEM Modular Approval Agreement. The module must be used with only the following approved antenna(s). AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 149 19.7 Pre-certied antennas The AMB2623 is pre-certied with the following antennas. Product AMB2623 AMB2623 -1 AMB1926 - 2.4 GHz dipole antenna as specied in chapter 14.3.4.3 PCB antenna included in the AMB2623 Certied antenna AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 150 20 Important information The following conditions apply to all goods within the wireless connectivity product range of Wrth Elektronik eiSos GmbH & Co. KG :
20.1 General customer responsibility Some goods within the product range of Wrth Elektronik eiSos GmbH & Co. KG contain statements regarding general suitability for certain application areas. These statements about suitability are based on our knowledge and experience of typical requirements con-
cerning the areas, serve as general guidance and cannot be estimated as binding state-
ments about the suitability for a customer application. The responsibility for the applicability and use in a particular customer design is always solely within the authority of the customer. Due to this fact, it is up to the customer to evaluate, where appropriate to investigate and to decide whether the device with the specic product characteristics described in the product specication is valid and suitable for the respective customer application or not. Accordingly, the customer is cautioned to verify that the documentation is current before placing orders. 20.2 Customer responsibility related to specic, in particular safety-relevant applications It has to be clearly pointed out that the possibility of a malfunction of electronic compo-
nents or failure before the end of the usual lifetime cannot be completely eliminated in the current state of the art, even if the products are operated within the range of the specica-
tions. The same statement is valid for all software and rmware parts contained in or used with or for products in the wireless connectivity product range of Wrth Elektronik eiSos GmbH & Co. KG . In certain customer applications requiring a high level of safety and espe-
cially in customer applications in which the malfunction or failure of an electronic component could endanger human life or health, it must be ensured by most advanced technological aid of suitable design of the customer application that no injury or damage is caused to third parties in the event of malfunction or failure of an electronic component. 20.3 Best care and attention Any product-specic datasheets, manuals, application notes, PCNs, warnings and cautions must be strictly observed in the most recent versions and matching to the products rmware revisions. This documents can be downloaded from the product specic sections on the wireless connectivity homepage. 20.4 Customer support for product specications Some products within the product range may contain substances, which are subject to re-
strictions in certain jurisdictions in order to serve specic technical requirements. Necessary information is available on request. In this case, the eld sales engineer or the internal sales person in charge should be contacted who will be happy to support in this matter. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 151 20.5 Product improvements Due to constant product improvement, product specications may change from time to time. As a standard reporting procedure of the Product Change Notication (PCN) according to the JEDEC-Standard, we inform about major changes in hard- or rmware. In case of further queries regarding the PCN, the eld sales engineer, the internal sales person or the technical support team in charge should be contacted. The basic responsibility of the customer as per section 20.1 and 20.2 remains unaffected. 20.6 Product life cycle Due to technical progress and economical evaluation we also reserve the right to discontin-
ue production and delivery of products. As a standard reporting procedure of the Product Termination Notication (PTN) according to the JEDEC-Standard we will inform at an early stage about inevitable product discontinuance. According to this, we cannot ensure that all products within our product range will always be available. Therefore, it needs to be veried with the eld sales engineer or the internal sales person in charge about the current product availability expectancy before or when the product for application design-in disposal is con-
sidered. The approach named above does not apply in the case of individual agreements deviating from the foregoing for customer-specic products. 20.7 Property rights All the rights for contractual products produced by Wrth Elektronik eiSos GmbH & Co. KG on the basis of ideas, development contracts as well as models or templates that are subject to copyright, patent or commercial protection supplied to the customer will remain with Wrth Elektronik eiSos GmbH & Co. KG . Wrth Elektronik eiSos GmbH & Co. KG does not warrant or represent that any license, either expressed or implied, is granted under any patent right, copyright, mask work right, or other intellectual property right relating to any combination, application, or process in which Wrth Elektronik eiSos GmbH & Co. KG components or services are used. 20.8 General terms and conditions Unless otherwise agreed in individual contracts, all orders are subject to the current ver-
sion of the "General Terms and Conditions of Wrth Elektronik eiSos Group", last version available at www.we-online.com. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 152 21 Legal notice 21.1 Exclusion of liability Wrth Elektronik eiSos GmbH & Co. KG considers the information in this document to be correct at the time of publication. However, Wrth Elektronik eiSos GmbH & Co. KG re-
serves the right to modify the information such as technical specications or functions of its products or discontinue the production of these products or the support of one of these products without any written announcement or notication to customers. The customer must make sure that the information used corresponds to the latest published information. Wrth Elektronik eiSos GmbH & Co. KG does not assume any liability for the use of its product-
s. Wrth Elektronik eiSos GmbH & Co. KG does not grant licenses for its patent rights or for any other of its intellectual property rights or third-party rights. Notwithstanding anything above, Wrth Elektronik eiSos GmbH & Co. KG makes no representations and/or warranties of any kind for the provided information related to their accuracy, correctness, completeness, usage of the products and/or usability for customer applications. Information published by Wrth Elektronik eiSos GmbH & Co. KG regarding third-party products or services does not constitute a license to use such products or services or a warranty or endorsement thereof. 21.2 Suitability in customer applications The customer bears the responsibility for compliance of systems or units, in which Wrth Elektronik eiSos GmbH & Co. KG products are integrated, with applicable legal regulation-
s. Customer acknowledges and agrees that it is solely responsible for compliance with all legal, regulatory and safety-related requirements concerning its products, and any use of Wrth Elektronik eiSos GmbH & Co. KG components in its applications, notwithstanding any applications-related in-formation or support that may be provided by Wrth Elektronik eiSos GmbH & Co. KG . Customer represents and agrees that it has all the necessary ex-
pertise to create and implement safeguards which anticipate dangerous consequences of failures, monitor failures and their consequences lessen the likelihood of failures that might cause harm and take appropriate remedial actions. The customer will fully indemnify Wrth Elektronik eiSos GmbH & Co. KG and its representatives against any damages arising out of the use of any Wrth Elektronik eiSos GmbH & Co. KG components in safety-critical applications. 21.3 Trademarks AMBER wireless is a registered trademark of Wrth Elektronik eiSos GmbH & Co. KG . All other trademarks, registered trademarks, and product names are the exclusive property of the respective owners. 21.4 Usage restriction Wrth Elektronik eiSos GmbH & Co. KG products have been designed and developed for usage in general electronic equipment only. This product is not authorized for use in equip-
ment where a higher safety standard and reliability standard is especially required or where a failure of the product is reasonably expected to cause severe personal injury or death, unless the parties have executed an agreement specically governing such use. Moreover, AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 153 Wrth Elektronik eiSos GmbH & Co. KG products are neither designed nor intended for use in areas such as military, aerospace, aviation, nuclear control, submarine, transportation
(automotive control, train control, ship control), transportation signal, disaster prevention, medical, public information network etc. Wrth Elektronik eiSos GmbH & Co. KG must be informed about the intent of such usage before the design-in stage. In addition, sufcient reliability evaluation checks for safety must be performed on every electronic component, which is used in electrical circuits that require high safety and reliability function or perfor-
mance. By using Wrth Elektronik eiSos GmbH & Co. KG products, the customer agrees to these terms and conditions. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 154 22 License agreement for Wrth Elektronik eiSos GmbH & Co. KG connectivity product rmware and software Agreement between You and Wrth Elektronik eiSos GmbH & Co. KG The following terms of this license agreement for the usage of the Wrth Elektronik eiSos GmbH & Co. KG wireless connectivity product rmware are a legal agreement between you and Wrth Elektronik eiSos GmbH & Co. KG and/or its subsidiaries and afliates (collective-
ly, "Wrth Elektronik eiSos "). You hereby agree that this license agreement is applicable to the product and the incorporated software and rmware (collectively, "Firmware") made available by Wrth Elektronik eiSos in any form, including but not limited to binary, exe-
cutable or source code form. The Firmware included in any Wrth Elektronik eiSos wireless connectivity product is pur-
chased to you on the condition that you accept the terms and conditions of this license agreement. You agree to comply with all provisions under this license agreement. 22.1 Limited license Wrth Elektronik eiSos hereby grants you a limited, non-exclusive, non-transferable and royalty-free license to use the Firmware under the conditions that will be set forth in this license agreement. You are free to use the provided Firmware only in connection with one of the products from Wrth Elektronik eiSos to the extent described in this license agreement. You are not entitled to change or alter the provided Firmware. You are not entitled to transfer the Firmware in any form to third parties without prior written consent of Wrth Elektronik eiSos . You are not allowed to reproduce, translate, reverse engineer, read out, decompile, disas-
semble or create derivative works of the incorporated Firmware in whole or in part. No more extensive rights to use and exploit the Firmware granted to you. 22.2 Usage and obligations The responsibility for the applicability and use of the Wrth Elektronik eiSos wireless con-
nectivity product with the incorporated Firmware in a particular customer design is always solely within the authority of the customer. Due to this fact, it is up to you to evaluate and investigate, where appropriate, and to decide whether the device with the specic product characteristics described in the product specication is valid and suitable for your respective application or not. You are responsible for using the Wrth Elektronik eiSos Product with the incorporated Firmware in compliance with all applicable product liability and product safety laws. You acknowledge to minimize the risk of loss and harm to individuals and bear the risk for failure leading to personal injury or death due to your usage of the product. Wrth Elektronik eiSos products with the incorporated Firmware are not authorized for use in safety-critical applications, or where a failure of the product is reasonably expected to cause severe personal injury or death. Moreover, Wrth Elektronik eiSos products with the incorporated Firmware are neither designed nor intended for use in areas such as military, aerospace, aviation, nuclear control, submarine, transportation (automotive control, train AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 155 control, ship control), transportation signal, disaster prevention, medical, public information network etc. You shall inform Wrth Elektronik eiSos about the intent of such usage before design-in stage. In certain customer applications requiring a very high level of safety and in which the malfunction or failure of an electronic component could endanger human life or health, you must ensure to have all necessary expertise in the safety and regulatory ramica-
tions of your applications. You acknowledge and agree that you are solely responsible for all legal, regulatory and safety-related requirements concerning your products and any use of Wrth Elektronik eiSos products with the incorporated Firmware in such safety-critical ap-
plications, notwithstanding any applications-related information or support that may be pro-
vided by Wrth Elektronik eiSos . YOU SHALL INDEMNIFY WRTH ELEKTRONIK EISOS AGAINST ANY DAMAGES ARISING OUT OF THE USE OF WRTH ELEKTRONIK EISOS PRODUCTS WITH THE INCORPORATED FIRMWARE IN SUCH SAFETY-CRITICAL AP-
PLICATIONS. 22.3 Ownership The incorporated Firmware created by Wrth Elektronik eiSos is and will remain the exclu-
sive property of Wrth Elektronik eiSos . 22.4 Firmware update(s) You have the opportunity to request the current and actual rmware for a bought wireless connectivity Product within the time of warranty. However, Wrth Elektronik eiSos has no obligation to update a modules rmware in their production facilities, but can offer this as a service on request. The upload of rmware updates falls within your responsibility, e.g. via ACC or another software for rmware updates. Firmware updates will not be communicated automatically. It is within your responsibility to check the current version of a rmware in the latest version of the product manual on our website. The revision table in the product manual provides all necessary information about rmware updates. There is no right to be provided with binary les, so called "rmware images", those could be ashed through JTAG, SWD, Spi-Bi-Wire, SPI or similar interfaces. 22.5 Disclaimer of warranty THE FIRMWARE IS PROVIDED "AS IS". YOU ACKNOWLEDGE THAT WRTH ELEK-
TRONIK EISOS MAKES NO REPRESENTATIONS AND WARRANTIES OF ANY KIND RELATED TO, BUT NOT LIMITED TO THE NON-INFRINGEMENT OF THIRD PARTIES INTELLECTUAL PROPERTY RIGHTS OR THE MERCHANTABILITY OR FITNESS FOR YOUR INTENDED PURPOSE OR USAGE. WRTH ELEKTRONIK EISOS DOES NOT WARRANT OR REPRESENT THAT ANY LICENSE, EITHER EXPRESS OR IMPLIED, IS GRANTED UNDER ANY PATENT RIGHT, COPYRIGHT, MASK WORK RIGHT, OR OTHER INTELLECTUAL PROPERTY RIGHT RELATING TO ANY COMBINATION, MACHINE, OR PROCESS IN WHICH THE WRTH ELEKTRONIK EISOS PRODUCT WITH THE INCOR-
PORATED FIRMWARE IS USED. INFORMATION PUBLISHED BY WRTH ELEKTRONIK EISOS REGARDING THIRD-PARTY PRODUCTS OR SERVICES DOES NOT CONSTI-
TUTE A LICENSE FROM WRTH ELEKTRONIK EISOS TO USE SUCH PRODUCTS OR SERVICES OR A WARRANTY OR ENDORSEMENT THEREOF. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 156 22.6 Limitation of liability Any liability not expressly provided by Wrth Elektronik eiSos shall be disclaimed. You agree to hold us harmless from any third-party claims related to your usage of the Wrth Elektronik eiSos products with the incorporated Firmware. Wrth Elektronik eiSos disclaims any liability for any alteration, development created by you or your customers as well as for any combination with other products. 22.7 Applicable law and jurisdiction Applicable law to this license agreement shall be the laws of the Federal Republic of Ger-
many. Any dispute, claim or controversy arising out of or relating to this license agreement shall be resolved and nally settled by the court competent for the location of Wrth Elek-
tronik eiSos registered ofce. 22.8 Severability clause If a provision of this license agreement is or becomes invalid, unenforceable or null and void, this shall not affect the remaining provisions of the agreement. The parties shall replace any such provisions with new valid provisions that most closely approximate the purpose of the agreement. 22.9 Miscellaneous This license agreement constitutes the entire understanding and merges all prior discussions between the parties relating to this license agreement. No ancillary verbal agreements have been made and no such agreements shall be valid. Any additions and amendments to this license agreement shall require the written form in order to be binding. We recommend you to be updated about the status of new rmware, which is available on our website or in our data sheet, and to implement new rmware in your device where appropriate. In case only rmware is provided, we expressly exclude the automatic receipt of PCN information. Thus, new rmware will also not be provided automatically. By ordering a wireless connectivity Product, you accept this license agreement in all terms. AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 157 List of Figures 3 1 2 14 11 Block diagram . Current consumption calculation in advertising mode with 40ms advertising interval, UART disabled . Measured AMB2623 transient current consumption in advertising mode with 40ms advertising interval, excerpt of 5ms . 15 Pinout (top view)
. 18 4 Power up . 21 5 State overview . 26 6 Layout . 130 7 Placement of the module with integrated antenna . 131 8 Dimensioning the antenna feed line as micro strip . 131 9 10 AMB1981: 868 MHz dipole-antenna . 134 11 AMB1982: 868 MHz magnet foot antenna with 1.5 m antenna cable . 135 12 AMB1926: 2.4 GHz dipole-antenna . 136 13 Reow soldering prole . 138 14 Module dimensions [mm]
. 142 15 Footprint [mm]
. 143 Lot number structure . 144 16 List of Tables 11 Ordering information . 1 12 Recommended operating conditions . 2 12 Absolute maximum ratings
. 3 13 Power consumption for 100% transmission/reception . 4 16 Radio parameters . 5 16 Output power . 6 17 Pin characteristics . 7 19 Pinout
. 8 27 9 LED behavior of the AMB2623 . 76 10 Message overview: Requests . 77 11 Message overview: Conrmations . 78 12 Message overview: Indications . 80 13 nRF52832 IC revision overview . 89 14 Security conguration ags . 92 15 Scan conguration ags . 16 Beacon conguration ags 94
. 17 Table of settings (Part 1) . 118 18 Table of settings (Part 2) . 119 19 Compatibility matrix . 127 20 Classication reow soldering prole, Note: refer to IPC/JEDEC J-STD-020E 137 21 Package classication reow temperature, PB-free assembly, Note: refer to IPC/JEDEC J-STD-020E . 138 22 Dimensions . 141 23 Weight . 141 Lot number details . 144 24 AMB2623 reference manual version 1.0 www.we-online.com/wireless-connectivity July 2018 158 Monitoring& ControlAutomated Meter ReadingInternet of Things more than you expectContact:Wrth Elektronik eiSos GmbH & Co. KGDivision Wireless Connectivity & SensorsRudi-Schillings-Str. 3154296 TrierGermanyTel.: +49 651 99355-0Fax.: +49 651 99355-69www.we-online.com/wireless-connectivity
This product uses the FCC Data API but is not endorsed or certified by the FCC