# US 2010/0250719 A1 · Universal Network Adapter for Industrial Control Networks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0250719 A1
- Document ID: US20100250719A1
- Status: Published application
- Kind: A1
- Application number: 12/413,712
- Filed: 2009-03-30
- Published: 2010-09-30
- Earliest claimed: 2009-03-30
- Assignees: Rockwell Automation Technologies, Inc.
- Inventors: Darren R. Klug; Petr Ptacek
- Web page: https://patentgrep.com/patent/US20100250719A1

## CPC

- G05B 19/0423: {Input/output}
- H04L 41/0226: Mapping or translating multiple network management protocols
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0856: {by backing up or archiving configuration information}
- H04L 69/18: Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A universal network adapter for a control system provides an appliance receiving a user selection of network cards for different proprietary network types and an internal interpreter running custom scripts downloadable to the appliance to map the network protocols of the different networks to a single common network communicating with the programmable controller. A buffer table interposed between the networks provides for a consistent ordering of data transfer in separate input and output sessions. Configuration data may be held by the appliance to configure the networks and the devices using the same scripting translation.

## Claims

### Claim 1

A network appliance for a programmable controller controlling a plurality of I/O nodes on different I/O networks using different communication protocols, the network appliance comprising:
a plurality of I/O network interface circuits providing hardware connections to the different I/O networks of the I/O node;
a controller network interface circuit providing a hardware connection to a controller network communicating with the programmable controller;
a memory holding a network appliance program, script files, and configuration files;
a processor executing the network appliance program to:
(a) store in memory, script files associated with the different I/O networks, the script files associated with particular I/O networks and executing to translate between protocols of the controller network and the particular I/O network;
(b) receive from the programmable controller and store in memory, configuration files associated with particular I/O networks and describing configuration parameters for the particular I/O networks;
(c) before communication between an I/O node and the programmable controller, configuring the I/O networks according to the associated configuration file; and
(d) in response to communication between an I/O node and the programmable controller, execute a script associated with the I/O network to translate between protocols of the I/O network and controller network;
whereby the programmable controller may communicate with I/O nodes as if they were connected directly to the controller network.

### Claim 2 (depends on 1)

The network interface of claim 1 wherein the controller network interface circuit provides network functionality that is a superset of the individual I/O networks.

### Claim 3 (depends on 1)

The network interface of claim 1 wherein the script files are received from the programmable controller.

### Claim 4 (depends on 1)

The network adapter of claim 1 wherein the controller network operates according to a connected messaging protocol in which communications between devices are subject to pre-designated connections specifying message timing, frequency and size.

### Claim 5 (depends on 1)

The network adapter of claim 1 wherein the controller network uses the EtherNet/IPprotocol.

### Claim 6 (depends on 1)

The network adapter of claim 1 wherein the script files further include a mapper translating between addresses on the controller network and addresses on the I/O network.

### Claim 7 (depends on 1)

The network adapter of claim 1 wherein the I/O networks are selected from the group consisting of: EtherNet/IP, DeviceNet, ControlNet.

### Claim 8 (depends on 1)

The network adapter of claim 1 wherein the I/O networks are selected from the group consisting of: SerBus, 69-Bus, HART, ModBus, and Foundation FieldBus.

### Claim 9 (depends on 1)

The network adapter of claim 1 wherein the I/O network interface circuits provide electrical connectors allowing them to be removably attached to a common bus.

### Claim 10 (depends on 1)

The network adapter of claim 1 wherein the network adapter program executes a scanning protocol for sequentially exchanging data between the programmable controller and each of the I/O nodes on a regular schedule with a predetermined order.

### Claim 11 (depends on 1)

The network adapter of claim 1 wherein the programmable controller and I/O nodes communicate between each other using a buffer table subject to distinct read and write cycles.

### Claim 12 (depends on 1)

The network adapter of claim 1 further including a housing holding components of the network adapter and physically independent from the programmable logic controller and the I/O nodes.

### Claim 13 (depends on 1)

The network adapter of claim 1 further including a housing providing a backplane having releasable electrical connectors for receiving different I/O network cards for connection to the backplane.

### Claim 14

And industrial controller comprising:
a set of I/O nodes attached to networks and providing electrical connections to actuators and sensors of a controlled process;
a programmable controller having a stored program for controlling the controlled process by providing signals to the actuators and receiving signals from the sensors through the I/O devices;
a network appliance having:
(a) a plurality of I/O network interface circuits providing hardware connections to the different I/O networks of the I/O node;
(b) a controller network interface circuit providing a hardware connection to a controller network communicating with the programmable controller;
(c) a memory holding a network appliance program, script files, and configuration files;
(d) a processor executing the network appliance program to:
(i) store in memory, script files associated with the different I/O networks, the script files associated with particular I/O networks and executing to translate between protocols of the controller network and the particular I/O network;
(ii) receive from the programmable controller and store in memory, configuration files associated with particular I/O networks and describing configuration parameters for the particular I/O networks;
(iii) before communication between an I/O node and the programmable controller, configuring the I/O networks according to the associated configuration file; and
(iv) in response to communication between an I/O node and the programmable controller, execute a script associated with the I/O network to translate between protocols of the I/O network and controller network;
whereby the programmable controller may communicate with I/O nodes as if they were connected directly to the controller network.

### Claim 15 (depends on 14)

The network interface of claim 14 wherein the script files are received from the programmable controller.

### Claim 16 (depends on 14)

The network adapter of claim 14 wherein the script files further include a mapper translating between addresses on the controller network and addresses on the I/O network.

### Claim 17 (depends on 14)

The network adapter of claim 14 wherein the I/O network interface circuits provide electrical connectors allowing them to be removably attached to a common bus.

### Claim 18 (depends on 14)

The network adapter of claim 14 wherein the network adapter program executes a scanning protocol for sequentially exchanging data between the programmable controller and each of the I/O nodes on a regular schedule with a predetermined order.

### Claim 19 (depends on 14)

The network adapter of claim 14 wherein the programmable controller and I/O nodes communicate between each other using a buffer table subject to distinct read and write cycles.

### Claim 20 (depends on 14)

The network adapter of claim 14 further including a housing holding components of the network adapter and physically independent from the programmable logic controller and the I/O nodes.
