This invention relates generally to communications between controllers and modules and, more specifically, to wireless communications within programmable logic controller (PLC) systems.
PLCs have a variety of configurations, including rack mounted Input/Output (I/O) systems. The racks provide mechanical/electrical connection slots for a power supply, central processing unit (CPU) boards, and controlled I/O modules, which provide interfaces to external devices to be controlled. In a rack system, the CPU communicates across a fixed size backplane in a main rack with local I/O modules. In many applications, more I/O modules are needed than can fit in the main control rack. Therefore, expansion racks, or multiple expansion racks, are used to hold additional I/O modules. A communication link also exists between the main rack which includes the CPU and the expansion racks to allow data transfers between all I/O modules in the application and the main rack CPU.
Other PLC systems incorporate modular configurations which allow a CPU to interconnect to a varying number of I/O modules through a common connector interface, extending the backplane communication as each I/O base is added to the previous module. This allows flexibility in installation since there is not a fixed size, as in the rack systems. The I/O modules provide different functionalities to the PLC system but all use a common communication scheme passed through the module bases. Modular systems, also, do not have to be singularly interconnected but may use a communication link between groups of interconnected modular I/O. The modular system communication link is similar to the expansion rack communication links with the main CPU controlling the flow of data to all modular I/O groups either directly through the common base connectors and through the communication cable link to an expansion grouping, or groupings, of I/O modules.
Known PLC systems incorporate many different proprietary and standard communication protocols and configurations for communications between a CPU of a PLC and I/O modules and PLC expansion racks or groups. Known industrial communications standards are still evolving, and include many different standards.
In one aspect, a method for manufacturing includes providing a central processing unit (CPU) configured for a Programmable Logic Controller (PLC). The PLC includes a PLC module bus for coupling at least one PLC module to the CPU. The method also includes providing a means for wireless radio frequency communications. The method also includes operationally coupling the means for wireless radio frequency communications to the CPU such that the means for wireless radio frequency communications and CPU communicate without using the PLC module bus.
In another aspect, a method for communicating includes providing a wireless communication device and sending a wireless message from the wireless communication device to a PLC having a central processing unit (CPU) and a PLC module bus for coupling at least one PLC module to the CPU. The CPU is coupled to a means for wireless radio frequency communications such that the means for wireless radio frequency communications and CPU communicate without using the PLC module bus.
In another aspect, a PLC includes a backplane, at least one module connector, a CPU card mounted on the backplane, a CPU mounted on the CPU card, and a transmitter/receiver mounted on the CPU card. The transmitter/receiver is operationally coupled to the CPU.
The present invention provides wireless communications embedded in a PLC for communication to other PLC products, additional PLC racks of modules, remote I/O, Human Machine Interface (HMI) systems or programming software. The connection layout may include using a wireless hub/network access point, but could also allow direct wireless communications from one wireless product to another. It is also possible to use wireless communications to connect to a server which would allow data to be transmitted to Internet based systems. The present invention includes several communication paths such as, PLC to PLC, PLC to sets of modules (remote I/O), PLC to stand alone device (personal computer or standard network), remote PLC and a I/O wireless product to a control unit, or PLC to cellular network (and to the Internet).
In use, the CPU sends information to be wirelessly communicated across the PLC module bus to wireless communication module 18. After receiving the information, wireless communication module 18 transmits the information to a device. Typical devices include another system like system 10, a remote rack, a computer, and a remote Input/Output (I/O). Additionally, information that is received by wireless communication module 18 is sent by wireless communication module 18 across the PLC module bus to the CPU.
Wireless communication embedded in a PLC system allows for relocation of the racks and modules without having to rewire the system, thereby increasing the flexibility and maintainability of the customer. Embedding wireless communications in the head unit, either in the CPU, Network Interface Unit or a stand-alone product, reduces costs by not having to manufacture separate modules. In addition, embedding wireless communications on a remote I/O module allows customers to place the controlling module closer to the system being controlled or monitored, further reducing costs by eliminating wires that would otherwise be necessary between the I/O module and the system.
In use, information to be wirelessly radio frequency transmitted is sent from CPU 36 to transmitter/receiver 38 directly without necessarily being sent across the PLC bus. Rather, CPU 36 is integrated with transmitter/receiver 38 such that the information is communicated from CPU 36 directly to transmitter/receiver 38. This direct connection i.e., CPU 36 and transmitter/receiver 38 not having to use the PLC module bus to communicate, facilitates a faster communication rate for system 30 than for system 10 (shown in
Wireless communications embedded in a PLC enables communication to other PLC products, additional PLC racks of modules, remote I/O, HMI systems or programming software. The connection layout may include using a wireless hub/network access point, but could also allow direct wireless communications from one wireless product to another. It is possible to use wireless communications to connect to a server which allows data to be transmitted to Internet based systems. In one embodiment several communication paths are provided such as, PLC to PLC, PLC to sets of modules (such as a remote I/O), PLC to a stand alone device (such as a personal computer or a known network), remote PLC and a I/O wireless product to a control unit, or PLC to cellular network (and then optionally to the Internet). One example method of accomplishing this is to integrate a Bluetooth transmitter/receiver in the main PLC rack (master PLC) and each expansion rack. The master PLC can then communicate to each slave Bluetooth device, transferring information between the devices. While this example uses Bluetooth, it may also be accomplished using wireless Ethernet (IEEE 802.11) or cellular communications.
The herein described, wireless communication embedded in a PLC removes the dependence on data cables between components and allows for quicker addition of components without creating additional wiring.
Additionally, by removing the need for a wireless communication module 18, system 30 has more available module connectors 40. In one embodiment, integrated PLC wireless communication system 30 includes at least one I/O module (not shown) and system 30 is configured as a Network Interface Unit (NIU) 30. For example, NIU 30 can be fabricated by providing an IC200GBIOO1 NIU, which is commercially available from GE FANUC North America Automation Inc. of Charlottesville Va., and which includes a VersaMax™ CPU and integrating a commercially available transmitter/receiver with the CPU. In one embodiment, transmitter/receiver 38 is a Bluetooth protocol transmitter/receiver. In another embodiment, transmitter/receiver 38 uses a wireless ethernet protocol according to the IEEE 802.11 standard. Additionally, transmitter/receiver 38 can be configurable to use a conventional cellular standard.
By embedding wireless communications capabilities in the head end unit (either the CPU or Network Interface Unit), costs are reduced by not having to manufacture a separate wireless communication module. Embedding the communications on a remote I/O or stand alone PLC and I/O product (Micro), simplifies installation by maintaining the entire product in one package.
Each separate component in the PLC system has hardware capable of wireless communications. In one example, shown in
Because of the nature of wireless communications, limitations sometimes occur if either the PLC or a component is inside an enclosure 56, as shown in
Using wireless communications between system components removes data connections, which reduces complexity. By using wireless remote I/O products, many of the wire connections between a machine and the controlling unit can be shortened, thereby saving time and money. Wireless also allows the system components to move freely within the given range of the wireless data. Any industrial control system can use wireless communications as long as there is no interference on the particular wireless frequency (or frequencies).
Central processing unit 36 is programmed to perform functions described herein, and, as used herein, the terms CPU and processor broadly refer to processors, microcontrollers, microcomputers, application specific integrated circuits, field programmable gate arrays (FPGA) and other programmable circuits.
While the invention has been described in terms of various specific embodiments, those skilled in the art will recognize that the invention can be practiced with modification within the spirit and scope of the claims.
Number | Name | Date | Kind |
---|---|---|---|
5757021 | Dewaele | May 1998 | A |
5774357 | Hoffberg et al. | Jun 1998 | A |
5867386 | Hoffberg et al. | Feb 1999 | A |
5875108 | Hoffberg et al. | Feb 1999 | A |
5884010 | Chen et al. | Mar 1999 | A |
5901246 | Hoffberg et al. | May 1999 | A |
5903454 | Hoffberg et al. | May 1999 | A |
5920477 | Hoffberg et al. | Jul 1999 | A |
5986790 | Ota et al. | Nov 1999 | A |
6012161 | Ariyavisitakul et al. | Jan 2000 | A |
6081750 | Hoffberg et al. | Jun 2000 | A |
6125284 | Moore et al. | Sep 2000 | A |
6167514 | Matsui et al. | Dec 2000 | A |
6216013 | Moore et al. | Apr 2001 | B1 |
6226613 | Turin | May 2001 | B1 |
6278752 | Golden et al. | Aug 2001 | B1 |
6329139 | Nova et al. | Dec 2001 | B1 |
6418424 | Hoffberg et al. | Jul 2002 | B1 |
6434390 | Rahman | Aug 2002 | B2 |
6442217 | Cochran | Aug 2002 | B1 |
6459957 | Bennett, III et al. | Oct 2002 | B1 |
6492897 | Mowery, Jr. | Dec 2002 | B1 |
6507676 | Harrington | Jan 2003 | B1 |
6519705 | Leung | Feb 2003 | B1 |
6636749 | Holmes et al. | Oct 2003 | B2 |
7058040 | Schmidt | Jun 2006 | B2 |
Number | Date | Country | |
---|---|---|---|
20040095910 A1 | May 2004 | US |