DSCInt Proc with Lab VIEW 8 2 Motivation

  • Slides: 21
Download presentation
DSCInt. Proc with Lab. VIEW 8. 2 • Motivation • "Shared Variables" • Difference

DSCInt. Proc with Lab. VIEW 8. 2 • Motivation • "Shared Variables" • Difference to Lab. VIEW 7. 1 • New Configuration Tools

Background SCADA Backend Dim CS other Stuff (OPC. . ) DIM

Background SCADA Backend Dim CS other Stuff (OPC. . ) DIM

CS and Lab. VIEW DSC Module LV-DSC: SCADA + OPC DIM DSCInt. Proc Dim

CS and Lab. VIEW DSC Module LV-DSC: SCADA + OPC DIM DSCInt. Proc Dim CS DSCInt. Proc: Class interfacing DIM services and Lab. VIEW DSC

"Tags" (LV 7. 1) – "Shared Variables" (LV 8. . . ) • "Using

"Tags" (LV 7. 1) – "Shared Variables" (LV 8. . . ) • "Using the Shared Variable" http: //zone. ni. com/devzone/cda/tut/p/id/4679 • Shared Variable (SV) properties important for CS – NI (!) protocol of choice when transferring data among computers – a SV lives in a "Process" within a Shared Variable Engine (SVE) • a SVE may host more than one process: URL contains process name • one SVE per node: URL contains node name • a distributed system may use more than one SVE – SV available in Full Development System, does not require LV-DSC – but: DSC required to create SV programmatically – alarming and trending are SV properties provided by LV-DSC, these properties are available via the network – wait on a value change only available via • "Data. Socket Read. vi": does not require DSC, no "wait-on-multiple" • LV-DSC: provides "wait-on-multiple"

Differences for DSC between LV 8. . . and LV 7. 1 LV 8.

Differences for DSC between LV 8. . . and LV 7. 1 LV 8. . . consequence for LV 8. . . create on-the-fly no yes in principle nice, but required for runtime remote alarming no yes great, no need to send alarms via CS remote historic trending no yes great, no need to send trending via CS wait-on-change-multiple no yes great OPC connectivity yes none. . . "Monitor" development yes none. . . "Monitor" 4 runtime yes no, but. . . oohps! "Configurator" 4 runtime yes no, but. . . oohps! Create SVs on the fly is a must!

Remote Alarming DIM DSCInt. Proc LV 7. 1 Tags Call DSCAlarm DIM DSCInt. Proc

Remote Alarming DIM DSCInt. Proc LV 7. 1 Tags Call DSCAlarm DIM DSCInt. Proc Call SVs DSCAlarm. GUI LV 8. . .

Historic Trending DIM LV 7. 1 Tags DSCInt. Proc Citadel DB gs Ta DSCTrend

Historic Trending DIM LV 7. 1 Tags DSCInt. Proc Citadel DB gs Ta DSCTrend DIM DSCInt. Proc Call SVs DSCTrend. GUI LV 8. . . Citadel DB (remote access) Historic Trend Viewer

"Wait-On-Change-Multiple" example for DSCInt. Proc class

"Wait-On-Change-Multiple" example for DSCInt. Proc class

Runtime: (not) Monitoring SVs • the good old "Tag Monitor" no longer exists for

Runtime: (not) Monitoring SVs • the good old "Tag Monitor" no longer exists for SVs • Start->Programs->National Instruments->"Variable Manager" as sole possibility – can not be used as normal user – administrator privileges required – allows to change everything: "Variable Manager"

Runtime: (not) Configuring SVs • the good old "Tag Configurator" no longer exists for

Runtime: (not) Configuring SVs • the good old "Tag Configurator" no longer exists for SVs • Start->Programs->National Instruments->"Variable Manager" as sole possibility – – – can not be used as normal user administrator privileges required allows to change everything: "Variable Manager" does not allow to load/save settings, but changes are always persistent (stored in registry? ) useless for maintaining/setting up large numbers of SVs • we are forced to create SVs on-the-fly • since there is no "Tag Configurator", and we like to maintain SVs for production systems, we have to write our own tool

How-To Configure SVs LV 7. 1 LV 8. . . 1 (create CLASSNAMEtags. txt)

How-To Configure SVs LV 7. 1 LV 8. . . 1 (create CLASSNAMEtags. txt) create CLASSNAME_SVTemplate. csv 2 (create CLASSNAME_dim_dsc. txt) 3 (use the CSDBTool to create an object specific file for tag import) 4 (use the CSDBTool to create an object specific dim_dsc. xml file) 5 configure tags in the "Configurator" 6 modify database entry for DSCInt. Proc to to use dim_dsc. xml file use created csv-files. 7 use the CSDBTool to create object specific csv-files use the "SV Editor" of the CSDB Tool (configure IO-Server for OPC connection) • less steps with LV 8. . . • easier mass configuration • no "comfortable tool" available as the "Tag Configurator"

A. CSV-Template Files • created by maintainer of a class • must be copied

A. CSV-Template Files • created by maintainer of a class • must be copied to the. . . /data directory of the CSCB Tool by the user • keyword in "Description" – DIM 2 DSC: "on value change", write value of DIM service to SV – DSC 2 DIM: "on value change", publish value of SV as DIM service

B. Create CSV-Files

B. Create CSV-Files

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

C. Modify CSV Files Alternative: MS-Excel

D. Configuration of DSCInt. Proc in addition: name of database, lifespan, . . .

D. Configuration of DSCInt. Proc in addition: name of database, lifespan, . . .

E. Configure IO-Server for OPC Connectivity • • one IO-Server per OPC Server: easy

E. Configure IO-Server for OPC Connectivity • • one IO-Server per OPC Server: easy via "Variable Manager" IO-Servers can also be create by DSCInt. Proc and xml file

Status • Pros – – works fine for me (db) mass configuration improved a

Status • Pros – – works fine for me (db) mass configuration improved a lot can create SVs on-the-fly from DIM, compatible with DSCInt. Proc of CS 3. 00 • Cons – – most experiments use DSCInt. Proc of CS 3. 00 not yet well established at experiments mass configuration must be done with care DSC module provides no comfortable configuration for runtime systems