Skip to main content
Sign in

Events-settings

Marisa Potgieter
  • Updated

FCPlus Events settings

Events settings

This manual describes in detailed settings that can be used to create Events, more information Events and how to use them can be found in Events manual. 

Please follow the steps below to access the Settings module in FCPlus and review the already created events:

1. Log in to FCPlus. 2. Click on the Settings module on the top right. 3. Click on the Events Tab under the Settings module.

The Events settings screen lists all the existing events on the left-hand side.

The selected check boxes next to each event indicate that the event is activated for the account. 

Notifications will be received once the event is triggered by vehicles.

You can choose to Lock events you no longer wish to receive notifications. You can also use the Search and Edit existing event conditions from the events tab in the Settings Module.

Create a new event

Follow the steps below to create a new Event:

  1. Click Open the Events Tab of the Settings Module. 
  2. Click on the Add New button on the top.

3.Event form on the right-hand side will be enabled.

  1. Enter all the necessary details in the Rule section of the Event form like:
  • Name: Each event has a name. When naming an event, it is recommended to choose a short and descriptive name, for example, "Speeding" or "Lengthy stop".

  • Condition: Each event is linked to a particular condition, a circumstance like a Vehicle stopping or battery voltage changes. The condition chosen is the critical element of an event. The following conditions are available:

  • Card is not inserted - event can be configured to be triggered after some minutes past the card extraction, or after a number of log points.

  • Check engine warning- "Check engine" warning on the dashboard; the corresponding CAN information depends on the device and installation.
  • Diagnostic trouble code - An event occurs when a new fault code is registered, depending on the device and installation.
  • Din turned off - The device's DIN (din1-3) is turned off.
  • Din turned on - The device's DIN (din1-3) is turned on.
  • Driving without card inserted - TCO Driver1 Working State = 3 (driving), TCO Driver1 Card Present = 0 (no card inserted), the tachograph indicates that the vehicle is driving without a card.
  • Engine status change - Change in ignition status.
  • Entering area - Entering an area.
  • EV remaining battery - CAN parameter EVStateOfCharge, if the value is less than X.
  • EV remaining distance - CAN parameter EVDistanceRemaining, if the value is less than X.
  • Event with code - Each log entry has a code, based on which the event is recorded.
  • Fuel decreasing - Fuel decrease when the engine is not running (Ruptela and Teltonika + fuel sensors are required).
  • Fuel level - Fuel level <> than X liters.
  • GH ButtonID - GH handheld device reads RFID identifiers.
  • GPS with status false - GPS cannot transmit correct coordinates.
  • Idling - Ignition is on, and speed is below 1 km/h.
  • Leaving area- Leaving an area.
  • Moving while ignition off - Ignition is off, and speed exceeds 10 km/h.
  • Next service reminder - CANServiceDistance parameter < X, availability depends on the device and installation.
  • Remaining internal battery - The charge level of the device's internal battery <> X volts.
  • Service now warning - When the vehicles's "Service-now" light turns on, availability depends on the device and installation.
  • Speed - Speed is <>, if X km/h.
  • Starting to move - Ignition is on, and speed exceeds 1 km/h.
  • Status off - Device status is off.
  • Status on - Device status is on.
  • Stopping - Ignition is on, and speed drops below 1 km/h.
  • Temperature - Temperature value <>, if it is above X ℃ and lasts more than X minutes.
  • Temperature sensor not sending data - Temperature sensor is not sending data for more than X minutes.
  • Temperature with engine OFF - Temperature when the engine is turned off.
  • Temperature with engine ON - Temperature when the engine is turned on.
  • Tire pressure warning - Tire pressure warning.
  • Trip end - Speed drops below 1 km/h, and the engine is turned off.
  • Turning ignition off - Turning off the ignition.
  • Turning ignition on - Turning on the ignition.
  • Vehicle hasn't sent any data - If the device has not sent data for more than X minutes.
  • Vehicle starts driving - The engine is started, and speed exceeds 1 km/h.
  • Vehicle weight - Vehicle weight parameter changes over X (CAN info, depends on the device, installation, and the vehicle's ability to transmit data).
  • Voltage - The device's supply voltage is V <> X, which may indicate the vehicle's battery is discharging.

  1. Enter details in the restriction section of the Event form.

  2. By default, the event condition applies to all vehicles in all locations at all times. However, there are three ways to restrict the condition:

  • Vehicles: The condition may apply to every vehicle in the organization (default) or a sub-selection/Options:

  • All vehicles: The rule is applied to all vehicles in the organization.

  • Vehicles by groups: This allows you to choose vehicle group(s) from the selection.
  • Individual vehicles: This allows you to choose from a list of all vehicles in the organization. Multiple personal vehicles may be selected.

  • Location: The condition may apply everywhere (default) or only in particular areas (defined in the Areas module) or to a sub-selection/Options:

  • Everywhere:  Applies irrelevant of location.

  • Inside any area:  Applies inside any location that has been defined in the organization.
  • Inside area group:  Select an area group. The rule applies if the vehicle is inside any area within the group.
  • Inside individual areas: Select individual areas from a list. The rule applies if the vehicle is inside any area selected.
  • Outside of area group:  Select an area group. The rule applies if the vehicle is outside every area of the area group.
  • Outside of individual areas: Select individual areas from a list. The rule applies if the vehicle is outside all of the selected regions.

  • Time: The Condition may always apply (default) or at selected times, for example, at working hours. Options include:

  • Always: The rule always applies.

  • At the working time: The rule applies during working time.
  • Outside of working time:  The rule applies at any time that is not inside working time.
  • At the specified time:  You can specify weekdays and time ranges at which the rule applies.
  1. Enter Actions, as necessary.

Actions define what happens if the conditions are met. If no action has been chosen, FCPlus will still show the event in the events list. For example, the following actions are possible:

  • Notification within application: If the event occurs, all users logged in will see a grey pop-up box with the event's name and the concerned vehicle.
  • Sound signal: If the event occurs, all users logged in will hear a sound signal.

  • E-mail: An e-mail will be sent to the specified user. Multiple users can be specified; commas should then separate the e-mail addresses. The e-mail sent will have the following content:

  • Event name: Name of the event as entered under Settings > Events.

  • Data: Numerical value of the event.
  • Started: 10.02.2011 16:27:16 The start of the event.
  • Vehicle: 123ABC. Info of the vehicle.
  • Place(s): Location where the event took place.
  • SMS: An SMS will be sent to the specified user. The country code should be entered with the phone number (e.g. Estonia + 372...) Thus, multiple users can be identified; commas should then separate the phone numbers
  1. Click the Save button on the bottom.

Turning ignition off event - Reset driver

You can reset the driver when using the "Turn Ignition Off" event. To find this feature, go to the Settings module, click on the Events tab, and select the condition "Turn ignition off" from the down list.

If option 'reset driver' is ticked, when a specific Event takes place, the driver currently assigned to the vehicle is 'kicked out.' When this happens, the vehicle is either: * left driver-less until the next driver identifies or * assigned back to the default driver if one is present.

Set up HTTP post for an event

You can define an event record that system will send via HTTP-post by following the steps below: 

  1. Open the Settings and navigate to the Events tab.
  2. Choose the event for which you want to configure an HTTP-post action.
  3. In the event's settings, check the box labeled HTTP POST.
  4. Add the desired link or URL where the HTTP-post should be sent.
  5. Once you have configured the event with the necessary HTTP-post URL, click Save.

Example of received information:

{

"method": "POST",

"headers": {

"Host": "...",

"Content-Type": "multipart\/form-data; boundary=------------------------3cefefcdc75c3194",

"Content-Length": "2484",

"Accept": "*\/*"

},

"POST": {

"id": "455978159", -- event id

"title": "Engine Off", -- event name (this should be agreed as user can name them)

"time": "10.02.2025 12:48:18", -- event timestamp

"startTimeStamp": "2025-02-10T10:48:18.829Z",

"orgId": "15983",  -- Customer organization id

"organizationName": "Somecompany Ltd", -- Customer organization name

"objectId": "422164", -- unique id of the vehicle in FC system

"lat": "58.378498",

"lon": "26.718408",

"location": "https:\/\/maps.google.com\/maps?q=58.378498,26.718408",   -- link to open this place in googlemaps

"objectName": "Testing object",

"placeNames": "-- address of the event --",

"loginAt": " -- just system login url for this account --",

"headerEncoding": "UTF-8",

"driverName": "John Smith", -- driver name if it was identified specifically

"plate": "123 ABC", -- vehicle plate no.

"deviceSerial": "2309842903849328",

"defaultDriverName": "John Smith", -- default driver name if it was set

"defaultDriverEmail": "John.Smith@somecompany.com"

},

"timestamp": "2025-02-10 12:48:28"

}

Powered by Zendesk