Skip to content
Safee Documentation

5-7-0

Release 5.7.0

Augmented Arguments

We are glad to announce a new feature that facilitates your operational work. The main goal of this feature is to give you as much flexibility as possible in using your devices’ inputs/outputs and some other parameters.

The service is about adding rules for each available argument, then determining the source of this argument. And of course, applying the rule to the target device(s) type/model. It’s equipped with default settings that can be overridden by the partner account or, furthermore, by the company account.

This feature is controlled by a permission, so the partner can grant it to the company admin.

Now, to access the feature, after getting the permission, go to the management tab, then “Augmented Arguments”. You’ll find 2 pages under this menu:

  1. Management/Exploring:

Here you can check the created rules or add new rules. If you click on the green button on the top corner of the page “Add”, you’ll enter the wizard of adding a new rule which consists of the following steps:

  • Introduction: First step is just an introduction to what you are going through
  • Argument Type: The second step is to determine the argument you need to set. Here you’ll find the most common arguments used in our partners’ devices. the available arguments for now are:
    • SOS: you can choose what digital input to use as a panic source.
    • Driver seatbelt: you can choose what digital input to use as a driver seatbelt indicator
    • Analog weight: you can choose whether to read the analog inputs and interpret them as the weight source -depending on the analog weight module configuration, or to use the combined weight provided by some CAN-Bus interfaces.
    • Trip type: this is currently fixed to digital inputs 3 & 4
    • Analog fuel sensor output: you can choose what analog input to use as the fuel source.
    • Ignition: if the device doesn’t have a dedicated ignition line and you use a digital input for the ignition, you can choose here what digital input is in use.
    • Driver ID: here you can choose whether your device reports the driver key via an ibutton report (1-wire interface) or an RFID (serial interface) one.
    • Four-wheel drive: you can choose what digital input is indicating the 4-wheel status
    • Temperature: this argument is to configure BLE sensors only. If you are using other temperature sensors, please don’t add a rule for them. Through this argument, you can add the appropriate scale for the BLE temperature readings along with the effective values range, so the system omits any value outside the defined range.
  • Argument Resolver: in this step, you’ll determine the source of the selected argument. E.g., if you choose in the second step to set the driver seatbelt argument, You need to set in this step the digital input used as a driver seatbelt. You’ll find in this step too the “process method” you prefer to adopt. That is:
    • If you want to override any directly received value from the device for the selected argument by the rule you are adding, choose “add anyway”
    • If you want to have the value gained thru this rule only and ignore the values received from the device directly, choose “clear previous data then add”
    • If you want to have a value for the selected argument whether the value is gained thru this rule or from the device directly, choose “add only if no previous data”. This option might be tricky a little bit, you need to make sure that there won’t be bad data upon alternately depending on directly received data and data obtained via the rule you are creating.
  • Device Types/Models: finally, you can choose what type/models of devices to which the rule will be applied. You need to tick the checkbox of the target device type to include it and click on the button “All Models” to switch to choosing specific models of your interest — if needed.
  • Confirmation: like all other wizards on our platform, last step is always for revising your choices and confirming.
  1. Explore Applicable:

On this page, you can check what rules (along with all related details) are applied to a specific vehicle under the account or a specific device type/model.

  1. You need to over-pay attention Not to adding 2 rules for the same argument in the same device type and model. The system will warn you in case of such a conflict and it’s your responsibility to fix it; otherwise, we can’t guarantee what rule will be applied to each received message and how fidelity the data will be.

  2. A rule’s priority starts at the lowest level, that is, if 2 levels (partner and company accounts) apply a rule related to the same argument on the same device type and model, the rule created by the lower level (company account) will be considered, and the rule created by the higher level (partner account) will be ignored.