New Vetronix Releases of Ford Event Data Recorders

2007 CDR Users Conference Houston, TX January 29-31, 2007 New Vetronix Releases of Ford Event Data Recorders Richard R. Ruth, P. E. Ruth Consulting LLC

New Vetronix Releases The 2005-2007 Ford Crown Victoria, Mercury Grand Marquis, and Lincoln Town Car Restraint Control Module (RCM) is in Vetronix CDR version 2.9, anticipated to be available very soon. There is a second module with some event data recording capability in these vehicles, the Powertrain Control Module (PCM), which is under development by Vetronix for public release TBD.

Key Takeaways on 05 CV RCM RCM still does not have vehicle speed, brake or throttle like newer GM modules do. The new 05-07 s have a new cumulative Delta V data field, and a new power management strategy that makes it MUCH more likely you will get usable data. There is a SECOND module with data, the PCM; you must use precautions not to spoil PCM data when reading RCM data.

Crown Vic RCM EDR Contents 2001-2004 No vehicle speed, brake or throttle data like GM has Deployment decision time Longitudinal Accel Data in G s every 0.8ms from sensors for approx. 0.1 seconds total duration Longitudinal Delta V in mph of crash calculated from the above - but duration of memory MAY not be long enough to capture complete crash Front seat belts on/off at time of crash No recording or partial recording if power is lost

Crown Vic RCM EDR Contents 2005-2007 same as 01-04 except Cumulative Longitudinal Delta V & algorithm run time added New energy management strategy in RCM makes it much more likely to recover usable data Event recording complete field added VIN as built, RCM Part #, and RCM serial # Key on timer added

2001-2004 Vetronix readout Crash may not be over yet Duration <100ms

2001-2004 Vetronix readout

Typical 05 System Status System Status at Time of Data Retrieval Vehicle Identification Num ber 2FAHP71W 76X127239 Module Serial Number 052890W M Restraints Control Module Part Number 6W 73-14B321-DA Restraints Control Module Software Version Number 0 Restraints Control Module Software Date January 5, 2005 Longitudinal Velocity Change (MPH) -21.1 Longitudinal Velocity Change (msec) 277.6 Deployment Counter 1 Restraints System Faults Present at time of deploym ent. No Current Lifetime Operating Timer (seconds) 3015781 System Status At Frontal Deployment Lifetime Operating Timer at Start of Event (frontal algorithm wake up) (sec) 3014168 Ignition Cycle Key On Timer at Start of Frontal Event 14601 Driver's Belt Switch Circuit Status Buckled Passenger's Belt Switch Circuit Status Unbuckled Driver seat forward of switch point Rearward Passenger occupant classification status Empty Driver First Stage Deployment Time (msec) 21.6 Driver Second Stage Deployment Time (msec) 172 Passenger First Stage Deployment Time (msec) N/A Passenger Second Stage Deployment Time (msec) N/A Driver Pretensioner Time Deployment Time (msec) 20.8 Passenger Pretensioner Deployment Time (msec) N/A Driver Column Device Deployment Time (msec) 20.8 Frontal Event Record Locked Frontal Event Recording Complete Yes Yes

New for 2007 Cumulative Delta V System Status at Time of Data Retrieval Vehicle Identification Number Module Serial Number Restraints Control Module Part Number Restraints Control Module Software Version Number Restraints Control Module Software Date Longitudinal Velocity Change (MPH) Longitudinal Velocity Change (msec) Deployment Counter Restraints System Faults Present at time of deployment. Current Lifetime Operating Timer (seconds) 2FAHP71W76X127239 052890WM 6W73-14B321-DA 0 January 5, 2005-21.1 277.6 1 No 3015781

Δt crash duration Time duration that the algorithm ran and Delta V was collected over System Status at Time of Data Retrieval Vehicle Identification Number Module Serial Number Restraints Control Module Part Number Restraints Control Module Software Version Number Restraints Control Module Software Date Longitudinal Velocity Change (MPH) Longitudinal Velocity Change (msec) Deployment Counter Restraints System Faults Present at time of deployment. Current Lifetime Operating Timer (seconds) Typically much longer duration than graph is 2FAHP71W76X127239 052890WM 6W73-14B321-DA 0 January 5, 2005-21.1 277.6 1 No 3015781

Vehicle details Original vehicle VIN, RCM serial no, and part number recorded for you System Status at Time of Data Retrieval Vehicle Identification Number Module Serial Number Restraints Control Module Part Number Restraints Control Module Software Version Number Restraints Control Module Software Date Longitudinal Velocity Change (MPH) Longitudinal Velocity Change (msec) Deployment Counter Restraints System Faults Present at time of deployment. Current Lifetime Operating Timer (seconds) 2FAHP71W76X127239 052890WM 6W73-14B321-DA 0 January 5, 2005-21.1 277.6 1 No 3015781

Restraints faults System Status at Time of Data Retrieval Vehicle Identification Number Module Serial Number Restraints Control Module Part Number Restraints Control Module Software Version Number Restraints Control Module Software Date Longitudinal Velocity Change (MPH) Longitudinal Velocity Change (msec) Deployment Counter Restraints System Faults Present at time of deployment. Current Lifetime Operating Timer (seconds) *** 2FAHP71W76X127239 052890WM 6W73-14B321-DA 0 January 5, 2005-21.1 277.6 1 No 3015781 If there is no deployment, the system reports faults present at the time of the READOUT modules with only non-deploy events read via direct connection to RCM will report YES *** This line may not display in initial release but will become visible in subsequent releases

Typical 05 - System Status System Status At Frontal Deployment Lifetime Operating Timer at Start of Event (frontal algorithm wake up) (sec) 3014168 Ignition Cycle Key On Timer at Start of Frontal Event 14601 Driver's Belt Switch Circuit Status Buckled Passenger's Belt Switch Circuit Status Unbuckled Driver seat forward of switch point Rearward Passenger occupant classification status Empty Driver First Stage Deployment Time (msec) 21.6 Driver Second Stage Deployment Time (msec) 172 Passenger First Stage Deployment Time (msec) N/A Passenger Second Stage Deployment Time (msec) N/A Driver Pretensioner Time Deployment Time (msec) 20.8 Passenger Pretensioner Deployment Time (msec) N/A Driver Column Device Deployment Time (msec) 20.8 Frontal Event Record Locked Frontal Event Recording Complete Yes Yes Most Important: This tells you the record is 100% complete (hence reliable)

Typical 05 - System Status System Status At Frontal Deployment Lifetime Operating Timer at Start of Event (frontal algorithm wake up) (sec) 3014168 Ignition Cycle Key On Timer at Start of Frontal Event 14601 Driver's Belt Switch Circuit Status Buckled Passenger's Belt Switch Circuit Status Unbuckled Driver seat forward of switch point Rearward Passenger occupant classification status Empty Driver First Stage Deployment Time (msec) 21.6 Driver Second Stage Deployment Time (msec) 172 Passenger First Stage Deployment Time (msec) N/A Passenger Second Stage Deployment Time (msec) N/A Driver Pretensioner Time Deployment Time (msec) 20.8 Passenger Pretensioner Deployment Time (msec) N/A Driver Column Device Deployment Time (msec) 20.8 Frontal Event Record Locked Frontal Event Recording Complete 4Hrs, 3 min, 1 sec How many seconds vehicle was key on before this event occurred Yes Yes

Typical 05 - System Status System Status At Frontal Deployment Lifetime Operating Timer at Start of Event (frontal algorithm wake up) (sec) 3014168 Ignition Cycle Key On Timer at Start of Frontal Event 14601 Driver's Belt Switch Circuit Status Buckled Passenger's Belt Switch Circuit Status Unbuckled Driver seat forward of switch point Rearward Passenger occupant classification status Empty Driver First Stage Deployment Time (msec) 21.6 Driver Second Stage Deployment Time (msec) 172 Passenger First Stage Deployment Time (msec) N/A Passenger Second Stage Deployment Time (msec) N/A Driver Pretensioner Time Deployment Time (msec) 20.8 Passenger Pretensioner Deployment Time (msec) N/A Driver Column Device Deployment Time (msec) 20.8 Frontal Event Record Locked Frontal Event Recording Complete Passenger Presence Empty, Occupied Disable (child or small object), Occupied Enable, or Occupied Large Occupant Yes Yes

Typical 05 - System Status System Status At Frontal Deployment Lifetime Operating Timer at Start of Event (frontal algorithm wake up) (sec) 3014168 Ignition Cycle Key On Timer at Start of Frontal Event 14601 Driver's Belt Switch Circuit Status Buckled Passenger's Belt Switch Circuit Status Unbuckled Driver seat forward of switch point Rearward Passenger occupant classification status Empty Driver First Stage Deployment Time (msec) 21.6 Driver Second Stage Deployment Time (msec) Disposal 150ms after Stage 1 172 Passenger First Stage Deployment Time (msec) N/A Passenger Second Stage Deployment Time (msec) N/A Driver Pretensioner Time Deployment Time (msec) 20.8 Passenger Pretensioner Deployment Time (msec) N/A Driver Column Device Deployment Time (msec) 20.8 Frontal Event Record Locked Frontal Event Recording Complete Restraint Device Deployment Times Yes Yes

05 Crash Graph Delta V for this 70ms of crash is 15.5 (total crash cumulative ΔV is 21.1) Sensor is within +/-40G Range, no saturation

Acceleration exceeds sensor range of +/-40G Delta V could be understated (or overstated)

Incomplete Graph missing

What good is the graph? You are NOT using the graph to get the total Delta V the graph will usually not be long enough to get you a complete crash You get total Delta V from the system status The graph tells if you have exceeded the sensor range and need to estimate error or at least acknowledge the theoretical possibility of error. The more of the total delta V shown on the graph, the greater your ability to place limits upon the degree of any possible error

Still Good Written early in recording process

Incomplete Recordings The Delta V is written early in the recording process followed by deploy times. Accel data is written near the end of the process. In general, if there is value and it is not zero, it was successfully written (exception: OCS status empty) If you need to rely in court on a portion of an incomplete recording, discuss with your attorney if you need an expert to validate it, such as Ford s supplier or a Vetronix trainer. Send examples of incomplete recordings to Vetronix trainers, a series of examples can be used to empirically illustrate the order of the data element recording.

How do you get the RCM data out? Use Vetronix version 2.9 available January 2007 CAUTION: Preserve PCM data by unplugging it or other means before turning key on to avoid spoliating PCM event data Use CDR through the Data Comm Link no direct connection to RCM cable will be supplied initially If the module has not locked the deployment and a direct connection is used, the fault code portion of the memory will be overwritten, spoliating evidence needed in the event of a product liability lawsuit.

How do you get the RCM data out? If the vehicle electrical system is damaged and the DLC does not work, consider removing the RCM and placing the module in another similar vehicle for readout. The 2005-2007 Crown Vic. Grand Marquis, and Town Car are very similar the only known difference is side airbags, 4 th VIN digit is H for side bags, F for no side bags. Town Car has standard side bags. Find one similar to your vehicle.

Have Patience The 2005 Crown Vic RCM data takes 8 minutes to read out 2 minutes and 40 seconds per pass If you don t see the screen change from Pass 1 to Pass 2 don t panic unless over 4 minutes have elapsed.

What if I don t have Version 2.9? Ford Dealers DO NOT have the ability to access to Event Data Recorder data with their service equipment. You can network with other agencies that have 2.9. You can ask Ford to read it. There may be a cost recovery charge for the service. Ford will typically ask you to mail the module in.

Limitations on Delta V If the sensor range was exceeded, acknowledge a tolerance proportionial to amount of time the data was clipped. For multiple events, review duration of algorithm run to see if more than one event may be included Delta V is only in the longitudinal direction if you have an angular hit you must use trig to get the total resultant Delta V.

To formally request Ford help reading an RCM send request to Attention: Third party request attorney Ford Office of the General Counsel 1400 Parklane Towers West 3 Parklane Boulevard Dearborn, MI 48126 Ford requires written owner permission or sufficient legal authority

Key Takeaways on 05 CV RCM RCM still does not have vehicle speed, brake or throttle like GM modules do. The new 05-07 s have a new cumulative Delta V data field, and a new power management strategy that makes it MUCH more likely you will have usable data. There is a SECOND module with data, the PCM, with speed, brake, and throttle data. You must use precautions not to spoil PCM data when reading RCM data.

End RCM Section QUESTIONS??