{"id":1430,"date":"2017-12-04T22:36:16","date_gmt":"2017-12-04T22:36:16","guid":{"rendered":"http:\/\/wiki.intouchgps.info\/?page_id=1430"},"modified":"2019-02-28T11:45:54","modified_gmt":"2019-02-28T16:45:54","slug":"malfunction-and-data-diagnostic-events","status":"publish","type":"page","link":"https:\/\/wiki.intouchgps.info\/index.php\/malfunction-and-data-diagnostic-events\/","title":{"rendered":"Malfunction and Data Diagnostic Events"},"content":{"rendered":"

Back to ELD Driver App<\/a><\/strong><\/p>\n

Malfunction and Data Diagnostic Events<\/strong><\/h3>\n\n\n\n\n\n\n\n\n\n\n\n
Malfunction Events<\/strong><\/span><\/td>\n<\/tr>\n
Requirement No.<\/strong><\/span><\/td>\n Event Code<\/strong><\/span><\/td>\n Event Name<\/strong><\/span><\/td>\nDescription<\/strong><\/span><\/td>\n<\/tr>\n
4.6.1.1<\/a><\/span><\/td>\nP \/ Power MF<\/span><\/td>\nPower Malfunction <\/span><\/td>\nAn ELD must set a power compliance malfunction if the power data diagnostics event described in paragraph 4.6.1.1(a) of this appendix indicates an aggregated in-motion driving time understatement of 30 minutes or more on the ELD over a 24-hour period across all driver profiles, including the unidentified driver profile.<\/span><\/td>\n<\/tr>\n
4.6.1.2 <\/span><\/a><\/td>\n E \/ Sync MF<\/span><\/td>\nEngine Synchronization Malfunction <\/span><\/td>\n An ELD must set an engine synchronization compliance malfunction if connectivity to any of the required data sources specified in section 4.3.1 of this 87 appendix is lost for more than 30 minutesduring a 24-hour period aggregated across all driver profiles, including the unidentified driver profile. <\/span><\/td>\n<\/tr>\n
 4.6.1.3<\/span><\/a><\/td>\n T \/ Timing MF<\/span><\/td>\nTiming Malfunction <\/span><\/td>\nThe ELD must periodically cross-check its compliance with the requirement specified in section 4.3.1.5 of this appendix with respect to an accurate external UTC source and must record a timing compliance malfunction when it can no longer meet the underlying compliance requirement.  <\/span><\/td>\n<\/tr>\n
4.6.1.4 <\/span><\/a><\/td>\n L \/ Pos MF<\/span><\/td>\nPosition Malfunction <\/span><\/td>\n ELD records requiring location information must use the last valid position measurement and include the latitude\/longitudecoordinates and distance traveled, in miles, since the last valid position measurement.<\/span><\/p>\n

An ELD must monitor elapsed time during periods when the ELD fails to acquire a valid position measurement within 5 miles of the CMV\u2019s movement. When such elapsed time exceeds a cumulative 60 minutes over a 24 hour period, the ELD must set and record a positioning compliance malfunction.<\/span><\/td>\n<\/tr>\n

 4.6.1.5<\/span><\/a><\/td>\n R \/ DR MF<\/span><\/td>\nData Recording Malfunction <\/span><\/td>\n An ELD must monitor its storage capacity and integrity and must detect a data recording compliance malfunction if it can no longer record or retain required events or retrieve recorded logs that are not otherwise catalogued remotely by the motor carrier. <\/span><\/td>\n<\/tr>\n
 4.6.1.7<\/span><\/a><\/td>\n S \/ Trans MF<\/span><\/td>\nData Transfer Malfunction<\/span><\/td>\n(a) An ELD must implement in-service monitoring functions to verify that the data transfer mechanism(s) described in section 4.9.1 of this appendix are continuing to function properly. An ELD must verify this functionality at least once every 7 days. <\/span>
\nThese monitoring functions may be automatic or may involve manual steps for a driver.<\/span>(c) After an ELD records a data transfer data diagnostic event, the ELD must increase the frequency of the monitoring function to check at least once every 24-hour period. If the ELD stays in the unconfirmed data transfer mode following the next three 90 consecutive monitoring checks, the ELD must detect a data transfer compliance malfunction.<\/span><\/td>\n<\/tr>\n
4.1.6.8 <\/span><\/a><\/td>\n O \/ Other MF<\/span><\/td>\nOther Malfunction<\/span><\/td>\nIn addition to the required monitoring schemes described in sections 4.6.1.1\u2013 4.6.1.7 of this appendix, the ELD provider may implement additional, technology-specific malfunction and data diagnostic detection schemes and may use the ELD\u2019s
\nmalfunction status indicator and data diagnostic status indicator (described in sections 4.6.2.1 and 4.6.3.1) to communicate the ELD\u2019s malfunction or non-compliant state to the operator(s) of the ELD.  <\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n\n\n\n\n\n\n\n\n\n
Data Diagnostic Events<\/span><\/strong><\/span><\/td>\n<\/tr>\n
Requirement No.<\/span><\/strong><\/span><\/td>\nEvent Code<\/span><\/strong><\/span><\/td>\nEvent Name<\/span><\/strong><\/span><\/td>\nDescription<\/span><\/strong><\/span><\/td>\n<\/tr>\n
4.6.1.1 <\/span><\/a><\/td>\n1 \/ Pwd Diag<\/span><\/td>\nPower Diagnostic<\/span><\/td>\nAn ELD must monitor data it receives from the engine ECM or alternative sources as allowed in sections 4.3.1.1-4.3.1.4 of this appendix, its onboard sensors, and data record history to identify instances when it may not have complied with the power requirements specified in section 4.3.1.1, in which case, the ELD must record a power data diagnostics event for the corresponding driver(s), or under the unidentified driver profile if no drivers were authenticated at the time of detection.<\/span><\/td>\n<\/tr>\n
4.6.1.2 <\/span><\/a><\/td>\n2 \/ Sync Diag<\/span><\/td>\nEngine Synchronization Diagnostic<\/span><\/td>\n An ELD required to establish a link to the engine ECM as described in section 4.2 must monitor its connectivity to the engine ECM and its ability to retrieve the vehicle parameters described under section 4.3.1 of this appendix and must record an engine-synchronization data diagnostics event when it no longer can acquire updated values for the ELD parameters required for records within 5 seconds of the need.<\/span><\/td>\n<\/tr>\n
 4.1.6.4 (d)<\/span><\/a><\/td>\n3 \/ Miss Diag<\/span><\/td>\nMissing Data Elements Diagnostic<\/span><\/td>\nIf a new ELD event must be recorded at an instance when the ELD had failed to acquire a valid position measurement within the most recent elapsed 5 miles of driving, but the ELD has not yet set a positioning compliance malfunction, the ELD must record the character \u201cX\u201d in both the latitude and longitude fields, unless location is 88 entered manually by the driver, in which case it must log the character \u201cM\u201d instead. Under the circumstances listed in this paragraph, if the ELD event is due to a change in duty status for the driver, the ELD must prompt the driver to enter location manually in accordance with section 4.3.2.7 of this appendix. If the driver does notenter the location information and the vehicle is in motion, the ELD must record a missing required data element data diagnostic event for the driver. <\/span><\/td>\n<\/tr>\n
4.1.6.7 <\/span><\/a><\/td>\n4 \/ Tran Diag<\/span><\/td>\nData Transfer Diagnostic<\/span><\/td>\n(b) If the monitoring mechanism fails to confirm proper in-service operation of the data transfer mechanism(s), an ELD must record a data transfer data diagnostic event and enter an unconfirmed data transfer mode.<\/span><\/td>\n<\/tr>\n
4.6.1.6 <\/span><\/a><\/td>\n5 \/ Unid Diag<\/span><\/td>\nUnidentified Driver DIagnostic<\/span><\/td>\n(b) If more than 30 minutes of driving in a 24-hour period show unidentified driver on the ELD, the ELD must detect and record an unidentified driving records data diagnostic event and the data diagnostic indicator must be turned on for all drivers logged in to that ELD for the current 24-hour period and the following 7 days.<\/span><\/p>\n

(c) An unidentified driving records data diagnostic event can be cleared by the ELD when driving time logged under the unidentified driver profile for the current 24-hour period and the previous 7 consecutive days drops to 15 minutes or less.<\/span><\/td>\n<\/tr>\n

 4.1.6.8<\/span><\/a><\/td>\n6 \/ Other Diag<\/span><\/td>\nOther Diagnostic<\/span><\/td>\nIn addition to the required monitoring schemes described in sections 4.6.1.1\u2013 4.6.1.7 of this appendix, the ELD provider may implement additional, technology-specific malfunction and data diagnostic detection schemes and may use the ELD\u2019s <\/span>
\nmalfunction status indicator and data diagnostic status indicator (described in sections 4.6.2.1 and 4.6.3.1) to communicate the ELD\u2019s malfunction or non-compliant state to the operator(s) of the ELD.   <\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Actions for Malfunction & Data Diagnostic Events<\/h4>\n

Carrier responsibilities regarding malfunctions:<\/h5>\n