US 6,779,128 B1Grant
Fault-tolerant data transfer
Issue Date:2004-08-17
•29 Claims
•3 Drawing Sheets
Abstract
A control system has a first module that includes a memory and diagnostic logic. The diagnostic logic periodically tests at least selected locations in the memory and, in connection with such testing, reads data from those locations and writes that data back to the locations. A second module is coupled to the first module such that the written back data is transferred to the second module, as well as to the memory of the first. Mapping or other conversion logic can translate addresses or other data identifiers, as necessary, to insure that the transferred data is properly identified upon its receipt by the second module.
Metadata
Assignee
- Invensys Systems, Inc.
Inventors
- Alan Gale
- Christain Bourdin
- Gene Cummings
Application Information
Application Number:US 09/507,326
Filing Date:2000-02-18
Priority Date:2000-02-18
Art Unit:7
Classifications
IPC:
G06F 1100G11C 2900
Field of Search:
714 42714 43714 52714718714719714 6714 7714 8
Patent Drawings (3 sheets)
Description
Background of the Invention
[0002] The invention pertains to process control and, more particularly, to digital data processing methods and apparatus for duplicating data in control systems.
[0003] The terms “control” and “control systems” refer to the control of a device or system by monitoring one or more of its characteristics. This is used to insure that output, processing, quality and/or efficiency remain within desired parameters over the course of time. In many control systems, digital data processing or other automated apparatus monitor the device or system in question and automatically adjust its operational parameters. In other control systems, such apparatus monitor the device or system and display alarms or other indicia of its characteristics, leaving responsibility for adjustment to the operator.
[0004] Control is used in a number of fields. Process control, for example, is typically employed in the manufacturing sector for process, repetitive and discrete manufactures, though, it also has wide application in electric and other service industries. Environmental control finds application in residential, commercial, institutional and industrial settings, where temperature and other environmental factors must be properly maintained. Control is also used in articles of manufacture, from toasters to aircraft, to monitor and control device operation.
[0005] Reliability is among the key requirements of any control system. Failures are almost never acceptable, for example, in critical process control and safety applications. Even occasional failures are undesirable in conventional control applications, such as manufacturing process control.
[0006] The art suggests the use of testing and other operational techniques to improve the reliability of control systems. Industry standards, such as IEC 61508 and DIN V VDE 0801, Class AK6, for example, set minimum requirements for fault detection in digital data processors used in safety-related systems. One of these calls for testing the random access memory of an operating computer on a periodic basis, e.g., every 15 seconds. This typically involves writing a known value to each addressable memory location and reading the locations to verify the stored values. Applications data contained in the memory is temporarily stored, e.g., in processor registers, while each memory location is being tested.
[0007] Though testing techniques as described above can give system designers and operators added comfort in the reliability of their control systems, the utility of those techniques is limited.
[0008] Though otherwise unrelated to the foregoing, the art also suggests the use of redundancy as a means of enhancing reliability. This typically involves using two or more control elements in place of one. For example, U.S. Pat. No. 4,347,563 discloses an industrial control system in which redundant digital data processing units serve as bus masters “of the moment,” monitoring status information generated by primary processing units. If a redundant unit detects that a primary has gone faulty while executing an application program, the redundant unit loads that program and takes over the primary's function.
[0009] A problem with systems that rely on redundant processing units is updating newly inserted units. Typically, this is accomplished by taking both active and new units off-line so that the contents of the former can be downloaded to the latter. Though the off-line period can be relatively brief by layman's standards, it can be quite long from a control perspective, thus, raising the probability that a failure will disrupt system operation, or worse.
[0010] An object of the present invention is to provide improved methods and apparatus for control and, more particularly, by way of example, for duplicating data utilized by modules in a control system. Another object is to provide improved such methods and apparatus as can be utilized in fault-tolerant or fault-detecting systems, e.g., for purposes of copying data from an active module to a newly inserted backup module.
[0011] Yet still another object of the invention is to provide such methods and apparatus as permit a backup unit to be updated while the control system remains online.
[0012] Still yet another object of the invention is to provide such methods and apparatus as can be implemented with little additional software and hardware overhead.
Summary of the Invention
[0013] The foregoing are among the objects attained by the invention which provides, in one aspect, a control system with a first module that includes a memory and diagnostic logic. The diagnostic logic periodically tests at least selected locations in the memory and, in connection with such testing, reads data from those locations and writes the data back to them. A second module is coupled to the first module such that the data that is written back to the memory of the first module is transferred to the second module, as well.
[0014] Further aspects of the invention provide a system as described above in which the first and/or second modules each form part of a workstation, field controller, field device, smart field device, or other functionality arranged for industrial, manufacturing, service, environmental, or process control. Data transferred between the modules can comprise any of bits, bytes, words, longwords, records, arrays, matrices, structs, objects, data structures or other items from or portions of the first module's memory. The system can include logic that maps addresses, symbolic names or other identifiers associated with data in the first module to corresponding addresses, symbolic names or other identifiers for association with the data in the second module.
[0015] By way of example, the first module can be a “smart” field device in a process control system. The second module can be a workstation that (among other things) stores backup copies of configuration or other data in the field device. Diagnostic logic present in the field device, for example, can test locations in its memory, e.g., in compliance with the aforementioned IEC and DIN standards. In connection with the testing, the logic can read and rewrite the contents of the memory locations. Switching logic can transfer those rewritten contents (e.g., data words, records, objects, etc.) to the second module, as well as to the first module's memory. Mapping or other conversion logic can map or translate addresses or other identifiers in connection with the transfer.
[0016] Further aspects of the invention provide a system as described above in which the first and second modules include first and second memories, respectively; the first memory element normally being coupled to a first memory bus; the second memory element normally being coupled to a second memory bus. Each memory element stores data in accord with commands received over the bus to which it is coupled. The switching logic has a memory update mode that temporarily couples the second memory element to the first memory bus in lieu of the second memory bus, e.g., so that the second memory element receives data and data storage commands identically with those received by the first memory element. The switching logic can remain in the memory update mode long enough for the diagnostic logic to rewrite all of the selected locations of the first memory element.
[0017] Further aspects of the invention provide a control device as described above in which the switching element includes a field effect transistor (FET) switch and, preferably, an array of such switches. The switches connect conductors in the first and second memory buses to respective conductors of the first memory element.
[0018] The invention provides, in other aspects, a control device having first and second memory elements and first and second memory buses, as described above. A first switching element has a first switching mode that couples the first memory element to the first memory bus, and a second switching mode that couples the first memory element to the second memory bus. A second switching element likewise has a first switching mode that couples the second memory element to the second memory bus, and a second switching mode that couples the second memory element to the first memory bus.
[0019] Logic coupled to the first and second switching elements normally places them in their respective first modes. The logic can respond, e.g., to insertion or powering-up of one of those elements, for placing the associated switching element in its second mode, thereby, causing its memory to be updated from the other memory.
[0020] Still further aspects of the invention provide a control device as described above in which the first and second memory elements are part of first and second modules, respectively, that include processors and input/output logic, as well as memory elements.
[0021] Still other aspects of the invention provide methods of operating control devices and systems of the types described above.
[0022] Methods and apparatus according to the invention are advantageous over the prior art. For example, a memory (or a selected portion thereof) can be copied to a backup unit without either unit being brought off-line. Moreover, the memory (or memory portion) can be copied quickly, i.e., in no more time than is required to verify the integrity of the unit being backed up. Still further, apart from switch setting, no substantial foreground, background or other additional processes are required for the update process.
Brief Description of the Drawings
[0023] A more complete understanding of the invention may be attained by reference to the drawings, in which:
[0024] FIG. 1 depicts a control device according to the invention;
[0025] FIG. 2 depicts a method of operating dual processing sections of the control device of FIG. 1; and
[0026] FIG. 3 depicts operation of the processing sections of the device of FIG. 1 during execution of the method of FIG. 2.
Detailed Description of the Illustrated Embodiment
[0027] FIG. 1 depicts processing modules 12, 14 of a control device or system 10 according to the invention. Such modules may be separate workstations, field controllers, field devices (“smart” or otherwise), or other functionality within an industrial, manufacturing, service, environmental or other control system.
[0028] In the illustrated embodiment, modules 12, 14 represent processing sections within an individual such workstation, field controller, field device, or other such functionality for industrial, manufacturing, service, environmental or other control. Particularly, illustrated sections 12, 14 provide fault-detecting and, preferably, fault-tolerant operation: upon failure of one of the processing sections, the other processing section may continue operation without substantial interruption.
[0029] Illustrated section 12 includes processor 16, memory 18, memory arbitration circuitry 20, PCI (or other bus) interface circuitry 22 and ethernet (or other network) interface circuitry 24. These are selected, configured and operated in the conventional manner known in the art, as modified in accord with the teachings hereof. Illustrated section 14 includes like components 26-32, likewise selected, configured and operated in the conventional manner, as modified in accord with the teachings hereof.
[0030] Sections 12, 14 can operate in lock-step synchronism, such that the contents of their respective memories 18, 28 and the operations of their respective processors 16, 26 (and other components) are substantially identical and synchronous at all times of normal operation. In the illustrated embodiment, sections 12, 14 operate with loose coupling, such that, although the processors 16, 26 (and other components) operate asynchronously with respect to one another, the operations they perform and the contents of their respective memories 18, 28 are identical when viewed over a longer time interval (e.g., between input/output or other events).
[0031] Those skilled in the art will appreciate that modules 12, 14 may operate with other degrees of synchronism and/or coupling. Thus, by way of non-limiting example, one of the modules may serve as a “shadow” to the other: in the event that the master becomes disabled, the shadow can take over. Moreover, the modules may operate in entirely different manners and with entirely different purposes, except insofar as one of the modules duplicates the memory (or a portion thereof) of the other module. Module 12, for example, may be a field device and module 14 may be a workstation that duplicates or “backs up” bits, bytes, words, longwords, records, arrays, matrices, structs, objects, data structures or items in or portions of the memory of section 12.
[0032] In the illustrated embodiment, logic (not shown) can be provided that monitors the operations of the sections 12, 14 to insure the desired degree of synchronicity or coupling. Further logic (not shown) can be provided to permit only one of the processing sections, to wit, the “master,” to drive signals to other components (not shown) of the control system. In this regard, illustrated sections 12, 14 are coupled to such other components by line 34, which may comprise a bus, network, or other communications medium which may, itself, be fault-tolerant, e.g., as indicated by redundant conductor sets 34a, 34b.
[0033] One and preferably both of modules 12, 14 comprise diagnostic logic that verifies the integrity of the respective memories 18, 28. This is accomplished by writing a known bit pattern or value to each location and reading the value so stored to insure a match. Compliance with the aforementioned IEC and DIN standards requires that each location within memories 18, 28 be checked once, approximately every 15 seconds. The specific testing pattern, timing, etc., varies in accord with standard.
[0034] To avoid losing valid data during testing, the diagnostic logic records the contents of each memory location, e.g., to a register of the associated processor, prior to testing that location. The recorded value is rewritten to the respective location, preferably, immediately after it has been tested.
[0035] Diagnostic testing of the memories can be performed by separate logic within (or outside) each of the modules 12, 14. In the illustrated embodiment, it is exercised by the respective processors 16, 26. This is indicated by blocks 36, 38 in FIG. 1.
[0036] Memories 18, 28 respond in the conventional manner to applied signals to store and retrieve data. Thus, for example, memory 18 responds to control signals applied via bus 40 to store data applied via that same bus. Memory 28 likewise, and by way of further example, responds to control signals applied via bus 42 to store data applied via that same bus.
[0037] In normal operation, buses 40, 42 are coupled to processors 16, 26, respectively, and more generally to the other components of the respective modules 12, 14. To this end, the illustrated embodiment employs switches 44, 46, each having a first operational mode that couples the buses 40, 42 (and, therefore, the memories 18, 28) to the processors 16, 26, respectively, and more generally to buses 48, 50, respectively, internal to each module. In this latter regard, it will be appreciated that the components 16 and 20-24 of module 12 may share a common bus (e.g., bus 48) and, likewise, that components, 26 and 29-32 share a common bus (e.g., bus 50).
[0038] With its switch 44 in its first mode, the memory 18 responds to control signals applied via bus 48 to store and retrieve data as dictated by elements 16 and/or 20-24. Similarly, with switch 46 in its first mode, memory 28 responds to control signals applied via bus 50 to store and retrieve data as dictated by elements 26 and/or 29-32.
[0039] Switches 44, 46 each have a second operational mode that couple buses 40, 42 (and, therefore, memories 18, 28) to processors 26, 16, respectively, and more generally to buses 50, 48, respectively, of the other module. In this mode, the memory 28 responds to control signals applied via bus 50 to at least store data dictated by elements 26 and 29-32. Similarly, memory 18 responds to control signals applied via bus 48 to store data dictated by elements 16 and 20-34. In the illustrated embodiment, read data generated by a memory 18, 28 is ignored when the respective switch is in the second mode.
[0040] A line 52 connects switches 44, 46 to one another, thereby, enabling the transfer of control and data signals between the modules 12, 14. Those skilled in the art will appreciate that each switch 44, 46 can be connected directly to the bus 50, 48, respectively, of the other module 14, 12, respectively, rather than to the other switch 46, 44, respectively. In the illustrated embodiment, line 52 comprises a dedicated parallel bus having equal width to the memory buses 48, 50.
[0041] In other embodiments, it can comprise a bus of differing width from either of memory buses 48, 50 or it can comprise other communications medium, e.g., a serial bus, network, or otherwise. Indeed, line 52 and line 34 can be coextensive, i.e., insofar as they represent the same communications medium. In such other embodiments, switches 44, 46 are equipped with suitable interface circuitry to permit the transfer of information with line 52. Such interface circuitry can include mapping logic for converting addresses in one address space (e.g., the memory address space of module 12) to that of another address space (e.g., the memory address space of module 14). Alternatively, such interface circuitry can include logic providing symbolic name or other identifier conversion, e.g., in embodiments where the modules 12, 14 use line 52 to transfer information pertaining to selected memory objects, data structures or other items.
[0042] During normal operation of the illustrated embodiment, switches 44, 46 operate in their first respective modes. A switch 44, 46 is placed in its second operational mode when its respective memory 18, 28 requires updating from the memory 28, 18 of the other module. The second operational mode is typically used, for example, upon powering-up a module and/or following an error. In the illustrated embodiment, that mode is preferably used only temporarily, i.e., for a period long enough for the diagnostic logic of the other module to sweep through its respective memory. In alternate embodiments, either of the switches can be configured to
[0043] The mode of switches 44, 46 is determined by control signals X_IN applied by the processors 16, 26, or other logic within (or outside) modules 12, 14. In the illustrated embodiment, a processor, e.g., 26, applies an X_IN signal (and more precisely takes the X_IN signal high) to its respective switch 46 in order to place that switch in the second mode. The other processor, e.g., 16, must concurrently apply an X_ENA signal (and, more precisely, take the X_ENA signal high) to its respective switch 44 in order to permit data to be transferred from its internal bus, e.g., bus 48, to the inter-switch line 52.
[0044] Those skilled in the art will appreciate that, in other embodiments the X_IN and X_ENA signals may be used individually or in combination with other signals and signal sources. Likewise, a single switch may be employed for all transfers. Thus, for example, switch 44 can be configured to transfer to module 14, over line 52, all signaling on memory buses 48, 50, respectively, pertaining to selected portions of memory (e.g., duplicated memory regions) including duplicated bits, bytes, words, longwords, records, arrays, matrices, structs, objects, data structures or other items or regions.
[0045] Switches 44, 46 comprise any hardware or software logic capable of providing coupling between the memory buses of the respective modules. In the illustrated embodiment, it provides for fast, low-power, low-noise switching over a parallel bus, directly connecting each of the conductors in the memories 18, 28 to the conductors in each of the memory buses 48, 50 to which they may be coupled. Such a switch can comprise field effect transistors (FETs) and, particularly, arrays of such switches, though other semiconductor and nonsemiconductor devices may be used instead or in addition. In alternate embodiments, the switches comprise interface logic (and, optionally, mapping logic) for transferring shared data and corresponding addresses, symbolic names, or other identifiers to/from line 52.
[0046] FIG. 2 depicts a method of operating the modules 12, 14 to effect updating of the memory 28 of the latter from memory 18 of the former. FIG. 3 illustrates operation of the modules as a consequence of execution of such a method.
[0047] In step 60, processing section 12 (e.g., Module A) engages in normal processing, i.e., with its switch 44 in its first operational mode. In step 62, processing section 14 (e.g., Module B) powers up or otherwise enters a state in which its memory 28 requires updating. See also, FIG. 3A, wherein memory 18 is shaded, indicating that it contains valid data. Conversely, memory 28 is unshaded, indicating that it contains invalid data. The double arrow between module 12 and line 34 also indicates that module transfers data with other components of the system (not shown) in the normal manner. No such arrow is shown between module 14 and bus 34.
[0048] In step 64, processor 26 of module 14 asserts X_IN, placing switch 46 in its second mode and, thereby, coupling memory 28 and bus 42 to bus 48. This has the effect of decoupling memory 28 and bus 42 from bus 50. In order to permit a transfer over line 52, process 16 asserts X_ENA. See step 66. See also FIG. 3B, wherein the arrow adjacent line 52 indicates the direction of information transfer of that bus during the update process.
[0049] Processors 16, 26 maintain assertion of X_ENA and X_IN, respectively, for a period sufficiently long to enable the diagnostic element 26 of module 12 to test all locations of memory 18. This entails, inter alia, reading and rewriting the contents of each of those locations. As a consequence of switch 46 being in its second mode, the rewritten data is stored to corresponding locations in memory 28, as well as to their locations in memory 18. See FIGS. 3C-3D, wherein memory 28 is shown as partially, then fully, shaded, depicting its filling with valid data from memory 18. The circular path shown in FIG. 3C between processor 16 and memory 18 depicts the memory testing cycle exercised by element 26.
[0050] A sequence for testing all locations of memory 18 is shown in steps 68-72. This includes marking a current location in memory 18, reading the data contained at that location and temporarily storing it (e.g., in a register or another memory location), testing the location (e.g., by writing a known bit pattern to the location and verifying that it is properly stored), writing the temporarily stored value back to the location, incrementing the location count and testing the next location. This process is repeated until the initial current location is subject to retesting.
[0051] At this time, module 12 wakes module 14. See step 74. In the illustrated embodiment, this is accomplished by having module 12 can call a routine, which causes its stack to be pushed and its register contents to be written to memories 18 and 28. In step 76, module 12 deasserts X_ENA, thereby, disabling further transfers over line 52. Module 14 likewise deasserts X_IN. See step 78. Module 12 then signals an interrupt, causing both modules 12, 14 to execute identical interrupt handling routines, which pop the stacks of the respective processors 16, 26 and place them in identical contexts, i.e., using data and status information written to the respective memories 18, 28 during the aforementioned push. The processors 16, 26 thereafter resume normal operation in identical states. See FIGS. 3D-3E, wherein arrows between module 14 and line 34 indicate that the module is in slave mode (FIG. 3D), at least listening to that bus and, subsequently, master mode (FIG. 3E), where it drives data to the bus.
[0052] Those skilled in the art will, of course, appreciate that other sequences for testing memory can be used. Likewise, module 14 need not rely on a wakeup from module 12 to begin normal operation and can instead rely, by way of non-limiting example, on a self-timed wait period. Moreover, the modules 12, 14 need not achieve identical state prior to resumption of operation by module 14.
[0053] Described above are methods and apparatus meeting the desired objects. Those skilled in the art will appreciate that the illustrated embodiment is merely an example of the invention and that other embodiments making modifications thereto may fall within the scope of the invention, of which
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
We claim:
1. A control system comprising
a first module and a second module, each forming at least part of any of a workstation, field controller, field device, smart field device, or other functionality for any of industrial, manufacturing, service, environmental, or process control,
the first module comprising a first memory element that is normally coupled to a first bus and that stores data in accord with commands received over that bus,
the second module comprising a second memory element that is normally coupled to a second bus and that stores data in accord with commands received over that bus,
diagnostic logic, coupled to at least the first bus, that issues commands causing data in at least selected storage locations in the first memory element to be periodically re-written to those storage locations via the first bus,
switching logic coupled to the first and second modules, the switching logic transmitting to the second module at least selected data on the first bus,
wherein the witching logic has a memory update mode that selectively couples the second memory element to the first bus and decouples the second memory element from the second bus during a period in which the diagnostic logic is causing data in the selected storage locations in the first memory element to be re-written to those storage locations.
2. A control system according to claim 1, wherein the switching logic comprises any of a bus, network and other communications medium.
3. A control system according to claim 1, comprising logic that converts any of an address, symbolic name or other identifier associated with data transferred between the modules.
4. A control system according to claim 1, wherein the switching logic transfers any of bits, bytes, words, longwords, records, arrays, matrices, structs, objects, data structures or other items or portions of memory between the first module and the second module.
5. A control device, comprising:
a first memory element that is normally coupled to a first bus and that stores data in accord with commands received over that bus,
a second memory element that is normally coupled to a second bus and that stores data in accord with commands received over that bus,
a switching element that is coupled to the first and second memory elements and to the first and second buses, the switching element having a mode that temporarily couples the first memory element to the second bus, while decoupling the first memory element from the first bus, and
logic coupled to at least the second bus that issues commands causing data in at least selected storage locations in the second memory element to be re-written to those storage locations.
6. The control device of claim 5, wherein said logic issues commands causing data in at least selected storage locations in the second memory element to be periodically re-written to those storage locations.
7. The control device of any of claims 5 and 6, wherein the switching element couples the first memory element to the second bus for a period sufficient to ensure that substantially all of the selected storage locations in the second memory element are re-written.
8. The control device of claim 7, wherein the switching element comprises an FET switch.
9. The control device of claim 7, wherein the switching element comprises an FET switch array.
10. The control dice of claim 9, wherein each element of the FET switch array selectively couples conductors in the second bus to respective conductors of the first memory element.
11. A control device, comprising:
a first memory element that is normally coupled to a first bus and that stores data in accord with commands received over that bus,
a second memory element that is normally coupled to a second bus and that stores data in accord with commands received over that bus,
first memory test logic coupled to at least the second bus, the first memory test logic issuing commands causing data in at least selected storage locations in the second memory element to be periodically rewritten to those storage locations,
a first switching element having a memory update mode that selectively couples the first memory element to the second bus and decouples the first memory element from the first bus, during a period in which the first memory test logic is causing data in the selected storage locations in the second memory element to be re-written to those storage locations.
12. A control device according to claim 11, comprising
second memory test logic coupled to at least the first bus, the second memory test logic issuing commands causing data in at least selected storage locations in the first memory element to be periodically re-written to those storage locations,
a second switching element having a memory update mode that selectively couples the second memory element to the first bus and decouples the second memory element from the second bus, during a period in which the second memory test logic is causing data in the selected storage locations in the first memory element to be re-written to those storage locations.
13. A control device according to claim 12, wherein the first and second switching elements are not concurrently in their respective memory update modes.
14. The control device of claim 11, wherein at least one of the switching elements comprises an FET switch.
15. The control device of claim 11, wherein at least one of the switching elements comprises an FET switch array.
16. The control device of claim 15, wherein each element of the FET switch array couples conductors in the first and second buses to respective conductors of a respective one of the memory elements.
17. A control device, comprising:
a first module and a second module operating with at least loose coupling,
the first module comprising
a first processor that is coupled to a first bus,
a first memory element that stores data in accord with commands received over a bus to which it is coupled,
the first processor having a memory test mode wherein it issues issuing commands causing data in at least selected storage locations in the first memory element to be periodically re-written to those storage locations,
the second module comprising
a second processor that is coupled to a second memory element by a second bus,
a second memory element that stores data in accord with commands received over a bus to which it is coupled,
a switching element that is coupled to the first and second buses and the second memory element, the switching element having a conventional operation mode that couples the second bus to the second memory element, and that has a memory update mode that couples the first bus to the second memory element,
logic that changes the first switching element from the conventional operation mode to the memory update during a period in which the first processor is in the memory test mode.
18. A control device, comprising:
a first module and a second module operating with at least loose coupling,
the first module comprising
a first processor that is coupled to a first bus,
a first memory element that stores data in accord with commands received over a bus to which it is coupled,
the second module comprising
a second processor that is coupled to a second bus,
a second memory element that stores data in accord with commands received over a bus to which it is coupled,
the first and second processor each having a memory test mode wherein they issue commands causing data in at least selected storage locations in the respective memory element to be periodically re-written to those storage locations,
a first switching element that is coupled to the first and second buses and the second memory element, the switching element having a conventional operation mode that couples the second bus to the second memory element, and that has a memory update mode that couples the first bus to the second memory element,
a second switching element that is coupled to the second and first buses and the first memory element, the switching element having a conventional operation mode that couples the first bus to the first memory element, and that has a memory update mode that couples the second bus to the first memory element,
logic that changes a selected one of the first and second switching elements from the conventional operation mode to the memory update during a period in which the second and first processors, respectively, is in the memory test mode.
19. The control device of any of claims 17 and 18, wherein at least one of the switching elements comprises an FET switch array.
20. The control device of claim 19, wherein each element of the FET switch array couples conductors in the first and second buses to respective conductors of a respective one of the memory elements.
21. A method of operating a control device, comprising the steps of:
storing data in a first memory element in accord with commands received over a first bus,
storing data in a second memory element in accord with commands received over a second bus,
temporarily coupling both the first memory element and the second memory element to the second bus so that both memory elements store data in accord with commands received over the second bus,
issuing commands on the second bus that cause data in at least selected storage locations in the second memory element to be re-written to those storage locations.
22. The method of claim 21, wherein the step of issuing commands comprises issuing commands on at least the second bus that cause data in at least selected storage locations in the second memory element to be periodically re-written to those storage locations.
23. The method of any of claims 21 and 22, comprising the step of coupling both the first and second memory elements to the second bus for a period sufficient to ensure that substantially all of the selected storage locations in the second memory element are re-written.
24. The method of claim 23, comprising the step of coupling the first memory element to the second bus with an FET switch.
25. The method of claim 23, comprising the step of coupling the first memory element to the second bus with an FET switch array.
26. The method of claim 25, comprising the step of coupling conductors in the second buses to respective conductors of the first memory element wit respective elements of the FET switch array.
27. A method of operating a control device, comprising the steps of:
storing data in a first memory element in accord with commands that are normally received over a first bus,
storing data in a second memory element in accord with commands that are normally received over a second bus,
issuing commands on the second bus causing data in at least selected storage locations in the second memory element to be periodically re-written to those storage locations,
selectively coupling both the first memory element and the second memory element to the second bus and concurrently decoupling the first memory element from the first bus during a period in which the commands are issued on the second bus causing data to be re-written.
28. A method of operating a control device according to claim 27, comprising the steps of
issuing commands on the first bus causing data in at least selected storage locations in the first memory element to be periodically re-written to those storage locations,
in lieu of selectively coupling both the first memory element and the second memory element to the second bus, selectively coupling both the first memory element and the second memory element to the first bus and concurrently decoupling the second memory element from the second bus during a period in which the commands are issued on the first bus causing data to be re-written.
29. The method of claim 28, wherein each element of the FET switch array couples conductors in the first and second buses to respective conductors of a respective one of the memory elements.
Patent Citations (193)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3810119(A) | 1974-05-01 | Zieve et al. | Applicant |
| US3825905(A) | 1974-07-01 | Allen, Jr. | Applicant |
| US4096566(A) | 1978-06-01 | Borie et al. | Applicant |
| US4276593(A) | 1981-06-01 | Hansen | Applicant |
| US4302820(A) | 1981-11-01 | Struger et al. | Applicant |
| US4312068(A) | 1982-01-01 | Goss et al. | Applicant |
| US4323966(A) | 1982-04-01 | Whiteside et al. | Applicant |
| US4347563(A) | 1982-08-01 | Paredes et al. | Applicant |
| US4410942(A) | 1983-10-01 | Milligan et al. | Applicant |
| US4423486(A) | 1983-12-01 | Berner | Applicant |
| US4428044(A) | 1984-01-01 | Liron | Applicant |
| US4435762(A) | 1984-03-01 | Milligan et al. | Applicant |
| US4456997(A) | 1984-06-01 | Spitza | Applicant |
| US4466098(A) | 1984-08-01 | Southard | Applicant |
| US4471457(A) | 1984-09-01 | Videki, II | Applicant |
| US4488226(A) | 1984-12-01 | Wagner, Jr. et al. | Applicant |
| US4493027(A) | 1985-01-01 | Katz et al. | Applicant |
| US4609995(A) | 1986-09-01 | Hasebe | Applicant |
| US4615001(A) | 1986-09-01 | Hudgins, Jr. | Applicant |
| US4628437(A) | 1986-12-01 | Poschmann et al. | Applicant |
| US4641276(A) | 1987-02-01 | Dunki-Jacobs | Applicant |
| US4648064(A) | 1987-03-01 | Morley | Applicant |
| US4649479(A) | 1987-03-01 | Advani et al. | Applicant |
| US4654819(A) | 1987-03-01 | Stiffler et al. | Examiner |
| US4663704(A) | 1987-05-01 | Jones et al. | Applicant |
| US4672530(A) | 1987-06-01 | Schuss | Applicant |
| US4675812(A) | 1987-06-01 | Capowski et al. | Applicant |
| US4682304(A) | 1987-07-01 | Tierney | Applicant |
| US4683530(A) | 1987-07-01 | Quatse | Applicant |
| US4692859(A) | 1987-09-01 | Ott | Applicant |
| US4692918(A) | 1987-09-01 | Elliott et al. | Applicant |
| US4703421(A) | 1987-10-01 | Abrant et al. | Applicant |
| US4709325(A) | 1987-11-01 | Yajima | Applicant |
| US4719593(A) | 1988-01-01 | Threewitt et al. | Applicant |
| US4727477(A) | 1988-02-01 | Gavril | Applicant |
| US4733366(A) | 1988-03-01 | Deyesso et al. | Applicant |
| US4742349(A) | 1988-05-01 | Miesterfeld et al. | Applicant |
| US4750109(A) | 1988-06-01 | Kita | Applicant |
| US4790762(A) | 1988-12-01 | Harms et al. | Applicant |
| US4805107(A) | 1989-02-01 | Kieckhafer et al. | Applicant |
| US4816996(A) | 1989-03-01 | Hill et al. | Applicant |
| US4817094(A) | 1989-03-01 | Lebizay et al. | Applicant |
| US4872106(A) | 1989-10-01 | Slater | Applicant |
| US4910658(A) | 1990-03-01 | Dudash et al. | Applicant |
| US4910691(A) | 1990-03-01 | Skeirik | Applicant |
| US4958277(A) | 1990-09-01 | Hill et al. | Applicant |
| US4959774(A) | 1990-09-01 | Davis | Applicant |
| US4965717(A) | 1990-10-01 | Cutts, Jr. et al. | Applicant |
| US4965742(A) | 1990-10-01 | Skeirik | Applicant |
| US4965880(A) | 1990-10-01 | Petitjean | Applicant |
| US4991170(A) | 1991-02-01 | Kem | Applicant |
| US5008805(A) | 1991-04-01 | Fiebig et al. | Applicant |
| US5050165(A) | 1991-09-01 | Yoshioka et al. | Applicant |
| US5068778(A) | 1991-11-01 | Kosem et al. | Applicant |
| US5129087(A) | 1992-07-01 | Will | Applicant |
| US5134574(A) | 1992-07-01 | Beaverstock et al. | Applicant |
| US5136704(A) | 1992-08-01 | Danielsen et al. | Applicant |
| US5138708(A) | 1992-08-01 | Vosbury | Applicant |
| US5146589(A) | 1992-09-01 | Peet, Jr. et al. | Applicant |
| US5151981(A) | 1992-09-01 | Westcott et al. | Applicant |
| US5162986(A) | 1992-11-01 | Graber et al. | Applicant |
| US5163055(A) | 1992-11-01 | Lee et al. | Applicant |
| US5166685(A) | 1992-11-01 | Campbell, Jr. et al. | Applicant |
| US5168276(A) | 1992-12-01 | Huston et al. | Applicant |
| US5175829(A) | 1992-12-01 | Stumpf et al. | Applicant |
| US5193175(A) | 1993-03-01 | Cutts, Jr. et al. | Applicant |
| US5212784(A) | 1993-05-01 | Sparks | Applicant |
| US5216672(A) | 1993-06-01 | Tatosian et al. | Examiner |
| US5233615(A) | 1993-08-01 | Goetz | Applicant |
| US5255367(A) | 1993-10-01 | Bruckert et al. | Applicant |
| US5258999(A) | 1993-11-01 | Wernimont et al. | Applicant |
| US5271013(A) | 1993-12-01 | Gleeson | Applicant |
| US5274648(A) | 1993-12-01 | Eikill et al. | Applicant |
| US5283729(A) | 1994-02-01 | Lloyd | Applicant |
| US5289365(A) | 1994-02-01 | Caldwell et al. | Applicant |
| US5295258(A) | 1994-03-01 | Jewett et al. | Applicant |
| US5302952(A) | 1994-04-01 | Campbell, Jr. et al. | Applicant |
| US5303227(A) | 1994-04-01 | Herold et al. | Applicant |
| US5303375(A) | 1994-04-01 | Collins et al. | Applicant |
| US5303392(A) | 1994-04-01 | Carney et al. | Applicant |
| US5307372(A) | 1994-04-01 | Sawyer et al. | Applicant |
| US5317726(A) | 1994-05-01 | Horst | Applicant |
| US5335221(A) | 1994-08-01 | Snowbarger et al. | Applicant |
| US5347181(A) | 1994-09-01 | Ashby et al. | Applicant |
| US5349343(A) | 1994-09-01 | Oliver | Applicant |
| US5352033(A) | 1994-10-01 | Gresham et al. | Applicant |
| US5359721(A) | 1994-10-01 | Kempf et al. | Applicant |
| US5381529(A) | 1995-01-01 | Matsushima | Applicant |
| US5390321(A) | 1995-02-01 | Proesel | Applicant |
| US5398331(A) | 1995-03-01 | Huang et al. | Applicant |
| US5400140(A) | 1995-03-01 | Johnston | Applicant |
| US5410717(A) | 1995-04-01 | Floro | Applicant |
| US5428781(A) | 1995-06-01 | Duault et al. | Applicant |
| US5434997(A) | 1995-07-01 | Laundry et al. | Applicant |
| US5444851(A) | 1995-08-01 | Woest | Applicant |
| US5450403(A) | 1995-09-01 | Ichii et al. | Applicant |
| US5450425(A) | 1995-09-01 | Gunn et al. | Applicant |
| US5450764(A) | 1995-09-01 | Johnston | Applicant |
| US5451939(A) | 1995-09-01 | Price | Applicant |
| US5457797(A) | 1995-10-01 | Butterworth et al. | Applicant |
| US5459839(A) | 1995-10-01 | Swarts et al. | Applicant |
| US5463735(A) | 1995-10-01 | Pascucci et al. | Applicant |
| US5475856(A) | 1995-12-01 | Kogge | Applicant |
| US5481125(A) | 1996-01-01 | Harris | Examiner |
| US5481741(A) | 1996-01-01 | McKaskle et al. | Applicant |
| US5483660(A) | 1996-01-01 | Yishay et al. | Applicant |
| US5485620(A) | 1996-01-01 | Sadre et al. | Applicant |
| US5504902(A) | 1996-04-01 | McGrath et al. | Applicant |
| US5509811(A) | 1996-04-01 | Homic | Applicant |
| US5513095(A) | 1996-04-01 | Pajonk | Applicant |
| US5513192(A) | 1996-04-01 | Janku et al. | Applicant |
| US5513354(A) | 1996-04-01 | Dwork et al. | Applicant |
| US5517655(A) | 1996-05-01 | Collins et al. | Applicant |
| US5519701(A) | 1996-05-01 | Colmant et al. | Applicant |
| US5522044(A) | 1996-05-01 | Pascucci et al. | Applicant |
| US5530643(A) | 1996-06-01 | Hodorowski | Applicant |
| US5539909(A) | 1996-07-01 | Tanaka et al. | Applicant |
| US5544008(A) | 1996-08-01 | Dimmick et al. | Applicant |
| US5550980(A) | 1996-08-01 | Pascucci et al. | Applicant |
| US5551047(A) | 1996-08-01 | Mori et al. | Applicant |
| US5555213(A) | 1996-09-01 | DeLong | Applicant |
| US5555437(A) | 1996-09-01 | Packer | Applicant |
| US5555510(A) | 1996-09-01 | Verseput et al. | Applicant |
| US5559963(A) | 1996-09-01 | Gregg et al. | Applicant |
| US5568378(A) | 1996-10-01 | Wojsznis | Applicant |
| US5572673(A) | 1996-11-01 | Shurts | Applicant |
| US5576946(A) | 1996-11-01 | Bender et al. | Applicant |
| US5579220(A) | 1996-11-01 | Barthel et al. | Applicant |
| US5579487(A) | 1996-11-01 | Meyerson et al. | Applicant |
| US5581760(A) | 1996-12-01 | Atkinson et al. | Applicant |
| US5586112(A) | 1996-12-01 | Tabata | Applicant |
| US5586329(A) | 1996-12-01 | Knudsen et al. | Applicant |
| US5586330(A) | 1996-12-01 | Knudsen et al. | Applicant |
| US5587899(A) | 1996-12-01 | Ho et al. | Applicant |
| US5594899(A) | 1997-01-01 | Knudsen et al. | Applicant |
| US5596752(A) | 1997-01-01 | Knudsen et al. | Applicant |
| US5600845(A) | 1997-02-01 | Gilson | Applicant |
| US5604871(A) | 1997-02-01 | Pecone | Applicant |
| US5611057(A) | 1997-03-01 | Pecone et al. | Applicant |
| US5613148(A) | 1997-03-01 | Bezviner et al. | Applicant |
| US5617540(A) | 1997-04-01 | Civanlar et al. | Applicant |
| US5627979(A) | 1997-05-01 | Chang et al. | Applicant |
| US5629949(A) | 1997-05-01 | Zook | Applicant |
| US5630056(A) | 1997-05-01 | Horvath et al. | Applicant |
| US5630152(A) | 1997-05-01 | DeLuca et al. | Applicant |
| US5642511(A) | 1997-06-01 | Chow et al. | Applicant |
| US5649121(A) | 1997-07-01 | Budman et al. | Applicant |
| US5655092(A) | 1997-08-01 | Ojala | Applicant |
| US5659680(A) | 1997-08-01 | Cunningham et al. | Applicant |
| US5664168(A) | 1997-09-01 | Yishay et al. | Applicant |
| US5671374(A) | 1997-09-01 | Postman et al. | Applicant |
| US5676141(A) | 1997-10-01 | Hollub | Applicant |
| US5680404(A) | 1997-10-01 | Gray | Applicant |
| US5680409(A) | 1997-10-01 | Qin et al. | Applicant |
| US5682476(A) | 1997-10-01 | Tapperson et al. | Applicant |
| US5687316(A) | 1997-11-01 | Graziano et al. | Applicant |
| US5701414(A) | 1997-12-01 | Cheng et al. | Applicant |
| US5708779(A) | 1998-01-01 | Graziano et al. | Applicant |
| US5727128(A) | 1998-03-01 | Morrison | Applicant |
| US5748467(A) | 1998-05-01 | Qin et al. | Applicant |
| US5751574(A) | 1998-05-01 | Loebig | Applicant |
| US5752007(A) | 1998-05-01 | Morrison | Applicant |
| US5752008(A) | 1998-05-01 | Bowling | Applicant |
| US5758073(A) | 1998-05-01 | Liang et al. | Applicant |
| US5758075(A) | 1998-05-01 | Graziano et al. | Applicant |
| US5761518(A) | 1998-06-01 | Boehling et al. | Applicant |
| US5768119(A) | 1998-06-01 | Havekost et al. | Applicant |
| US5777874(A) | 1998-07-01 | Flood et al. | Applicant |
| US5790791(A) | 1998-08-01 | Chong et al. | Applicant |
| US5793963(A) | 1998-08-01 | Tapperson et al. | Applicant |
| US5794071(A) | 1998-08-01 | Watanabe et al. | Applicant |
| US5796602(A) | 1998-08-01 | Wellan et al. | Applicant |
| US5797038(A) | 1998-08-01 | Crawford et al. | Applicant |
| US5801942(A) | 1998-09-01 | Nixon et al. | Applicant |
| US5805922(A) | 1998-09-01 | Sim et al. | Applicant |
| US5822220(A) | 1998-10-01 | Baines | Applicant |
| US5828851(A) | 1998-10-01 | Nixon et al. | Applicant |
| US5835704(A) | 1998-11-01 | Li et al. | Applicant |
| US5841963(A) | 1998-11-01 | Nakamikawa et al. | Applicant |
| US5854944(A) | 1998-12-01 | Catherwood et al. | Applicant |
| US5862052(A) | 1999-01-01 | Nixon et al. | Applicant |
| US5872992(A) | 1999-02-01 | Tietjen et al. | Applicant |
| US5873089(A) | 1999-02-01 | Regache | Applicant |
| US5909586(A) | 1999-06-01 | Anderson | Applicant |
| US5974497(A) | 1999-10-01 | Teshome | Applicant |
| US6018778(A) | 2000-01-01 | Stolowitz | Applicant |
| US6119244(A) | 2000-09-01 | Schoenthal et al. | Examiner |
| US6173377(B1) | 2001-01-01 | Yanai et al. | Examiner |
| US6240526(B1) | 2001-05-01 | Petivan et al. | Examiner |
| US6263452(B1) | 2001-07-01 | Jewett et al. | Examiner |
| US6389564(B1) | 2002-05-01 | Lu | Examiner |
| US6484271(B1) | 2002-11-01 | Gray | Examiner |
| US6487561(B1) | 2002-11-01 | Ofek et al. | Examiner |
Non-Patent Literature (96)
- Stevens, et al. “TCP/IP Illustrated, vol. 1. The Protocols,” TCP/IP Illustrated vol. 1, XP-002106390, pp. 85-96.Applicant
- ICCard Design Sep./Oct. 1995.Applicant
- Strack, Bob. “The Hawk is Soaring,” Chemical Processing (May 1996) p. 11.Applicant
- “Control System Features Plug-and-Play Technology, Scalability,” Chemical Processing (May 1996), p. 33.Applicant
- “Editors' Product Picks,” Chemical Processing (May 1996), p. 34.Applicant
- “Agenda,” ISA/SP50—1988-180, ISA Draft.Applicant
- Application of PRIAM Model to Safety Systems on Offshore Oil/Gas Platforms. Silvertech Ltd., Jan. 9, 1995.Applicant
- “Automation System Monitors, Controls Fab HVAC, Other Systems,” Microcontamination (Aug. 1994).Applicant
- Batch Control. Part I: Models and Terminology. (Approved Feb. 28, 1995) ISA-S88.01 1995.Applicant
- Benkhallat, Yazid, et al. “Interoperability of sensors and distributed systems,” Sensors and Actuators A vol. 37-38 (1993), 247-254.Applicant
- Blevins, Terry. “Characteristics of Function Block Requirements for the Process Industry and Manufacturing Automation,” Fisher-Rosemount, Oct. 31, 1995.Applicant
- Brunn, P. “Collision Avoidance for Two Robots Sharing a Common Workspace,” (1995) The Institution of Electrical Engineers.Applicant
- Burton, P. I. “A personal history of batch control,” Measurement + Control vol. 27 (Apr. 1994), pp. 69-73.Applicant
- Burton, P. I., et al. “Field Bus Based on MIL-STD-1553B: Proposal to ISA-SP-50” ERA Technology Ltd. (Apr. 6, 1988) ISA/SP50-1988-148.Applicant
- Capetta, L., et al. “From Current Actuators and Transmitters Towards Intelligent Actuation and Measurement: PRIAM Approach,” BIAS 93.Applicant
- Caro, Richard H. “Field Bus Applications,” ISA (1989) Paper #89-0569, pp. 989-994.Applicant
- Caro, Richard H. “The Fifth Generation Process Control Architecture,” ISA (1988) Paper #88-1487, pp. 659-667.Applicant
- Caro, Richard H. “The Fifth Generation Process Control Architecture,” ISA Transactions vol. 28 No. 4 (1989), pp. 23-28.Applicant
- Chettle, Tim. “Multiplexing techniques optimise data collection,” Electrotechnology (Oct./Nov. 1995).Applicant
- Coleman, Vernon. “National Electrical Manufactures Assoication Field Bus Report to ISA SP50,” (Oct. 1988) ISA/SP50-1988-234.Applicant
- Conference Record of the 1993 IEEE Industry Applications Conference, Part III (excerpt).Applicant
- Contents, Proceedings of the Second International Workshop on Configurable Distrubuted Systems, Mar. 21-23, 1994, Pittsburgh, PA.Applicant
- Craig, Lynn W. “SP-88 Defines Batch Control,” INTECH Mar. 1994, pp. 34-37.Applicant
- Crowder, R. S. “A Communication Architecture for Automation & Control,” ISA, pp. 669-673.Applicant
- Crowder, R. S.. “Generic Data Link Transactions for Simple Devices,” Proposal to ISA SP 50 & IEC/SC65C/WG6 (Oct. 15, 1988) ISA Document.Applicant
- Delahostria. Communication Model Application Layer. (Oct. 14, 1988) ISA/SP50-1988 247, ISA Draft.Applicant
- Delfino, B. and Pinceti, P. “Fieldbus Applications for Electrical Industrial Systems,” IEEE (1993), pp. 2084-2090.Applicant
- Dezso, Danyi. “Halozati szabalyozas,” Meres es Automatika vol. 37 (1989), pp. 208-213.Applicant
- Editing Committee Draft Application Layer, Version 6, Dec. 1990.Applicant
- Editing Committee Draft Application Layer, Version 8, May 1991.Applicant
- Editing Committee Draft Application Layer, Version 12, Oct. 1991.Applicant
- Esprit Project 6188, “PRIAM Dictionary: Major Terms and Definitions Used in the PRIAM Project,” Prenormative Requirements for Intelligent Actuation and Measurement, May 1995.Applicant
- Esprit Project 8244, “User Requirements for Intelligent Transmitter and Actuators,” European Intelligent Actuation and Measurement User Group, Nov. 24, 1995.Applicant
- Fieldbus Standard for Use in Industrial Control Systems. Part 2: Physical Layer Specification and Service Definition. (1992) ANSI/ISA/S50.02.Applicant
- Foxboro Fieldbus Proposal (Presented to ISA SP-50 Committee Feb. 24, 1988) ISA/SP50-1988-123B, ISA Draft.Applicant
- Furness, Harry. “Fieldbus: The Differences Start From the Bottom Up,” Control Engineering (Mar. 1994), pp. 75-77.Applicant
- Holding, David and Wood, Graham. “Communications in microprocessor industrial implementation,” Microprocessors and Microsystems vol. 3 No. 10 (Dec. 1979), pp. 443-451.Applicant
- Johnson, Dick. “Prepare Sensing Advances: Are They in our Process'Future?” Control Engineering (Apr. 1995), pp. 67-72.Applicant
- Kelly, D. Mark. “Digital fieldbus cluster cuts plant's wiring costs up to 20%,” INTECH (Apr. 1995), pp. 62-64.Applicant
- Koth, H. and Oeder, K. “The Advantages of Intelligent Field Modules for Nuclear Power Plant Operation and Maintenance,” Kerntechnik 60 (1996) 5-6, pp. 215-219.Applicant
- Lenhart, Gerald W. “A Field Bus Approach to Local Control Networks,” ISA, Paper #93-281 (1993).Applicant
- Lenhart, Gerald W. “Fieldbus-Based Local Control Networks,” INTECH (Aug. 1994), p. 31-34.Applicant
- Loose, Graham. “Fieldbus—the user's perspective,” Measurement + Control vol. 27 (Mar. 1994), pp. 47-51.Applicant
- Meeting Minutes, SP50, International Electrotechnical Commission, Technical Committee No. 65: Industiral-Process Measurement and Control, Sub-Committee 65C: Digital Data Communications for Measurement and Control and Working Group 6: Field Bus Standard for Use in Industrial Control Systems, Feb. 28-Mar. 4, 1988, Scottsdale, AZ.Applicant
- Meeting Minutes, SP50.4 Application Layer, Oct. 19-21, 1988, Houston, TX.Applicant
- Meeting Minutes, Windows Working Group of Application Subcommittee, Mar. 1-3, 1989, New Orleans, LA.Applicant
- Meeting Minutes Ad Hoc Function Block Meeting, Jun. 14, 1990, Chapel Hill, NC.Applicant
- Meeting Minutes, SP50, Signal Compatibility of Electrical Instruments, Dec. 5-7, 1990, Orlando, FL.Applicant
- Meeting Minutes, Process Control Working Group of SP50.4, Jan. 21-23, 1991, Atlanta, GA.Applicant
- Meeting Notes, International Electrotechnical Commission Sub Committee No. 65C: Digital Communications Working Group 7, Process Control Function Blocks Report to AMT/7. Apr. 4, 1996.Applicant
- Mirabella, Orazio. “A Short Presentation of IEC Fieldbus Application Layer,” Informatics and Communication Institute, Engineering Faculty, University of Catania, Italy.Applicant
- Morel, G., et al. “Discrete Event Automation Engineering: Outline of the PRIAM Project”.Applicant
- “NCR Fieldbus Slave Controller Advance Information,” ISA-SP50-1988-161, ISA Draft.Applicant
- NOAH: Network Oriented Application Harmonisation based on General Purpose Field Communication System. Project description rev. 1.0, Oct. 25, 1995. P-NET, PROFIBUS, WorldFIP.Applicant
- Nobuhiko, Tsuji, et al. “An Advanced Optical Fieldbus Instrumentation System Using 16 x 16 Reflection Type Optical Star Coupler and Low Powered Transmitter,” pp. 755-764.Applicant
- Output to Valve, Revision No. 1.4, Jan. 18, 1991, (Draft Document), Instrument Society of America.Applicant
- Owen, S., et al. “A modular reconfigurable approach to the reation of flexible manufacturing cells for education purposes,” Fast Reconfiguraciton of Robotic and Automation Resources (Colloquium) Oct. 20, 1995, The Institution of Electrical Engineers, Digest No. 95/174.Applicant
- Pace, Hugh W. “Valve Actuators Ready for Fieldbus,” Control Engineer (Oct. 1995), pp. 65-73.Applicant
- Petti, Thomas F. and Dhurjati, Prasad S. “A Coupled Knowledge Based System Using Fuzzy Optimization for Advisory Control,” IChE Journal vol. 38 (Sep. 1992) No. 9, pp. 1369-1378.Applicant
- Pfeifer T. and Fussel B. “Sensorbetribssystem fur messtechnische Problemstellungen in der Produktionstechnik,” Technisches Messen vol. 58 (1991) Nos. 7/8.Applicant
- Phinnery, Thomas L. “An Analysis of Contending Proposals in ISA SP-50 for an ISA/IEC Field Instrument Bus,” ISA (1988) Paper #88-1489.Applicant
- Preface: Field Bus Process Control User Layer Technical Support, Feb. 10, 1993.Applicant
- Product Specification, I/A Series ® RBATCH II.Applicant
- Proway-LAN Industrial Data Highway. (Approved Feb. 3, 1986) ISA-S72.01-1985.Applicant
- Report from IEC TC65 Working Group 6 Function Blocks, May 1, 1995.Applicant
- Schuur, C. “Comments on ‘Analysis and Suggestions for ISA-SP50’ as submitted to the SP50 Committee by Honeywell Inc.” (Mar. 11, 1988) ISA-SP50-1988-155, ISA Draft.Applicant
- Schuur, Chris and Warrior, Jay. “Philips Token Passing Field Bus Controller Timed Token Mode,” ISA/SP50—1988-186, ISA Draft.Applicant
- “SDRD Using 1553B Data Link Services,” ISA/SP50-1988-243 (1988).Applicant
- Skabowski, E. L. “Recommendations for Consideration at October, 1988 Application Layer Subcommittee Meeting,” (Oct. 3, 1986).Applicant
- Solvie, Michael J. “Configuration of Distributed Time-Critical Fieldbus Systems,” IEEE (1994), p. 211.Applicant
- Strothman, Jim and Ham, John. “Alliances, Fieldbus, Windows Stir ISA/94 Anaheim Pot,” INTECH (Dec. 1994), pp. 32-35.Applicant
- Strothman, Jim and Ham, John. “ISA/95 New Orleans: ‘Open’, NT winds (not Opal) blow strong,” INTECH (Nov. 1995), pp. 45-48.Applicant
- “Suggested Outline for Application Sub-committee Document: Fieldbus Architecture Subcommittee Document,” ISA/SP50-1988-175, ISA Draft.Applicant
- Table of Contents, Automation & Technology Department, 1995.Applicant
- Table of Contents, Automation & Technology Department, 1993.Applicant
- Table of Contents, Industrial Computing Society (no date).Applicant
- Table of Contents, Proceedings of the Industrial Computing Conference, vol. 3, Sep. 19-24, 1993, Chicago, IL. Industrial Computing Society.Applicant
- [Table of Contents], Proceedings of the 20th International Conference on Industrial Electronics Control and Instrumentation, vols. 1-3, Sep. 5-9, 1994, Bologna, Italy.Applicant
- [Table of Contents], Proceedings of the 7th Mediterranean Electrotechnical Conference, vol. 1, Apr. 12-14, 1994, Antalya, Turkey.Applicant
- Table of Contents, ISA/88, Houston, MA, (no date).Applicant
- Table of Contents, ISA/89, (no date).Applicant
- Tobin, David. “Southeast Paper Installs Largest Foxboro Distributed Control System.”Applicant
- “User Layer Structure,” SP-50 Technical Report (Jul. 25, 1990).Applicant
- “User Layer Technical Report,” ISA/SP50—1990-389C, ISA Draft.Applicant
- Weinert, A., et al. “RT/OS—a realtime programming and application environment for the COSY control system,” Nuclear Instruments and Methods in Physics Research A vol. 352 (1994), pp. 277-279.Applicant
- WG1 List of Criteria (Appendix 1), (Oct. 21, 1988) ISA/SP50-1988-242, ISA Draft.Applicant
- Wood, G. G. “The Argus CONSUL System for On-Line Computer Control,” Electrical Engineering Transactions (Mar. 1969), pp. 114-118.Applicant
- Wood, G. G. “The Challenge of Standards for Plant Communication,” IFAC Distributed Computer Control Systems, (1982), pp. 191-192.Applicant
- Wood, G. G. “Current Fieldbus activities,” computer communications vol. 11 (Jun. 1988) No. 3, pp. 118-123.Applicant
- Wood, Graeme G. “Data Transmission, Processing and Presentation,” pp. 46-54.Applicant
- Wood, G. G. “Evolution of communication standards for the process industry,” Measurement + Control vol. 19 (Jul./Aug. 1986), pp. 183-188.Applicant
- Wood, Graeme. “Fieldbus Status 1995,” Computing & Control Engineering Journal (Dec. 1995), pp. 251-253.Applicant
- Wood, Graeme. “Generic Link Transactions for Simple Devices in Fieldbus.” ISA/SP50—1988—240 (Sep. 20, 1988).Applicant
- Wood, Graeme, G. “Standardisation Work for Communication Among Distributed Industrial Computer Control Systems—A Status Report,” INRIA (1984), pp. 67-69.Applicant
- Wood, G. G. “Survey of LANs and Standards,” Computer Standards & Interfaces vol. 6, (1987), pp. 27-36.Applicant
- Wood, G. G. “Towards digital information control,” Measurement + Control vol. 21 (Jul./Aug. 1988), pp. 179-180.Applicant