| Product: | Elvis |
| Version: | 2.4 |
| Booth: | 2006-02-14 |
Summary
Many devices or other programs can be addressed locally via the Internet Protocol (IP) or, for example, via Ethernet. TCP and UDP are the most widely used data transport protocols. In the past, interfaces for Elvis based on TCP have often been implemented for communication with third-party systems.
Here, the implementation of such interfaces should now also be brought closer to the ambitious Elvis user. A sample project with a simple protocol definition makes it quite easy to get started.
Download sample project (preset for a UDP connection), script and the elviscpd .dll: elviscp_udp.zip (175 KB)
Details
The Elvis Server and the Custom Port
The Elvis server has no knowledge of the system or the protocol (telegram structure, etc.). For him, a data point from the EIB is structured no differently than a data point from the LON or any other system. This is exactly where the special charm of the custom port lies.
Every operation that the Elvis server can perform (e.g. time programs, recordings, alarm handling, reporting, calculations, etc.) can also be fully used for the data points of your custom port. The values from one port (e.g. EIB) can thus also influence other systems (e.g. audio/video servers). Of course, the data point values can also be displayed and changed as usual with control elements in the interface.
Custom Port White Paper: elviscpd_doc_d.pdf(20 KB)
If you need help with the implementation of your own interfaces, please contact us. We’re here to help!
