← Back to Patent Explorer
US5261092A Expired / Lapsed US ⏱️ 0.0 years remaining

Synchronizing slave processors through eavesdrop by one on periodic sync-verify messages directed to another followed by comparison of individual status

Assignee: Honeywell Inc
•
Filing: 1990-09-26
•
Granted: 1993-11-09
•
Expires: 2010-09-26
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract Data bases of a first and second input output processor (IOP), which are primary and secondary slave IOPs, respectively, are synchronized, and communications by a master controller is made only to the first IOP. Each IOP is executing the same tasks utilizing their own clocking systems. A method for periodically verifying that the first and second data base remain synchronized comprises the steps of sending a sync-verify type message to the first IOP. The second IOP eavesdrops on the communications, and when the second IOP recognizes that the message is addressed to the corresponding primary slave IOP, accepts the message. Upon detecting the message is of the sync-verify type by each IOP, operations by each IOP are suspended. A number is generated by each IOP of its own data base, the number being indicative of the contents of the information stored in the data base. A status request type message is issued by the master controller to the first IOP for the number generated by the first IOP, and a status request type message is issued by the master controller to the second IOP for the number generated by the second IOP. Upon receipt of the numbers by the master controller, the value of the number generated by the first IOP is compared to the value of the number generated by the second IOP, thereby determining that the information stored in the first and second data bases are the same when the numbers compare.

Inventors

  • 👤 Paul F. McLaughlin
  • 👤 Robert W. Bristow

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-10-30 01:57
CPC Classifications
G; G06; G06F; G06F11/00; G06F11/07; G06F11/16; G06F11/1658; G06F11/1675; G06F11/1683; G06F11/1687; G06F11/20; G06F11/2097; G05; G05B; G05B2219/00; G05B2219/30; G05B2219/31; G05B2219/31324; G06F11/1629; G06F11/1641; G06F11/202; G06F11/2038

Claims Analysis

Total Claims: 8
Claim 1
Independent Claim 333 words
In a process control system, having a master controller and at least one pair of slave input/output processors (IOPs), wherein a first IOP of the pair is a primary slave IOP, and a second IOP of the pair is a secondary slave IOP, the first and second IOP having a first and second data base, respectively, the first and second IOP each executing the same tasks utilizing a first and second clocking system, respectively, and further wherein the data bases of the first and second IOPs are synchronized, communications by the master controller being made only to the first IOP including communications which modify the first data base, a method for periodically verifying that the data bases of each IOP remain synchronized, comprising the steps of: a) on a periodic basis, sending a sync-verify type message to the first IOP by the master controller; b) eavesdropping on the communications of step (a) by the second IOP; c) when the second IOP recognizes that the message of step (a) is addressed to the corresponding primary slave IOP, accepting the message by the second IOP; d) upon detecting the message is of the sync-verify type by each said IOP, suspending operations by each IOP; e) generating a number by each said IOP of its own data base, the number being indicative of the contents of the information stored in the data base; f) issuing a status request type message by the master controller to the first IOP for the number generated by the first IOP; g) issuing a status request type message by the master controller to the second IOP for the number generated by the second IOP; and h) upon receipt of the numbers by the master controller, comparing the value of the number generated by the first IOP to the value of the number generated by the second IOP, in order to provide an indication that the information stored in the first and second data bases are the same when the numbers compare.
Claim 2
Dependent Claim 333 words
In a process control system, having a master controller and at least one pair of slave input/output processors (IOPs), wherein a first IOP of the pair is a primary slave IOP, and a second IOP of the pair is a secondary slave IOP, the first and second IOP having a first and second data base, respectively, the first and second IOP each executing the same tasks utilizing a first and second clocking system, respectively, and further wherein the data bases of the first and second IOPs are synchronized, communications by the master controller being made only to the first IOP including communications which modify the first data base, a method for periodically verifying that the data bases of each IOP remain synchronized, comprising the steps of: a) on a periodic basis, sending a sync-verify type message to the first IOP by the master controller; b) eavesdropping on the communications of step (a) by the second IOP; c) when the second IOP recognizes that the message of step (a) is addressed to the corresponding primary slave IOP, accepting the message by the second IOP; d) upon detecting the message is of the sync-verify type by each said IOP, suspending operations by each IOP; e) generating a number by each said IOP of its own data base, the number being indicative of the contents of the information stored in the data base; f) issuing a status request type message by the master controller to the first IOP for the number generated by the first IOP; g) issuing a status request type message by the master controller to the second IOP for the number generated by the second IOP; and h) upon receipt of the numbers by the master controller, comparing the value of the number generated by the first IOP to the value of the number generated by the second IOP, in order to provide an indication that the information stored in the first and second data bases are the same when the numbers compare.
Claim 3
Dependent Claim 68 words
A method for periodically verifying that the data bases of each said IOP remains synchronized according to claim 1, wherein the step of sending a sync-verify type message to the first IOP by the master controller further comprising the steps of: a) receiving the message by the first IOP; and b) upon detecting the destination address is for the first IOP, accepting the message by the first IOP.
Claim 4
Dependent Claim 48 words
A method for periodically verifying that the data bases of each said IOP remains synchronized according to claim 2, wherein the step of accepting the message by the first IOP includes the step of: storing the message in a write buffer of the first IOP for subsequent processing.
Claim 5
Dependent Claim 48 words
A method for periodically verifying that the data bases of each said IOP remains synchronized according to claim 3, wherein the step of accepting the message by the second IOP includes the step of: storing the message in a write buffer of the second IOP for subsequent processing.
Claim 6
Dependent Claim 41 words
A method for periodically verifying that the data bases of each said IOP remain synchronized according to claim 4, wherein the step of issuing a status request type message by the master controller to the second IOP is by physical address.
Claim 7
Dependent Claim 41 words
A method for periodically verifying that the data bases of each said IOP remains synchronized according to claim 5, wherein the step of issuing a status request type message by the master controller to the first IOP is by logical address.
Claim 8
Dependent Claim 46 words
A method for periodically verifying that the data bases of each said IOP remains synchronized according to claim 6, wherein the number generated by each IOP indicative of the contents of the information store in the respective data bases is a first and second checksum number.

References Cited (Backward Citations)

US4183086A Cited
US4700292A Cited
US4610013A Cited
US4959774A Cited
US4799150A Cited
US5164985A Cited
US5119493A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 1996-11-08 1997-05-10 1997-11-09 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2000-11-08 2001-05-10 2001-11-09 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2004-11-08 2005-05-10 2005-11-09 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag