WO2005016552A2

WO2005016552A2 - User-friendly control system for coating equipment

Info

Publication number: WO2005016552A2
Application number: PCT/US2004/026077
Authority: WO
Inventors: James M. Khoury; Drew L. Roberts; Mark J. Ignatius
Original assignee: Nordson Corporation
Priority date: 2003-08-12
Filing date: 2004-08-12
Publication date: 2005-02-24
Also published as: WO2005016552A3

Abstract

Various embodiments of a control system for a material application system are disclosed. One control system embodiment comprises a spray monitor, an OPC server having OPC server logic for providing OPC-compliant communication with the spray monitor, and a client communicating with the OPC server.

Description

User-Friendly Control System for Coating Equipment RELATED APPLICATION

[0001] This application claims the benefit of U.S. provisional patent application serial no. 60/481,215 filed on Aug. 12, 2003 for MONITOR FOR FLUID DISPENSING SYSTEM, the entire disclosure of which is fully incorporated herein by reference. BACKGROUND OF THE INVENTION [0002] Fluids may be applied to any number of objects and surfaces by a variety of dispensing techniques including spraying. Dispensing systems typically include a dispensing device that may have a nozzle that produces a desired pattern, a pump and other related devices. It is often desirable to be able to monitor various flow characteristics of the fluid within the dispensing system in order to, for example, detect system malfunctions or wearing parts.

[0003] Exemplary monitoring systems are described in U.S. Pat. No. 5,999,106 (the

'"106 patent") issued to Buckler and U.S. Pat. No. 6,611,203 (the '"203 patent") issued to Whitmore et al., both owned in common with the assignee of the present invention, the entire disclosures of which are fully incorporated herein by reference. The '203 patent describes a fluid dispensing interface including a visual display coupled to a monitor. Such a visual display provides an improved user interface to system monitoring, but does not easily provide remote or distributed access to the monitors. SUMMARY OF THE INVENTION [0004] In accordance with one embodiment of the present invention, a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices is provided. The system includes a spray monitor, an OPC server having OPC server logic and a client communicating with the OPC server.

[0005] In accordance with another embodiment of the present invention, a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices is provided. The system includes a spray monitor means, a client and an OPC-compliant server means. [0006] In accordance with another embodiment of the present invention, a method for monitoring a fluid dispensing apparatus having a plurality of dispensing devices and a client is provided. The method includes the steps of providing OPC-compliant communication between the dispensing devices and the client, operating the dispensing devices via OPC- compliant communications and monitoring operation of the dispensing devices via OPC- compliant communication. [0007] In accordance with another embodiment of the present invention, a control system for fluid coating equipment is provided. The system includes an OPC server and a client. The client has a display device for displaying an operator interface. The operator interface has a plurality of icons providing navigation through the operator interface.

[0008] In accordance with another embodiment of the present invention, a control system for fluid coating equipment is provided. The system includes an OPC server and a client. The client has a display device for displaying an operator interface. The operator interface displays written words in a language of a user's choice.

[0009] In accordance with another embodiment of the present invention, a control system for fluid coating equipment is provided. The system includes an OPC server and a client. The client has a display device for displaying an operator interface. The operator interface has a master icon and provides a list of available icons upon actuation of the master icon.

[0010] In accordance with another embodiment of the present invention, a control system for fluid coating equipment is provided. The system includes an OPC server and a client. The client has a display device for displaying an operator interface. The operator interface has a dynamically-sizable area.

[0011] In accordance with another embodiment of the present invention, a control system for fluid coating equipment is provided. The system includes an OPC server and a client. The client has a display device for displaying an operator interface. The operator interface has a scalable display scaled to match a meter of a user. BRIEF DESCRIPTION OF THE DRAWINGS [0012] Fig. 1 is an exemplary overall system diagram of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices.

[0013] Fig. 2 is a block diagram of a logical component of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices.

[0014] Fig. 3 is an exemplary overall system diagram of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices.

[0015] Fig. 4 is an exterior view of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices.

[0016] Fig. 5 is an exterior and cutaway view of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices. [0017] Fig. 6 is a visual representation of a screen of an operator interface of a client of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices.

[0018] Fig. 7 is a visual representation of three screens of an operator interface of a client of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices.

[0019] Fig. 8 is a block diagram of components of an operator interface of a client of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices.

[0020] Fig. 9 is a visual representation of a screen of an operator interface of a client of a system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices. DETAILED DESCRIPTION [0021] The following includes definitions of exemplary terms used throughout the disclosure. Both singular and plural forms of all terms fall within each meaning. Except where noted otherwise, capitalized and non-capitalized forms of all terms fall within each meaning:

[0022] As used herein, "OPC" is used generically and generally means object linking and embedding for process control. "OPC" as used herein includes but is not limited to a plurality of standards and specifications for facilitating interoperability among objects, interfaces and methods of use in process control and/or manufacturing automation applications. An exemplary set of OPC standards is managed by the OPC Foundation of Scottsdale, Arizona, and is generally available at the OPC Foundation website at http://www.opcfoundation.org. Exemplary OPC Foundation OPC standards include, but are not limited to, OPC data access, OPC alarms & events, OPC historical data access and OPC data exchange. While embodiments set forth herein are described with reference to the OPC Foundation OPC standards, it will be appreciated that any suitable OPC standards, i.e., any suitable specifications or standards for facilitating interoperability among objects, interfaces and methods of use in process control and/or manufacturing automation applications, are optionally used. As used herein, "OPC compliant" is used interchangeably with "OPC standards compliant" and "OPC specifications compliant."

[0023] As used herein, "network" is used generically and includes but is not limited to the Internet, intranets, Ethernet, Virtual Private Networks, Wide Area Networks and Local Area Networks. [0024] As used herein, "logic" is used generically and includes but is not limited to hardware, software and/or combinations of both to perform a function. [0025] As used herein, "software" is used generically and includes but is not limited to one or more computer executable instructions, routines, algorithms, modules or programs including separate applications or from dynamically linked libraries for performing functions as described herein. Software may also be implemented in various forms such as a servlet, applet, stand-alone, plug-in or other type of application. Software can be maintained on various computer readable mediums as known in the art.

[0026] With reference to Fig. 1, a user- friendly control system for coating equipment

100 is shown. System 100 includes one or more dispensing device 110, one or more spray monitor 120, one or more OPC server 130 and one or more client 170. [0027] Dispensing device 110 is any suitable dispensing device, such as, for example, a fluid spray gun. While Fig. 1 illustrates a single dispensing device 110, it will be appreciated that a plurality of dispensing devices is optionally used. Operation of each dispensing device is monitored and/or controllable by a spray monitor 120. Spray monitor 120 includes one or both of monitor control 122 and machine control 124, as described in further detail in the '106 patent and the '206 patent. An exemplary spray monitor 120 is the iTrax™ Spray Monitor available from Nordson Corporation of Westlake, Ohio. Generally speaking, spray monitor 120 converts a characteristic or parameter of dispensing device 110 into an electrical signal or signals for monitoring use by system 100 and conversely converts electrical signal(s) into characteristics or parameters for controlling use by system 100. While Fig. 1 illustrates a single spray monitor 120, it will be appreciated that a plurality of spray monitors is optionally used, for example, a spray monitor for each dispensing device 110 or for each pair of dispensing devices 110.

[0028] Spray monitor 120 electrically communicates 150 with OPC server 130 by any suitable network or other suitable electrical connection. An exemplary suitable communication 150 is a Controller Area Network ("CAN") bus. OPC server 130 optionally includes CAN bus interface 135 for connecting to the exemplary CAN bus. [0029] OPC server 130 is any suitable computer capable of executing OPC server logic 140 and further capable of communicating 150 with at least one spray monitor 120 and communicating 160 with at least one client 170. Exemplary suitable computers include, but are not limited to, Intel™-processor based machines from, e.g., Dell or IBM. OPC server 130 runs on any suitable operating system, such as, e.g., Microsoft™ Windows™. While Fig. 1 illustrates a single OPC server 130, it is understood that a plurality of OPC servers is optionally used.

[0030] In an exemplary embodiment, OPC server 130 automatically detects and connects to one or more spray monitors 120. Auto detection and connection is achieved in any suitable manner. For example, in the event one or dispensing devices goes offline (such as, e.g., during a power down), the action of going online (such as, e.g., during re-power) optionally triggers the OPC server auto detect, and the OPC server automatically connects to the device. In this embodiment, typical network "log-on's" are optionally avoided via the OPC server auto detect and connect.

[0031] OPC server 130 includes OPC server logic 140. OPC server logic 140 includes any suitable steps, methods, processes and/or software for making OPC-compliant communications from and, optionally, to, spray monitor 120. OPC server logic 140 is embodied in any suitable programming language, such as, e.g., in Axeda FactorySoft™ OPC toolkit and Microsoft Visual Stuio.NET™ v7.0. In an embodiment, OPC server 130 receives a plurality of characteristic and/or parameter information from spray monitor 120 regarding the operation of dispensing device 110. OPC server logic 140 converts such characteristic and/or parameter information into OPC compliant information, facilitating access to such information by any OPC compliant client. In a further example, OPC server 130 receives OPC compliant controller instructions from an OPC compliant client. OPC server logic 140, using OPC standards, converts the controller instructions into electronic instructions suitable for controlling the dispensing device 110 via spray monitor 120. In this regard, any OPC compliant client is capable of communicating with a dispensing device 110 through a spray monitor 120, without knowing the specific and/or proprietary standards which govern the characteristics and/or parameters of the individual dispensing device.

[0032] With reference to Fig. 2, OPC server logic 140 optionally comprises one or more of OPC DA logic 210, OPC alarms and events logic 220, OPC historical data access logic 230, OPC data exchange logic 240 and any other suitable OPC compliant logic, such as, e.g., recognized by the OPC Foundation.

[0033] OPC DA ("Data Access") logic 210 includes any suitable steps, methods, processes and/or software for facilitating OPC compliant real-time data access with a dispensing device 110. For example, OPC DA logic 210 converts real-time data from a dispensing device 110 into an OPC DA compliant standard, such as the OPC DA specification provided by the OPC Foundation. OPC DA logic 210 thus facilitates real-time access to dispensing device 110 data by any OPC compliant client. [0034] OPC alarms and events logic 220 includes any suitable steps, methods, processes and or software for facilitating OPC compliant alarm and event notifications on- demand with a dispensing device 110. For example, OPC alarms and events logic 220 provides OPC compliant (e.g., compliant with the OPC alarms and events specification provided by the OPC Foundation) on-demand alarm processing, operator action and informational messaging, such as, e.g., tracking and/or auditing messages. OPC alarms and events logic 220 thus optionally facilitates on-demand interaction with a dispensing device 110, including the receipt of alarms from the device and the sending of operator actions (controls) to the device, all optionally from any OPC compliant client. [0035] OPC historical data access logic 230 includes any suitable steps, methods, processes and or software for providing OPC compliant access to previously-stored data. For example, with reference to Fig. 3, a system 100 optionally includes a database 310 for storing a plurality of historic characteristics and/or parameter values of a dispensing device 110. OPC historical data access logic 230 converts some or all of the data accessed from database 310 into an OPC compliant format (e.g., compliant with the OPC historical data access specification provided by the OPC Foundation) with OPC compliant queries which facilitates access to database 310 by any OPC compliant client. While Fig. 3 illustrates a single database 310, it will be appreciated that any number of databases 310 or other suitable data storage devices are optionally used.

[0036] With reference again to Fig. 2, OPC server 130 electronically communicates

160 with client 170 by any suitable mechanism, including but not limited to by any suitable network. In an embodiment, client 170 is a local client such as, e.g., an industrial flat panel PC, which is coupled to OPC server 130. Additionally and or alternatively, client 170 is a remote client which communicates 160 with OPC server 130 by any suitable network, such as an Ethernet network or the Internet (as described in further detail below). Client 170 optionally performs the functions of an operator control and/or a display control as set forth in the '106 patent and/or the '206 patent.

[0037] Client 170 interfaces with one or more dispensing devices 110 via OPC server

130 and one or more spray monitors 120. In embodiments wherein client 170 is capable of OPC compliant communication, client 170 communicates with OPC server 130 via OPC compliant queries and instructions. For example, client 170 obtains real-time data access to dispensing device 110 via an OPC DA compliant interface. Real-time dispensing device 110 data is monitored by a spray monitor 120, transmitted to an OPC server 130, converted to OPC DA compliant format by OPC DA logic 210 as shown in Fig. 2, and transmitted to client 170 in OPC DA compliant form. Similarly, client 170 provides on-demand controls (or receives on-demand alarms) to a dispensing device 110 by transmitting an OPC alarms and events compliant signal to OPC server 130. OPC alarms and events logic 220 converts the OPC compliant signal to an electrical signal receivable by spray monitor 120, and transmits same to spray monitor 120. Spray monitor 120 in turn transmits the signal to the dispensing device 110.

[0038] With reference to Fig. 3, system 100 optionally includes a plurality of remote clients in communication with one or more dispensing devices via OPC server 130. One or more remote OPC clients 320 and 322 electronically communicate 350 with OPC server 130 by any suitable means, including but not limited to by any suitable network, such as, e.g., an Ethernet network. While Fig. 3 illustrates two remote clients connected via a network 350, it will be appreciated that any suitable number of remote clients optionally electronically communicate with OPC server 130. Remote OPC client 320 and 322 include any suitable computing device capable of electronically communicating with OPC server 130. Exemplary computing device are personal computers or network computers running any suitable operating system. While remote OPC client optionally runs one or more software applications which are capable of electronic communication via one or more OPC standards, it will be appreciated that an OPC client is any suitable computing device capable of electronically communicating with OPC server 130.

[0039] OPC remote clients (for example, 320 and 322) optionally include software applications which are capable of OPC compliant communication. In this example, an OPC remote client communicates with OPC server 130 using OPC protocols and exchanges information pursuant to an appropriate OPC standard. For example, a user at OPC remote client 320 desires to access real-time performance data regarding a dispensing device coupled to spray monitor 120. OPC remote client 320 runs a software application which is OPC DA compliant, communicating with OPC server 130 to receive converted OPC DA compliant data from spray monitor 120 via OPC server 130. In this regard neither the OPC remote client nor the application running on the OPC remote client need know the communication protocols of spray monitor 120, as spray monitor's 120 real-time data feed is converted by OPC server 130 into a OPC DA compliant format. Furthermore, in the event multiple remote clients wish to communicate with a spray monitor, the spray monitor is not inundated with multiple requests for communication, as all such requests go to OPC server 130, which facilitates communication by multiple clients with spray monitor 120. In this regard multiple clients optionally ask for identical information (e.g., a plurality of clients desiring to access real-time data), and OPC server 130 fulfills the requests based upon a single real-time data feed from spray monitor 120.

[0040] OPC server 130 optionally facilitates communication between a plurality of remote clients in system 100. For example, database 310 is electronically connected 350 to OPC server 130 by any suitable means, such as, e.g., a network such as an Ethernet network. Database 310 is supported by any suitable remote client, such as, e.g., a computer which contains the database and one or more applications for accessing the database. In embodiments wherein database 310 is OPC compliant, such as OPC historical data access compliant, any other remote OPC client on network 350 or otherwise within system 100 can communicate with database 310. For example, remote OPC client 320 includes an application which is capable of database query and or other database interface via an OPC historical data access standard. Communicating via OPC server 130, remote OPC client 320 communicates with database 350 via an appropriate OPC standard. While this embodiment is illustrated with respect to access to a database, it will be appreciated that OPC server 130 facilitates communication between any suitable nodes of system 100 which are capable of OPC compliant communication.

[0041] System 100 optionally further includes one or more remote OPC clients 330 electronically communicating 345 with network server 340, which in turn electronically communicates 350 with OPC server 130. Remote OPC client 330 is any suitable remote OPC client. Communication 345 is any suitable remote communication, including but not limited to the Internet, a WAN, a LAN or a VPN. Network server 340 is any suitable network server capable of communicating with a network client. Remote OPC client 330 maintains a network connection with network server 340 via any suitable protocol. [0042] Network server 340 and OPC server 130 communicate via any suitable protocol. In an embodiment (with further reference to Fig. 2), OPC server 130 includes OPC data exchange logic 240. OPC data exchange logic 240 includes any suitable steps, methods, processes and/or software for facilitating OPC compliant data exchange between an OPC server and any other suitable server. An exemplary OPC compliant data exchange standard is the OPC data exchange standard from the OPC Foundation. Using OPC data exchange logic 240, OPC server 130 is capable of OPC compliant communication with any network server which is also capable of OPC compliant communication. With reference to Fig. 3, in an embodiment, network server 340 includes one or more software applications which facilitates electronic communication via an OPC data exchange standard. Under this standard, the network server electronically communicates with OPC server 130 to exchange OPC compliant data. In embodiments wherein remote OPC client 330 includes one or more applications capable of OPC compliant communication, remote OPC client 330 can issue or make an OPC compliant request or command to a dispensing device coupled to spray monitor 120. The OPC compliant communication is transmitted to network server 340, which in turn transmits the same to OPC server 130. In this regard the remote OPC client 330 need not know the communication protocols of the dispensing device, the spray monitor or any of the nodes in between. The remote OPC client need not even know how many nodes participate in the communication.

[0043] While Fig. 3 illustrates an exemplary system 100 having a plurality of remote

OPC nodes, it will be appreciated that system 100 optionally has a local client 170 coupled thereto or otherwise in electronic communication therewith. OPC server 130 is optionally capable of serving communication needs of both remote and local clients. [0044] It will be appreciated that a plurality of spray monitors 120 are optionally included in system 100 to monitor a plurality of dispensing devices. In an embodiment, a pair of spray monitors 120 and 380 are housed in a spray monitor enclosure 390. Enclosure 390 is any suitable monitor enclosure, including an industrial enclosure available from Nordson Coφoration of Westlake, Ohio. Enclosure 390 includes any suitable number of spray monitors, and optionally includes a power supply, a switch, and indicator and one or more terminal blocks. With reference to Figs. 4 and 5, an exemplary enclosure 390 is illustrated containing a pair of spray monitors 120 and 380. While exemplary system embodiments illustrated in Figs. 3, 4 and 5 illustrate a system having one enclosure 390, it will be appreciated that any suitable number of enclosures 390, containing any suitable number of spray monitors, may be used. For example, in a system having ten dispensing devices and enclosures housing two spray monitors each, five enclosures are used. [0045] With further reference to Figs. 4 and 5, in an embodiment OPC server 130 is contained in an industrial enclosure 400. Any suitable enclosure, such as available from Nordson Coφoration of Westlake, Ohio, is optionally used. Local client 170 is optionally coupled to enclosure 400. For example, local client 170 is optionally embodied in an industrial flat panel PC 410 having a display device 420 for interfacing with a user. With further reference to Fig. 4, enclosures 400 (with coupled client 170) and 390 are optionally mounted in proximity to each other.

[0046] Each client 170 includes a display device for facilitating interaction with a user. Any suitable display device is optionally used. In the example illustrated in Fig. 4, the display device includes a flat panel LCD display. For remote clients (e.g., as illustrated in Fig. 3), any suitable display device (e.g., a CRT or an LCD display) coupled to the computer which houses the software application(s) which comprise the client are used. While the remainder of this description will be made with reference to client 170, it will be appreciated that the following description is also applicable for any remote client, including remote OPC clients 320, 322 and 330.

[0047] Each client 170 includes an operator interface viewable on the display device of client 170 for facilitating interface between a user and client 170. The operator interface integrates with one or more input device(s) for facilitating user input to client 170. Any suitable input device or device(s) is used, including but not limited to a keyboard and a mouse. In an embodiment, the display device includes a touch screen for facilitating input from a user via touching the display device.

[0048] The operator interface is a part of one or more applications running on client

170 or optionally provides a "front end" GUI for accessing one or more applications running on client 170. In an embodiment, client 170 (either local or remote) is a OPC compliant client. In this embodiment, one or more applications running on client 170 are OPC compliant, and the operator interface optionally includes OPC compliant objects. While it will be appreciated that any suitable client having any suitable operator interface is optionally used, the remainder of this description is set forth with regard to an OPC compliant client having an operator interface which facilitates OPC compliant communication. [0049] With reference to Fig. 6, an exemplary screen 610 of an exemplary operator interface 600 is illustrated. Operator interface 600 is embodied in any suitable programming language, such as, e.g., Borland™ C++ Builder v6.0, and runs on any suitable operating system, such as, e.g., Microsoft™ Windows 2000™ or above. Operator interface 600 is supported at any suitable screen resolution, such as, e.g., 800 x 600 pixels and above. [0050] In an embodiment, operator interface 600 uses icons 620 and/or pictures 630 to navigate through the operator interface. For example, with reference to Fig. 7, fault resolution screens 700, 710 and 720 contain iconic and pictorial representations of components of the dispensing devices, rather than written descriptions thereof. To navigate through the fault resolution sections of the operator interface, or to select one of the dispensing device components displayed in screens 700, 710 or 720, a user need only identify the part by the picture and select the part by selecting the corresponding picture. In embodiments wherein the operator interface is included on a display device which supports a touch screen, a user need merely touch one of the pictures to select the component which is associated with the picture. [0051] To the extent words are used rather than icons and/or pictures (such as, e.g., in menu lists or captions), operator interface 600 supports a plurality of written languages. For example, when an English language user uses the system, words are displayed in the English language, while when a German language user uses the system, words are optionally displayed in the German language.

[0052] With reference to Fig. 8, operator interface 600 optionally includes one or more language files 810. Each language file contains language-specific words for use in specific instances within the operator interface. For example, with reference to Fig. 6, each object 640 and 650 contain labels for "Base," "Fire" and "Delta," which identify characteristics of dispensing devices "Gun 1" and "Gun 2." Operator interface 600 internally stores the labels for "Base," "Fire" and "Delta" as identifies irrespective of a particular spoken language. For example, internal identifiers may include "object base," "object display," "object delta" or similar identifiers. Each language file 810 contains a value for each internal identifier which is equal to the spoken language word which describes the identifier. For example, in the English language file, the value associated with "object base" is the word "Base." In the German language file, the value associated with "object_base" is the German word for "Base."

[0053] Operator interface 600 displays the words contained in the selected language file. For example, upon displaying a screen of operator interface 600, operator interface 600 accesses the selected foreign language file to obtain the word values associated with the identifiers contained within the displayed screen. An appropriate foreign language file is selected by any suitable means, including, but not limited to, by selection by a user during use of the operating interface.

[0054] In an embodiment, a user of an operator interface 600 optionally has a user profile 800, and operator interface 600 optionally has a plurality of user profiles, one for each user. Each user profile 800 contains an identifier of the foreign language file preferred by the user. For example, a user identified as "Bill" speaks English and has a user profile which identifies the English language file as the language file to be used when "Bill" uses the operator interface. In an embodiment, users must log into the client to use the client. Upon logging in, the identity of the user is revealed, and the operator interface uses the language file identified in the user profile associated with the identified user. While this embodiment has been described with reference to language files and/or user profiles, it will be appreciated that any suitable mechanism is optionally used to provide foreign language support in operator interface 600. Furthermore, while the above embodiments have been described with reference to "words," it will be appreciated that foreign languages optionally include foreign units of weights and measure.

[0055] While multiple foreign languages are supported in an embodiment of the operator interface, icons and pictures are used wherever practicable. In an embodiment, with reference again to Fig. 6, a screen of the operator interface includes a master icon 660. Master icon 660 is placed in any suitable location on the screen, such as, e.g., in the upper right-hand corner of the screen. Master icon 660, when actuated (by, e.g., clicking or touching with a touch screen) displays a list of all available icons and, optionally, the functions of such icons. Master icon 660 is optionally included on a plurality of screens in the operator interface, and is optionally included on all screens of the operator interface. Master icon 660, when actuated, optionally displays all icons available to the user in the operator interface. Alternatively, master icon's 660 actions upon actuation are dependant upon the screen upon which the icon resides. For example, in an embodiment wherein the master icon 660 is context-sensitive, actuating the icon will display all icons available only on the current screen.

[0056] In an additional embodiment, with reference to Fig. 9, icons and or other buttons of an operator interface are dynamically sizable. Exemplary mater icon 660 (at its normal size at 660) is dynamically resizable to any suitable smaller size (e.g., 810) or any suitable larger size (e.g., 820). Sizing is achieved in any suitable manner, including, but not limited to, by clicking and dragging a side or corner of the icon (or button) or by inputting a specified size. Dynamic sizing of icons and/or buttons facilitates changing the actuation area of each such icon or button. In embodiments wherein touch screens are employed as display devices, sizing of icons and/or buttons modifies the area upon which a user touches the screen to effectuate a selected icon or button. While dynamic sizing has been described herein with reference to icons and/or buttons, it will be appreciated that any area of the operating interface is optionally dynamically sizable.

[0057] In an additional embodiment, displays in the operating interface, such as, e.g., graphical displays of real-time data, are scaled in the display to match the meters of a particular installation, customer or user. For example, a particular user's meters have a certain range of value within the universe of available values. Displays in the operator interface which include such values are calibrated, or automatically scaled, to focus on the user's range of values rather than the universe of values available. Such scaling is accomplished by any suitable mechanism. An exemplary suitable mechanism is a software sensor calibration tool. Such a tool senses, or identifies, a user's meters (or range of values) in any suitable way, such as, e.g., receiving input from the user regarding the value or tracking historic values to identify a commonly-used range. The tool scales the display to match the user's meters (or range of values). Any suitable meter is optionally used, including, but not limited to, a graphical display of a dispensing device firing. [0058] While the present invention has been illustrated by the description of embodiments thereof, and while the embodiments have been described in considerable detail, the scope of the appended claims should not be restricted or in any way limited to such detail. Additional advantages and modifications will readily appear to those skilled in the art. Therefore, the invention, in its broader aspects, is not limited to the specific details, the representative systems, and illustrative examples shown and described. Accordingly, departures may be made from such details without departing from the spirit or scope of the invention disclosed herein.

Claims

What is claimed is: 1. A system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices, comprising: at least one spray monitor for monitoring at least one dispensing device; an OPC server having OPC server logic for providing OPC-compliant commumcation with the spray monitor; and at least one client communicating with the OPC server.

2. The system of claim 1, the OPC server logic having OPC DA logic for providing OPC-compliant access to the client for real-time data provided by the spray monitor.

3. The system of claim 1, the OPC server logic having OPC alarms and events logic for providing OPC-compliant on-demand communication between the client and the spray monitor.

4. The system of claim 1 further including previously-stored data, the OPC server logic having OPC historical data access logic for providing OPC-compliant access by the client to the previously-stored data.

5. The system of claim 1, the OPC server having a CAN bus interface, wherein the client and the OPC server communicate.

6. The system of claim 1 wherein the client is a local client coupled to the OPC server.

7. The system of claim 1 wherein the client is a remote client communicating with the OPC server via a network.

8. The system of claim 1 wherein the client is OPC-compliant.

9. The system of claim 8 wherein the client includes at least one application which is configured to communicate under an OPC standard.

10. The system of claim 1 wherein the client and the OPC server communicate via OPC-compliant communications.

11. The system of claim 1 further comprising a plurality of OPC-compliant clients which communicate with the OPC server via OPC-compliant communications.

12. The system of claim 11 wherein at least one client is local and at least one client is remote.

13. The system of claim 11 wherein at least one client communicates with at least one other client via the OPC server and via OPC-compliant communications.

14. The system of claim 1, further comprising a network server remotely communicating with a remote client, wherein the OPC server logic includes OPC data exchange logic for facilitating OPC-compliant communication between the OPC server and the network server, wherein the network server communicates with the OPC server via OPC- compliant communications, and wherein the remote client is OPC-compliant.

15. The system of claim 1 having at least two spray monitors contained in a single enclosure.

16. The system of claim 15 wherein the OPC server is contained in an industrial enclosure and coupled to a local client having a flat panel LCD display device.

17. The system of claim 1 wherein the client has a display device for interacting with a user.

18. The system of claim 17 wherein the display device displays an operator interface for receiving input from and sending output to a user.

19. The system of claim 18 wherein the operator interface includes at least one OPC-compliant object.

20. The system of claim 18, the operator interface having a plurality of icons to provide user navigation through the operator interface.

21. The system of claim 20 wherein navigation through the operator interface consists essentially of icons.

22. The system of claim 18 wherein the operator interface displays a plurality of written words in a language.

23. The system of claim 22 wherein the language is selectable by a user.

24. The system of claim 22 further including a plurality of language files, wherein each supported language has a language file, and each language file has a list of the plurality of written words in the language of the language file.

25. The system of claim 24 wherein the operator interface obtains the plurality of written words in a selected language from the language file containing words of that language.

26. The system of claim 25 further including a plurality of user profile files, each user profile file containing an identity of a user and the foreign language file preferred by the user.

27. The system of claim 18 wherein the operator interface includes a master icon.

28. The system of claim 27, the operator interface providing a list of available icons upon actuation of the master icon.

29. The system of claim 27, the operator interface providing a list of icons available on a screen having the master icon upon actuation of the master icon.

30. The system of claim 18 wherein the operator interface includes at least one dynamically sizable area.

31. The system of claim 30 wherein the area is a button.

32. The system of claim 30 having a display device having a touch screen, wherein the dynamically sizable area is a touch-actuated area.

33. The system of claim 18 wherein the operator interface includes at least one display which is scalable.

34. The system of claim 33 wherein the scalable display is scaled to match at least one meter of a user.

35. The system of claim 33 further having a software sensor calibration tool for scaling a display.

36. A system for monitoring a fluid dispensing apparatus having a plurality of dispensing devices, comprising: spray monitor means for monitoring at least one dispensing device; at least one client; and OPC-compliant server means for providing OPC-compliant communication between the client and the spray monitor means.

37. The system of claim 36, the client including an operator interface means for communicating with a user.

38. A method for monitoring a fluid dispensing apparatus having a plurality of dispensing devices and at least one client, comprising: providing OPC-compliant communication between the dispensing devices and the client; operating the plurality of dispensing devices via OPC-compliant communications from the client; and monitoring operation of the plurality of dispensing devices via OPC-compliant communication with the client.

39. The method of claim 38, the providing OPC-compliant communication step further including providing an OPC server having OPC server logic for converting communications from and to the dispensing devices into OPC-compliant communications.

40. The method of claim 38, further comprising: visually displaying an operator interface on a display device coupled to the client, the operator interface using a plurality of icons for navigation through the operator interface.

41. The method of claim 38, further comprising: visually displaying an operator interface on a display device coupled to the client, the operator interface displaying written words in a language of a user's choice.

42. The method of claim 38, further comprising: visually displaying an operator interface on a display device coupled to the client, the operator interface including a master icon for displaying available icons.

43. The method of claim 38, further comprising: visually displaying an operator interface on a display device coupled to the client, the operator interface including at least one dynamically sizable area.

44. The method of claim 38, further comprising: visually displaying an operator interface on a display device coupled to the client, the operator interface including at least one scalable display scaled to match at least one meter of a user.

45. A control system for a material application system, comprising: an OPC server providing OPC-compliant communication between the material application system and a client, the client having a display device for displaying an operator interface for providing user input and output for controlling the material application system via the OPC server, the operator interface having a plurality of icons providing navigation through the operator interface.

46. A control system for a material application system, comprising: an OPC server providing OPC-compliant communication between the material application system and a client, the client having a display device for displaying an operator interface for providing user input and output for controlling the material application system via the OPC server, the operator interface displaying written words in a language of a user's choice.

47. The system of claim 46, the operator interface further including a plurality of language files.

48. The system of claim 47, the operator interface further including a plurality of user profile files.

49. A control system for a material application system, comprising: an OPC server providing OPC-compliant communication between the material application system and a client, the client having a display device for displaying an operator interface for providing user input and output for controlling the material application system via the OPC server, the operator interface having at least one master icon and providing a list of available icons upon actuation of the master icon.

50. The system of claim 49, the list of available icons being contextually defined dependant upon the icons available on the screen from which the master icon was actuated.

51. A control system for a material application system, comprising: an OPC server providing OPC-compliant communication between the material application system and a client, the client having a display device for displaying an operator interface for providing user input and output for controlling the material application system via the OPC server, the operator interface having at least one dynamically-sizable area.

52. The system of claim 51, the display device including a touch screen, wherein the dynamically-sizable area is a touch-sensitive part of the screen.

53. A control system for a material application system, comprising: an OPC server providing OPC-compliant communication between the material application system and a client, the client having a display device for displaying an operator interface for providing user input and output for controlling the material application system via the OPC server, the operator interface having at least one scalable display scaled to match at least one meter of a user.

54. A control system for a material application system, comprising: a computer having a display device for displaying an operator interface for providing information for controlling the material application system, the operator interface having a plurality of icons providing navigation through the operator interface and further having a master icon which provides information about said plurality of icons.

55. The control system of Claim 54 further comprising a server computer providing communication between the material application system and the computer.

56. A control system for a material application system, comprising: a computer having a display device for displaying an operator interface for providing information for controlling the material application system, the computer further having an input device through which a user can log into the computer, the computer further including a memory which stores information identifying the user with a particular language, wherein when a user logs in, the computer accesses the memory to determine the language associated with the user and then displays information to the user through the display in the language associated with the user.

57. The control system of Claim 56 wherein the memory also stores information identifying the user with particular units of measure, and wherein when a user logs in, the computer accesses the memory to determine the units of measure associated with the user and then displays information to the user through the display in the units of measure associated with the user.

58. The system of claim 56, wherein the memory further includes a plurality of language files.

59. The system of claim 56, wherein the memory further includes a plurality of user profile files.

60. The system of claim 54 wherein the master icon provides a list of available icons upon actuation of the master icon

61. The system of claim 60 wherein the list of available icons is dependant upon the icons available on the screen from which the master icon was actuated.

62. A control system for a material application system, comprising: a computer having a display device for displaying an operator interface for providing information for controlling the material application system, the operator interface having at least one dynamically-sizable area.

63. The system of claim 62 wherein the display device including a touch screen, wherein the dynamically-sizable area is a touch-sensitive part of the screen.

64. A control system for a material application system, comprising a computer having a display device for displaying an operator interface for providing information for controlling the material application system, the operator interface having at least one scalable display scaled to match at least one meter of a user.

65. The control system of claim 64 wherein the meter is a graphical display of a dispensing device firing.

66. The system of claim 1 wherein the OPC server automatically detects one or more spray monitors.

67. The system of claim 1 wherein the automatic detection occurs in response to a re- power of a dispensing device.

68. The system of claim 66 wherein the OPC server automatically connects to an automatically detected spray monitor