ALEOS 4.3.4 Software Configuration User Guide
208 4114514
2. After deployment, the device begins measuring a physical input.
3. The measurement is compared to the user-configured threshold or state
change. If there is no change, then another measurement is performed. If a
state change (or threshold crossing) occurs, then the flow moves to step 4.
4. The Action associated with the Event. In this step, a report may be generated,
or some other activity is performed. Afterwards, the flow returns to step 1.
Additional Behavior and Features
Events/Actions are not one shot activities. After an Action is performed, the Event
is still active and will trigger the next time the state change or threshold crossing
occurs.
A single Event may activate one or more Actions. For example, if RSSI is below
threshold, you can turn off data services (Action 1) and send an SMS message
(Action 2).
A single Action may be activated by one or more Events. For example, if the
vehicle speed is above a threshold or if the vehicle heading changes, either Event
can perform the same action.
After defining an Event, always select the Apply button to save these definitions
and apply them to an Action.
Selecting the Delete button on the Events Reporting tab will delete all current
Event and Action data.
Configuration Overview
To configure Events and Actions, complete the following steps:
Note: All Events Reporting configuration changes take effect after a short delay (about one
minute). No reboot of the AirLink device is necessary.
1. Define an Event – Events can be configured using the ACEmanager user
interface. Select the Events Reporting Tab, and then select the Add New
subtab to add an event (e.g., RSSI).
Note in the Action Description frame that there are no actions listed.
Comments to this Manuals