|
|
The ethernet-to-OEM solutions are used when OEM specific interface (TTL I/O, A/D, D/A or other) is to be connected to an ethernet interface. Usually for remote control, monitoring or data acquisition/transfer over an intranet or internet. Examples of OEM specific interfaces are:
Solution example 1: Web-enabling a device with OEM specific interface
Original configuration: The configuration consists of a PC with a dedicated I/O board and a device that has an OEM specific interface. An OEM specific protocol is used for interactive access to parameters and/or data of the OEM device.
Wanted: A web interface for the device is wanted that enables using a web browser for accessing the OEM device over an intranet/internet.
Solution
The O2E solution takes care of the handling the OEM specific interface of the device and presenting the information in the form of (dynamic) web pages. Additional options: Alarming or data acquisition to RAM disk. Data transfer using email or FTP.
In the figures above the O2E solution represents one of the following:
In the solution above we assumed interactive communications with the device, initiated by the user on the PC. However, the same solution can also be used for non-interactive, automated, configurations. For example for periodic retrieval of device data by a central server over ethernet using FTP. |
Necoso, Het Kasteel 315, 7325 PE Apeldoorn, The Netherlands
|