Skid Communicator Tool Quick Connection Technique
Patent Information
- Application Number
- JP2020085032
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2019-05-20
- Filing Date
- 2020-05-14
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2040-05-14
Smart Images

Figure 0007591873000001 
Figure 0007591873000002 
Figure 0007591873000003
Abstract
Description
[Technical field]
[0001] The present disclosure relates generally to skids found in process control environments, and more specifically to a skid communicator tool that can quickly establish communications with a skid. [Background technology]
[0002] A process control system, such as a distributed or scalable control system such as those used in power generation, chemical, petroleum, or other processes, typically includes one or more controllers communicatively coupled to each other via a process control network to at least one host or operator workstation, and to one or more field devices via an analog, digital, or combined analog / digital bus. The field devices, which may be valves, valve positioners, switches, and transmitters (e.g., temperature, pressure, flow sensors), perform functions within the process or plant, such as opening and closing valves, switching devices on and off, and measuring process parameters. The controller receives signals indicative of process or plant measurements made by the field devices (or other information related to the field devices), uses this information to implement control routines, and then generates control signals that are sent over the bus to the field devices to control the operation of the process or plant. Information from the field devices and controllers is typically made available to one or more applications executed by the operator workstations, allowing the operator to perform any desired function related to the process or plant, such as viewing the current state of the plant, modifying the operation of the plant, etc.
[0003] Typically located within a process plant environment, a process controller receives signals indicative of process measurements or process variables produced by or associated with the field devices (or other information related to the field devices) and executes a controller application. The controller application implements a control module that makes process control decisions and generates control signals based on the received information and interfaces with control modules or blocks within the field devices, such as HART® and Fieldbus field devices. The control modules within the process controller send control signals over communication lines or signal paths to the field devices, thereby controlling the operation of the process.
[0004] Information from the field devices and process controllers is typically made available over the process control network to one or more other hardware devices, such as operator workstations, maintenance workstations, personal computers, handheld devices, data historians, report generators, centralized databases, etc. The information communicated over the network enables an operator or maintenance personnel to perform desired functions with respect to the process. For example, the information may enable an operator to change settings in process control routines, alter the operation of control modules in a process controller or smart field device, view the current state of a process or the status of particular devices in a process plant, view alarms generated by field devices and process controllers, simulate the operation of a process for purposes of training personnel or testing process control software, diagnose problems or hardware failures in a process plant, etc.
[0005] Field devices typically communicate with hardware devices over a process control network, which may be an Ethernet-configured LAN. The network relays process parameters, network information, and other process control data to various entities in the process control system through various network devices. The network devices typically facilitate the flow of data through the network by controlling its routing, frame rates, timeouts, and other network parameters, but do not normally modify the process data itself.
[0006] Some process plants include modular process skids ("skids") that may be integrated to various degrees into the process control system. A skid can be thought of as a "system in a box" that operates as a self-contained process or sub-process. Each skid typically includes a controller, such as a programmable logic controller ("PLC"). A PLC typically includes one or more processors, one or more memory or storage components, and specialized input / output (I / O) modules. Note that there are several important characteristics that distinguish PLCs from general-purpose computers. Most importantly, PLCs are typically more reliable and designed for mean time between failures measured in years. Second, PLCs can be deployed in industrial environments that have a significant amount of electrical noise, vibration, extreme temperatures, and humidity. Third, PLCs are easily maintained by plant technicians. Summary of the Invention
[0007] The described methods and systems allow a skid communicator tool to quickly change network settings to those required by a particular skid or network in a process control environment with which a user of the tool wishes to establish communications. These methods and systems are useful because skids and networks in a process control environment often require different network settings for any device attempting to communicate with the skid or network, and users must often manually load these network settings each time they wish to communicate with a different network or skid. In contrast, the described methods and systems allow a skid communicator tool to seamlessly connect, disconnect, and reconnect to either a skid or other network that requires different network settings with minimal input from the user, thus allowing a user to easily navigate and interact with different areas, units, or equipment of a process control environment.
[0008] In one embodiment, a skid communicator tool for communicating with a skid controller in a process control environment includes any one or more of a communications interface, one or more processors, memory, or a user interface component (e.g., including a display or input sensor, such as a touch screen, or one associated with an electromechanical input component such as a mouse, keyboard, or any other type of button). The skid communicator tool may be configured to do one or more of the following: (i) detect a link (which may be wired) between a communication interface and a skid controller for a skid in a process control environment; (ii) detect that a set of initial network settings does not enable a communication channel between the skid communicator tool and the skid controller over the link; (iii) perform an analysis of a plurality of pre-configured sets of network settings to identify a specific set of pre-configured network settings associated with the skid controller; and (iv) once a specific set of pre-configured network settings is identified through the analysis, (a) automatically configure the communication interface according to the specific set of reconfigured network settings to establish a communication channel over the link; and (b) control, monitor, or configure operation of the skid by sending or receiving skid data over the communication channel.
[0009] In one embodiment, a method for quickly connecting to a skid controller and downloading a skid configuration may include any one or more of: detecting, by the skid communicator tool, a link (which may be wired) between the skid controller and a skid communicator tool for a skid in a process control environment; detecting, by the skid communicator tool, that a set of initial network settings according to which the skid communicator tool is configured does not enable a communications channel between the skid communicator tool and the skid controller over the link; analyzing a plurality of sets of pre-configured network settings to identify a specific set of pre-configured network settings associated with the skid controller; once a specific set of pre-configured network settings is identified via the analysis: (a) automatically configuring, by the skid communicator tool, according to the specific set of pre-configured network settings to enable the skid communicator tool to establish a communications channel over the link; and (b) controlling, monitoring, or configuring operation of the skid by sending or receiving skid data over the communications channel.
[0010] It should be noted that this Summary is provided to introduce a selection of concepts that are further described below in the Detailed Description. As described in the Detailed Description, particular embodiments may include features and advantages that are not described in this Summary, and particular embodiments may omit one or more features or advantages described in this Summary. [Brief description of the drawings]
[0011] Each of the figures described below illustrates one or more aspects of the disclosed system(s) or method(s) according to an embodiment. The detailed description refers to the reference numbers included in the following figures.
[0012] [Figure 1A]FIG. 1 is a block diagram of an example process control environment including a set of skids and a skid communicator tool for communicating with and configuring the skids. [Figure 1B] FIG. 1B is a perspective view of one of the skids shown in FIG. 1A. [Diagram 2] FIG. 1C is a block diagram of the skid shown in FIG. 1B and the skid communicator tool shown in FIG. 1A. [Diagram 3] 1A and 2 , enabling the skid communicator tool to fully communicate with the skid controller according to a set of pre-configured network settings that match the set of whitelisting settings maintained by the skid controller shown in FIG. 2 . [Figure 4] 1A and 1B illustrate example displays that may be provided by the skid communicator tool shown in FIG. 2 prompting a user to confirm configuring the skid communicator tool according to a set of preconfigured network settings. [Diagram 5] 1A and 1B show an example display that may be provided by the Skid Communicator tool shown in FIG. 2 that allows a user to request restoration of a previous network configuration. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0013] A process plant, process control system, or process control environment that operates to control one or more industrial processes in real time may include one or more skids, each representing a modular, self-contained control system that controls a particular process or sub-process within the broader plant environment, and that are controlled in a manner that differs from the manner in which more typical field devices and other process control devices are controlled.
[0014] A portable skid communication tool may monitor, control, or perform configuration operations on a skid. Each skid may require different network settings for any device attempting to communicate with the skid, which may require a cumbersome reconfiguration process every time a user wishes to transition between skids. Utilizing one or more of the skid communication techniques, systems, apparatus, components, devices, or methods described herein, the skid communication tool allows for quick and seamless reconfiguration of the tool, allowing users to easily transition between skids.
[0015] Specifically, the portable skid communication tool allows for quick and seamless reconfiguration of network settings, allowing the tool to quickly connect, disconnect, and reconnect to skid controllers that implement restrictive access control policies. Note that skid controllers often implement restrictive access control policies. For security reasons, skid controllers often require that any device connecting to the skid controller have a specific static IP address or have one of a small number of specific static IP addresses. As a result, when an operator or technician on-site wishes to establish communication between his or her device and the skid controller, he or she must first manually configure the device to have the specific IP address required by the skid controller (e.g., where it is unlikely that the device will be assigned an appropriate IP address, as opposed to allowing the device to be dynamically assigned an IP address). This restricted access control policy helps prevent unknown, unauthorized, and potentially hostile parties from establishing connections to the skid, thus preventing such entities from intentionally or negligently disrupting the normal operation of a process or sub-process controlled by the skid, and preventing potential delays, lost revenue, and dangerous mechanical failures that may result from such disruption. Unfortunately, these restricted access control policies also often force manual reconfiguration of devices by technicians whenever they wish to communicate with the skid controller, which is inefficient and interrupts the technician's workflow. The portable skid communication tool described herein allows users to avoid this manual reconfiguration process.
[0016] With respect to a plant environment, when commissioned and operating online, a process plant includes one or more wired or wireless process control devices, components, or elements that perform physical functions in cooperation with a process control system to control one or more processes running within the process plant. A process plant or process control system may include, for example, one or more wired communication networks and / or one or more wireless communication networks. In addition, a process plant or control system may include centralized databases, such as continuous, batch, asset management, history, and other types of databases.
[0017] The following description is organized into sections that describe: (I) an example plant environment in which one or more skids and skid communicator tools can be seen, with reference to FIG. 1A; (II) examples of skids and skid communicator tools, with reference to FIG. 1B and FIG. 2; (III) example operations that may be performed by the skid communicator tools, with reference to the flowchart shown in FIG. 3 and the example displays shown in FIG. 4 and FIG. 5; and (IV) additional considerations.
[0018] Exemplary Plant Environment 5 FIG. 1A is a block diagram of an example process plant, process control system, or process control environment 5 including a set of skids 103-105 and a skid communicator tool 101 for communicating with and configuring the skids 103-105. Each of the skids 103-105 requires a different network setting for any device attempting to communicate with the skids 103-105. The tool 101 includes a skid client that allows the tool 101 to quickly change the network settings to the settings required by the particular skid with which a user of the tool 101 wishes to establish communication. As a result, while a user moves through and interacts with different areas, units, or equipment within the plant 5, the tool 101 can seamlessly connect, disconnect, and reconnect to any of the skids or other networks that require different network settings.
[0019] The process plant 5 controls a process that can be said to have one or more "process outputs" (e.g., tank levels, flow rates, material temperatures, etc.) that characterize the state of the process, and one or more "process inputs" (e.g., various environmental conditions and actuator states, actions that can change the process outputs). The process plant or control system 5 of FIG. 1A includes a field environment 122 (e.g., the "process plant floor 122") and a back-end environment 125, each of which are communicatively connected by a process control backbone or data highway 10, which may include one or more wired or wireless communication links and may be implemented using any desired or suitable communication protocol, such as an Ethernet protocol.
[0020] At a high level (and as shown in FIG. 1A ), the field environment 122 includes physical components (e.g., process control devices, networks, network elements, etc.) that are arranged, installed, and interconnected to operate to control a process during runtime. For example, the field environment 122 includes the I / O network 6. Generally, the components of the I / O network 6 are located, installed, or otherwise contained within the field environment 122 of the process plant 5. Generally, in the field environment 122 of the process plant 5, raw materials are received and processed using the physical components arranged therein to produce one or more products.
[0021] In contrast, the back-end environment 125 of the process plant 5 includes various components, such as computing devices, operator workstations, databases or databanks, etc., that are shielded or protected from the harsh conditions and materials of the field environment 122. In some configurations, the various computing devices, databases, and other components and equipment included in the back-end environment 125 of the process plant 5 may be physically located at different physical locations, some of which may be local to the process plant 5 and some of which may be remote.
[0022] Plant 5 Field Environment 122 As described above, the field environment 122 includes one or more I / O networks, each of which includes (i) one or more controllers, (ii) one or more field devices communicatively connected to the one or more controllers, and (iii) one or more intermediate nodes (e.g., I / O cards) that facilitate communication between the controllers and the field devices.
[0023] Generally, at least one field device performs a physical function (e.g., opening or closing a valve, raising or lowering a temperature, measuring, sensing a condition, etc.) to control the operation of a process implemented in the process plant 5. Some types of field devices communicate with a controller via an I / O device (sometimes referred to as an "I / O card"). The process controllers, field devices, and I / O cards may be configured for wired or wireless communication. Any number and combination of wired and wireless process controllers, field devices, and I / O devices may be included within the process plant environment or system 5.
[0024] For example, the field environment 122 includes an I / O network 6, which includes a process controller 11 communicatively connected to a set of wired field devices 15-22 via I / O card 26 and I / O card 28. The field environment 122 also includes a wireless network 70 that includes a set of wireless field devices 40-46 coupled to the controller 11 (e.g., via a wireless gateway 35 and network 10). The wireless network 70 may be part of the I / O network 6 or may be part of an I / O network not shown in FIG. 1A (and may include controllers or I / O cards not shown in FIG. 1A).
[0025] In some configurations (not shown), the controller 11 may be communicatively connected to the wireless gateway 35 using one or more communications networks other than the backbone 10. Such networks may include any number of nodes and wired or wireless communications links supporting one or more communications protocols such as HART®, WirelessHART®, Profibus, FOUNDATION® Fieldbus, or any one or more of the communications protocols, standards, or technologies identified in the “Additional Considerations” section.
[0026] Process Controller 11 The controller 11 may be, by way of example, a DeltaV™ controller sold by Emerson Process Management and may operate to implement a batch or continuous process using at least some of the field devices 15-22 and 40-46. In addition to being communicatively connected to the process control data highway 10, the controller 11 is also communicatively connected to at least some of the field devices 15-22 and 40-46 using, for example, standard 4-20 mA devices, I / O cards 26, 28, or any desired hardware and software associated with any smart communication protocol, such as FOUNDATION® Fieldbus protocol, HART® protocol, WirelessHART® protocol, etc. In FIG. 1A, the controller 11, field devices 15-22, and I / O cards 26, 28 are wired devices and the field devices 40-46 are wireless field devices. Of course, the wired field devices 15-22 and the wireless field devices 40-46 may conform to any other desired standard(s) or protocol, such as any wired or wireless protocol.
[0027] The process controller 11 includes a processor 30 that implements or oversees one or more process control routines 38 (e.g., stored in memory 32). The processor 30 is configured to communicate with the field devices 15-22 and 40-46, and with other nodes communicatively connected to the controller 11. It should be noted that any control routines or modules described herein may be implemented or executed in part by different controllers or other devices, if desired. Similarly, the control routines or modules 38 described herein implemented within the process control system 5 may take any form, including software, firmware, hardware, etc. The control routines may be implemented in any desired software format, such as using object-oriented programming, ladder logic, sequential function charts, function block diagrams, or any other software programming language or design paradigm. The control routines 38 may be stored in any desired type of memory 32, such as random access memory (RAM) or read-only memory (ROM). Similarly, the control routines 38 may be hard-coded, for example, into one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), or any other hardware or firmware elements. In short, the controller 11 may be configured to implement a control strategy or routine in any desired manner.
[0028] The controller 11 implements the control strategy using what are generally referred to as function blocks, where each function block is an object or other portion (e.g., a subroutine) of an overall control routine. The controller 11 may work in conjunction with function blocks implemented by other devices (e.g., other controllers or field devices) to implement process control loops within the process control system 5. A control-based function block typically performs one of the following: (i) an input function (sometimes referred to as an "input block"), such as those associated with a transmitter, sensor, or other process parameter measurement device; (ii) a control function (sometimes referred to as a "control block"), such as those associated with a control routine performing PID, fuzzy logic, etc.; or (iii) an output function (sometimes referred to as an "output block") that controls the operation of some device, such as a valve, to perform some physical function within the process control system 5. Of course, hybrid and other types of function blocks exist.
[0029] The function blocks may be stored within and executed by controller 11, which is typically the case when these function blocks are used for or associated with certain types of smart field devices, such as standard 4-20 mA devices and HART® devices, or the function blocks may be stored within and implemented by the field device itself, which may be the case for FOUNDATION® Fieldbus devices. One or more of the control routines 38 may implement one or more control loops that are performed by executing one or more of the function blocks.
[0030] Wired field devices 15-22 and I / O cards 26 and 28 Wired field devices 15-22 can be any type of device such as sensors, valves, transmitters, positioners, etc., while I / O cards 26 and 28 can be any type of process control I / O device conforming to any desired communication or controller protocol. In Fig. 1A, field devices 15-18 are standard 4-20 mA or HART® devices that communicate with I / O card 26 via analog lines or combined analog-digital lines, while field devices 19-22 are smart devices such as FOUNDATION® Fieldbus field devices that communicate with I / O card 28 via a digital bus using the FOUNDATION® Fieldbus communication protocol. Additionally or alternatively, in some embodiments, at least some of the wired field devices 15-22, or at least some of the I / O cards 26, 28, may communicate with the controller 11 using the process control data highway 10 or by using other suitable control system protocols (e.g., Profibus, DeviceNet, Foundation Fieldbus, ControlNet, Modbus, HART, etc.).
[0031] Wireless field devices 40-46 In FIG. 1A, the wireless field devices 40-46 communicate over a wireless process control communication network 70 using a wireless protocol such as the WirelessHART® protocol. Such wireless field devices 40-46 may communicate directly with one or more other devices or nodes of the wireless network 70 that are also configured to communicate wirelessly (e.g., using the wireless protocol or another wireless protocol). To communicate with one or more other nodes not configured to communicate wirelessly, the wireless field devices 40-46 may utilize a wireless gateway 35 that is connected to the process control data highway 10 or another process control communication network. The wireless gateway 35 provides access to the various wireless devices 40-58 of the wireless communication network 70. In particular, the wireless gateway 35 provides a communicative coupling between the wireless devices 40-58, the wired devices 11-28, or other nodes or devices of the process control plant 5. For example, the wireless gateway 35 provides a communicative coupling by using the process control data highway 10 or by using one or more other communication networks of the process plant 5.
[0032] Similar to the wired field devices 15-22, the wireless field devices 40-46 of the wireless network 70 perform physical control functions within the process plant 5, such as opening or closing a valve or taking a measurement of a process parameter. However, the wireless field devices 40-46 are configured to communicate using the wireless protocol of the network 70. In this manner, the wireless field devices 40-46, the wireless gateway 35, and the other wireless nodes 52-58 of the wireless network 70 are producers and consumers of wireless communication packets.
[0033] In some configurations of the process plant 5, the wireless network 70 includes non-wireless devices. For example, in FIG. 1A, the field device 48 of FIG. 1A is a conventional 4-20 mA device and the field device 50 is a wired HART® device. To communicate within the network 70, the field devices 48 and 50 are connected to the wireless communication network 70 via wireless adapters 52a, 52b. The wireless adapters 52a, 52b support a wireless protocol such as WirelessHART and are compatible with the Foundation (registered trademark) standard. 登録商標 1A , the wireless network 70 may also support one or more other communication protocols, such as Fieldbus, PROFIBUS, DeviceNet, etc. Additionally, in some configurations, the wireless network 70 includes one or more network access points 55a, 55b, which may be separate physical devices in wired communication with the wireless gateway 35 or may be provided within the wireless gateway 35 as an integrated device. The wireless network 70 may also include one or more routers 58 for forwarding packets from one wireless device to another within the wireless communication network 70. In FIG. 1A , the wireless devices 40-46 and 52-58 communicate with each other and with the wireless gateway 35 via wireless links 60 of the wireless communication network 70 or through the process control data highway 10.
[0034] Plant 5 backend environment 125 As mentioned above, the back-end environment 125 typically includes various components such as computing devices, operator workstations, databases or data banks, etc. that are shielded or protected from the harsh conditions and materials of the field environment 122. The back-end environment 125 may include any one or more of: (i) one or more operator workstation(s) 71; (ii) a configuration application 72a and a configuration database 72b; (iii) a data history application 73a and a data history database 73b; (iv) one or more other wireless access points 74 that communicate with other devices using other wireless protocols; and (v) one or more gateways 76, 78 to systems external to the instant process control system 5, each of which may be communicatively connected to the data highway 10.
[0035] Operator Workstation 71 Users (e.g., operators) may utilize the operator workstations 71 to view and monitor the runtime operation of the process plant 5, as well as take any diagnostic, corrective, maintenance, or other actions that may be required. At least some of the operator workstations 71 may be located within various protected areas within or near the plant 5, and in some situations, at least some of the operator workstations 71 may be located remotely but still communicatively connected to the plant 5.
[0036] The operator workstation 71 may be a wired or wireless computing device, and may be a dedicated or multi-purpose device. For example, in some embodiments, the set of applications, routines, or specially configured circuitry (e.g., ASICs) that enable the functionality provided by the workstation 71 may be implemented by any suitably configured computing device or set of computing devices (e.g., a desktop computer, a laptop, a mobile device such as a phone or tablet, a client / server(s) system, etc.) that allows access to the network 10, and may include a user interface with UI input or UI output components as identified in the "Additional Considerations" section, enabling a user of the workstation 71 to monitor run-time parameters, change run-time parameters, or perform or monitor diagnostic, corrective, or maintenance operations.
[0037] Configuration application 72a and database 72b A configuration application 72a and a configuration database 72b (collectively, the "configuration system 72") may be utilized to configure particular aspects of the plant 5. Various instances of the configuration application 72a execute on one or more computing devices (not shown) to enable a user to create or modify process control modules and download those modules to the controllers 11 via the data highway 10, as well as to enable a user to create or modify an operator interface through which an operator can view data and change data settings within the process control routines (e.g., an interface provided by the workstation(s) 71).
[0038] Typically, but not necessarily, the user interface for the configuration system 72 is distinct from the operator workstation 71 because the user interface for the configuration system 72 is utilized by configuration and development engineers regardless of whether the plant 5 is operating in real time, whereas the operator workstation 71 is utilized by an operator during real-time operation of the process plant 5 (also referred to herein interchangeably as “run-time” operation of the process plant 5). Each instance of the configuration application 72a may be implemented on any suitable computing device or set of computing devices (e.g., a desktop computer or workstation, a laptop, a mobile device such as a phone or tablet, a client / server(s) system, etc.), which may include a user interface with UI input or UI output components as identified in the “Additional Considerations” section.
[0039] During operation, the configuration database 72b stores process modules or user interfaces that have been created or otherwise configured by a user of the application 72a. The configuration application 72a and the configuration database 72b may be centralized and have a single logical appearance to the process control system 5, although multiple instances of the configuration application 72a may run simultaneously within the process control system 5. Additionally, the configuration database 72b may be implemented across multiple physical data storage devices. Thus, the configuration application 72a, the configuration database 72b, and the user interfaces to them (not shown) constitute a configuration or development system 72 for a control or display module.
[0040] In addition to enabling configuration of process modules and user interfaces, the configuration system 72 enables creation, assignment, and storage of logical identifiers for components and signals (e.g., field devices 15-22 and 40-46 and corresponding signals transmitted or received by field devices 15-22 and 40-46) within the plant 5. The logical identifiers may be referenced by control modules and devices implemented in the plant 5 to interact with the components (and associated signals) assigned to the logical identifiers. For example, one or more devices within the plant may each have an assigned “device tag” or “DT”. Additionally, one or more signals transmitted or received by devices within the plant may each have an assigned “signal tag”, which may also be referred to as a “device signal tag” or “DST”. In some cases, a DST need only be implemented for devices that transmit or receive multiple signals. Collectively, DTs and DSTs may simply be referred to as “tags”, “system tags”, or “system identifiers”. Often, a logical identifier has an associated value or set of values, each of which represents a particular variable value (e.g., a measurement) or command. Generally speaking, tags may be used by the process plant 5 in both the field environment 122 and the back-end environment 125 to uniquely identify an associated device or signal. For example, a control routine may reference the tag and the associated value to implement control of the plant.
[0041] To illustrate, for a given field device, configuration database 72b may store information that maps or binds a logical identifier or tag to a particular hardware address or I / O channel. The hardware address may identify a particular address for a particular controller, a particular I / O card connected to a particular controller, or an I / O channel that connects a particular I / O card to the field device. For example, configuration database 72b may store a binding that maps a tag to an I / O channel of I / O device 28 coupled to field devices 19-22, allowing devices in plant 5 to reference signals transmitted and received by each of field devices 19-22. In some cases, this mapping or binding may be stored in controller 11, user interface device 75, operator workstation 71, or any other desired device (e.g., any device that needs to resolve the logical identifier). After a tag is bound to a hardware address or I / O channel, the tag is considered "assigned."
[0042] As a second example, configuration database 72b may store a tag for skid 103 (e.g., "SK103"). Other devices may reference and communicate with skid 103 via the tag (although in some cases, the other devices may not be able to directly access, control, or communicate with the actuators, sensors, and other skid components of skid 103). The skid tag may be mapped to a hardware or network address associated with a monitoring system that connects skid 103 to network 10, as shown in FIG.
[0043] Data History 73a and Database 73b The data historian application 73a collects some or all of the data provided across the data highway 10 and historizes or stores the collected data in a history database 73b for long-term storage. The data historian application 73a and history database 73b may be centralized and have a single logical appearance to the process control system 5 (e.g., they may appear as a single application or suite of applications), although multiple instances of the data historian application 73a may run simultaneously within the process control system 5 and the data historian 73b may be implemented across multiple physical data storage devices. Each instance of the data historian application 73a may be implemented on any suitable computing device or set of computing devices (e.g., a desktop computer or workstation, a laptop, a mobile device such as a phone or tablet, a client / server(s) system, etc.), which may include a user interface with UI input or UI output components as identified in the "Additional Considerations" section.
[0044] Wireless Access Point 74 One or more other wireless access points 74 enable devices in the backend environment 125 (and sometimes in the field environment 122) to communicate with other devices using any suitable wireless communication protocol, such as Wi-Fi or any other wireless communication protocol or standard identified in the “Additional Considerations” section.
[0045] Typically, the wireless access point 74 enables a handheld or other portable computing device (e.g., user interface device 75) to communicate over a wireless process control communications network that is connected to the network 10 or is a sub-network of the network 10. This wireless network may be different from the wireless network 70 and may support a different wireless protocol than the wireless network 70. For example, the wireless or portable user interface device 75 may be a mobile workstation or diagnostic test equipment utilized by an operator (e.g., one instance of the operator workstation 71) in the process plant 5. In some scenarios, in addition to the portable computing device, one or more process control devices (e.g., the controller 11, the field devices 15-22, or the wireless devices 35, 40-58) also communicate using the wireless protocol supported by the access point 74.
[0046] Gateways 76 and 78 The gateways 76 and 78 may interface with systems external to the instant process control system 5. Typically, such systems are customers or suppliers of information generated or manipulated by the process control system 5. For example, the process control plant 5 may include a gateway node 76 for communicatively connecting the instant process plant 5 with another process plant. Additionally or alternatively, the process control plant 5 may include a gateway node 78 for communicatively connecting the instant process plant 5 with external public or private systems, such as a laboratory system (e.g., a laboratory information management system or LIMS), an operator round inventory control system, a product inventory control system, a production scheduling system, a weather data system, a shipping and handling system, a packaging system, the Internet, another provider's process control system, or other external systems.
[0047] 1A only illustrates a single wireless controller 11 with a finite number of field devices 15-22 and 40-46, a wireless gateway 35, a wireless adapter 52, an access point 55, a router 58, and a process control communications network 70 contained within an exemplary process plant 5, but this is merely an exemplary and non-limiting embodiment. Any number of controllers 11 may be included within a process control plant or system 5, and any of the controllers 11 may communicate with any number of wired or wireless devices and networks 15-22, 40-46, 35, 52, 55, 58, and 70 to control processes within the plant 5.
[0048] Skid 103 and Skid Communicator Tool 101 1B is a perspective view of skid 103 (also shown in FIG. 1A). Skid 103 is a modular, self-contained, and autonomous or semi-autonomous control system (compared to the larger control system implemented in plant 5). Examples of skids include bottle filling skids, cleaner skids, labeler skids, imprinter skids, cartoner skids, capper skids, wrapper skids, centrifuge skids, compressor skids, clean-in-place skids, etc.
[0049] The skid 103 includes a control cabinet 152, a frame 154, and a set of skid components 156. The control cabinet 152 may include a controller (e.g., a PLC) configured to monitor and control the skid components 156, which may include sensors (e.g., for measuring temperature, flow rates, pressure, fluid levels, etc.), actuators, and piping for material flow.
[0050] 2 is a block diagram of skid 103 and skid communicator tool 101 (also shown in FIG. 1A). Tool 101 includes a skid client 222 that allows tool 101 to quickly and automatically change network settings to those required by each of skids 103-105 or network 10, thereby allowing an operator of tool 101 to quickly and easily navigate and communicate between skids 103-105 and network 10 without having to spend a great deal of time manually updating network settings.
[0051] With respect to the communication links shown in FIG. 2, the tool 101 may be coupled to the skid 103 via a wired link 299, to the network 10 via a wired or wireless link 295, or to the monitoring system 230 via a wired or wireless link 298. The link 299 may be wireless in some examples, but for security reasons, it may be desirable for the link 299 to be wired. In some cases, the link 299 includes one or more intermediate nodes and sub-links. For example, the tool 101 and the skid 103 may be coupled through a networking device in the plant 5, such as a router, hub, or switch. As indicated by the dashed lines for the links 295 and 298, in some examples, the tool 101 may not be coupled to the network 10 or the supervisor 230.
[0052] With regard to the communication links to the skid 103, the skid 103 may communicate with the monitoring system 230 or the network 10 via a wired or wireless link 297, and the monitoring system 230 may be coupled to the network 10 via a wired or wireless link 296. If desired, the skid 103 may be coupled to the network 10 via a direct link (not shown). The following description details the components and functions of the skid 103, the tool 101, and the monitoring system 230.
[0053] Skid 103 The skid 103 is a modular process control system contained within a frame that allows the contained system to be easily transported and may be considered a self-contained "system in a box." An owner or operator of a plant 5 may avoid the time and effort spent purchasing a skid 103 and designing a corresponding system from the ground up.
[0054] Skid 103 includes a set of skid components 244-248 (e.g., corresponding to component 156 shown in FIG. 1B) and a controller 250 (e.g., located within cabinet 152 shown in FIG. 1B) that controls components 244-248. Each of components 244-248 may be any suitable process equipment or field device, such as a valve, a pump, a temperature / pressure / level / flow sensor or indicator, etc. Indeed, each component 244-248 may be similar or identical to one or more of field devices 15-22 and 40-46 shown in FIG. 1A.
[0055] The controller 250 of the skid 103 includes a processor 254 communicatively connected to a memory 252 and a communication interface 256, which enables the controller 250 to (i) connect to the network 10 and communicate with one or more nodes of the network 10, (ii) communicate with the tool 101, (iii) communicate with the monitoring system 230, or (iv) communicate with or control any one or more of the skid components 244-248.
[0056] The communications interface 256 may include any number and combination of wired and wireless interfaces. For example, the tools 101, the monitoring system 230, and the skid components 244-256 may all connect to the controller 250 through a single wireless card or adapter, or each may connect to the controller 250 through a different wired or wireless connection, port, or adapter. As shown in FIG. 2, the controller 250 may include a switch 257 integrated as part of the communications interface 256 and may include one or more exterior-facing ports (e.g., to which the tools 101 may connect) and one or more interior-facing ports or connection points (e.g., connecting the controller 250 to devices connected to the switch 257). Thus, the communication interface 256 may perform several functions typically associated with a switch, such as enabling or disabling ports (e.g., for the port to which the tool 101 is connected), adjusting link bandwidth and duplex settings, configuring and monitoring Quality of Service (QoS), filtering hardware addresses (e.g., MAC) and other access control list functions such as those associated with the IEEE 802.1X standard, configuring Spanning Tree Protocol (STP) and Shortest Path Bridging (SPB) functions, Simple Network Management Protocol (SNMP) monitoring of device and link health, port mirroring for traffic monitoring and troubleshooting, link aggregation configuration to set up multiple ports on the same connection to achieve higher data transfer rates and reliability, or network traffic snooping, etc. In some embodiments, the switch 257 may be external to the controller 250; i.e., it may be a component of the skid 103 and may couple the communication interface 256 of the controller 250 to other devices (e.g., the tool 101) connected to the switch 257.
[0057] The memory 252 stores instructions 253, including a set of routines 262 for controlling the components 244-248, and data 255, including a skid configuration 264, a set of skid parameters 266, and a set of whitelisting network settings 268. In operation, the controller 250 implements a control strategy defined by one or more control routines in the set of routines 262. When the processor 254 executes one or more of the control routines, the controller 250 transmits control signals (i.e., "control outputs") to the skid components 244-248 over a wired or wireless communication link or network to control the operation of a process or sub-process controlled by the skid 103. The controller 250 may generate the control signals based on (i) one or more received signals, which may be referred to as "control inputs" (e.g., one or more received signals representing measurements obtained by one of the skid components 244-248), and (ii) the logic of one or more control routines, which may be defined by one or more software elements (e.g., function blocks). Typically, the controller 250 manipulates process inputs (sometimes called "manipulated variables") to change a particular process output (sometimes called a "controlled variable") based on feedback (i.e., measured values of the controlled variables) and the desired value of the process output (i.e., set point).
[0058] Routine(s) 262 The routines 262 may take any form including software, firmware, or hardware. The routines 262 may be stored in any desired type of memory 252, such as RAM or ROM. Similarly, the routines 262 may be hard-coded, for example, in one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), or any other hardware or firmware elements. The routines 262 may include control routines, communication routines, security routines, or any other desired routines that may be utilized to facilitate operation of the skid 103.
[0059] As a first example, the routines 262 may include control routines or instructions implemented by the processor 254 to monitor or control the skid components 244-248. The control routines may be implemented in any desired software format, such as using object oriented programming, ladder logic, sequential function charts, function block diagrams, or using any other software programming language or design paradigm. The control routines may include one or more programs, each generally consisting of an interconnection of function blocks, which may be written in any of the IEC languages. The control routines may include declarations of physical inputs / outputs and variables.
[0060] As a second example, the routine 262 may include communications routines or instructions for facilitating the establishment of communications between the controller 250 and the tool 101 sufficient to enable the tool 101 to implement operations associated with the skid client 222 to control, monitor, and configure the controller 250.
[0061] As a third example, the routines 262 may include security routines or instructions implemented by the processor 254 to ensure secure communication and operation with the skid 103. For example, the controller 250 may identify the tool 101 or a user of the tool 101 by requesting an identity (ID). The controller 250 may authenticate the tool 101 or user by requesting that the tool provide "secret" information that only the controller 250 (or a connected server) and the tool 101 or user should know. Examples of secret information include a password, a PIN, a code, or some other "secret" information that the controller 250 can compare to a known "secret" for the ID. Additionally, the controller 250 may authorize the tool 101 or user to perform only certain authorized activities. For example, an ID may be authorized to monitor values of the skid parameters 266, but not authorized to write to the skid parameters 266, perform control operations, or download or upload the skid configuration 264. Additionally, the controller 250 may utilize a whitelisting setting 268 to implement an access control function. For example, the controller 250 may only allow the tool 101 to fully communicate with the controller 250 if the tool 101 has a particular IP address, a particular MAC address, a particular username or ID, etc. Specifically, the switch 257 may be configured to disable the port to which the tool 101 is connected, or may simply not forward traffic (or a subset of traffic) from the tool 101 to the controller 250 if the IP address or MAC address of the tool 101 is not included in a set of whitelisted addresses.
[0062] Skid Configuration 264 Skid configuration 264 is a package of data and instructions for configuring controller 250 and may be formatted as an XML file or set of files, or according to any other suitable format for such data sets. Configuration 264 includes the routines (e.g., routines 262) that are loaded and implemented (e.g., ladder logic, SFC diagrams, etc.), and the names, addresses, and initial values of parameters utilized by the routines. Configuration 264 may also include setup parameters for controller 250, such as a name for configuration 264, an IP address for skid 103, and a set of whitelisted network settings (e.g., IP addresses) that can be utilized to connect to controller 250.
[0063] When the configuration 264 is initially transferred to the skid 103 (e.g., from the tool 101, the supervisor 230, or from another computing device connected to the network 10), the information packaged in the configuration 224 may be extracted and loaded or installed so that the processor 254 can execute the included routines and read or write the parameters included in the configuration 224. The configuration 264 may initially be stored in long-term storage (e.g., non-volatile memory). Extracting or loading the packaged information may include transferring at least a portion of the packaged information to primary storage (e.g., volatile memory) and allocating address space for the included parameters and routines. The routines 262, parameters 266, and whitelisting settings 268 may be packaged in the configuration 264. After the configuration 264 is initially received by the controller 250, each of these items may be extracted and stored in the memory 250 in a manner that makes them accessible by the processor 254.
[0064] Skid parameters 266 The skid parameters 266 may include operational parameters, diagnostic parameters, or configuration parameters. Examples of operational parameters include process output parameters (e.g., tank levels, flow rates, material temperatures, etc.) that characterize the state of a process controlled by the skid 103, and process input parameters that may be adjusted to affect a change in the controlled process (e.g., to cause an actuator to change the state of a valve or pump, thereby changing one or more process outputs). Examples of diagnostic parameters include an index representing the health of one or more skid parameters 244-248, alarm parameters, communication status parameters indicating whether one or more skid parameters 244-248 or the communication interface 256 are communicating as intended, etc. Examples of configuration parameters include network configuration parameters, signal mapping parameters that map signals to and from the skid components 244-248 to operational parameters, or graphical displays (e.g., contained within the cabinet 152 shown in FIG. 1B) that may be displayed on a local display (not shown) of the skid 103 to enable monitoring of the skid 103.
[0065] Whitelisting network settings 268 The set of whitelisting network settings 268 includes network settings that allow another device to communicate with the controller 250, assuming the device is configured according to a set of network settings that are compatible with the whitelisting settings 268. In some cases, the whitelisting settings 268 may be a few more network settings than are utilized by the controller 250. Knowing these network settings allows another device, such as the tool 101, to be configured accordingly (e.g., to ensure that the tool 101 is on the same network or subnet as the controller 250). Additionally, in some cases, the whitelisting settings 268 may specifically identify specific network settings that should be used by the tool 101 attempting to communicate with the controller 250.
[0066] If desired, the whitelisted settings 268 may serve as a reference utilized by the controller 250 to control access by other devices to the controller 250 and, in some circumstances, may not be available or accessible by external devices such as the tool 101. In such circumstances, a user of the tool 101 may only be made aware of the specific details of the whitelisted settings 268, for example, by consulting a document (e.g., digital or paper) stored in a database connected to the network 10 or in a filing cabinet in a control room.
[0067] In other situations, some or all of the whitelisted settings 268 may be available or accessible to other devices, with their availability depending on one or more security measures. For example, the controller 250 may require the tool 101 to authenticate itself by providing a known name and password pair before accessing the whitelisted settings 268, or may allow access only if the hardware address (typically persistent) of the tool 101 matches a hardware address stored in a record of known and authorized addresses maintained by the controller 250 or by a database accessible by the controller 250. In any event, regardless of the accessibility of the whitelisted settings 268 to other devices, devices attempting to fully communicate with the controller 250 will generally need to be configured according to network settings compatible with the whitelisted settings 268.
[0068] The controller 250 and the tool 101 may be configured to communicate according to the Internet Protocol Suite (sometimes referred to as "TCP / IP"), and the whitelisted settings 268 may specify the skid IP address and subnet mask of the controller 250. Generally speaking, an IP address is a 32-bit number that includes two components: a network address and a host address. An example of an IP address is the binary number "11000000 10101000 00000001 00000001" or the decimal number "192.168.1.1". The subnet mask is a 32-bit number (e.g., the binary number "11111111 1111111 11111111 00000000" or the decimal number "255.255.255.0"), and a bitwise AND operation performed on the subnet mask and the IP address separates the IP address into a network address and a host address. A subnet mask contains a series of consecutive "1's" starting from the most significant bit, where every "1" indicates that the bit in the corresponding position in the IP address is part of the network address, and the remaining bits each have a value of "0" indicating that the bit in the corresponding position in the IP address is part of the host address.
[0069] Referring to the IP address and subnet mask example above, after the bitwise AND operation, the resulting network address is "192.168.1" and the resulting host address is "1". In total, 256 unique hosts can be part of this subnet, each with a unique IP address in the range "192.168.1.0" to "192.168.1.255". Devices with a different subnet than "192.168.1" cannot connect to this subnet without connecting to a network device, such as a router, that is connected to the subnet and has the appropriate IP address (e.g., 192.168.1.x) configured on its connection port.
[0070] Thus, the tool 101 utilizes the skid IP address and skid subnet mask to identify the subnet used by the controller 250 and potential host addresses that can be assigned to the tool 101, allowing the tool 101 to generate or otherwise assign itself an IP address that allows the tool 101 to communicate with the controller 250. For example, if the above example is implemented as a skid IP address ("192.168.1.1") and skid subnet mask ("255.255.255.0"), the tool 101 may be assigned an IP address "192.168.1.x", where "x" represents a wildcard having any value between 0 and 255. If the host address (represented by "x" in this example) is different from the address utilized by the controller 250 (e.g., "1") and all other devices connected to the subnet, the tool 101 may establish communication with the controller 250. As noted above, the controller 250 may require the tool 101 to perform one or more security measures before the tool 101 can perform the monitoring, control, and configuration operations described above.
[0071] In addition to or instead of the skid IP address and skid subnet mask, the whitelisted settings 268 may specify one or more authorized IP addresses. In such a scenario, the tool 101 may establish full communication with the controller 250 only if its IP address matches one of the authorized IP addresses in the whitelisted settings 268.
[0072] Surveillance system 230 The monitoring system 230 (or supervisor 230) is an electronic device configured to collect data from the controlled process (e.g., measurement data from the field devices or skids, diagnostic data, etc.) and send commands to the field devices and skids. The supervisor 230 may be essentially similar to the controller 11 shown in FIG. 1A and may be connected to the network 10, the backend 125, and any components connected to the network 10 in a similar manner.
[0073] At a high level, the monitoring 230 may be thought of as a gateway between the larger process control system 5 (and the corresponding high level control scheme implemented by the system 5) and the skid 103. Because the skid 103 may be self-contained and operate as a more or less autonomous process control system, it may not be fully integrated into a larger control scheme for controlling the plant 5 in the same manner that the field devices 15-46 are fully integrated. For example, the larger control scheme for the plant 5 may include routines specifically configured to directly control the field devices 15-46, but the larger control scheme may not directly control the skid 103. Rather, the skid 103 may implement its own specifically configured control routine(s), and the larger control scheme for the plant 5 may be primarily responsible for monitoring the skid 103 for proper operation. Because the supervisor 230 is often not expected to exercise direct control of the skid 103 based on real-time feedback, communications between the skid 103 and the supervisor 230 may have longer latency than that found in communications between, for example, the controller 11 and the field devices 15-46. In some instances, a larger control scheme may adjust parameters of the skid 103 (e.g., measured output targets such as temperature, pressure, flow rate, etc.) without accessing specific routines 262 of the skid 103, and the routines 262 may then attempt to control the skid 103 in light of the adjusted parameters.
[0074] Supervisor 230 may include a set of circuitry (not shown) configured to enable the described monitoring and control functions. For example, system 230 may include a processor, memory (e.g., for storing routines and data configured for the described operations), and a communication interface (e.g., for coupling supervisor 230 to network 10 and skid 103). In addition to or instead of software routines, in some examples, supervisor 230 may include customized circuitry configured to perform the described operations.
[0075] Skid Communicator Tools 101 The tool 101 is a portable electronic device configured to wirelessly communicate with the skid 103, allowing the tool 101 to (i) monitor parameters within the skid 103, (ii) adjust values of parameters within the skid 103 and send commands to the skid 103, (iii) download skid configurations from the skid 103, (iv) update or configure the skid configurations, and (v) upload skid configurations from the tool 101 to the skid 103. Unlike many user devices in a plant environment, the tool 101 can quickly and seamlessly connect, disconnect, and reconnect to any of a number of skids and networks that require different network settings. The tool 101 enables these seamless transitions because the user does not need to manually look up network settings or manually configure the tool 101 with network settings every time the tool transitions between a first skid (or network) having a first set of whitelisted network settings and a second skid (or network) having a second set of whitelisted network settings.
[0076] Traditionally, a typical network-enabled device in a plant environment is slow to transition between the network and devices that require different network configurations. As noted above, for example, many skids only allow a device to join the skid if the device is configured to have a specific IP address that is included in a small set of whitelisted IP addresses. Devices that are configured to dynamically set their own IP addresses rarely dynamically set their IP addresses to the addresses required by the skid. As a result, typically, a user must manually identify the whitelisted IP addresses and configure the device to have a static IP address that is included in the set of whitelisted IP addresses.
[0077] As a result, users often waste time manually looking up network settings and manually configuring devices to connect to the skid. Or, they may avoid the hassle altogether and simply avoid doing minor tasks that require connecting to the skid. As noted above, often times each skid in a plant environment requires a separate set of whitelisted network settings for any device attempting to connect to the skid, and a plant network, such as network 10, may require yet another set of network settings. Configuring a device according to any one of these sets may prevent the device from connecting to other skids or networks. This can be problematic because whenever a user wants to connect to a different network or device, the user must manually update the network settings on the device. For example, a user must first identify the whitelisted network settings of the first skid, which may not be immediately accessible. Ideally, the whitelisted network settings of a skid would be visibly posted on the skid itself, but these posted settings are often covered or otherwise replaced over time. In some cases, the whitelisted settings are not posted, forcing users to look to plant personnel, manuals and documentation, or the skid vendor to find the whitelisted settings. Even if the whitelisted settings are posted or otherwise made available, someone may update the skid's whitelisted network settings to reflect the new whitelisted settings without updating the posting.
[0078] In either case, assuming the user finds the whitelisted settings needed to connect to the skid, they must then navigate through several menus and prompts on the device to configure the device with network settings that correspond to those whitelisted for the first skid. When the user completes a task or project involving the first skid and wants to reconnect to the plant network or the second skid, they must again find and load the whitelisted settings for the plant network or the second skid. They must go through this process again each time they want to transition between skids, or between one of the skids and the plant network.
[0079] Advantageously, the tool 101 can quickly and seamlessly configure and reconfigure itself for any of several sets of network settings. As a result, while the network 10 may require a first set of whitelisted network settings that is separate from a second set of whitelisted network settings required by the skid 103, the tool 101 can quickly reconfigure itself according to each of the first and second sets of network settings, allowing the tool 101 to quickly switch between connections to the network 10 and the skid 103. Similarly, the skids 104 and 105 shown in FIG. 1A may require third and fourth sets of separate whitelisted network settings, and a user may make alternating connections between any one or more of the network 10, the skid 103, the skid 104, and the skid 105.
[0080] Continuing with FIG. 1A , the tool 101 may include a set of network settings 225 that correspond to the whitelisted settings 268 for the skid 103. The tool 101 may detect a physical connection to the skid 103 (e.g., by sending or receiving a discovery message) or detect user input indicating a desire to connect to the skid 103 and respond by identifying and loading the network settings 225 associated with the skid 103, allowing the tool 101 to quickly and seamlessly establish communications with the skid 103.
[0081] 2, the tool 101 may communicate with the skid 103 via wired link 299, with the supervisor 230 via wireless link 298, and with the network 10 via wireless link 295 (e.g., connecting the tool 101 to a wireless gateway 35). As indicated by the dashed lines for links 295 and 298, in some examples, the tool 101 may not be coupled to the network 10 or the supervisor 230. Depending on the implementation, any one or more of links 295, 298, and 299 may be wired or wireless links.
[0082] The tool 101 includes a processor 204 coupled to each of a memory 202, a communication interface 206, and an input / output (I / O) interface 208. The I / O interface 208 is coupled to one or more user interface (UI) components 210 including a display 211 and a set of input sensors 213. The display 211 may be any suitable display, such as an LCD display, a smartwatch display, a headset display (e.g., VR goggles), a projector, a touch display, or some combination thereof. The input sensors 213 may include any desired mechanical or electrical components, such as hardware actuators (e.g., "hard" buttons) or electrical sensors, such as resistive or capacitive touch sensors. Such touch sensors may be integrated with the display 211 as a touch screen. The UI 210 may include speakers for audio output, actuators for providing haptic feedback, etc. The tool 101 may include a power source 212 configured to provide power to other components of the tool 101. The memory 202 stores instructions 253, including a skid client 222, and data 205, including a skid configuration 224 and a set of pre-configured network settings 225-229.
[0083] Skid Client 222 Generally speaking, the skid client 222 is a set of routines including (i) routines or instructions that enable the tool 101 to communicate with the skid 103, and (ii) routines or instructions that enable the tool 101 to perform operations that facilitate monitoring, controlling, and configuring the controller 250 and the skid 103 via the tool 101. The client 222 may take any form including software, firmware, or hardware. The client 222 may be stored in any desired type of memory 202, such as RAM or ROM. Similarly, the client 222 may be hard-coded, for example, in one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), or any other hardware or firmware elements.
[0084] With respect to routines or instructions for communicating with the skid 103, the skid client 222 may enable the tool 101 to detect a skid ID of the skid 103, identify (e.g., automatically) a set of pre-configured settings linked to the skid ID, and load the set of pre-configured settings onto the tool 101 to enable a quick and seamless communication connection to the skid 103. The client 222 may also enable the tool 101 to create or update pre-configured settings for the skid 103 that can be used in the future to enable the tool 101 to automatically or seamlessly communicate with the skid 103. Updating or creating a set of pre-configured settings may include an auto-configuration process that includes requesting at least a portion of whitelisted network settings from the skid 103. Additional details regarding the tool 101 establishing communication with the skid 103 are described below in section IV with reference to an exemplary method illustrated in FIG. 3 that may be implemented, in whole or in part, by the client 222 and the tool 101.
[0085] With respect to routines or instructions that facilitate monitoring, controlling, and configuring the controller 250 via the tool 101, the skid client 222 may enable the tool 101 to perform any one or more of the following, depending on the particular configuration of the tool 101 and skid 103: (i) monitor parameters within the skid 103; (ii) adjust values of parameters within the skid 103 and send commands to the skid 103; (iii) download the skid configuration from the skid 103; (iv) update or configure the skid configuration; and (v) upload the skid configuration from the tool 101 to the skid 103.
[0086] Skid Configuration 224 Skid configuration 224 is a package of data and instructions for configuring controller 250 and may be formatted as an XML file or set of files. Configuration 224 includes routines (e.g., ladder logic, SFC diagrams, etc.) to be loaded and implemented by the skid's controller, as well as names, addresses, and initial values of parameters utilized by the routines. Configuration 224 also includes setup parameters, such as a name for configuration 224, an IP address of a skid that will receive and implement configuration 224, or a set of whitelisted network settings (e.g., IP addresses) that can be utilized to connect to a skid that will receive and implement configuration 224.
[0087] To illustrate, the configuration 224 may be transmitted to the skid 103 to configure the skid 103. When the configuration 224 is initially received by the controller 250 of the skid 103, the information packaged in the configuration 224 may be extracted and loaded or installed so that the processor 254 can execute the included routines and read and write parameters included in the configuration 224 (loading or installing may include allocating memory space and addresses in the memory 252 for the included parameters).
[0088] Set of pre-configured network settings 225-229 Each set of network settings 225-229 may specify a network address according to which the tool 101 should be configured to communicate with the skid, network, or device associated with the particular set. The network address may include an IP address and a subnet mask. Each set may also include a parameter indicating whether the tool 101 should have a static or dynamic network address.
[0089] Stated another way, each set 225-229 corresponds to a particular set of whitelisted configurations associated with a particular skid, network, or device. For example, configuration 225 may correspond to skid 103, configuration 226 may correspond to skid 104, configuration 227 may correspond to skid 105, configuration 228 may correspond to network 10, and configuration 229 may correspond to any other device or network.
[0090] Examples of actions implemented by the Skid Communicator tool 3 is a flow chart of an example method 300 for quickly configuring a skid communicator tool according to a set of network settings whitelisted by a skid controller, enabling the skid communicator tool to fully communicate with the skid controller. Method 300 may be implemented, in whole or in part, by skid communicator tool 101 shown in FIG. 2 and stored in memory as one or more instructions or routines. Although method 300 is described with reference to tool 101, skid 103, and other components of plant 5 shown in FIGS. 1-2, any suitably configured skid communicator tool may implement method 300 to communicate with any suitably configured skid.
[0091] Method 300 begins at step 301 when a wired link is established between the tool 101 and the skid controller 250 of the skid 103. Step 301 may include a user physically coupling the skid 103 and the controller 250 via any suitable medium utilized for communication, such as a coaxial cable, a twisted pair cable (e.g., an Ethernet cable such as a CAT3 to CAT7 cable), a fiber optic cable, a USB cable (e.g., compliant with USB 1.x, 2.x, or 3.x standards), a FireWire cable, a Thunderbolt cable, etc. In some cases, the link may be wireless in nature.
[0092] In step 302, the tool 101 detects a request to communicatively couple the tool 101 to the skid controller 250 via the wired link referenced in step 301. The tool 101 may automatically detect the request by detecting that the skid 103 is linked to another device via a wired link. In other words, step 302 may be automatic and occur without user intervention.
[0093] In some cases, step 302 includes a manual action involving a user. For example, the input sensor 213 may detect a user input representing a request (e.g., detect a touch input, an actuation of a physical button or key such as a mouse key, etc.). In some cases, the tool 101 may perform step 302 before step 301.
[0094] In step 304, the tool 101 determines whether communication with the controller 250 is enabled by the current network settings loaded into the tool 101. For example, the tool 101 may currently be configured according to a set of preconfigured network settings 228 for communicating with the network 10. If communication between the tool 101 and the controller 250 is not enabled by the current network settings (e.g., the network 10 settings 228), the tool 101 proceeds to step 306.
[0095] On the other hand, if communications between the tool 101 and the controller 250 is enabled by the current network settings, the tool 101 proceeds to step 332 and establishes a communications link with the controller 250 sufficient to enable the tool 101 to perform one or more of the operations described elsewhere in connection with the tool 101 to monitor, control, or configure the skid 103. Step 332 is described in further detail below.
[0096] In step 306, the tool 101 detects the skid ID of the skid 103 or the controller 250. The skid ID may be any suitable string or variable type having a value that identifies the skid 103 (e.g., "SK103"). The value of the skid ID may be referred to as a tag (e.g., a device tag) and may be unique to the skid 103 relative to other devices in the plant 5 and may be stored in the database 72b. Skids 104 and 105 may also have unique skid IDs or tags, such as "SK104" and "SK105."
[0097] Continuing with step 306, the tool 101 may automatically discover the skid ID of the skid 103 by sending a message to the controller 250 requesting the skid ID. The controller 250 may respond by transmitting the skid ID to the tool 101 or by transmitting unique information that allows the tool 101 to determine the skid ID (e.g., by transmitting a unique value stored in a database on the network 10 that can be queried by the tool 101 or that the tool 101 can utilize to identify the skid ID to correlate with). Alternatively, the tool 101 may detect the skid ID through a manual action involving a user. For example, the tool 101 may prompt the user (e.g., via a graphic or message provided via the display 211) to input the skid ID, which the user may provide via the input sensor 213.
[0098] At step 308, after detecting the skid ID, the tool 101 analyzes the memory 252 to identify a set of preconfigured network settings associated with the detected skid ID. Specifically, the tool 101 may analyze one or more stored sets of preconfigured settings 225-229. In some cases, the tool 101 may interact with a server (e.g., via the network 10) to identify a set of preconfigured network settings associated with the skid ID. For example, the tool 101 may send the skid ID to a server coupled to the network 10 along with a request for a corresponding set of network settings. The server may respond by analyzing a record of stored preconfigured network settings to determine whether any of the stored settings are associated with the received skid ID. If a suitable set of preconfigured network settings is found by the server, the server may send the settings to the tool 101. Otherwise, the server may send to the tool 101 to inform the server that no preconfigured network settings exist for the given skid ID.
[0099] In step 310, the tool 101 may either (i) not identify a set of preconfigured settings associated with the skid ID and proceed to step 312 and begin the configuration process (described in more detail below), or (ii) identify a set of preconfigured settings associated with the skid ID and proceed to step 329 or step 330 and load the preconfigured settings. With respect to the first scenario, for example, the tool 101 may determine that none of the preconfigured settings 225-229 are associated with the skid ID "SK103" and proceed to step 312, described in more detail below.
[0100] With respect to the second scenario referenced with respect to step 310, by way of illustration, the tool 101 may determine that a set of network settings 225 is associated with skid ID "SK103" and may proceed to step 329 or directly to step 330 (as indicated by the dashed line). If the tool 101 is configured to automatically detect and load pre-configured settings for a given skid (e.g., immediately after a user connects the tool 101 to the controller 250), then the tool 101 may proceed directly to step 330.
[0101] At step 329, the tool 101 detects a user request or confirmation that a pre-configured setting is to be loaded. To illustrate, FIG. 4 shows an exemplary display 400 of a GUI that may be provided on the display 211 of the tool 101. The user may actuate (e.g., click) a button labeled "Determine Network" to provide a request that has been detected by the skid 103. Note that display 400 requires little to no knowledge from the user regarding the particular network setting or name of the skid 103. The user simply clicks the button to load the appropriate setting and quickly establishes communication with the skid 103. The button or graphic element with which the user may interact to provide the request may have any suitable label. For example, the name or skid ID of the skid 103 may be displayed. After step 329, the tool performs step 330.
[0102] In step 330, tool 101 configures its network settings according to set 225. For example, tool 101 may set IP address and subnet mask settings according to the IP address and subnet mask specified by setting 225 (e.g., 192.168.1.3 and 255.255.255.0). As noted above, tool 101 may perform this step immediately after step 310 to allow for quick and automatic network configuration of tool 101 without user input. Tool 101 may then proceed to step 304.
[0103] In step 304 of this second scenario, the tool 101 may verify that full communication between the tool 101 and the controller 250 is enabled when the tool 101 is configured according to the set 225. Assuming that the loaded set 225 enables communication, the tool 101 proceeds to step 332 and establishes a communication link with the controller 250. However, if the loaded set 225 does not enable communication, then the loaded set 225 clearly does not match the whitelisted configuration 268 utilized by the controller 250. Thus, the tool 101 may return to step 304 and attempt to detect the skid ID again (e.g., if the initially detected skid ID was incorrect for some reason). Note that the tool 101 may proceed to step 312 to set up or configure (e.g., by updating set 225) a new set of pre-configured settings for the controller 250 and skid 103 because the whitelisted settings 268 may have changed since the set 225 was last created or updated and stored in the memory 202 of the tool 101. In any event, if one or more of steps 301-310, 329 and 330 do not result in the tool 101 identifying and loading a set of pre-configured settings associated with the skid ID that enables the tool 101 to fully communicate with the controller 250, the tool 101 proceeds to step 312.
[0104] At step 312, if automatic configuration of the tool 101 is not enabled, the tool 101 may proceed to step 314 to begin a manual configuration operation. If automatic configuration is enabled, the tool 101 may proceed to step 320. The tool 101 may determine whether automatic configuration is enabled based on the values of variables stored in memory 252. Alternatively or additionally, the tool 101 may prompt the user and request that the user enter a command indicating whether the user wants to proceed with manual or automatic configuration. This input may be as simple as pressing a graphical button labeled, for example, "Automatically Configure Network Settings."
[0105] At step 314, a manual configuration procedure may be initiated (e.g., if automatic configuration is not enabled or otherwise activated). The manual configuration may include two steps or sub-steps, namely, step 316 and step 318. At step 316, the tool 101 prompts the user to input a set of network settings that may be loaded into the tool 101 to enable the tool 101 to communicate with the skid 103. The prompt may include a text or numeric field and may request the user to input an IP address of the tool 101 or a subnet mask of the tool 101 that will enable the tool 101 to communicate with the skid 103. At step 318, the tool 101 receives the provided network settings (e.g., via a text or numeric field) and proceeds to step 328, which will be described in more detail below. As noted above, in some examples, the tool 101 performs an automatic configuration procedure of step 320 instead of the manual configuration procedure of step 314.
[0106] In step 320, the tool 101 performs an auto-configuration procedure (e.g., when auto-configuration is enabled and activated). The auto-configuration may include three steps or sub-steps: step 322, step 324, and step 326.
[0107] In step 322, the tool 101 sends a message to the controller 250 including a request for information that will enable the tool 101 to identify network settings that can be loaded into the tool 101 to enable the tool 101 to fully communicate with the controller 250.
[0108] In step 324, the tool 101 performs one or more security operations, if necessary. For example, the tool 101 may identify itself by sending to the controller 250 an identity or "ID" (e.g., the MAC address of the tool 101, the IP address of the tool 101, the username or user of the tool 101, or any other unique or relatively unique information linked to the tool 101 or user). In some circumstances, the tool 101 may facilitate authentication of itself by sending secret information (e.g., a password) linked to the ID to the controller 250. If necessary, the tool 101 may encrypt messages sent to the controller 250 and decrypt messages received from the controller 250. Note that step 324 may be performed at any time, if necessary, and may be repeated as necessary. For example, the tool 101 may perform step 324 before or after step 332, to the extent that the controller 250 requires that various security measures be met before granting certain monitoring, control, or configuration permissions to the tool 101. In some cases, the tool 101 does not perform step 324. In any case, the tool 101 may proceed to step 326 after steps 322 or 324.
[0109] In step 326, tool 101 receives network configuration information from controller 250. The received information may include whitelisted configuration 268 or a portion of whitelisted configuration 268. In some cases, the received information includes a particular network configuration that enables communication. In other examples, the received information includes information that enables tool 101 to generate or otherwise identify a particular network configuration that enables communication. In any event, after step 326, tool 101 performs step 328.
[0110] In step 328, the tool 101 analyzes the configuration information received in steps 318 or 326 to (i) identify pre-configured settings to load into the tool 101 to enable communication with the controller 250, and (ii) store the pre-configured settings in memory 202 such that they are referenceable by a skid ID (e.g., “SKD103”). As noted above, in some examples, the received information includes specific network settings that are saved as a set (e.g., set 225) of pre-configured network settings for the skid 103. For example, the tool 101 may analyze the received information to identify, depending on the embodiment, any one or more of the following within the received information: (i) a specific IP address and a specific subnet mask according to which the tool 101 should be configured; (ii) a range of potential IP addresses that may be utilized by the tool 101; (iii) a skid IP address and skid subnet mask utilized by the controller 250, which the tool 101 may analyze to generate an IP address for the tool 101; and (iv) a token that the tool 101 may utilize, for example, to query a database for an appropriate IP address. In either case, after tool 101 identifies a set of preconfigured network settings (e.g., IP address, subnet mask, static / dynamic indicator, or some combination thereof) that enable tool 101 to communicate with controller 250, tool 101 stores the set of preconfigured network settings in memory 202 (e.g., as set 225). For example, tool 101 may store set 225, which may include an IP address (e.g., 192.168.1.3), a subnet mask (e.g., 255.255.255.255), a static / dynamic indicator (e.g., "Static"), and a skid ID parameter having a value that correlates with an associated skid (e.g., "SK103"). After step 328, the tool performs step 329.
[0111] In step 329, the tool 101 may detect a request to load a pre-configured setting. As previously mentioned, in some examples, step 329 is not implemented and the tool 101 can proceed directly from step 328 to step 330.
[0112] In step 330, the tool 101 loads a set of pre-configured settings (e.g., set 225) stored in memory. The tool 101 then performs step 304. When performing step 304 after steps 330 and 328, the tool 101 performs steps 306-328 (i) if the pre-configured settings (e.g., set 225) do not enable the tool 101 to communicate with the controller 250, or (ii) if the pre-configured settings enable communication between the tool 101 and the controller 250, performs step 332. With regard to the former, steps 306-328 may be necessary, for example, if the user provided the tool 101 with incorrect settings during manual configuration (step 314). In any case, if the pre-configured settings enable the tool 101 to communicate with the controller 250, the tool 101 performs step 332.
[0113] In step 332, the tool 101 establishes a communications link (e.g., link 299) with the controller 250. Communications over link 299 generally conform to the TCP / IP protocol, but may conform to any additional or alternative desired protocols or standards (e.g., USB, Bluetooth, NFC, Wi-Fi, MODBUS / TCP, EtherNet / IP, HTTP, BootP, DHCP, DNS, SNTP, FTP, SNMP, SMTP, etc.).
[0114] After establishing communication, the tool 101 may perform any suitable of: (i) a monitoring or control operation, (ii) a read or write operation (e.g., reading or writing values of skid parameters 266), or (iii) a configuration operation. With respect to a configuration operation, the tool 101 may download the skid configuration 264 from the controller 250. The tool 101 may store the configuration 264 in the memory 202 as needed, and may update or modify the configuration 264 by adding, deleting, or adjusting routines or parameters of the configuration 264 (e.g., based on user input detected by the sensor 213). The skid configuration 224 stored in the memory 202 shown in FIG. 2 may represent an updated version of the configuration 264 or may represent a separate configuration. In any case, the tool 101 may upload the updated configuration 264 or configuration 224 to the controller 250, cause the controller 250 to load the configuration 224, and cause the controller 250 to operate according to the routines or parameters included in the updated configuration 264 or configuration 224.
[0115] When the user is finished interacting with skid 103, the user may again quickly change the settings of tool 101 to communicate with network 10, one of skids 104 or 105, or another device. For example, the user may connect tool 101 to a new skid, causing tool 101 to return to step 301.
[0116] As another example, when a user finishes interacting with skid 103, the user may request a change in network settings without establishing a wired connection to another skid. For example, the user may request that tool 101 revert to a previous network setting (e.g., the network setting of network 10) that was used prior to the current network setting. To illustrate, FIG. 5 shows an example display 500 of a GUI that may be provided on display 211. The user may activate a button labeled "Restore Previous Settings" to simply restore the settings that were loaded prior to the currently loaded settings (e.g., set 225). The previous settings may be stored in memory 202 (e.g., when tool 101 loads a new set of network settings). After loading the previous settings, tool 101 may proceed to step 304 and verify that communication with network 10 (or whichever skid, network, or device is associated with the previous settings) is valid.
[0117] Alternatively or additionally, the display 500 may include interactive elements (e.g., buttons, drop-down menus, etc.) specific to each set of stored preconfigured settings 225-229 (and thus specific to each skid, network, or device for which the tool 101 has preconfigured settings). In some cases, the tool 101 may display a search box that allows the user to search for a tag associated with a skid or network (e.g., "SK103"). In any case, when the user interacts with a graphical element that corresponds to one of the sets of preconfigured network settings 225-229, the tool 101 loads the corresponding set 225-229 and proceeds to step 304. If the loaded set does not work, the tool 101 may proceed to step 306 again.
[0118] It should be noted that in some circumstances, method 300 may include alternative or additional actions. For example, in addition to or instead of step 301, tool 101 may attempt to establish a wireless link to skid controller 250. In such an embodiment, tool 101 may fail to establish a wireless link and, in response to this failure and in response to a determination that the user wishes to communicatively couple tool 101 to controller 250, may proceed to step 306 of method 300. In some cases, tool 101 may establish a wireless link with limited communication capabilities. The limited wireless link may enable only certain types of messaging between tool 101 and controller 250, as desired (e.g., messages related to device / network identification, device / network discovery, authentication operations, and other security measures). This enablement of only certain types of messaging may be desirable even if tool 101 is configured according to a network configuration that complies with a whitelisted network configuration at skid 103, for example. In such a case, the tool 101 may perform one or more of the security operations discussed with reference to step 324 before proceeding to step 304 or step 332 .
[0119] Further considerations While this detailed description contemplates various embodiments, it should be understood that the legal scope of any claimed system or method is defined by the language of the claims set forth at the end of this patent. This detailed description should be construed as merely exemplary and does not describe every possible embodiment, as describing every possible embodiment would be impractical, if not impossible.
[0120] Throughout this specification, multiple instances may implement components, operations, or structures described as a single instance. Although individual operations of one or more methods have been illustrated and described as separate operations, one or more of the individual operations may be performed simultaneously in certain embodiments.
[0121] As used herein, any reference to "one embodiment" or "an embodiment" means that a particular element, feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrase "in one embodiment" in various places in the specification are not necessarily all referring to the same embodiment.
[0122] As used herein, the terms "comprises," "comprising," "includes," "including," "has," "having," or any other variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, article, or apparatus that includes a list of elements is not necessarily limited to only those elements and may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Furthermore, unless expressly stated to the contrary, "or" means an inclusive or, not an exclusive or. For example, a condition A or B is satisfied by any one of A being true (or present) and B being false (or absent), A being false (or absent) and B being true (or present), and both A and B being true (or present).
[0123] Additionally, the use of "a" or "an" is used to describe elements and components of the embodiments herein. This description, and the claims that follow, should be read to include one or at least one. The singular also includes the plural unless it is clear that it does not include the plural.
[0124] In various embodiments, the hardware systems described herein may be implemented mechanically or electronically. For example, a hardware system may include dedicated circuitry or logic that is permanently configured (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or application specific integrated circuit (ASIC)). A hardware system may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations (e.g., contained within a general-purpose processor or other programmable processor). It will be appreciated that the decision to mechanically implement a hardware system in dedicated and permanently configured circuitry or in temporarily configured circuitry (e.g., configured by software) may be made based on cost and time considerations.
[0125] Throughout this specification, some of the following terms are used.
[0126] Communications Interfaces. Some of the described devices and / or systems include a “communications interface” (sometimes called a “network interface”). For example, FIG. 2 The controllers 250 of the tool 101 and skid 103 shown in each diagram include a communication interface. The described communication interfaces allow the systems of which they are a part to send information or data to other systems or receive information / data from other systems. In some examples, the communication interfaces allow for the establishment of a direct link to another system (e.g., between the tool 101 and skid 103). In some cases, the communication interfaces allow for connection via a link to a network such as network 10 (e.g., a personal area network (PAN), a local area network (LAN), or a wide area network (WAN)).
[0127] Where appropriate, the described communications interfaces may include (i) circuitry to enable connection to a wired link (e.g., via coaxial or fiber optic cables) that carries electrical or optical signals to another device and communicates with other devices, or (ii) circuitry to enable wireless communication (e.g., short-range or long-range communication) via electromagnetic signals, such as radio frequency (RF) signals. The described communications interfaces and systems may conform to any one or more suitable communications protocols, standards, or technologies, such as those described herein.
[0128] Communications Protocols, Standards, Technologies. Examples of communications protocols, standards, or technologies that may be utilized in the described system include those that facilitate communications over a nanoscale network, a near field network, a personal area network ("PAN"), a local area network ("LAN"), a backbone network, a metropolitan area network ("MAN"), a wide area network ("WAN"), an Internet area network ("IAN"), or the Internet.
[0129] Examples of near field network protocols and standards include typical radio frequency identification ("RFID") standards or protocols, and near field communication ("NFC") protocols or standards. Examples of PAN protocols and standards include 6LoWPAN, Bluetooth (i.e., a wireless standard for exchanging data between two devices using radio waves in the range of about 2.4 to 2.485 GHz), IEEE 802.15.4-2006, ZigBee, Thread protocol, Ultra Wide Band ("UWB"), Universal Serial Bus ("USB"), Wireless USB, ZigBee, and ANT+. Examples of LAN protocols and standards include 802.11 protocols and other radio frequency protocols / systems for wireless communication in bands ranging from about 1 GHz to 60 GHz (including, for example, the 900 MHz, 2.4 GHz, 3.6 GHz, 5 GHz, or 60 GHz bands), as well as standards for suitable cables, such as coaxial cables and fiber optic cables. Examples of technologies used to facilitate wireless WANs include technologies used for LANs, as well as 2G (e.g., GPRS and EDGE), 3G (e.g., UMTS and CDMA2000), 4G (e.g., LTE and WiMAX), and 5G (e.g., IMT-2020) technologies. Note that the Internet may be considered a WAN.
[0130] Other communications protocols and standards that may be used include BitTorrent, Bluetooth Bootstrap Protocol ("BOOTP"), Domain Name System ("DNS"), Dynamic Host Configuration Protocol ("DHCP"), Ethernet, File Transfer Protocol ("FTP"), Hypertext Transfer Protocol ("HTTP"), infrared communications standards (e.g., IrDA or IrSimple), Transmission Control Protocol / Internet Protocol ("TCP / IP") (e.g., any of the protocols used in each of the TCP / IP layers), Real-Time Transport Protocol ("RTP"), Real-Time Streaming Protocol ("RTSP"), Simple Mail Transfer Protocol ("SMTP"), Simple Network Management Protocol ("SNMP"), Simple Network Time Protocol ("SNTP"), Secure Shell Protocol ("SSH"), and any other communications protocol or standard, or any combination thereof.
[0131] Communications Link. A "communications link" or "link" is a path or medium that connects two or more nodes. A link may be a physical link or a logical link. A physical link is the interface and / or medium(s) over which information is transferred and may be wired or wireless in nature. Examples of wired links include (i) cables with conductors (e.g., copper) for electrical energy transmission, such as coaxial cables and twisted pair cables (e.g., Ethernet cables such as CAT3-CAT7 cables), and (ii) fiber optic cables or connections for the transmission of light (e.g., typically utilizing glass as the transmission medium).
[0132] A wireless link may be a wireless electromagnetic signal that carries information via changes made to one or more characteristics of an electromagnetic wave(s). The wireless electromagnetic signal may be microwave or radio wave and may be referred to as a radio frequency or "RF" signal. Unless otherwise noted, the RF signals described may oscillate at a frequency within any one or more bands found in the spectrum from approximately 30 kHz to 3,000 GHz (e.g., 802.11 signals in the 2.4 GHz band). Examples of RF bands include the low frequency ("LF") band from 30 to 300 kHz, the medium frequency ("MF") band from 300 to 3,000 kHz, the high frequency ("HF") band from 3 to 30 MHz, the very high frequency ("VHF") band from 30 to 300 MHz, the extremely high frequency ("UHF") band from 300 to 3,000 MHz, the super high frequency ("SHF") band from 3 to 30 GHz, the millimeter wave frequency ("SHF") band from 30 to 300 GHz, and the tremendously high frequency ("THF") band from 300 to 3,000 GHz.
[0133] In some cases, the wireless electromagnetic signal may be an optical signal oscillating at a frequency between approximately 300 GHz and 30 PHz and having a wavelength between approximately 100 nm and 1 mm, which may be (i) an ultraviolet ("UV") signal having a wavelength in the range of approximately 10 nm to 400 nm and a frequency in the range of approximately 750 THz to 30 PHz, (ii) a visible light signal having a wavelength in the range of approximately 400 nm to 700 nm and a frequency in the range of approximately 430 THz to 750 THz, or (iii) an infrared ("IR") signal having a wavelength in the range of approximately 700 nm to 1 mm and a frequency in the range of approximately 300 GHz to 430 THz. Unless otherwise specified, the optical signals described may conform to any suitable optical signal protocol or standard, such as the Visible Light Communication (VLC) standard, the Light Fidelity (Li-Fi) standard, the Infrared Data Association (IrDA) standard, the IrSimple standard, etc.
[0134] A logical link between two or more nodes represents an abstraction of the underlying physical links or intermediate nodes that connect the two or more nodes. For example, two or more nodes may be logically coupled via a logical link. A logical link may be established via any combination of physical links and intermediate nodes (e.g., routers, switches, or other network equipment).
[0135] A link may also be referred to as a "communication channel." In wireless communication systems, the term "communication channel" (or simply "channel") generally refers to a particular frequency or frequency band. A carrier signal (or carrier wave) may be transmitted at a particular frequency or within a particular frequency band of a channel. In some cases, multiple signals may be transmitted in a single band / channel. For example, signals may be transmitted simultaneously in a single band / channel, sometimes over different sub-bands or sub-channels. As another example, signals may be transmitted over the same band, sometimes by allocating time slots, with each transmitter and receiver using that band.
[0136] Memory and Computer Readable Media. Generally speaking, the phrases "memory" or "memory device" as used herein refer to a system or device that includes a computer readable medium or media ("CRM"). A "CRM" refers to a medium accessible by an associated computing system for placing, retaining, or retrieving information (e.g., data, computer readable instructions, program modules, applications, routines, etc.). Note that "CRM" refers to a medium that is non-transitory in nature, and does not refer to intangible transitory signals such as radio waves.
[0137] A CRM may be implemented in any technology, device, or group of devices contained within or in communication with an associated computing system. A CRM includes volatile or non-volatile media, and removable or non-removable media. A CRM may include, but is not limited to, RAM, ROM, EEPROM, flash memory, or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, or any other medium that can be used to store information and accessed by a computing system. The CRM is communicatively coupled to a system bus, enabling communication between the CRM and other systems or components coupled to the system bus. In some implementations, the CRM may be coupled to the system bus through a memory interface (e.g., a memory controller). The memory interface is a circuit that manages the flow of data between the CRM and the system bus.
[0138] Network. As used herein, unless otherwise specified, when used in the context of systems or devices that communicate information or data, the term "network" means a collection of nodes (e.g., devices or systems that can send, receive, or forward information) and links that are connected to enable long-distance communication between the nodes.
[0139] A network includes dedicated routers, switches, or hubs responsible for forwarding or directing traffic between nodes, and, optionally, dedicated devices responsible for configuring and managing the network. Some or all of the nodes may also be adapted to function as routers to direct traffic sent between other network devices. Network devices may be interconnected in a wired or wireless manner, and network devices may have different routing and forwarding capabilities. For example, a dedicated router may be capable of large volume transmissions, while some nodes may be capable of sending and receiving relatively small amounts of traffic in the same period of time. In addition, connections between nodes on a network may have different throughput capabilities and different attenuation characteristics. Fiber optic cables, for example, may be capable of providing a bandwidth several orders of magnitude greater than a wireless link due to differences in the inherent physical limitations of the medium. A network may include a network or sub-network, such as a local area network (LAN) or a wide area network (WAN).
[0140] Node. Generally speaking, the term "node" means a connection point, a redistribution point, or a communication end point. A node can be any device or system (e.g., a computer system) that can transmit, receive, or forward information. For example, an end device or end system that originates or ultimately receives a message is a node. Intermediate devices that receive and forward messages (e.g., between two end devices) are also generally considered to be "nodes."
[0141] Processor. Various operations of the method examples described herein may be performed, at least in part, by one or more processors. Generally speaking, the terms "processor" and "microprocessor" are used interchangeably and each refers to a computer processor configured to retrieve and execute instructions stored in a memory. By executing these instructions, the processor may perform various operations or functions defined by the instructions. The processor may be temporarily configured (e.g., by instructions or software) or permanently configured to perform the associated operations or functions (e.g., a processor for an application specific integrated circuit or ASIC), depending on the particular embodiment. Each processor may be part of a chipset, which may also include, for example, a memory controller or an I / O controller. A chipset is a collection of electronic components in an integrated circuit typically configured to provide I / O and memory management functions as well as a number of general-purpose or special-purpose registers, timers, etc. Generally speaking, one or more of the described processors may be communicatively coupled to other components (such as memory devices and I / O devices) via a system bus.
[0142] Certain performance of an operation may reside not only within a single machine, but may be distributed among one or more processors deployed across several machines. In some embodiments, one or more processors may reside in a single location (e.g., in a home environment, in a work environment, or as a server farm), while in other embodiments, the processors may be distributed across multiple locations.
[0143] Words such as "processing," "computing," "calculating," "determining," "presenting," "displaying," etc. may refer to machine (e.g., computer) operations or processes that manipulate or transform data represented as physical (e.g., electrical, magnetic, or optical) quantities in one or more memories (e.g., volatile memory, nonvolatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.
[0144] Routines. Unless otherwise specified, a "routine" or "application" as described in this disclosure refers to a set of computer-readable instructions that may be stored in a CRM. In general, a CRM stores computer-readable code ("code") representing or corresponding to instructions, the code adapted to be executed by a processor to facilitate the functionality described as represented by or associated with the routine or application. Each routine or application may be implemented via a standalone executable file, a suite or bundle of executable files, one or more non-executable files utilized by an executable file or program, or some combination thereof. In some cases, unless otherwise specified, one or more of the routines described may be hard-coded into one or more EPROMs, EEPROMs, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or any other hardware or firmware elements.
[0145] Additionally, unless otherwise specified, each routine or application may be embodied as (i) a stand-alone software program, (ii) a module or submodule of a software program, (iii) a routine or subroutine of a software program, or (iv) a resource that is invoked or accessed by a software program via a "call" that causes the system to perform a task or function associated with the resource. The call may be (i) a "function call" invoked to cause execution of a resource (e.g., a set of instructions) stored in a library accessible by the software program, (ii) a "system call" invoked to cause execution of a system resource (e.g., often executed in privileged kernel space and executable only by an operating system), (iii) a "remote call" invoked to cause a logical or physical entity having a different address space to execute a resource, or (iv) some combination thereof. As an example, a routine executed by a processor of a device may invoke a "remote call" to cause execution of a resource in (i) a second device (e.g., a server host, an end-user device, a networking device, a peripheral device that communicates with the device, or some other physical device); (ii) a virtual machine on the same or a different device; (iii) a processor (e.g., a CPU or GPU) that is different from the original processor and may be internal or external to the device executing the routine; or (iv) some combination thereof.
[0146] Each routine may be represented by code implemented in any desired language, such as source code (e.g., interpretable for execution or compilable into lower level code), object code, byte code, machine code, microcode, etc. The code may be written in any suitable programming or scripting language (e.g., C, C++, Java, Actionscript, Objective-C, Javascript, CSS, Python, XML, Swift, Ruby, Elixir, Rust, Scala, etc.).
[0147] User Interface (UI). Generally speaking, a user interface refers to the components of a computer system through which a user interacts with the computer system. UI components can be hardware, software, or some combination thereof, and can include UI input components, UI output components, or some combination thereof.
[0148] Examples of UI output components include (i) visual output components such as lights (e.g., LEDs) and electronic displays (e.g., LCD, LED, CRT, plasma, projection displays, heads-up displays, etc.), (ii) audio output components such as speakers, and (iii) movement generation components such as motors that provide haptic feedback.
[0149] Examples of UI input components include: (i) mechanical or electrical components for detecting physical or touch input, such as hardware actuators (e.g., those used in keyboards, mice, "hard" buttons found on tablets or phones, etc.) or electrical sensors (e.g., resistive or capacitive touch sensors); (ii) audio sensors (e.g., microphones) for detecting audio input, such as voice commands; (iii) image sensors for detecting image or video input, such as those found in a camera (e.g., allowing for facial recognition or gesture input without requiring the user to touch the device); and (iv) motion sensors (e.g., accelerometers, gyroscopes, etc.) for detecting movement of the computer system itself (e.g., allowing a user to provide input by rotating or otherwise moving the computer system).
[0150] Some systems provide a graphical user interface (GUI) through a UI output component, such as an electronic display. Generally speaking, a GUI is generated through routines and allows a user to interact with indicators and other graphical elements that are displayed on the electronic display. Generally speaking, the graphical elements of a GUI can be GUI output elements (i.e., that convey some information to the user), GUI control elements (i.e., that are user "interactive" to cause the system to perform an action), or both (e.g., an icon may include an image representing a browser and may be interacted with to launch the browser).
[0151] Examples of GUI control elements include buttons (e.g., radio buttons, check boxes, etc.), sliders, list boxes, spinner elements, drop-down lists, menus, menu bars, toolbars, interactive icons, text boxes, windows that can be moved or minimized and maximized, etc.
[0152] Generally speaking, a window is an area on the screen that displays information, whose contents are displayed independently of the rest of the screen. A menu is generally a list of selectable options that a user can select to perform a corresponding command (e.g., expanding the menu to reveal additional options, spawning a new window, etc.). An icon is generally a small picture that represents an object such as a file, an application, a web page, or a command. A user can typically interact with an icon (e.g., pressing or clicking once or twice) to perform a command, open a document, or run an application.
Claims
1. 1. A skid communicator tool for communicating with a skid controller in a process control environment, comprising: a communications interface configured according to a set of initial network settings; one or more processors coupled to the communication interface, (i) detecting a link between the communications interface and a skid controller for a skid in a process control environment; (ii) detecting that the set of initial network settings does not enable a communications channel between the skid communicator tool and the skid controller over the link; (iii) performing an analysis of a plurality of pre-configured sets of network configurations to identify a particular pre-configured set of network configurations associated with the skid controller; (iv) once the particular set of pre-configured network settings is identified via the analysis, (a) automatically configuring the communication interface according to the particular set of pre-configured network settings to establish the communication channel over the link; (b) one or more processors configured to control, monitor, or configure operation of the skid by sending or receiving skid data over the communication channel.
2. the skid communicator tool further includes a user interface coupled to the one or more processors; the one or more processors are further configured to detect, via the user interface, a request to enable the communication channel; The skid communicator tool of claim 1 , wherein the one or more processors automatically configure the communication interface in response to detecting the request.
3. the one or more processors are further configured to respond to detecting that the set of initial network settings does not enable the communication channel by generating a notification provided at the user interface indicating that the set of initial network settings does not enable the communication channel; The skid communicator tool of claim 2 , wherein the notification is generated and provided before the one or more processors detect the request to enable the communication channel.
4. Transmitting or receiving the skid data over the communication channel receiving from the skid controller values read from the skid parameters; or 4. The skid communicator tool of claim 1, further comprising transmitting to the skid controller values to be written to skid parameters.
5. the skid data includes a skid configuration including one or more skid routines and one or more skid parameters; Transmitting or receiving the skid data over the communication channel (i) downloading the skid configuration from the skid controller; or The skid communicator tool of claim 1 , further comprising: (ii) uploading the skid configuration to the skid controller.
6. The skid communicator tool further includes a user interface coupled to the one or more processors, the one or more processors further comprising: displaying, via the user interface, a graphical user interface (GUI) for editing a skid configuration; receiving, via the GUI, a request to adjust values of the one or more routines or values of the one or more parameters in the skid configuration; updating the skid configuration in response to the request; The skid communicator tool of claim 5 , further configured to upload the updated skid configuration to the skid controller.
7. the one or more processors performing the analysis of the plurality of sets of pre-configured network settings; 7. The skid communicator tool of claim 1, configured to identify the particular set of pre-configured network settings by identifying the particular set of pre-configured network settings from the plurality of sets of pre-configured network settings based on the particular set of pre-configured network settings being correlated to a value of a skid ID of the skid controller.
8. 8. The skid communicator tool of claim 7, wherein the one or more processors are further configured to detect the value of the skid ID via the communications interface by sending a message to the skid controller requesting the value of the skid ID and receiving the value of the skid ID from the skid controller.
9. 9. The skid communicator tool of claim 7 or claim 8, wherein the one or more processors are configured to detect the value of the skid ID via a user interface coupled to the one or more processors by detecting a user input indicating the value of the skid ID at a user interface coupled to the one or more processors.
10. The particular set of pre-configured network settings: An Internet Protocol (IP) address; and A skid communicator tool as claimed in any preceding claim, further comprising: a subnet mask.
11. the one or more processors: storing the set of initial network settings in a memory prior to automatically configuring the communication interface according to the set of preconfigured network settings; 11. The skid communicator tool of claim 1, further configured to, after controlling, monitoring, or configuring operation of the skid, (i) receive, via a user interface coupled to the one or more processors, a request to restore previous network settings of the skid communicator tool, and (ii) in response to receiving the request to restore, automatically configure the communication interface according to the set of initial network settings stored in memory.
12. the skid is a first skid and the skid controller is a first skid controller; the particular set of pre-configured network settings is a first set among the plurality of sets of pre-configured network settings; The plurality of preconfigured sets of network settings include: (i) a second set of pre-configured network settings correlated to a second skid controller for a second skid; and (ii) a third set of pre-configured network settings correlated to a plant network of the process control environment.
13. the one or more processors: when the particular set of pre-configured network settings is not identified via the analysis, (i) displaying a prompt in a user interface requesting a user to provide network settings for the skid controller; (iii) receiving, via the user interface, a set of user-provided network configurations; and 13. The skid communicator tool of claim 1, further configured to generate the specific set of pre-configured network settings by: (iv) storing the user-provided network settings in a memory as the specific set of pre-configured network settings.
14. the one or more processors: when the particular set of pre-configured network settings is not identified via the analysis, (i) sending, via the communications interface, to the skid controller a request for a set of network configurations that match a set of whitelisted network configurations maintained by the skid controller; (ii) receiving a set of skid-provided network configurations via the communication interface; and 14. The skid communicator tool of claim 1, further configured to generate the specific set of pre-configured network settings by: (iii) storing the skid-provided network settings in a memory as the specific set of pre-configured network settings.
15. the one or more processors are further configured to transmit, to the skid controller, information that enables the skid controller to identify or authenticate the skid communicator tool; The skid communicator tool of claim 14 , wherein the skid controller is configured to transmit the skid-provided network configuration after identifying or authenticating the skid communicator tool based on the information.
16. 1. A method for quickly connecting to a skid controller and downloading a skid configuration, comprising: Detecting a link between a skid communicator tool and a skid controller for a skid in a process control environment by the skid communicator tool; detecting, by the skid communicator tool, that a set of initial network settings according to which the skid communicator tool is configured does not enable a communications channel between the skid communicator tool and the skid controller over the link; analyzing a plurality of pre-configured sets of network settings to identify a particular pre-configured set of network settings associated with the skid controller; Once the particular set of pre-configured network settings is identified via the analysis, (a) automatically configuring, by the skid communicator tool, the skid communicator tool according to the particular set of pre-configured network settings to enable the skid communicator tool to establish the communications channel over the link; (b) controlling, monitoring, or configuring operation of the skid by transmitting or receiving skid data over the communication channel.
17. detecting, by the skid communicator tool, a request to enable the communication channel; 17. The method of claim 16, wherein once the particular set of pre-configured network settings is identified, the automatically configuring occurs in response to the skid communicator tool detecting the request to enable the communication channel.
18. and responding to the detection that the set of initial network settings does not enable the communication channel by generating a notification provided at a user interface of the skid communicator tool indicating that the set of initial network settings does not enable the communication channel; The method of claim 17 , wherein the detected request to enable the communication channel is provided via the user interface in response to a prompt.
19. Transmitting or receiving the skid data over the communication channel receiving from the skid controller a value read from a skid parameter; A method according to any of claims 16 to 18, comprising sending to the skid controller values to be written into skid parameters.
20. the skid data includes a skid configuration including one or more skid routines and one or more skid parameters; Transmitting or receiving the skid data over the communication channel (i) downloading the skid configuration from the skid controller; 20. The method of claim 16, further comprising: (ii) uploading the skid configuration to the skid controller.
21. displaying, via the skid communicator tool, a graphical user interface (GUI) for editing a skid configuration; receiving a request via the skid communicator tool to adjust values of the one or more routines or values of the one or more parameters in the skid configuration; updating the skid configuration in response to the request; and 21. The method of claim 20, further comprising uploading the updated skid configuration to the skid controller.
22. Analyzing the plurality of sets of pre-configured network configurations to identify the particular set of pre-configured network configurations includes:
22. The method of claim 16, further comprising: identifying the particular set of pre-configured network settings from the plurality of sets of pre-configured network settings based on the set of pre-configured network settings being correlated to a value of a skid ID of the skid controller.
23. The particular set of pre-configured network settings: An Internet Protocol (IP) address; and Subnet mask and A method according to any of claims 16 to 22, comprising: a setting indicating that the IP address is static.
24. storing the set of initial network settings in a memory prior to automatically configuring the skid communicator tool according to the set of preconfigured network settings; 24. The method of claim 16, further comprising, after controlling, monitoring, or configuring operation of the skid, (i) receiving, via the skid communicator tool, a request to restore previous network settings of the skid communicator tool, and (ii) in response to receiving the request to restore, automatically configuring the skid communicator tool according to the set of initial network settings stored in memory.
25. the skid is a first skid and the skid controller is a first skid controller; the particular set of pre-configured network settings is a first set among the plurality of sets of pre-configured network settings; The plurality of preconfigured sets of network settings include: (i) a second set of pre-configured network settings correlated to a second skid controller for a second skid; and 25. The method of claim 16, further comprising: (ii) a third set of pre-configured network settings correlated to a plant network of the process control environment.
26. when the particular set of pre-configured network settings is not identified via the analysis, (i) displaying a prompt in the skid communicator tool requesting a user to provide network settings for the skid controller; (iii) receiving, via said skid communicator tool, a set of user-provided network configurations; and 26. The method of claim 16, further comprising: (iv) generating the specific set of pre-configured network settings by storing the user-provided network settings in a memory as the specific set of pre-configured network settings.
27. when the particular set of pre-configured network settings is not identified via the analysis, (i) sending, via the skid communicator tool, to the skid controller a request for a set of network configurations that match a set of whitelisted network configurations maintained by the skid controller; (ii) receiving, via said Skid Communicator Tool, a set of Skid-provided network configurations; and 27. The method of claim 16, further comprising: (iii) generating the specific set of pre-configured network settings by storing the skid-provided network settings in a memory as the specific set of pre-configured network settings.
28. transmitting to the skid controller information that enables the skid controller to identify or authenticate the skid communicator tool; 28. The method of claim 27, wherein the skid controller is configured to transmit the skid-provided network configuration only after identifying or authenticating the skid communicator tool based on the information.
Citation Information
Patent Citations
Process control system, configuration data base system, method for using configuration data in the same system, and method for performing configuration operation in the same system
JP2001184250A
Apparatus, method, and program for verification
JP2007243839A
Programmable controller system
JP2009223587A
Improved maintenance of wireless field equipment
JP2012527056A
Systems and methods for merging modular control systems into process plant
JP2018073419A
