AggreGating Your Devices

Tibbo hardware and software products make it cheap and easy to network-enable your smart device and connect it to AggreGate. There are five ways to make an existing or new device work with AggreGate.

The first four ways below describe how to connect devices in so-called "Intelligent Mode". In this mode, AggreGate is used to store and process data collected from the devices, and control and monitor them. AggreGate "understands" device settings, operations and events and therefore provides comprehensive control, configuration, monitoring and management capabilities.

If your device supports one of the standard communication protocols (e.g. SNMP), it may be directly connected to AggreGate. No software of hardware protocol conversion is required in this case. Just set up all necessary physical connections and your device is ready to communicate with LinkServer.

Using this method, you embed a Tibbo module, such as the EM1000, into your device. This module runs a BASIC application called Agent. You modify the source for the Agent application so that it interfaces with your device ("understands" its communication protocol). It is then used as a transparent interface between AggreGate and your device, allowing you to access all device settings, data and events from within AggreGate.

Note that if for some reason you are unable to embed a device into your existing circuit, you can always use an external BASIC-Programmable Device Server (such as the DS1202, the stand-alone version of the EM1202) running the Agent application.

Tibbo module, such as the EM1000, is powerful enough to serve as the central processor for your application. You can connect it directly to the various sensors and circuits of your device, and use it as the main CPU, locally controlling your device's operation. In effect, you will be taking the Agent application and greatly expanding and customizing it. You would be saving the cost of a CPU for your device, and still be able to connect to AggreGate and enjoy all of its benefits.

AggreGate's communication protocol is open and well-documented. For some large-volume applications, it may sometimes be economical to write a complete implementation of this protocol for the microcontroller you are already using. The microcontroller would then connect to AggreGate just like a device running Agent does. From the system's point of view, there would be no difference, and the device would work smoothly as a part of the system.

You could also tackle the problem from a strictly software angle. A plugin is a software component allowing AggreGate to "understand" the protocol for an existing device. By coding a plugin for your device, you could then just connect it to AggreGate without making any modifications to the device itself.

You might want to use AggreGate to just route data between your devices and/or computers running some device-specific client software. In this case, AggreGate doesn't have to "understand" the data that being transferred, and does not store or process it. The Device Server converts data from the format supported by the device (RS232, USB etc.) to Ethernet traffic and routes it to and from the LinkServer.

This mode doesn't use the full power of AggreGate's data processing functions, but can be useful in several situations:

When devices are located in different LANs protected by firewalls and thus cannot connect to each other. In this case LinkServer acts as a middle-man and routes data between these devices.

When devices don't have static IP addresses. In this case they can be registered in DNS by the LinkServer and can be accessed by their host names instead of IP addresses.

Sometimes devices located in protected networks have embedded web-servers. These web-servers cannot be accessed directly, but LinkServer provides an HTTP proxy service that allows to establish a secure HTTP connection with the server instead of connecting to the device directly. LinkServer forwards this connection to the device.