Fatigue system Information

Fatigue Snapshot Photos

How the system talks to each other:

  1. When the fatigue camera detects an events or is requested, the camera takes a snapshot photo and sends this to the tracking device

  2. The tracking devices saves this image in the external SD card and generates a new high priority data packet. The tracker then packs the new AVL data packet containing the event trigger and sends this to there GPS platform server whilst simultaneously sending the snapshot photo to the LMS fatigue server.

  3. The GPS platform server receives the new AVL data packet then unpacks this data. once done so, the server now updates the users account and generates a event alert. At the same time, the LMS fatigue server is downloading the snapshot photo then synchronizing the photo with client folder allowing the end user to view the photo in there personal Share Point folder.

Video footage around the triggered event will be saved locally on the camera modem and you can access this if need be via the cameras mobile app - Camera mobile app guide.

Video footage can not be accessed remotely and requires you to be with in range of the camera system to connect a mobile device.

Snapshot Overlay

When you receive a new snapshot photo, there will be a text overlay showing a time/date stamp from the time of the event and also a explanation of the event (Yawning, Drowsiness, Distraction, Phone usage, Requested)

The first explanations are self explanatory, but when a photo shows “Requested” this can be a few different things.

You need to understand that when a photo shows requested, the tracker has asked for a photo to be taken, this could be from:

  • Ignition on trigger

  • Harsh driving events

  • Crash detection

  • GPRS request

Adjustable DSM Parameters