Rockwell Automation Technologies Incorporated

Scott A Pierce

Kenwood H Hall

Eric D Decker

Terence Scott Tenorio

Andreas P Frischknecht

Robert J Kretschmann

Bret S Hildebran

Raymond R Husted

Harsh Shah

DuWayne D Mulhall

Peter M Delic

Richard O Ruggeri

Patrick D Telljohann

Anthony J Diblasio

Gregg M Sichner

Sivaram Balasubramanian

Anthony Gerard Gibart

Kendal R Harris

Jonathan D Bradford

Gregory J Svetina

David M Fort

Douglas Brian Sumerauer

Charmaine J Van Minnen

David A Pasela

Christopher E Stanek

Mark A Flood

Russell William Brandes

Mark A Chaffee

Gregory A Majcher

Kyle E Neet

Chandresh R Chaudhari

Edward C Korsberg

David Allen Johnston

Fabio Malaspina

Douglas W Reid

Jacob Strickler Baker

Petr Pitrinec

Anthony J Cachat

Steven A Zuponcic

James A Bizily

Robert R Sepsi

Dennis M Wylie

Roman Vitek

Paul Griesmer

Robert D Law

Luis A Capriles

Eryn Amara Danielle Manela

Michal Hanzeli

Martin Paulicek

Anthony Sorbello

John J Kolat, Jr

Antoon Laane

Mark Chaffee

Eric C Decker

Harsh P Shah

An industrial integrated development environment (IDE) allows project topologies to be defined using an industrial domain-specific language (DSL) script. DSL scripting language can be used to define a control system topology in terms of the devices that make up the control system as well as the data connections between those devices. The IDE system can translate resulting topology to a project tree that serves as the basis for a control system project.

Industrial automation system topology with point to point business rule integration

An industrial integrated development environment (IDE) allows add-on bus profiles and add-on controller profiles to be defined using an industrial domain-specific language (DSL) script. These add-on profiles can then be added to the IDE's device profile library for use in industrial control projects. This mitigates the need to write new source code to create these profiles and to release an updated version of the IDE software to make these profiles available for use. Industrial DSL scripting can also be used to define a physical and logical topology of an industrial control system within the IDE system as part of the control system project that will be deployed to the control system.

Extensible profiles for industrial controller devices

A system of communicating data over a high availability industrial control system is disclosed. The industrial control system includes a first data producer, a second data producer in communicative connection with the first data producer, a first data consumer, and a second data consumer in communicative connection with the first data consumer. The system further includes the first producer communicating the data over multiple connection paths from the first producer to the first consumer and the second consumer through intermediate modules, and the second producer communicating the data over multiple connection paths from the second producer to the first consumer and the second consumer through intermediate modules. Also disclosed is a method of communicating data over the high availability industrial control system.

System and method of communicating data over high availability industrial control systems

An industrial integrated development environment (IDE) can dynamically generate user interfaces for device profiles using predefined reusable profile templates together with data models of the devices for which the device profile interfaces are to be created. The device profile template defines features or components of profile interface views that are reusable across multiple different devices. The industrial IDE determines which interface features defined by the device profile template are required to support the device's data and supported features defined by the data model, and dynamically adapts the device profile template to yield a suitable device profile interface that can be used to view and edit the device's data and configuration parameter values.

Presentation design dynamic generation from data model server

A program environment is configured to allow building an industrial control program by instantiating classes of device types corresponding to industrial control devices in which each device type includes a device profile defining parameter(s) for communicating with the type of device and instruction(s) for causing the type of device to take action(s) in the program. Accordingly, device-specific instructions can be injected into logic of the control program. Such device type classes can correspond to various types of devices, such as variable frequency drives, mass flow meters, HART devices, and the like. A user interface can connect to the program environment to allow such devices to be instantiated from the device type classes and/or displayed to a GUI a diagrammatical arrangement. As a result, the control program can be developed with increased speed and reduced complexity.

System for building an industrial control program from device type classes having device specific instructions

An improved system for handling events in an industrial control system is disclosed. A module in an industrial controller is configured to generate an event responsive to a predefined signal or combination of signals occurring. The event is transferred to an event queue for subsequent execution. The event queue may also be configured to store a copy of the state of the module at the time the event is generated. The event queue may hold multiple events and each event is configured to trigger at least one event task. Subsequent events that occur during execution of the event task are stored in the event queue for later execution. An event, or combination of events, may trigger execution of an event task within the module, within the controller to which the module is connected, or within multiple controllers.

Method of managing event generation for an industrial controller

A method and system for interacting with data frames passing through a module connected to an industrial network is disclosed. Each module includes an aggregation unit located on the network interface above the physical layer. To transmit data, the aggregation unit reads a header from a dynamic data packet to determine if the module is a participant module for the packet. If so, the aggregation unit inserts data from the module into the data packet and transmits the packet to another module. To receive data, the aggregation unit reads a header from the data packet to determine whether the data packet includes data for the module. If so, the aggregation unit reads the data and passes the data packet to another module. If the aggregation unit determines that a data packet is not intended for the module, the data packet is passed to another module with no further interaction.

Method and system for data aggregation in an industrial communication protocol

An input module for an industrial controller includes configurable execution windows. The execution windows are defined by a first parameter and a second parameter stored within the input module. A third parameter defines a status bit which is compared against the execution window to set a window output signal within the input module. The execution window may define a range between the first and second parameters against which the status bit is compared. Alternately, the first and second parameters may define setpoints against which the status bit is compared. At one of the setpoints, the window output signal is set and at the other of the setpoints, the window output signal is reset.

Execution windows for an input module of an industrial controller

An input module for an industrial controller is configurable to simplify setup and commissioning. The input module includes input terminals configurable, for example, as a counter input. Still other input terminals may be configured to trigger events as a function of the input signals present at the terminals. Time signals corresponding to transitions in state of the input terminals, triggering of events, or operation of the counters may be recorded. The input module is further configurable to transmit data back to the processor or to transmit data directly to another module in the industrial control network.

User configurable terminals for an input module of an industrial controller

Event generation management for an industrial controller

An output module for an industrial controller configurable to simplify setup and commissioning is disclosed. The output module includes configurable PWM outputs that may be scheduled to start at different times within the PWM period, that may be configured to generate a fixed number of PWM pulses, and that may have an extendable PWM period. The output terminals are configurable to enter a first state upon generation of a fault and further configurable to enter a second state after a configurable time delay following the fault being generated. The output module may receive inputs signals directly from another module and set output signals at the terminals responsive to these signals.

Peer communication between modules in an industrial controller

A system for defining information for multi-option devices connected to an industrial network is disclosed. Each device has a single electronic data sheet (EDS) defining options associated with the device as well as each of the choices associated with those options. An option data sheet (ODS) is included for each option defining the device information corresponding to that option. A programmer interface may allow a programmer to select devices as well as the options for each of those devices associated with a control system. Each device is also configured to store the EDS and each ODS corresponding to that device within memory in the device. The programmer interface generates a controller configuration file defining the connections between each device and the controller.

Device class information support for multi-option devices

Growing community of inventors

Concord Township, OH, United States of America

Scott A Pierce