WL05 Driver Library – API Documentation
Although the WL03 and WL05 driver libraries are inherently incompatible to one another, effort has been made, so that the WL05 library API resembles the WL03 API, in order to ease development using the new WL05 module. This guide aims to aid users who have already developed applications using the WL03 module, and would like to deploy the WL05 successor module.
The most important driver library differences between WL03 and WL05 are listed here. Despite these differences in API calls and data types, the WL05 library presents a simpler interface, abstracting away superfluous low level settings.
All the data types and API functions availabe in the WL03 library start with the prefixes wl03_ and WL03_.
In accordance to this notational convention, all the data types and API functions availabe in the WL05 library start with the prefixes wl05_ and WL05_.
This section lists the differences between data type definitions between the WL03 and WL05 libraries. It should be noted that this list entails actual definition differences and not naming differences that are a result of the prefix change described in the above section: Prefix.
Such an example is the WL05_DrvIndicationCodes enumeration, whose definition is one-to-one in compatible to the corresponding WL03 definition.
This section lists the differences between API function definitions between the WL03 and WL05 libraries. Both argument and return value differences are listed.
This section describes the differences between the CHIP.INI entries that are documented in the WL03 library, and are either changed or obsolete for the WL05 library.