EVENTS SCADA Software

1
EVENTS SCADA Software

• Graphical Software
• for
• Radio Telemetry
• Data Acquisition Systems

2
Events Overview

• Provides data security.
• Displays real time data.
• Shows current alarms.
• View historical data.
• Build reports
• Using the task scheduler.

3
Security

• Provides password protection for
• Changing forms.
• Changing files alarms.
• Changing communications.
• Changing passwords.
• Changing Modbus setup.
• You can log on and off of EVENTS.
• You can stop EVENTS from being closed.
• Events logs off after 1 hour of no use.
• View the current user on the bottom status bar.

4
Viewing Displays

• Screens (forms) show real time data when
  received.
• Build as many screens as needed.
• View screens by Navigating
• Select bottom tabs.
• Select menu items.
• Click form buttons.

5
Display Maintenance

• Maintenance data shows
• Low battery annunciators and battery trends.
• Communications fails.
• Pressure transducer failures.
• Poll remote sites from the maintenance screen.

6
Display Lift Station

• Lift station screen shows
• Pump start and stop set points.
• LED Alarms.
• Pump runtime Totals.
• Bar charts showing levels.
• Buttons for viewing other screens.

7
Display Water Distribution

• Well 4 screen shows
• Pump start and stop set points.
• HOA (hand, off, auto) controls.
• Pumps running or failed.
• Well measurements.
• Site Alarms.
• Buttons for viewing other screens.

8
Display Weather Data

• Weather screen shows
• Temperature humidity.
• Wind speed direction at 3 different sites.
• Reservoir level button trend chart.
• Buttons for viewing other screens.

9
Showing Alarms

• The alarm display shows current historical
  alarms.
• Acknowledge button.
• Acknowledge before clearing.
• Printing daily alarms.
• Scheduling.

10
View Historical Data

• The SQL editor is used to view stored historical
  data.
• Use the wizard button to build your first SQL
  commands.
• The Steps are
• Build an SQL command.
• Run the SQL command.
• Check the results.
• Trend the results.
• Store the SQL command if you want to use it again.

11
Reports

• The report editor is used to build data reports
  for printing and display. You can
• Print current data.
• Print historical data.
• Print display screens.
• There are 2 report modes
• Editing (building a report).
• Running a report.

12
Scheduler

• Output HTML files to a shared network folder.
  HTML reports can include
• Daily alarm reports.
• All your screen displays.
• Historical data.
• Trends.
• Statistics.
• Print alarm reports.
• Print reports on a daily or weekly basis.
• Print form displays.
• Backup your project on a regular basis.

13
Configuring a System

• Build receive and transmit arrays.
• Import RUG9 master arrays.
• Define new sensors.
• Configure sensor databases.
• Configure sensor alarms.
• Build display screens (forms).
• Build SQL statements for historical data.
• Make reports for real time historical data.
• Set scheduler for daily tasks.

14
Background Tasks

• Communications
• Receive Arrays
• Transmit Arrays
• Defined Sensors
• Files (Database)
• Statistics
• Alarms
• Rate Alarms
• Scheduling

15
System Data Flow

• Master RTU receives data from remotes by radio
• EVENTS polls data from Master RTU every second
• Data is placed in Modbus receive grid
• Receive grid updates
• Defined sensors
• Alarm grid
• Database
• Statistics
• Displays

16
Alarm Setup

• Events alarms are setup in Files Alarm grid.
• Each alarm is assigned an action(s)
• Actions include
• Log log alarms (always include log).
• Show current alarms.
• Sound speaker alarms.
• Blink application.
• Message show message.

17
Local Area Networking

• The full version includes networking.
• Users need a licensed copy of Events on each
  networked machine.
• The network uses secure data messaging.
• An Events client sends an update command to the
  master and the time interval (seconds) to be
  updated.
• The master updates the clients receive arrays on
  the defined update interval.
• Client set point changes update the master on
  change.

18
Trouble Shooting

• Access errors after system crash.
• 1. Close Events.
• 2. Open Explorer.
• 3. Find your Events project folder.
• 4. Find data folder in project folder.
• 5. Rename data folder (dataold).
• 6. Restart Events.
• Modbus errors.
• Form errors.