FLOW-X LEVEL 2 TRAINING 2...ü Flow meter Q.Sonic (uniform) ü Flow meter Q.Sonic plus (Modbus) ü...
Transcript of FLOW-X LEVEL 2 TRAINING 2...ü Flow meter Q.Sonic (uniform) ü Flow meter Q.Sonic plus (Modbus) ü...
—
—
CONFIDENTIAL
FLOW-X LEVEL 2 TRAININGFlow-Xpress Professional
—TOPICS
March 9, 2018 Slide 2
ü Application structure
ü Sheets & templates
ü Historical data archives
ü Redundancy
ü Debug online
ü Remote run / remote station
ü Communication lists
ü Communication drivers
ü Develop own communication driver
ü Use custom values
—SWITCH TO PROFESSIONAL MODE
March 9, 2018 Slide 3
Switch to professional mode
—APPLICATION STRUCTURE
March 9, 2018 Slide 4
—APPLICATION STRUCTURE
March 9, 2018 Slide 5
Sheets:
ü Application- and system sheets
ü Communication sheets
ü Driver sheets
ü Custom sheets
—SHEETS & TEMPLATES
March 9, 2018 Slide 6
—SHEETS & TEMPLATES
March 9, 2018 Slide 7
—HISTORICAL DATA ARCHIVES
March 9, 2018 Slide 8
—HISTORICAL DATA ARCHIVES
March 9, 2018 Slide 9
—REDUNDANCY
March 9, 2018 Slide 10
—REDUNDANCY
March 9, 2018 Slide 11
Enable/disable redundancy
Tags to synchronize
—REDUNDANCY
March 9, 2018 Slide 12
192.168.1.31
192.168.2.31
192.168.1.32
192.168.2.32
—DEBUG ONLINE
March 9, 2018 Slide 13
ü Check live values inside the flow computer
ü Check calculations of the flow computer using these live values
ü Check statuses
ü Debug communication drivers
—EXERCISE
March 9, 2018 Slide 14
ü Start Flow-Xpress and switch to Professional Mode
ü Read the application from the Flow-X
ü Select Debug / Debug online
ü Select the IP address of the flow computer
ü Browse through the sheets
ü Look up the run totalizers and check if they are running
ü If they are not running, check why they’re not running (you may also use the
web browser) and fix it
—DEVICE COMMUNICATION DRIVERS
March 9, 2018 Slide 15
ü Flow meter Krohne Altosonic V12ü Flow meter Caldon LEFM 380Ciü Flow meter Flowsic 600ü Flow meter FMC MPUü Flow meter Panametrics / GE GF868ü Flow meter Micro Motionü Flow meter Q.Sonic (uniform)ü Flow meter Q.Sonic plus (Modbus)ü Flow meter RMG USZ08ü GC ABB BTU 8100ü GC ABB NGC 8206ü GC Siemens Maxumü GC Siemens Sitransü GC Yamatake HGCü GC Danalyzerü GC Encal 3000ü GQA Angusü Tag list Omni V27
ü Flow meter ABB CoriolisMasterü Flow meter Micro Motion Coriolisü Flow meter E+H Promassü Flow meter Caldon LEFMü Flow meter Faure Herman 8400ü Densito meter Anton Paar L-dens 427ü Tag list Omni v24ü Tag list Omni v24 bi-dirü Tag list Omni v25
—COMMUNICATION LISTS
March 9, 2018 Slide 16
ü Modbus listü Modbus list (16 bits)ü Remote runü Remote station
—COMMUNICATION LISTS
March 9, 2018 Slide 17
—COMMUNICATION DRIVERS
March 9, 2018 Slide 18
Read onlyRead only
Writeable
ModbusMaster -> Com portsModbusClient -> Ethernet
—COMMUNICATION DRIVERS
March 9, 2018 Slide 19
Query definition
Tag items definition
—COMMUNICATION DRIVERS
March 9, 2018 Slide 20
Interval: Sample time * 0.1 secTimeout: Timeout value * 0.1 secRetries: Number of retries before go into sleepSleepTime: Sleep time * 0.1 sec
—COMMUNICATION DRIVERS
March 9, 2018 Slide 21
Type: 1 = Coil based2 = Register based
Address: Start address of the queryLength: Number of registersSize: Number of bits per register
—COMMUNICATION DRIVERS
March 9, 2018 Slide 22
SW: Function code of single writeMW: Function code of multiple writeMR: Function code of multiple read
—COMMUNICATION DRIVERS
March 9, 2018 Slide 23
Query: Link to the queryAddress: Modbus register nr.TagName: Internal tag nameDescription: Tag descriptionUnits: Units of the tag, e.g. m3DataType: Data type, xd_bit, xd_float, …Tag Function: Internal fxTag function to store
the value
—COMMUNICATION DRIVERS
March 9, 2018 Slide 24
Communication displays
—EXERCISE
March 9, 2018 Slide 25
Ø Add the following tags into the 16 bits taglist:
Ø Gas (USC: replace GM by GU)
Ø 340 mod1_GM_Run!IV_REV_CUM dword
Ø 342 mod1_GM_Run!GV_REV_CUM dword
Ø 344 mod1_GM_Run!BV_REV_CUM dword
Ø 346 mod1_GM_Run!MASS_REV_CUM dword
Ø 348 mod1_GM_Run!ENGY_REV_CUM dword
Ø Liquid (USC: replace LM by LU)
Ø 348 mod1_LM_Run!IV_REV_CUM dword
Ø 350 mod1_LM_Run!GV_REV_CUM dword
Ø 352 mod1_LM_Run!NSV_REV_CUM dword
Ø 354 mod1_LM_Run!MASS_REV_CUM dword
Ø 356 mod1_LM_Run!GSV_REV_CUM dword
Ø Compile the application to verify that there are no errors
—EXERCISE
March 9, 2018 Slide 26
Ø Create a new Modbus Client driver, named Comm_Dens to read the values every 5 seconds
Ø Use function code 3 in the MR column (Multiple Read)
Ø Use the following 16 bits addresses:
Ø 100 Density status as short
Ø 200 Gas density as floating point
Ø 300 Liquid density as floating point
Ø Configure the driver in Ports & Devices
Ø IP-address: 192.168.2.150
Ø Port: 503
Ø Add a communication display to setup the Modbus ID and show the values
Ø Write the application to the flow computer
Ø Configure Modbus ID 1
Ø Check if your driver is working well
—COMMUNICATION DEBUGGING
March 9, 2018 Slide 27
ü Communication displays on Flow-X or web browser
• Summary of actual driver values
ü Communication diagnostics through web browser
• Detailed communication messages
ü Through Flow-Xpress debug online
• Actual driver values plus extra status info
—COMMUNICATION DEBUGGING
March 9, 2018 Slide 28
Communication displays on Flow-X or web browser
—COMMUNICATION DEBUGGING
March 9, 2018 Slide 29
Communication diagnostics through web browser
—COMMUNICATION DEBUGGING
March 9, 2018 Slide 30
Debug Online
—CUSTOMS VALUES
March 9, 2018 Slide 31
ü Custom values that can be written to through Modbus or through a user calculation
ü Custom values can be used instead of transmitter values
ü Examples:
• Pressure: PT_CUSTOM_VAL
• Temperature: TT_CUSTOM_VAL
• Density: DT_CUSTOM_VAL
• Heating value: HV_CUSTOM_VAL
• Gas composition: COMP_C1_CUSTOMVAL, COMP_C2_CUSTOMVAL, COMP_CO2_CUSTOMVAL, …
—CUSTOM VALUES
March 9, 2018 Slide 32
Custom valueDensity
CommunicationDriver
User calculation (SetOnCondition)
Modbus
—CUSTOM VALUES
March 9, 2018 Slide 33
GM_Run GM_STN
—EXERCISE
March 9, 2018 Slide 34
Ø Add a custom calculation to write the gas- or liquid
density value to the custom observed density of the run:
DT_CUSTOM_VAL
Ø Add a custom calculation to write the density status to
the custom observed density status of the run:
DT_CUSTOM_FAIL
Ø Write the application to the flow computer
Ø Configure the observed density input type as ‘Custom
input’
Ø Check if the custom density is being used by the flow
computer