BL654 Series Bluetooth Module with NFC

Recommended for New Design (RND)

Overview

March 2021 – Added 802.15.4 certification for FCC/ISED/EU

Building on Laird Connectivity’s expertise with Nordic from the BL600 and BL652 series comes the most powerful yet -the BL654 series! It provides OEMs with the maximum design flexibility and performance. A complete multi-protocol embedded wireless offering with exceptional processing capability, all at a micro power budget. Powered by Nordic’s nRF52840 silicon, the small form factor BL654 modules, DVKs and USB Dongle provide for a secure, robust Bluetooth LE and Cortex -M4F CPU for any OEM’s product design. The BL654 provides you with maximum development flexibility with programming options for the Nordic SDK, a simple, intuitive AT Command Set, as well as Laird Connectivity’s own smartBASIC environment.

The BL654 series brings out all nRF52840 hardware features and capabilities including USB access, up to 5.5V supply considerations, and 802.15.4 (Thread) implementation. Complete regulatory certifications enable faster time to market and reduced development risk completes Laird Connectivity’s simplification of your next Bluetooth design!

 

Secure, Efficient, and Optimized

  • Bluetooth 5.1 & Thread (802.15.4) - Bluetooth Low Energy (LE) plus NFC, featuring Nordic nRF52840

  • Widest Range of Configurable Interfaces - UART, I2C, SPI, ADC, GPIO, PWM, FREQ, USB, and NFC

  • 2Mbps & LE Long Range - Support for 2 Mbps, 1 Mbps, and 125 kps coded

  • Hostless Operation with Powerful Core - Internal MCU reduces BOM and Cortex-M4F (1 Mbit Flash, 256k RAM)

  • Application Design Choice - Leverage Laird Connectivity’s smartBASIC, simple AT Command Set or utilize Nordic SDK directly

  • USB Dongle Option - Packaged USB Adapter – bring full Bluetooth 5.1 connectivity to ANY device with a virtual COM port capability

Multiple Options for Design Flexibility

PCB Module

BL654 PCB Modules.jpg

USB Adapter

BL654-USB.jpg

A Kit That Delivers Just What You Need

Laird’s BL654 development kits provide a platform for rapid prototyping of BL654 modules. The development boards provide simple, easy-to-use access to the various hardware interfaces and configuration options for the modules. These DVKs are the perfect platform to provide early development testing of BL654 features and functionality.

  1. DVK Unit
  2. External NFC Antenna
  3. FlexPIFA Antenna (455-00002 DVK only)
  4. Fly Leads (x6)
  5. USB-A to Micro-USB Cable
  6. DVK Board Standoffs
bl654-devkit-contents.png

Endless Applications

  • IoT Devices and Sensors

    IoT Devices and Sensors

  • Beacons and Proximity Applications

    Beacons and Proximity Applications

  • Secure Medical Peripherals

    Secure Medical Peripherals

  • Industrial Monitoring

    Industrial Monitoring

Getting Started with Zephyr on the BL652/BL654

The BL652 and BL654 support many development options - software support for Laird Connectivity’s smartBASIC, simple AT Command Set, and the Nordic SDK. We've also recently added support for Zephyr RTOS. See the video below for details. 

Specifications

Bluetooth Version
5.1
Chipset
Nordic nRF52840
Antenna Options
Integrated (451-00001, 451-00003) or External via IPEX MH4 (451-00002)
BLE Connections
20
BT Class
1
Central Role
Yes
Certifications
FCC, ISED, EU, UKCA, MIC, AS-NZS, Bluetooth SIG
Compliance
RoHS, REACH
Development Tools
Utilities include UWTerminalX, Android and iOS applications with free source code, UART firmware upgrade
Dimension (Height - mm)
2.2 mm
Dimension (Length - mm)
15 mm
Dimension (Width - mm)
10 mm
Dual Mode
No
Link Budget
103 dB @ Bluetooth LE 1 Mbps (conducted)
Logical Interfaces
UART, I2C, SPI, ADC, PDM, GPIO, USB
NFC
Yes
Operating Temp (Max) (°C)
85
Operating Temp (Min) (°C)
-40
Peripheral Role
Yes
Processor On Board
Cortex M4F
Programming Options
smartBASIC, Nordic SDK, or simple AT Command Set
Receive Sensitivity
-95 dBm (1 mpbs)
Stack On Board
Yes
Transmit Power
8 dBM (max.) Configurable down to -40 dBm
Part NumberAdditional DescriptionAntenna OptionsAntenna TypeBulk or SingleChipset (Wireless)Dimension (Height - mm)Dimension (Length - mm)Dimension (Width - mm)Frequency Range (Max)Frequency Range (Min)Frequency Range 2 (Max)Frequency Range 2 (Min)Logical InterfacesOS/SoftwareProduct TypeProgramming OptionsSystem ArchitectureTechnologyTypeUSB
BL654 Series
451-00001
Recommended for New Design (RND)
Buy Now
Internal Bulk - Tape/Reel Nordic nRF52840 2480 MHz2402 MHz13.56 MHz13.56 MHzSerial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB Nordic SDK, smartBASIC, AT Commands, Zephyr Embedded Module Hostless Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee Module
BL654 Series
451-00002
Recommended for New Design (RND)
Buy Now
IPEX MHF4 External Bulk - Tape/Reel Nordic nRF52840 2480 MHz2402 MHz13.56 MHz13.56 MHzUART, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM UwTerminalX (Windows/Linux/Mac), Nordic SDK, smartBASIC, AT Commands, Zephyr Embedded Module Hostless Bluetooth 5.1, Single Mode (BLE), NFC Module
BL654 Series
451-00001C
Recommended for New Design (RND)
Buy Now
Internal Bulk - Cut Tape Nordic nRF52840 2480 MHz2402 MHz13.56 MHz13.56 MHzSerial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB Nordic SDK, smartBASIC, AT Commands, Zephyr Embedded Module Hostless Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee Module
BL654 DVK Box Contents - Square
455-00001
Recommended for New Design (RND)
Buy Now
Internal Single Nordic nRF52840 2480 MHz2402 MHz13.56 MHz13.56 MHzSerial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB Nordic SDK, smartBASIC, AT Commands, Zephyr Development Kit Hostless Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee Development Board
DVK BL654 Box Contents (square)
455-00002
Recommended for New Design (RND)
Buy Now
IPEX MHF4 External Single Nordic nRF52840 2480 MHz2402 MHz13.56 MHz13.56 MHzSerial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB Nordic SDK, smartBASIC, AT Commands, Zephyr Development Kit Hostless Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee Development Board
BL654 Series
451-00002C
Recommended for New Design (RND)
Buy Now
IPEX MHF4 External Bulk - Cut Tape Nordic nRF52840 2480 MHz2402 MHz13.56 MHz13.56 MHzSerial, GPIO, ADC, I2C, SPI, PCM, I2S, NFC, PWM, USB Nordic SDK, smartBASIC, AT Commands, Zephyr Embedded Module Hostless Bluetooth 5.1, Single Mode (BLE), NFC, 802.15.4 / Thread / Zigbee Module
BL654-USB with smartBASIC
451-00003
Recommended for New Design (RND)
Buy Now
Internal Single Nordic nRF52840 11 mm50.74 mm18.39 mm2480 MHz2402 MHz13.56 MHz13.56 MHzSerial (UART) smartBASIC, AT Commands USB Adapter smartBASIC, AT Command Set, (Nordic SDK not supported) Hostless Bluetooth 5.1, Single Mode (BLE), 802.15.4 / Thread / Zigbee Pluggable USB Adapter FTDI Based - Virtual COM Port
BL654-USB with Nordic SDK
451-00004
Recommended for New Design (RND)
Buy Now
Internal Single Nordic nRF52840 11 mm50.74 mm18.39 mm2480 MHz2402 MHz13.56 MHz13.56 MHzSerial (USB) Nordic SDK, Zephyr USB Adapter Zephyr / Nordic SDK Hostless Bluetooth 5.1, Single Mode (BLE), 802.15.4 / Thread / Zigbee Pluggable USB Adapter
USB-SWD Programming Kit - Box Contents
453-00062-K1Buy Now
USB-SWD Programming Kit: Includes mainboard, TC2050-IDC Tag Connect cable, 10-pin flat IDC cable, 1.2 m USB cable, and 2-pin jumper

Documentation

Name Part Type Last Updated
Product Brief - BL654 Series All Product Brief 10/11/2021
Product Brief - BL654 USB for Nordic SDK / Zephyr All Product Brief 10/11/2021
Product Brief - BL654 USB with smartBASIC All Product Brief 10/11/2021
Datasheet - BL654 All Datasheet 12/22/2021
User Guide - BL654 USB with smartBASIC All Documentation 05/18/2021
User Guide & Quick Start Guide - BL654 DVK All Documentation 05/18/2021
User Guide - smartBASIC Core Functionality v3.4 All Documentation 06/22/2020
BL654 smartBASIC Extensions Guide v29.1.1.0 All Documentation 08/15/2019
BL654 smartBASIC Extensions Guide v29.2.2.0 All Documentation 08/15/2019
BL654 smartBASIC Extensions Guide v29.3.3.0 All Documentation 08/15/2019
Quick Start Guide - BL65x AT Interface All Documentation 02/12/2021
Throughput Testing with BT 5 - LE 2M PHY Feature v1 0.pdf All Application Note 01/17/2019
Using the DVK-BL654 and Nordic SDK v1 0.pdf All Application Note 01/17/2019
Using vSP Service with smartBASIC v1 0.pdf All Application Note 01/17/2019
BLE Data Transfer - CODED PHY Modulation - BL654 v1 0.pdf All Application Note 01/17/2019
Application Note - Using Direct Test Mode - BL654 All Application Note 07/21/2021
Textpad Color Syntax Highlighting - BL654 v1 0.pdf All Application Note 01/17/2019
Upgrading BL654 Firmware via UART - BL654 v1 0.pdf All Application Note 01/17/2019
Upgrading BL654 Firmware via JTAG - BL654 v1 0.pdf All Application Note 01/17/2019
Using BL654 DVK with Nordic nRFToolbox v1 1.pdf All Application Note 01/17/2019
Using Notepad and Color Syntax Highlighting - BL654 v1 0.pdf All Application Note 01/17/2019
Low Power Modes - BL654 v1 1.pdf All Application Note 01/17/2019
NFC Manager - BL654 Sample smartBASIC Application v1 0.pdf All Application Note 01/17/2019
Laird Range Testing - BL654 v1.1.pdf All Application Note 09/16/2019
Exiting DTM Mode - BL654 v1 0.pdf All Application Note 01/17/2019
Loading and Running Applications with UwTerminalX - BL654 v1 1.pdf All Application Note 01/17/2019
NEW - BLE Mesh – BL654 smartBASIC Implementation - MESH310_8 r1 All Application Note 06/10/2019
RoHS 3 - Bluetooth All Certification 01/04/2022
Getting Started with the BL654 Dongle (smartBASIC variant) v1_1 All Documentation 06/10/2019
CS-RN-BL654-v29.1.1.0.pdf All Documentation 01/17/2019
PCB Footprint for ASCII and DXF format - BL654.zip All Technical Drawings 10/13/2020
SCH Symbol for OrCAD format - BL654.zip All Technical Drawings 01/17/2019
BL654 Firmware v29.2.2.0 r0.zip All Software 01/17/2019
3D Models - BL654.zip All Technical Drawings 01/17/2019
Mechanical Schematic - BL654 Series.pdf All Technical Drawings 01/17/2019
Host Land Pattern Schematic - BL654 Series.pdf All Technical Drawings 01/17/2019
Schematics - DVK-BL654 v1.0.pdf All Technical Drawings 01/17/2019
Application Note - Laird Custom BLE Serial Port Service All Application Note 06/21/2022
BL654 FIrmware for Upgrade v29.1.1.0 r0 All Software 01/17/2019
NEW - BL654 Firmware For Upgrade v29.3.31.8-MESH310-8 r1 All Software 06/10/2019
BL654 Firmware for Upgrade v29.3.3.0 r0 All Software 01/17/2019
BL654 Firmware for Upgrade v29.3.5.0 All Software 08/15/2019
Application Note - Guidelines for Replacing Antennas v1.0 All Application Note 01/17/2019
PCN 4B-2019 - BL654 Series All Documentation 08/23/2021
MIC Certifications - BL654 Module All Certification 10/03/2022
FCC Certifications - BL654 Module All Certification 03/15/2021
AS/NZS Certifications - BL654 Module All Certification 12/11/2020
EU Certifications - BL654 Module All Certification 01/13/2021
ISED (Canada) - Certifications - BL654 Module All Certification 03/15/2021
User Guide - BL654 USB for Nordic SDK / Zephyr All Documentation 07/23/2020
BL654 smartBASIC Extensions Guide v29.3.5.0 All Documentation 08/15/2019
Application Note - Creating a Secure Bootloader Image (BL654-USB) All Application Note 10/01/2019
Application Note - Using the BL654 and Nordic SDK v16.0.0 with Eclipse and GCC All Application Note 11/27/2019
BL654 smartBASIC Extensions Guide v29.4.6.0 All Documentation 03/20/2020
BL654 FIrmware for Upgrade v29.4.6.0 r0 All Software 12/09/2019
Application Note - Bootloader UART Protocol - BL6xx All Application Note 08/16/2021
Datasheet - NFC Flex PCB Antenna All Datasheet 11/17/2022
CAD Files - 451-00003 (USB Adapter - smartBASIC) All Technical Drawings 04/17/2020
CAD Files - 451-00004 (USB Adapter - Nordic/Zephyr) All Technical Drawings 04/17/2020
User Guide - Repeater/Gateway Application All Documentation 02/16/2022
UwTerminalX – Serial Terminal Utility All Software 04/27/2020
UwFlashX – Serial Firmware Update Utility All Software 04/27/2020
Application Note - Using UART Efficiently to Extend Battery Life (BL65x) All Application Note 06/04/2020
BL654/BL654PA Firmware for Upgrade v29.4.6.6 r1 All Software 07/29/2021
Application Note - How to Set Up vSP Service - BLxx All Application Note 07/31/2020
DoC - BL654 Bluetooth USB Adapter All Certification 08/13/2020
PCN 9A-2020 - BL654 Series All Documentation 09/23/2020
AS/NZS Certifications - BL654-USB All Certification 12/14/2020
EU Certifications - BL654-USB All Certification 12/14/2020
FCC Certifications - BL654 Dongle All Certification 12/14/2020
ISED (Canada) - BL654-USB All Certification 12/14/2020
BL654/BL654PA Firmware for Upgrade v29.5.7.2.r2 All Software 01/15/2021
Release Notes - BL654/BL654PA v29.5.7.2 r0 All Documentation 01/18/2021
User Guide - BL65x AT Interface Application All Documentation 09/19/2022
Regulatory Information - BL654 All Certification 06/14/2022
BL654/BL654PA smartBASIC Extensions Guide v29.5.7.2 All Documentation 03/02/2022
Application Note - BL654 Bluetooth v5 Adapter as a BLE Sniffer All Application Note 02/04/2021
BL654 PCB footprint (DXF and Altium format) All Technical Drawings 12/22/2021
smartBASIC Applications Migration Guide - BL65x All Documentation 03/09/2021
FCC/ISED/EU Modular Approval (C2PC) - 802.15.4 (March 2021) All Certification 03/16/2021
Regulatory Information - BL654 Dongles All Certification 02/22/2022
ISED ICES-003 Issue 7 Declaration of Compliance All Certification 05/18/2021
Application Note - GATT Table with AT Interface Application All Application Note 06/09/2021
PCN 8J-2021 - BL653/BL653µ/BL654 All Documentation 09/07/2021
BL654 SCH symbol (Altium format) All Technical Drawings 12/22/2021
Application Note - BT 5.x Feature Comparison for Laird Connectivity Bluetooth Modules All Application Note 11/17/2022
KC Certifications - BL654 Module All Certification 06/01/2022
Application Note - DTM Configuration Using AT Commands - BL65x Series All Application Note 09/14/2022

Certified Antennas

  • EFA2400A3S-10MH4L

    EFA2400A3S-10MH4L

    mFlexPIFA Flexible Adhesive-Backed PIFA Internal Antenna
    Learn More
  • 001-0022

    001-0022

    FlexPIFA / FlexPIFA 6E Flexible Adhesive-Backed PIFA Internal Antennas
    Learn More
  • 001-0023

    001-0023

    FlexNotch 2.4 GHz Antenna
    Learn More
  • 0600-00061

    0600-00061

    NFC Flex PCB Antenna
    Learn More

FAQ

How many concurrent connections I can get with BL654 loaded with AT Commands interface app code?

The default maximum numbers of BLE connection allowed with AT Commands is 8.

Assuming you are working with the AT Command interface application version 4.04 and Library version 5.02 or newer, you can reach until 16 concurrent BLE connections through non-VSP mode:

User-added image

To do so, you'll first need to set up your BL654 to non-VSP mode via S Register 100 (Start-up Flags) then increase the maximum allowable concurrent connections within S Register 126 (Max Connections as Master/Central) as follows:

User-added image

You'll then be able to connect to until 15 BLE devices as master (AT+LCON) plus 1 as slave (AT+LADV) as follows:

User-added image

Please note that multiple connections means sharing bandwidth where latency and throughput will be significantly impacted.

How can I connect a BL654 (loaded with smartBASIC AT Commands) to a BT510?

The BT510 is an event driven BLE multi-sensors which is capable of measuring temperature, open/close magnet and motion detection. There is basically two ways to get data from it:

  • Advertisements
  • Connection

While the BT510 as been especially designed to transfer data via BLE advertisements, you can also use BLE connection to retrieve data. It's worth mentioning that preliminary intended use of BLE connection with the BT510 is for configuration (usually during commissioning process on the field). As exposed into the Sentrius™ BT510 User Guide section 4.2, the BT510 make use of BLE Virtual Serial Port (VSP) service.

The BL654 is BLE v5.1 module which embeds an nRF52840 chipset from Nordic. Laird Connectivity developed smartBASIC, an event driven programming language that sits on top of Nordic SDK. Its most famous software/feature is the AT Commands Interface where you can drive a BLE module through UART with using batch of intuitive commands.

As part of IoT applications that involve to interact with a BT510 via BLE through a BL654 loaded with AT Command Interface, it can be useful to know the steps to get the BL654 connected to the BT510.

Because the BT510 GATT table is protected by a pairing process which involve static passkey (123456), it's important to change BL654 IOCAP in first instance to allow a Passkey entry procedure during pairing/bonding process.

On the BL654 side you'll need to follow the procedure below with AT Commands :

  • Change BL654 IOCAP setting either on 2 (Keyboard only) or 4 (Keyboard+Display)
  • Engage a non-VSP connection (AT+LCON)
  • Engage a pairing/bonding process with AT+PAIR 1
  • Issue BT510 passkey as part of the pairing/bonding process with AT+PRSP 1,123456
  • Disconnection from non-VSP connection (AT+LDSC 1)
  • Reconnect with VSP connection (ATD)

Now that both devices are connected with VSP mode, you can write JSON commands to send over BL654 UART in order to configure the BT510 as you like. For more information on JSON spec, you can have a look here :  https://www.jsonrpc.org/specification

A typical AT Commands session could look like this, where 01C630157769EE is a BT510 BLE Mac Address:

ATS 107=4 
OK
AT&W
OK
ATZ
OK
AT+LCON 01C630157769EE
connect 1,01C630157769EE,15000,6000000,0
AT+PAIR 1
OK
passkey? 1
AT+PRSP 1,123456
encrypt 1
AT+LDSC 1
discon 1,22

// BL654 is now bonded to BT510, VSP connection can be made.

ATD 01C630157769EE
ENCRYPT
CONNECT 0,01C630157769EE,15000,6000000,0

Can I load OTA application code into my BL654 USB Dongle P/N 451-00003?

To be able to load an application code Over the Air into a BL654, you need to enter into Virtual Serial Port Command mode. The only way to enter into this mode is to have access to the VSP pin (SIO_02) and pull it to VCC.

User-added image

The BL654 USB Dongle P/N 451-00003 doesn't expose VSP pin which is tied to the ground internally. There is hence no way to enter into Virtual Serial Port Command mode and to load an application code Over the Air on that product.

Can I use the BL654 USB Dongle as USB HCI Bluetooth device?

There exist two variants of the BL654 dongle:

  • 451-00003 is the SmartBASIC driven version which uses an FTDI USB UART converter for USB connection.
  • 451-00004 is the Nordic version which leverages the nRF52840 native USB device interface.

Whereas the SmartBASIC version cannot be used anything different than a virtual serial port device from a USB perspective, the Nordic version could be programmed for different USB device classes.
The Zephyr project provides various sample application projects including a Bluetooth usb_hci project. Since the BL654 USB Nordic dongle is a supported board in Zephyr it is possible to compile and load the usb_hci project into the dongle. After doing so, the dongle will operate as a Bluetooth HCI device and enumerate on USB accordlingly. Please follow the general build instructions for Zephyr and the programming/flashing instructions for the BL654 USB dongle.

Does the BL65x or BL5430 support Matter?

Matter can be supported on the BL5340 (nRF52840) and the BL654 when using the Nordic nRF Connect SDK. However, due to the memory requirements of Matter it can not be used on the BL653, BL652 nor the BL651 given their flash and RAM memory footprint.The BL653 (nRF52833) has 512K of Flash and 128K of RAM and BL652 and BL651 has less than that.

There are instructions on how to reduce the memory footprint for Matter in the documentation on the nRF Connect SDK Main branch, Memory footprint optimization » Matter, but even using this you will not be able to get it down to a size fitting on the nRF52833. With the steps from the optimization page with the light bulb sample the size was reduced to approximately 730 kB of flash and 170 kB of RAM when building for nRF52840, which is still way too high for the nRF52833. Additionally, there are possibilities that the Matter flash usage will grow more before the official release, as more bug fixes and things from the Matter specification will be added.

Why can’t I Re-open the UART when it closes when running AT Interface LPUART App?

The LPUART AT Interface app allows users to close down the UART port when entering low power Doze mode for additional power savings. The UART when it is open can consume as much as 350uA. The AT Interface LPUART app provides a cross-compile switch that allows the UART to close most of the time when there is no activity and the Tx/Rx buffers are empty. A “Keep UART Open” is implemented by using a GPIO that when low allows the UART to close after a low power operation timer has expired. When this Keep UART Open GPIO signal is high the UART will not close automatically.

The AT Interface Application sets the default GPIO used for this function to SIO_24. An application can chose any pin other than the default by writing the desired SIO port number to Sreg 109.

The BL65x EVK connects SIO_24 to Button 3. However, if running the AT Interface LPUART application on the EVK the UART will close automatically as soon as the low power timer expires (default set to 5 seconds). The UART can not be re-opened in the case. To reduce power the application configures the Keep UART Open GPIO to input pulldown. However, to operate properly Button 3 when pressed will pull the signal to ground which results in an Event interrupt. Since the GPIO uses an input pulldown it is already low and no Event occurs leaving the UART closed.

A simple change in $LIB$.AT.interface can be made to configure Keep UART Open GPIO to input pullup. This keeps the GPIO high at all times and the UART open. When Button 3 is pressed long enough for the low power time to expire the UART is closed. To re-open the UART Button 3 is pressed again which causes an Event which will re-open the UART.

Change the following line in InitGpio() function in $LIB$.AT.interface:

From:

rc = GpioSetFunc(vspCmdModePin, SIOTYPE_DIN, INPUT_PULL_DOWN)

To:

rc = GpioSetFunc(vspCmdModePin, SIOTYPE_DIN, INPUT_PULL_UP)

Also to change the functionality so once the UART is closed is remains closed until the next button press also change the next line in InitGpio().

From:

rc = GpioAssignEvent(0, vspCmdModePin, 0)

To:

rc = GpioAssignEvent(0, vspCmdModePin, 1)

How to avoid/disable module reset on UART break with SmartBASIC?

The default behaviour of the SmartBASIC driven BLE modules is entering deep sleep mode when a UART break condition is being detected and wake up through reset when released. While this is a convenient way to reset a module without having access to the reset line e.g., during development when connected with UwTerminalX, it might be unintended in the final application environment.

For the more recent SmartBASIC BLE modules like BL652, BL653, BL654, BL654PA the behaviour when detecting a UART break is configurable when opening the UART with UartOpen(). Character 9 in the stOptions string specifies the behaviour and it's possible to chose from entering deep sleep / reset, ignore the break or send an event EVUARTBREAK to the SmartBASIC application. See below table:

UartOpen() stOptions string
 

 

 

The default behaviour is entering deep sleep, hence you would have to close the uart and re-open it at the beginning of your application to apply changes to the behaviour.

See the SmartBASIC Extensions User Guides for each module for more details.

The BT900 dual-mode BT/BLE module does not offer configurability of the UART break behaviour and will always go to deep sleep and wake up through a reset.

How can I read out the MAC address from a BLE module during test/production?

A fast and convenient way to read out the MAC address of each module during a test/production process would be through SWD from FICR (Factory information configuration registers) registers DEVICEADDR[0] and DEVICEADDR[1]. The following command will read the MAC address from our BLE modules:

nrfjprog --memrd 0x100000A4 --w 8 --n 6

Please note that reading from memory through SWD will halt the CPU. If you need your application firmware to start afterwards (like for performing some test sequence) you would have to run the CPU with

nrfjprog –run

More information on FICR registers are available in the respective data sheets, like this for nRF52840 / BL654.

Is the BL5340 pin compatable with the BL654/653?

No, the BL5340 and BL653/BL654 are not the same pin mapping or layout, a whole new design is required for a PCB to have a BL5340 fitted. That being said, the reserved pins on the BL653/BL654 are:

  • QSPI (BL654 only, no QSPI on BL653)
  • SPIM4 (SPIM4 only, this is the high-speed SPI port at 32MHz)
  • TRACE
  • 32KHz Crystal
  • NFC

On the BL5340, the list is similar:

  • QSPI
  • SPIM4 (SPIM4 only, this is the high-speed SPI port at 32MHz)
  • I2C (only if they plan to use 1Mbps I2C which might be known as I3C?)
  • TRACE
  • 32KHz Crystal
  • NFC

Do I have to go through BT qualification if I use the BL654 dongle in my product?

It depends on how the BL654 dongle is being used.

As a consumer you are not required to go through the qualification program. You can buy any commercially available dongle, headset etc. For example, a Linux PC would have a Qualified and Declared Host Subsystem and the Dongle would be Qualified and Declared as a Controller Subsystem. Each part would have been Qualified and declared by the manufacturer who has agreed to the two licensing agreements.

If you include the BL654 in your own product, for example plugged into an internal USB port, then Yes, if you are selling the Dongle as part of a product and it supports Bluetooth functionality then you are required to go through the qualification program. In this case it should be Qualified, via the simple Declaration model.

The above also applies if you are plugging the BL654 into an external USB port as part of your product. The interface is irrelevant, it’s the use of the Bluetooth IP in your product that would trigger the need for Qualification.

If the BL654 is an optional part of your product then the Bluetooth option should be Qualified, via the simple Declaration model.

In summary:

If you are including some Bluetooth IP no matter what the interface used, and representing the product as your own then they would need to go through the Qualification and Declaration process, only a retailer who simply sells an already qualified and declared Bluetooth Product, manufactured by a 3rd party is exempt. If the retailer represented the product as their own, like Amazon branding a dongle, then they would have to go through the qualification process.

 

Do I still have to list/qualify my product with the BT SIG even if I don't use the BT logo?

Yes, you need to qualify/list any product that uses BT SIG intellectual property, even if you do not use the logo or require interoperability with other BT devices. see here for more details. Qualify Your Product | Bluetooth® Technology Website

 

How can a enable/disable particular BLE channels used for advertising/scanning or when in a connection?

The smartBASIC language provides functions for setting a specific set of channels to be used for BLE advertising/scanning or a BLE connection.

  • BleChannelMap(chanMap$) enables or disables data channel usage when in a connection.
  • BleAdvSetCreate(nSetId, nAdvProperties, nPriSecPhy, nFilterPolicy, peerAddr$, chanMask$) can set BLE advert channels.
  • BleScanStartEx(scanTimeoutMs, nPriPhyScan, chanMask$, nFilterHandle) can set channels used for BLE scanning.

The channel map/mask has to be entered as a 5 byte long string for each of the functions and due to the little-endian architecture of the underlying ARM core its composition can be confusing. The below example will show the actual assignment of channel within that string. Furthermore the meaning of a set bit differs among the above functions.

  • BleChannelMap() -> a set bit means channel is enabled!
  • BleAdvSetCreate() and BleScanStartEx() -> a set bit means channel is disabled!

Now let's “visualize” the channel mapping into the five byte string:

channel number:

00000000|11111100|22221111|33222222|xxx33333
76543210|54321098|32109876|10987654|xxx65432
\byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/

So for enabling e.g., channels 9+10 only you would set the yellow bits:

00000000|11111100|22221111|33222222|xxx33333
76543210|54321098|32109876|10987654|xxx65432
\byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/
 0x00     0x06     0x00     0x00     0x00

giving “0006000000” as string.

For disabling channel only 35, i.e. active channels are 0-34 and 36, it would be:

00000000|11111100|22221111|33222222|xxx33333
76543210|54321098|32109876|10987654|xxx65432
\byte 0/ \byte 1/ \byte 2/ \byte 3/ \byte 4/
  0xFF     0xFF     0xFF     0xFF     0x17

giving “FFFFFFFF17” as string.

Further detail is given in the smartBASIC Extension Guides in the documentation section of the product page for each BLE module at Bluetooth Module Portfolio.

Does Laird have example code for a Windows Demo App which enables scanning and connecting to Bluetooth Low Energy peripheral IoT devices?

Unfortunately, we do not have an example of a Windows Bluetooth Low Energy application. If you require assistance with developing a Windows Bluetooth Low Energy application please contact one of our Sales Experts and let them know you are interested in a Design Services engagement and we will be happy to discuss your application requirements and provide a quote.

What factors influence the actual TX rate of the controller?

The actual TX rate is influenced by the PDU and MTU sizes along with the Connection Intervals and Slave Latency.

Where can I find the appropriate arguments/parameters to use with the BleAttrMetadata() function used in many examples in the BL65x User Guide, as I only see BleAttrMetadataEx() listed which appears to have different arguments/parameters?

The BLEATTRMETADATA () function is intentionally not documented in the BL65x Extension User Guides for our BL65x series smartBASIC modules, as it is preferred that the ‘EX’ variant BLEATTRMETADATAEX () is used going forward. The two functions are primarily the same, however, the EX version enables more functionality with the nFlags argument as compared to the FlsVariableLen argument in the deprecated BLEATTRMETADATA () function. The non-EX version is still supported to ensure old apps using it still work, including the code examples referred to in the user guide.

If you are looking for specifics about the BLEATTRMETADATA () function, such as the arguments and returns specific to that function these can still be found in the BT900 smartBASIC Extensions User Guide (pg 228), or BL600 smartBASIC Extensions User Guide (pg 110).

Can Pullups or Pulldowns be Disabled on Default UART Pins

The BL65x is delivered with the smartBASIC runtime FW loaded and no smartBASIC application. In this configuration the module will boot into smartBASIC Interactive mode and the default pins for the UART at startup are set as per:

  • RTS: digital out, no pull, default high
  • TXD: digital out, no pull, default high
  • CTS: digital in, pull down
  • RXD: digital in, pull up

Startup flow is as follows:

  • sB engine starts
  • If there is no autorun application - UART is opened (default parameters)
  • If there is an autorun application - UART is not opened
    • If the autorun application uses print - UART is opened (default parameters)
    • If the autorun application uses UARTOPEN - UART is opened (custom parameters)

 

The pull up/down options can be changed in the smartBASIC application only when the UART is not open. If the $autorun application has opened the UART by using a print statement or calling UARTOPEN() then the UART must first be closed by calling the UARTCLOSE() function.

In the smartBASIC application when the UART port has been closed the code can call GpioSetFunc() to configure the desired GPIO parameters.

The smartBASIC application can use UARTOPEN() function to now enable the UART port. UARTOPEN() does not configure GPIO pull up/down configurations keeping the desired GPIO configurations intact.

How Can I Change the BL65x Tx Power Setting

The BL65x is delivered with the smartBASIC runtime FW loaded and no smartBASIC application. The BL65x will boot up in interactive mode and can be configured via AT Commands. In this mode the TX Power for both advertisements and connections is controlled via Config Register 109. This register is read from or written to via the AT+CFG AT command as is described in the BL654 smartBASIC Extensions Users Guide. However, Config register 109 is valid for Tx Power adjustment when Virtual Serial Port services is enabled.

If Virtual Serial Port Services is not enabled TX Power is configured via the BleTxPowerSet() function within a users smartBASIC application code. In this mode the current setting of Tx Power can be obtained from ATI register 2008 as described in the BL654 smartBASIC Extensions Users Guide

How many SPI Interfaces does the BL65x support

The BL654 Data sheet lists four SPI Interfaces (up to 8 Mbps) are supported. The data sheet is provided as a hardware guide and refers to the hardware itself. The Nordic nRF52840 MCU supports up to 4 SPI instances. However, the actual number of SPI interfaces depends on what SW is used for application development. If using smartBASIC for development there is one SPI instance that can be configured as SPI master.

The SPI port is opened via smartBASIC function SPIOPEN(). This function includes parameters that allow configuration of SPI Mode, SPI Clock Rate and SPI Flags. SPI pins cannot be configured and use the pins that are specified in the BL65x Data Sheet. Refer to smartBASIC Core Functionality Specification. SPI_CS is not controlled in smartBASIC firmware and must be controlled by the application through use of SIO pins.

For applications developed using Nordic SDK or Nordic Zephyr SDK the nRF528xx MCU supports up to 4 SPI Instances. There can be up to 4 SPI Master interfaces (SPIM Master) and up to 3 SPI Slave interfaces (SPIS) but not all at once. There are four total SPI interfaces and master/slave combinations are shared across those four instances. The nRF528xx also contains two I2C Instances which are shared with the two lower SPI instances via TWI. Refer to the latest nRF52xx data sheet for details.

How many I2C ports does the BL65x support

The BL65x Data sheet lists two I2C controllers (up to 400 Kbps) are supported. The data sheet is provided as a hardware guide and refers to the hardware itself. The Nordic nRF528xx BLE mcu’s support multiple I2C controllers. However, the actual number of I2C interfaces depends on what SW is used for application development. If using smartBASIC for development there is one I2C instance and that instance is a master, there is no slave support.

Referring to the smartBASIC Extensions guide for the various BL65x modules it states:

Note I2COpenEx() allows for SCL and SDA to be routed to other GPIO pins.

This function uses the same I2C instance but allows changing the pins it is operating on. The smartBASIC I2C driver does not support a second instance. The intent of this function is so multiple devices with the same I2C address can be used. Some devices support a single address, some have multiple addresses they can use. If a sensor with 2 possible addresses is used then a third cannot be added on the same bus because the address of 2 devices will clash, but it can be used on different pins. Another example is if one sensor only supports 100KHz mode but another that supports 250KHz. Different busses would need to be used so that the 250KHz signals do not cause undefined operation for the 100KHz sensor

For applications developed using Nordic SDK or Nordic Zephyr SDK then I2C interfaces supported by the particular nRF528xx BLE MCU can be used. Both master and/or slave operation is also supported. Refer to the nRF828xx data sheet for details.

Why is the data I am sending in an advertisement PDU seem to be received as converted ASCII data?

When sending extended or normal advertisements by setting AD Elements for scan or advertise response PDU’s using AT+AARA tag,<payload> or At+ASRA tag, <payload> the parser is expecting the payload to be a string enclosed by quotes.

However, how do you differentiate between a normal text string and a string of ASCII hex?

Is FF 0x46 0x46

Or is it

0xFF.

For example if the data added in the response packet is:

T+AARA tag, “BEEF”

The parser interprets this as a four byte string of 0x42, 0x45, 0x45, 0x46

If the command is changed to:

At+AARA tag, “\BE\EF” the parser would interpret this as a two byte string of 0xBE, 0xEF. The slash interprets the following two characters as ONE hex byte.

How many bytes can BL65x modules support for Extended Advertising using smartBASIC?

BL65x modules can support up to 255 Bytes when using extended advertising. This equates to an advertisement packet being sent on one secondary channel.

Extended Advertisement were introduced in Bluetooth SIG v5.0 specification. Advertisement channels 37, 38 and 39 are now qualified as Primary Advertisement Channels with channels 0 to 36 now qualified for use as Secondary Advertisement Channels. Each secondary channel can have up to 255 bytes of payload and the v5.0 specification allows for chaining up to 6 packets for up to 1650 bytes total. However, receiving all of those chained packets may be unreliable resulting in many stack vendors not offering the full chaining capacity.

How can I update and send Extended or Normal Advertisement data using AT Interface application?

In AT Interface there are just a few commands for modifying and sending Extended or Normal Advertisement data. Extended Advertisement Data is provided from the Server to the Scanner via Scan Request and Response PDU’s. An AD Element needs to be created to add the AD report that is returned after a scan request is received. To add AD Elements to the Advert Report use AT Command:

AT+AARA tag,”payload”

Tag refers to the Data Type Value specified in the Bluetooth SIG Generic Access Profile document. Using a tag of Data Type Value of 0xFF <Manufacturing Specific Data> the command will look like:

AT+AARA 0xFF “payload”

Or

AT+AARA 255 “payload”

Once the AD Report is updated it must be committed using:

AT+ACMT

To begin Extended Advertisements use AT Command:

AT+EADV <advProp>,<advIntvlMs>,<maxCount>,<priSecPhy>,<peerAddr>, <chanMask>

Refer to AT Interface Guide for more details of parameters.

For now the key parameter is <advProp>. <advProp> is a bitmask where bit 0 is set for connectable adverts, bit 1 is set for scannable adverts, bit 2 for directed adverts and in that case ‘peerAddr’ must be a valid 14 hex digit string and bit 3 is set for extended adverts. For this example AT Command:

AT+EADV 8

This command will begin sending non-connectable Extended Advertisements using default values for remaining fields which are taken from their corresponding S Registers.

To clear AD Elements when new advertisement data needs to be sent use AT Commands:

AT+ARST 1

followed by

AT+ARST 0.

This will clear existing AD Elements. If the need to maintain current AD Elements for the Advert report but additional AD Elements need to be added to the Advert Report then simply continue adding AD Elements using

AT+AARA

and

AT+ACMT

commands.

What influence does the client have when it comes to notifications?

The Client must initiate the ability of the Server to send Notifications by writing to the CCCD descriptor for the Notified Characteristic on the Server.
 

Why are multiple EMPTY_PDU are being sent from the Master per connection interval?

The communications protocol for Bluetooth is a ping pong type style, so every connection event begins with the Master sending the slave a packet and the Slave then responds to that packet with any data it may have. Therefore, when the Master has no data to transmit it will send an EMPTY_PDU to the Server and the Server, if it has data to send, will send back the data in response. You can see this readily where there is no data transmissions, the Master and Slave ping pong EMPTY_PDU’s back and forth on every connection event, if Slave Latency was incorporated then during these periods of no data transmissions you would see Master send EMPTY_PDU and no response from Slave because it has no data to send and was allowed to skip the connection event because of it.
 

Error received when flashing custom Nordic application to DVK-BL65x: SVCALL(SD_SOFTDEVICE_ENABLE, uint32_t, sd_softdevice_enable(nrf_clock_lf_cfg_t const * p_clock_lf_cfg, nrf_fault_handler_t fault_handler)); Programming custom Nordic App to DVK-BL65x

This error indicates and issue with the clock source referenced in your code. We recommend referencing the appropriate Application Note for Using the DVK-BL65x and Nordic SDK linked below:

As noted in the Application Note, by default the DVK-BL65x uses the on-chip RC oscillator as its clock source, as opposed to Nordic's development kit or dongle which use an external crystal. The difference in oscillator source should therefore be reflected in the SDK as shown Application Note. Alternatively, you can connect an external crystal as per BL65x DVK User Guide

Can the BL5340 or BL65x use a different stack to support a hosted application?

Theoretically as long as whoever 3rd party BLE stack is used is tested and supported on Nordic nRF5340 or nRF528xx used on BL65x modules.

Laird would not have tested anything other than Zepher/nRF SDK.

A 3rd party CODEC could be used as well as long as it is targeted for nRF5340. However, licensing would need to be considered.

What is the maximum number of characteristics that can be supported using smartBASIC?

The maximum number of characteristics is not a limitation in smartBASIC but a limitation in the underlying Nordic SoftDevice SDK. The SoftDevice has a maximum RAM allowance of 64KB, adding more characteristics will increase RAM usage and depending on other configuration, will determine how many characteristics can be supported within the 64KB allowed RAM space.

The maximum number of characteristics supported in smartBASIC is roughly 24. This is a product of the combination of the total RAM allowance of 64K for SoftDevice, GATT Table configuration as well as the GATT Table size as is specified in Configuration Key 204 (refer to BL654 smartBASIC Extension Guide). The default GATT table size is 1792 bytes (Config 204)) which will allow for roughly 11 characteristics.

If using the AT Interface application the maximum number of characteristics is set to 24 by default. The default configuration can be found in $autorun$.AT.interface.BL654._.sb file:

 //This defines the maximum number of characteristics we can manage

 

 

#define MAX_CHARACTERISTICS 24


As mentioned previously this is the max number of characteristics that can be supported but Out of Box the GATT table size is 1792 bytes resulting in roughly 11 characteristics.

 

How to open multiple BLE connection simultaneously with the SmartBASIC AT interface?

While it is not possible to open multiple virtual serial port (VSP) connection at a time, it is possible to open more than one regular BLE connection.

The SmartBASIC AT interface application provides configuration S registers for setting certain BLE parameters, which are accessible by the ATS command. The default configuration is optimized for establishing one VSP connection with high throughput between two BLE modules. Given this, certain S register have to be modified to accomodate for different applications.

The default configuration has set bit 3 in S register 100 (Start-up Flags), which gives max bidirectional throughput of about 127kbps. As a consequence the number of simultaneous BLE connections is being limited to 1. If you want to use more than one non-VSP BLE connections, bit 3 in S register 100 needs to be cleared and then max connections in S register 126 can be increased.

  • ATS 100=1  (if you want to keep the VSP service being active)
  • ATS 100=0  (if you want to disable the VSP service)

If you need to set other bits in S register 100, like data length extension or phy rate, add them as required. You can use ATS 100? to retrieve the current settings before changing.

Now the number of simultaneous BLE connections can be set in S register 126.

  • ATS 126=8  (set max connections to eight or some other value, the actual maximum number might depend on your particular BLE module)

Then make sure to save and apply the new settings.

  • AT&W  (this will store S register settings permanently)
  • ATZ  (does a soft reset and apply changed settings of S registers)

After the soft reset the new settings are active and you can open several BLE connections simultaneously with AT+LCON command.

See BL65x AT Interface User Guide for more information on S register settings and AT commands.

Is achieving the theoretical throughput of 2 Mbps possible with BLE radio with 2M PHY?

Unfortunately, no. At the time of this writing, even with 2M PHY enabled, BLE 5.x radios have a limitation of 1.2 - 1.5 Mbps due to the packet format. In order to achieve throughput of 2Mbps or higher you would have to use a different RF Technology, such as Wi-Fi.

Please see the Application Note for Throughput Testing with Bluetooth 5 LE 2M PHY Feature for the BL65x module.

(Note: The above Application Notes have not yet been added to the BL653 or BL654PA Product Pages, however, they do apply to those modules as well. The only difference is the DVK setup.)

 

Is it possible to have multiple connections as a peripheral device on the BL65x modules?

Multiple connections as a peripheral device is currently not supported in smartBASIC on the BL65x modules. This functionality is supported in Nordic SDK beginning with SoftDevice S132 v.4.0.0.

However, as of the writing of this FAQ, this functionality has been brought out as an experimental feature in the smartBASIC firmware for the BL654/BL654PA only, as per the Release Notes for the v29.5.7.2.0 fw It is not documented in the smartBASIC Extensions User Guide at this time due to it being an experimental feature, and no additional support is currently available for this functionality.

If interested in testing with this experimental feature, the below test can be performed using two/three mobile devices (tablets/phones) as the central devices to demonstrate that two (or more) central role devices can connect to the BL654 configured as a peripheral at the same time. (This does not test GATT functionality or anything else.) While in interactive command mode:

at+cfg 205?   // Query the current MAX number of peripheral role connections  (User Guide still indicates the MAX this can be set to is 1)
at+cfg 206?   // Query the current MAX number of central role connections
 
27 0x00000001 (1)      //Response to MAX Peripheral role connections
00
27 0x0000000F (15)   //Response to MAX Central role connections
00

Increase the MAX Peripheral role connections and decrease the MAX Peripheral role connections and then reset the module for the settings to take effect:
at+cfg 205 3        //Configure Max Peripheral to 3
at+cfg 206 3       //Configure Max Central to 3
atz                       //Reset

In our testing we used the cmd.manager.sb sample application available from the BL654 Sample Application Repository on GitHub. After setting the MAX connection parameters and resetting the device load and run the cmd.manager.sb sample application.

The commands and parameters for cmd.manager are found in the comments section of the code: To simplify this for testing purposes enter the following command to start adverts:

 advert undirected 250 30000 0 

Explanation of the command from the code:

advert undirected #INTintervalms# #INTtimeoutms# #INTfilterpolicy#
// - Use this to start adverts of type ADV_IND using the parameters specified
// - #INTfilterpolicy# is 0=no filtering, otherwise set 1 to 4 which is the
// - whitelist handle created using the 'whitelist' command

This will start adverts for 30 seconds, adjust the INTtimeoutms setting if you want to advertise for longer. Then while it is advertising, connect to it using your phones/tablets (central role devices). If the advert times out before you connect the additional devices you can restart it with the advert
undirected 250 30000 0 command.

 

Is there a way to extend the shelf life of Laird modules?? If the shelf life cannot be extended in any way, what are the consequences of using modules after shelf life?

The shelf life statements are essentially to prevent mishandling of the product and not storing it properly. If the modules are still sealed in the package, stored at the proper temperature and have not been exposed to moisture they should be fine. However, when working with modules beyond their shelf life you MUST bake the modules before populating the them to your board. Failure to bake the modules could result in the yield rate dropping down lower than expectation due to popcorn or de-lamination on the modules. It is recommended that you follow IPC/JEDEC J-STD-033 which is the general standard for the handling, packing, shipping and use of moisture/reflow sensitive surface mount devices.

Our main concern is around the castellation/pads which solder the module to the board. It is imperative those pads do not get tarnished, as this would cause soldering issues. Humidity can affect solderability as well, as if there is any excess moisture in the solder on the module, during reflow of the module to the board, steam balls can essentially explode the solder and sometimes result in an open circuit (or possibly a short circuit).

As long as all of the moisture handling and temperature guidelines are being followed you will likely have no issues. It is further recommended that when you do the build with modules that have exceeded their shelf life that you start with a handful to perform a test run and do a final test to make sure all is working as expected. As long as there are no issues with the initial test run we would expect that you will not experience any problems.

What does the Bluetooth message "advertised data length corrected" indicate?

This is effectively a Bluetooth SPAM message. It indicates the advert data being parsed is less than a full advert record can be, in other words trailing zeroes were removed.

How do I select the 32.768kHz Low Power Clock Source in the new nRF Connect SDK

Customers using the new nRF Connect SDK from Nordic will need to change the low power 32kHz clock source when working with the BL65x family of products.

To do this in the new SDK using the Segger IDE follow the instructions here;

  1. In Segger Embedded Studio select Project --> Configure nRF Connect SDK Project 
  2. Filter the list for 'osc' or drill down in the list to the Device Drivers --> Hardware clock controller support --> NRF Clock controller support --> 32KHz clock source
  3. Select the clock source based on your configuration/design:
    1. Without the optional external 32khz xtal, default configuration for our modules, select 'RC Oscillator'
    2. With the external 32Khz xtal connected to the module, select 'Crystal Oscillator'

 

With the correct value selected your code should build with the right clock source configuration and your application should run smoothly.

Where can I download UwTerminal as referenced in the BT900 or BL600 User Guides?

The BT900 and BL600 documents refer to the UwTerminal utility which was the primary utility when these documents were written. This utility is still available in the firmware zip files when they are downloaded from the BT900 Product Page or BL600 Product Page .

However, UwTerminalX is the new improved version of UwTerminal offering additional features not available in predecessor UwTerminal. We recommend working with UwTerminalX as it will support all the features mentioned in the BT900 documentation and offer the additional features, such as access to online Xcompilers.

The latest release of UwTerminalX can be downloaded from our GitHub Repository: UwTerminalX/releases


 

Can I use Windows to scan for my BLE Peripheral and Connect to it?

Laird does not provide a Windows utility for scanning and connecting to BLE devices. We are also not aware of any existing third party apps to do this either. Android and iOS are the best options for scanning for and connecting to BLE radios. 

Getting ERROR: JLinkARM DLL not found. Please reinstall latest JLinkARM when trying to flash BL65x module via the JTAG interface. How can this be resolved?

If you are getting ERROR: JLinkARM DLL not found. Please reinstall latest JLinkARM, you will need to download and install the updated Segger drivers for the J-Link.
Segger J-Link Drivers

What could be causing additional power draw when in standby doze state?

There are several functions within an application that can increase current consumption above the measurement indicated in the Datasheet for standby doze, low power mode.

  • Timers
  • GPIOs held in an asserted state
  • LEDs
  • Nested functions - which keep the module from entering the standby doze state
  • UART (when open)

 

What are the production programming options for the BL65x modules when using smartBASIC?

For production programming we recommend the following options:

  1. FLASH cloning: Instructions for FLASH cloning can be found in the firmware Zip files, which can be downloaded from the BL65x Product Page. There are two README files contained in the "Firmware" folder of the files, as well as the utilities required to create the cloned image. The first option, ____READ_ME_TO_CLONE_FILESYSTEM___, captures only the flash file and data system and does not include the firmware. The second option,  READ_ME_TO CLONE FIRMWARE_&_APP__, clones the flash file and data system as well as the firmware. When possible, we recommend cloning the firmware as well as the flash and data systems.
  2. MultideviceLoader, which is a command-line application for Windows, Linux and Mac that can be used to XCompile an application (Windows only) and download it to multiple Laird devices at the same time and provides options for: renaming the file, running it after download and other functions. This is a companion application for UwTerminalX and is mostly suited to production/end-stage testing purposes. Command line arguments are available in the Wiki on the GitHub repository.

Note: UwFlashx and Uwflash_embed are for firmware upgrades, and cannot be used to program smartBASIC applications.

How do I program BL65x modules in production or in the field (Tag-Connect)?

Consider using a PCB pad layout with support for Tag-Connect for JTAG which allows for easy, low cost programming in production or in the field.

Note: Laird recommends you use JTAG (2-wire interface) to handle future BL65x module firmware upgrades. You MUST wire out the JTAG (2-wire interface) on your host design , where four lines should be wired out, namely SWDIO, SWDCLK, GND and VCC. Firmware upgrades can still be performed over the BL65x UART interface, but this is slower (60 seconds using UART vs. 10 seconds when using JTAG) than using the BL65x JTAG (2-wire interface).

Is it possible to use Nordic's UART Serial Port Service when a BL65x module is configured for UART Bridge Mode rather than using Laird's Virtual Serial Port Service?

Yes, if config key 112 set to 1, via the AT+CFG 112 command then the service UUIDs for the UART serial port service is as per Nordic’s implementation. Any other value will use the service UUIDs for Laird’s custom service - vSP (Virtual Serial Port).

Please reference the Virtual Serial Port Service Managed section in the smartBASIC Extensions User Guide of the BL65x module you are working with for additional information.

Issues with Flashing custom firmware to BL65x using Segger Embedded Studios IDE

The BL652, BL653, and BL654 modules come preloaded with our smartBASIC firmware. When flashing custom firmware using Segger IDE it is necessary to do a full erase of the Laird BL65x module before programming the module. This can be accomplished using the NRFJPROG command line tool to send the command nrfjprog --eraseall.

How can I connect a Bluetooth Low Energy Device to a PC?

Bluetooth Low Energy uses Services as opposed to the set of standardized profiles that exists for Classic Bluetooth. While some Bluetooth Low Energy services have been standardized by the Bluetooth SIG, the development of custom services is allowed to meet custom application requirements.
 
Because Bluetooth Low Energy uses a completely different protocol than Classic Bluetooth and supports custom services, Bluetooth Low Energy devices cannot connect to a computer through the typical Bluetooth configuration of a computer. Therefore, connecting to a PC requires writing and running a Bluetooth Low Energy Central Role/Client application to collect the data sent from the Bluetooth Low Energy peripheral modules. Application development for PCs and Mobile devices is outside the scope of our support. Alternatively, a BL654 USB dongle could be used as a BLE Central Role device, to collect the BLE data and pass it to the PC over a COM Port. However, you would still need an application to view and process the data received over that COM Port.
 
We generally recommend customers who are new to Bluetooth Low Energy obtain a copy of Getting Started with Bluetooth Low Energy to help them understand the Bluetooth Low Energy protocol and the GATT table. There are also many resources available online which explain this. 

When Bluetooth Low Energy was first introduced and we launched our BL6xx product line (predecessors to the BL65x series) we produced the BL600 and BL620 smartBASIC Application Walkthrough document, which provides an overview of how Bluetooth Low Energy works and how a GATT table is constructed. 

How do you change the BAUD rate in the AT Interface Application for BL65x smartBASIC modules?

The default baud rate in the AT Interface application is 115200. In order to change the baud rate within the AT Interface code there are two modifications required in the AT Interface files as shown below:

  1. Locate the following settings within the $autorun$.AT.Interface.BL652._.sb file which sets the baud to 115200 (highlighted):
    #define SREGINIT_VAL32_0 "\4C\1D\00\00\98\3A\00\00\00\C2\01\00\00\20\00\00\01\20\00\00"
    #define SREGINIT_MIN32_0 "\4C\1D\00\00\4C\1D\00\00\B0\04\00\00\01\00\00\00\01\00\00\00"
    #define SREGINIT_MAX32_0 "\1E\04\3D\00\1E\04\3D\00\40\42\0F\00\FF\FF\00\00\FF\FF\00\00"

     
    Modify the settings to set the Hex value for the desired BAUD rate in little endian format
    The example below will set it to 9600 baud (0x00 0x00 0x25 0x80)  as shown below (highlighted)
    #define SREGINIT_VAL32_0 "\4C\1D\00\00\98\3A\00\00\80\25\00\00\00\20\00\00\01\20\00\00"
    #define SREGINIT_MIN32_0 "\4C\1D\00\00\4C\1D\00\00\B0\04\00\00\01\00\00\00\01\00\00\00"
    #define SREGINIT_MAX32_0 "\1E\04\3D\00\1E\04\3D\00\40\42\0F\00\FF\FF\00\00\FF\FF\00\00"
  2. Locate the settings for S Register 302 in the $LIB$.SRegInterface.sb file: Modify the settings in #cmpif 0x00010000 : rc=BleEncode32(SregCache32$[0],115200,offset) to set the baud rate to the desired baud rate.

 

Do BL65x modules support Boundary Scan function?

Unfortunately, we do not offer Boundary Scan functionality on the BL65x modules.


We do understand it is harder to place and recommend during development the use of an X-ray or some other means to verify to soldering process.

Do you have a smartBASIC example for Android or iOS devices such as smartphones or tablets?

smartBASIC is a programming language developed for our BT900 and BL6xx modules to simplify the code required for programming them. It is not used for developing Android or iOS device applications. BLE applications for Android and iOS devices would need to written in code specific to the Android or iOS platform.

Our, Laird Toolkit Application available for iOS and Android is currently in the process of being updated for Android and iOS to work with newer OS platforms.
Once it is complete we expect to make the source code available, to customers working with our smartBASIC modules, for reference when developing Apps for these platforms.
As of the writing of this FAQ the current version of the Laird Toolkit is still available on the App store for iOS and Google Play for Android, however, it may not work with newer versions of iOS or Android until the updates have been made.
Google Play Store
Apple Store

An alternate resource, the Nordic nRF Toolbox is also available from the iOS App Store and Google Play. The source code for this application is available from Nordic's Website.
nRf Toolbox
Android
iOS

Is there protection from Hacking when using smartBASIC modules?

Our Bluetooth 5.0 smartBASIC modules (BL652, BL653, BL654) have the capability of supporting LE Secure Connections Pairing as well as encryption. LE Secure Connection is an enhanced security feature introduced in Bluetooth v4.2. It uses a Federal Information Processing Standards (FIPS) compliant algorithm called Elliptic Curve Diffie Hellman (ECDH) for key generation. 
 
LE Secure Connections, supports four association models: 

  • Just Works
  • Numeric Comparison (Only for LE Secure Connections)
  • Passkey Entry
  • Out of Band (OOB)

Additional information about LE Secure Connections and the models can be found here: www.bluetooth.com.
 

Our Bluetooth 4.0 smartBASIC modules (BT900 /BL600 /BL620) support Simple Secure Pairing and Encryption 
Additional information about Simple Secure Pairing can be found here:
lairdconnect.com/resources/newsroom/secure-ble-pairing-iot
lairdconnect.com/resources/white-papers/ble-and-lairds-bl6x0-series-bt900-modules-guide-security-and-privacy
 
We recommend reviewing the Pairing, Bonding and Security Manager functions in the BL6xx/BT900 smartBASIC Extensions User Guides. The full security of the Bluetooth/Bluetooth Low Energy connection will depend largely on how the smartBASIC application is written, and what the input/output capabilities are of the devices that are connecting. If either device will not have any input/output capabilities then pairing will have to default to Just Works, which is the least secure pairing method. However there are additional layers of security that can be added to increase protection from hacking when the Just Works pairing model is used.

With Bluetooth Low Energy, to further secure the connection, it is recommended that the metadata for the characteristic attributes are configured for Encryption with man-in-the-middle protection for characteristic value access. This will prevent anyone from accessing data on the module without proper encryption keys. (See BleAttrMetadataEx in the BL6xx/BT900 smartBASIC Extensions User Guides.) Additionally, when using Just Works pairing, or any time additional security is required, we recommend adding a challenge/response question to the application layer, with a timer, which expects the connecting device to respond to the challenge question in a specified period of time after a connection has occurred. If the correct response is not received within that time period the application would force a disconnection. Finally, whisper mode pairing can be used during the pairing process as an additional layer of security. This is accomplished by reducing the Tx power while pairing using BleTxPwrWhilePairing as per the BL6xx/BT900 smartBASIC Extensions User Guide, which will reduce the radius which a hacker would need to breach in order to capture or spoof the encryption procedure.

Online Xcompiler is not accessible is there a way to Xcompile a smartBASIC Application locally when using UwTerminalX?

If you are having issues using the Online Xcompilers it could be related to security settings in your system which may be blocking access to the Online Xcompilers. If you are not able to resolve this it is possible to Xcompile locally by following the steps below:

  1. Disable (uncheck) the Online XCompilers on the Config Tab in UwTerminalX as shown below:
  2. Locate the Xcomp_mmmmm_xxxx_xxxx.exe file in the firmware zip folder (downloaded from module's Product Page) for the version of firmware loaded to the module.
    Note: the Xcomp version MUST match the firmware version loaded to the module or the application will not compile.
    mmmmm = module
    xxxx_xxxx =Xcomp version
  3. Copy or Move the Xcomp_mmmmm_xxxx_xxxx.exe to the same folder the smartBASIC application is stored in as shown below:

You should now be able to Xcompile the application using UwTerminalX by right-clicking in the terminal and selecting one of the Xcompile options :

  • Xcompile
  • Xcompile+Load
  • Xcompile+Load+Run

Select the application from the folder where the Xcomp file is located. UwTerminalX will now look for the local Xcompiler in the application folder.

How do I set parity on the BL65x?

Setting parity is not possible using smartBASIC on the BL652 and BL654. However, setting parity is supported when working with the Nordic SDK. Therefore, if parity setting is required, the module will have to be programmed using the Nordic SDK and the Nordic examples instead of Laird's smartBASIC examples.

Please refer to the Using the DVK-BL652 and Nordic SDK v14.0.0 with Eclipse & GCC or the Using the BL654 and Nordic SDK v16.0.0 with Eclipse and GCC  application note for assistance in setting up the BL652-DVK or BL654-DVK using the Nordic SDK. Please note that Nordic examples work with the external crystal as the clock source. The DVK-BL652 uses the internal RC Oscillator as the clock source, therefore if you will not be fitting the low frequency external crystal please be sure to modify the Nordic examples as explained in the above application note. You may also wish to refer to the BL652 Dev Kit User Guide or the BL654-DVK User Guide & Quick Start Guide

Can I write/encode an NFC tag using the BL65x?

The NFC capability of the BL652 is NFC-A Listen Mode, Type 2. It is exposed as a passive interface. Therefore, the BL652 NFC functionality currently allows for read-only (type 2) tags which can be read from an Active NFC reader, such as a smartphone or Arduino-based shield. It is not able to write or encode external tags.

More information on NFC capability on the BL652 can be found in section 7.1, "Near Field Communication (NFC) on page 314 of the BL652 smartBASIC Extensions User Guide

For the BL654, more information can be found in section 6.1 on page 344 of the BL654 smartBASIC Extensions User Guide

Can I load a smartBASIC application to the BL654 451-00004 dongle?

The 451-00004 is the Nordic/Zephry variant of the BL654 Dongle It was intended for developers who prefer working with Nordic SDK or Zephyr Project, or those who may already have an application developed on one of these platforms.

It is does not support the smartBASIC firmware and therefore smartBASIC applications cannot be loaded to it. Please reference the following documents available from the BL654 Product Page /wireless-modules/bluetooth-modules/bluetoo… for additional information about getting started with 451-00004 BL654 Dongle.

Product Brief - BL654 USB for Nordic SDK / Zephyr
Quick Start Guide - BL654 USB for Nordic SDK / Zephyr

Both Nordic and Zephyr provide their own library of sample applications and assistance with software development when electing to work with either of these platforms.

nRF5 SDK: https://www.nordicsemi.com/Software-and-tools/Software/nRF5-SDK
Zephyr Project: https://docs.zephyrproject.org/latest/

The 451-00003 is the smartBASIC variant of the BL654 Dongle which comes preloaded with smartBASIC firmware and can be programmed with smartBASIC applications. This variant of the dongle only supports loading applications developed using our smartBASIC firmware. We recommend referencing:

The Getting Started with the BL654 Dongle (smartBASIC variant) Application Note
User Guide - BL654 USB with smartBasic
Loading and Running Applications with UwTerminalX - BL654 v1.1

Can a BL65x firmware be updated OTA?

OTA firmware updates are not available for the BL65x modules. While smartBASIC programs (e.g. hello.world.sb) can be uploaded OTA, Laird firmware version (e.g. v28.9.6.0) updates can only be done over JTAG or UART.

How do I exit autorun on the BL654 dongle?

To exit an autorun application on the BL654 dongle, navigate to the "Config" tab and select "BL654 USB Dongle - Exit autorun" from the options at the top of the page (see below). This will enable you to put the dongle back into Interactive Command Mode while an autorun application is loaded to the dongle.

This option is only available in the SSL version of UwTerminalX. If you do not see this option, please download the SSL version of UwTerminalX which can be found on Github. https://github.com/LairdCP/UwTerminalX/releases

Do I have to use the Segger branded debugger to program over the 2-wire SWD interface (JTAG) of the Nordic-based modules?

Yes, any programmer/debugger that supports the SWD 2-wire interface and the Cortex M4F processor should work with the Nordic-based modules. You can find information about the memory map in the nRF5xxxx Product Specification under the Memory and NVMC sections.

Can I use USB on the BL654 if I'm using smartBASIC?

No, USB functionality was not built in to smartBASIC but all other peripherals are supported. You will need to use the Nordic SDK or Zephyr for your application development if USB is required.

The BL654 Dongle is not presenting as a Bluetooth Adapter

The BL654 is a stand-alone Bluetooth dongle with its own Bluetooth stack - it does not rely on the host stack and should present as a USB Serial COM Port or nRF52 SDFU USB COM port under Ports in Device Manager depending on which variant of the dongle was purchased.

smartBASIC variant (451-00003)

The 451-00003 will need to be programmed with a smartBASIC application in order to configure it for BLE operations.

Nordic/Zephyr variant (451-00004)

The 451-00004 will need to be programmed with a Nordic or Zephyr application in order to configure it for BLE operations.

Additional documentation for programming the dongle is available from the BL654 Product Page.

How can BL65x module or dongle be used to receive data from a custom service running on another device?

Several Sample Applications are available from the corresponding BL65x-Applications folder on Laird Connectivity's GitHub repository, including an AT Interface sample application.  The AT Interface sample application enables a quick way to configure a smartBASIC BL65x module using the commands available in the AT Interface User Guide to scan, connect, read the GATT table and receive data from the connecting device via the appropriate UUID for the custom service. We recommend referencing the AT Interface Quick Start Guide v1 0.pdf to get started with the AT Interface Application, which walks you through loading the application and a few of the basic commands, including initiating a vSP connection, (vSP is Laird's custom Serial UART application.) A non-vSP connection can be established using AT+LCON  as per page 21 of the AT Interface User Guide.

Alternatively, a custom smartBASIC central application could be developed and loaded to the dongle to connect with the custom service by referencing the Core Functionality smartBASIC and modular Extension User Guides available on the corresponding Product Page for the module, for example:

User Guide - smartBASIC Core Functionality v3.4
BL654 smartBASIC Extensions Guide v29.4.6.0

Please note: the BL654 dongle comes in two variants, smartBASIC variant (451-00003) and Nordic/Zephyr variant (451-00004). If electing to work with the smartBASIC firmware and example applications available on the GitHub repository it will be necessary to purchase the 451-00003 smartBASIC variant, as smartBASIC applications cannot be loaded to the 451-00004 Nordic/Zephyr variant.

Is it safe to run a Laird Connectivity Bluetooth module through a PCBA wash cycle?

In general, cleaning the populated modules is strongly discouraged. Residuals under the module cannot be easily removed with any cleaning process. 

  • Cleaning with water can lead to capillary effects where water is absorbed into the gap between the host board and the module. The combination of soldering flux residuals and encapsulated water could lead to short circuits between neighboring pads. Water could also damage any stickers or labels.
  • Cleaning with alcohol or a similar organic solvent will likely flood soldering flux residuals into the RF shield, which is not accessible for post-washing inspection. The solvent could also damage any stickers or labels.
  • Ultrasonic cleaning could damage the module permanently.

However, if water washing is required you will need to use deionized water. We do not recommend chemical cleaning and cannot guarantee it will not damage the modules. If you MUST clean PCB with chemicals it is recommended that you test on one board and then confirm the module still works after the process, prior to adding it to production, while understanding the above affects washing the populated PCBs can have on the module.

What is Laird Connectivity's product lifecycle EOL and PCN policy?

Laird Connectivity is committed to the long-term supply of all its standard embedded wireless modules and packaged products. Laird Connectivity’s products are specifically designed to meet the needs of the industrial and medical markets, which typically require 7 – 10 years product lifecycle. Although Laird Connectivity can’t guarantee that a component used in our products will not be obsoleted and cannot be reasonably substituted, Laird Connectivity can assure customers we will continue to sell our product when we have customer demand and can obtain the necessary components to build our products.

View our full policy here. 

Is BT 5.0 extended range feature related to higher power on newer modules like BL654, Sable X-R2?

Actually the extended range is achieved with slower transmission bit rate which let the radio emissions can be correctly received at a longer range. This data rate is reduced.

Can I use BL652/BL654 pair with BLE tag?

No. it is not possible as BL652/BL654 is NFC tag as well. You can make it to pair with a phone. The phone can provide the NFC energy field to energize the BL652.

What's the total number of concurrent connections?

The BL652/654 can do 7 (outgoing)+1(incoming) connections. But it is not possible to do 2 incoming, as peripheral can only 1 incoming, per the BLE spec.

 

What is the easiest way to change the advertised Device Name in a smartBASIC Application?

Changing the advertised device name is accomplished using three different functions prior to calling the BleAdvertStart () function.

First, the BleGapSvcInit () function is used to change the device name from the default, Laird [BL600 | BT900], to the desired device name.
Next, the BleAdvRptInit () funtion must be called to create and initialize the advert report with the new device name.
Finally, the BleAdvRptsCommit () function must be called to commit the changes.

Below is an example of a simplified smartBASIC app which changes the default device name to "My Device":
 

//******************************************************************************
// Laird Connectivity
// Rikki Horrigan
//******************************************************************************

//******************************************************************************
//Definitions
//******************************************************************************

//******************************************************************************
//Global Variable Definitions
//******************************************************************************
dim rc     //result code
dim nameWritable
dim nAppearance
dim nMinConnInterval
dim nMaxConnInterval
dim nSupervisionTout
dim nSlaveLatency

//******************************************************************************
// Initialize Global Variable
//******************************************************************************
nameWritable = 0 //The device name will not be writable by peer.
nAppearance = 1091 //Device will apear as Walking sensor on hip (org.bluetooth.characteristic.gap.appearance.)
nMinConnInterval = 500000 // must be smaller than nMaxConnInterval.
nMaxConnInterval = 1000000 //must be larger than nMinConnInterval
nSupervisionTout = 4000000 //Range is between 100000 to 32000000 microseconds (rounded to the nearest 10000 microseconds)
nSlaveLatency = 0 //value must be smaller than (nSupervisionTimeout/nMaxConnInterval)-1

//******************************************************************************
//Functions & Subroutines
//******************************************************************************

//ERROR HANDLER
SUB assertRC(rc, line)
  IF rc != 0 THEN
    PRINT "\nError on line ";line;", code: ";INTEGER.H'rc
  ENDIF
ENDSUB

// Change Device Name

FUNCTION OnStartup()
print "Default Device Name: "; BleGetDeviceName$ ();"\n"
dim deviceName$ //declare variable for DEVICENAME
deviceName$= "My Device" //Set new DEVICENAME
rc = BleGapSvcInit (deviceName$, nameWritable, nAppearance, nMinConnInterval, nMaxConnInterval, nSupervisionTout, nSlaveLatency )
print "\n New Device Name: "; BleGetDeviceName$ (); "\n"

//Create and Initializing the Advert Report (not advertised until BLEADVRPTSCOMMIT is called)
dim adRpt$ //advert report
adRpt$ = ""
rc = BleAdvRptInit(adRpt$, 2, 0, 16)

//Commit the advert report
dim scRpt$ //scan report
scRpt$ = ""
rc = BleAdvRptsCommit(adRpt$,scRpt$)

//Start Advertising
dim addr$
addr$ = ""
rc = BleAdvertStart(0,addr$,100,0,0)

ENDFUNC 1 // Remain in WAITEVENT
//******************************************************************************
//Handler Definitions
//******************************************************************************

//******************************************************************************
//OnEvent Statements
//******************************************************************************

//******************************************************************************
//Equivalent to Main() in C
//******************************************************************************
rc = OnStartup()

Waitevent

Become a Laird Connectivity Customer and Gain Exclusive Access to Our Design Services Team

  • Antenna Scans
  • Antenna selection and placement
  • Custom antenna design
  • Worldwide EMC testing / certifications
  • Embedded RF hardware / firmware design
  • Cloud architecture and integration
  • Mobile application development
  • Product & Industrial Design

Talk to an Expert

Buy Now

Distributor Part In Stock Region Buy
Tomark Electronics Ltd UK 451-00001 2763 EMEA Buy Now
RX Electronics Limited 451-00001 150 APAC Buy Now
Avnet 451-00001 0 North America Buy Now
Farnell 451-00001 0 EMEA Buy Now
Farnell 451-00001 0 EMEA Buy Now
Future Electronics 451-00001 0 North America Buy Now
Mouser 451-00001 0 North America Buy Now
RS 451-00001 0 EMEA Buy Now
RS 451-00001 0 EMEA Buy Now
RS 451-00001 0 EMEA Buy Now
Symmetry Electronics 451-00001 0 North America Buy Now
element14 APAC 451-00001 0 APAC Buy Now
Avnet 451-00001C 0 North America Buy Now
Future Electronics 451-00001C 0 North America Buy Now
Mouser 451-00001C 0 North America Buy Now
Symmetry Electronics 451-00001C 0 North America Buy Now
Digi-Key 451-00002 2665 North America Buy Now
Digi-Key 451-00002 2665 North America Buy Now
Digi-Key 451-00002 2000 North America Buy Now
Avnet 451-00002 0 North America Buy Now
Farnell 451-00002 0 EMEA Buy Now
Farnell 451-00002 0 EMEA Buy Now
Future Electronics 451-00002 0 North America Buy Now
Mouser 451-00002 0 North America Buy Now
Newark 451-00002 0 North America Buy Now
RS 451-00002 0 EMEA Buy Now
RS 451-00002 0 EMEA Buy Now
RS 451-00002 0 EMEA Buy Now
Symmetry Electronics 451-00002 0 North America Buy Now
element14 APAC 451-00002 0 APAC Buy Now
Avnet 451-00002C 0 North America Buy Now
Future Electronics 451-00002C 0 North America Buy Now
Mouser 451-00002C 0 North America Buy Now
Symmetry Electronics 451-00002C 0 North America Buy Now
Digi-Key 451-00003 1385 North America Buy Now
Farnell 451-00003 533 EMEA Buy Now
Newark 451-00003 400 North America Buy Now
element14 APAC 451-00003 400 APAC Buy Now
Symmetry Electronics 451-00003 200 North America Buy Now
Future Electronics 451-00003 180 North America Buy Now
Sourcengine 451-00003 180 North America Buy Now
Classic Components 451-00003 139 North America Buy Now
RS 451-00003 72 EMEA Buy Now
Chip One Stop 451-00003 12 APAC Buy Now
Avnet Europe 451-00003 5 EMEA Buy Now
Avnet 451-00003 0 North America Buy Now
Mouser 451-00003 0 North America Buy Now
Mouser 451-00004 2811 North America Buy Now
Digi-Key 451-00004 1017 North America Buy Now
RS 451-00004 407 EMEA Buy Now
Farnell 451-00004 344 EMEA Buy Now
Newark 451-00004 344 North America Buy Now
element14 APAC 451-00004 344 APAC Buy Now
Chip One Stop 451-00004 100 APAC Buy Now
Sourcengine 451-00004 100 North America Buy Now
Symmetry Electronics 451-00004 100 North America Buy Now
Future Electronics 451-00004 43 North America Buy Now
Avnet Europe 451-00004 5 EMEA Buy Now
Classic Components 451-00004 4 North America Buy Now
Avnet 451-00004 0 North America Buy Now
Digi-Key 453-00062-K1 25 North America Buy Now
Mouser 453-00062-K1 24 North America Buy Now
Avnet Europe 453-00062-K1 5 EMEA Buy Now
RS 453-00062-K1 4 EMEA Buy Now
Avnet 453-00062-K1 0 North America Buy Now
Symmetry Electronics 453-00062-K1 0 North America Buy Now
Avnet Europe 455-00001 64 EMEA Buy Now
Symmetry Electronics 455-00001 50 North America Buy Now
Farnell 455-00001 32 EMEA Buy Now
Newark 455-00001 29 North America Buy Now
element14 APAC 455-00001 29 APAC Buy Now
Mouser 455-00001 24 North America Buy Now
Chip One Stop 455-00001 5 APAC Buy Now
RS 455-00001 5 EMEA Buy Now
Sourcengine 455-00001 5 North America Buy Now
Avnet 455-00001 0 North America Buy Now
Future Electronics 455-00001 0 North America Buy Now
Digi-Key 455-00002 49 North America Buy Now
Classic Components 455-00002 8 North America Buy Now
Farnell 455-00002 8 EMEA Buy Now
Newark 455-00002 8 North America Buy Now
element14 APAC 455-00002 8 APAC Buy Now
Avnet Europe 455-00002 7 EMEA Buy Now
Mouser 455-00002 7 North America Buy Now
Sourcengine 455-00002 7 North America Buy Now
Future Electronics 455-00002 3 North America Buy Now
Avnet 455-00002 0 North America Buy Now
RS 455-00002 0 EMEA Buy Now
Symmetry Electronics 455-00002 0 North America Buy Now

Distributors

Distributor Phone Number Region Website
Alpha Micro UK Only +44 1256-851770
EMEA Website
Arrow Electronics 1-855-326-4757
+44 2039 365486
APAC, North America, South America, EMEA Website
Avnet 1-480-643-2000
+44 1628 512900
APAC, North America, South America, EMEA Website
Cal-Chip Connect 1-215-942-8900
North America Website
Control Synergy +61-2-4966-5211
APAC Website
Digi-Key 1-800-344-4539
North America, South America, APAC, EMEA Website
EBV Elektronik EMEA Website
Farlink Technology +86 13266922199
APAC Website
Farnell 1-800-936-198
+44 3447 11 11 22
EMEA Website
Future Electronics 1-800-675-1619
1-514-428-8470
North America, South America, APAC, EMEA Website
Glyn +49-6126-590-0
EMEA Website
Jetronic China, Hong Kong and Taiwan 852-27636806 
APAC Website
Laird Connectivity 1-847-839-6925
+44 1628 858941
North America, South America, APAC, EMEA Website
M2M Germany +49-6081-587386-0
EMEA Website
Martinsson +46 8 7440300
EMEA Website
McCoy South East Asia +65 6515 2988
APAC Website
Mouser 1-800-346-6873
+44 1494 427500
North America, South America, APAC, EMEA Website
RS Components +852-2421-9898
+44 3457-201201
North America, South America, APAC, EMEA Website
Ryoyo Japan +81-3-3543-7711
APAC Website
Symmetry Electronics 1-866-506-8829
North America Website
Tekdis Australia and New Zealand +61 3 8669 1210
APAC Website
Telsys +972 3 7657666
EMEA Website