Bluetooth Modules

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.

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. 

Assuming that our smartBASIC applications are used for blood pressure, heart rate, health thermometer, proximity, and find me profiles, you may maintain all of our existing approvals including full Bluetooth SIG EPL. If you choose to use Laird’s BL600 hardware with a different SDK (such as the Nordic SDK) for their application development, Laird’s BL600 EPL becomes invalid. You will then need to generate your own EPL using the Laird QDID for the BL600 hardware and then certify the software application portion based upon its own SDK.

The following link lists the versions of the BT specification along with their status and deprecation/withdrawal dates

Specifications – Bluetooth® Technology Website

It can be useful to filter for all versions and only the core elements of the specification to quickly show if a version is active, deprecated or withdrawn as well as future deprecation and withdrawal dates.

Range can be difficult to quantify as it depends on a number of factors not least the environment it is being used in.

In the first instance it can be useful to use the Bluetooth SIG range estimator at the link below

Understanding Bluetooth Range | Bluetooth® Technology Website

Here you can take data from the Ezurio module datasheet and estimate the range. Note that the range is dependant on the overall link budget, that is how loud one end of the link shouts (tx power) and how well the other end can listen (rx sensitivity).

The next stage is determining useable range is to use one or more Ezurio development kits to measure the range.

With the final stage being to measure range using the Ezurio on your own PCB. Note that PCB design can have a big impact on range performance and the layout guidelines provided in the module datasheet should be followed to ensure best performance.

Applications using smartphones can be particularly challenging as smartphones are not usually optimised  for maximum range.

The nature of the application/data can also impact usable range. High throughput applications or audio may not get as good a range as low throughput or "bursty" type data.

No. There is no software support for BLE Mesh, AoA (Angle of Arrival) and Angle of Departure (AoD) in our current AT Command Set Interface implementation. Please feel free to build and develop your own BLE Mesh, AoA or AoD application in C by using the Bluetooth SDK and tools from Silicon Labs. In this case, as a starting point, we highly recommend the Simplicity Studio 5 IDE which offers a rich set / collection of example projects and templates.

Bluetooth Mesh is a wireless mesh topology and standard which enables many-to-many (m:m) device communication for an enormous number of local BLE devices. It supports large-scale node networks without the need of an ordinary BLE gateway infrastructure. Refer to https://www.lairdconnect.com/making-bluetooth-mesh-simple and https://www.bluetooth.com/learn-about-bluetooth/recent-enhancements/mesh for additional information.

Angle of Arrival (AoA) and Angle of Departure (AoD) are two concepts for location positioning and direction finding. Without going into too much detail and to keep things very simple: One of the two BLE devices must have at least two antennas or more, so that the data received from those antennas then can be used to identify the direction and angular position of the location where the Bluetooth signals come from. Please find further information available at https://www.lairdconnect.com/resources/blog/magic-bluetooth-aoaaod-direction-finding and https://www.bluetooth.com/blog/new-aoa-aod-bluetooth-capabilities.

Ultra-wideband, often referred to as UWB, ultrawide band, or ultraband, constitutes a short-range wireless communication protocol that harnesses radio waves to facilitate seamless device-to-device communication. While bearing a resemblance to Bluetooth, UWB surpasses it in terms of precision, dependability, and efficiency.

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.

In Bluetooth, "class" refers to the three levels of power for Bluetooth devices: Class 1, 2, and 3. The following table compares power and range of these three classes:

To communicate over the 100 meter range, a class 1 BT device is required at both ends. To communicate over the 10 meter range, a class 1 or class 2 device is required at both ends.

Note: Class 3 devices are uncommon due to their very limited range.

Ezurio did provide breakout boards for our older BL600(EOL) modules but we do not produce breakout boards for any of our current range of Bluetooth modules as of 2024.

This includes all BL65x, BL53xx, BL54xxx, BTxxx, Vela and Lyra modules.

We do provide development kits for all of our module offerings. To learn more, visit any product page on ezurio.com. 

When selecting a Bluetooth module, consider your application's specific requirements, including the need for Bluetooth Classic or Low Energy (BLE), data rate, transmission range, and power consumption. Evaluate the module's antenna type, vendor reputation, and compliance with relevant standards. The choice between Bluetooth Classic and BLE depends on your project's needs for data transfer speed, range, and power efficiency. 

Additionally, consider the module's interface options (such as UART, SPI, I2C, or USB) to ensure compatibility with your system. The chipset is crucial for performance and capabilities, so choose from reputable manufacturers. Lastly, select the appropriate packaging type (in-line, surface mount, or serial port adapter) based on your production volume and integration method. 

Bluetooth Classic is optimized for continuous, high-throughput data transfer, making it suitable for applications like audio streaming, file transfers, and wireless peripherals. It typically consumes more power and is designed for use cases where maintaining a constant connection is crucial. Bluetooth Classic supports higher data rates and longer transmission distances, which are essential for applications that require robust and sustained communication.

In contrast, Bluetooth Low Energy (BLE) is tailored for applications that prioritize power efficiency & intermittent data transfer. BLE consumes significantly less power, making it ideal for battery-powered devices that need to operate for extended periods without frequent recharging. While BLE has a lower data rate compared to Bluetooth Classic, it offers sufficient performance for periodic data transmission and control tasks. BLE's design focuses on short bursts of data transfer, which conserves energy and extends battery life, making it a preferred choice for modern IoT applications.

Dual-mode Bluetooth is a wireless technology that combines the capabilities of Bluetooth Classic (BR/EDR) and Bluetooth Low Energy (BLE) in a single module, enabling devices to support a wide range of use cases from high-throughput data streaming to low-power sensor communication. According to Symmetry Electronics, dual-mode Bluetooth 5 is becoming the technology of choice for advanced IoT applications requiring music streaming, voice recognition, and connection to smartphones and other devices.