................................................................................................................................... 16Definition of rules
................................................................................................................................... 22Configuration of Chatter Notification Engine
................................................................................................................................... 26Configuration of the Rules Engine
................................................................................................................................... 29Configuration of the SCADA plug-in
................................................................................................................................... 37Configuration of the STORMFLOW plug-in
Naming objects in a SCADA system
................................................................................................................................... 48Spredsheet for object names
................................................................................................................................... 52Import-file for object names
Creating Stormflow data
................................................................................................................................... 55Spreadsheet for stormflow data
................................................................................................................................... 56Import file for stormflow data
4
15
39
54
IGSS only information
................................................................................................................................... 59Creation of objects in IGSS 8
................................................................................................................................................................... 62String type objects
63
64
3
GB CHATTER NOTIFICATION CONFIGURATION 1303
Area
Phone
e-mail
Europe
+45 45 56 06 56
mjk@mjk.com
Denmark
+45 45 56 06 56
mjk@mjk.dk
Norway
+47 69 20 60 70
mjk@mjk.no
Sweden
+46 53 31 77 50
kontoret@mjk.se
Netherlands
+31 251 672171
mjknl@mjk.com
Ireland
+353 8795 35625
mke@mjk.com
USA
+1 847 482 8655
mjkusa@mjk.com
Australia
+61 3 9758 8533
ns@mjk.com
Item number
Description
840128-2008R2-001
2008 R2, release 001
Revision
Revisions
001
First release in this format
Introduction
system to meet your requirements.
To ensure the best result MJK recommends that the user reads this manual to become familiar with all features,
Configure the system as instructed by the manufacturer, MJK Automation ApS, to ensure reliable operation and
accurate measurements.
You can always get in touch with your supplier or with an MJK support hotline for advice and guidance:
MANUAL
Visit our website www.mjk.com to read more about MJK Automation ApS, our other products and the people behind.
system.
Ordering
Brief revision history
4
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
5
System overview
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
6
GB CHATTER NOTIFICATION CONFIGURATION 1303
Description
System. It treats the measurement or the alarm according to a set of rules. The rules tests the new measurement
or alarm, and decides - according to its origin - how to treat it.
A verbal description of a rule could be:
by the SCADA plug-in and the result forwarded to the SCADA-system.
Chatter Notification Engine - the component which receives the measurement or the alarm
Chater Rules Engine - the component which determines the further treatment of the measurement or alarm
SCADA plug-in - the component which treats data before forwarding them to the SCADA-system
STORMFLOW plug-in - the component which calculates numbers, durations and amount of spill during stormflows
based on a level measurement. The results is forwarded to a SCADA system.
MANUAL
16
7
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
System description
System. It treats the measurement or the alarm according to a set of rules. The rules tests the new measurement or
alarm, and decides - according to its origin - how to treat it.
A verbal description of a rule could be:
the SCADA plug-in and the result forwarded to the SCADA-system.
Chatter Notification Engine - the component which receives the measurement or the alarm
Chater Rules Engine - the component which determines the further treatment of the measurement or alarm
SCADA plug-in - the component which treats data before forwarding them to the SCADA-system
STORMFLOW plug-in - the component which calculates numbers, durations and amount of spill during stormflows
based on a level measurement. The results is forwarded to a SCADA system.
8
Stormflow processing overview
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
9
GB CHATTER NOTIFICATION CONFIGURATION 1303
Description
A stormflow starts when a water level has exceeded a preset maximum for a certain period of time.
A stormflow stops when the level has been below a preset level for a certain period of time.
MANUAL
10
Stormflow - Float switch
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
11
Stormflow - Pressure transmitter
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
12
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
13
GB CHATTER NOTIFICATION CONFIGURATION 1303
Not all available plug-in may be used in your installation
MANUAL
Functions overview
General
If new data is detected, they are treated by a Chater Rules Engine, which determines - according to a set of rules which plug-in will treat the data.
Plug-in's
received from Chater Rules Engine
SCADA plug-in
This plug.-in receives data from Chater Rules Engine and creates a file with comma-separated values from the data. This
file with comma-separated values contains measurement or alarm data which is delivered to various SCADA-systems.
The current version will supply data for:
7-Tedhnologies IGSS32 release 8 with DDHC Data FileDriver (Driver ID 66) installed.
7-Tedhnologies IGSS32 release 9 with DDHC Data FileDriver (Driver ID 66) installed.
System
BV Electronics System 2000
STORMFLOW plug-in
This plug-in receives data from Chater Rules Engine and creates a file with comma-separated values from the data. This
file with comma-separated values contains data on stormflows which is delivered to various SCADA-systems.
The current version will supply data for:
7-Tedhnologies IGSS32 release 8 with DDHC Data FileDriver (Driver ID 66) installed.
7-Tedhnologies IGSS32 release 9 with DDHC Data FileDriver (Driver ID 66) installed.
System
BV Electronics System 2000
14
Detailed configuration
Step
Desription
1
Configure the Chatter Notification Engine to use the correct database.
Information about setting up the engine are found in this chapter.
2
Define at least one rule in the configuration file cnsRulesEngineGlobalConfig.xml.
Information about how to set up rules are in this chapter.
Step
Desription
1
Create at least one rule in the range 0 - 1999 the configuration file
cnsSCADAplugInGlobalConfig.xml.
Information about how to set up rules are in this chapter.
2
Create a corresponding entry in the cnsSCADAobjects table in the database
Information about how to create and name objects in the database are in this chapter
3
Configure the SCADA plug-in to deliver its output data in a place to suit your needs
Information about how to configure this are in this chapter
Step
Desription
1
Create at the 2;M;1;0;M; rule in the configuration file
cnsRulesEngineGlobalConfig.xml.
Information about how to set up rules are in this chapter.
2
Create the necessary entries in the cnsSCADAobjects table in the database
Information about how to create and name objects in the database are in this chapter
3
Configure the STORMFLOW plug-in settings to suit your needs.
Information about how to configure this are in this chapter
General
SCADA plug-in
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
22
16
16
39
29
STORMFLOW plug-in
16
39
37
15
Definition of rules
#
Description
1;
The first element of the rule is 1, thus the data will be processed by the SCADA plug-in
M;
The second element of the rule is M, thus data must come from a Modbus input on any MJK
1;
The third element of the rule is 1, thus data must come from Modbus input number 1 on any
0;
The fourth element of the rule is 0, thus the SCADA plug-in will output the measured value
M;
The fifth element of the rule is M, thus data must come from a measurement.
#
Description
1;
The first element of the rule is 1, thus the data will be processed by the SCADA plug-in
M;
The second element of the rule is M, thus data must come from a Modbus input on any MJK
1;
The third element of the rule is 1, thus data must come from Modbus input number 1 on any
1024;
The fourth element of the rule is 1024, thus the SCADA plug-in will output the GSM signal
M;
The fifth element of the rule is M, thus data must come from a measurement.
C:\Program Files (X86)\MJK Automation\Chatter - Notification Service
cnsRulesEngineGlobalConfig.xml
#1
Description
1;
Data will be treated by the SCADA plug-in
Rules definition
A rule
measurements or alarms - are processed.
system.
they will be processed by the rule, if not, they will be ignored.
System operate.
Example number one
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
Example number two
Definition of rules
Rules are kept in this file:
First element - process where?
The first element is a digit designating which plug-in will process the data coming from this rule:
16
2;
Data will be treated by the STORMFLOW plug-in
Second element - input type
#2
Description
D;
Data must come from a digital input
A;
Data must come from a analog input
C;
Data must come from a counter on a digital input
M;
Data must come from a Modbus input
I;
Data must come from an internal measurement
#3
Description
1;
Data must come from X-input number 1
2;
Data must come from X-input number 2
3;
Data must come from X-input number 3
4;
Data must come from X-input number 4
measurement or alarm which is processed by this rule.
#4
From
Description
0;
comma-separated values.
1000;
Chatter
Output the battery voltage in mV from the internal battery in the current MJK
1001;
Chatter
Output the GSM signal strength as a value between 1 and 31 as recorded for
Value
Description
1 - 14
The signal strength is marginal
15 - 19
The signal strength is is acceptable
20 - 24
The signal strength is is good
25 - 31
The signal strength is is excellent
1002;
Chatter
reset to the file with comma-separated values.
for this rule:
Third element - input number
data for this rule:
GB CHATTER NOTIFICATION CONFIGURATION 1303
MANUAL
Fourth element - data output
The fourth element is a number designating which data, this rule will output to a recipient, typically a SCADA-system.
Data output is divided into three different groups;
marked with a Chatter in the table below.
Database in the table below.
Output of data from the STORMFLOW plug-in, marked with an Stormflow in the table below.
17
GB CHATTER NOTIFICATION CONFIGURATION 1303
1003;
Chatter
measurement or alarm to the file with comma-separated values.
1004;
Database
the file with comma-separated values.
1005;
Database
Logger to the file with comma-separated values.
1006;
Database
Logger is located to the file with comma-separated values. Used mostly at
waterworks.
1007;
Database
Data Logger to the file with comma-separated values.
1008;
Database
Output the name from the middle level in the location for the current MJK
1009:
Database
Output the name from the lowest level in the location for the current MJK
1010;
Database
with comma-separated values.
1011;
Database
Output the signal type which is the origin of the data to the file with commaseparated values.
1012;
Database
Output the signal number which is the origin of the data to the file with commaseparated values.
1013;
Database
with comma-separated values.
1014;
Database
file with comma-separated values.
1015;
Database
Logger to the file with comma-separated values.
1016;
Database
file with comma-separated values.
1017;
Database
the file with comma-separated values.
1018;
Database
the file with comma-separated values.
1019;
Database
Output the flag telling if Minimum Threshold is enabled in the current MJK
1020;
Database
Output the flag telling if Maximum Threshold is enabled in the current MJK
1021;
Database
with comma-separated values.
1022;
Database
comma-separated values.
1023:
Database
server to the file with comma-separated values.
1024;
Chatter
Data Logger converted from mV to V to the file with comma-separated values.
1025;
Chatter
Output the GSM signal strength converted to dBm as recorded for the current
MANUAL
18
GB CHATTER NOTIFICATION CONFIGURATION 1303
Value
Converted to dBm
0
-113 dBm
1
-111 dBm
2 - 30
-109 dBm til -53dBm in steps of -2 dBm
31
-51 dBm
1026;
Database
measurement or alarm, converted to seconds since midnight, January 1st, 1970
using the local time zone, to the file with comma-separated values
1027;
Database
measurement or alarm, converted to seconds since midnight, January 1st, 1970
using UTC, to the file with comma-separated values
1028;
Database
server, converted to seconds since midnight, January 1st, 1970 using the local
time zone, to the file with comma-separated values.
1029;
Database
server, converted to seconds since midnight, January 1st, 1970 using UTC, to the
file with comma-separated values.
Numbers above 2000 are usable only if the installation contains the
STORMFLOW plug-in
2000;
Stormflow
Output the start time for the first stormflow within the last 24 hours to the file with
comma-separated values.
2000 must always be in the cnsSCADAobjects table whether it is
used or not!
2001;
Stormflow
Output the end time for the last stormflow within the last 24 hours to the file with
comma-separated values.
2002;
Stormflow
Output the duration of all stormflows within the last 24 hours to the file with
comma-separated values.
2003;
Stormflow
Output the number of sub-stormflows within the last 24 hours to the file with
comma-separated values.
2004;
Stormflow
Outputs the number of stormflows within the last 24 hours to the file with commaseparated values.
2005;
Stormflow
Outputs the total number of stormflows since system start to the file with commaseparated values.
2006;
Stormflow
Outputs the total duration of stormflows since system start to the file with
comma-separated values.
2007;
Stormflow
Outputs the amount of spill in litres within the last 24 hours to the file with
comma-separated values.
2008;
Stormflow
Outputs the amount of spill in m3 within the last 24 hours to the file with commaseparated values.
2009;
Stormflow
Outputs the total amount of spill in litres since system start to the file with
comma-separated values.
2010;
Stormflow
Outputs the total amount of spill in m3 since system start to the file with commaseparated values.
2011;
Stormflow
Outputs the momentary flow at log-time in litres pr. second to the file with
comma-separated values.
2012;
Stormflow
Outputs the momentary flow at log-time in m3 pr. second to the file with commaseparated values.
MANUAL
19
GB CHATTER NOTIFICATION CONFIGURATION 1303
2013;
Stormflow
Outputs the momentary flow at log-time in m3 pr. minute to the file with commaseparated values.
2014;
Stormflow
Outputs the momentary flow at log-time in m3 pr. hour to the file with commaseparated values.
2015;
Stormflow
Output the start time for the latest, completed stormflow to the file with commaseparated values.
2016;
Stormflow
Output the end time for the latest, completed stormflow to the file with commaseparated values.
2017;
Stormflow
Output the duration for the latest, completed stormflow to the file with commaseparated values.
2018;
Stormflow
Output the number of sub-stormflows for the latest, completed stormflow to the
file with comma-separated values.
2019;
Stormflow
Outputs the amount of spill in litres for the latest, completed stormflow to the file
with comma-separated values.
2020;
Stormflow
Outputs the amount of spill in m3 for the latest, completed stormflow to the file
with comma-separated values.
2021;
Stormflow
Output the start time for the first stormflow within the last 24 hours, converted to
seconds since midnight, January 1st, 1970 using UTC, to the file with comma-
separated values.
2022;
Stormflow
Output the start time for the first stormflow within the last 24 hours, converted to
seconds since midnight, January 1st, 1970 using the local time zone, to the file
with comma-separated values.
2023;
Stormflow
Output the end time for the last stormflow within the last 24 hours, converted to
seconds since midnight, January 1st, 1970 using UTC, to the file with comma-
separated values.
2024;
Stormflow
Output the end time for the last stormflow within the last 24 hours, converted to
seconds since midnight, January 1st, 1970 using the local time zone, to the file
with comma-separated values.
2025;
Stormflow
Output the start time for the latest, completed stormflow , converted to seconds
since midnight, January 1st, 1970 using UTC, to the file with comma-separated
values.
2026;
Stormflow
Output the start time for the latest, completed stormflow, converted to seconds
since midnight, January 1st, 1970 using the local time zone, to the file with
comma-separated values.
2027;
Stormflow
Output the end time for the latest, completed stormflow , converted to seconds
since midnight, January 1st, 1970 using UTC, to the file with comma-separated
values.
2028;
Stormflow
Output the end time for the latest, completed stormflow , converted to seconds
since midnight, January 1st, 1970 using the local time zone, to the file with
comma-separated values.
Numbers 2029 to 2032 requires the Alarm interval in the MJK
2029;
Stormflow
Outputs the momentary flow at log-time in litres pr. second for the for the
current, ongoing stormflow to the file with comma-separated values.
2030;
Stormflow
Outputs the momentary flow at log-time in m3 for the for the current, ongoing
stormflow to the file with comma-separated values.
2031;
Stormflow
Outputs the summed amount of spill in litres for the for the current, ongoing
stormflow to the file with comma-separated values.
2032;
Stormflow
Outputs the summed amount of spill in m3 for the for the current, ongoing
stormflow to the file with comma-separated values.
MANUAL
20
Loading...
+ 45 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.