United States Patent
`Verissimo et al.
`
`[19]
`
`111111111111111111111111111111111111111111111111111111111111111111111111111
`US005841654A
`Patent Number:
`Date of Patent:
`
`5,841,654
`Nov. 24, 1998
`
`[11]
`
`[45]
`
`[54] WINDOWS BASED NETWORK
`CONFIGURATION AND CONTROL METHOD
`FOR A DIGITAL CONTROL SYSTEM
`
`5,386,360
`5,442,693
`5,485,620
`
`1/1995 Wilson et al.
`8/1995 Crowder et al.
`1/1996 Sadre et al. ....
`
`364/146
`371/20.1
`395/700
`
`[75]
`
`Inventors: Emani Sperandio Verissimo, Ribeirao
`Preto; Gerson Valentin; Marco A. O.
`Pagnano, both of Sertaozinho; Omar
`Sacilotto Donaires, Ribeirao Preto;
`Vanderlei L. D. Miranda, Sertaozinho,
`all of Brazil
`
`[73] Assignee: SMAR Research Corporation,
`Ronkonkoma, N.Y.
`
`[21] Appl. No.: 543,434
`
`[22]
`
`Filed:
`
`Oct. 16, 1995
`
`Int. CI.6
`G05B 9/02
`[51]
`364/188; 370/85.1; 370/20.1;
`[52] U.S. CI.
`370/254; 370/255; 370/257; 370/258; 395/500;
`395/159; 371/20.1
`364/188, 551.01;
`Field of Search
`395/500, 159; 370/85.1, 254, 257, 258,
`255; 371/20.1
`
`[58]
`
`[56]
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`4,304,001
`4,663,704
`4,862,345
`5,134,574
`5,168,441
`5,261,044
`5,280,477
`5,301,301
`5,335,339
`5,371,895
`
`12/1981 Cope
`5/1987 Jones et al.
`8/1989 Lekron
`7/1992 Beaverstock et al.
`12/1992 Onarheim et al.
`11/1993 Dev. et al.
`1/1994 Trapp
`4/1994 Kodosky et al.
`8/1994 Maejima et al.
`12/1994 Bristol
`
`371/8
`364/188
`364/188
`364/551.01
`364/146
`395/159
`370/85.1
`395/500
`395/500
`395/800
`
`OTHER PUBLICATIONS
`
`Fieldbus Foundation™, Fieldbus Specification, Function
`Block Application Process-Part 1, FF-94-890, Revision
`PS 1.0,Apr. 27, 1995.
`Fieldbus Foundation™, Fieldbus Specification, Function
`Block Application Process-Part 2, FF-94-891, Revision
`PS 1.0,Apr. 27, 1995.
`"SMAR,Fieldbus Tutorial", SMAR Int'L. Corp. 1993.
`
`Primary Examiner~eba I. Elmore
`Assistant Examiner-McDieunel Marc
`Attorney, Agent, or Firm-Kenyon & Kenyon
`
`[57]
`
`ABSTRACT
`
`A system for configuring a process control system, e.g., a
`Fieldbus network, having intelligent field mounted devices
`coupled to a data communications bus. A software repre(cid:173)
`sentation of the process control system to be configured is
`first designed on a computer. Using the system, a user selects
`representations of the various field mounted devices to be
`included in the actual control system. The user then specifies
`which function blocks of each field mounted device are to be
`used and how those function blocks are to be linked. The
`computer is then coupled to the communications bus of the
`actual control system via an interface device and the con(cid:173)
`figuration and link data are downloaded to the field mounted
`devices of the control system. The computer can act as a bus
`master of the communications bus of the control system with
`the field mounted devices acting as slaves. The computer can
`also be disconnected from the control system communica(cid:173)
`tions bus and the control system will operate with one of the
`field mounted devices acting as the bus master.
`
`15 Claims, 30 Drawing Sheets
`
`JUNCTION
`BOX
`
`FIELDBUS
`
`37
`
`LIQUID
`STORAGE
`TANK
`
`VALVE
`
`40
`
`30
`FIELDBUS
`
`36
`
`Oracle Exhibit 1006, Page 1
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 1 of 30
`
`5,841,654
`
`32
`
`FIELDBUS
`
`37
`
`LIQUID
`STORAGE
`TANK
`
`VALVE
`
`40
`
`30
`
`FIELDBUS
`
`36
`
`FIG. 1
`
`Oracle Exhibit 1006, Page 2
`
`

`

`d•
`'JJ.
`
`• ~~.
`
`....
`~=.....
`
`zo
`
`~ N
`
`~,J;;,.
`
`'""'"'0
`'0
`QIO
`
`'JJ.=(cid:173)~
`~....
`...,
`~c
`
`No.
`
`}--- FIELDBUS
`
`Ul
`....
`00
`
`~ ~
`
`....
`0\
`Ul
`~
`
`INPUT BOARD /51
`
`I
`
`MAINBOARD
`
`52
`
`~O
`
`TRANSDUCER
`
`~2
`
`AID
`
`SWITCHES
`
`PROGRAMMING 1I55 76
`r-1 PROM ISUPPLY
`t
`t
`EEPROM 57
`58
`I RAM r
`I
`I
`IMODEM f-
`59
`DISPLAY BOARD
`
`I -
`
`CPU
`EEPROM
`RAM ,
`54
`
`/61
`POWER
`
`SUPPLY --
`--
`
`I
`
`60
`
`MAU
`
`DISPLAY
`CONTROLLER
`
`1/63
`
`64
`
`0000
`0000
`
`3
`
`FIG. 2
`
`Oracle Exhibit 1006, Page 3
`
`

`

`d•
`'JJ.
`
`• ~~.
`
`....
`~=.....
`
`zo
`
`~ N
`
`~,J;;,.
`
`'""'"'0
`'0
`QIO
`
`'JJ.=(cid:173)~
`~....
`...,
`~c
`
`~o.
`
`Ul
`....
`00
`
`~ ~
`
`....
`0\
`Ul
`~
`
`-
`
`FIELDBUS
`
`I
`I
`I
`I
`I
`I
`I
`I
`I
`-l
`
`1 - - - - - - - - - ,
`,
`I
`I
`I
`'--1
`I
`I
`
`I
`
`II
`
`TRANSDUCER
`
`J
`
`-- HARDWARE
`
`INPUT
`
`I---
`
`I
`
`I
`
`ANALOG
`INPUT
`FUNCTION
`BLOCK
`
`--
`
`I
`
`I 70
`,
`
`J
`
`---.
`I
`
`11
`PID
`CONTROLLER
`FUNCTION
`BLOCK
`
`r-
`
`GENERAL
`PURPOSE
`ARITHMETIC
`BLOCK
`
`-
`
`--
`
`r-
`
`),-72
`
`-
`
`I
`
`IL
`
`FIG. 3
`
`Oracle Exhibit 1006, Page 4
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 4 of 30
`
`5,841,654
`
`t"')
`CO
`\
`
`"
`w
`u-
`>
`w
`0
`>-
`<{
`.....J
`a..
`en-
`
`0
`
`•
`
`<..?-lL..
`
`>-
`a::
`
`0~w~
`
`~
`
`::::)
`a..
`u
`
`00"-
`
`\
`
`~"-
`
`~.....
`
`~w
`::::)u
`0..>
`ZW
`-0
`
`"lI:t
`CO
`
`\
`en
`
`z0-
`
`~<
`
`{
`u
`-
`
`z:
`
`:::)
`~
`~
`0
`U
`<{
`~
`<{
`0
`
`Oracle Exhibit 1006, Page 5
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 5 of 30
`
`5,841,654
`
`MAIN ROUTINE
`
`/1000
`
`1002
`
`GENERATE
`OPENING
`WINDOW
`
`1004
`
`1006
`
`DETERMINE
`SELECTED
`COMMAND OR
`FUNCTION
`
`1010
`
`CALL FILE
`COMMAND
`SUBROUTINE
`
`1012
`
`FIG. SA
`
`Oracle Exhibit 1006, Page 6
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 6 of 30
`
`5,841,654
`
`FILE COMMAND SUBROUTINE
`
`IF NEW
`CONFIGURATION
`FILE
`
`DETERMINE
`SELECTED FILE
`COMMAND
`
`CALL
`CONFIGURATlON
`SUBROUTINE
`
`2010
`
`IF
`SAVE
`
`IF OPEN LINK
`FILE
`
`CALL LINK
`SUBROUTINE
`
`IF DOWNLOAD
`LINK FILE
`
`DOWNLOAD
`LINK FILE
`TO FIELD
`DEVICES
`
`2018
`
`RETURN TO
`BLOCK 1006 OF
`MAIN ROUTINE
`
`2022
`
`FIG. 58
`
`Oracle Exhibit 1006, Page 7
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 7 of 30
`
`5,841,654
`
`CONFIGURATION SUBROUTINE
`
`OPEN
`CONFIGURATION
`WINDOW AND
`GENERATE
`REPRESENTATION
`OF MASTER
`COMPUTER
`
`3008
`
`DETERMINE
`SELECTED
`COMMAND.
`FUNCTION OR
`DEVICE
`
`IF FILE
`COMMAND
`CALL FILE
`COMMAND
`SUBROUTINE
`
`3030
`
`FIG. 5C-1
`
`DISPLAY
`AVAILABLE
`DEVICE
`FUNCTIONS
`
`Oracle Exhibit 1006, Page 8
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 8 of 30
`
`5,841,654
`
`GET INPUT
`IDENTIFYING
`SELECTED
`INTERFACE
`
`3014
`
`DISPLAY
`SELECTED
`INTERFACE
`DEVICE
`
`3020
`
`GET INPUT
`IDENTIFYING
`SELECTED
`INTERFACE
`
`GET INPUT
`IDENTIFYING
`SELECTED
`FUNCTION
`
`DISPLAY
`SELECTED
`FIELD DEVICE
`
`DISPLAY
`FUNCTION
`BLOCK
`
`FIG. 5C-2
`
`Oracle Exhibit 1006, Page 9
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 9 of 30
`
`5,841,654
`
`BEGIN LINK
`FILE
`SUBROUTINE
`AND DISPLAY
`FUNCTION LINK
`WINDOW
`
`DETERMINE
`SELECTED
`COMMAND.
`FUNCTION OR
`DEVICE
`
`IF LINK TOOL
`SELECTED
`
`LINK FILE SUBROUTINE
`
`GENERATE FILL
`CONTROL
`FUNCTION
`WINDOW
`
`IF FUNCTION IN
`CONFIGURATION
`WINDOW TO BE
`COUPLED
`IF FUNCTION IN
`FUNCTION LINK
`WINDOW
`
`DETERMINE
`SELECTED FUNCTION IN
`CONFIGURATION WINDOW TO BE
`COUPLED; FUNCTION IN FUNCTION
`LINK WINDOW; FUNCTION IN
`CONFIGURATlON WINDOW FOR
`SETTING A PARAMETER.
`OR FILE COMMAND
`
`IF FUNCTION IN
`CONFIGURATION
`WINDOW FOR
`SETTING A
`PARAMETER
`
`IF FILE
`COMMAND
`
`4038
`
`CALL FILE
`COMMAND
`SUBROUTINE
`
`FIG. 5D-1
`
`Oracle Exhibit 1006, Page 10
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 10 of 30
`
`5,841,654
`
`4014 ~'---­
`GET INPUT
`IDENTIFYING
`SELECTED
`FUNCTION FILL
`COLORS
`
`GENERATE
`REPRESENTATION
`OF SELECTED
`FUNCTION IN
`FUNCTION LINK
`WINDOW
`
`GENERATE
`DETAILED FUNCTION
`BLOCK DIAGRAM
`
`DISPLAY LIST OF
`FUNCTION PARAMETERS
`AND INPUTS AND
`OUTPUTS
`
`4022
`
`FIG. 5D-2
`
`Oracle Exhibit 1006, Page 11
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 11 of 30
`
`5,841,654
`
`100
`
`<=1 104 106
`-" fllE/HElpJ
`102
`
`SYSTEM CONFIGURATOR
`
`IV]A
`
`110
`
`/1..-
`
`I
`
`I
`
`FIG. 6A
`
`Oracle Exhibit 1006, Page 12
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 12 of 30
`
`5,841,654
`
`=>
`
`filE HELP
`
`114
`
`c:::::I
`
`I.e;;
`II:
`
`SYSTEM CONFIGURATOR
`
`IvlA
`
`TEST.FBC
`
`IvlA
`
`I,..-
`
`110
`
`,/
`
`v 112
`
`I
`
`I
`
`FIG. 68
`
`Oracle Exhibit 1006, Page 13
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 13 of 30
`
`5,841,654
`
`<=1
`FILE HELP
`
`I
`~}14
`
`116/
`
`I
`
`SYSTEM CONFIGURATOR
`
`IvlA
`
`=1
`NEW INTERFACE
`MANUFACTURER
`I ~116a
`lsmar
`INTERFACE
`1+J.. ,l16b
`IBC1
`DEV. REV. DO. REV.
`I } 116c
`110
`11
`CARD NUMBER [[] ~ ~116d
`I[QK] ICANCELII HELP I I
`.
`..
`116e
`
`IvlA
`
`,
`
`110
`
`.;
`
`v112
`
`I
`
`FIG. 6C
`
`Oracle Exhibit 1006, Page 14
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 14 of 30
`
`5,841,654
`
`=
`FILE HELP
`
`SYSTEM CONFIGURATOR
`
`Ivl~
`
`114
`
`TEST.FBe
`
`=1
`l.--'" ~BC1(SERIAL PORT 1)
`118
`
`Ivl~
`
`110
`
`t.--
`
`..
`
`v l12
`
`'"
`
`I
`
`I
`
`FIG. 6D
`
`Oracle Exhibit 1006, Page 15
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 15 of 30
`
`5,841,654
`
`c:::l
`
`FILE HELP
`
`SYSTEM CONFIGURATOR
`
`Ivl6
`
`c:::::I
`
`c:::ll
`
`NEW DEVICE
`MANUFACTURER
`Ismar
`.f;;;
`~CI(SERIA DEVICE TYPE
`!LD302
`(CHANN
`DEV. REV. DD. REV.
`110
`122- 11
`TAGS
`ILD301_1
`I~
`ADDRESS I0
`'-122e
`I00 ICANCELII HELP II
`
`I -1220
`B
`-122b
`I ~122c
`I v122d
`
`Ivl6
`
`--
`110
`
`- ....-112
`
`I
`
`114
`"-
`118
`
`120
`
`-
`
`--
`
`I
`
`FIG. 6E
`
`Oracle Exhibit 1006, Page 16
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 16 of 30
`
`5,841,654
`
`==1
`filE HELP
`
`SYSTEM CONFIGURATOR
`
`Iv l6
`
`=
`b
`
`TEST.FBC
`118~ BC 1(SERIAL PORT1 )
`{CHANNEL O. ADDRESS OJ
`co LD301_1 {LD302,ADDRESS OJ
`124
`
`120
`
`114
`
`I
`
`Iv l6
`
`.. I.-
`
`110
`
`~112
`
`...
`
`I
`
`FIG. 6F
`
`Oracle Exhibit 1006, Page 17
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 17 of 30
`
`5,841,654
`
`==>
`
`fiLE HELP
`
`SYSTEM CONFIGURATOR
`
`Ivl6
`
`c::::I
`
`TEST.FBC
`4 ~
`11
`~BCl (SERIAL PORTl)
`8- I.-
`11
`DIICHANNEL 0, ADDRESS 011
`-
`120
`t@ LD301_1 ILD302,ADDRESS 01
`124
`~ TT302_1 ITT302,ADDRESS 11
`6-- L--
`12
`
`/ '
`
`Ivl 6
`
`110
`
`/ "
`
`.....112
`
`...
`
`I
`
`I
`
`FIG. 6G
`
`Oracle Exhibit 1006, Page 18
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 18 of 30
`
`5,841,654
`
`=::I
`
`fiLE HELP
`
`SYSTEM CONFIGURATOR
`
`Iv l6
`
`TEST.FBC
`11
`4
`~1FUNCTION BLOCK INSTANTIATION H28
`'L:~ BCl (SERI
`8
`11
`TAG
`ICHAN~ ILD302_PID
`I ~128b
`120
`--~l!m.Q FUNCTION BLOCK TYPE
`124
`--- ~TT30 IPIO
`IU>tUICANCEL II HELP II
`6-
`12
`
`Iv l6
`
`I...-
`
`~
`
`110
`
`1.--112
`
`-
`
`I+~ ~1280
`
`=::I
`
`~
`
`l -
`
`I
`
`I
`
`FIG. 6H
`
`Oracle Exhibit 1006, Page 19
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 19 of 30
`
`5,841,654
`
`c::::o
`
`FILE HELP
`
`SYSTEM CONFIGURATOR
`
`Ivl~
`
`Ivl~
`
`-
`
`:...-
`
`110
`
`v 112
`
`-
`
`=:0
`
`.r
`
`TEST.FBC
`~Cl (SERIAL PORTlI
`LD ICHANNEL O. ADDRESS 01
`t:® LD301_1 ILD302~DRESS 01
`~ TT302_1 {TT302~DRESS 11
`==[] 1TROTT 1
`=1]1 TROTT 1
`=§ TT302 _ PIO IPIDI
`!TT302 _ AI IAllnl
`
`14 -
`18
`----
`120
`124
`6- - ~
`12
`13
`0
`13
`2~
`4
`13
`6
`13
`
`~
`
`11
`
`~
`
`I
`
`I
`
`FIG. 61
`
`Oracle Exhibit 1006, Page 20
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 20 of 30
`
`5,841,654
`
`SYSTEM CONFIGURATOR
`
`fiLE ~ELP
`
`NEW FILE 2
`
`TEST.FBC
`
`140
`
`.
`........................
`
`112
`IBC1 (SERIAL PORT1 ) ] - -1L118
`ICHANNEL 0, ADDRESS OJ
`120
`co LD301_1 ILD302,ADORESS
`124
`co TT302_1 ITT302,ADORESS
`126
`A I TROTT J
`130
`AI TROTT J
`132
`TT302 _ PIO IPIOJ
`134
`TT302 _ AI IAI#1J
`136
`
`FIG. 6J
`
`Oracle Exhibit 1006, Page 21
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 21 of 30
`
`5,841,654
`
`=1
`FILE HELP
`
`SYSTEM CONFIGURATOR
`
`Ivl6
`
`Ivl6 c:::o
`TEST.FBC
`NEW FILE 2
`c:::oT
`........................ ~
`........................
`::::::::::::::::::::::::
`IBC 1(SERIAL PORT1)]
`::::::::::::::::::42: '~TOOLBAR
`J {CHANNEL 0 ADDRESS 01
`.................1 1-:-
`~ ~1
`•
`~ LD301_1 lLD302.ADDRESS
`: : : : : : : : : : : : : : : : : : : : :
`--
`~ TT302_1 lTT302.ADDRESS fool
`~ : : : : : : : : : : : : : : : : : : :
`III I TROTT 1
`:::::::::::::::: :f43~
`..
`.....................
`·....................
`III I TROTT 1
`:::::::::::::::: :14~~
`· ....................
`-gj TT302 _ PID {PIOI -
`·....................
`· ....................
`· .......................
`·.......................
`TT302 _ AI {AlllI---
`· .......................
`
`
`301
`'-1
`32
`134
`136
`
`I--
`
`Ivl6
`,...-
`
`-1
`
`12
`
`24
`26
`
`L..--
`
`140
`
`FIG. 6K
`
`Oracle Exhibit 1006, Page 22
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 22 of 30
`
`5,841,654
`
`=1
`FILE HELP
`
`SYSTEM CONFIGURATOR
`
`112
`
`/
`
`1 I I I. D 1)
`
`I
`
`I
`
`I¢
`
`I
`
`SET FILL COLOR-------,
`..........
`:::::f460:
`I 1 I I I I
`:: :: :: :: :: - I I I I
`PORT
`I
`I
`0, ADDRESS 01 I
`: : : : : : : : : : .....
`:: :: :f46:~
`SET FILL STYLE
`{LD302,ADDRESS
`140 T::iU~>~III~ ~ I¢~ ~~3102)DDRESS
`~I ~ I CANCEL I
`IHELP I ITT 1
`~
`~ ~
`~
`~
`
`>~
`
`~ 2 _ PID {PIDI
`~ 2 _ AI {Alln
`
`FIG. 6L
`
`Oracle Exhibit 1006, Page 23
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 23 of 30
`
`5,841,654
`
`<=1
`filE HELP
`
`SYSTEM CONFIGURATOR
`
`Ivl~
`
`-=f
`NEW FilE 2
`Tvl~ -=
`·.......................
`:::: ... :: :1:4-a:::::::::::
`
`TEST.FBC
`
`Ivl~
`
`BC1 (SERIAL PORT1)
`
`--
`
`-
`112
`
`140
`
`. . . . . . . . .. .
`·
`.:::::::::::
`:..
`- >-: : : : : : : : : : : : : : : : : : : : :
`·.. ... .... ... ... ... ..
`:::::::::::::::::::::
`...................~~
`· ............... ·14 .
`· ....................
`·....................
`· ....................
`·....................
`·.......................
`· .......................
`·.......................
`
`I-
`
`124
`
`~ LD301_1 ILD302,ADDRESS
`iQJ {TRDlO I
`PIO IP 01 1---- -
`138
`~I lD302
`-
`139
`
`I
`-
`l0302 _ AI IAI#11----
`
`0
`
`TT302_1 ITT302,ADDRE~
`
`-1
`
`26
`
`FIG. 6M
`
`Oracle Exhibit 1006, Page 24
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 24 of 30
`
`5,841,654
`
`SYSTEM CONFIGURATOR
`
`v.o.
`
`fiLE ~ELP
`
`=
`
`140
`
`• • • • • • • • • • • • • • • • • • • I • • • •
`
`" - - - " " ~~
`
`TEST.FBC
`v .0.
`D LD301_1 {LD302)DDRE
`~.-.r 124
`{ TROLO }
`138
`L0302 _ PIO {PIO}
`139
`L0302 _ AI {AI#l}
`D TI302_1 {TT302)DDRE
`126
`.1. {TROTT}
`.1. {TROTT}
`TT302 _ PIO {PIO}
`ITT302 _ AI {AI#ll I
`
`158
`159
`
`112
`
`FIG. 6N
`
`Oracle Exhibit 1006, Page 25
`
`

`

`d•
`'JJ.
`
`• ~~.
`
`....
`~=.....
`
`zo
`
`~ N
`
`~,J;;,.
`
`'""'"'0
`'0
`QIO
`
`'JJ.=(cid:173)~
`~....
`
`NU
`
`l
`o....,
`~c
`
`SELECT THE OUTPUT PARAMETER: LD302 - AI -LD302-.A1
`
`INPUT- #
`
`CLAMP_ HIGH
`
`CLAMP_ LOW
`
`CLAMP- DOM
`
`OUT
`
`MODE_ PER
`
`MANUAL SP
`
`MODE
`- - - -
`
`MODE
`SELECTION
`
`y~ 1600
`
`MODE_BLK
`PT(AU) 1 - - - - - - - - ,
`
`FILTER
`DAMPING
`,
`
`h
`ALARM I
`DISC
`Il-J OUT- D
`
`___ _____ ____- - .1 HLLlM
`LO_L1M-
`UUC(AM)
`ALARM_HTS
`ALARM_HTS
`
`I
`
`'
`
`PARAMETER DESCRIPTION
`THIS PARAMETER IS THE PROCESS VARIABLE OF THE ANALOG INPUT BLOCK IN ENGINEERING UNITS IN AUTO MODE AND /V
`IS THE VALUE SPECIFIED BY THE OPERATOR/ENGINEER IN MAN.
`ICANCEL I
`I OK
`I
`
`I HELP I
`
`IL160b
`
`FIG. 60 p
`
`Ul
`....
`00
`
`0\
`Ul
`~
`
`Oracle Exhibit 1006, Page 26
`
`

`

`d•
`'JJ.
`•
`
`~~.
`
`....
`~=.....
`
`zo
`
`~ N
`
`~,J;;,.
`
`SELECT THE OUTPUT PARAMETER: LD302 - PID - LD302_ PID
`
`160
`
`RCAS_OUTj
`
`"\
`
`ROUT_IN
`
`l
`OUTPUT
`PID
`ALGORITHIM f---- SELECTION I--
`
`bBKCAL_OUT
`
`SETPOINT
`SELECTION
`
`SP
`
`....--
`
`-
`
`PP
`
`PV
`(asP)
`SCALING
`PV AND
`DEVIATION
`ALARM
`FEED
`FORWARD
`GAIN
`
`/'
`
`CAS_INC-
`SETPOINT
`.--- SELECTION
`Y
`ACAS_IN
`
`INC
`
`I--
`
`PV
`FILTERS
`
`FEED
`FF_ VALC I--- FORWARD
`SCALING
`TRACK
`SCALING
`
`TRK_ VALC -
`
`TRK_IN_OC
`BKCAL_INC
`
`,.-
`
`1600
`
`'""'"'0
`'0
`QIO
`
`'JJ.=(cid:173)~
`~....
`
`N0
`
`'1
`o....,
`~c
`
`.----
`.----
`
`OUTPUT
`SCALING .....
`ROUT_ OUT 0 - -
`
`'----
`
`OUTPUT
`LIMIT
`
`I---
`
`POUT
`
`"-
`PARAMETER DESCRIPTION
`THIS PARAMETER IS THE REMOTE SETPOINT VALUE, WHICH MUST COME FROM ANOTHER FIELDBUS BLOCK, OR ADCS
`BLOCK.
`
`~
`
`...
`
`I OK
`
`I
`
`ICANCEL I
`
`I HELP I
`
`160b
`
`FIG. 6P e....
`
`Ul
`....
`
`0\
`Ul
`~
`
`Oracle Exhibit 1006, Page 27
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 27 of 30
`
`5,841,654
`
`SYSTEM CONFIGURATOR
`
`FILE HELP
`-
`-
`
`<=I
`
`NEW FILE 2
`:l'48: :::::::::::::150: ::
`142
`::..
`..::::..
`..:::::
`....
`.
`. .
`n:cTO~OLB~AR
`
`140
`
`........................
`•• ~:::::!J
`
`112
`
`TEST.FBC
`v A
`'" LD301_1 {LD302,ADDRE
`{ TRDLD J
`LD302 _ PID {PIDI
`LD302 _ AI {AI#1}
`'" TT302_1 {TT302,ADDRE S
`J.
`{TRDTT I
`J.
`{TROTT I
`TT302 _ PIO IPIDJ
`ITT302 - AI IAI#ll I
`
`FIG. 6Q
`
`Oracle Exhibit 1006, Page 28
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 28 of 30
`
`5,841,654
`
`SYSTEM CONFIGURATOR
`
`filE ~ElP
`
`<:::I
`
`NEW FilE 2
`:146: :::::::::::::1$0: ::
`
`........................
`
`•• ~:::::::!I
`
`151
`
`TEST.FBC
`
`v ~
`
`{ TRDlD I
`[lD302 _ PID {PIDII
`
`CAS _IN
`I
`I
`IN
`o OUT
`C SP
`
`112
`138
`
`FIG. 6R
`
`Oracle Exhibit 1006, Page 29
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 29 of 30
`
`5,841,654
`
`e::::tl
`fiLE HELP
`
`SYSTEM CONFIGURATOR
`
`v A
`
`III
`
`I
`
`I
`
`•
`
`175
`1750
`175b
`175c
`
`c=l
`IvlA IIIc=l
`NEW FILE 2
`....
`- ~ =1
`PARAMETER VALUE
`· ...
`It • • PARAMETER TAG
`..
`..
`~ KSP
`.... CURRENT VALUE
`....
`..
`~ KO
`...
`·... DESIRED VALUE
`·...
`I
`'" . 10
`.... OSAVE VALUE TO CONFIGURATION FILE
`·...
`·... ISEND IOOICANCELIIHELPI
`·...
`·...
`........................ -~ 1
`·.......................
`· .......................
`I I
`
`TEST.FBC
`~ SIP
`I
`.
`:
`
`I
`I
`I
`I
`I
`I
`
`I
`
`•
`I
`I
`
`I
`I
`
`I IA A
`.." -"
`112
`
`-
`....
`
`....-
`
`'\IV
`
`I
`
`FIG. 65
`
`Oracle Exhibit 1006, Page 30
`
`

`

`u.s. Patent
`
`Nov. 24, 1998
`
`Sheet 30 of 30
`
`5,841,654
`
`700
`
`I
`
`I
`
`COMPUTER
`
`V702
`
`A ~
`
`703
`
`B. , -
`
`704
`
`C ~
`
`705
`
`D I..-
`
`706
`
`E.v
`
`707
`
`708 ....- F
`
`709./ G
`
`710-- H
`
`711./
`
`I
`
`FIG. 7
`
`Oracle Exhibit 1006, Page 31
`
`

`

`5,841,654
`
`1
`WINDOWS BASED NETWORK
`CONFIGURATION AND CONTROL METHOD
`FOR A DIGITAL CONTROL SYSTEM
`
`FIELD OF THE INVENTION
`
`The present invention relates to process control systems,
`and more particularly, to methods and apparatus for config(cid:173)
`uring and controlling digital control system networks and
`devices, e.g., Fieldbus networks.
`
`BACKGROUND OF THE INVENTION
`Process control relates to the control of processes, e.g.,
`manufacturing processes, through the use of control devices
`including sensors, e.g.,
`temperature sensors, pressure
`sensors,
`flow sensors, and digital computers. Presently,
`many sensors and other types of control devices include a
`central processing unit, memory for a program, e.g., func(cid:173)
`tion routines, parameters and control variables. Control
`devices which include CPUs are often referred to as smart
`devices.
`Smart devices are often programmed to perform a variety
`of functions, e.g., convert pressure into a value representing
`volume or convert a command into a signal used to move a
`valve. Functions are frequently performed by software as
`well as hardware. A function, whether implemented in
`hardware or software, can be characterized as a function
`block. Each function block of a device may have a plurality
`of inputs and outputs, as well as internal parameters and
`internal signals which are used to perform the function.
`A control system may include a plurality of smart devices
`coupled together via, e.g., a digital bus operating according
`to a preselected communication protocol. A Fieldbus is a bus
`which operates according to the Fieldbus communication
`protocol which is a bidirectional digital communications 35
`protocol. A Fieldbus network is a plurality of smart devices
`coupled together via a Fieldbus.
`The Fieldbus communications protocol is described in
`"SMAR, FIELDBUS TUTORIAL", which is published by
`SMAR INT'L CORP., 1993 which is hereby expressly 40
`incorporated by reference. As discussed in the cited
`reference,
`the Fieldbus communications protocol permits
`devices coupled to a Fieldbus to communicate system con(cid:173)
`figuration information, sensed values, function parameters,
`etc. between each other and a master computer over a 45
`Fieldbus.
`Access to the Fieldbus may be controlled using a token
`system, wherein a token is used to indicate which device is
`authorized to initiate a transaction on the Fieldbus. In such
`an embodiment, a master device or computer, sometimes 50
`referred to as a link active scheduler, serves to insure that the
`token is passed to each device requesting to initiate a bus
`transaction according to a preselected scheduling order.
`In addition to the "SMAR, FIELDBUS TUTORIAL"
`additional references which describe the Fieldbus commu- 55
`nications protocol include FIELDBUS FOUNDATIONTM,
`Fieldbus Specification, Function Block Application Process,
`Parts 1 and 2, Revision PS 1.0, Apr. 27, 1995 which are
`hereby expressly incorporated by reference. The cited Field(cid:173)
`bus Specification documents, are useful
`in providing 60
`insights into the communication protocols used for commu(cid:173)
`nicating information between various function blocks imple(cid:173)
`mented in devices coupled to Fieldbus networks and for
`providing a better understanding of function blocks in
`general.
`While Fieldbus systems offer several advantages over
`prior art control networks, because a plurality of different
`
`2
`smart devices may be coupled to a single Fieldbus, and each
`device must often be configured with, e.g., control and
`parameter information so that it will properly respond to
`other devices on the bus and perform the various functions
`5 desired, it has become a relatively complicated process to
`program field mounted devices coupled to a Fieldbus.
`The difficulty in configuring Fieldbus devices and a
`Fieldbus network is often complicated by the limited screen
`size provided on field mounted devices and the limited
`10 number of inputs provided on such devices. With a relatively
`limited number of inputs on a device, e.g., one or two
`buttons, it is often necessary to scroll through a plurality of
`menus, in a preselected sequence, until the device is prop(cid:173)
`erly set. Errors in setting parameter values may require an
`15 operator to scroll through several screen displays before the
`parameter values can be reset.
`In addition, it may be difficult or impossible to configure
`the entire network using the inputs and display incorporated
`into a single field mounted device requiring an operator to
`20 individually configure a plurality of field mounted devices
`by physically visiting and setting each device.
`Accordingly, there is a need for an improved method and
`apparatus for configuring a Fieldbus network so that an
`25 operator can configure the entire network with a minimal
`amount of difficulty. Furthermore, it is desirable that the
`operator be able to visually see a graphical representation of
`the Fieldbus network including the devices coupled thereto
`when configuring the network. It is also desirable that the
`30 operator be able to easily set and reset parameter and control
`information for each of the system devices from a single
`location.
`It is also desirable that
`the configuration method and
`apparatus be capable of being used from any point on the
`Fieldbus, e.g., either in a control room or in the field near a
`device on the Fieldbus.
`
`SUMMARY OF THE INVENTION
`
`The present invention is directed to methods and appa(cid:173)
`ratus for configuring digital control system networks and
`devices, e.g., Fieldbus networks.
`In accordance with the present invention, a computer, e.g.,
`a notebook personal computer, running a WINDOWSTM
`based configuration and network control program, imple(cid:173)
`mented in accordance with the present invention, is used as
`a network configuration device.
`In accordance with the present invention, a graphical
`representation of the various elements of a Fieldbus network
`are illustrated as icons linked together by a line representing
`a Fieldbus.
`In one embodiment, the graphical representation of the
`Fieldbus network is created by first displaying an icon
`representing a computer. After the computer icon is dis(cid:173)
`played a user is permitted to select an interface device, for
`coupling the computer to the fieldbus network to be config-
`ured or controlled, from a menu of available interface
`devices. Upon selection of an interface device, an interface
`icon representing the interface is added to the graphic
`representation of the Fieldbus network with the interface
`icon being linked to the computer icon.
`Once an interface has been selected, a user can select from
`a list of possible field mounted devices, field mounted
`devices which are part of the Fieldbus network to be
`65 configured. Upon the selection of each field mounted device
`invention generates an icon
`the program of the present
`representing the selected device coupled to the fieldbus
`
`Oracle Exhibit 1006, Page 32
`
`

`

`5,841,654
`
`5
`
`3
`network. As part of the device selection process, a user is
`permitted to assign a TAG name to the field mounted device,
`and an address. Upon configuration, the address for a device
`is set to match the address of an actual field mounted device
`to which the selected device corresponds.
`In the above described manner, the program of the present
`invention, in response to device selections and inputs from
`an operator, generates a graphical representation of the
`actual devices which comprise the Fieldbus network to be
`configured. At the same time the graphical representation of
`the Fieldbus network to be configured is generated a con(cid:173)
`figuration file which includes a list of the devices in the
`network, the tag names, and the addresses assigned to the
`devices is generated.
`After one or more devices have been selected to be
`included in the network to be configured and thus are
`incorporated into the graphical representation of the Field(cid:173)
`bus network, an operator may select device functions which
`are to be used. In one exemplary embodiment, this is done
`by using a mouse and clicking on the icon of a field mounted
`device. The computer program of the present
`invention
`detects the selection of the device icon and generates a list
`of available functions supported by the selected device icon.
`The operator may then select one or more of the available
`functions,
`represented as function blocks to be used. 25
`Selected functions are represented as icons connected to the
`icon of the device to which they correspond. The configu(cid:173)
`ration file is updated to keep a record of the functions
`associated with each device which have been selected for
`use.
`After generation of a network configuration file, e.g., in
`the above described manner,
`the program of the present
`invention permits an operator to establish input and output
`links between device function blocks. Such links indicate
`the passing of data or other information between the selected
`inputs and outputs.
`The program of the present invention monitors the avail(cid:173)
`able computer input devices for input signals. Upon detect(cid:173)
`ing a file command to open or create a new link file, which 40
`is used to store information on the links between various
`functions, the program of the present invention opens a links
`window. In one embodiment, the links window is displayed
`next
`to a configuration window in which the tree like
`representation of the Fieldbus network and the devices 45
`comprising the network is illustrated.
`In accordance with the present invention, function blocks
`in the configuration window can be copied to the links
`window using, e.g., a mouse to select and drag function
`blocks to be copied. As function blocks are copied into the 50
`links window, the links file is updated to maintain a record
`of the functions that have been copied to the links window.
`The record may include, e.g., the tag name of the function,
`the tag name of the device to which the function belongs, the
`device addresses, and a record of the functions, parameter 55
`values, and the connection of the function inputs and outputs
`relative to other function blocks copied to the links window.
`Once function blocks have been copied into the links
`window, where, in one embodiment, they are represented as
`circles with the function's tag name and device's tag name 60
`displayed on the circle, the function block inputs and outputs
`may be selected for linking.
`The program of the present invention, detects the selec(cid:173)
`tion of a function block displayed in the links window and,
`upon detection of the selection of a function block generates 65
`a detailed block diagram of the function block illustrating
`the inputs and outputs of the function block. Each input and
`
`4
`output may represent, e.g., a different variable or signal that
`may be transmitted to, or received from, another function
`block or device.
`Once the detailed function block is displayed, a user
`selects an input or output to be linked to another function
`block. In the exemplary embodiment, this is done by using
`a mouse to click on the illustrated input or output which is
`then highlighted by the program. After making an input/
`output selection, the program removes the detailed diagram
`10 of the function block from the screen and returns to the link
`window to provide the operator the opportunity to select
`another function block input or output to couple the previ(cid:173)
`ously selected input/output.
`After an input and an output are selected for linking in the
`15 above described manner, the program generates a line con(cid:173)
`necting the functions which have been linked to represent
`the link existing therebetween. The link file is updated to
`indicate that the selected inputs and outputs are to be linked.
`After creating a link file in the above described manner,
`indicating how information should be exchanged between
`function blocks of one or more devices, the configuration
`and link file may be downloaded to the field mounted
`devices.
`The downloading process involves providing to each field
`mounted device, using the selected interface, all or some of
`the information stored in the link file. The link file infor(cid:173)
`mation is transmitted over the Fieldbus using Fieldbus
`compliant signals.
`In the above described manner, a computer, e.g., a por-
`table notebook computer, using a program operating accord(cid:173)
`ing to the present invention, can be used to configure and
`control an entire Fieldbus network. By permitting an opera(cid:173)
`tor to configure the network by generating a graphical
`35 representation of a Fieldbus network and the devices
`included therein, and then by permitting an operator to link
`inputs and outputs of function blocks of various field
`mounted devices in a graphical manner, Fieldbus network
`configuration is greatly simplified.
`Other features and advantages of the method and appa(cid:173)
`ratus of the present invention are described below.
`
`20
`
`30
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a schematic representation of a representative
`industrial process control system with a Fieldbus showing a
`computer coupled to the Fieldbus via an interface device.
`FIG. 2 is a block diagram of a typical field mounted
`device for coupling to a Fieldbus.
`FIG. 3 is a block diagram illustrating function blocks
`included in the field mounted device of FIG. 2.
`FIG. 4 is a block diagram of a computer used in the
`operation of the present invention.
`FIGS. 5A through 5D are flow diagrams illustrating the
`operation of the computer of FIG. 4, in accordance with the
`present invention.
`FIGS. 6A through 6S illustrate screen displays generated
`by an embodiment of the present invention.
`FIG. 7 illustrates a Fieldbus network including a control
`computer coupled by a Fieldbus to nine field mounted
`devices.
`
`DETAILED DESCRIPTION
`
`FIG. 1 is a schematic representation showing a computer
`20 coupled to a Fieldbus 30 of a representative process
`control system via an interface device 10. In the represen-
`
`Oracle Exhibit 1006, Page 33
`
`

`

`5,841,654
`
`5
`tative system of FIG. 1, which is used to control and monitor
`a liquid storage tank 40, the Fieldbus 30 is connected to
`several components such as a junction box 32, a temperature
`sensor 34, a pressure sensor 36 and an interface 37 for a
`valve 38.
`The junction box 32 is used to couple together multiple
`branches of a Fieldbus system, as shown in FIG. 1.
`The temperature sensor 34, which is coupled to the
`Fieldbus 30, monitors the temperature of the liquid storage
`tank 40 and generates signals indicative of the temperature 10
`for transmission over the Fieldbus. A commercially avail(cid:173)
`able temperature sensor which can be used as the tempera(cid:173)
`ture sensor 34 is the TT302 temperature sensor manufac(cid:173)
`tured by Smar Equipamentos Ind. Ltda. of Brazil.
`The pressure sensor 36, which is coupled to the Fieldbus 15
`30, monitors the pressure of the storage tank 40 and gener(cid:173)
`ates signals indicative of the pressure for transmission over
`the Fieldbus. A commercially available pressure sensor
`which can be used for such a purpose is the LD302 pressure
`sensor manufactured by Smar Equipamentos Ind. Ltda. of 20
`Brazil.
`The interface 37, which serves to convert bet-ween digital
`Fieldbus signals and analog 4-20 rnA signals, is used to
`control a valve 38. The valve 38 controls the flow of fluid
`into or out of the storage tank 40 in response to signals
`placed by a controlling device on the Fieldbus 30. The valve
`control signals are received by the interface 37 which, in
`response, generates a corresponding analog 4-20 rnA con(cid:173)
`trol signal which controls the actuation of the valve 38. The
`interface 37 can be implemented using an FI302 Fieldbus 30
`interface module manufactured by Smar Equipamentos Ind.
`Ltda. of Brazil.
`The interface device 10 allows the computer 20 to trans(cid:173)
`mit and receive signals on the Fieldbus 30. As a result, the 35
`computer 20 can monitor signals generated by sensors such
`as the temperature sensor 34 and the pressure sensor 36. The
`computer 20 can also generate control signals to control
`devices such as the valve 38, which is coupled to the
`Fieldbus 30 via the interface 37.
`The interface device 10 is described more fully in U.S.
`patent application, Ser. No. 08/542,591,
`titled "COM(cid:173)
`PUTER TO FIELD BUS CONTROL SYSTEM
`INTERFACE", filed on Oct. 13, 1995, which is hereby
`expressly incorporated by reference. A commercially avail- 45
`able device that can be used as the interface device is the
`BC1 interface device manufactured by Smar Equipamentos
`Ind. Ltda. of Brazil.
`The computer 20 operates in accordance with the method
`of the present
`invention, as will be described below in 50
`greater detail.
`In the system of FIG. 1, each field mounted device is an
`intelligent device capable of performing several different
`functions within the Fieldbus network to which the field
`mounted device is coupled. In addition to performing a 55
`parameter sensing or an actuation function, each field
`mounted device is capable of performing functions which
`control or affect other components of the Fieldbus network.
`The combination of such functions distributed among the
`field mounted devices coupled to a Fieldbus sys