Embedded Files
How to add a variable to Logger and add an alarm -
How to add a variable to Logger and add an alarm -
In this example we would add CAM-1BL-DM Max Counts to the Logger and trigger the alarm when it exceeds 40000
To select the variable you want to add to the logger and open it in the database editor
Database Editor > Device Ops > Device variable ops > Device Variable
Navigate to the correct Device Type. eg. Point Grey Camera
Navigate to desired device eg. CAM-1BL-DM
Navigate to desired Variable eg. Max Counts
Ensure that there is an Alias for the device variable. If not, create one and set device variable. The Logger would not work if there is no Alias.
-----------------------------------------------------------------------------------------------------
To add the Variable to the plotter, within the database editor -
UI ops > Logger/Presets/Scans > Add Logger Variable
Navigate to the correct Device Type. eg. Point Grey Camera
Navigate to desired device eg. CAM-1BL-DM
Navigate to desired Variable eg. Max Counts
Assign the correct group name eg BELLA ECS CAMS
Add Logger variable
-------------------------------------------------------------------------------------------------------
Remote into computer name with the DSC Logger - (eg. BELLACAM6 for PW)
Click Stop on the open DSC Logger
Reopen the DSC Logger from the shortcut on the desktop. (The restart is required for the variable list to update).
Navigate to the configuration tab
Use the Wizard if required (it will make the setup simpler.)
Add the following fields
Name - Give the Alarm a name
Set the type of alarm - Hi, Lo (Higher or lower than..) [NOTE : You can set all 4 alarm conditions for 1 variable and the alarm would sound if any of them are met).
Level/Change - Limit at which it is triggered
Deadband/Time - Number of adjacent acquisitions that should meet the alarm criteria so that an alarm is raised.
Activate the Alarm
---ACKNOWLEDGING ALARMS--------------------------------------------------------------------------
To acknowledge an alarm, log onto the computer with the DSC Logger
Navigate to the Set Alarms Tab
On the bottom of the program tab, there would be a list of alarms
Right click & acknowledge all.
SAM's edits 12/8/20
Add variables to log via database editor: UI Ops>>Logger/Preset/Scans>>Add logger variable. Variable must have an alias before it can be added.
For HTW,
THIS PAGE IS OBSOLETE
Logger:
The logger is a LabVIEW based program that acquires data from different aspects of the BELLA project and saves in a common TDMS file.
The logger collects data from the following entities:
1. Johnson Controls Server (Environmental Data for the BELLA facility)
2. Shared Variable Engine for Thales Laser System
3. BELLA Control system for device data
1. Johnson Controls Server (JCS): The interface to the JCS is implemented using a client application developed in VB6 called the ‘BELLA JC Interface Server’ and a LabVIEW DLL that works as a translation layer between the VB6 Client and the BELLA logger.
The VB6 client makes WebService calls to the JCS to retrieve data. The LV DLL translated this data to be sent as an array of strings over datasocket to the logger that listens on the same port.
a. To begin logging from the JCS, launch the datasocket Server from Start Menu/All Programs/National Instruments/Datasocket/Datasocket Server
Figure 1: NI Datasocket Server
b. Launch the BELLA JCS Interface program using the shortcut on the desktop. The program is also located at "C:\Users\loasis\Documents\Johnson Controls Logger\BELLA JC Server Interface.exe". The following screen will pop open.
Figure 2: BELLA JC Server Interface
Hit the login button and click on “OK” to begin logging. The Site Director, User name and password information has been pre enetered and set as default as shown in Figure 3. BELLA JCS Server interface will query data values every 30 seconds.
Figure 3: BELLA JC Server Interface Login Screen
c. Sometimes the Server stops responding to logging queries from the BELLA JCS Server interface. In such an event an error messages shown in Figure 4 pops up. The resolution for this error is to close the application and relaunch it using steps a-c.
Figure 4: JC Server Interface Error
1-1 Adding new variables for logging
STEP 1: Editing the INI for BELLA JC Interface application.
a. To add new variables as channels to be logged, shout down the BELLA JCS Interface application. The datasocket server can be left running.
b. Open the MetasysSampleApp.ini file located at “C:\Users\loasis\Documents\Johnson Controls Logger” using Notepad. An example is shown in Figure 5.
Figure 5: Configuration file for JC Server Interface
c. In the Configuration sextion edit the maxrefs entry (2 in Figure 5) to match the number of channels/variables that have to be looged. For example, in figure 5, there are 6 channels being logged. The reference keys that map to the JC server are entered in the Input Reference section of the INI file. The maxrefs parameters is thus set to 6.
d. The reference key (1 in Figure 5) can be obtained using the JC web interface by navigating to the parameters being logged.
STEP 2. Editing the INI for Super logger
a. Open the sl-config.ini file located at “C:\Users\loasis\Documents\Johnson Controls Logger” using Notepad. An example is shown in Figure 6.
Figure 6: Configuration File for Super Plotter
Three sections as marked in the INI file have to be edited to start logging the new variables/References added in the BELLA JC Interface ini file (MetasysSampleApplication.ini).
sequentially add the variables to be logged. Any name may be used for the channels
Other detailed instructions for adding channels to the ini file can be found in the commented section of the INI file itself.
2. Shared Variable Engine for Thales Laser System
STEP 1. Edit the sl-config.ini file
The super logger is capable of logging the shared variables from the Thales Laser system also. The Thales shared variable logging system also uses the “sl-config.INI” file as shown in Figure 7
Figure 7: Thales Variables in Configuration file for Super Logger
The variables to be logged should be added using the same naming/entry convention as defined in the commented section of the INI file itself.
STEP 2. Launch the translation application for Thales SVE
Launch the translation application “Thales SVE Logger” using the shortcut on the desktop. The application is also located at "C:\Users\loasis\Documents\000 Labview Local\Developers Version\Interface\builds\Logger and Plotter\Thales SVE logger.exe". This layer/application will connect to the Thales SVE and transmit the data received over datasockets to the superlogger.
Note: The Thales SVE data will not get logged if the datasocket server is not running.
Figure 8: Thales SVE Interface
The application will display “Collecting data” if all connections are valid. A communication error is reported if network connections are dropped.
3. BELLA Control system for device data
Variables from the BELLA Control system devices can now be logged by the super logger.
Step1. Adding variables to be logged by the superlogger
a. Launch the database editor application on any control room computer or any computer on the BELLA network. Using the Menu, launch the Plot/Log-Logger-Add Logger Variable editor.
b. Select the Device type, Device and Variable to be logged and click on Add Logger Variable to enable logging for the particular variable using the superlogger. Repeat this for all the variables you need to configure for logging
c. Launch the MC and choose the datalogging experiment. Launch the control system devices to be monitored.
Page updated
Report abuse