Sterling-LWB5+ WiFi 5 + Bluetooth 5.2 Module
Overview
Laird Connectivity’s customers across multiple industries have a diverse set of requirements and specific needs. They asked for a truly robust industrial IoT module: one that’s rugged, small, simplifies their BOM, is globally certified, has reliable connectivity, and easy to integrate.
Laird Connectivity’s new Sterling-LWB5+ answers that call for next-gen wireless IoT. Powered by Infineon’s CYW4373E silicon, the Sterling-LWB5+ is purpose-built for IIoT connectivity through a secure, reliable, and robust feature set. It’s IoT from the start: fully certified, easy to integrate, and is the fastest route to the market for IoT.
- Purpose Built: Made with manufacturability in mind, and pre-certified to cut down barriers to entry.
- Compatible: Our Linux Backports package supports many Linux kernels.
- Reliable: Integrated PA (Power Amplifier) and LNA (Low Noise Amplifier) with antenna diversity for reliable connectivity in harsh RF environments.
- Robust: Rich feature-set including 802.11ac Wi-Fi and Dual-Mode Bluetooth. Reliable in industrial temperature range, and solder-down module is suitable for industrial vibration and impact demands.
- Secure: Supports the latest WPA3 security standards.
Specifications
Bluetooth 5.2
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00045-K1 | Development Kit | Internal, Chip Antenna | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Development Kit | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | Packaging | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00045C | Solderable Module | Internal, Chip Antenna | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Embedded Module | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E | Cut Tape |
Description | Antenna Type | Logical Interfaces | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Packaging | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00045R | Solderable Module | Internal, Chip Antenna | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Embedded Module | Android, Linux | SDIO, Serial | Hosted | Tape/Reel |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00046-K1 | Development Kit | External, MHF4 Connector | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Development Kit | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | Packaging | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00046C | Solderable Module | External, MHF4 Connector | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Embedded Module | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E | Cut Tape |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | Packaging | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00046R | Solderable Module | External, MHF4 Connector | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Embedded Module | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E | Tape/Reel |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | Packaging | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00047C | Solderable Module | External, Trace Pin | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Embedded Module | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E | Cut Type |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | Packaging | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00047R | Solderable Module | External, Trace Pin | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Embedded Module | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E | Tape/Reel |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00048 | M.2 Carrier Board (E-Type Key w/ SDIO/UART) | External, MHF4 Connector | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Embedded Module | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00048-K1 | Development Kit for M.2 Key E (SDIO/UART) | External, MHF4 Connector | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Development Kit | Android, Linux | SDIO, Serial | Hosted | Infineon CYW4373E |
Antenna Type | Description | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00049 | External, MHF4 Connector | M.2 Carrier Board (E-Type Key w/ USB) | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Embedded Module | Android, Linux | USB | Hosted | Infineon CYW4373E |
Description | Antenna Type | Technology | Frequency Range (Min) | Frequency Range (Max) | Frequency Range 2 (Min) | Frequency Range 2 (Max) | Product Type | OS/Software | Logical Interfaces | System Architecture | Chipset (Wireless) | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
453-00049-K1 | Development Kit for M.2 Key E (USB/USB) | External, MHF4 Connector | 802.11ac, Bluetooth 5.0 | 2400 MHz | 2495 MHz | 5150 MHz | 5825 MHz | Development Kit | Android, Linux | USB | Hosted | Infineon CYW4373E |
Photo Gallery
Certified Antennas
001-0009
2.4 / 5.5 GHz Dipole RF AntennasPre-certified 2.4 and 5 GHz RF antennas, IP67-rated for dust and water protection.
001-0021
FlexPIFA Flexible Adhesive-Backed PIFA Internal AntennaDual band antenna with MHF4L connector
Industry-first, flexible, planar inverted-F antenna for curved surfaces 2.5-3 dBi gain. 2.4 GHz and dual-band 2.4/5.5 GHz.
EMF2449A1-10MH4L
Mini Nanoblade Flex / Flex 6E Series Internal AntennaFlexible, onmidirectional PCB Mini NanoBlade. Vertically polarized, with 2.79 dBi gain @ 2.4 GHz and 3.38 dBi gain @ 5 GHz.
ENB2449A1-10MH4L
Nanoblade Series Internal AntennaVertically polarized, omnidirectional planar antenna with 2 dBi gain @2.24-2.5 GHz, 3.9 dBi gain @ 5.15-5.35 GHz, and 4 dBi gain @ 5.6 Ghz.
CARSMF10AMH4L-001
Reverse Polarity SMA Cable AssembliesU.FL or MHF4L to Reverse Polarity SMA Cable assemblies, engineered for peak performance up to a maximum of 7.5 GHz.
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
Documentation
Backports fails to compile with 'refcount_t {aka struct refcount_struct}' has no member named 'counter'
There are certain patch ranges within kernels 4.4 and 4.9 that need a modification so backports can build, the reason why we cannot fix it in backports is that we cannot track and differentiate between patch versions of the same 'major.minor' version of kernel. To fix this issue, move the function kobject_has_children
from linux/kobject.h to drivers/base/core.c in your kernel source, rebuild the kernel and then rebuild backports.
How can I receive notifications of the latest updates to the driver and firmware?
Simply log into GitHub, go to the corresponding release packages page and click the "Watch" button (eye icon) in the top right of the page. Some radios (such as the LWB Series) requires you to download firmware separately from the product page; this firmware is updated on the product page in conjunction with GitHub releases.
How do I manually cross-compile the Sterling supplicant from source?
It is best practice to include the source in your build system. If using Yocto, our external layer will do this for you.
Here is an example manually compiling using our SOM60 as a target in a Buildroot environment:
- Download and extract the Sterling supplicant source.
- Navigate to the "laird" directory.
- Edit the config_laird file:
- Find the following line, uncomment and change the path to your "openssl/include" directory:
original line:
#CFLAGS += -I/usr/local/openssl/include
modified line:
CFLAGS += -I/wb/buildroot/output/som60sd/build/host-libopenssl-1.1.1d/include
- Run make with the following flags
set:
CC="" for your cross-compile binary
PKG_CONFIG="" for your pkg-config binary
PKG_CONFIG_PATH="" for your pkgconfig directory
OBJCOPY="" for your objcopy binary
Note the following example is a single line command:
make CC="/wb/buildroot/output/som60sd/host/bin/arm-buildroot-linux-gnueabihf-gcc" PKG_CONFIG="/wb/buildroot/output/som60sd/host/bin/pkg-config" OBJCOPY="/wb/buildroot/output/som60sd/host/arm-buildroot-linux-gnueabihf/bin/objcopy" PKG_CONFIG_PATH="/wb/buildroot/output/som60sd/host/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/pkgconfig"
How do I test layer 2 Bluetooth stability without setting up a profile on a Linux platform?
In BlueZ, some commands such as l2test or l2ping are able to generate traffic on L2CAP layer. To test performance and reliability, you can use the l2test command:
On the server, run the command:
l2test -I 2000 -r
On the client side, run the command:
l2test -O 2000 -s XX:XX:XX:XX:XX:XX
How do I use your precompiled dynamically linked binaries such as your supplicants or radio testing tools?
If the binary returns "not found" or does not work after confirming the executable bit is set with chmod +x <filename>
, then you will need to create a symlink pointing to the system's interpreter. The file
tool will show the expected interpreter and architecture of a binary, readelf
is a lot more verbose and is used to discover the expected "sonames" of shared libraries. These utilities do not have to be used on the target system and is convenient to use on a common x86 Linux machine. These utilities can be installed on Ubuntu with sudo apt install binutils
.
Example output from the file command:
sterling_supplicant-arm-7.0.0.139/usr/sbin$ file wpa_supplicant
wpa_supplicant: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 3.0.0, stripped
Example output from the readelf command:
sterling_supplicant-arm-7.0.0.139/usr/sbin$ readelf -ld wpa_supplicant Elf file type is EXEC (Executable file)
Entry point 0xba28
There are 10 program headers, starting at offset 52 Program Headers:
...
<edited>
...
[Requesting program interpreter: /lib/ld-linux.so.3]
...
<edited>
...
Dynamic section at offset 0x176ee8 contains 30 entries:
Tag Type Name/Value
0x00000001 (NEEDED) Shared library: [librt.so.1]
0x00000001 (NEEDED) Shared library: [libnl-3.so.200]
0x00000001 (NEEDED) Shared library: [libnl-genl-3.so.200]
0x00000001 (NEEDED) Shared library: [libdl.so.2]
0x00000001 (NEEDED) Shared library: [libdbus-1.so.3]
0x00000001 (NEEDED) Shared library: [libgcc_s.so.1]
0x00000001 (NEEDED) Shared library: [libc.so.6]
...
<edited>
...
To use this binary, we will have to confirm this symlink exists or create a new symlink pointing to the interpreter on the target filesystem:
cd /lib/
ls -l ld-*
-rwxr-xr-x 1 root root 158772 Dec 2 2019 /lib/ld-2.26.so
ln -sf ld-2.26.so ld-linux.so.3
ls -l ld-*
-rwxr-xr-x 1 root root 158772 Dec 2 2019 /lib/ld-2.26.so
lrwxrwxrwx 1 root root 10 Dec 21 18:55 /lib/ld-linux.so.3 -> ld-2.26.so
If the binary now reports that a library is not found when executed, repeat the steps shown above for creating a library symlink/soname pointing to it's real name. This may require you to use the find command to discover the location of the library. Example for libnl-genl-3:
find / -name 'libnl-genl-3*' -exec ls -l {} 2>/dev/null \;
-rwxr-xr-x 1 root root 18524 Feb 14 23:42 /usr/lib/libnl-genl-3.so.200.26.0
cd /usr/lib/
ln -sf libnl-genl-3.so.200.26.0 libnl-genl-3.so.200
ls -l libnl-genl-3*
-rwxr-xr-x 1 root root 18524 Feb 14 23:42 /usr/lib/libnl-genl-3.so.200.26.0
lrwxrwxrwx 1 root root 24 Feb 14 23:37 /usr/lib/libnl-genl-3.so.200 -> libnl-genl-3.so.200.26.0
If the library does not exist, you will have to include that package in your build. For instance if the above example libnl was missing, include the libnl package when building your filesystem.
How to set radio to Soft AP mode?
If you don't want simultaneous ap/sta, you can run the commands:
nmcli conn add type wifi ifname wlan0 con-name softAP autoconnect no ssid softAP
nmcli conn modify softAP 802-11-wireless.mode ap 802-11-wireless.band bg 802-11d
nmcli conn up softAP
You can also do it via wpa_supplicant .conf files if you do not have nmcli.
What are the requirements to be able to leverage "Modular Approval"?
In order to be able to leverage the Modular Approval of a wireless module the following requirements have to be met:
- The RF circuitry must be shielded
- The module must have buffered modulation/data inputs. Module must inherently ensure compliance under host fault (watch dog) conditions
- The module must have a regulated power supply
- An antenna needs to be attached permanently or a unique antenna connector must be mounted on the module
- The module must be compliant with the regulations in a stand-alone configuration
- The module must be labeled with its permanently affixed FCC ID label or use an electronic display
- A user manual needs to provide comprehensive instructions to explain compliance requirements.
- The module must comply with RF exposure requirements
What is my best chance to use an antenna that is not pre-certified for my wireless module?
To use an antenna that is not listed on your wireless modules datasheet, it must be of the same topology (e.g. dipole, PIFA, etc.), equal or lesser gain, and have the same in-band and out of band characteristics.
Note: Japan (MIC) lists applicable antennas on its certificates. If your antenna is not on the approved list, regardless of whether it is comparative, it must be added to the certificate before it can be used in Japan.
When I try to get my Bluetooth interface up on the UART using "patchram" I receive the error "can't set line discipline"?
When the error "can't set line discipline" occurs when the patchram tool is used to bring up the Bluetooth HCI-UART device it is very likely that the "Bluetooth HCI UART" driver (or module) is not enabled in the Linux kernel configuration as module.