Harvest Config Help
Menu
Alarms
Base Profile
Basic Information
Copy Settings
Custom Converters
Graphs and Traces
Hardware
HSN and Menu Names
Log Operations
Quick View
Base Profile
Profiles
Extreme care should be taken when using profiles, and it should be noted that when you "Change Profile" for a unit it will change not just the config, but the SPE settings and Maptable as well.
NB. Profiles will NOT overwrite/copy any of the HSN and Menu Names or Data Export Clients details.
Customer: Basic list of customers, profiles are sorted by customer first, then by the type of hardware.
HardwareType: Hardware type, it is important to get this right as various SPE settings as well as the Maptable are hardware specific.
Profile: This is the name of the actual profile, created when you "Save As New Profile".
Change Profile: After selecting a customer, hardware type, and profile to load, pressing this button will initiate the change. (Only available on the config page.)
Save As New Profile: Use this to save the current page to a profile. You must select the "Customer" and "HardwareType" enter the name of the profile into the box.
You cannot save to an existing profile using the drop down box, rather you must enter the name of the existing profile into the text box.
Example of setting up a profile and using it on another unit
First you need to set up a unit with the desired SPE settings, Config settings, and Maptable settings. Once happy with this you need to save each section to the desired profile.
-Navigate to the SPE page, select the Customer->HardwareType and then type the desired name into the text box and click "Save As New Profile".
-Repeat this step for the Config tab and the Maptable (remember to type the same name into the box, rather than try to select it in the "Profile" drop down list).
We now have a profile set up that can be loaded onto either current units, or used as the start point for a new system.
To load this onto a current system follow these steps:
-Open up the Config page of the unit you wish to load the profile onto.
-Select the appropriate profile Customer->HardwareType->Profile.
-Click "Change Profile". This will give you a warning prompt, cautioning you as to what the procedure will do.
-Click "Ok" if you are sure and the system will modify the unit.
To create a new unit with a profile follow these steps:
-Navigate to the database, either by clicking the DB tab, or by going to db.harvest.com.
-Select "HSNs" and then "New HSN"
-Select the Country, and Region BEFORE you do anything to the profile drop down boxes (otherwise they will just get reset).
-Make any other changes that are necessary (Unit Type: is now redundant with profiles).
-Select the profile needed, Customer->HardwareType->Profile, and click "Add HSN"
Top of page
HSN and Menu Names
HSN and Menu Names
HSN: This is the Harvest Serial Number of the unit.
Group: This is the group the unit belongs to, the following is a list of the groups:
Italics denotes hidden group
-Main: Frost/weather system that is viewable on the normal Harvest website.
-Police: Hidden group for Police or Alarm related units.
-New Installations: Hidden group for units that are finished and ready to be shipped to the customer.
-Testing: Hidden group for units that are currently being tested.
-Tested: Hidden group for the units that have been tested.
-Proxy: Proxy units that are viewable to customers.
-AWT: Group for units belonging to AWT, accessible via awt.harvest.com.
-Disconnected: Hidden group for units that have been disconnected, usually due to unpaid invoices or no longer requiring the service.
-Old: Hidden group for old units.
-NZ Fire Service: Group for units belonging to the NZ Fire Service, accessible via nzfire.harvest.com.
-ADS: Group for units belonging to ADS, accessible via ads.harvest.com.
-Kiwirail: Group for Kiwirail's crossing monitors (not track temperature, DED, or weather stations), accessible via kiwirail.harvest.com.
-Downer EDI: Group for Downer EDI units, accessible via downeredi.harvest.com.
-Trustpower: Group for units belonging to Trustpower, accessible via trustpower.harvest.com.
-Ontrack: Group for Kiwirail's weather units (track temperature, DED and weather stations), accessible via ontrack.harvest.com.
-Offline: Group for units that are Offline, these are usually set-up to be just loggers and will not be calling in to Harvest servers.
-FMR: Group for FMR units, these are available on both the Main site and FMR site, accessible via fmr.harvest.com.
Country: This cannot be changed within the config, instead you must go to the database to modify it.
Region: The region the unit is in, usually this is broken down by a countries regions, but can be thought of as simply a 3 tier sorting system with this being the top most.
Owner / Subregion: This is the 2nd tier, usually this is the company or individual that owns the station, but for special customers (ones with a separate website) can be used as a sub category
Location Name: The actual name of the unit/site
SiteName Alias: Used in conjunction with the Data Export and Data Export Clients check boxes.
Sort Hint: The Sort Hint is a way of ordering units within their subregion. The units will be ordered by number i.e. to get a unit at the top set it to 1. The default is 500,
which results in units being ordered alphabetically.
Top of page
Hardware
Hardware Type
Use this drop down box to record the hardware type of the unit. This controls the map table entries available (especially important for Flowshark), and various options specific to different units (for example
the satellite option gives the entry boxes needed for the satellite serial number, mapping and rounding).
Top of page
Basic Information
Protection
Three levels of data protection can be assigned to a unit.
With all levels of protection, the full password is needed to change details (such as alarms and growing season), and a minimum of the read-only password is needed to download the data
No Protection: All data is visible.
Frost Protection: Password required to view data during frost event.
Full Protection: A password is required to view ANY data.
Top of page
Password
This password is the main access password used by the customer. This gives them access to the options page where they are able to change this password, the read only password,
adjust alarm levels and modify alarm rosters, as well as change the seasons for their alarms and growing period.
Top of page
ReadOnlyPassword
The ReadOnlyPassword is available for customers to give to various individuals that need to see the data but they don't want having access to the options page. These may be frost fighters, consultants, or temporary managers.
This password gives them access to the data (if under frost/full protection) and the ability to download the data.
Top of page
Time Zone
Time Zone affects the display of the data and corresponding downloaded data. Ensure you have the right setting for the region, including whether the data will be adjusted for daylight savings or not.
Top of page
Access Report
This report outputs who has access to the current unit. The two drop down boxes allow you to define at which scope you running the report.
GROUP
COUNTRY
REGION
OWNER
UNIT
Map User
Readonly
Admin User
Power User
Top of page
Telemetry Type
Check boxes refer to the type of telemetry the unit is running.
FROST/WEATHER: Normal setting for frost/weather stations
ADS: Setting used for ADS units
ADS_RAIN: Setting used for ADS units that are monitoring rain
AWT_ACCQMIN: Setting used for AWT ACCQMIN units
AWT_RAIN: Setting used for AWT Rain units
MACE: Setting used for a unit with a MACE attached, if the unit is set up with a proxy (HSN +30000) then this will cause the wbackend to redirect to the MACE backend.
If the unit has the ASE set in the SPE settings to 8 then it will call into the MACE backend.
AWT_LEVEL: Setting used for AWT sites with depth sensors (Waterpilot/PMC)
AWT_PRN:
FLOWSHARK: Setting used for a unit with a Flowshark attached, if the unit is set up with a proxy (HSN +30000) then this will cause the wbackend to redirect to the Flowshark backend.
If the unit has the ASE set in the SPE settings to 8 then it will call into the Flowshark backend.
Top of page
ADS Serial No
This is only used when the unit has a Flowshark attached, this is the Flowshark serial number.
Top of page
Data Export Clients
This list contains the current clients that have data sent to them via FTP, the data we send is selected by the Data Export check box for each trace. Checking any of these boxes will cause
the backend to forward the selected data to the appropriate destinations each time the unit finishes a call.
Top of page
TSR Type
When setting up a TSR this must be selected for the type of aircraft it is being used in.
Top of page
Growing Season
The growing season is the time period in which the system will calculate GDD, and inversely RCU. This should be defined by the customer (they are also able to modify this in the Options tab).
Top of page
Humidity Source
This needs to be set to the temperature input that the humidity sensor is present on, in most cases this will be Temp1 (if unsure check with installer/customer).
Top of page
Dewpoint Source
Similar to the Humidity Source, this needs to be set to the temperature sensor that has the humidity sensor present. You may set this to another temperature sensor (thus using temperature from one site,
and humidity from another) but this won't give true readings, and is not recommended.
Top of page
Initial Collection Age
This defines the number of days back we will try to collect data from a newly attached serial device. Default is 1 so when a MACE or FLOWSHARK is attached for the first time to a unit, it will only attempt to
retrieve data from the last 24hours.
If the device has been logging for a period of time it is advised to set this back to the start of the logging period. If the device is attached and the unit calls before this
has been set to a number of days appropriate for pulling in the required data you must RENAME any raw log files in the SPE directory so as to set the unit into a state of thinking its the first time a device
has been attached.
Top of page
Customer Setup Remote Call
Default: Unchecked
Setting this will allow the customer to set the modem to stay on for 30minutes in their Options tab.
Top of page
Customer Access Graph Config
Default: Unchecked
Setting this will give the customer access to the graphing part of the config in their Options tab.
Top of page
Customer Change LID And Region Names
Default: Unchecked
Setting this will allow the customer to change the naming of the unit. They will be able to alter the region, owner and unit name.
Top of page
Customer Change Google Maps
Default: Unchecked
Setting this will allow the customer to modify their system placement on the Google Maps interface.
Top of page
Customer Leave Temporary Settings
Customer Leave Temporary Settings
Top of page
Hang Up After Call
Default: Checked
Setting this will cause the backed to issue the "hang-up" command to the unit.
If this is unchecked the unit will keep the cell phone powered on. This is useful for sites where we are
calling in with very short intervals over long periods e.g. Calling every minute constantly. This allows us to save cost on data charges.
Top of page
Don't Hang Up In Temp Report Zone
Default: Checked
Setting this means the backend will not send the "hang-up" command to the unit if it is in a temperature report zone. This means that during a frost, or heat alarm instance, we will not hang-up the phone.
Top of page
Count On Report
Default: Unchecked
Setting this means the unit will be counted as a "live" unit. This affects whether the system alarms for low percentage of units calling. This should not be set until the unit has been sent out and installed.
It should also be turned off when a unit is received back that is not to be returned.
Top of page
Show On Google Maps
Default: Unchecked
Setting this means the unit will be shown on the Google Maps interface.
Top of page
ITU Style Logs
Default: Checked
Redundant check box used on historical units to convert logs into ITU-Styled logs
Top of page
Ask For Logs
Default: Checked
Setting this means the backend will ask for logs when the unit next calls in. Turning this off is useful when dealing with units that will be sending through a lot of logs the next call and you don't want to wait
for the unit to send all its logs through.
Top of page
Ask For Logs On Scheduled Call Time
Default: Checked
Setting this means the backend will ask for logs when the reason for calling is SCT. To have this functionality, HWHY must be set in the AFS in the units SPE settings. Useful for preserving battery on non-solar
units if you wish to have it call once a day just to ensure it is still "alive".
Top of page
Get All Next Call
Default: Unchecked
Setting this means the backend will ask for ALL the logs on the unit the next time it calls.
Top of page
Proxy Unit
Default: Unchecked
Setting this will label the unit as a Proxy Unit. For now this removes the "last called" tag that appears above the tag, as this would usually result in an erroneous reading of "last called 18 months ago".
Top of page
Blurb
This section allows you to write a blurb to be appended above the graph on the main page. It handles HTML so is useful for providing links to customer pages, or recording information that may be appropriate for
the specific unit such as offsets, or consent details.
Top of page
Graphs and Traces
Setting up a units Graph Page
Typically you will start with a set of graphs through a pre-defined profile.
Ensure that you have your Maptable setup with the required inputs (in the case of the ITU-2 it must also have been uploaded to the unit).
Example Trace Setup for a Temperature Sensor
First we need to create a new "Graph", this is done by pressing insert on the Graph line below where you want the graph to appear.
Now we have a new "Graph", we want to add the temperature trace to it. This is done by pressing add trace on our new graph line. This will show a default trace which can be
edited to show any available data. Before editing the trace finish with the graph by giving it a name (this will be displayed on the left hand side of the graph next to the y-scale), and set the
height (for our temperature graph we will set it to Average).
To set up a trace (as noted previously) you must have the maptable set up correctly and in the case of ITU-2's it must also be uploaded to the ITU (otherwise you will not see the correct options
in the input drop down box).
Trace is where you put the name of the trace, this will appear on the right hand side of the graph, next to the various values you select (
Min, Max, Avg etc) in the colour set for the trace. In the case of a temperature we will call it
"Temp 1" but usually the customer will have a custom name for it that will refer to the block or area the sensor is in.
The converter defines what we do with the data and the units we present it in. In the case of a temperature we will use Temp_C, this will display the temperature in °C.
Input is a reference to the map table for the unit, this is where we will retrieve the RAW data and convert it using the converter that we just selected. In our case we will use Temp1.
If the customer wishes to see this trace on their "Quick View" page then you will need to check QV Show as well as setting up a quickview Group Name further down in the config.
For this example we will leave SiteName Alias, Trace Alias and Source HSN blank.
Clip lo and Clip hi will be left blank for this as well. Temperature's are usually Drawn as line's, you will find that the Temp_C you selected
has already set some of the default settings for temperature traces. Set the "In" to the desired colour for the trace (you will usually want each trace on a graph to use a different colour for ease of viewing).
The rest of the settings should have been automatically set by the converter, and should be the following:
Display - Number
Min - Checked
Avg - Checked
Max - Checked
Last - Checked
Total - Unchecked
GDD - Checked
RCU - Checked
Int - Unchecked
No AutoScale - Unchecked
Data Export - Unchecked
Decimal Places - 1
Now we have a completed temperature graph, ensure that all the information settings are correct and click "Save Config". If there is data coming into the unit on the Temp 1 input you should see a trace displaying this.
Top of page
Default Graph Range
The default graph range refers to the initial time scale that is used when looking at a units graph.
This can be set to either:
Hour
3 Hour
Day
Week
Month
Typically the Day view will be the most used, and is the usual default value.
Top of page
Height
This drop down box contains the available heights for graphs. Depending on the traces you are graphing you will need to change this to get a nice layout.
Dwarf: Very small graph, useful for plotting one or two traces that will not change very much, such as the system battery for a unit with no solar panel.
Short: Similar to the dwarf it is appropriate for traces that will not be varying very much.
Average: The default graph size. This is perfect for displaying a few of most traces. Can handle two temperature sensors with GDD and RCU set.
Tall/Huge/SuperHuge/ChunkyHuge: These are all larger variations of the graph. SuperHuge is the tallest, and can handle a maximum of 5 temperature sensors if you are
showing GDD and RCU.
Time Axis: This graph is removes the x and y axis lines, and sets it to the right size for the time to be shown on the x-axis. The name should be set to "Time" as well.
Gap: This graph removes the x and y axis lines and sets the size to a small gap. This should be used in between each graph unless you already have a time graph, or in between wind direction and speed.
The name should be set to "Gap" as well
ArrowGap: Similar to the gap but includes the arrows for navigating the time scale forward/back.
Rain: This graph is useful for graphing rain on, though it can be graphed on any sized graph fine.
Wind Dir: Wind Direction should be graphed on this (unless the customer wants to graph the actual ° of wind), set the display to Wind Dir and it will display in NSEW bearing.
Digital: Any data that is a digital on/off format should be graphed using this style of graph. It provides a nice compact graph that allows you to see the state of the input over the time period.
Each trace you add to this will make the graph one line bigger so many traces can be on the one graph. Ensure the display is set to digital, and the states are named appropriately.
Top of page
Hide
Default: Unchecked
Checking this box will hide the graph from anyone viewing the page that is not a PowerUser, it will also set the x and y axis colour to blue to allow for differentiation between hidden/normal graphs.
Top of page
History
Default: Unchecked
Checking this box will mean the graph (and associated traces) will be displayed in the "History" tab of the unit. Make note you must add the gap/time graphs to the history otherwise the layout will be
compressed.
Top of page
Delete
This button deletes the graph as well as any traces associated with it.
Top of page
Insert
This button inserts a graph (with no traces) above the current graph.
Top of page
Add Trace
This button adds a trace to the current graph. It adds it to the bottom of the traces on the graph, but once added you may move the traces around within
the graph. Currently you cannot move a trace to another graph.
Top of page
Input
A selection box for the input (from the maptable) that you will be using. In some cases the converter may require more than one input, for example in the case of dewpoint you will be asked for humidity and two
temperature sensors, in this case you only use the first temperature sensor, but it gives you the choice for a second "backup" sensor.
Top of page
SiteName Alias
Certain customers may require data to be exported to either themselves or a external ftp server. In some cases they will require the trace to be named with a special alias (e.g. in the case of consents where
you need to set the SiteName Alias as the consent number for the particular bore).
Top of page
Trace Alias
Similar to SiteName Alias if a customer requires data to be exported there may be a specification that the data have a particular name for the software at the receiving server.
This tag is for the naming of the particular trace on a graph (e.g. Consents for water bores, the total take should be aliased as "Abstraction Volume", and rate as "Abstraction Rate").
Top of page
Source HSN
This text box is for putting in the serial number of another unit that you wish to retrieve data from. This is useful for setting up "Proxy" units (units where the customer may want to show only a few sensors to the
public and keep the rest private on the actual unit page) or showing information from multiple units on one graph.
NB. if you do set up a site as a proxy unit make sure that the Proxy box is checked, otherwise you will show erroneous "last called" information.
Top of page
Clip Lo/Hi
Clip Lo/Hi are for setting constraints on the graph so that data is clipped. Examples of this in use would be setting Clip Lo to 0 on a wind speed sensor. These are purely aesthetic settings and will not affect the raw data,
they will also only clip the data so anything above your Clip Hi will be set back to that value (as opposed to error like you would see if using Error Lo/Hi in the custom/built-in converters).
Top of page
Drawn As
Drawn As determines the type of graph that will be drawn.
None: Used when you do not wish to show the trace of the data, but wish to display the actual values (shown on the right hand side of the graph).
Line: Default option for drawing traces. This will present the trace in a simple line format, but at the month view will change to bars.
Dots: Similar to a scatter graph, good for displaying data that will be "jumping" around a bit. In month view the format will change to bars.
Bars: Graphs the data in a bar form, this is not actually a bar graph, rather it displays the high (max point of the bar) and the low (bottom of the graph) and the trend for a segment of time.
Just Line: Displays the same as "Line" but stays in this form when viewing in month view.
Just Dots: As with Just Line, Just Dots displays the same as Dots, but will not change to bars in the month view.
Flow: Used for drawing flow rate graphs.
Botrytis: Leaf wetness can be used to calculate the Bacchus Botrytis risk. Use this when graphing the risk.
Ascospore/Conidial: Ascospore and Conidial graph types are both used in reference to Powdery Mildew.
Rain: Using this graph type will result in rain drops being drawn.
Wind Dirs: This graph type displays the data in a NSEW bearing format, this is primarily for wind direction
Digital: Best used with digital type data (0 or 1, on or off etc). Will graph with a simple line, showing state change by switching between two levels.
Blobs: A second approach to drawing digital data. Will draw a blob when the input is high (1/on) and nothing when it is low (0/off). Useful when graphing a wind machines engine run, as it
can be graphed on a temperature graph and it will draw the blobs at the top.
Flight: Used with the TSR, this will graph the flight time of an aircraft.
Calls: Adds a call marker to indicate when the unit made a call.
Top of page
Display
The display option box determines how the data is to be displayed.
Number: Default setting; displaying the data in a normal number format.
Digital: If the graph is of a digital format then use this. Changing the option will give two additional text boxes to enter the "states" of the input e.g. On/Off, Open/Closed.
Wind Dir: This setting will result in the data being displayed in a NSEW bearing format, this is primarily for wind direction.
Top of page
Min
Default: Checked
Shows the minimum value recorded within the current time period. This will not show for periods that are not complete. (E.g. when looking at the current day view it will not be complete due to the way the time-line progresses,
so there will be no min showing.)
Top of page
Avg
Default: Checked
Shows the average value for the current time period. This will not show for periods that are not complete. (E.g. when looking at the current day view it will not be complete due to the way the time-line progresses,
so there will be no avg showing.)
Top of page
Max
Default: Checked
Shows the maximum value recorded within the current time period. This will not show for periods that are not complete. (E.g. when looking at the current day view it will not be complete due to the way the time-line progresses,
so there will be no max showing.)
Top of page
Last
Default: Checked
Shows the last value recorded. If the last value is unavailable but there is a log, then it will display Error. This will not display if you look at historical data.
Top of page
Total
Default: Unchecked
Displays the "total" for the time period, used especially when dealing with rain or engine run time.
Top of page
GDD
Default: Unchecked
If you wish to calculate the Growing Degree Days for a particular temperature sensor check this box.
Top of page
RCU
Default: Unchecked
If you wish to calculate the Richardson Chill Units for a particular temperature sensor check this box.
Top of page
Int
Default: Unchecked
Intensity, setting this will display the max rainfall in the time period as well as calculating rainfall per hour.
Top of page
No AutoScale
Default: Unchecked
When unchecked, the system will graph the data in such a way that it makes the best use of space with only a small amount of area at the top and bottom beyond the max and min for the time period. If checked
this auto-scale function will be disabled. If checked and Clip lo or Clip hi are set it will use these as the constraints for the y-axis.
Top of page
Data Export
Default: Unchecked
Set this if the data is to be exported to a customer, must be used in conjunction with Data Export Clients and in most cases a SiteName Alias
will need to be set in the HSN and Menu names section.
Top of page
Decimal Places
Default: 1
This is fairly self explanatory, this controls the number of decimal places that is shown on the displayed data including Min, AVG, Max and
Last.
Top of page
Custom Converters
Custom Converter Details
Name: This is the name to be given to the converter, this will be what shows up in the Converter drop down box.
Unit: This is the unit that will be displayed on the graph (e.g. Pump Pressure (hPa)).
Input type: The type of input that this converter will be using.
Err lo: Sets a low point for the converter, this goes off the RAW data. If the RAW data is below this value then the converter will simply output ERROR.
Err hi: Similar to the Err lo, if the RAW data is above this value then the converter will output ERROR.
Delta: Optional value to scale the value by in delta time in seconds.
Scale: Scale that the unit will by multiplied by.
Offset: Offset to be applied to the scaled value.
Scale/offset Calculator: Used to calculate the scale and offset for a converter (SPE-2 and ITU-G1 only).
Display: Whether or not this converter will be displayed in the customer options page (only for certain customers like AWT) along with its offset.
Zero: The zero point for a converter, this is usually the initial value of the offset. This is used for calculating the final offset of the unit. (Offset - Zero = Applied Offset)
Top of page
SPE-2 and ITU-G1 Example Custom Converter
There are differences in the way the RAW data is handled and presented by the SPE-2/ITU-G1 and the ITU-G2. For both systems a converter for a depth sensor (5m pressure sensor) will be created.
For the SPE-2 and ITU-G1 there is a handy calculator for working out the correct Scale and Offset needed.
-Firstly name the converter, in this case "0-5m Depth".
-Input the unit to be used, in this case we could do it in m or in mm, .
-The Input type will be analog (this is a 4-20mA device, wired into the analog inputs).
-Leave Err Lo and Err Hi as "none" for now.
-Leave Delta as "none".
-Scale and offset will be calculated with the calculator tool, so click that to open up the input boxes.
-V1 is the bottom value for the reading, in this case since the device is 4-20mA we will enter 0.4.
-Y1 is the bottom value for the device's data range, in this case it is a 0-5000mm, so we will enter 0.
-V2 set as 2.
-Y2 set as 5 if you want it in m, otherwise 5000.
-Set the drop down box to 4-20mA and click calculate.
-The Scale and Offset boxes should read 1.9073.... and -1250 respectively.
-If you wish to display the applied offset, you will need to copy the offset into zero, and check the Display box.
Top of page
ITU-G2 Example Custom Converter
The setup for an ITU-G2 is the same as the above example until you get to the scale and offset.
For the ITU-G2 the Raw data is in an easier to understand format.
-4-20mA devices the data will be logged in a 0-1 format. I.e. 4mA is the equivalent to 0, and 20mA is 1.
-Voltage devices the data will be logged in the raw volts. I.e. 3V reading will be logged as 3.
-Since this is a 4-20mA device, we will use a scale of 5000. This means that at 0(4mA), we read 0mm, and then at 1 (20mA) we read 5000mm.
-The offset will be left as 0 for now, as well as Zero.
Top of page
Copy Settings
Copy Settings
This tool is for copying the config settings (and Maptable) of the current unit, to another unit.
Be Aware That:
-You have the correct destination unit.
-This will not copy any of the details in the HSN and Menu Names or Data Export Clients sections.
-If the units are ITU-G2's then the maptable will be need to be saved on the destination unit after it has been copied.
-This will NOT copy SPE settings. The only way to do this is with profiles.
-Quick view and alarm settings will not be copied.
Top of page
Log Operations
Log Operations
This section is for simple log operations. Specifically used for copying/merging logs from another unit onto the current one.
Deleting logs is fairly simple, select the date range you wish to delete the logs for and click Delete Logs.
For merging logs there are a few things to remember:
-Do not try and merge logs from an ITU-G1 with an ITU-G2 (or vice versa). The log formats are different and will result in erroneous data in the logs.
-This will overwrite any data you currently have.
-The data is merged based on the Maptable input number, this means if you have swapped sensors over to different inputs you may need to perform log manipulations with the "Multi" tool.
Top of page
Quick View
Quick View
This is for creating a Quick View group (or adding a unit to an existing group).
To create a new group, simply type the name into the Group name box (this also affects the wap path, so if you set the group as testunit, the user can go to www.harvest.com/testunit on their phone).
To add to an existing group, choose the group name from the drop down list.
Top of page
Alarms
Graphs and Traces
Graph-Trace: This is where you select the data that you want to alarm off, you must have already set up a trace in the graphs for it to be visible in this drop down box.
Alarms: Enter the name of the alarm (found in Alarm Levels) that you wish to apply to the trace.
Top of page
Only Send Alarm If D1 On
Only Send Alarm If D1 On
Top of page
Alarm Levels
Alarms: The alarm name, this is what will be entered in the Alarms part of the Graphs and Traces.
Name: This is the name of the alarm, if the "Custom" check box is set it will be the actual alarm message that is sent.
Custom: Set this if you wish to send a custom alarm (the custom message will need to be entered into the "Name").
Level: Set this for the level at which the alarm will be sent
Reset: Set this for the level at which the alarm will be reset and be ready to send another alarm
Roster: Select the Roster that the alarm will be sent to.
Delay: (Minutes) This allows you to set a time delay on sending the alarm. If the trace is still in the alarm state when the delay elapses then it will send the alarm, otherwise it will not.
This is useful for avoiding erroneous alarms (such as a spike on a depth sensor) and setting up alerts for when a trace has been "normal" for an extended period of time
(e.g. overflow alarm that has been normal for 24 hours)
Always Send: If checked the alarm will always be sent, including if the unit was "logging" but not "calling". (Unit may have gone into frost 3 hours ago and then back to normal an hour later,
but the unit has only just called, if this box was checked it would send the alarm.)
Top of page
Conditional Alarms
A Conditional Alarm consists of one or more Groups, each containing one or more Conditions.
There are two types of groups: Alarm and Reset.
The Alarm groups are ORed together to determine the alarm state whereas the individual conditions within each group are ANDed.
Similarly the Reset groups are ORed together to determine the reset state.
In other words, if all the conditions in any one of the Alarm groups are met then the alarm will be sent.
Or, if all the conditions in any one of the Reset groups are met then the alarm will be reset.
Log Delay: (Minutes) How long after each condition's delay to keep checking logs (in case the log time doesn't exactly match up).
Restrict To: The alarm will only be sent on the checked days and only between the selected hours/minutes on those days.
T1: The first trace to be compared.
Condition: The condition used to compare T1 and T2.
T2: The second trace (or specified value) to be compared. If 'Use Value In Box' is selected then T1 is compared to the value entered in the box.
Delay: (Minutes) How long to wait from the time the initial condition(s) are met before checking this condition.
Period: (Minutes) If the 'Whole Period' checkbox is ticked then this specifies how long this condition must be met. This can be set to a huge value to keep checking the condition indefinitely (if 'Whole Period' is unchecked).
Repeat: (Minutes) After an alarm is sent the alarm will keep being resent if this condition (along with any other conditions in the same group with a repeat greater than 0) is still met.
Look at Rangitoto Dairies for a fairly complicated example.
Top of page
Rate of Change Alarms
Most of the setup is the same as a normal alarm, the only differences are:
Change: The amount of change that the trace has to go through within the set period.
Period: The period of time over which the trace must reach the desired change for an alarm to be sent.
Top of page
Roster
Roster: Name of the roster, this is what will be available in the drop down box "Roster" when setting up alarms
Name: Name of the individual that the following number/email belongs to.
Number or Email: Either the individuals landline, mobile phone, or email will be entered here. Make sure to set the correct "type".
Type: The type of medium the previous text box will use. Options include:
-Text Message: Will send a text message to any mobile phone (Telecom numbers will have alarms sent via Telecom phone and Vodafone via Vodafone phone).
-Voice Call: Will send a voice call to a land line or mobile. Please limit voice calls to two per unit (one if the unit is situated overseas).
-Email: Will send an email to the recipient.
-HttpPost:
-Harvest Alias:
-Command:
-None: Will not send any alarms to this recipient, useful for keeping a name and number for future use if you don't wish to send alarms to them currently.
TimeStamp: Will add a timestamp to the end of the alarm, This refers to the time at which the trace reached the alarm level.
-(Bolded part is the timestamp) ****- ************************: Depth 30MIN (61mm) 10 Nov 2010 22:55.
Alarms are on: Options that dictate when (if at all) alarms will be sent to the roster.
Always: Will always send alarms (off)
Never: Will never send alarms (off)
In Season: Allows you to set a date-range in which the alarms will be active. Day/Month -> Day/Month
Top of page
Alarm Group
Alarm groups work similar to Quick View Groups if you are creating a new group, simply enter the name of the group (current convention is
regionInitials.Owner.UnitName e.g. wai.harvest.solway).
Otherwise to add it do a current group, select the group from the drop down list, save the config, then adjust the Graphs and Traces.
Top of page
|
Search
Home
Online Solutions
Products
Product Support
Picture Gallery