Home : Products : Hach WIMS : Interfaces : Hach WIMS Indirect Server-Side Interface to Wonderware InTouch HMI : Documentation : Topics specific to the operation of this interface : Supported variable configurations for interface Q12706
Q12802 - HOWTO: Supported variable configurations for interface Q12706
Supported variable configurations for the Hach WIMS Indirect Server-Side Interface to Citect SCADA Reports.

To configure a variable to hold values from Citect SCADA Reports, select Edit/View Variables in the Hach WIMS client and select the Interface tab.

Then click Interface To radio button. The drop down box next to the option is now enabled, click the drop down arrow and choose the Cimplicity SQL interface name (name given when configuring the interface).

Now you are ready to configure a signal tag to the Citect SCADA Reports Historian. The Tag name and a Statistic are all that are mandatory.

  • This is the history table followed by the tag found in your WonderWare Historian. The table name is needed because it is possible to have the same tag name in multiple tables.

  •  This is a listing of all the statistics supported by this interface. This includes the following statistics for a specified time period.

    AVERAGE

    Take the average of the data points


    TOTAL

    Take the sum total of all values

    MINIMUM

    Get the minimum value


     

    MAXIMUM

    Get the maximum value


    FIRST

    Get the first value


    LAST

    Get the last value


    DIFF

    Calculate the difference between the first and last values. If the first value is larger than the second then it will perform the following calculation: (10 ^ (Ceil(LOG(first_value) / LOG(10)))) - first_value + last_value

    Ceil will cause the value to round up

     

    RANGE

    Calculate the absolute value of the difference between the minimum and maximum values

     

    COUNT

    Counts the number of data points.


    MINTIME

    The date and time when the minimum value occurred.

    MAXTME

    The date and time when the maximum value occurred.

    TIMEGT(x)

    Counts the number of data points greater then 'x'.


    TIMELT(x)

    Counts the number of data points less than 'x'.


    TIMEEQ(x)

    Counts the number of data points equal to 'x'.


    INVENTORY

    Running total of used volume. Only decreases in value are counted. Use the DEADBAND option in Hach WIMS variable setup to eliminate erroneous readings due to noise or vibrations.


     


  •  

    • This is the value to multiply the result by when using parameter variable types. Commonly used to convert from one unit base to another. For example to convert gallons per minute (GPM) to gallons per day (GPD), set the scale factor to 1440 (1440 minutes per day).

    • All three fields must have numeric values or the word None (as shown). The Low Range and High Range will crop data from the source. For example to eliminate negative numbers from a particular tag, set the Low Range to 0 (zero) - this will get any values equal to or greater than 0 (zero). The Deadband is used for the statistic Inventory and will elliminate noise levels up to the value specified. For example, if you enter .5 next to Deadband, any value change of .5 or less, will be ignored.



      • Start Time will set the beginning of the time slot for this variable.
      • Stop Time will set the ending time for the time slot.
      • Same Day as Start is only used by daily variables and it means the stop time is on the same day as the start time.
      • Day After Start is also only used by daily variables and it means the stop time is a day after the start time.

    •  Allows you to filter data based on another tag. For example, flow rate while not in backwash, but during backwash we don't want flow rates uploaded to Hach WIMS.
      • Node:Tag.Field is the Cimplicity SQL Tag you want to filter by, in our example it would be the backwash state.
      • Middle field is the filter operator. This can be <, >, =, <=, >=, <>, or CYCLESTO.
      • Last field is the filter value. So when the 'backwash state' is greater than 0 (not backwashing) then our system will get values. When the value drops to zero or negative, do not get values.

Related Articles
No Related Articles Available.

Article Attachments
No Attachments Available.

Related External Links
No Related Links Available.
Help us improve this article...
What did you think of this article?

poor 
1
2
3
4
5
6
7
8
9
10

 excellent
Tell us why you rated the content this way. (optional)
 
Approved Comments...
No user comments available for this article.
Created on 1/11/2010 1:57 PM.
Last Modified on 1/12/2010 1:21 PM.
Last Modified by No Author Name Available!.
Article has been viewed 4380 times.
Rated 0 out of 10 based on 0 votes.
Print Article
Email Article