OKE Implementation Sanity Check

Has the OKE implementor fully ported the CWL to their platform by carefully reviewing and modifying as appropriate all the functions in cwport.c and the configuration options in cwport.h?

Has the OKE implementor verified that cwport.c and cwport.h are the only CWL source files that have been modified?

Has the OKE implementor requested and received their Make/Model ID code from Powerhouse Dynamics, and use that code when generating the OKE's Device ID?

Is the OKE Device ID of every device guaranteed to be unique?

Does the OKE correctly support reporting the network status of the WiFi CWM?

Does the OKE correctly implement initiating a CWM WiFi network scan.

Does the OKE correctly report WiFi network scan results from a WiFi CWM.

Does the OKE support configuration of the CWM's WiFi network, custom and SAP mode?

Does the OKC simulator display a set of one or more OKE generated heartbeat messages every minute that contain all the expected equipment specific data?

Does the OKE generate a complete set of heartbeat messages when an asynchronous request is made from the OKC simulator.

Does the OKE track ephemeral equipment events by maintaining an event count rather than simply reporting a status bit?

Does the OKE report the correct local time via its local user interfaces?

Does the OKE timestamp messages with the correct local time?

Does the OKE receive files correctly and completely from the OKC?

Does the OKE send files correctly and completely to the OKC?

Does the OKE report its file directory correctly?

Does the OKE delete files correctly?

Does the OKE respond to a ping request from the OKC?

Does the OKE reset its controller when it receives a reset command from the OKC?

Does the OKE appropriately flush queues or other data stores when it receives a flush command from the OKC?

Has the OKE implementor had cwport.c and cwport.h code reviewed by Powerhouse Dynamics?