00:00 |
Each package allows us to configure a wide range of package-based warnings and we we will deal with these a little further through the course.
|
00:08 |
These package based warnings can be viewed through the ‘Warning Source’ element that can be found on a number of the worksheets in a particular package.
|
00:17 |
There are worksheets however that don’t include a warning source element, and if you are on one of these worksheets, you may not notice that a warning has become active.
|
00:27 |
Tune-based alarms are a convenient way of allow you to configure any alarms you want, and have them pop up regardless of where you are at the time.
|
00:36 |
We can configure these alarms by clicking on the warning icon here.
|
00:40 |
This should be very familiar to anyone who has configured a MoTeC dash, and the setup is similar.
|
00:47 |
We can start by clicking ‘Add’, to add a new warning. Now we can give the warning a name.
|
00:53 |
For this example, lets set up a engine temperature warning, so we can call the warning ‘Coolant Temperature’.
|
01:01 |
Below this we can choose what will happen when the warning is triggered.
|
01:06 |
Normally we would want to choose either ‘Alert’ which will bring up a box on the screen, or ‘Warning’, which is a little more subtle and will display the warning on the bottom status bar.
|
01:17 |
With these warnings we can also choose to play a sound when the warning is triggered, or alternatively when it is active to bring your attention to the alarm.
|
01:26 |
Now we can enter the conditions that we want the warning to trigger.
|
01:30 |
In this case we can start by searching for ‘Coolant Temperature’ in the search box here.
|
01:37 |
We can then use the greater than symbol and enter the temperature we want the warning to trigger at.
|
01:42 |
In this case I’m going to enter eighty degrees.
|
01:46 |
We can also choose how long to wait after the alarm is acknowledged before it becomes active again.
|
01:52 |
This prevents the alarm constantly popping back up.
|
01:56 |
Once I’m are happy with the alarm, I can press Ok. Since the coolant temperature is below 80 degrees, nothing will happen.
|
02:04 |
Let’s open the alarm back up though and change the temperature to 30 degrees.
|
02:09 |
Now when I press OK, you can see the alarm is instantly activated, and an alarm box pops up to warn me.
|
02:16 |
I can press ‘A’ to acknowledge the alarm and the warning will disappear.
|
02:22 |
If the coolant temperature remains above the threshold, the alarm will activate again after the programmed delay time elapses.
|
02:30 |
Now let’s see what happens when we open the alarm again and change it from an alarm, into a warning.
|
02:36 |
If we press OK, you can see that this time rather than a window opening up, the alarm is displayed in the lower status bar.
|
02:43 |
If we press shift and F3, this will open the alarm window where we can see the details of the alarm.
|
02:49 |
This is a slightly less obtrusive way of bringing our attention to a particular warning.
|
02:55 |
When the alarm window is open, we can click on the ‘Log’ tab to view a log of all of the alarms.
|
03:01 |
We can see when they have become active and when they have been acknowledged.
|
03:06 |
We can create as many alarms as we want here, and we can use a combination of alarms and warnings depending on the severity of the event.
|