CA2088337C - Supervisory control and data acquisition system and method of operation - Google Patents
Supervisory control and data acquisition system and method of operationInfo
- Publication number
- CA2088337C CA2088337C CA002088337A CA2088337A CA2088337C CA 2088337 C CA2088337 C CA 2088337C CA 002088337 A CA002088337 A CA 002088337A CA 2088337 A CA2088337 A CA 2088337A CA 2088337 C CA2088337 C CA 2088337C
- Authority
- CA
- Canada
- Prior art keywords
- unit
- dimension
- message
- identifier
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q9/00—Arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom
- H04Q9/14—Calling by using pulses
Abstract
This invention relates to a supervisory control and data acquisition (SCADA) system in which a central station (10) sends control information to, and acquires information from remote stations (11, 12) over a wire, radio or other link.
Each station comprises a tabular memory (15 - 18) comprising storage locations in an 'x' direction for storing data relating to different elements of the second system and storage locations in a 'y' direction for storing data relating to different parameters of those elements.
Transmitting means are provided for transmitting a message from one unit to the other unit, said message comprising an 'x' part, a 'y' part and a qualifier, for reading from and writing to storage locations in the tabular memory of the other unit depending on the result of a logical operation defined by the qualifier.
Each station comprises a tabular memory (15 - 18) comprising storage locations in an 'x' direction for storing data relating to different elements of the second system and storage locations in a 'y' direction for storing data relating to different parameters of those elements.
Transmitting means are provided for transmitting a message from one unit to the other unit, said message comprising an 'x' part, a 'y' part and a qualifier, for reading from and writing to storage locations in the tabular memory of the other unit depending on the result of a logical operation defined by the qualifier.
Description
...,_ SUPFRVISORY CONTROT AND DATA ACOUISITION SYSTFM ~D MFTHOD OF
OPFRATION
This invention relates to a supervisory control and data acquisition (SCADA) system in which a central station sends control information to, and acquires information from remote stations over a wire, radio or other link and a method of operation of such a system.
Summ~ry of the Prior ~rt Prior art SCADA systems are described in GB-A-2118338 and GB-A-2236606.
As SCADA systems become more and more complex, with remote units controlling and monitoring more and more aspects of a system (for example a security system for a building, an irrigation system etc.), there is a need for the exchange of more and more information over the link between the central unit and the remote units.
It is useful to tabulate data to be transferred between units, in the form of, for example, rows for different elements of a system being controlled or monitored and columns for different parameters to be controlled or monitored. Thus, for example in an irrigation system, a remote unit can store a table having a row for each valve being controlled or monitored and a column for the open/closed state of the valve, the flow rate, the temperature, etc. Motorola's MIR 5000 (trade mark) system is an example of a SCADA system having memory tables at the remote units.
In the operation of such a system, there is a need to keep the traffic between the central and the remote stations to a minimum and at the same time provide flexibility in communication.
In the design, operation and maintenance of such a system, there is a need to provide a clear, simple to operate and efficient manner of relating parameters at the central unit with parameters at a remote unit. Thus, for example, where a modiflcation is to be made so as to report a new - 2 - 20~337 ~"",, parameter from a remote unit to the central unit, a change needs to be made to the software in one or both units and it is desirable to provide a simple software structure that can readily be updated to make provision for such changes.
Summary of the Invention According to the present invention, there is provided a supervisory control and data acquisition system comprising a central unit and at least one remote unit and a communications link therebetween. The remote unit comprises a plurality of inputs and outputs for receiving data from and sending control signals to different elements of a second system being supervised and controlled and a tabular memory comprising storage locations in an 'x' dimension for storing data referring to different elements in the second system and storage locations in a 'y' dimension for storing data relating to different parameters of those elements. The central unit comprises, for each remote unit, a tabular memory for storing data corresponding to the data in the tabular memory of the remote unit. The system further comprises: transmitting means for transmitting a message from one unit to the other unit, said message comprising at least one pair of a 'y' dimension identifier (y or sub-y) and a qualifier, the qualifier of said pair defining conditions to be satisfied by information identified by the corresponding 'y' dimension identifier of said pair and a 'x' dimension identifier; means for locating the information defined by the 'y' dimension identifier; logic means for determining whether that information satisfies the conditions defined by the qualifier and means responsive to the logic means for selectively reading data from and writing data to a location or set of locations identified by the 'x' dimension identifier.
The invention provides for a clear and concise way of defining memory locations, allowing for rapid transfer of information based on very flexible logical operations which allow detailed or highly selective targeting of the information required.
OPFRATION
This invention relates to a supervisory control and data acquisition (SCADA) system in which a central station sends control information to, and acquires information from remote stations over a wire, radio or other link and a method of operation of such a system.
Summ~ry of the Prior ~rt Prior art SCADA systems are described in GB-A-2118338 and GB-A-2236606.
As SCADA systems become more and more complex, with remote units controlling and monitoring more and more aspects of a system (for example a security system for a building, an irrigation system etc.), there is a need for the exchange of more and more information over the link between the central unit and the remote units.
It is useful to tabulate data to be transferred between units, in the form of, for example, rows for different elements of a system being controlled or monitored and columns for different parameters to be controlled or monitored. Thus, for example in an irrigation system, a remote unit can store a table having a row for each valve being controlled or monitored and a column for the open/closed state of the valve, the flow rate, the temperature, etc. Motorola's MIR 5000 (trade mark) system is an example of a SCADA system having memory tables at the remote units.
In the operation of such a system, there is a need to keep the traffic between the central and the remote stations to a minimum and at the same time provide flexibility in communication.
In the design, operation and maintenance of such a system, there is a need to provide a clear, simple to operate and efficient manner of relating parameters at the central unit with parameters at a remote unit. Thus, for example, where a modiflcation is to be made so as to report a new - 2 - 20~337 ~"",, parameter from a remote unit to the central unit, a change needs to be made to the software in one or both units and it is desirable to provide a simple software structure that can readily be updated to make provision for such changes.
Summary of the Invention According to the present invention, there is provided a supervisory control and data acquisition system comprising a central unit and at least one remote unit and a communications link therebetween. The remote unit comprises a plurality of inputs and outputs for receiving data from and sending control signals to different elements of a second system being supervised and controlled and a tabular memory comprising storage locations in an 'x' dimension for storing data referring to different elements in the second system and storage locations in a 'y' dimension for storing data relating to different parameters of those elements. The central unit comprises, for each remote unit, a tabular memory for storing data corresponding to the data in the tabular memory of the remote unit. The system further comprises: transmitting means for transmitting a message from one unit to the other unit, said message comprising at least one pair of a 'y' dimension identifier (y or sub-y) and a qualifier, the qualifier of said pair defining conditions to be satisfied by information identified by the corresponding 'y' dimension identifier of said pair and a 'x' dimension identifier; means for locating the information defined by the 'y' dimension identifier; logic means for determining whether that information satisfies the conditions defined by the qualifier and means responsive to the logic means for selectively reading data from and writing data to a location or set of locations identified by the 'x' dimension identifier.
The invention provides for a clear and concise way of defining memory locations, allowing for rapid transfer of information based on very flexible logical operations which allow detailed or highly selective targeting of the information required.
3 20~83~7 "
It is preferred that the means responslve to the logic means are arranged to selectively read data from or write data to locations in said 'x' dimension at which the information identified by the 'y' dimension identifier satisfies the conditions defined by the qualifier. There may be a number of 'y' (or sub-'y') dimension identifiers, each with a corresponding qualifier. In this way, complex and powerful qualifiers may be set up.
The tabular memory of each of the central unit and the remote unit preferably comprise tables of storage locations extending in a 'z' dimension, and possibly further (sub-y) dimensions and the transmitting means may comprise means for transmitting a message comprising a 'z' part for identifying a table of storage locations in which the 'x' and 'y' parts of the message identify individual locations.
The tabular memory can equally be considered to have a tree-like structure as is explained below with reference to a preferred embodiment, which is now described by way of example only.
Brief Description of the Drawings Fig. 1 shows a supervisory control and data acquisition system in accordance with the invention.
Fig. 2 shows a table of a remote unit of Fig. 1.
Fig. 3 shows an example of a message passing between the central unit and a remote unit of Fig. 1.
Fig. 4 shows a second example of a message passing between the central unit and a remote unit of Fig. 1.
Fig. 5 shows a representation of a specification in the form of a tree-like hierarchical structure.
Detailed Description of the Preferred Embodiment Referring to Fig. 1, there is shown a supervisory control and data acquisition system comprising a central unit 10 and a number of remote units, of which two are shown (11 and 12). Each of the remote units is connected to a system being controlled and monitored, by means of inputs and _ 4 _ 2~%~37 ~ .
outputs 13 and 14. The system being controlled and monitored could be, for example, a security system or an irrigation system. There may be a number of inputs and outputs . connected, for ex~mple, to.alarm.sen$ors and siren.s in.the ...
S case of a security system, or flow valves, flow meters, temperature sensors etc. in the case of an irrigation system.
For the purposes of further illustration, the case of an irrigation system will be considered.
The remote unit 11 comprises a transmitter and receiver 20, a processor 21 and memory 22 shown in an inset as being arranged as a table 15 for storing parameters relating to the system it is controlling and monitoring. For example, the memory 22 will contain, for different valves, flow pipes, reservoirs etc. data relating to on/off status, flow rate, level indication, temperature, etc. This information is used for monitoring the irrigation system and reporting back to the central unit 10, or it is used for controlling the irrigation system by receiving commands from the central unit 10 (for example to change the status of a valve from closed to open). The remote unit 12 similarly comprises a transmitter and receiver 26, a processor 27 and memory 28 arranged as a table 16.
The central unit 10 comprises a receiver and transmitter 23, a processor 24 and a number of tables 17 and 18 in memory 25. Table 17 corresponds to table lS of RTU 11 and table 18 corresponds to table 16 contained in memory 28 of RTU 12.
Although all the tables have been shown in 2-dimensional form, it will be understood that, in the preferred embodiment of the invention, they extend over 3 dimensions. The tables could, of course, be 2-dimensional or multi-dimensional.
The central unit 10 communicates with the remote units 11 and 12 over a radio link, as is well known in the art, but the units can equally communicate over a land line, such as a ~ wide area network.
Details of the preferred contention protocol of the System are described in UK Patent application number 9119186.6.
Referring to Fig. 2, details of one 2-dimensional part of table 15 are shown. The table shown comprises six columns r ~
~ 5 ~ Q ~ 8 3 ~ ~
and five rows. The columns are identified by an x co-ordinate and the rows are identified by a y co-ordinate. In a typical system, each of the columns represents, for example, a flow duct, and each of the rows represents a parameter such as valve on/off, flow rate, temperature etc.
In the individual locations in the table, specific values are stored representing status, cubic metres per second, degrees centigrade, etc. The particular locations identified by crosses in the table of Fig. 2 can be identified by means of a data-base protocol or "specification". The protocol is a convenient and simple way of transporting tabular data-base information between the tables 15 and 17 of Fig. l or the table 16 and 18.
Referring to Fig. 3, there is shown an unqualified specification identifying the locations indicated in Fig. 2.
The specification comprises a length part 31, a read/write direction part 32, a z part 33, a y part 34 and an x part 35.
The length part 3~ identifies the number of bytes of the total specification. In this case, it identifies that there are 10 bytes of the specification following the length part 31. The purpose of this is that it informs the receiving (either the central or the remote) unit to know when the message ends. The second part 32 is either "00" for "send"
or "80" for "interrogate". In this case, it is the latter, meaning that the transmitting unit is interrogating the receiving unit.
The third part 33 of the message is the z co-ordinate, identifying the particular table ~or layer) to be integrated.
In this case it is table number 9.
The fourth part 34 of the message commences with the hexadecimal numeral C, identifying that what follows is the y specification and the hexadecimal numeral 4, identifying the number of bytes of the y specification which follow. In this case there are 4 bytes as follows: "00", "02", "FE" and "04".
The first of these bytes identifies row 0 and the next three bytes together form a command which means all rows from 02 to 04. An alternative to the command "FE" is the command "FD"
which requests the rows to be transmitted in descending ~' - 6 - 20~37 .. .~, order. Thus the command "04 FD 02" means "send rows 4 to 2 in descending order".
The x part 35 commences with the byte "42", in which the hexadecimal digit "4" identifies that this is the x specification and the hexadecimal digital "2" identifies that there are two bytes to follow in the x part.
The specification of Fig. 3 uniquely identifies the indicated locations of the table of Fig. 2. It can be seen that the structure of the specification provides great flexibility in identifying different elements of different rows and columns, in a very compact format.
Fig. 4 shows a message in which the Y part 34 has a qualifier 40 associated with it. In this example, the parts 31 to 34 have the same meaning as in Fig. 3, viz:
13 = length of the complete specification 80 = interrogation from sending unit (read cycle) 09 = table number C4 = Y-list having a length equal to 4 The first two digits of the qualifier have the following meaning:
8 = qualifier code) i.e. "what follows is a qualifier";
8 = qualification list The main part of the qualifier causes the following operation to be performed:
IF X1=5 AND X2>3 then fetch the "+" elements.
In other words the qualifier causes a logical operation to be performed on the data in the table being interrogated, and the results returned to the interrogating unit are dependent on the result of the operation. This reduces the amount of data that needs to be reported back. This is particularly advantageous where a large number of remote units have to be interrogated by a single central unit.
The manner in which the above logical operation is derived from the qualifier "01 00 00 05; 02 49 00 03" is as follows.
FIRST CONDITION
01 = co-ordinate of X
00 = eight bits of "zero", i.e. "0000 0000", of which the first three mean "if X is equal to", the fourth and ~ ~ O ~ ~ ~ 3 ~
fifth are a length indication and the sixth to eighth mean .....
00 05 = value to which X is to be equated.
SECOND CONDITION
5 02 = co-ordinate of X
49 = 01001001, of which the first three bits (010) mean "if X is greater than", the fourth and fifth are a length indication, in this case showing that the number of conditions is l; and the last three bits (in reverse Polish notation) indicate an AND operation;
00 03 = value to which X is to be compared.
As before, the final part 35 of the message is the X part and in this case indicates the X elements to be fetched.
A possible meaning of the above example is:
"for valves one and two, if the flow rate is 5 m3/s and the level is greater than 3m, send the data for parameters 0, 2 and 3".
For each of the columns identified in the part of the message following the qualifier, the qualifier sets logical operations to be performed in specified rows (specified in the qualifier) and if those conditions are satisfied, the data specified by the y part is sent (or accepted) for that column.
The preferred complete set of logical operations and their 3-bit indications are as follows:
000 = equal 001 = not equal 010 > unsigned 011 < unsigned 100 > signed 101 < signed It can be arranged that the qualifier does not set conditions, but merely requires unconditional operations selected from the above set.
Referring to Fig. 5, the tables 17 and 18 which make up a data base in the central unit 10 are represented as a hierarchical data base. The specification transferred between the central unit and the remote unit is a way to represent groups of element co-ordinates in this hierarchical data base. Each element of data is uniquely defined by a set of co-ordinates. The top most co-ordinate is the number of h ~ - 8 - ~ 0 ~ 8 ~ ~ ~
the remote unit (station). Each station has a data base.
The location of the data element is defined by the following co-ordinates: the category or the z level optionally a number of y levels (called sub-y levels) and one x level. The data elements are organised in a tree-like structure, as shown in Fig. 5, that may contain data in any leaf (which is approached via co-ordinate sequence zyyx or similar). The specification is a way to describe one or many such elements.
The software in the central unit or the remote unit is able to disassemble the joint specification to a list of single element co-ordinates.
The tree-like structure is merely another way of representing the tabular N-dimensional data base (in Fig. 5 there are 4 dimensions shown), since there may be areas ~f the tabular representation that are unoccupied and therefore With reference to Fig. 5, it can be noted that the number of sub-y levels is arbitrary and that the data itself resides as an x element.
Further details of a specification format are given in the following example. In this example, the following notations have the following meanings:
< > - element [ ] - optional { } - possibly many times (or none) The format of a single specification is:
<spec> = <Total length> {<spec-k>}
The <spec> consists of several <spec-k>'s that are preceded by one byte that contains the total length of all cspec-k>'s:
<spec-k> = <Flags><Z-spec> [{<Y-spec>} {<Y-spec> <Q-spec>}
{<X-spec>}]
The <spec-k> consists of: Z description, optionally some Y (mid-levels) descriptions, possible QUALIFICATION
(condition on Y level) and X description. Note that the Y
levels other than the first are also called Sub-Y (SY).
The composition of the above elements is as follows:
<Flags>: One byte --20~33 ~
.~
If MSB = 1, this means "interrogation from unit to central". If MSB = 0, this means "transmit from central to unit".
<Z-spec>: One byte comprising Z (category) under 0-255.
<Y-spec>: <Y-id, length> <list>
The first item is a leader byte that consists of: 2 bits that identify that this is a Y ID. The 6 least bits are the length of <Y-spec> NOT including this first byte. <LIST> is defined below.
<X-spec>: <X-id, length> <List>
The first item is a leader byte that consists of: 2 bits that identify X ID. The 6 least bits are the length of <X-spec> NOT including the first byte.
<List> is a combination of bytes that describes co--ordinates of X level or of Y level.
There now follows a number of optional possibilities.
X-level: 0 - 127 If MSB is one, this is an X DEFAULT value. The co-ordinate is the seven least significant bits, but the value of the element is not the value which comes from the database: it is some default value which does not reside in the database. In such a case, the item value is not transmitted or received: it is some predefined value.
Y-level: 0 - $FA is the actual co-ordinate number.
253 ($FD): DOWN TO code. That is, all co-ordinates DOWN
To next byte co-ordinate: 4 $FD 0 is {4,3,2,1,0}.
254 ($FE): UP TO Code. That is, all co-ordinates UP TO
next byte co-ordinate: 0 $FE 4 is {0, 1, 2, 3, 4}. Note:
<List> = $FE 4 is same as 0 $FE 4, that is, default base for UP TO is 0.
255 ($FF)" "UP END" code. That is, current co-ordinate and all that follows are taken. To know what is the end, an external routine is invoked because this information is not coded within the spec.
These codes can be used in any order, such as: 1 $FE 3 7 $FF, which means {1, 2, 3, 7, 8, 9 10} if the end is 10.
The qualifier specification is as follows:
CQ-spec> = <Q-id, length> <cond> {<cond>}
' ' 20~g~3 ~
The first leader byte consists of: 2 bits that identify the Quality ID and 6 least bits that are the length of <Q-spec> NOT including first byte.
Note: a <Q-spec~ is not admissible without at least one <Y-spec> in front of it in <spec>.
Qualification is a method, in RUN TIME, to prune the branches of the database tree that MDLC has to take care of.
That is, to QUALIFY or DISQUALIFY any branch in the current level. If it qualifies, the current vertex is taken. If not, it is skipped.
The qualifications are used to compare a certain database element to another value that can be some-immediate value or some other data base element. It is implemented as follows:
<cond> = <Xk-description> <opcode> <Compared value>
The "Condition" (<cond>) consists of three parts. The <Xk-description> which is the item on which to perform the check, the <opcode> which is what to do how to compared and what to do with the result, and <Compared value> which is the immediate value or element co-ordinate with which to compare.
These various elements are as follows.
<Xk-description>
If the most significant bit of Xk = 0 then the qualification's structure is:
Xk co-ordination (z && y are known in this situation from the spec.) If Xk (msb) = 1 then the qualification's structure is:
if Xk 10000xxx.
This structure provides a very powerful tool for constructing qualifier operations and combinations, not just on the particular branch of the "tree" to which the specification currently leads, but also to other tables, columns, rows etc.
1) if xxx=000 then an element in another table is selected and the same "Y" co-ordinate is checked.
<Xk> <Z> <Xi> <OPCODE> <IMMIDIATE VALUE>
2) xxx=111 is used to enhanced the range of X up to 255.
<Xk> <enhanced X> <OPCODE> <IMMIDIATE VALUE>
3) other values of xxx (001-110) will indicate number of Y' levels.
<Xk> <Z> <Y1>...<Yn> <Xi> <OPCODE> <IMMIDIATE VALUE>
If Xk = 10010xxx <Xk> <OFFSET IN A TABLE OF USER ROUTINES> <PARAMETER>
the <PARAMETER> length of the routine is determined as follows:
if xxx=000 NO Parameter if xxx=001 1 Byte Parameter if xxx=010 2 Byte Parameter if xxx=011 3 Byte Parameter if xxx=100 4 Byte Parameter <opcode>:
1. The most significant 3 bits are the operation opcode.
The 8 possibilities are: EQ, NE, unsigned GT, unsigned LT, signed GT, signed LT, Bitwise OR, Bitwise AND
2. The least significant 5 bits describe what to do with the comparison result, which is a YES or a NO. The result is pushed into a stack-like data structure (This works in RPN -Reverse Polish Notation). Now it is possible to define logic operations between the head of the stack and its predecessor.
The first 2 bits of this field (the middle 2 bits of the byte) define the number of logic operations that are to be made. If 3, this means that after the new result is pushed onto the stack, 3 times logical operations are performed, each with the top of the stack and its predecessor. The result will replace both as the head of the stack. So there can be 0-3 logical operations. The logical operations can be AND or OR. This is defined by the 3 least significant bits.
Each bit is used to determine the type of a possible logical operation. If there are less than 3 logical operations, the irrelevant bits are ignored.
At the end of the CONDITION PARSING, there should be~5 only one element in the stack that is the result.
- 12 - 20~337 <Compared value>
This can be an immediate value the length of which is same as the length of the element described in the <Nk-description>.
<Compared value> = <Immediate value> or This can be the external user qualification routine parameter.
By virtue of the possibility of having a number of conditions, as indicated by the optional extra specification portions {<Y-spec> <Q-spec>} and {<cond>} above, in the qualifier specification, complex and powerful qualifiers can be built up, with a number of sub-y elements, each followed by a condition, where the complete qualifier defines a sét of logical operations to be performed on different elements or sets of elements, not necessarily in the same table, row or column, i.e. not necessarily in the same branch of the tree, and with the down-loading of information from the central unit to the remote unit, or the up-loading of information in the other direction, being dependent on the complex qualifier being satisfied.
When the qualifiers are not satisfied, a negative result is returned to the interrogating unit.
When a specification is passed from the central unit to a remote unit and the specification incorrectly defines a nonexistent branch of the tree, an error code is returned to the central unit together with the identity of the specification part that gave rise to the error. For example:
wrong z, wrong y, syntax error in qualifier, etc. Errors are reported in the opposite direction in a similar manner.
Thus, a supervisory control and data acquisition system has been described which has the advantage that every element of the data base can be reached in a unique concise manner.
Complete tables can be accessed in a short time or tables can be cut in a short time. Cuttings of tables can be made by a "smart", i.e. Boolean logic, qualification. For example, "if the flow rate is 5 metres3/s and the level is greater than 3 metres and smaller than 6 metres, then send the data".
~ - 13 - 20~337 ",."= .
Qualifiers can be set up to request the down-loading of information from elements of the system under supervision, where the particular elements which will respond are not known at the outset, but depend on the results of the qualifier.
Qualifiers are not limited to setting conditions dependent on information defined by a particular branch of the tree or particular table to which the specification "points". On the contrary, qualifiers can set conditions dependent on information from other branches or tables.
The communication is clear and rapid. A large specification can be sent or received including a number of small specifications. Specifications can be defined to send data or to make interrogations. Errors are returned in a clear manner.
It is preferred that the means responslve to the logic means are arranged to selectively read data from or write data to locations in said 'x' dimension at which the information identified by the 'y' dimension identifier satisfies the conditions defined by the qualifier. There may be a number of 'y' (or sub-'y') dimension identifiers, each with a corresponding qualifier. In this way, complex and powerful qualifiers may be set up.
The tabular memory of each of the central unit and the remote unit preferably comprise tables of storage locations extending in a 'z' dimension, and possibly further (sub-y) dimensions and the transmitting means may comprise means for transmitting a message comprising a 'z' part for identifying a table of storage locations in which the 'x' and 'y' parts of the message identify individual locations.
The tabular memory can equally be considered to have a tree-like structure as is explained below with reference to a preferred embodiment, which is now described by way of example only.
Brief Description of the Drawings Fig. 1 shows a supervisory control and data acquisition system in accordance with the invention.
Fig. 2 shows a table of a remote unit of Fig. 1.
Fig. 3 shows an example of a message passing between the central unit and a remote unit of Fig. 1.
Fig. 4 shows a second example of a message passing between the central unit and a remote unit of Fig. 1.
Fig. 5 shows a representation of a specification in the form of a tree-like hierarchical structure.
Detailed Description of the Preferred Embodiment Referring to Fig. 1, there is shown a supervisory control and data acquisition system comprising a central unit 10 and a number of remote units, of which two are shown (11 and 12). Each of the remote units is connected to a system being controlled and monitored, by means of inputs and _ 4 _ 2~%~37 ~ .
outputs 13 and 14. The system being controlled and monitored could be, for example, a security system or an irrigation system. There may be a number of inputs and outputs . connected, for ex~mple, to.alarm.sen$ors and siren.s in.the ...
S case of a security system, or flow valves, flow meters, temperature sensors etc. in the case of an irrigation system.
For the purposes of further illustration, the case of an irrigation system will be considered.
The remote unit 11 comprises a transmitter and receiver 20, a processor 21 and memory 22 shown in an inset as being arranged as a table 15 for storing parameters relating to the system it is controlling and monitoring. For example, the memory 22 will contain, for different valves, flow pipes, reservoirs etc. data relating to on/off status, flow rate, level indication, temperature, etc. This information is used for monitoring the irrigation system and reporting back to the central unit 10, or it is used for controlling the irrigation system by receiving commands from the central unit 10 (for example to change the status of a valve from closed to open). The remote unit 12 similarly comprises a transmitter and receiver 26, a processor 27 and memory 28 arranged as a table 16.
The central unit 10 comprises a receiver and transmitter 23, a processor 24 and a number of tables 17 and 18 in memory 25. Table 17 corresponds to table lS of RTU 11 and table 18 corresponds to table 16 contained in memory 28 of RTU 12.
Although all the tables have been shown in 2-dimensional form, it will be understood that, in the preferred embodiment of the invention, they extend over 3 dimensions. The tables could, of course, be 2-dimensional or multi-dimensional.
The central unit 10 communicates with the remote units 11 and 12 over a radio link, as is well known in the art, but the units can equally communicate over a land line, such as a ~ wide area network.
Details of the preferred contention protocol of the System are described in UK Patent application number 9119186.6.
Referring to Fig. 2, details of one 2-dimensional part of table 15 are shown. The table shown comprises six columns r ~
~ 5 ~ Q ~ 8 3 ~ ~
and five rows. The columns are identified by an x co-ordinate and the rows are identified by a y co-ordinate. In a typical system, each of the columns represents, for example, a flow duct, and each of the rows represents a parameter such as valve on/off, flow rate, temperature etc.
In the individual locations in the table, specific values are stored representing status, cubic metres per second, degrees centigrade, etc. The particular locations identified by crosses in the table of Fig. 2 can be identified by means of a data-base protocol or "specification". The protocol is a convenient and simple way of transporting tabular data-base information between the tables 15 and 17 of Fig. l or the table 16 and 18.
Referring to Fig. 3, there is shown an unqualified specification identifying the locations indicated in Fig. 2.
The specification comprises a length part 31, a read/write direction part 32, a z part 33, a y part 34 and an x part 35.
The length part 3~ identifies the number of bytes of the total specification. In this case, it identifies that there are 10 bytes of the specification following the length part 31. The purpose of this is that it informs the receiving (either the central or the remote) unit to know when the message ends. The second part 32 is either "00" for "send"
or "80" for "interrogate". In this case, it is the latter, meaning that the transmitting unit is interrogating the receiving unit.
The third part 33 of the message is the z co-ordinate, identifying the particular table ~or layer) to be integrated.
In this case it is table number 9.
The fourth part 34 of the message commences with the hexadecimal numeral C, identifying that what follows is the y specification and the hexadecimal numeral 4, identifying the number of bytes of the y specification which follow. In this case there are 4 bytes as follows: "00", "02", "FE" and "04".
The first of these bytes identifies row 0 and the next three bytes together form a command which means all rows from 02 to 04. An alternative to the command "FE" is the command "FD"
which requests the rows to be transmitted in descending ~' - 6 - 20~37 .. .~, order. Thus the command "04 FD 02" means "send rows 4 to 2 in descending order".
The x part 35 commences with the byte "42", in which the hexadecimal digit "4" identifies that this is the x specification and the hexadecimal digital "2" identifies that there are two bytes to follow in the x part.
The specification of Fig. 3 uniquely identifies the indicated locations of the table of Fig. 2. It can be seen that the structure of the specification provides great flexibility in identifying different elements of different rows and columns, in a very compact format.
Fig. 4 shows a message in which the Y part 34 has a qualifier 40 associated with it. In this example, the parts 31 to 34 have the same meaning as in Fig. 3, viz:
13 = length of the complete specification 80 = interrogation from sending unit (read cycle) 09 = table number C4 = Y-list having a length equal to 4 The first two digits of the qualifier have the following meaning:
8 = qualifier code) i.e. "what follows is a qualifier";
8 = qualification list The main part of the qualifier causes the following operation to be performed:
IF X1=5 AND X2>3 then fetch the "+" elements.
In other words the qualifier causes a logical operation to be performed on the data in the table being interrogated, and the results returned to the interrogating unit are dependent on the result of the operation. This reduces the amount of data that needs to be reported back. This is particularly advantageous where a large number of remote units have to be interrogated by a single central unit.
The manner in which the above logical operation is derived from the qualifier "01 00 00 05; 02 49 00 03" is as follows.
FIRST CONDITION
01 = co-ordinate of X
00 = eight bits of "zero", i.e. "0000 0000", of which the first three mean "if X is equal to", the fourth and ~ ~ O ~ ~ ~ 3 ~
fifth are a length indication and the sixth to eighth mean .....
00 05 = value to which X is to be equated.
SECOND CONDITION
5 02 = co-ordinate of X
49 = 01001001, of which the first three bits (010) mean "if X is greater than", the fourth and fifth are a length indication, in this case showing that the number of conditions is l; and the last three bits (in reverse Polish notation) indicate an AND operation;
00 03 = value to which X is to be compared.
As before, the final part 35 of the message is the X part and in this case indicates the X elements to be fetched.
A possible meaning of the above example is:
"for valves one and two, if the flow rate is 5 m3/s and the level is greater than 3m, send the data for parameters 0, 2 and 3".
For each of the columns identified in the part of the message following the qualifier, the qualifier sets logical operations to be performed in specified rows (specified in the qualifier) and if those conditions are satisfied, the data specified by the y part is sent (or accepted) for that column.
The preferred complete set of logical operations and their 3-bit indications are as follows:
000 = equal 001 = not equal 010 > unsigned 011 < unsigned 100 > signed 101 < signed It can be arranged that the qualifier does not set conditions, but merely requires unconditional operations selected from the above set.
Referring to Fig. 5, the tables 17 and 18 which make up a data base in the central unit 10 are represented as a hierarchical data base. The specification transferred between the central unit and the remote unit is a way to represent groups of element co-ordinates in this hierarchical data base. Each element of data is uniquely defined by a set of co-ordinates. The top most co-ordinate is the number of h ~ - 8 - ~ 0 ~ 8 ~ ~ ~
the remote unit (station). Each station has a data base.
The location of the data element is defined by the following co-ordinates: the category or the z level optionally a number of y levels (called sub-y levels) and one x level. The data elements are organised in a tree-like structure, as shown in Fig. 5, that may contain data in any leaf (which is approached via co-ordinate sequence zyyx or similar). The specification is a way to describe one or many such elements.
The software in the central unit or the remote unit is able to disassemble the joint specification to a list of single element co-ordinates.
The tree-like structure is merely another way of representing the tabular N-dimensional data base (in Fig. 5 there are 4 dimensions shown), since there may be areas ~f the tabular representation that are unoccupied and therefore With reference to Fig. 5, it can be noted that the number of sub-y levels is arbitrary and that the data itself resides as an x element.
Further details of a specification format are given in the following example. In this example, the following notations have the following meanings:
< > - element [ ] - optional { } - possibly many times (or none) The format of a single specification is:
<spec> = <Total length> {<spec-k>}
The <spec> consists of several <spec-k>'s that are preceded by one byte that contains the total length of all cspec-k>'s:
<spec-k> = <Flags><Z-spec> [{<Y-spec>} {<Y-spec> <Q-spec>}
{<X-spec>}]
The <spec-k> consists of: Z description, optionally some Y (mid-levels) descriptions, possible QUALIFICATION
(condition on Y level) and X description. Note that the Y
levels other than the first are also called Sub-Y (SY).
The composition of the above elements is as follows:
<Flags>: One byte --20~33 ~
.~
If MSB = 1, this means "interrogation from unit to central". If MSB = 0, this means "transmit from central to unit".
<Z-spec>: One byte comprising Z (category) under 0-255.
<Y-spec>: <Y-id, length> <list>
The first item is a leader byte that consists of: 2 bits that identify that this is a Y ID. The 6 least bits are the length of <Y-spec> NOT including this first byte. <LIST> is defined below.
<X-spec>: <X-id, length> <List>
The first item is a leader byte that consists of: 2 bits that identify X ID. The 6 least bits are the length of <X-spec> NOT including the first byte.
<List> is a combination of bytes that describes co--ordinates of X level or of Y level.
There now follows a number of optional possibilities.
X-level: 0 - 127 If MSB is one, this is an X DEFAULT value. The co-ordinate is the seven least significant bits, but the value of the element is not the value which comes from the database: it is some default value which does not reside in the database. In such a case, the item value is not transmitted or received: it is some predefined value.
Y-level: 0 - $FA is the actual co-ordinate number.
253 ($FD): DOWN TO code. That is, all co-ordinates DOWN
To next byte co-ordinate: 4 $FD 0 is {4,3,2,1,0}.
254 ($FE): UP TO Code. That is, all co-ordinates UP TO
next byte co-ordinate: 0 $FE 4 is {0, 1, 2, 3, 4}. Note:
<List> = $FE 4 is same as 0 $FE 4, that is, default base for UP TO is 0.
255 ($FF)" "UP END" code. That is, current co-ordinate and all that follows are taken. To know what is the end, an external routine is invoked because this information is not coded within the spec.
These codes can be used in any order, such as: 1 $FE 3 7 $FF, which means {1, 2, 3, 7, 8, 9 10} if the end is 10.
The qualifier specification is as follows:
CQ-spec> = <Q-id, length> <cond> {<cond>}
' ' 20~g~3 ~
The first leader byte consists of: 2 bits that identify the Quality ID and 6 least bits that are the length of <Q-spec> NOT including first byte.
Note: a <Q-spec~ is not admissible without at least one <Y-spec> in front of it in <spec>.
Qualification is a method, in RUN TIME, to prune the branches of the database tree that MDLC has to take care of.
That is, to QUALIFY or DISQUALIFY any branch in the current level. If it qualifies, the current vertex is taken. If not, it is skipped.
The qualifications are used to compare a certain database element to another value that can be some-immediate value or some other data base element. It is implemented as follows:
<cond> = <Xk-description> <opcode> <Compared value>
The "Condition" (<cond>) consists of three parts. The <Xk-description> which is the item on which to perform the check, the <opcode> which is what to do how to compared and what to do with the result, and <Compared value> which is the immediate value or element co-ordinate with which to compare.
These various elements are as follows.
<Xk-description>
If the most significant bit of Xk = 0 then the qualification's structure is:
Xk co-ordination (z && y are known in this situation from the spec.) If Xk (msb) = 1 then the qualification's structure is:
if Xk 10000xxx.
This structure provides a very powerful tool for constructing qualifier operations and combinations, not just on the particular branch of the "tree" to which the specification currently leads, but also to other tables, columns, rows etc.
1) if xxx=000 then an element in another table is selected and the same "Y" co-ordinate is checked.
<Xk> <Z> <Xi> <OPCODE> <IMMIDIATE VALUE>
2) xxx=111 is used to enhanced the range of X up to 255.
<Xk> <enhanced X> <OPCODE> <IMMIDIATE VALUE>
3) other values of xxx (001-110) will indicate number of Y' levels.
<Xk> <Z> <Y1>...<Yn> <Xi> <OPCODE> <IMMIDIATE VALUE>
If Xk = 10010xxx <Xk> <OFFSET IN A TABLE OF USER ROUTINES> <PARAMETER>
the <PARAMETER> length of the routine is determined as follows:
if xxx=000 NO Parameter if xxx=001 1 Byte Parameter if xxx=010 2 Byte Parameter if xxx=011 3 Byte Parameter if xxx=100 4 Byte Parameter <opcode>:
1. The most significant 3 bits are the operation opcode.
The 8 possibilities are: EQ, NE, unsigned GT, unsigned LT, signed GT, signed LT, Bitwise OR, Bitwise AND
2. The least significant 5 bits describe what to do with the comparison result, which is a YES or a NO. The result is pushed into a stack-like data structure (This works in RPN -Reverse Polish Notation). Now it is possible to define logic operations between the head of the stack and its predecessor.
The first 2 bits of this field (the middle 2 bits of the byte) define the number of logic operations that are to be made. If 3, this means that after the new result is pushed onto the stack, 3 times logical operations are performed, each with the top of the stack and its predecessor. The result will replace both as the head of the stack. So there can be 0-3 logical operations. The logical operations can be AND or OR. This is defined by the 3 least significant bits.
Each bit is used to determine the type of a possible logical operation. If there are less than 3 logical operations, the irrelevant bits are ignored.
At the end of the CONDITION PARSING, there should be~5 only one element in the stack that is the result.
- 12 - 20~337 <Compared value>
This can be an immediate value the length of which is same as the length of the element described in the <Nk-description>.
<Compared value> = <Immediate value> or This can be the external user qualification routine parameter.
By virtue of the possibility of having a number of conditions, as indicated by the optional extra specification portions {<Y-spec> <Q-spec>} and {<cond>} above, in the qualifier specification, complex and powerful qualifiers can be built up, with a number of sub-y elements, each followed by a condition, where the complete qualifier defines a sét of logical operations to be performed on different elements or sets of elements, not necessarily in the same table, row or column, i.e. not necessarily in the same branch of the tree, and with the down-loading of information from the central unit to the remote unit, or the up-loading of information in the other direction, being dependent on the complex qualifier being satisfied.
When the qualifiers are not satisfied, a negative result is returned to the interrogating unit.
When a specification is passed from the central unit to a remote unit and the specification incorrectly defines a nonexistent branch of the tree, an error code is returned to the central unit together with the identity of the specification part that gave rise to the error. For example:
wrong z, wrong y, syntax error in qualifier, etc. Errors are reported in the opposite direction in a similar manner.
Thus, a supervisory control and data acquisition system has been described which has the advantage that every element of the data base can be reached in a unique concise manner.
Complete tables can be accessed in a short time or tables can be cut in a short time. Cuttings of tables can be made by a "smart", i.e. Boolean logic, qualification. For example, "if the flow rate is 5 metres3/s and the level is greater than 3 metres and smaller than 6 metres, then send the data".
~ - 13 - 20~337 ",."= .
Qualifiers can be set up to request the down-loading of information from elements of the system under supervision, where the particular elements which will respond are not known at the outset, but depend on the results of the qualifier.
Qualifiers are not limited to setting conditions dependent on information defined by a particular branch of the tree or particular table to which the specification "points". On the contrary, qualifiers can set conditions dependent on information from other branches or tables.
The communication is clear and rapid. A large specification can be sent or received including a number of small specifications. Specifications can be defined to send data or to make interrogations. Errors are returned in a clear manner.
Claims (14)
1 A supervisory control and data acquisition system comprising a central unit and at least one remote unit and a communications link therebetween, wherein the remote unit comprises a plurality of inputs and outputs for receiving data from and sending control signals to different elements of a second system being supervised and controlled and a tabular memory comprising storage locations in an 'x' dimension for storing data referring to different elements in the second system and storage locations in a 'y' dimension for storing data relating to different parameters of those elements, and wherein the central unit comprises, for each remote unit, a tabular memory for storing data corresponding to the data in the tabular memory of the remote unit, the system further comprising:
transmitting means for transmitting a message from one unit to the other unit, said message comprising at least one pair of a 'y' dimension identifier (y or sub-y) and a qualifier, the qualifier of said pair defining conditions to be satisfied by information identified by the corresponding 'y' dimension identifier of said pair and a 'x' dimension identifier;
means for locating the information defined by the 'y' dimension identifier;
logic means for determining whether that information satisfies the conditions defined by the qualifier and means responsive to the logic means for selectively reading data from and writing data to a location or set of locations identified by the 'x' dimension identifier.
transmitting means for transmitting a message from one unit to the other unit, said message comprising at least one pair of a 'y' dimension identifier (y or sub-y) and a qualifier, the qualifier of said pair defining conditions to be satisfied by information identified by the corresponding 'y' dimension identifier of said pair and a 'x' dimension identifier;
means for locating the information defined by the 'y' dimension identifier;
logic means for determining whether that information satisfies the conditions defined by the qualifier and means responsive to the logic means for selectively reading data from and writing data to a location or set of locations identified by the 'x' dimension identifier.
2. A system according to claim 1, wherein the means responsive to the logic means are arranged to selectively read data from or write data to locations in said 'x' dimension at which the information identified by the 'y' dimension identifier satisfies the conditions defined by the qualifier.
3. A system according to claim l, wherein the message comprises more than one pair of a 'y' dimension identifier (y or sub-y) and a qualifier and wherein the logic means are arranged to determine whether the information defined by each 'y' dimension identifier satisfies the conditions defined by its corresponding qualifier.
4. A system according to claim 3, wherein the tabular memory of each of the central unit and the remote unit comprises tables of storage locations extending in further dimensions and the transmitting means comprises means for transmitting a message comprising at least two pairs of a 'y' dimension identifier (y or sub-y) and a qualifier, wherein the 'y' dimension identifiers of the at least two pairs of 'y' dimension identifiers (y or sub-y) and qualifiers identify storage locations in different dimensions (y and sub-y).
5. A system according to claim 1, wherein the message includes an indication of the number of pairs of 'y' dimension identifiers and qualifiers in the message.
6. A system according to any one of the preceding claims, wherein the tabular memory of each of the central unit and the remote unit comprises tables of storage locations extending in a 'z' direction and the transmitting means comprises means for transmitting a message comprising a 'z' part for identifying a table of storage locations in which the 'x' and 'y' parts of the message identify individual locations.
7. A system according to claim 6, wherein the tabular memory of each of the central unit and the remote unit comprises tables of storage locations extending in further dimensions and the transmitting means comprises means for transmitting a message comprising a part for identifying locations in said further dimensions.
8. A system according to claim 1, wherein a storage location is uniquely defined by the following co-ordinates: a z level, optionally a number of y levels, and one x level.
9. A system according claim 1 wherein each unit is arranged to receive the message transmitted from the one unit to the other unit and arranged to retransmit an error signal when the message received defines a nonexistent storage location at the unit receiving the message.
10. A supervisory control and data acquisition system comprising a central unit and at least one remote unit and a communications link therebetween, wherein the remote unit comprises a plurality of inputs and outputs for receiving data from and sending control signals to different elements of a second system being supervised and controlled and a memory organised in a tree-like structure comprising branches and leaves, different branches relating to different parameters of the elements of second system and different leaves being storage locations for storing data relating to different elements, and wherein the central unit comprises, for each remote unit, a tree-like memory for storing data corresponding to the data in the memory of the remote unit, the system further comprising:
transmitting means for transmitting a message from one unit to the other unit, said message comprising:
at least one pair of a branch identifier (y or sub-y) and a qualifier, the qualifier of said pair defining conditions to be satisfied by information identified by the corresponding branch identifier (sub-Y) of said pair;
a leaf identifier (x) for identifying an individual storage location or set of locations in the memory of the other unit; and means for selectively reading data from and writing data to the individual storage location or set of locations identified by the leaf identifier (x) dependent on the satisfying of the conditions defined by the qualifier.
transmitting means for transmitting a message from one unit to the other unit, said message comprising:
at least one pair of a branch identifier (y or sub-y) and a qualifier, the qualifier of said pair defining conditions to be satisfied by information identified by the corresponding branch identifier (sub-Y) of said pair;
a leaf identifier (x) for identifying an individual storage location or set of locations in the memory of the other unit; and means for selectively reading data from and writing data to the individual storage location or set of locations identified by the leaf identifier (x) dependent on the satisfying of the conditions defined by the qualifier.
11. A system according to claim 10, wherein the system comprises receiving means for receiving the message transmitted from the one unit to the other unit and wherein the transmitting means comprises means for transmitting a message comprising a number of pairs of branch identifiers and qualifiers, and the receiving means comprises means for acting on the message received only if all the pairs of qualifiers are satisfied.
12. A system according to claim 11, wherein the means for acting on the message received comprises means for reading data from or writing data to a data base location or set of locations identified by the leaf identifier.
13. A method of operation of a supervisory control and data acquisition system comprising a central unit and at least one remote unit and a communications link therebetween, wherein the remote unit comprises a plurality of inputs and outputs for receiving data from and sending control signals to different elements of a second system being supervised and controlled and a tabular memory comprising storage locations in an 'x' dimension for storing data referring to different elements in the second system and storage locations in a 'y' dimension for storing data relating to different parameters of those elements, and wherein the central unit comprises, for each remote unit, a tabular memory for storing data corresponding to the data in the tabular memory of the remote unit, the method comprising the steps of:
transmitting a message from one unit to the other unit, said message comprising:
at least one 'x' dimension identifier for defining at least one set of values in the 'x' dimension;
at least one first 'y' dimension identifier for defining at least one set of values in the 'y' dimension and at least one pair of a second 'y' dimension identifier (y or sub-y) and a qualifier, the second 'y' dimension identifier of the pair identifying, for each defined value in the 'x' dimension, one or more storage locations in the tabular memory of the other unit, and the qualifier of said pair defining conditions to be satisfied by information stored in the storage locations thus identified;
locating, at the other unit, the information defined by the second 'y' dimension identifier, determining whether that information satisfies the conditions defined by the qualifier and selectively reading data from and writing data to a location or set of locations identified by the 'x' dimension identifier and the first 'y' dimension identifier, depending on whether said information satisfies said conditions.
transmitting a message from one unit to the other unit, said message comprising:
at least one 'x' dimension identifier for defining at least one set of values in the 'x' dimension;
at least one first 'y' dimension identifier for defining at least one set of values in the 'y' dimension and at least one pair of a second 'y' dimension identifier (y or sub-y) and a qualifier, the second 'y' dimension identifier of the pair identifying, for each defined value in the 'x' dimension, one or more storage locations in the tabular memory of the other unit, and the qualifier of said pair defining conditions to be satisfied by information stored in the storage locations thus identified;
locating, at the other unit, the information defined by the second 'y' dimension identifier, determining whether that information satisfies the conditions defined by the qualifier and selectively reading data from and writing data to a location or set of locations identified by the 'x' dimension identifier and the first 'y' dimension identifier, depending on whether said information satisfies said conditions.
14. Method of operation of a supervisory control and data acquisition system comprising a central unit and at least one remote unit and a communications link therebetween, wherein the remote unit comprises a plurality of inputs and outputs for receiving data from and sending control signals to different elements of a second system being supervised and controlled and a memory organised in a tree-like structure comprising branches and leaves, different branches relating to different parameters of the elements of second system and different leaves being storage locations for storing data relating to different elements, and wherein the central unit comprises, for each remote unit, a tree-like memory for storing data corresponding to the data in the memory of the remote unit, the method comprising the steps of:
transmitting a message from one unit to the other unit, said message comprising:
at least one leaf identifier, for identifying a leaf on one or more branches representing for each branch an individual storage location in the memory of the other unit;
at least one first branch identifier (y or sub-y), for identifying at least one branch representing at least one set of individual storage locations in the memory of the other unit;
at least one pair of a second branch identifier (y or sub-y) and a qualifier, the qualifier of said pair defining conditions to be satisfied by information identified by the second branch identifier (y or sub-y) of said pair; and selectively reading data from and writing data to one or more selected individual storage locations identified by the leaf identifier (x) and the first branch identifier (y or sub-y), dependent on the satisfying of the conditions defined by the qualifier.
transmitting a message from one unit to the other unit, said message comprising:
at least one leaf identifier, for identifying a leaf on one or more branches representing for each branch an individual storage location in the memory of the other unit;
at least one first branch identifier (y or sub-y), for identifying at least one branch representing at least one set of individual storage locations in the memory of the other unit;
at least one pair of a second branch identifier (y or sub-y) and a qualifier, the qualifier of said pair defining conditions to be satisfied by information identified by the second branch identifier (y or sub-y) of said pair; and selectively reading data from and writing data to one or more selected individual storage locations identified by the leaf identifier (x) and the first branch identifier (y or sub-y), dependent on the satisfying of the conditions defined by the qualifier.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB9202201.1 | 1992-02-01 | ||
| GB9202201A GB2263989B (en) | 1992-02-01 | 1992-02-01 | Supervisory control and data acquisition system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2088337A1 CA2088337A1 (en) | 1993-08-02 |
| CA2088337C true CA2088337C (en) | 1998-08-18 |
Family
ID=10709698
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002088337A Expired - Fee Related CA2088337C (en) | 1992-02-01 | 1993-01-28 | Supervisory control and data acquisition system and method of operation |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US5452465A (en) |
| AU (1) | AU660347B2 (en) |
| CA (1) | CA2088337C (en) |
| GB (1) | GB2263989B (en) |
| IL (1) | IL104411A (en) |
Families Citing this family (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5659467A (en) * | 1996-06-26 | 1997-08-19 | Texas Instruments Incorporated | Multiple model supervisor control system and method of operation |
| US5963734A (en) * | 1997-04-03 | 1999-10-05 | Abb Power T&D Company Inc. | Method and apparatus for configuring an intelligent electronic device for use in supervisory control and data acquisition system verification |
| US6088659A (en) * | 1997-09-11 | 2000-07-11 | Abb Power T&D Company Inc. | Automated meter reading system |
| WO1999045510A2 (en) | 1998-03-03 | 1999-09-10 | Itron, Inc. | Method and system for reading intelligent utility meters |
| US6005759A (en) * | 1998-03-16 | 1999-12-21 | Abb Power T&D Company Inc. | Method and system for monitoring and controlling an electrical distribution network |
| US6700902B1 (en) | 1998-10-19 | 2004-03-02 | Elster Electricity, Llc | Method and system for improving wireless data packet delivery |
| DE10202028A1 (en) * | 2002-01-18 | 2003-07-24 | Endress & Hauser Gmbh & Co Kg | Transmitter for detecting a physical measured variable and for converting it into an electrical variable uses signal processors to reshape the electrical variable into a test signal |
| US6879893B2 (en) * | 2002-09-30 | 2005-04-12 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Tributary analysis monitoring system |
| US8176532B1 (en) | 2003-03-17 | 2012-05-08 | Sprint Communications Company L.P. | Secure access point for scada devices |
| US7702594B2 (en) | 2004-09-24 | 2010-04-20 | Elster Electricity, Llc | System and method for automated configuration of meters |
| US7742430B2 (en) | 2004-09-24 | 2010-06-22 | Elster Electricity, Llc | System for automated management of spontaneous node migration in a distributed fixed wireless network |
| US7460931B2 (en) | 2005-10-07 | 2008-12-02 | Jay Jacobson | Method and system for improving the efficiency and reliability of a power grid |
| US8073384B2 (en) | 2006-12-14 | 2011-12-06 | Elster Electricity, Llc | Optimization of redundancy and throughput in an automated meter data collection system using a wireless network |
| US8320302B2 (en) | 2007-04-20 | 2012-11-27 | Elster Electricity, Llc | Over the air microcontroller flash memory updates |
| WO2009082761A1 (en) | 2007-12-26 | 2009-07-02 | Elster Electricity, Llc. | Optimized data collection in a wireless fixed network metering system |
| US8525692B2 (en) | 2008-06-13 | 2013-09-03 | Elster Solutions, Llc | Techniques for limiting demand from an electricity meter with an installed relay |
| DE102008038968A1 (en) * | 2008-08-13 | 2010-02-18 | Schad Gmbh | System for monitoring, control and data acquisition of technical processes |
| US8203463B2 (en) | 2009-02-13 | 2012-06-19 | Elster Electricity Llc | Wakeup and interrogation of meter-reading devices using licensed narrowband and unlicensed wideband radio communication |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4468728A (en) * | 1981-06-25 | 1984-08-28 | At&T Bell Laboratories | Data structure and search method for a data base management system |
| US4700294A (en) * | 1982-10-15 | 1987-10-13 | Becton Dickinson And Company | Data storage system having means for compressing input data from sets of correlated parameters |
| US4638453A (en) * | 1983-03-28 | 1987-01-20 | Motorola, Inc. | Signal processing unit |
-
1992
- 1992-02-01 GB GB9202201A patent/GB2263989B/en not_active Expired - Fee Related
-
1993
- 1993-01-15 IL IL10441193A patent/IL104411A/en not_active IP Right Cessation
- 1993-01-22 AU AU31967/93A patent/AU660347B2/en not_active Ceased
- 1993-01-26 US US08/009,174 patent/US5452465A/en not_active Expired - Lifetime
- 1993-01-28 CA CA002088337A patent/CA2088337C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| US5452465A (en) | 1995-09-19 |
| IL104411A (en) | 1996-03-31 |
| GB2263989A (en) | 1993-08-11 |
| GB9202201D0 (en) | 1992-03-18 |
| AU3196793A (en) | 1993-08-05 |
| GB2263989B (en) | 1995-05-31 |
| AU660347B2 (en) | 1995-06-22 |
| CA2088337A1 (en) | 1993-08-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2088337C (en) | Supervisory control and data acquisition system and method of operation | |
| US5197095A (en) | System for remote transfer and collection of data, in particular from meters | |
| US20060187031A1 (en) | Selecting RFID tags using memory-mapped parameters | |
| EP0702323B1 (en) | System and method for radio frequency tag group select | |
| CN1053037C (en) | Error detection for HVAC systems | |
| US7246193B2 (en) | Interface module for use with a Modbus device network and a Fieldbus device network | |
| CN103149899B (en) | Grain bin intelligent sensor integration terminal | |
| CN101242549A (en) | Neutral network construction method for communication network alarm association | |
| EP0388436A4 (en) | Network and intelligent cell for providing sensing, bidirectional communications and control | |
| CN103401930B (en) | A kind of industrial monitoring method and device of sing on web Service | |
| CN110311990A (en) | A kind of configurable internet of things data acquisition system and configuration method | |
| CN108390699B (en) | Cloud communication system based on power line carrier technology and communication method and device | |
| CN112995172B (en) | Communication method and communication system for butt joint between Internet of things equipment and Internet of things platform | |
| CN104731079A (en) | Oil field data monitoring system and method | |
| WO2001002953B1 (en) | Method of integrating an application in a computerized system | |
| CN102460466A (en) | Method and apparatus for tunneling information in RFID communications | |
| US11310353B2 (en) | Data transmission method for creating data structure facilitating data transmission and reception | |
| CN106302485A (en) | OPC standard and the bi-directional conversion system of power remote agreement | |
| CN101227327A (en) | Method for concentrating network managing system and uploading lower level alarm information | |
| CN107480182A (en) | A kind of spacecraft telemetry source tracing method and system | |
| CN105955710A (en) | Parallel simulation data processing method based on tree communication structure | |
| WO2003021877A1 (en) | Communication device and meter reading device | |
| US6313763B1 (en) | Variable length data packet with adjustable length indicator | |
| EP0912069A2 (en) | Execution of service control requests in a single service control point | |
| CA2422920C (en) | Method of making measured values available to final customers |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |