DSCIntProc with LabVIEW 8.2DSCIntProc with LabVIEW 8.2

• Motivation

• "Shared Variables"

• Difference to LabVIEW 7.1

• New Configuration Tools

Dim

BackgroundBackground

CS

DIM

SCADA Backendother S

tuff (OP

C..)

Dim

CSCS and LabVIEW DSC Module and LabVIEW DSC Module

CS

DIM

LV-DSC: SCADA + OPC

DSCIntProc

DSCIntProc: Class interfacing DIM services and LabVIEW DSC

"Tags" (LV7.1) – "Shared Variables" (LV8...)"Tags" (LV7.1) – "Shared Variables" (LV8...)

• "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

• "DataSocket Read.vi": does not require DSC, no "wait-on-multiple"

• LV-DSC: provides "wait-on-multiple"

Differences for DSC between LV8... and LV7.1Differences for DSC between LV8... and LV7.1

LV7.1 LV8... consequence for LV8...

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 yes none...

"Monitor" development yes 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 AlarmingRemote Alarming

DSCIntProcDIM Tags

DSCAlarm DSCAlarmGUICall

Call

LV7.1

DSCIntProcDIM SVs DSCAlarmGUILV8...

Historic TrendingHistoric Trending

DSCIntProcDIM SVsLV8...

DSCIntProcDIM Tags

DSCTrend DSCTrendGUICall

LV7.1

Citadel DB

Tags

Citadel DB

Historic Trend Viewer

(remote access)

"Wait-On-Change-Multiple""Wait-On-Change-Multiple"

example for DSCIntProc class

Runtime: (not) Monitoring SVsRuntime: (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 SVsRuntime: (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 SVsHow-To Configure SVs

LV7.1 LV8...

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)

use the CSDBTool to create object specific csv-files

4 (use the CSDBTool to create an object specific dim_dsc.xml file)

5 configure tags in the "Configurator" use the "SV Editor" of the CSDB Tool

6 modify database entry for DSCIntProc to use dim_dsc.xml file

modify database entry for DSCIntProc to use created csv-files.

7 (configure IO-Server for OPC connection)

• less steps with LV8...

• easier mass configuration

• no "comfortable tool" available as the "Tag Configurator"

A. CSV-Template FilesA. 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"– DIM2DSC: "on value change", write

value of DIM service to SV– DSC2DIM: "on value change",

publish value of SV as DIM service

B. Create CSV-FilesB. Create CSV-Files

C. Modify CSV FilesC. Modify CSV Files

Alternative: MS-Excel

C. Modify CSV FilesC. Modify CSV Files

Alternative: MS-Excel

C. Modify CSV FilesC. Modify CSV Files

Alternative: MS-Excel

C. Modify CSV FilesC. Modify CSV Files

Alternative: MS-Excel

C. Modify CSV FilesC. Modify CSV Files

Alternative: MS-Excel

D. Configuration of DSCIntProcD. Configuration of DSCIntProc

in addition: name of database, lifespan, ...

E. Configure IO-Server for OPC ConnectivityE. Configure IO-Server for OPC Connectivity

• one IO-Server per OPC Server: easy via "Variable Manager"

• IO-Servers can also be create by DSCIntProc and xml file

StatusStatus

• Pros– works fine for me (db)– mass configuration improved a lot– can create SVs on-the-fly– from DIM, compatible with DSCIntProc of CS 3.00

• Cons– most experiments use DSCIntProc 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