Premium WiFi Advantage Software

Ezurio (formerly Laird Connectivity) Stack Advantage

The core of our software advantage is the Wi-Fi connectivity stack for Linux and Android we provide and support for our Wi-Fi + Bluetooth certified modules. Utilizing the core software structure and stack components that make up the Linux Wi-Fi and Bluetooth connectivity stack, we leverage its expertise and QA capabilities to expand upon the usual deliverable for a Wi-Fi + Bluetooth combination radio.

We provide a broader selection of components to reduce the chance of incompatibility and create a simpler and faster integration of the device specific components by pretesting and QA-ing the full stack with the device specific software and those components they interact with. The result is a set of software components in the connectivity stack that have previously been tested and confirmed to build before you even see them. A comparison of the tested and supplied connectivity components vs. our competition can be seen here:

Since we utilize the standard Linux Wi-Fi connectivity stack architecture and software components, it is possible to selectively use the provided files provided in our Ezurio Stack package. However, this must be done with caution and the understanding that we cannot guarantee the resulting stack will build or perform correctly. We also will not directly support any integrations that do not utilize our entire stack, this is due to the fact we have no knowledge of the components being used.

Our connectivity stack is fully supported by our support team. So if you have any issues building or getting your code to operate as expected, we can provide direct technical support to make sure your system is operational as soon as possible.

Linux Kernel Backports Package

As part of our connectivity stack we utilize the Linux kernel backports project. This allows Ezurio to provide not just a single known supported kernel for our radios, but a range that covers the most widely used variants. This extends the simplicity of integration that the stack provides beyond just a single instance and allows you build functional code very quickly even if you are not using the latest kernel version.

We support kernel versions as early as v2.6.37 and maintain options through the latest long-term support versions being used by the industries to most popular MPU SDK packages. There are over 60 kernel versions supported in the backports package, not all kernel versions are supported by all radios. The currently supported kernels, by radio, can be seen in table below.

Since our connectivity stack is maintained constantly and gets the benefits of bi-annual updates each year (more if there are security or feature adds), the table will have been extended and it is recommended you check with your support contact to get the latest support profile.

Additionally, we have the ability to support kernel version outside of those listed above. This includes vendor Linux kernels and Android release versions.

wpa_supplicant

One of the advantages of testing this important component of the connectivity stack, directly linked to the supported security provided by the Wi-Fi radio, is that we can extend and confirm operation for a broad set of security options. These include the support for Enterprise security, the EAP types, certificate length and cypher types.

The following table outlines how our security type support compares with some of our competitors:

Without this work the effort to get the components and security features enabled can be large. It also means we can extend the supported set as security demands change and customers require updated and extended security support.

Feature Performance

Our investment into producing the highest quality product is reflected in the performance, breadth of features we can provide. The following highlights these benefits:

AP mode throughput identifies the aggregate average throughput for all clients when the max number of clients are simultaneously passing data. Testing is done on both the 2.4 GHz and 5 GHz bands (if supported) using the maximum link rate. Results are also gathered in both the upstream and downstream direction. The performance test is accomplished using IxChariot software to generate the traffic flows and accumulate the results. The throughput is measured between the IxChariot endpoints installed on the AP and each of the test clients using a standard IxChariot throughput script sending IP traffic. 

Delivery and Development

The best software in the world is no use if you cannot get access to it. We have spent a great deal of time making our software accessible and easily integrated. Firstly, we follow the open-source licensing utilized by the Linux.org for software distribution, we require no additional licenses for the standard connectivity stack components. However, there are situations where software necessary for the development and testing of a system could require tools that must be licensed form the supporting silicon vendor, where possible we have developed and support a license free tool for these situations called the Laird Regulatory Utility (LRU), again making access to the necessary components for development as easy as possible. The table below shows some of the highlights:

Access to the software is critical and not universal in how it can be achieved; again we have enabled the most flexible and easily accessible access to our connectivity stack. Compared to the options form our competitors, it provides the simplest access and most flexible integration options, especially when combined with the options provided by the connectivity stack.

Comparing some of the approaches available against Ezurio's solution might provide some clarity on why our approach will suite you the best. 

How Do I Get Access to the Radio Software?

There are several ways to provide access to the radio software, some are limited by licensing and other reduce flexibility of integration but let’s look at the options. 

In options 2 through 4 you are not guaranteed to get anything more than the device driver and associated radio firmware binaries. Integrating the driver source with your Linux distribution, that will have its own Wi-Fi connectivity stack, falls on you. Often driver to supplicant interaction needs significant work to make sure it is fully compatible and meets the operational requirements for your application.