Home     Rugid Hardware     Applications     Company     Pricing     Download  

 

                                              

Events Specification                                         2 of 3   

Download Events specification.

 

  Windows interface:  Events can be installed on Windows 95, 98, ME, NT4, 2000 or XP operating systems.  

  Unlimited tags:  Events will allow you to make as many inputs and outputs as necessary in the full version.  Tags are assigned modbus inputs.  The 64/64 version allows 64 inputs and 64 outputs.

  Form editor:  Events has three sets of component toolbars for making custom form displays.  The toolbars include  display components, background components and control components.  The form editor allows the user to modify existing displays by adding new components or deleting components.  You can make as many displays as needed for your system.

  Communications:  Events serial communications includes the Modbus binary protocol and the ALERT protocol.  Modbus is used with Modbus RTUs or PLCs that can be configured as a Modbus Slave.  The ALERT protocol is used with a receiver decoder that outputs data in an ALERT format.

  Defined sensors:  New sensors can be defined from existing sensors.  Defined sensors can use an if-then-else equation, a lookup table (level vs flow), a complex numerical equation, a capture statement (capture the time of the last transmission), or just be used to change the sensor name or add a local set point.  Defined sensors can be used in  alarm setup and can be logged in the database.
  Alarm processing:  Each sensor can be assigned multiple alarm set points with alarm actions for each event.  Actions include logging the alarm, speaker sounds, blinking the application, showing the alarm form, and messages.  A message can play any number of wave files for voice alarm messages.  Current and historical alarms can be shown or printed at any time.   Statistics:  Events provides a statistical table for daily maximums, minimums, and averages for any sensor in the system.  Events stores 7 days of statistical information and then overwrites the older statistical files.  Statistical data can also be logged the the database.
  Security: Events has a log on and off password security for five main program areas.  The user must be logged on and have permission to change communications, modbus setup, files & alarms, forms and passwords.  Events automatically logs off after one hour of no use.   Change log:  Events keeps a change log to monitor changes made to forms, set points and other modifications to your program.  The log can be viewed and printed at any time.
  Importing modbus:  Events uses a spreadsheet table for specifying your modbus inputs and outputs.  You can use the import menu item if you are using a RUG9 master RTU.  By importing the modbus array, you eliminate input errors between your master RTU and Events.   Database:  Events allows each sensor or device to be stored in multiple databases.  You can setup on-change databases as well as on-time databases.  On-time databases are good for reports and historical trends.  On-change databases store each sensor as it changes.
  Networking:  Networking is included in the full version of Events.  Events can be networked on a local area network.  Network commands are sent once from the client to the server and then the server updates the client with the data requested on a timed basis (i.e. every 15 seconds).  One client can receive updates from multiple Events servers for updating several processes on one machine.  Each full version of Events can be either a network server or client or both.  The networking will work on any Microsoft networks and should be tried on other network configurations.   Reports:  Events provides a report editor that can pull data from real time sources or can pull historical data from your databases.  The report editor also can accept graphic images (form snapshots or trends).  Users can make a reports by changing font color, font sizes, adding images, inserting titles, subtitles, dates, times, and data placeholders.  Data placeholders ( =[1] ) are assigned sensor names, SQL statements or local tags such as datetime.  Users can run the report, preview it, print it, save it, and set the scheduler to print the report when needed.
  Scheduler:  Events provides a powerful scheduler that triggers tasks on time or on an event.  The scheduler is used to output HTML files and text files of your data as needed.  Triggers include three types of timers, click events on your forms, alarm events, receive status changes, transmit sensor changes, or defined sensor events.   HTML output:  Events can build HTML web pages of your forms, historical data, historical trends, alarms, statistics and reports.  You set your scheduler to output your forms every 15 minutes, while alarms and reports are triggered on change.  Events will update your users on your network without additional networking costs. 
  CSV output:  The scheduler can also output comma delimited data and tab delimited data for other programs.  These files can be appended to or overwritten as required.   eMail option:  Events can email message with file attachments.  The scheduler triggers email message to a group of users as assigned.  EMail is an optional item and can only be added to the full version of Events.

2 of 3