| |
 |
EtherNet/IP™ Client – EtherNet/IP Server DLL |
The Fastest Way to Turn Your VB or C++ Application into an EtherNet/IP Client or Server |
| |
|
|
 |
|
 |
|
 |
|
 |
Ethernet is no longer an option for Industrial Devices – ETHERNET IS A REQUIREMENT. Ethernet is the fastest growing segment of Industrial Networking for one reason – The Market (Your Customers) Loves Ethernet. And the most important Industrial Ethernet protocol is EtherNet/IP™. EtherNet/IP is the Ethernet solution used in the Rockwell Automation architecture and the one GM is requiring for Robots, Welders and other automation devices.
Creating EtherNet/IP Windows-based applications is now easier than ever. Your C++ or VB application can now function as an EtherNet/IP Scanning Client, an EtherNet/IP Server or an EtherNet/IP Tag Client for applications requiring access to ControlLogix applications. As an EtherNet/IP Scanning Client your application can make connections and exchange data with any EtherNet/IP server. As an EtherNet/IP Server, your PC application can function as a device on the other end of the network. You accept connections from an EtherNet/IP Client like ControlLogix and exchange data with it. And as an EtherNet/IP Tag Client you can simply read and write any tag in a Logix (ControlLogix or CompactLogix) controller. |
| |
| EtherNet/IP Client DLL |
The EtherNet/IP Client DLL wraps the standard Real Time Automation, Inc. EtherNet/IP application layer protocol stack and exposes the portion of the application layer needed by a MS Windows (or .Net) application. The remainder of the application layer protocol stack is internally processed by the DLL and hidden from the end user application.
Prior to enabling communications, the EtherNet/IP Client DLL must be configured. The configuration parameters are set from the consumer's application via a set of function calls to the DLL. These configuration parameters must be set before communications are enabled. Attempts to set these parameters, once communications are enabled, is considered an error.
The end user application can enable and disable communications via a pair of function calls. When communications are enabled, the EtherNet/IP Client application layer protocol initiates connections with the EtherNet/IP Servers and begins exchanging data as configured by the end user application. When communications are disabled, the DLL disconnects any existing Server connections and disregards any further protocol traffic and network requests.
Internally, the DLL performs communications processing using a worker thread. This thread is created when communications are enabled and exits when communications are disabled. The thread runs in an endless loop waiting on sockets, timers, or a signal to exit.
Notifications from the DLL of messages that require custom processing are handled via callback functions to the end user application. These callback functions are defined to the DLL by the consumer's application prior to enabling communications. The consumer's application should be aware that these callbacks are called in a multi-threaded context, and must implement the callback functions in a thread-safe manner. Specifically, the consumer's application should (if necessary) provide thread-synchronization when accessing its own data/functions (e.g., using critical sections), and efficiently processing the callback and returning in a timely fashion. |
| |
top of page |
| |
| EtherNet/IP Server DLL |
The EtherNet/IP Server DLL wraps the EtherNet/IP application layer protocol stack and exposes the portion of the application layer needed by a MS Windows (or .Net) application. The remainder of the application layer protocol stack is internally processed by the DLL and hidden from the end user application.
Prior to enabling communications, the EtherNet/IP Server DLL must be configured. The configuration parameters are set from the consumer's application via a set of function calls to the DLL. These configuration parameters must be set before communications are enabled. Attempts to set these parameters, once communications are enabled, is considered an error.
The end user application can enable and disable communications via a pair of function calls. When communications are enabled, incoming connections from EtherNet/IP Clients are accepted, messages are received and parsed and responses are issued. The end user application is notified if any messages are received from the Client that require the attention of the end user application. When communications are disabled, the DLL disconnects any existing Client connections and disregards any further protocol traffic and network requests.
Internally, the DLL performs communications processing using a worker thread. This thread is created when communications are enabled and exits when communications are disabled. The thread runs in an endless loop waiting on sockets, timers, or a signal to exit.
Notifications from the DLL of messages that require custom processing are handled via callback functions to the consumer's application. These callback functions are defined to the DLL by the consumer's application prior to enabling communications. The consumer's application should be aware that these callbacks are called in a multi-threaded context, and must implement the callback functions in a thread-safe manner. Specifically, the consumer's application should (if necessary) provide thread-synchronization when accessing its own data/functions (e.g., using critical sections), and efficiently processing the callback and returning in a timely fashion. |
|
top of page |
| |
| EtherNet/IP Tag Client DLL |
The EtherNet/IP Tag Client DLL is a special function DLL for C++ and VB applications that require access to Logix (ControlLogix and CompactLogix) data tags. All of the EtherNet/IP functionality required for this functionality is hidden from the user and only the portion of the application layer needed by a MS Windows (or .Net) application to read and write tags is exposed to the end user application.
Prior to enabling communications, the EtherNet/IP Tag Client DLL must be configured. The configuration parameters are set from the consumer's application via a set of function calls to the DLL. These configuration parameters must be set before communications are enabled. Attempts to set these parameters, once communications are enabled, is considered an error.
The end user application is in complete control of communications. When communications are enabled, the EtherNet/IP Tag Client DLL application layer protocol initiates connections with a Logix processor and can read and write any tag defined in the processor data table upon direction of the user application.
Internally, the DLL performs communications processing using a worker thread. This thread is created when communications are enabled and exits when communications are disabled. The thread runs in an endless loop waiting on sockets, timers, or a signal to exit.
Notifications from the DLL of responses to read and write tag requests are handled via callback functions to the end user application. These callback functions are defined to the DLL by the consumer's application prior to enabling communications. The consumer's application should be aware that these callbacks are called in a multi-threaded context, and must implement the callback functions in a thread-safe manner. Specifically, the consumer's application should (if necessary) provide thread-synchronization when accessing its own data/functions (e.g., using critical sections), and efficiently processing the callback and returning in a timely fashion. |
| |
| ORDERING INFORMATION |
479ES |
EtherNet/IP XP Server DLL – Royalty Free Product License |
479EC |
EtherNet/IP XP Client DLL – Royalty Free Product License |
479ETC |
EtherNet/IP Tag Client DLL – Royalty Free Product License |
|
| |
 |
|
top of page |
|
|
| (c) 2007 Real Time Automation, Inc. - Specialists In EtherNet/IP™ Client – EtherNet/IP Server DLL |
| |
|
|
