Development Process

The following steps are guidelines to take Aironet Developer Platform-based expansion module designs from prototype to production:

Phase 1: Evaluation Phase

1.1 Developers register on DevNet to access resources such as HDK Specifications At-A-Glance, as well as electrical and power constraints.

1.2 Developers can schedule 2-hour slots to get hands-on experience with the HDK (Raspberry Pi 3) in a sandbox environment and use learning labs for guidance.

1.3 Developers can download sample code from GitHub, share projects on DevNet Creations, and get support through the Cisco Aironet Developer Platform DevNet community forum.

1.4 The developer contacts with information on use-case, product, and to arrive at additional integration requirements, if any.

Phase 2: Prototyping Phase

2.1 The developer orders the AP and WLC infrastructure though preferred Cisco Partners.

2.2.A Option A: Use the HDK to prototype.
The HDK powers user development boards via onboard power and provides bridging functionality via Ethernet interface to the AP3800/WLC. Data frames are encapsulated into a transport protocol of their choice e.g. HTTP, MQTT, web sockets, etc. which tunnels data back to a destination IP either on premise or cloud based servers. Developers are responsible for building their end-application on the module and server side. Additional development platform such as Raspberry Pi 1/2/3, Beaglebone Black, or Intel Joule may need to be bought from a retailer of the developer’s choice.

Note: The HDK is intended for prototyping and development purposes only; developers need to design their own module for production. The ADP module functionality is supported starting from the Cisco Wireless Release 8.5. All support for debugging ADP HDK/SDK issues will be handled through the Cisco Aironet Developer Platform DevNet community forum.

2.2.B Option B: Build your own custom board which complies with the Cisco pin-out configuration, detailed here.

Note: To move forward with custom development, Cisco DevNet will provide a downloadable software package. Contact to gain access.

Phase 3: IVT Testing and Productization

3.1 To ensure third-party developed expansion modules meet Cisco’s standard for interoperability and compliance, developers must engage with Cisco's IVT solution partner and Compliance labs. Please review the ADP product bulletin for guidelines on this program.

Note: This is an additional cost for the developer. Developers are responsible for procuring and conducting IVT testing to validate minimal impact to the AP's performance and the expansion module. Cisco does not influence IVT compliance testing prices and timelines, and does not assume any liability or responsibility with respect to third party-developed expansion modules.

3.2 Once the expansion module has passed the IVT testing criteria, developers can bring the product to market by leveraging the Cisco Solutions Partner Program (CSPP). CSPP ensures due diligence, qualifies partners and validates the module to ensure conformity to Cisco’s standards of compliance. Cisco will not provide technical support on the module and partner solution.