InSight Development Kits

The premier set of embedded wireless networking tools developed specifically for OEMs, the InSight Development Kit includes hardware, development tools, and software for embedded applications—everything you need to build intelligent, robust, decentralized device networks into your products. The software package includes a service-aware API that simplifies code development and lets you focus on your embedded applications. The Ember API is consistent across all products, providing an easy-to-use interface for rapid and uniform application development across the Ember platforms.

Some of our customers build simple devices that can be controlled from the same microprocessor that controls the radio. Other customers have complex or processing-intensive applications that use a two-processor approach.

In either case, Ember’s communications API facilitates the development of self-organizing, self-healing, peer-to-peer networks targeted to specific customer requirements. It contains libraries for EmberZNet’s mesh-, star-, and hybrid-networks. To achieve efficient messaging in complex networks, the communications API allows developers to build the most effective network for the application.

Ember’s flexible approach to network organization is made possible through the use of multiple message types. For example, broadcast and unicast message types support traditional mesh networking, while a special data aggregator message type reduces memory demands in large sensor networks. The API provides calls corresponding to each message type, making the libraries easy to learn and use.

Combined with Ember’s commitment to service, support and training, the InSight Development Kits give you all the tools you need to create Ember Enabled products that form reliable, flexible, secure and useful device networks. Port your application expertise onto our infrastructure and you’ll do more with your device network than you may have ever imagined, more easily and effectively than ever before.

For further information, please see the Documentation Page.