Qualcomm OBDII J1708 Guía para resolver problemas descargar pdf (Pagina 71)

80-JB566-1 Rev. C 25-1

MAY CONTAIN U.S. AND INTERNATIONAL EXPORT CONTROLLED INFORMATION

Critical Event Reporting Troubleshooting

Overview

Critical Event Reporting (CER) captures and reports vehicle critical event information (e.g.,

hard braking, vehicle speed, location, stability control (VDC), lane departure warning (LDW),

and panic button events). With each hard braking event, five minutes of speed information is

recorded and sent to the CER host system. Events are processed two minutes after they

occur.

Normal Performance

In order for the CER feature to function, the MCP50 must be connected to the vehicle’s data

link wires.

Critical events can be triggered by a:

• Hard Brake event

• Stability Control event (if available)

• Lane Departure Warning (LDW) (if option is installed)

• Manually triggered CER event.

Text-to-speech (TTS) can be enabled so CER events can be audibly conveyed to the driver.

Abnormal Performance

If any of the above items do not trigger a CER event, or if a critical event is reported in error,

there is a problem. A problem is usually caused by one or more of the following:

• The unit is misconfigured

• Loose or bad connection to the data link

• Intermittent data supplied by stability control device or lane departure warning device

• Intermittent data supplied by ECM of vehicle

1 2 ... 66 67 68 69 70 71 72 73 74 75 76 ... 109 110

Sin comentarios

Qualcomm OBDII J1708 Guía para resolver problemas Pagina 71