|
|
|
Programming Not Attempted - The DRBIII t attempts to read the programmed key status and Programming Key Failed - (Possible Used Key From Wrong Vehicle) - SKIM is unable to program – faulty ignition key transponder – ignition key is programmed to another vehicle. 8 Keys Already Learned, Programming Not Done - SKIM transponder ID memory is full. 1. Obtain ignition keys to be programmed from customer (8 keys maximum) 2. Using the DRBIII t, erase all ignition keys by selecting MISCELLANEOUS and ERASE ALL 3. Program all ignition keys. Learned Key In Ignition - Ignition key tran- sponder ID is currently programmed in SKIM mem- 3.3 DIAGNOSTIC TROUBLE CODES Each diagnostic trouble code is diagnosed by following a specific testing procedure. The diagnos- Always begin by reading the diagnostic trouble codes using the DRBIII t. 3.3.1 HARD CODE A diagnostic trouble code that comes back within one cycle of the ignition key is a hard code. This DTC’s that are for OBDII/Euro Stage III OBD monitors will not set with just the ignition key on. t pre-test screens will help with this for MONITOR cycles, and the use of the DRBIII t, refer to the On Board Diagnostic training booklet #81-699-97094. 3.3.2 INTERMITTENT CODE A diagnostic trouble code that is not there every time the PCM checks the circuit is an intermittent • Visually inspect related wire harness connectors. • Visually inspect the related harnesses. Look for • Refer to any technical service bulletins that may • Use the DRBIII t data recorder or co-pilot. 3.3.3 STARTS SINCE SET COUNTER The start since set counter counts the number of times the vehicle has been started since codes were The number of starts helps determine when the trouble code actually happened. This is recorded by t as STARTS since set. When there are no trouble codes stored in mem- ory, the DRBIII t will display NO DTC’s Detected and the reset counter will show STARTS since clear 3.3.4 DISTANCE SINCE MI SET The Euro Stage III OBD directive requires that the distance traveled by the vehicle while the MI is 1. If the MI is illuminated due to a fault, the distance count is updated (i.e. it is counting). 2. If there is a stale MI fault (i.e. the fault is still frozen in memory but the MI has been extin- 3. If the distance count is being held due to (Item 2.) and the fault is cleared, the distance is 4. If the distance count is being held due to (Item 2.) and another MI occurs, the distance count is 5. If a fault occurs while the MI is already illumi- nated due to a previous fault (the distance count 17 GENERAL INFORMATION |