Update 06.08.2006: i.LON 1000 Internet Server is no longer available; we have not yet been able to test the successor product.
Update 18.03.2019: We found a link to IPLONGATE here . The product has not been tested by us. We cannot assume any liability for this. The following description refers to an old version of IPLONGATE.
In the search for a good OPC server for LON, we have arrived at IPLONGATE .
The IPLONGATE OPC server meets all the criteria we place on OPC servers:
1. Export the relevant project data (at least the address) in a file format that can be opened with Excel. This makes it possible to import into Elvis.
We have also written a small tool for this: opc2csv.zip. Launch the program in the command prompt. If the CSV file is not created with this tool for your OPC server, please let us know.
2. Clean installation of the OPC server.
3. Good manageability.
4. Good documentation and support.
Especially for LON:
3. It must be possible to break up the structures of the network variables.
4. The LNS versions (2.x and 3.x) must be supported.
A disadvantage of the IPLONGATE is the high resource consumption (main memory and computing power). However, this can also be due to the implementation of OPC.
We tested the OPC servers in test environments (only a few nodes). If you need information on the performance in large plants, who Ingenieurgesellschaft mbH will certainly be happy to provide you with reference plants in order to ensure safety there.
The demo version of the OPC server runs continuously for 8 hours.
In Elvis, only a few settings are necessary. The use of the OPC server is easy to specify via the bus connections. Among the data points, the address format of the LON network variables stands out:
All other design steps are analogous to the EIB system.
Interfaces from echelon can be used to connect the visualization PC to the LON. A good interaction with the IPLONGATE and high performance is achieved with the built-in card PCLTA-20 PCI LonTalk Adapter and the i.LON 1000 Internet Server.