| Malfunction Notes | ELD functionality has 2 components: 1. iOS application that is running on a iOS device (iPhone or iPad with a data plan) 2. Digi WVA (Wireless Vehicle Bus Adapter) J1939 device iOS application is connecting wireless to the WVA device. When the application is started it tries to connect to the device at every 10 seconds by sending a sequence of calls to get engine parameters (total distance, total engine hours, engine speed, vehicle speed, truck VIN). If the calls fails then there are 2 cases: 1. iOS app can't connect to the WVA because the driver is not in the truck(iOS device is not in the truck), in this case when the popup that is asking the driver "Is the device connected?" the user should select "No", in this case no diagnostics will be recorded. 2. iOS app can't get engine params, in this case if the call tooked more than 5 seconds a diagnostic event will be recorded. When the driver logs out then we are doing a "Clear All" diagnostic events for that user because Diagnostics are recorded for each driver. For Power Compliance Malfunction (P): If the iOS app is connected to the WVA and the call to get Engine Speed takes more than 5 seconds then a Power Data Diagnostic event is recorded. Power data Diagnostic can be cleared: a.) automatically when a call for getting the engine speed is successfully (clear event was recorded). b.) manually when the driver taps on the clear button from the Diagnostic list. When clearing Diagnostics, we are checking the duration of the diagnostic event (started-ended). If the accumulated duration is greater than 30 min then we are recording a Malfunction Power Data Diagnostic Power Compliance Malfunction can be manually cleared by tapping on the clear button from Malfunctions list. Engine Synchronization Malfunction (E): If the iOS app is connected to the WVA device and if the call to get engine params(total distance, total engine hours, vehicle speed, VIN) takes more than 5 seconds then a "Engine Synchronization Diagnostic" event" is recorded. Engine Synchronization Diagnostic can be cleared: a.) automatically (clear event was recorded) when a call for getting the engine parameter (total distance, total engine hours, speed) is successfully. b.) manually when the driver taps on the "Clear" button from the Diagnostic list. When clearing the Diagnostic event we are checking to see the duration of the event, if is greater than 30 min we are recording a Engine Sync Malfunction. For making everything more clear we are recording Engine Diagnostic events for each parameter: total distance, total engine hours, vehicle speed, truck VIN. Engine Sync Malfunction can be cleared also manually by tapping on the clear button from the Malfunctions List. Timing compliance Malfunction (T): Every time when we start the iOS app we are making a call to get the current UTC time (using a third party server) If the difference from the current local time from iOS device is greater than 10 minutes then a Timing Compliance Malfunction event is recorded. Timing Malfunctions can be manually cleared by the driver from the Malfunctions list. Position Compliance Malfunction (L): Every time when we receive the response for getting the Total Distance parameter, we are checking if we need to record a "Diagnostic Missing Required Data Element" event for Position. We are checking to see if the distance since the previous call is greater than 5 miles. If is > 5 miles then we are checking to see if the latitude or longitude changed also since the previous values. If Latitude and longitude didn't changed then we are recording a "Diagnostic Start For Missing Required Elements" for the Position Key. If the next call for getting the distance returns valid data and the distance that passed is > 5 miles and Latitude and Longitude have changed then we are recording a Diagnostic End event for Missing Required Elements for key Position. When clearing the Diagnostic event we are checking the accumulated duration of the Missing Required Data Elements is > 60 min then we are recording the Position Compliance Malfunction event. Data Recording Malfunction (R): If saving of a Event fails then a Data Recording Malfunction event is recorded. Data Transfer Compliance (S): We have implemented "In Monitor" functionality which alerts the driver to check the transfer functionality. If there is no successfully Transfer RODs File in the last 7 days then a popup will be shown to ask the user to check the Data Transfer functionality. If the driver consider that is working then a custom Event will be recorded to save the date and time. If a "Data Transfer Diagnostic" is recorded then a popup will be shown at every 24 hours to check the functionality. When a transfer fails then a "Data Transfer Diagnostic" Start is recorded and when the transfer is successfully a "Data Transfer Diagnostic" Clear (ended) is recorded. If the driver didn't checked the In Monitor functionality for 3 days since recording a "Data Transfer Malfunction" is recorded. |
