Methods and apparatus for implementing widgets and web browser extensions to interact with a web server in a digital controller
By integrating web servers and browser extensions into field devices, fast and intuitive data access and configuration in industrial process control valve systems are achieved, solving the problem of complex interaction in existing technologies and improving operational efficiency and user experience.
Patent Information
- Application Number
- CN202610674784.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-16
- Filing Date
- 2026-05-15
- Publication Date
- 2026-11-17
AI Technical Summary
In existing industrial process control valve systems, the interaction between field devices and process control computers is complex, making it difficult to achieve fast and intuitive data access and configuration, resulting in low operational efficiency.
Integrating a web server into field devices provides real-time data monitoring and configuration functions through a browser-accessible interface. Combining with third-party browser extensions enhances storage and functionality, enabling intuitive user interaction.
It improved the operational efficiency of field equipment, enabled near real-time data access and configuration, reduced equipment downtime, and enhanced the user experience.
Smart Images

Figure CN123123322A_ABST
Abstract
Description
Related applications
[0001] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 807,383, filed May 16, 2025, entitled "DIGITAL FIELD DEVICECONTROLLERS WITH WEBSERVERS AND METHODS THEREOF". U.S. Provisional Patent Application No. 63 / 807,383 is incorporated herein by reference in its entirety. Priority is claimed from U.S. Provisional Patent Application No. 63 / 807,383. Technical Field
[0002] This disclosure generally relates to distributed control systems, and more specifically to methods and apparatus for implementing widgets and web browser extensions to interact with a web server in a digital controller. Background Technology
[0003] Control valves (e.g., sliding rod valves, rotary valves, axial flow valves, gate valves, etc.) are commonly used in industrial processes, such as oil and gas pipeline distribution systems and chemical processing plants, to control the flow of process fluids. These control valves are typically automated using actuators controlled by field devices (e.g., digital valve controllers). These field devices usually communicate with a process control computer to command changes in fluid flow within the valve, thereby achieving the desired control strategy. Summary of the Invention
[0004] An apparatus includes: an interface circuit; machine-readable instructions; and a programmable circuit programmed by the machine-readable instructions to perform the following operations: instantiate a web server at a field device in a control system; establish a connection between the web server and a client device; access data collected by the field device in response to a request from the client device; and cause the interface circuit to transmit data from the web server to the client device.
[0005] An exemplary machine-readable medium includes instructions for causing a programmable circuit to perform at least the following operations: instantiating a web server at a field device in a control system; establishing a connection between the web server and a client device; accessing data collected by the field device in response to a request from the client device; and causing data to be transmitted from the web server to the client device.
[0006] An exemplary method includes: instantiating a web server at a field device in a control system by executing instructions using programmable circuitry; establishing a connection between the web server and a client device; accessing data collected by the field device in response to a request from the client device; and transmitting the data from the web server to the client device by executing instructions using programmable circuitry. Attached Figure Description
[0007] Figure 1 This is an example environment in which an exemplary digital valve controller includes an exemplary web server and communicates with client devices.
[0008] Figure 2 It is a collection of multiple exemplary digital valve controllers that communicate with client devices. Figure 1 An exemplary environment.
[0009] Figure 3 yes Figure 1 A block diagram of an exemplary implementation of a digital valve controller.
[0010] Figure 4 It can be made by Figure 1 and Figure 3 A web server service in a digital valve controller provides an exemplary device overview graphical user interface (GUI) for configuring and / or displaying process variables.
[0011] Figure 5 It can be made by Figure 1 and Figure 3 A web server service in a digital valve controller provides an exemplary GUI for displaying trends of process variables.
[0012] Figure 6 It can be made by Figure 1 and Figure 3 The web server service in the digital valve controller provides an exemplary settings overview GUI for displaying and / or configuring device settings.
[0013] Figure 7 It can be made by Figure 1 and Figure 3 The web server service in the digital valve controller provides an exemplary communication settings GUI for displaying and / or configuring device communication settings.
[0014] Figure 8 It can be made by Figure 1 and Figure 3 The web server service in the digital valve controller provides an exemplary alarm settings GUI for displaying and / or configuring device alarm settings.
[0015] Figure 9 It can be made by Figure 1 and Figure 3 An example active alarm GUI is provided in the web server service of the digital valve controller to display active diagnostic alarms.
[0016] Figure 10 It can be made by Figure 1 and Figure 3 An exemplary video tutorial GUI for troubleshooting active diagnostic alarms using a web server service in a digital valve controller.
[0017] Figure 11 It can be made by Figure 1 and Figure 3 A web server service in a digital valve controller is used to display an exemplary valve feature overall scan GUI for diagnosing valve characteristics.
[0018] Figure 12 It can be made by Figure 1 and Figure 3 An example tuning GUI for performing tuning maintenance is provided by a web server service in a digital valve controller.
[0019] Figure 13 It can be made by Figure 1 and Figure 3 An example calibration pressure sensor GUI is provided in a web server service within a digital valve controller to perform calibration maintenance.
[0020] Figure 14 and Figure 15 It shows that it can be made by Figure 1 and Figure 3 An example camera view of the device GUI in a digital valve controller, which uses a web server service to perform connectivity maintenance.
[0021] Figure 16 It shows that it can be made by Figure 1 and Figure 3 An example camera view of a device's nearby GUI is provided by a web server service in a digital valve controller to offer visual indications of the conditions in the area near the digital valve controller.
[0022] Figure 17 This is a block diagram of an example system that enables client devices to access the web server of a digital valve controller and also extends access to large files from one or more web browsers.
[0023] Figure 18 It involves Figure 17 An exemplary operation sequence 1800 for the interaction between a client device and a digital valve controller.
[0024] Figure 19 and Figure 20This is a flowchart illustrating exemplary machine-readable instructions and / or exemplary operations that can be executed, instantiated, and / or implemented by exemplary programmable circuitry. Figures 1-3 Digital valve controllers and web servers.
[0025] Figure 21 This is a block diagram of an example processing platform including programmable circuitry configured to execute, instantiate, and / or perform example machine-readable instructions and / or perform... Figure 19 and Figure 20 Example operations to implement Figures 1-3 Digital valve controllers and web servers.
[0026] Figure 22 This is a block diagram of an exemplary software / firmware / instruction distribution platform (e.g., one or more servers) for distributing software, instructions, and / or firmware (e.g., corresponding to...). Figure 19 and Figure 20 The exemplary machine-readable instructions are distributed to client devices associated with end users and / or consumers (e.g., for licensing, selling and / or using), retailers (e.g., for selling, reselling, licensing and / or sublicensing), and / or original equipment manufacturers (OEMs) (e.g., for inclusion in products to be distributed to, for example, retailers and / or other end users such as direct purchase customers).
[0027] Generally, the same reference numerals will be used throughout the accompanying drawings and written description to refer to the same or similar parts. The drawings are not necessarily drawn to scale. Detailed Implementation
[0028] The examples disclosed herein can be used to implement digital field device controllers with integrated web servers and associated methods. As disclosed herein, the exemplary web server integrated into the field device controller is designed to display device-specific data through a streamlined, browser-accessible interface. The examples disclosed herein can be implemented using Ethernet with an advanced physical layer (Ethernet-APL) for monitoring, configuring, and interacting with the field device controller across process control systems. The examples disclosed herein provide an intuitive method for directly accessing diagnostic, configuration information, and substantially real-time data from the field device controller. The examples disclosed herein enhance the accessibility of the integrated web server, modernize the user experience, and accelerate field workflows. In the examples disclosed herein, the exemplary field device controller with an integrated web server is described as a digital valve controller (e.g., a valve positioner). However, the examples disclosed herein can be implemented in conjunction with any other type of field device controller (e.g., a flow meter, etc.).
[0029] Figure 1 The exemplary environment 100 includes an exemplary digital valve controller 102 that includes an integrated exemplary web server 104 and communicates with a client device 106. The digital valve controller 102 is operatively coupled to a fluid control valve 108 to configure, control, and monitor the operation of the fluid control valve 108. In some examples, the digital valve controller 102 is operatively coupled to a camera 110 (e.g., a webcam) positioned to have a view capturing the digital valve controller 102, the fluid control valve 108, and / or an area adjacent to (e.g., in the vicinity of) the digital valve controller 102. The digital valve controller 102 communicates with the client device 106 via an exemplary network 112 such as a local area network (LAN) or a wide area network (WAN) (e.g., the Internet). Although the examples disclosed herein are described in conjunction with the fluid control valve 108, the examples disclosed herein can be implemented with any other component of a process control system.
[0030] Web server 104 includes a built-in interface directly hosted on digital valve controller 102 and accessible via the Internet Protocol (IP) address of digital valve controller 102 through any standard Internet web browser and / or application. Web server 104 provides access to a range of capabilities associated with configuring, controlling, and monitoring digital valve controller 102 and fluid control valve 108. Examples of such capabilities include substantially real-time diagnostics (e.g., valve signature, step test results, equipment alarms and warnings), configuration tools (e.g., adjustment of equipment-specific settings, communication parameters, and alarm thresholds), live data visualization (e.g., substantially real-time insights into stroke, supply pressure, setpoint input, output pressure, and stroke deviation), and secure remote access (e.g., access from within the plant's control network—eliminating the need for a handheld or local user interface within short wireless communication proximity). An exemplary GUI served by web server 104 is provided in... Figures 4-16 As shown in, and including Figure 4 and Figure 5 Example process variable GUI in Figures 6-8 The exemplary device settings GUI in the example Figures 9-11 Exemplary diagnostic GUI and Figures 12-16 An example maintenance GUI is shown in the example.
[0031] In the examples disclosed herein, client device 106 can remotely access web server 104 via network 112, allowing users to access status information and interact with digital valve controller 102 from a convenient and / or secure location, regardless of where digital valve controller 102 is located within the process control system. Client device 106 is shown as an exemplary laptop / personal computer and mobile communication device (e.g., smartphone, tablet computing device, etc.). However, client device 106 may include any other suitable type and / or any other number of devices having an application or web browser for accessing web server 104.
[0032] Figure 2 It includes multiple exemplary digital valve controllers 202a-c that communicate with client device 106. Figure 1 Exemplary environment 100. Digital valve controller 202a-c with Figure 1 The digital valve controller 102 is basically similar to or the same as that of the others. Figure 2 In the examples, each of the digital valve controllers 202a-c includes a... Figure 1 Web servers 104 and 204a-c are substantially similar to or identical to web servers 204a-c, and each web server 204a-c is assigned a unique IP address. For example, web server 204a of digital valve controller 202a is assigned IP address 192.168.0.1, web server 204b of digital valve controller 202b is assigned IP address 192.168.0.2, and web server 204c of digital valve controller 202c is assigned IP address 192.168.0.3. Client device 106 can access a specific one of digital valve controller 202a-c and web server 204a-c based on its corresponding IP address. Web server 204a-c is configured to simultaneously provide substantially real-time diagnostic data and configuration control to multiple client devices in client device 106, and allows multiple users to interact with and change the configuration via their corresponding client devices in client device 106.
[0033] Figure 3 It is used for configuration, control and monitoring Figure 1 The digital valve controller 102 and the fluid control valve 108 Figure 1 A block diagram of an exemplary embodiment of the digital valve controller 102. Figure 3The digital valve controller 102 can be instantiated by a programmable circuit (e.g., creating an instance of it, making it exist for any length of time, materializing it, implementing it, etc.). For example, the programmable circuit can be implemented by a central processing unit (CPU) that executes the first instruction, a field-programmable gate array (FPGA), a programmable logic device (PLD), a general-purpose array logic (GAL) device, a programmable array logic (PAL) device, a complex programmable logic device (CPLD), a simple programmable logic device (SPLD), a microcontroller (MCU), a programmable system-on-a-chip (PSoC), etc. Additionally or alternatively, Figure 3 The digital valve controller 102 can be instantiated (e.g., instantiated, made to exist for any length of time, materialized, implemented, etc.) by (i) an application-specific integrated circuit (ASIC) and / or (ii) a field-programmable gate array (FPGA) (e.g., another form of programmable circuit) constructed and / or configured to perform the operation of the digital valve controller 102. It should be understood that... Figure 3 Some or all of the circuits can be instantiated at the same or different times. Figure 3 Some or all of the circuitry can be instantiated, for example, in one or more threads that execute concurrently on hardware and / or serially on hardware. Furthermore, in some examples, Figure 2 Some or all of the circuitry can be implemented by microprocessor circuitry that executes instructions and / or FPGA circuitry that performs operations to implement one or more virtual machines and / or containers.
[0034] The digital valve controller 102 includes an exemplary interface circuitry 302, an exemplary programmable circuitry 304, an exemplary memory system 306, and an exemplary graphical user interface (GUI) 308. The interface circuitry 302 is provided to enable the web server 104 to receive and send communications via network 112. The programmable circuitry 304 is provided to instantiate the web server 104. The memory system 306 is provided to store machine-readable instructions for implementing the web server 104, and to store substantially real-time diagnostic data, configuration tools, configuration data, and live data. The memory system 306 may include any suitable type of volatile memory (e.g., random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), flash memory, etc.), and / or storage devices (e.g., one or more solid-state drives (SSDs), one or more magnetic hard disk drives (HDDs), optical disc drives, etc.). The GUI 308 provides different screens for the web server 104 to display substantially real-time diagnostic data, configuration tools, configuration data, and live data for user access via client device 106.
[0035] In some examples, the programmable circuit 304 is programmed with machine-readable instructions to perform operations to achieve the following combination Figures 4-16 The characteristics described.
[0036] As mentioned above, Figure 3 The interface circuit system 302, programmable circuit system 304, memory system 306, and GUI 308 are structures. Such structures can implement means for performing the corresponding disclosed functions. Examples of such functions have been described above in conjunction with their counterparts in interface circuit 302, programmable circuit 304, memory system 306, and GUI 308, and examples of such functions are described below in conjunction with... Figures 4-16 Examples of this type of functionality are described.
[0037] Although Figure 3 The implementation is shown in the figure. Figure 1 The example of the digital valve controller 102, but Figure 3 One or more of the elements, processes, and / or devices shown may be combined, divided, rearranged, omitted, eliminated, and / or implemented in any other way. Furthermore, interface circuitry 302, programmable circuitry 304, memory system 306, and GUI 308, and / or more generally, Figure 3 The exemplary digital valve controller 102 can be implemented solely by hardware or by a combination of hardware and software and / or firmware. Therefore, for example, any of the interface circuitry 302, programmable circuitry 304, memory system 306, and GUI 308, and / or more generally, the exemplary digital valve controller 102 can be implemented by programmable circuitry, processor circuitry, analog circuitry, digital circuitry, logic circuitry, programmable processors, programmable microcontrollers, graphics processing units (GPUs), digital signal processors (DSPs), ASICs, programmable logic devices (PLDs), vision processing units (VPUs), and / or field-programmable logic devices (FPLDs) (e.g., FPGAs) combined with machine-readable instructions (e.g., firmware or software). Furthermore, Figure 3 An exemplary digital valve controller 102 may include, in addition to Figure 3 Those other than or in place of those shown Figure 3 One or more of the elements, processes and / or devices shown, and / or may include more than one of any or all of the elements, processes and devices shown.
[0038] Figure 4 It can be made by Figure 1 and Figure 3The web server 104 in the digital valve controller 102 serves an exemplary device overview GUI 400 for configuring and / or displaying process variables. The device overview GUI 400 includes an example device status area 402, which includes an exemplary device status indicator 404 and an exemplary mode control element 406. The device status indicator 404 allows the user to monitor the status of the digital valve controller 102 and the corresponding fluid control valve 108. The exemplary mode control element 406 indicates the current operating mode of the digital valve controller 102 and allows the user to switch between automatic and manual modes.
[0039] The device overview GUI 400 includes various process variable widgets to show substantially real-time updates of the process variables of the digital valve controller 102 and / or the corresponding fluid control valve 108. The widgets can display the process variables in different formats, such as graphs, lists, etc. The device overview GUI 400 includes an exemplary setpoint and stroke widget 408, which displays a configured stroke setpoint relative to the actual stroke of the plunger of the fluid control valve 108. As used herein, the plunger is an internal component of the fluid control valve that travels toward the closed position to reduce fluid flow through the fluid control valve by decreasing the size of the valve's opening. The plunger also travels in the opposite direction toward the open position to increase fluid flow through the fluid control valve by increasing the size of the valve's opening.
[0040] The device overview GUI 400 includes an exemplary pressure widget 410 that displays pressure measurements associated with controller inputs and outputs, such as the input supply pressure and output pressure of ports A and B. The device overview GUI 400 includes an exemplary stroke widget 412 that shows the actual stroke of the plunger of the fluid control valve 108. The device overview GUI 400 includes an exemplary setpoint widget 414 that shows the configured stroke setpoint, stroke distance, and device signals associated with the plunger operating the fluid control valve 108. The device overview GUI 400 includes an exemplary temperature widget 416 that shows temperature measurements associated with the digital valve controller 102.
[0041] Pressure widget 410 and temperature widget 416 allow for customization of pressure and temperature units to suit individual preferences. Temperature widget 416 enables users to set upper and lower operating limits. The performance (e.g., appearance) of temperature widget 416 changes depending on whether the measured temperature variable is within or outside the upper and lower operating limits, thus providing clear visual cues for user analysis.
[0042] Known digital valve controllers and / or other process control products operate based on Device Descriptor (DD) technology, which typically requires users to navigate through several pages to potentially change thresholds (e.g., temperature limits). Unlike such known devices, the Device Overview GUI 400 concurrently (e.g., simultaneously) displays widgets 408, 410, 412, 414, and 416 to provide intuitive “one-click” navigation that allows users to change different configuration parameters (e.g., limits to ranges such as temperature). For example, after a user clicks on the temperature widget 416, the Device Overview GUI 400 generates (e.g., pops up) an edit threshold window 418 that allows the user to change the temperature threshold without requiring the user to navigate out of the Device Overview GUI 400.
[0043] In some implementations, the digital valve controller 102 may have limited memory space (e.g., Figure 3 The memory system 306 has a capacity to store machine-readable instructions implementing widgets 408, 410, 412, 414, and 416 or other widgets and / or web features. To overcome this limited memory capacity, the web server 104 is configured to communicate with a third-party web browser extension, which may be developed by a third party to provide additional storage of features in a web browser connected to the web server 104. The third-party web browser extension may be customized by the end-user company. Such a third-party web browser extension can be used to enhance the user experience by adding additional features specific to different end-users. Examples of such third-party web browser extensions include communication gateway extensions and firmware update extensions. Communication gateway extensions can be provided to offer different network configurations for communicating with the web server 104. In some examples, communication gateway web browser extensions (e.g., ValveLink Pro communication gateways) can configure the client device 106 as an end-user-specific gateway without requiring a separately configured and dedicated gateway. Firmware update extensions can be provided to update the firmware in the digital valve controller 102 according to the needs of different end-users.
[0044] Other examples of such third-party web browser extensions that can be developed include allowing data to be processed, visualized, filtered, stored, etc., in a way specific to the end user. Some third-party web browser extensions can be developed to store video tutorials, high-resolution images, user manuals, and / or any other type of information on the client device 106 that might not be stored on the digital valve controller 102 due to memory limitations. That is, one purpose of the web extension is to enable access to data for which the memory of the digital valve controller 102 (e.g., memory system 306) is insufficient to store such data. In some examples, the web server 104 of the digital valve controller 102 provides and / or includes instructions for the availability of web browser extensions. For example, in Figure 4 In the example shown, the device overview GUI 400 includes an exemplary web extension widget 420 that lists available web browser extensions. In some examples, the list includes hyperlinks for activating and / or opening web browser extensions on client device 106. Alternatively, in some instances, the list contains hyperlinks to websites where the web browser extension can be downloaded by client device 106 (e.g., if it has not already been downloaded).
[0045] Figure 5 It can be made by Figure 1 and Figure 3 A web server 104 in the digital valve controller 102 serves an exemplary trend GUI 500 to display process variables. The trend GUI 500 includes an exemplary graphical area 502 to trend variables (e.g., stroke, supply pressure, setpoint, pressure A, pressure B, etc.) and calculations (e.g., setpoint in, stroke deviation, etc.) from the digital valve controller 102 and / or fluid control valve 108 substantially in real time. As mentioned above, the digital valve controller 102 typically has relatively limited memory. However, in some examples, the memory is sufficient to store trend variables and / or calculation results for a recent period (e.g., the last day, the last week, the last two weeks, the last month, etc.) to generate trends. In some such examples, if a user is interested in accessing variables and / or calculation results at a point in time beyond the scrolling window, for which data is stored on the digital valve controller 102, the user may need to access a historical archive stored remotely from the controller 102.
[0046] like Figure 5As shown in the example, the graphical area 502 can display data from a direct measurement channel that provides direct measured values corresponding to the digital valve controller and / or fluid control valve 108. This direct measurement data can be provided by sensors of the digital valve controller 102 and / or fluid control valve 108. The graphical area 502 can also display calculated data from a computational channel, which is obtained by performing one or more mathematical processes or other data modifications on the data obtained from the direct measurement channel. For example, a calculated current channel can be displayed to show the current value calculated based on the directly measured voltage level and static resistance value.
[0047] The Trend GUI 500 includes an exemplary setpoint configuration area 504 for substantially real-time control of the setpoint (e.g., commanding the valve position of fluid control valve 108) via button controls (e.g., -25, 0, 50, 100, 125) or slider controls. The Trend GUI 500 includes an exemplary auto-calibration button control 506 for instantiating the execution of auto-calibration of the digital valve controller. The Trend GUI 500 also includes an exemplary step test button 508 for configuring and / or running different step tests. In some examples, data associated with the auto-calibration process and / or step test is presented substantially in real-time in the graphics area 502 as the corresponding procedure completes. Providing substantially real-time data associated with calibration and / or step test operations was previously impossible due to the known speed at which digital controllers report data. Specifically, many known digital controllers report data at a signaling rate of 1200 baud. Therefore, in the past, when users needed to perform calibration procedures or step tests, they had to initiate the process and wait for it to run (which could take more than 20 minutes for relatively large valves), and then wait several additional minutes (up to 15 minutes) for the data associated with the operation to be transmitted over time before the results were presented to them. This meant that users could potentially wait more than half an hour before knowing whether the operation had proceeded as expected or whether any problems had occurred. In the example disclosed herein, data associated with valve operations (e.g., calibration procedures, step tests, etc.) are provided essentially in real time. Therefore, users can quickly confirm that the operation is proceeding as expected and / or identify any errors that have occurred during the operation for immediate response, saving significant time.
[0048] Figure 6 It can be made by Figure 1 and Figure 3The web server 104 in the digital valve controller 102 serves an exemplary settings overview GUI 600 to display and / or configure device settings. The settings overview GUI 600 can be used to receive user configuration of the stroke control type of the plunger of the fluid control valve 108, and to configure the plunger's cut-off and stroke limits.
[0049] Figure 7 It can be made by Figure 1 and Figure 3 The web server 104 in the digital valve controller 102 provides an exemplary communication settings GUI 700 for displaying and / or configuring device communication settings. The communication settings GUI 700 is provided to allow users to configure settings for communication protocols such as Modbus Transmission Control Protocol (ModbusTCP), IPv4 / IPv6, etc.
[0050] Figure 8 It can be made by Figure 1 and Figure 3 The web server 104 in the digital valve controller 102 provides an exemplary alarm settings GUI 800 for displaying and / or configuring device alarm settings. The alarm settings GUI 800 includes an exemplary drive signal alarm configuration area 802, an exemplary IP drive current alarm configuration area 804, and an example electronic component defect alarm configuration area 806. Alarm configuration areas for other categories of alarms may be additionally or alternatively provided in the alarm settings GUI 800. In some examples, NE107 category alarms may be configured in the alarm settings GUI 800. Thus, the alarm settings GUI 800 allows the user to configure different types of alarms in the digital valve controller 102. In the examples disclosed herein, an NE107 alarm refers to a notification category defined by the NAMUR user group as an NE107 alarm. An NE107 alarm indicates whether the device is in good condition, has malfunctioned, requires maintenance, or is out of service.
[0051] In some examples, the alarm setting GUI 800 allows simulation of alarm active and inactive states, enabling users to verify that alarm configurations have been correctly set. Due to the way existing systems are implemented (based on DD technology), alarm simulation on existing systems overrides actual / real alarm bits on devices (e.g., digital valve controllers). Any integration from the host (e.g., the digital valve controller) for the actual alarm bits is affected. Therefore, existing systems cannot easily determine which alarms are simulated and which are real when the user operates in simulation mode. Furthermore, alarm simulation in existing systems overrides real alarms. In some existing systems, such as HART devices communicating using the HART bus protocol, simulation cannot be performed when write protection is enabled on such HART devices. For example, in some devices, an automatic operation mode is set to enable write protection for those devices. Therefore, when write protection is enabled on a device, hardware alarm bits cannot be set in the device hardware. Unlike such known systems, the examples disclosed herein allow alarm simulation by providing a simulation mode in web server 104. In emulation mode, a web browser interacting with web server 104 receives user input to set emulation alarm bits in the web browser environment, rather than in the hardware bits of the actual digital valve controller 102. Therefore, alarms are only overridden within web server 104. Any integrations from web server 104 will be applied (e.g., displaying active alarms in a list, showing recommended actions, etc.). Digital valve controller 102 does not see changes in emulation alarm bits and therefore does not act on emulation alarms. However, if a real alarm is activated and acts accordingly during emulation, web server 104 will see changes in the hardware alarm bits in digital valve controller 102. Thus, the user can distinguish between emulation and real alarms. This allows the user to run alarm emulation while digital valve controller 102 is in write-protected mode. In some examples, when digital valve controller 102 detects a real alarm while the user is in emulation mode, a notification is provided via web server 104 to draw the user's attention to the real alarm. In some examples, the notification includes a pop-up window on top of the alarm setting GUI 800, which displays emulation alarm data in other ways. In some examples, the alarm settings GUI 800 is modified in other ways to draw the user's attention to real alarms. For example, the alarm settings GUI 800 may be frozen and / or grayed out, except in the notification area that identifies real alarms. In some examples, depending on the type and / or severity of the real alarm, the digital valve controller 102 may automatically terminate the user's emulation mode session and switch the user back to standard (real alarm) mode, enabling the user to view and respond to real alarms.
[0052] In some examples, there is some hardware integration. For example, alarm emulation can be bound to the NE107 state, allowing the physical LEDs on the digital valve controller 102 (e.g., Figure 14 The hardware LED 1404 changes color during simulation.
[0053] Figure 9 This is an exemplary activity alert GUI 900 for displaying activity diagnostic alerts, and Figure 10 This is an example video tutorial GUI 1000 for troubleshooting activity diagnostic alarms. The Activity Alarms GUI 900 and the Video Tutorial GUI 1000 can be provided by... Figure 1 and Figure 3 The web server 104 in the digital valve controller 102 provides services. The activity alarm GUI 900 includes an exemplary alarm message 902. Alarm message 902 displays activity alarms categorized by status and indicated by color. In the example shown, alarm message 902 corresponds to a stroke deviation and provides a description of valve stroke not tracking the setpoint. Alarm message 902 also provides a recommended action. Figure 9 and Figure 10 Exemplary recommended actions include checking valve friction, supplying air, and air leaks. An exemplary virtual LED bullet indicator 904 is matched with a hardware LED status indicator on the digital valve controller 102, allowing a user to view the status of the hardware LEDs via a web browser through the web server 104. For example, the virtual LED bullet indicator 904 could reflect the NE107 status of the digital valve controller 102 or any other type of status.
[0054] Users can click on alert message 902 to view more information, such as Figure 10 As shown. Figure 10 The video tutorial GUI 1000 displays a user-selectable video tutorial link 1002. When the video tutorial GUI 1000 receives a user selection of the video tutorial link 1002, the web server 104 provides an exemplary tutorial video 1004, which is displayed as an embedded video by the video tutorial GUI 1000. Therefore, the user can view the tutorial video 1004 to troubleshoot the digital valve controller 102 and / or the fluid control valve 108.
[0055] The examples disclosed herein allow a video tutorial GUI 1000 to display tutorial videos even when the internet connection for retrieving such videos from an internet-connected media server is unavailable. For example, client device 106 may be connected to web server 104 via a LAN, but may lack internet access (e.g., in an air-gap isolated environment). To overcome this, the examples disclosed herein can be used to store the video locally on digital valve controller 102 (e.g., in memory system 306), allowing web server 104 to deliver the video from digital valve controller 102 to the web browser of client device 106 via a LAN. In such an example, the video can be loaded into digital valve controller 102 when it is connected to the internet and is able to download the video from an internet-connected media server before the user requests to view it. As mentioned above, in some cases, digital valve controller 102 may not have sufficient storage for the video. Therefore, the examples disclosed herein can be additionally or alternatively implemented to store the video at client device 106 in a web browser extension on client device 106, so that the web browser of client device 106 can load the video for the user even when client device 106 is offline from the internet. In such an example, when client device 106 is connected to the internet and is able to download the video from an internet-connected media server before the user requests to view the video, the video can be loaded into a web browser extension. In some examples, the web browser extension can be configured to interact with licensing features associated with installing the browser extension and / or accessing licensed video content from an internet-connected media server.
[0056] Video tutorials are provided in the video tutorial GUI 1000 (e.g., Figure 10 The tutorial video 1004 allows users to easily understand the alarm codes signaled by the virtual LED bullet point indicator 904 and how to resolve them (e.g., how to fix the problem). Directly linking the alarm codes signaled by the virtual LED bullet point indicator 904 with relevant information in the active alarm GUI 900 and the video tutorial GUI 1000 significantly reduces equipment downtime by reducing the amount of research required from the user to resolve equipment problems.
[0057] In some examples, licenses for different diagnostic features, configuration features, maintenance features, etc., may be stored in the digital valve controller 102 (e.g., in the memory system 306) and / or on one or more web browser extensions on the client device 106, so that the client device 106 can access such licensed features when an internet connection is unavailable to communicate with the license server. In such examples, when a user requests access to a licensed feature, the web browser extension may generate the corresponding license and / or request the corresponding license from the digital valve controller 102, thereby granting the user access to the licensed feature.
[0058] Figure 11 It can be made by Figure 1 and Figure 3 A web server 104 in a digital valve controller 102 serves an exemplary valve feature overall scan GUI 1100 to display diagnostic valve features. As used herein, a valve feature represents the correlation between the spring force and diameter pressure of a fluid control valve (e.g., fluid control valve 108). Therefore, a valve feature is a unique characteristic of the valve's response relative to the valve's spring force input. The valve feature overall scan GUI 1100 includes an example-type feature graph area 1102 that displays the valve features of the fluid control valve 108. The feature graph area 1102 allows the user to configure and run the valve features and view live-updated data. The examples disclosed herein allow the feature graph area 1102 to show the progress of diagnostics as live-stream data (e.g., substantially in real-time) without missing points. For example, to avoid missing diagnostic points, the feature graph area 1102 displays the progress with live-stream data and simultaneously stores the live valve feature data as a whole to a file (e.g., a diagnostic file). In such an example, even if some data points are omitted from the displayed live stream data in feature map region 1102 (e.g., the live stream data is downsampled relative to the complete data stored in the diagnostic file), these omitted data points are still saved in the diagnostic file. Therefore, subsequent analysis can be used to run diagnostics on the entire valve feature data in the file.
[0059] By displaying updated live valve characteristic data, users can see, almost in real time, whether there are any undesirable response characteristics of a particular valve. For example, oscillating behavior represented in the live valve characteristic data may be undesirable. When a user identifies such an undesirable condition almost in real time, they can immediately stop valve operation and resolve any issues that may be causing this undesirable behavior. Compared to existing systems that cannot provide real-time data, this reduces troubleshooting and / or the time required for online valve configuration and maintenance, because of the combination of the above... Figure 5 The discussion essentially involves real-time display of the calibration process and / or step test overview, but the communication speed is limited.
[0060] Figure 12 It can be made by Figure 1 and Figure 3 The web server 104 in the digital valve controller 102 serves an exemplary regulation GUI 1200 to perform regulation maintenance. The regulation GUI 1200 includes an exemplary stroke regulation configuration control 1202, which provides the ability to update the stroke regulation set in the digital valve controller 102 for operating the fluid control valve 108.
[0061] Figure 13 It can be made by Figure 1 and Figure 3 The web server 104 in the digital valve controller 102 serves an exemplary calibration pressure sensor GUI 1300 to perform calibration maintenance. The calibration pressure sensor GUI 1300 provides the ability to set the pressure sensor calibration count corresponding to the pressure sensor of the fluid control valve 108.
[0062] Figure 14 and Figure 15 It shows that it can be made by Figure 1 and Figure 3 The web server 104 in the digital valve controller 102 serves an exemplary camera view of the device GUI 1400 to perform connectivity maintenance. The camera view of the device GUI 1400 includes an exemplary live video stream area 1402, which presents a camera pointing towards the front of the digital valve controller 102 (e.g., ...). Figure 1 Live video stream from camera 110. Figure 14 and Figure 15 In the example, the front of the digital valve controller 102 includes an exemplary hardware LED 1404 that can be remotely monitored via a live video stream area 1402. The camera view of the device GUI 1400 also includes an exemplary virtual LED 1406 that reflects the same color state emitted by the hardware LED 1404. For example, based on different colors, the hardware LED 1404 and the virtual LED 1406 can represent the NE107 state or any other type of state. When the color state on the hardware LED 1404 changes, the virtual LED 1406 is updated to show the same color. For example, based on… Figure 14 The "good" device status indicated by the image shows hardware LED 1404 and virtual LED 1406. Figure 14 The middle can be all green. Alternatively, in Figure 15 In the example, based on Figure 15The "out of specification" device status indicated in the diagram can be indicated by both hardware LED 1404 and virtual LED 1406 being yellow. Users can use the camera view of the device GUI 1400 to verify that the web server 104 and digital valve controller 102 are correctly synchronized. If they are not correctly synchronized, users can perform connectivity maintenance to reconnect and / or resynchronize the web server 104 and digital valve controller 102.
[0063] In some examples, live streams of views from other cameras near the digital valve controller 102 may be additionally or alternatively provided via a web server 104 of the digital valve controller 102. For example, Figure 16 It shows that it can be made by Figure 1 and Figure 3An exemplary camera view of the device proximity GUI 1600, served by web server 104 in the digital valve controller 102. The camera view of the device proximity GUI 1600 includes an exemplary live video stream area 1602, which presents a live video stream captured by camera 110 near the digital valve controller 102. In some examples, camera 110 may be focused on the fluid control valve 108 to which the digital valve controller 102 is attached. In some examples, camera 110 captures a close-up view of the fluid control valve 108, which, depending on the viewing angle, may partially or completely omit the digital valve controller 102. In the illustrated example, camera 110 is positioned to capture a larger proximity area including the digital valve controller 102, the fluid control valve 108, and a proximity area 1604. In this example, the proximity area 1604 corresponds to a person's workspace and / or walkway. Therefore, the camera view of the device proximity GUI 1600 allows the user to identify whether there is a person near the digital valve controller 102 and the associated fluid control valve 108. In other examples, the camera view may be positioned to capture other conditions and / or areas near the digital valve controller 102. For example, a live camera feed may allow a remote user to visually inspect for abnormal conditions of the equipment and / or environment without immediate on-site access. In some examples, a live camera feed may allow a remote user to assess the environment and / or safety conditions near the equipment and / or prepare such personnel to handle these conditions before dispatching personnel (e.g., video feed may reveal hazardous conditions such as fluid or gas leaks, spills of chemicals or oil, excessive vibrations that cause camera shake, or other unsafe operating conditions). In some examples, a live camera feed may allow a remote user to monitor other personnel near the equipment and / or collaborate with them via a user interface (e.g., providing guidance, feedback, and / or verification of processes performed by them). In some examples, camera 110 is adjacent to (e.g., mounted on) the digital valve controller 102 and oriented with its face away from the digital valve controller 102. In such an example, the live video stream region 1602 depicts the adjacent region (e.g., region 1604) without showing the digital valve controller 102 or the fluid control valve 108.
[0064] Figure 17This is a block diagram of an exemplary system 1700 that enables client device 106 to access web server 104 of digital valve controller 102 and also to access large files from one or more web browser extensions 1702. In this example, web browser extension 1702 is downloaded via Internet 1704 using browser 1705 on client device 106. In some cases, client device 106 may not be able to access Internet 1704 when it connects to digital valve controller 102. Therefore, in some examples, client device 106 needs to download extension 1702 beforehand in order to access information and / or files provided by web browser extension 1702 when connected to digital valve controller 102. As mentioned above, an important reason for web browser extension 1702 is to enable client device 106 to access the local file system 1706 associated with digital valve controller 102 (e.g., ...). Figure 3 The limited memory capacity of the digital valve controller 102 (306) prevents the local storage of relatively large files, applications, tools, and / or information (e.g., videos, high-resolution images, manuals, diagnostic tools, etc.). In the disclosed examples, such large files and / or applications are stored in the memory of the client device 106. In some examples, files, applications, tools, and / or information are included in the web browser extension 1702, even if they could be stored locally by the digital valve controller 102. That is, file size is not the only reason for using the web browser extension 1702. For example, in some examples, new diagnostic tools may be developed that are not included in the firmware of the digital valve controller 102 due to their later development. In some such examples, the new diagnostic tools can be implemented directly on the client device 106 (via the web browser extension 1702) without having to be executed on the digital valve controller 102. Additionally or alternatively, in some examples, the digital valve controller 102 can be updated to include new diagnostic tools by installing new tools obtained from the client device 106 via the web browser extension 1702. More generally, in some examples, the web browser extension 1702 may include firmware update files for the digital valve controller 102 (whether or not the update includes new diagnostic tools), which may be provided to the digital valve controller 102 by the client device 106 for updating.
[0065] exist Figure 17In the example shown, client device 106 connects to the digital valve controller via a local Advanced Physical Layer (APL) 1708 (e.g., Ethernet APL). In some examples, client device 106 uses a browser 1705 to access information on the digital valve controller 102 to connect to the web server 104. However, when the corresponding web browser extension 1702 is downloaded, large files can be stored directly on client device 106, while smaller files, applications, and / or information (e.g., configuration files, logs, small images, live data, etc.) are provided directly by the digital valve controller 102 via the web server 104.
[0066] Figure 18 It involves Figure 17 An exemplary sequence of operations 1800 for interaction between client device 106 and digital valve controller 102. At a first time point 1802, a web browser extension 1702 is downloaded and installed on client device 106. At the next time point 1804, the user uses a browser 1705 on the client device to request a homepage (or any other web page) from web server 104 of digital valve controller 102. At the next time point 1806, web server 104 of digital valve controller 102 retrieves data from the digital valve controller's database (e.g., ...). Figure 3 The memory system 306 and / or Figure 17 At time 1706, the local file system 104 requests homepage data. At the next time point 1808, the database returns the homepage data. At the next time point 1810, the web server 104 serves the homepage to the client device 106 (e.g., for rendering via a browser 1705).
[0067] In some examples, the homepage corresponds to Figure 4 An exemplary device overview GUI 400 is provided. Other web pages and / or GUIs may be provided in addition to or in place of the device overview GUI 400. In some examples, different pages and / or content are provided based on additional requests from the user via client device 106. In some examples, such requests are provided by the user selecting one of widgets 408, 410, 412, 414, 416 included in the device overview GUI 400. In some examples, the user indicates a request for additional information and / or a different page by selecting from available menu options provided on the current page (e.g., the device overview GUI 400).
[0068] As a specific example, in Figure 18At another time point 1812 in the operation sequence 1800, the user submits a request for device configuration data. In some examples, the user may not directly request configuration data, but instead select a web page configured to provide configuration data. At the next time point 1814, the web server 104 of the digital valve controller 102 requests configuration data (and / or the associated web page) from the database of the digital valve controller 102. At the next time point 1816, the database returns the requested data. At the next time point 1818, the web server 104 provides the configuration data to the client device 106 (e.g., for rendering via a browser 1705).
[0069] Additionally or alternatively, at another time point 1820, the user submits a request for live data. In some examples, the user may not directly request live data, but instead select a web page configured to provide live data. At the next time point 1822, the web server 104 of the digital valve controller 102 requests live data (and / or the associated web page) from the digital valve controller's database. At the next time point 1824, the database returns the requested data. At the next time point 1826, the web server 104 provides the requested data to the client device 106 (e.g., for rendering via a browser 1705).
[0070] In some examples, at another time point 1828, the user submits a request for an activity alert. In some examples, the user may not directly request an activity alert, but instead choose a web page configured to provide such data. At the next time point 1830, the web server 104 of the digital valve controller 102 requests the activity alert (and / or the associated web page) from the digital valve controller's database. At the next time point 1832, the database returns the requested data. At the next time point 1834, the web server 104 provides the requested data to the client device 106 (e.g., for rendering via a browser 1705).
[0071] like Figure 18As illustrated in the example, the web server 104 of the digital valve controller 102 can provide a homepage, configuration data, live data, and activity alerts based on information locally stored in the digital valve controller 102 (e.g., in a database). In some examples, other information of interest to the user may not be available on the digital valve controller 102. In some such examples, this information can be provided via a web browser extension 1702 previously installed on the client device 106 at a first time point 1802. For example, in this example, a request for an activity alert returns a trip deviation alert. In this example, the user wants to know more about the trip deviation alert. Therefore, the user request is directed to a trip deviation alert help video available on a web page served by the web server 104 of the digital valve controller 102. In this example, at the next time point 1836, the request is passed to the web browser extension 1702 stored on the client device 106. At the next time point 1838, the requested video is queried from the web browser's database (e.g., associated with the memory of the client device 106). At the next time point 1840, the requested video is returned. At the next time point 1842, the requested video is provided to be rendered on client device 106. In some examples, if the video is not already cached on client device 106 (e.g., a web browser extension is not pre-installed) and the client device is currently connected to the Internet, client device 106 can directly access and view the video via the Internet.
[0072] Additionally or alternatively, in some examples, at a different time point 1844, the user can request the latest user manual from the digital valve controller 102. This request is passed to the web browser extension 1702 on the client device 106. At the next time point 1846, the web browser extension 1702 requests the latest user manual from the web browser database. At the next time point 1848, the requested manual is returned. At the next time point 1850, the user manual is provided for presentation on the client device 106. In some examples, if the user manual is not already cached on the client device 106 (e.g., the web browser extension is not pre-installed) and the client device is currently connected to the Internet, the client device 106 can download the user manual and / or view it online via the Internet.
[0073] In some examples, data associated with the web browser extension 1702 downloaded to client device 106 may be provided (e.g., uploaded) to digital valve controller 102. For example, at a specific time point 1852, the user submits a request for the latest firmware release delivered to the web browser extension 1702 on the client device. At the next time point 1854, the web browser extension 1702 requests the latest firmware release from the web browser database. At the next time point 1856, the firmware release is returned. At the next time point 1858, the firmware release is provided to client device 106. Furthermore, at the next time point 1860, the firmware release is then provided to digital valve controller 102 so that digital valve controller 102 can be updated. In some examples, if the firmware release has not yet been cached on client device 106 (e.g., the web browser extension has not been pre-installed) and the client device is currently connected to the Internet, client device 106 may download the firmware release via the Internet and then deliver it to digital valve controller 102.
[0074] exist Figure 19 and Figure 20 The diagram illustrates how this can be implemented and / or instantiated by programmable circuitry. Figure 1 and Figure 3 Exemplary machine-readable instructions and / or representations of the digital valve controller 102 and web server 104 can be executed by programmable circuitry to implement and / or instantiate them. Figure 1 and Figure 3 A flowchart illustrating the exemplary operation of the digital valve controller 102 and the web server 104 is provided. Machine-readable instructions may be used by programmable circuits (such as those combined below). Figure 21 The programmable circuitry 2112 shown in the exemplary processor platform 2100 discussed herein executes one or more executable programs or portions of one or more executable programs, and / or may be one or more functions or portions of functions to be executed by other types of programmable circuitry (e.g., FPGA). In some examples, machine-readable instructions cause operations, tasks, etc., to be performed and / or carried out automatically in the real world. As used herein, “automation” means without human intervention.
[0075] The program may be embodied in instructions (e.g., software and / or firmware) stored on one or more non-transitory computer-readable and / or machine-readable storage media, such as cache memory, magnetic storage devices or disks (e.g., floppy disks, hard disk drives (HDDs), etc.), optical storage devices or disks (e.g., Blu-ray discs, optical discs (CDs), digital versatile discs (DVDs), etc.), redundant arrays of independent disks (RAID), registers, read-only memory (ROM), solid-state drives (SSDs), non-volatile memory (e.g., electrically erasable programmable ROM (EEPROM), flash memory, etc.), volatile memory (e.g., random access memory (RAM) of any type), and / or any other storage device or disk. Non-transitory computer-readable storage media may include one or more media and / or media types. The instructions of the non-transitory computer-readable and / or machine-readable media may be programmed and / or executed by programmable circuitry located in one or more hardware devices, but the entire program and / or portions thereof may alternatively be executed and / or instantiated by one or more hardware devices other than programmable circuitry, and / or may be embodied in dedicated hardware. Machine-readable instructions can be distributed across multiple hardware devices and / or executed by two or more hardware devices (e.g., server and client hardware devices). For example, client hardware devices can be implemented by endpoint client hardware devices (e.g., hardware devices associated with human and / or machine users) or intermediate client hardware device gateways (e.g., radio access networks (RAN)) that can facilitate communication between the server and endpoint client hardware devices. Similarly, non-transitory computer-readable storage media can include one or more media. Furthermore, although references... Figure 19 and Figure 20 The flowchart shown illustrates an exemplary procedure, but many other methods for implementing the exemplary digital valve controller 102 and / or web server 104 can be used alternatively. Furthermore, any or all boxes in the flowchart can be implemented by one or more hardware circuits (e.g., processor circuitry, discrete and / or integrated analog and / or digital circuitry, FPGA, ASIC, comparator, operational amplifier, logic circuitry, etc.) configured to perform the corresponding operation without executing software or firmware.
[0076] Although reference Figure 19 and Figure 20 The flowchart shown illustrates an exemplary procedure, but many other methods for implementing the exemplary digital valve controller 102 can be used instead. For example, the execution order of the blocks in the flowchart can be changed, and / or some of the blocks described can be changed, eliminated, or combined.
[0077] Programmable circuit systems can be distributed across different network locations and / or can be localized to one or more hardware devices (e.g., single-core processors (e.g., single-core CPUs), multi-core processors (e.g., multi-core CPUs, XPUs, etc.)). As used herein, programmable circuits include any type of circuit that can be programmed to perform a desired function, such as CPUs, GPUs, VPUs, and / or FPGAs. Programmable circuit systems can include one or more CPUs, one or more GPUs, one or more VPUs, and / or one or more FPGAs located in the same package (e.g., the same integrated circuit (IC) package or two or more separate housings), one or more CPUs, GPUs, VPUs, and / or one or more FPGAs in a single machine, multiple CPUs, GPUs, VPUs, and / or FPGAs distributed across multiple servers in a server rack, and / or multiple CPUs, GPUs, VPUs, and / or FPGAs distributed across one or more server racks. Additionally or alternatively, in any of the foregoing contexts, a programmable circuit may include a programmable logic device (PLD), a general-purpose array logic (GAL) device, a programmable array logic (PAL) device, a complex programmable logic device (CPLD), a simple programmable logic device (SPLD), a microcontroller (MCU), a programmable system-on-a-chip (PSoC), and / or any combination thereof. As used herein, the term "circuit" refers to at least one "circuit," and therefore, a circuit refers to a circuit or a system of circuits. As used herein, a programmable circuit includes and / or corresponds to at least one programmable circuit.
[0078] The machine-readable instructions described herein can be stored in one or more of the following formats: compressed format, encrypted format, segmented format, compiled format, executable format, packaged format, etc. Machine-readable instructions as described herein can be stored as data (e.g., computer-readable data, machine-readable data, one or more bits (e.g., one or more computer-readable bits, one or more machine-readable bits, etc.), bit streams (e.g., computer-readable bit streams, machine-readable bit streams, etc.)) and / or stored in data structures (e.g., as parts of instructions, code, code representations, etc.) that can be used to create, manufacture, and / or produce machine-executable instructions. For example, machine-readable instructions can be segmented and stored on one or more storage devices, disks, and / or computing devices (e.g., servers) located in the same or different locations (e.g., in the cloud, at the edge device, etc.) within a network or set of networks. Machine-readable instructions may require installation, modification, adaptation, updating, combination, supplementation, configuration, decryption, decompression, unpacking, distribution, redistribution, compilation, etc., to make them directly readable, interpretable, and / or executable by computing devices and / or other machines. For example, machine-readable instructions may be stored in multiple parts that are individually compressed, encrypted, and / or stored on separate computing devices, wherein these parts, when decrypted, decompressed, and / or combined, form a set of computer-executable and / or machine-executable instructions that, when implemented together, can form one or more functions and / or operations of a program such as those described herein.
[0079] In another example, machine-readable instructions may be stored in a state where they can be read by programmable circuitry, but libraries (e.g., dynamic link libraries (DLLs)), software development kits (SDKs), application programming interfaces (APIs), etc., need to be added to enable execution of the machine-readable instructions on a specific computing device or other device. In yet another example, the machine-readable instructions may need to be configured (e.g., stored settings, data input, recorded network addresses, etc.) before they can be fully or partially executed. Therefore, machine-readable, computer-readable, and / or machine-readable media as used herein can include instructions and / or programs, regardless of their specific format or state.
[0080] The machine-readable instructions described in this article can be written or represented using any suitable previously developed or future developed instruction language, scripting language, programming language, etc., including, for example, C, C++, Java, C-Sharp, Perl, Python, JavaScript, Hypertext Markup Language (HTML), Structured Query Language (SQL), Swift, etc.
[0081] As mentioned above, Figure 19 and Figure 20Exemplary operations can be implemented using executable instructions (e.g., computer-readable and / or machine-readable instructions) stored on one or more non-transitory computer-readable and / or machine-readable media. As used herein, the terms non-transitory computer-readable medium, non-transitory computer-readable storage medium, non-transitory machine-readable medium, and / or non-transitory machine-readable storage medium are explicitly defined to include any type of computer-readable storage device and / or storage disk, excluding propagation signals and transmission media. As used herein, the terms "non-transitory computer-readable storage device" and "non-transitory machine-readable storage device" are defined to include any physical (mechanical, magnetic, and / or electrical) hardware for retaining information for a period of time, excluding propagation signals and transmission media. As used herein, the term "device" refers to a physical structure, such as mechanical and / or electrical equipment, hardware, and / or circuitry, which may or may not be configured by computer-readable instructions, machine-readable instructions, etc., and / or manufactured to execute computer-readable instructions, machine-readable instructions, etc. As used herein, the term "disk" refers to a physical structure containing information storage elements to which information can be written and saved for subsequent access by a computer or other hardware platform. Examples of non-transitory computer-readable media, non-transitory computer-readable storage media, non-transitory machine-readable media, non-transitory machine-readable storage media, non-transitory computer-readable storage devices, non-transitory machine-readable storage devices, non-transitory computer-readable disks, and / or non-transitory machine-readable disks include any type of random access memory (RAM), any type of read-only memory (ROM), solid-state memory, flash memory, optical discs (e.g., CDs, DVDs, etc.), magnetic disks (e.g., magnetic HDDs), disk drives, caches, registers, redundant array of independent disks (RAID) systems, and / or any other non-transitory computer-readable and / or machine-readable media, wherein information is stored for any duration (e.g., extended time periods, permanent, transient, for temporary buffering, and / or for caching information).
[0082] Figure 19 This means that it can be executed, instantiated, and / or implemented by a programmable circuit. Figures 1-3 A flowchart of exemplary machine-readable instructions and / or exemplary operations of a digital valve controller and web server 1900. Figure 19The exemplary machine-readable instructions and / or exemplary operations 1900 begin at block 1902, where programmable circuitry 304 instantiates a web server in a field device within the control system. For example, programmable circuitry 304 instantiates web server 104 in digital valve controller 102. At block 1904, interface circuitry 302 establishes a connection between web server 104 and client device 106. At block 1906, interface circuitry 302 receives a request from client device 106 (e.g., based on user input to client device 106). For example, interface circuitry 302 receives a Hypertext Transfer Protocol (HTTP) request from client device 106 instructing web server 104 to provide data to client device 106. The data may be substantially real-time data collected by digital valve controller 102 from one or more sensors that measure pressure, temperature, valve stroke, etc., associated with fluid control valve 108. At block 1908, interface circuitry 302 accesses the data collected by digital valve controller 102. For example, interface circuitry 302 accesses data from memory system 306 and / or status bits of digital valve controller 102 and / or web server 104. In some examples, the data is substantially real-time data collected by digital valve controller 102 from one or more sensors. At block 1910, interface circuitry 302 transmits the requested data to client device 106 before the example process ends. In some examples, interface circuitry 302 sends a command instructing client device 106 to access a web browser extension to provide data to be presented on client device 106. In some such examples, the web browser extension is stored in the memory of client device 106.
[0083] Figure 20 This means that it can be executed, instantiated, and / or implemented by a programmable circuit. Figures 1-3 A flowchart of exemplary machine-readable instructions and / or example operations for a digital valve controller and web server 2000. Figure 20 The flowchart provides more specific details (relative to) Figure 19 This implements widgets and web browser extensions to enable interaction between client device 106 and web server 104 of digital valve controller 102. Figure 20The exemplary machine-readable instructions and / or exemplary operations 2000 begin at block 2002, where programmable circuitry 304 instantiates a web server in a field device within a control system. For example, programmable circuitry 304 instantiates a web server 104 in a digital valve controller 102. At block 2004, interface circuitry 302 establishes a connection between web server 104 and client device 106. At block 2006, interface circuitry 302 provides a web page, including any embedded widgets, to client device 106. For example, web server 104 generates a web page as part of a GUI 308, including multiple widgets, and populates the widgets with corresponding data. In such an example, interface circuitry 302 sends data to client device 106 associated with the corresponding widget in the web page's widgets.
[0084] At box 2008, interface circuitry 302 determines whether a request for data has been received from client device 106. In some examples, this request is based on the user of client device 106 interacting with a widget within a widget. In some examples, the request is based on the user navigating to a different web page and / or selecting different options on the current web page and / or on a different web page the user has already navigated to. If no request has been received, operation 2000 proceeds to box 2022. If a request has been received, operation 2000 proceeds to box 2010.
[0085] At block 2010, programmable circuitry 304 and / or memory system 306 determine whether the requested data is locally available. If so, control proceeds to block 2012, where memory system 306 retrieves the requested data. At block 2014, exemplary interface circuitry 302 provides the requested data to client device 106 (e.g., via GUI 308). Control then proceeds to block 2022. Returning to block 2010, if the requested data is not locally available, control proceeds to block 2016, where interface circuitry 302 determines whether client device 106 has a web browser extension with the requested data. If so, control proceeds to block 2018, where programmable circuitry 304, in conjunction with interface circuitry 302, instructs client device to retrieve the requested data from the web browser extension. In some examples, the requested data may be any type of data and / or file that is not locally available on digital valve controller 102 (e.g., due to memory constraints). For example, the requested data could be a video (e.g., a video tutorial), a high-resolution image, a user manual, etc. After client device 106 is instructed to retrieve the requested data, control proceeds to box 2022. Returning to box 2016, if client device 106 does not have a web browser extension, control proceeds to box 2020, where interface circuitry 302 provides notification about web browser extensions and / or links to them. Control then proceeds to box 2022. If client device 106 is currently connected to the internet, it may be able to download the web browser extension at that time to retrieve the requested data. If the internet is currently unavailable, the user may need to record the available extensions and download them the next time client device 106 connects to the internet.
[0086] At box 2022, exemplary interface circuitry 302 determines whether a command to update the firmware of a field device (e.g., digital valve controller 102) has been received from client device 106. If so, control proceeds to box 2024, where interface circuitry 302 receives the firmware update from a web browser extension on client device 106. At box 2026, programmable circuitry 304 updates the firmware of the field device. Control then proceeds to box 2028. Returning to box 2022, if no firmware update command has been received, control proceeds directly to box 2028. At box 2028, programmable circuitry system 304 determines whether to continue the process. If so, control returns to box 2006. Otherwise, Figure 20 The exemplary operation 2000 ends.
[0087] Figure 21 It is constructed to execute and / or instantiate Figure 19 and Figure 20Exemplary machine-readable instructions and / or exemplary operations to implement Figure 3 A block diagram of an exemplary programmable circuit system platform 2100 for a digital valve controller 102. The programmable circuit system platform 2100 may be, for example, a server, a personal computer, a workstation, a self-learning machine (e.g., a neural network), an embedded system, or any other type of computing and / or electronic device.
[0088] The programmable circuit system platform 2100 shown in the example includes programmable circuitry 2112. Programmable circuitry 2112 is hardware. For example, programmable circuitry 2112 can be implemented by one or more integrated circuits, logic circuits, FPGAs, microprocessors, CPUs, GPUs, DSPs, XPUs, and / or microcontrollers from any desired family or manufacturer. Programmable circuitry 2112 can be implemented by one or more semiconductor-based (e.g., silicon-based) devices. In this example, programmable circuitry 2112 implements programmable circuitry 304 and GUI 308.
[0089] The programmable circuit 2112 of the illustrated example includes local memory 2113 (e.g., cache, registers, etc.). The programmable circuit 2112 of the illustrated example communicates via bus 2118 with main memories 2114, 2116, including volatile memory 2114 and non-volatile memory 2116. The volatile memory 2114 may be implemented using synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS® dynamic random access memory (RDRAM®), and / or any other type of RAM device. The non-volatile memory 2116 may be implemented using flash memory and / or any other desired type of memory device. Access to the main memories 2114, 2116 of the illustrated example is controlled by a memory controller 2117. In some examples, the memory controller 2117 may be implemented using one or more integrated circuits, logic circuits, microcontrollers, or any other type of circuit from any desired family or manufacturer to manage the flow of data to and from the main memories 2114, 2116. In the examples disclosed herein, main memories 2114 and 2116 are Figure 3 It is part of the memory system 306.
[0090] The programmable circuit system platform 2100 shown in the example also includes interface circuitry 2120. Interface circuitry 2120 can be implemented in hardware according to any type of interface standard, such as an Ethernet interface, a Universal Serial Bus (USB) interface, a Bluetooth® interface, a Near Field Communication (NFC) interface, a Peripheral Component Interconnect (PCI) interface, and / or a Peripheral Component Interconnect Fast (PCIe) interface. In the example disclosed herein, interface circuitry 2120 implements... Figure 3The interface circuit 302.
[0091] In the example shown, one or more input devices 2122 are connected to interface circuitry 2120. Input devices 2122 allow users (e.g., human users, machine users, etc.) to input data and / or commands into programmable circuitry 2112. Input devices 2122 can be implemented using, for example, audio sensors, microphones, cameras (still or video), keyboards, buttons, mice, touchscreens, touchpads, trackballs, isotope devices, and / or voice recognition systems.
[0092] One or more output devices 2124 are also connected to the interface circuitry 2120 of the illustrated example. The output devices 2124 may be implemented, for example, by display devices (e.g., light-emitting diodes (LEDs), organic light-emitting diodes (OLEDs), liquid crystal displays (LCDs), in-plane switching (IPS) displays, touchscreens, etc.) and / or haptic output devices. Therefore, the interface circuitry 2120 of the illustrated example typically includes a graphics driver card, a graphics driver chip, and / or graphics processor circuitry such as a GPU.
[0093] The interface circuit 2120 of the example shown also includes communication devices such as transmitters, receivers, transceivers, modems, residential gateways, wireless access points, and / or network interfaces to facilitate the exchange of data with external machines (e.g., any kind of computing device) via network 2126. Communication can be achieved through, for example, Ethernet connections, digital subscriber line (DSL) connections, telephone line connections, coaxial cable systems, satellite systems, beyond-line-of-sight wireless systems, line-of-sight wireless systems, cellular telephone systems, optical connections, etc.
[0094] The programmable circuit system platform 2100 illustrated also includes one or more mass storage disks or devices 2128 for storing firmware, software, and / or data. Examples of such mass storage disks or devices 2128 include magnetic storage devices (e.g., floppy disks, drives, HDDs, etc.), optical storage devices (e.g., Blu-ray discs, CDs, DVDs, etc.), RAID systems, and / or solid-state storage disks or devices (such as flash memory devices and / or SSDs). In the examples disclosed herein, the mass storage disk or device 2128 is... Figure 3 It is part of the memory system 306.
[0095] It can be by Figure 19 and Figure 20 The machine-readable instructions 2132 implemented by the machine-readable instructions may be stored in a mass storage device 2128, a volatile memory 2114, a non-volatile memory 2116 and / or on at least one non-transitory computer-readable storage medium that may be removable.
[0096] As used herein, an integrated circuit / circuit system is defined as one or more semiconductor packages containing one or more circuit elements, such as transistors, capacitors, inductors, resistors, current paths, diodes, etc. For example, an integrated circuit can be implemented as one or more of an ASIC, FPGA, chip, microchip, programmable circuit, semiconductor substrate coupling multiple circuit elements, system-on-a-chip (SoC), etc.
[0097] exist Figure 22 The diagram illustrates the use of, for example, to... Figure 21 This is a block diagram of an exemplary software distribution platform 2205 that distributes software, such as the exemplary machine-readable instructions 2132, to other hardware devices (e.g., hardware devices owned and / or operated by a third party from the owner and / or operator of the software distribution platform). The exemplary software distribution platform 2205 can be implemented by any computer server, data facility, cloud service, etc., capable of storing software and delivering it to other computing devices. The third party can be a customer of the entity that owns and / or operates the software distribution platform 2205. In the illustrated example, the software distribution platform 2205 includes one or more servers and one or more storage devices. The storage devices store the machine-readable instructions 2132, which may correspond to the instructions described above. Figure 19 and Figure 20 The exemplary machine-readable instructions are provided. One or more servers of the exemplary software distribution platform 2205 communicate with the exemplary network 2210, which may correspond to the Internet and / or any one or more of the example networks described above. The servers enable the downloading of machine-readable instructions 2132 from the software distribution platform 2205. Although referred to as software above, the distributed “software” may alternatively be firmware.
[0098] "Comprising" and "including" (and all their forms and tenses) are used herein as open-ended terms. Therefore, whenever a claim uses any form of "comprising" or "including" (e.g., including, containing, comprising, having, etc.) as a preamble or within any kind of claim statement, it should be understood that additional elements, terms, etc., may be present without falling outside the scope of the corresponding claim or statement. As used herein, when the phrase "at least" is used as a transitional term, for example, in the preamble of a claim, it is open-ended in the same way that the terms "comprising" and "including" are open-ended. When used, for example, in the form of A, B, and / or C, the term "and / or" refers to any combination or subset of A, B, C, such as (1) only A, (2) only B, (3) only C, (4) A and B, (5) A and C, (6) B and C, or (7) A and B and C. As used herein in the context of describing structures, components, items, objects, and / or things, the phrase "at least one of A and B" is intended to refer to an implementation that includes (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. Similarly, as used herein in the context of describing structures, components, items, objects, and / or things, the phrase "at least one of A and B" is intended to refer to an implementation that includes (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. As used herein in the context of describing the implementation or execution of processes, instructions, actions, activities, etc., the phrase "at least one of A and B" is intended to refer to an implementation that includes (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. Similarly, as used herein in the context of describing the implementation or execution of processes, instructions, actions, activities, etc., the phrase "at least one of A and B" is intended to refer to an implementation that includes (1) at least one A, (2) at least one B, or (3) at least one A and at least one B.
[0099] As used herein, singular references (e.g., "a," "an," "first," "second," etc.) do not exclude plural. As used herein, the term "a" or "an" refers to one or more of the same object. The terms "a" (or "an"), "one or more," and "at least one" are used interchangeably herein. Furthermore, although listed separately, multiple means, elements, or actions may be implemented by, for example, the same entity or object. Additionally, although individual features may be included in different examples or claims, these features may be combined, and inclusion in different examples or claims does not imply that the combination of features is infeasible and / or disadvantageous.
[0100] Unless otherwise specified, descriptors such as “first,” “second,” “third,” etc., are used herein without imposing or otherwise indicating any meaning of priority, physical order, arrangement in a list, and / or any sorting, but merely as labels and / or arbitrary names to distinguish elements for the purpose of understanding the disclosed examples. In some examples, the descriptor “first” may be used to refer to an element in a particular embodiment, while the same element may be referred to in the claims by different descriptors (such as “second” or “third”). In such cases, it should be understood that such descriptors are only used to clearly identify those elements in the context of the discussion (e.g., in the claims), where elements may otherwise share the same name, for example.
[0101] As used herein, unless otherwise stated, a connection reference (e.g., attachment, coupling, connection, and engagement) may include intermediate components between elements referenced by the connection reference and / or relative movement between these elements. Therefore, a connection reference does not necessarily imply that two elements are directly connected and / or fixed to each other.
[0102] As used in this article, "substantially real-time" and "substantially real-time" mean that something happens in a near-instantaneous manner, acknowledging that there may be real-world delays in computation time, transmission, etc. Therefore, unless otherwise stated, "substantially real-time" and "substantially real-time" mean real-time plus 1 second.
[0103] As used herein, the phrase “communication” (including its variations) covers direct communication and / or indirect communication through one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or continuous communication, but additionally includes selective communication at periodic intervals, predetermined intervals, non-periodic intervals and / or one-off events.
[0104] As used herein, “programmable circuit” is defined as including: (i) one or more special-purpose circuits (e.g., special-purpose circuits (ASICs) configured to perform one or more specific operations and including one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors)); and / or (ii) one or more general-purpose semiconductor-based circuits that can be programmed with instructions to perform one or more specific functions and / or one or more operations and include one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors). Examples of programmable circuits include programmable microprocessors, such as a central processing unit (CPU) capable of executing first instructions to perform one or more operations and / or functions, a field-programmable gate array (FPGA) capable of executing second instructions to configure and / or construct an FPGA to instantiate one or more operations and / or functions corresponding to the first instructions, a graphics processing unit (GPU) capable of executing first instructions to perform one or more operations and / or functions, a digital signal processor (DSP), an XPU, a network processing unit (NPU), one or more microcontrollers capable of executing first instructions to perform one or more operations and / or functions, and / or integrated circuits such as application-specific integrated circuits (ASICs). For example, an XPU can be implemented by a heterogeneous computing system that includes multiple types of programmable circuits (e.g., one or more FPGAs, one or more CPUs, one or more GPUs, one or more NPUs, one or more DSPs, etc., and / or any combination thereof), and orchestration techniques (e.g., multiple application programming interfaces (APIs) that can assign multiple computing tasks to any of the multiple types of programmable circuits that are suitable and available to perform the multiple computing tasks).
[0105] Based on the foregoing, it should be understood that exemplary systems, apparatuses, articles, and methods for implementing digital field device controllers with web servers have been disclosed. The disclosed systems, apparatuses, articles, and methods improve the efficiency of interaction with field device controllers in process control systems by implementing a web server in the field device controller to provide device-specific data via a streamlined browser-accessible interface on client devices. Therefore, the disclosed systems, apparatuses, articles, and methods relate to one or more improvements to the operation of machines such as computers or other electronic and / or mechanical equipment.
[0106] Further examples and combinations thereof include the following:
[0107] Example 1 includes an apparatus comprising interface circuitry, machine-readable instructions, and programmable circuitry programmed by the machine-readable instructions to: instantiate a web server at a field device in a control system; establish a connection between the web server and a client device; access data collected by the field device in response to a request from the client device; and cause the interface circuitry to transmit data from the web server to the client device.
[0108] Example 2 includes an apparatus according to any of the preceding clauses, wherein the data is substantially real-time data from one or more sensors used to measure at least one of pressure or temperature.
[0109] Example 3 includes an apparatus according to any of the preceding clauses, wherein the field device is a digital valve controller and the data is substantially real-time data representing the stroke of a fluid control valve.
[0110] Example 4 includes an apparatus according to any of the preceding clauses, wherein the programmable circuitry causes the web server to generate a web page including a plurality of widgets, populates the widgets with different data from the data, and causes the interface circuitry to transmit the data in association with the corresponding widgets in the widgets to the client device.
[0111] Example 5 includes an apparatus according to any of the preceding clauses, wherein the data is first data, and the programmable circuitry instructs the client device to access second data included in a web browser extension installed on the client device, the second data being associated with the field device.
[0112] Example 6 includes an apparatus according to any of the preceding clauses, wherein the memory of the field device is insufficient to store the second data.
[0113] Example 7 includes an apparatus according to any of the preceding clauses, wherein the second data includes at least one of video, high-resolution image, or user manual.
[0114] Example 8 includes an apparatus according to any of the preceding clauses, wherein the programmable circuitry updates the firmware of the field device based on a firmware update file provided by the client device, the firmware update file being included in a web browser extension installed on the client device.
[0115] Example 9 includes a non-transitory machine-readable medium comprising instructions for causing a programmable circuit to perform at least the following operations: instantiating a web server at a field device in a control system; establishing a connection between the web server and a client device; accessing data collected by the field device in response to a request from the client device; and causing data to be transferred from the web server to the client device.
[0116] Example 10 includes a non-transitory machine-readable medium according to any of the preceding clauses, wherein the data is substantially real-time data from one or more sensors used to measure at least one of pressure or temperature.
[0117] Example 11 includes a non-transitory machine-readable medium according to any of the preceding clauses, wherein the field device is a digital valve controller and the data is substantially real-time data representing the stroke of a fluid control valve.
[0118] Example 12 includes a non-transitory machine-readable medium according to any of the preceding clauses, wherein the instructions cause the programmable circuitry to perform the following operations: cause the web server to: generate a web page including a plurality of widgets, and populate the widgets with different data from the data; and cause the data to be transmitted to the client device in association with a corresponding widget among the widgets.
[0119] Example 13 includes any non-transitory machine-readable medium as described in the preceding clauses, wherein the data is first data, and the instructions cause the programmable circuitry to instruct the client device to access second data included in a web browser extension installed on the client device, the second data being associated with the field device.
[0120] Example 14 includes a non-transitory machine-readable medium according to any of the preceding clauses, wherein the memory of the field device is insufficient to store the second data.
[0121] Example 15 includes a non-transitory machine-readable medium according to any of the preceding clauses, wherein the second data includes at least one of video, high-resolution image, or user manual.
[0122] Example 16 includes any of the non-transitory machine-readable media described in the preceding clauses, wherein the instructions cause the programmable circuitry to update the firmware of the field device based on a firmware update file provided by the client device, the firmware update file being included in a web browser extension installed on the client device.
[0123] Example 17 includes a method comprising: instantiating a web server at a field device in a control system by executing instructions using programmable circuitry; establishing a connection between the web server and the client device in response to a request from a client device; accessing data collected by the field device; and transmitting the data from the web server to the client device by executing instructions using programmable circuitry.
[0124] Example 18 includes the method according to any of the preceding clauses, wherein the data is substantially real-time data from one or more sensors used to measure at least one of pressure or temperature.
[0125] Example 19 includes the method according to any of the preceding clauses, comprising: generating a web page including a plurality of widgets using the web server; populating the widgets with different data from the data; and transmitting the data in association with a corresponding widget among the widgets to the client device.
[0126] Example 20 includes the method according to any of the preceding clauses, wherein the data is first data, and the method includes instructing the client device to access second data included in a web browser extension installed on the client device, the second data being associated with the field device.
[0127] The appended claims are hereby incorporated by reference into this specific embodiment. Although certain example systems, apparatuses, articles, and methods have been disclosed herein, the scope of this patent is not limited thereto. Rather, this patent covers all systems, apparatuses, articles, and methods that fall fully within the scope of the claims of this patent.
Claims
1. An apparatus comprising: Interface circuit; Machine-readable instructions; Programmable circuit, programmed by the machine-readable instructions to perform the following operations: Instantiate the web server at the field device in the control system; Establish a connection between the web server and the client device; In response to a request from the client device, access the data collected by the field device; as well as The interface circuit transmits the data from the web server to the client device.
2. The apparatus according to claim 1, wherein, The data is substantially real-time data from one or more sensors used to measure at least one of pressure or temperature.
3. The apparatus according to claim 1, wherein, The field device is a digital valve controller, and the data is substantially real-time data representing the stroke of the fluid control valve.
4. The apparatus according to any one of claims 1-3, wherein, The programmable circuit is used for: Cause the web server to perform the following operations: Generate a web page that includes multiple widgets; and Populate the widget with different data from the data; and The interface circuit transmits the data, associated with the corresponding widget in the widget, to the client device.
5. The apparatus according to any one of claims 1-3, wherein, The data is first data, and the programmable circuitry is used to instruct the client device to access second data included in a web browser extension installed on the client device, the second data being associated with the field device.
6. The apparatus according to claim 5, wherein, The field device's memory is insufficient to store the second data.
7. The apparatus according to claim 5, wherein, The second data includes at least one of video, high-resolution image, or user manual.
8. The apparatus according to any one of claims 1-3, wherein, The programmable circuitry is used to update the firmware of the field device based on a firmware update file provided by the client device, the firmware update file being included in a web browser extension installed on the client device.
9. A machine-readable medium comprising instructions for causing a programmable circuit to perform at least the following operations: Instantiate the web server at the field device in the control system; Establish a connection between the web server and the client device; In response to a request from the client device, access the data collected by the field device; as well as This enables the data to be transmitted from the web server to the client device.
10. The machine-readable medium according to claim 9, wherein, The data is substantially real-time data from one or more sensors used to measure at least one of pressure or temperature.
11. The machine-readable medium according to claim 9, wherein, The field device is a digital valve controller, and the data is substantially real-time data representing the stroke of the fluid control valve.
12. The machine-readable medium according to claim 9, wherein, The instructions are used to cause the programmable circuit system to perform the following operations: Cause the web server to perform the following operations: Generate a web page that includes multiple widgets; and Populate the widget with different data from the data; and The data is transmitted to the client device in association with the corresponding widget in the widget.
13. The machine-readable medium according to any one of claims 9-12, wherein, The data is first data, and the instructions are used to cause the programmable circuitry to instruct the client device to access second data included in a web browser extension installed on the client device, the second data being associated with the field device.
14. The machine-readable medium according to claim 13, wherein, The field device's memory is insufficient to store the second data.
15. The machine-readable medium of claim 13, wherein the second data comprises at least one of video, high-resolution image, or user manual.
16. The machine-readable medium according to any one of claims 9-12, wherein, The instructions are used to cause the programmable circuit to update the firmware of the field device based on a firmware update file provided by the client device, the firmware update file being included in a web browser extension installed on the client device.
17. A method comprising: Instantiate the web server at the field device in the control system; Establish a connection between the web server and the client device; In response to a request from the client device, access the data collected by the field device; as well as The data is transmitted from the web server to the client device.
18. The method according to claim 17, wherein, The data is substantially real-time data from one or more sensors used to measure at least one of pressure or temperature.
19. The method of claim 17, comprising: The web server is used to generate a web page that includes multiple widgets; as well as Populate the widget with different data from the data; as well as The data is transmitted to the client device in association with the corresponding widget in the widget.
20. The method according to any one of claims 17-19, wherein, The data is first data, and the method includes instructing the client device to access second data included in a web browser extension installed on the client device, the second data being associated with the field device.
