80 likes | 228 Views
Wavenis plug-in. Advanced library for Waveport communications and third-party Wavenis integrations. History. It was created by a developer with usage by other developers in mind.
E N D
Wavenis plug-in Advanced library for Waveport communications and third-party Wavenis integrations
History • It was created by a developer with usage by other developers in mind. • The library was created in 2005 from scratch by the person who developed the legacy libraries used by integrators. The knowledge of advantages and disadvantages of the previous libraries ensured a more efficient and easier to use library. • Like the old libraries, the plug-in features classes for communications with Waveflows, Wavetherms, Wavelogs, Wavesenses, Wavehub,…
Optimized communication kernel • The library’s core reads data coming from the Waveport as it comes, with minimal processor usage: only one thread per Waveport, dedicated to receiving. • Minimal memory allocation: memory slots are retained throughout the life of the instance, to save processor. • The serial communication layer was developed exclusively for use with a Waveport. • Automatic filtering of incoming data (response to a request, or spontaneous alarms). • The object model allows easy request serialization, and thus remoting. • Events can be handled to intercept data from the normal flow.
Your application NS.Plugin.Wavenis TCP layer TCP Client TCP Server NS.Plugin.Wavenis Serial link (USB, RS232) TCP Client TCP Server Waveport Waveport communications • Serial communications: • RS232 • USB • TCP: • IP Waveport: the library connects to the Waveport over an IP network. • GPRS Waveport: the library listens to incoming connections originating from Waveports. • Bluetooth: • A Bluetooth serial communication link is created with the Waveblue • Remoting: • The library can emulate a GPRS Waveport or and IP Waveport to grant a remote application control over the physical Waveport.
One basic request object • All requests are executed using a WavecardRequest class • A minimal amount of information is needed for the instance to launch its request, since most often used settings are defaulted automatically for the request: • RFID of the target device • RFID of relays used to reach the target device • Payload. • Timeout management is automatic, based on: • Network settings, • Number of relays, • Type of request. • Or can be set to a specific duration
Open to add-ons • The library provides interfaces, public methods and events to allow third parties to add features: • Events used to resolve Waveports with a network manager (in multi-Waveport configuration) • Events used to resolve relay routes with a network manager. • Alarm and sensor interfaces to allow other integrators to use new Wavenis-enabled products, without the need for a new library and a separate Waveport: they simply need to implement device-specific treatment. • The library is programmed using .NET, speeding up development time, and time to market.
Field proven efficiency • The library has been field proven on metering gateways, and runs flawlessly. • Built-in watchdog: you may physically disconnect and reconnect your Waveport, the library will automatically reattach itself. • Even user code errors are handled: if an error is generated while handling an alarm event, the instance will survive, and not crash the whole application. • No down time. • The accelerated communication speed with the
Integrators that made the choice Licensed integrators Currently evaluating ICOL, Utiligy, Oleoware, aqua-consulting