<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title> &#187; Floor Mat Interference</title>
	<atom:link href="http://www.safetyresearch.net/category/floor-mat-interference/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.safetyresearch.net</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2012 11:33:41 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
		<item>
		<title>Updated Toyota Report: The Recall Ate My Floormat!</title>
		<link>http://www.safetyresearch.net/2011/05/03/updated-toyota-report/</link>
		<comments>http://www.safetyresearch.net/2011/05/03/updated-toyota-report/#comments</comments>
		<pubDate>Tue, 03 May 2011 17:02:51 +0000</pubDate>
		<dc:creator>srsadmin</dc:creator>
				<category><![CDATA[Accelerator pedal]]></category>
		<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Electronics]]></category>
		<category><![CDATA[Floor mat]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=2532</guid>
		<description><![CDATA[Well, here we are, 14 months after Toyota began admitting to the world that it could no longer design a simple pedal, a floor mat or a floor pan, by launching Phase I of many phases of a recall to replace all-weather floor mats that may entrap the accelerator. Initially, the recall 90L, the mother [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;">Well, here we are, 14 months after Toyota began admitting to the world that it could no longer design a simple pedal, a floor mat or a floor pan, by launching Phase I of many phases of a recall to replace all-weather floor mats that may entrap the accelerator. Initially, the recall 90L, the mother of all floor mat recalls, was meant to switch those sneaky little All-Weather Floor Mats out of 3.8 million Toyota and Lexus vehicles.  (See <a href="http://www.safetyresearch.net/Library/Toyota_Floormat.pdf"> Toyota All-Weather Floor Mat Entrapment</a>) <span id="more-2532"></span></span></p>
<p><span style="color: #c0c0c0;">But as time has passed, more models and model years have been added. In total since 2005, when Toyota announced a small campaign to recall some Lexus IS250 vehicles from model year 2006 for “accelerator pedals which could become stuck in the partially depressed position due to inadequate clearance between the accelerator pedal linkage and a plastic pad embedded in the vehicle’s carpet,” Toyota has recalled more than 100 different makes, model and model year vehicles for an unintended acceleration-related safety defect. There have been a total of seven different recalls. Monster recall 90L is in now in Phase 11.</span></p>
<p><span style="color: #c0c0c0;">Behold! Our latest Toyota Recall Matrix:</span></p>
<p><a href="http://www.safetyresearch.net/Library/Recall%20Matrix_20110503.pdf"><img class="alignnone size-full wp-image-2553" title="Recall Matrix_20110503_Preview" src="http://www.safetyresearch.net/wp-content/uploads/Recall-Matrix_20110503_Preview1.jpg" alt="" width="300" height="194" /></a></p>
<p><span style="color: #c0c0c0;">The remedies are a complex welter of fixes:</span></p>
<p><span style="color: #c0c0c0;">• New floor mats</span></p>
<p><span style="color: #c0c0c0;">• Shorter accelerator pedals – or not</span></p>
<p><span style="color: #c0c0c0;">• Yes/electronic brake-override/No electronic brake-override</span></p>
<p><span style="color: #c0c0c0;">• Definitely getting a new accelerator pedal, or getting a new accelerator pedal if you ask the dealer for one.</span></p>
<p><span style="color: #c0c0c0;">• New Retention clips—not once but twice</span></p>
<p><span style="color: #c0c0c0;">• Shaved plastic pads</span></p>
<p><span style="color: #c0c0c0;">Employing everything from software to razor blades hasn’t really stopped the SUAs from occurring. We got some interesting real-life recent incidents we’ll be sharing in coming days. Stay tuned.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2011/05/03/updated-toyota-report/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Another Attack of the Killer Floor Mats: Sarasota Edition</title>
		<link>http://www.safetyresearch.net/2011/02/24/another-attack-of-the-killer-floor-mats-sarasota-edition/</link>
		<comments>http://www.safetyresearch.net/2011/02/24/another-attack-of-the-killer-floor-mats-sarasota-edition/#comments</comments>
		<pubDate>Thu, 24 Feb 2011 18:29:03 +0000</pubDate>
		<dc:creator>Sean</dc:creator>
				<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Electronics]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[Lexus]]></category>
		<category><![CDATA[NASA]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Throttle Contols]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[all-weather floor mat]]></category>
		<category><![CDATA[Floor mat]]></category>
		<category><![CDATA[Safety Research & Strategies]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=2481</guid>
		<description><![CDATA[Dear Toyota: Why did you buy back Tim Scott’s 2007 Lexus RX? We mean, really? You gave him a bunch of different reasons, but he doesn’t believe you. (We’re finding it a little hard to swallow, too.) Awaiting your reply, SRS Here’s Tim Scott’s story. In early December, as NHTSA and NASA were putting the [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;">Dear Toyota:</span></p>
<p><span style="color: #c0c0c0;">Why did you buy back Tim Scott’s 2007 Lexus RX? We mean, really? You gave him a bunch of different reasons, but he doesn’t believe you. (We’re finding it a little hard to swallow, too.)</span></p>
<p><span style="color: #c0c0c0;">Awaiting your reply,</span></p>
<p><span style="color: #c0c0c0;">SRS</span></p>
<p><span style="color: #c0c0c0;">Here’s Tim Scott’s story. In early December, as NHTSA and NASA were putting the finishing touches on their reports saying that there is nothing wrong with Toyota’s electronics or software, Scott experienced an unintended acceleration event in his 2007 Lexus RX350, on his way home from the gym. Here’s the narrative that Scott, 46, the chief financial officer for the International Union of Police Associations, wrote:<span id="more-2481"></span></span></p>
<p><span style="color: #c0c0c0;">“At approx. 8:05 am on Thursday, December 2nd I was stopped behind a school bus that was picking up children at the intersection of Sarasota Square Blvd and Crockers   Lake Blvd in Sarasota,  FL. After the bus cleared the intersection (1-2 min wait) I gave the car enough gas to make the right hand turn onto Crockers Lake Blvd. which is only approx. 150-200 ft in length. I estimate the speed was between 10-15 mph when I began braking to make the left hand turn into the Citation Club Apartments when I noticed the vehicle was not slowing. I pressed the brake pedal harder and the car continued to pull against the brakes. As I approached the end of Crockers Lake Blvd I had both feet on the brakes and the car was slowing, however the engine was &#8220;screaming&#8221; and the tachometer was approaching to &#8220;red-line&#8221;. I managed to make the left hand turn and as the car slowed I shifted it into park to stop it. The engine was screaming so I turned the ignition to the off position. I attempted to restart the vehicle and it immediately red-lined again; I immediately turned the car off. At this time two employees of Citation Club approached me on the passenger side in a service golf cart and asked what was wrong. I indicated I didn&#8217;t know but they should &#8220;hear this&#8221; at which time I started the car again and it again red-lined. I immediately turned the ignition off. One of the Citation Club employees told me they would push me out of the entrance area to prevent my vehicle from being struck should someone attempt to enter the complex. Once safely parked, I exited the vehicle and immediately checked to be sure the floor mats were still secured by the anchors; they were. <em>I looked for any type of obstruction near the accelerator and found none.</em>”</span></p>
<p><span style="color: #c0c0c0;">The dealership, Wilde Lexus, however did find a problem – they found three different problems. Or, rather, one problem that changed three times. First, they told him that his vehicle was equipped with the wrong carpet mats. Then they told him that the floor mats were the right size, but that they were “bunched up” around the accelerator. Then they told him that the driver’s side floor mat appeared to dislodge a section of molding that obstructed the accelerator. So – wrong-size floor mats, bunched up floor mats, then dislodged molding. Are you with us?</span></p>
<p><span style="color: #c0c0c0;">About a week later, the dealership informed him that even though they had isolated the problem to a carpeted floor mat, Lexus was sending a team of engineers to examine the vehicle. When the engineers arrived, they called Scott to ask if the accelerator was 25-percent or 50-percent depressed. The accelerator was zero-percent depressed – Scott was braking at the time the UA occurred.</span></p>
<p><span style="color: #c0c0c0;">Back to the narrative: “Late in the afternoon of December 20th I received a call from Lexus (Corporate) stating that the engineers had determined they ‘didn&#8217;t want to take any more chances with the vehicle on the road and that they wanted to purchase my vehicle back if I was interested.’ ”</span></p>
<p><span style="color: #c0c0c0;">Scott was interested – and stunned.</span></p>
<p><span style="color: #c0c0c0;">“I never anticipated hearing that out of the blue,” Scott told SRS. “It was supposedly a floor mat issue. I remember telling the service manager, ‘I find it hard to believe Toyota buys back cars because of a floor mat problem.’ ”</span></p>
<p><span style="color: #c0c0c0;">And today, the mystery deepened. <span style="color: #000000;"><a href="http://www.safetyresearch.net/Library/toy_022411.pdf">Toyota announced more floor mat recalls and under-the-floor-mat and trim interference recalls</a></span>!</span></p>
<p><span style="color: #c0c0c0;">First, Toyota added three more models to its earlier all-weather floor mat recalls (also see</span><strong><strong> </strong></strong><a title="http://www.safetyresearch.net/Library/Toyota_Floormat.pdf" href="../Library/Toyota_Floormat.pdf">Toyota  All-Weather Floor Mat Entrapment</a><span style="color: #c0c0c0;">) to address the potential for unsecured or incompatible floor mat entrapment of the accelerator pedal: the 2003 through 2009 4Runner; 2008 through 2011 Lexus LX 570; and the 2010 RAV4. <br />
 </span></p>
<p><span style="color: #c0c0c0;">Second, it announced a new safety recall of approximately 20,000 2006 and early 2007 Model Year GS 300 and GS 350 All-Wheel Drive vehicles to modify the shape of the plastic pad embedded in the driver’s side floor carpet, which apparently can be moved during a service operation, and interfere with the gas pedal.</span></p>
<p><span style="color: #c0c0c0;">Third, it announced a recall of 372,000 2004 through 2006 and early 2007 RX 330, RX 350, and RX 400h vehicles, and 397,000 2004 through 2006 Highlander and Highlander HV vehicles, to replace the driver’s side floor carpet cover and its two retention clips, because “if the forward retention Ilip used to secure the floor carpet cover, which is located in front of the center console, is not installed properly, the cover may lean toward the accelerator pedal and interfere with the accelerator pedal arm.”</span></p>
<p><span style="color: #c0c0c0;">And the freaky thing is – Toyota had already recalled the 2004-2005 and early 2006 Highlanders and 2004 – 2005 Lexus RX 330 and 2006 RX400h center console to replace the forward retention clip used to secure the floor carpet cover in front of the center console. In 2006 (<span style="color: #000000;"><a href="http://www.safetyresearch.net/Library/R06V253.pdf">06V253</a></span>)!  The campaign warned: “The two Retaining Clips for the driver’s side forward Center Console (Floor Carpet Cover) can become loose. If both clips separate from the Floor Carpet Cover, the cover may lean toward the accelerator pedal, causing interference with the accelerator pedal rod. In the worst case, this condition may interfere with the accelerator pedal returning to the idle position and thus may increase the possibility of a crash.”</span></p>
<p><span style="color: #c0c0c0;">So is this a re-notification? The forward retention clip Toyota replaced five years ago is already breaking and they are worried about the rear clip, too? So many questions.</span></p>
<p><span style="color: #c0c0c0;">Now, Scott is no little old lady. He’s a strapping guy of 250 pounds who, as an RX owner, had been following all the Toyota news. The first thing he checked when he stopped his vehicle was the state of his carpet mats. They were secured, in place and nowhere near his accelerator.</span></p>
<p><span style="color: #c0c0c0;">“I don’t scare easy, but that scared the s—t out of me. If it had happened three minutes earlier, I would have plowed into the back of a school bus. I had all my weight on those brakes. The engine was screaming. And when I got the car to stop, I almost jumped out, because I thought it was going to explode,” he says “It’s a travesty what they are trying to do. The fact that there’s another massive round of recalls just underlines that there’s a problem. I don’t like that large corporations can get way with putting people’s lives in jeopardy.”</span></p>
<p><span style="color: #c0c0c0;">Obviously, Mr. Scott did not get the memo from Ray and his band of rocket scientists: all mechanical causes of unintended acceleration have already been identified and remedied. There are no electronic or software problems with Toyotas. <br />
 </span></p>
<p><span style="color: #c0c0c0;">P.S. Toyota, we don’t know if truth is stranger than fiction, but fiction sure is more work to maintain.</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2011/02/24/another-attack-of-the-killer-floor-mats-sarasota-edition/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>So What About the Defects?</title>
		<link>http://www.safetyresearch.net/2011/01/04/so-what-about-the-defects/</link>
		<comments>http://www.safetyresearch.net/2011/01/04/so-what-about-the-defects/#comments</comments>
		<pubDate>Tue, 04 Jan 2011 13:48:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Accelerator pedal]]></category>
		<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Rulemaking]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Throttle Contols]]></category>
		<category><![CDATA[Timeliness Query]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[FMVSS 124]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=2326</guid>
		<description><![CDATA[In 2010, NHTSA levied nearly $50 million in fines against Toyota for flouting the recall regulations in three separate instances. The total represents the largest single fines in the agency’s history – and, (although we haven’t checked) quite possibly more than the agency has ever collected from any and all automakers in 40 years of [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;">In 2010, NHTSA levied nearly $50 million in fines against Toyota for flouting the recall regulations in three separate instances. The total represents the largest single fines in the agency’s history – and, (although we haven’t checked) quite possibly more than the agency has ever collected from any and all automakers in 40 years of existence. <br />
</span></p>
<p><span style="color: #c0c0c0;">This tough stance on recall timeliness is welcome – but does not resolve the larger issues raised by Toyota unintended acceleration – namely how defects are defined in the era of automotive electronics and how such defects are investigated when they are rare, multi-root-cause, and potentially deadly? <br />
</span></p>
<p><span style="color: #c0c0c0;">The dribble of documents released by the Multi-District Litigation and Congress so far show that UA has been duplicated by Toyota technicians and, contrary to attempts by Toyota advocates and agency investigators to pass off all incidents as driver error, sticky pedals, big shoes and floor mats, there are instances when reliable technical personnel take the vehicle for a test spin and experience UA with no pedal involvement. In fact, we have discovered that Toyota techs were able to duplicate UA in one of very public and widely debated case – but lied to the consumer about it. (We’ll feature that story in a future post.)<span id="more-2326"></span></span></p>
<p><span style="color: #c0c0c0;">The root cause – or causes – of such instances remain obscured, for the moment. There are multiple possibilities. (We suspect that Toyota execs and technical staff in Japan have a much better idea of why these instances occur.) We know that Toyota has bought back vehicles that have experienced a UA event in front of dealership personnel for further testing. Independent testing and vehicle inspections continue to show Toyota’s fault detection software has some serious flaws – flaws that allow unwanted events to occur undetected and without activation of the failsafe features.  There are no regulations that govern the layers of safety need in today’s sophisticated vehicle electronics.  While some manufacturers follow strict multi-tiered safety strategies that catch inevitable (and sometimes rare) occurrences, Toyota appears to be missing some core layers.  How and whether this gets addressed will set the foundation for the future of motor vehicle defect investigations and recalls.</span></p>
<p><span style="color: #c0c0c0;">Eventually, this knot will be untangled – but by whom? The National Academy of Sciences is still working on its report. But the panelists aren’t experts in vehicle electronics and have an incredibly broad mandate to review everything from electronic controls design and reliability to environmental factors to cyber-security of automotive electronic control systems.  We don’t expect any revelations there. The Inspector General is looking at NHTSA’s investigatory process, and this work may yield some insight and suggested improvements. The joint NASA-NHTSA effort is scheduled to conclude in 2011.  NHTSA still has an open Recall Query, RQ10-003, to determine if Toyota too narrowly defined the defect in its two UA-related recalls.</span></p>
<p><span style="color: #c0c0c0;">And that takes us back to our first question. ODI investigators have traditionally been broken parts guys and gals. What happens if the defect is a line of code or a faulty detection strategy made of digital Swiss cheese? The agency itself may have to broaden the concept of defect to address the evolution of vehicle computer systems and electronics and whether rare events with serious consequences are safety-related defects under their mandate.</span></p>
<p><span style="color: #c0c0c0;">To our second question about investigations into a rare, random, and yet potentially deadly defects – the agency isn’t going to get anywhere until it catches up to today’s engine systems. Some of the agency’s public efforts to date, such as the “study” of SUA events using Event Data Recorders, showed how far NHTSA has to go. The agency mischaracterized the data and failed to address the many discrepancies in the readouts. Further, it omitted any context about the questionable reliability of Toyota’s EDRs and about the incidents it included.  The “results” didn’t add much of anything to the discussion other than blaring headlines that alleged NHTSA exonerated Toyota of electronic defects.</span></p>
<p><span style="color: #c0c0c0;">Toyota SUA has also exposed more regulatory fissures. Federal Motor Vehicle Safety Standard 124 Accelerator Controls has pretty much lost its relevance. Its purpose is: “to reduce deaths and injuries resulting from engine overspeed caused by malfunctions in the accelerator control system.” In 2005, NHTSA proposed amending it. But, the industry sought to rescind the standard, arguing that market forces and litigation pressure were sufficient to assure fail-safe performance without a safety standard. The agency terminated the rulemaking.</span></p>
<p><span style="color: #c0c0c0;">And, while these broad questions beg for answers, automakers are experimenting with even more sophisticated and integrated electronics.</span></p>
<p><br class="spacer_" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2011/01/04/so-what-about-the-defects/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Double Ding for Toyota</title>
		<link>http://www.safetyresearch.net/2010/12/21/double-ding-for-toyota/</link>
		<comments>http://www.safetyresearch.net/2010/12/21/double-ding-for-toyota/#comments</comments>
		<pubDate>Tue, 21 Dec 2010 15:45:57 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Relay Rod]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Timeliness Query]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[Civil Penalty]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=2321</guid>
		<description><![CDATA[Toyota closes out 2010 by shelling out another $32.4 million to the government for tardiness. The two fines – for failing to recall its floor mats and defective relay rods within five days of determining a defect – were disclosed yesterday. Three record fines in one year ain’t beanbag. In all three cases – the [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;">Toyota closes out 2010 by shelling out another $32.4 million to the government for tardiness. The two fines – for failing to recall its floor mats and defective relay rods within five days of determining a defect – were disclosed yesterday.</span></p>
<p><span style="color: #c0c0c0;">Three record fines in one year ain’t beanbag. In all three cases – the relay rods, the accelerator pedal and the floor mats – Toyota had recalled the affected vehicles overseas months before it got around to recalling those components here. It’s refreshing to see the agency enforce the law. But penalizing a manufacturer for failing to file a timely defect report only requires counting to five. The agency will greet 2011 with the much more complicated issue of unintended acceleration hanging in the balance. We’ll address that in a future post.</span></p>
<p><span style="color: #c0c0c0;">In the meantime, back to the fines. The details were MIA. NHTSA did not say when it thought Toyota had a duty to recall those components. Toyota didn’t admit it did anything wrong. Since the agency hasn’t made its case for the penalty to the public, the <em>Safety Record Blog</em> will do it for them.<span id="more-2321"></span></span></p>
<p><span style="color: #c0c0c0;"><strong>Why Toyota Was Late in Recalling the Floor Mats</strong></span></p>
<p><span style="color: #c0c0c0;">In March, Toyota submitted a detailed chronology of the events leading up to its first floor mat recall in September 2007, when Toyota shut down Engineering Analysis 07010, by launching a floor mat recall. The chronology contained scant detail, but it did yield several interesting points: Toyota claimed to have had practically no complaints about floor mat interference; it scrambled to take action beginning in March 2007 to avert a NHTSA investigation; and it initiated a floor mat “field action” in the European market sometime in July 2007, two months before the automaker announced a recall in the U.S.</span></p>
<p><span style="color: #c0c0c0;">Further, the chronology was at odds with information presented to the agency in PE-07016. The chronology did not explain these discrepancies.</span></p>
<p><span style="color: #c0c0c0;">For example, the chronology showed that prior to taking any action, Toyota had only two reports of floor-mat interference – a field technical report in February 2006 involving a 2005 Prius and September dealership report involving a 2007 Lexus 350ES, using multiple floor mats – before it decided to stop the sale of all of All Weather Floor Mats to implement changes. In its June 11, 2007 response to PE07-016, Toyota says it had no field reports related to pedal entrapment in MY2007 Lexus ES350s.  Further, according to the response Toyota filed in June 2007 to PE07-016, it had received 38 consumer complaints related to pedal entrapment in Lexus 350ES vehicles – eight involved crashes; five with injuries. The chronology does not mention any of these incidents as influencing their ensuing actions.</span></p>
<p><span style="color: #c0c0c0;">On March 27, 2007, the automaker says that added a hangtag to be removed by customers and put a product usage label on the packaging. A stop-sale would appear to be an extraordinary reaction, if there were only two incidents in seven months involving different makes, models and model years. However, it is more likely that Toyota’s decision to add these warnings was an effort to get out in front of a pending NHTSA investigation.</span></p>
<p><span style="color: #c0c0c0;">According to the Toyota chronology, the automaker learned on March 29, 2007 that NHTSA opened a Preliminary Evaluation on the floor mat issue. However, e-mails offered as exhibits in the multi-district litigation show that Toyota already knew that an Opening Resume on floor mat interference in the ES350 was soon in the offing. In the days leading up the official opening on an investigation, Toyota’s manager of government affairs, Christopher Tinto, informed his colleague Mitch Kato, about the state of negotiations with NHTSA, which clearly began before Toyota’s March 27 decision:</span></p>
<p><span style="color: #c0c0c0;">“I spoke to NHTSA management today (K. Demeter) about a potential compromise on the ES350 floor mat Issue. In lieu of a Part 573 safely recall, I offered the following:</span></p>
<p><span style="color: #c0c0c0;">Toyota will send a letter to all 2007MY ES350 owners reminding them not to install all weather mats on top of existing mats; In addition, we will enclose a caution label advising owners of the same, and ask owners to affix the label on the flat surface on the backside of the mat; We will also alert dealers of the issue, and remind them not to install mats on top of existing mats; If the owners want to have the dealer affix the label to the mat, Toyota will offer that they bring their vehicles to the dealer to ask them to do it, free of charge. However, we will NOT file a 573 (i.e. this is not a safety recall), because a) this is an &#8216;aftermarket&#8217; install b) there is no design or manufacturing defect in the mat or vehicle, and c) the issue really boils down to improper installation of the mats by the owner or the dealer (but I noted that Toyota has no evidence that dealers are actually doing this.) Ms. Demeter said that there is precedent in NHTSA&#8217;s history for safety recalls in this area, but understood our idea she pledged that they would discuss it internally and get back to me with a response to our proposal in a few days. She also insured me that NHTSA would not open a formal PE until she gets back to me.”</span></p>
<p><span style="color: #c0c0c0;">Toyota also acknowledged that before it launched the first, limited floor mat recall in September 2007, it had initiated some sort of a floor mat campaign for its European customers in July. Little is publicly known about what Toyota calls a “field action.” Under the TREAD ACT, manufacturers must report an overseas safety recall or “other safety campaign in a foreign country on a motor vehicle or motor vehicle equipment that is identical or substantially similar to a motor vehicle or motor vehicle equipment offered for sale in the United States.”  There is no evidence in the public record that Toyota did reported this floor mat “field action” to NHTSA prior to disclosing it in TQ10-001.</span></p>
<p><span style="color: #c0c0c0;">In the ensuing two years, the cycle repeated itself. According to the chronology, Toyota reported having received only two more complaints. (SRS is aware of a January 2008 crash involving floor-mat entrapment in a Lexus ES350, which occurred on a Connecticut highway. This crash was reported to Toyota. It was noted on one of Toyota’s quarterly EWRs, but it is not one of the complaints mentioned in the chronology.)</span></p>
<p><span style="color: #c0c0c0;">After the Saylor crash spotlighted Toyota’s SUA problems, the automaker again ramped up a response. The very public loss of life, involving a California Highway Patrol officer caught Toyota’s attention in a way eight previous NHTSA investigations did not.</span></p>
<p><span style="color: #c0c0c0;">In a September 2009 e-mail from Toyota’s Koji Sakekibara to his colleagues underscored the delicate position in which the automaker found itself:</span></p>
<p><span style="color: #c0c0c0;">“In light of the information that two minutes before the crash, an occupant made a call to 911 telling that the accelerator pedal was stuck and the vehicle would not stop, I think that the Body Engineering Division should act proactively first, (investigate issues such as whether the accelerator assay is the cause, how to secure floor mats, the timing of introducing shape improvements.) Furthermore, taking into account the circumstances that in this event a police officer and his entire family TMS-PQSS Public Affairs Group thinks that the NHTSA and the USA public already hold very harsh opinions in regards to Toyota (As I think you know, in some cases in the USA killing a police officer means the death penalty.”)</span></p>
<p><span style="color: #c0c0c0;">This time, the internal assessment took other solutions into account: “Toyota conducted various analyses to evaluate the emergency shutdown method of Toyota vehicles and competitor vehicles, to evaluate the brake override system of competitor vehicles, to evaluate the accelerator pedal shape change to reduce the risk of pedal entrapment by floor mats, and to compare the shift levers of Toyota vehicles with competitor vehicle,” Toyota wrote in its chronology.  After initially advising owners to remove the All-Weather Floor Mats from their vehicles, Toyota issued a second-phase response, which included a brake-to-idle override for some models, and newly designed floor mats for all vehicles under the recall.</span></p>
<p><span style="color: #c0c0c0;">The chronology admitted to no virtually internal evidence of a problem over a four-year period. Was Toyota suggesting that consumer complaints, early warning reports and legal and warranty claims had no role in driving their recall decisions? Did Toyota expect the experienced ODI staff to accept the explanation that on the basis of two field reports, Toyota initiated a stop sale? Based on Toyota’s EWRs, NHTSA opened at least five Death and Injury inquiries on incidents in which floor mat entrapment was alleged. Toyota did not mention any on these incidents in its chronology.</span></p>
<p><span style="color: #c0c0c0;">The outline of events cast Toyota’s floor mat recall campaigns in September 2007 and October 2009 as rear-guard actions, driven by NHTSA or other externalities. While the agency investigation is in the preliminary evaluation stage, the automaker conducts pedal entrapment analyses in an Avalon and Prius in relation to pedal geometry and the All-Weather floor mat, and finds nothing wrong. Once NHTSA elevates the investigation to the engineering analysis stage, Toyota decides to conduct a floor mat recall in September 2007.</span></p>
<p><span style="color: #c0c0c0;">In conclusion: Toyota claimed to have practically no complaints about floor mat interference; it only acted in March 2007 to shut down ODI; it initiated a floor mat “field action” in the European market sometime in July 2007, two months before the automaker announced a recall in the U.S.</span></p>
<p><span style="color: #c0c0c0;">Ding!</span></p>
<p><span style="color: #c0c0c0;"><strong>Why Toyota Was Late in Recalling Defective Relay Rods</strong></span></p>
<p><span style="color: #c0c0c0;">The relay rod recall chronology was much less tortured. In October 2004, the automaker disclosed to NHTSA that it had recalled Hilux and Hilux Surf vehicles sold in Japan for defective relay rods – but not its U.S. counterparts, Toyota 4Runner, the Toyota Truck and Toyota T100. The rods had a tendency to snap, leaving the driver with no steering controls. But Toyota blamed it on driving conditions unique to the Japanese market:</span></p>
<p><span style="color: #c0c0c0;">“TMC has received field information from the Japanese market, but no similar information from the U.S. market has been received. In addition to the different steering linkage design between the right hand drive and the left hand drive vehicles, TMC believes that the unique operation conditions in Japan, such as frequent standing full lock turns, such as for narrow parking spaces and close quarters maneuvering, greatly affects the occurrence of this problem.”</span></p>
<p><span style="color: #c0c0c0;">The Hilux recall was a scandal in Japan; with police referring three Toyota executives for criminal prosecution. Top managers avoided jail time. Instead, the Japanese government publicly criticized Toyota and ordered the company to reform its recall practices.</span></p>
<p><span style="color: #c0c0c0;">Back in the U.S., Toyota told NHTSA that it had not received any reports of relay rod failures.</span></p>
<p><span style="color: #c0c0c0;">Here’s one of those complaints the automaker didn’t receive in 2004, as reported among its 2004 EWR data:</span></p>
<p><span style="color: #c0c0c0;">The driver, Zoe Chapman of Whitethorn, CA, was driving her T-100 truck at about 20 mph near Humboldt  Redwoods State   Park, when she lost steering. The truck climbed an embankment and rolled over. Chapman and her passengers were belted and escaped with minor injuries, but the truck was totaled. Immediately after the crash, Chapman and her passengers saw that the relay rod was severed at a line of rust. They happened to be professional and accomplished photographers who made an on-the-spot visual record of the evidence. Toyota looked at the same facts and decided that the relay rod broke as a <em>result </em>of the rollover and told Chapman to pound sand.</span></p>
<p><span style="color: #c0c0c0;">On September 6, 2005, Toyota finally recalled the defective steering relay rods on 977, 839 1989-1995 Toyota pick ups and 4Runners in the U.S. The repair rate was so low, Toyota took the unusual step of issuing an owner re-notification, but it came too late for 18-year-old Michael “Levi” Stewart of Idaho, who died in a September 2007, after the relay rod on his 1991 Toyota pickup fractured. The Stewart family received a recall notice two months later.</span></p>
<p><span style="color: #c0c0c0;">Attorney John Kristensen, who represents the Stewart family, did some digging and discovered that Toyota had actually received at least 44 reports in the U.S. since as early as 2000, including crashes involving rollovers and injuries, plus a bunch of warranty claims. In May, Kristensen called on NHTSA to open a Timeliness Query for the relay rod recall, which it did.</span></p>
<p><span style="color: #c0c0c0;">In conclusion: In 2004, Toyota recalls vehicles in Japan for broken relay rods, but not in the U.S.; Toyota lies to the agency and claims it has no reports of relay rod failures in the U.S.; Toyota recalls U.S. vehicles with broken relay rods one year later.</span></p>
<p><span style="color: #c0c0c0;">Ding! Ding!</span></p>
<p><span style="color: #c0c0c0;">In total, Toyota paid $48.8 million in timeliness fines – a slight wobble on their $2.2 billion bottom line. Individual drivers and passengers paid for that delay – in economic losses, and in some cases, with their lives.</span></p>
<p><span style="color: #c0c0c0;"> </span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2010/12/21/double-ding-for-toyota/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No Black Box Exoneration for Toyota, Part II</title>
		<link>http://www.safetyresearch.net/2010/08/11/no-black-box-exoneration-for-toyota-part-ii/</link>
		<comments>http://www.safetyresearch.net/2010/08/11/no-black-box-exoneration-for-toyota-part-ii/#comments</comments>
		<pubDate>Wed, 11 Aug 2010 19:58:54 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Black Box]]></category>
		<category><![CDATA[EDR]]></category>
		<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Event Data Recorder]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[George Person]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Throttle Body]]></category>
		<category><![CDATA[Throttle Contols]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=2147</guid>
		<description><![CDATA[After the Wall Street Journal plastered the front page a few weeks ago claiming NHTSA had “black box” (aka Event Data Recorder or EDR) data to support that driver error, not electronics, was the cause of the unintended acceleration issues in Toyotas, the headline is back yet again following a NHTSA Congressional briefing yesterday. The [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;">After the <em>Wall Street Journal</em> plastered the front page a few weeks ago claiming NHTSA had “black box” (aka Event Data Recorder or EDR) data to support that driver error, not electronics, was the cause of the unintended acceleration issues in Toyotas, the headline is back yet again following a NHTSA Congressional briefing yesterday.</span></p>
<p><span style="color: #c0c0c0;">The WSJ in a subsequent story identified George Person, recently retired head of the recall division at NHTSA, as the source.  (see</span> <a title="Permanent Link: No Black Box Exoneration for Toyota" href="../2010/07/14/no-black-box-exoneration-for-toyota/">No Black Box Exoneration for Toyota</a> <span style="color: #c0c0c0;">and</span> <a title="Permanent Link: Lawsuits Fill in Outline of Toyota Sudden Accleration Cover-Up" href="../2010/08/04/lawsuits-fill-in-outline-of-toyota-sudden-accleration-cover-up/">Lawsuits Fill in Outline of Toyota Sudden Acceleration Cover-Up</a><span style="color: #c0c0c0;">)<span id="more-2147"></span></span></p>
<p><span style="color: #c0c0c0;">Person’s leak appears to have prompted the briefing and, based on the briefing memo, Person accurately described the findings.  But what is missing from the <em>WSJ</em> – and most other reports about the data – is context.</span></p>
<p><span style="color: #c0c0c0;">(And while we’re on the topic of Person, we failed to mention that we do appreciate Mr. Person’s concern about government transparency – Person told the <em>WSJ</em> “When I asked why it hadn’t been published, I was told that the secretary’s office didn’t want to release it.”  But he lost us when he claimed “The agency has for too long ignored what I believe is the root cause of the unintended acceleration cases … It’s driver error.  It’s pedal misapplication and that what this data shows.”  Sorry George, but, we still hold fast that your statement tells more about your bias than it does the facts.)</span></p>
<p><span style="color: #c0c0c0;">Let’s start with the data, what is it and what has NHTSA disclosed about it:</span></p>
<p><span style="color: #c0c0c0;">NHTSA claims it conducted 58 field inspections and the vehicles it selected for inspection were crashes in which:</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">“There was an allegation of unintended acceleration or the possibility of unintended acceleration based on preliminary incident information; the vehicle was still available with the EDR intact; the vehicle contained an EDR with pre-crash data; and the owner of the vehicle was willing to allow NHTSA to read the EDR.  It is also important to note that most Toyota models manufactured before 2007 were not equipped with EDRs capable of pre-crash data.”</span></p>
<p><span style="color: #c0c0c0;"><br />
</span></p>
<p><span style="color: #c0c0c0;">NHTSA noted that it gleaned the following breakdown from the data in the 58 cases:</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">35 showed no brake application</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">14 involved partial braking</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">9 involved braking late in the crash</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">3 involved early braking</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">2 involved mid-event braking</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">1 event was said to have involved pedal entrapment</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">1 event showed both brake and accelerator application</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">1 case the EDR contained information related to a separate incident</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">1 case NHTSA is still working to resolve inconclusive data from the EDR</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">5 cases resulted in no EDR activation at all</span></p>
<p><span style="color: #c0c0c0;"><br />
</span></p>
<p><span style="color: #c0c0c0;">How has NHTSA characterized these findings:</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">“At this early point in its investigation, NHTSA officials have drawn no conclusions about the additional causes of unintended acceleration in Toyotas beyond the two defects already known – pedal entrapment and sticking gas pedals.”</span></p>
<p><span style="color: #c0c0c0;">NHTSA made it clear that these data are only a small piece of the puzzle, and while driver error is a likely cause of <em>some</em> SUA events, the EDR data don’t make for a compelling case that this is all that’s happening – particularly as independent experts <em>and</em> Toyota continue to document events in which the vehicle diagnostic systems fail to detect unwanted acceleration events.</span></p>
<p><span style="color: #c0c0c0;">NHTSA has included in the 58 cases events that have “the possibility of unintended acceleration based on preliminary incident information.”  How many is not known.</span></p>
<p><span style="color: #c0c0c0;">We have examined many possible SUA crash events too, and those “possible” SUA events tend to involve single vehicle run-off-the-road crashes with no explanation and no witnesses.  While these events need to be investigated, they are far from the more typical events in which no EDR is activated, the driver, passengers, other witnesses, or in some cases Toyota dealers report first hand engines racing that can’t be explained by mechanical interference or driver error.  Some of these cases were detailed in the Multi-District Litigation complaint against Toyota which cited dealer reports produced by Toyota.  (see <a title="Permanent Link: Lawsuits Fill in Outline of Toyota Sudden Accleration Cover-Up" href="../2010/08/04/lawsuits-fill-in-outline-of-toyota-sudden-accleration-cover-up/">Lawsuits Fill in Outline of Toyota Sudden Acceleration Cover-Up</a>)</span></p>
<p><span style="color: #c0c0c0;">The NHTSA EDR data don’t address pre-2007 Toyota / Lexus model vehicles as those vehicles are not equipped with EDRs that capture pre-crash data – yet many of the pre-2007 vehicles (including the Camry and Tacoma) have the highest SUA complaint rates and are not part of any recall.</span></p>
<p><span style="color: #c0c0c0;">Safety Research &amp; Strategies has already addressed the murkiness and accuracy of Toyota’s EDR’s (see EDR: </span><a href="../2010/06/11/edr-toyota%E2%80%99s-electronic-doubt-receptacle/">Toyota’s Electronic Doubt Receptacle</a>)<span style="color: #c0c0c0;">.  And since most of the news reports failed to mention it, we would like to remind you again of an important bit of context: Toyota has always stated that the accuracy of the black boxes has never been scientifically validated. In fact, the company fights to keep the data from being used in litigation because it says the EDR data aren’t reliable.</span></p>
<p><span style="color: #c0c0c0;">Now, NHTSA’s briefing yesterday noted the agency has done its own EDR validation testing on two 2007 Camry’s and one 2008 Highlander and they have found “Toyota EDR data the same as the data produced by the NHTSA test equipment.” So, what’s the take-away from this set of data:  The Toyota EDRs report accurate information when the vehicle is functioning properly.  What happens when a vehicle experiences an unintended event, sets no error code, and a crash ensues?</span></p>
<p><span style="color: #c0c0c0;">In summary, upwards of 95 percent of the SUA reported incidents don’t involve EDR activation.  The recent NHTSA EDR data summary is interesting and worth further examination, but it clearly cannot be extrapolated to the thousands of incidents of SUA in which an EDR didn’t activate and witnesses report racing engines without driver input or mechanical interference.</span></p>
<p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="if(typeof(jsCall)=='function'){jsCall();}else{setTimeout('jsCall()',500);}" type="hidden" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2010/08/11/no-black-box-exoneration-for-toyota-part-ii/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Money for Nothing and Complaints for Free</title>
		<link>http://www.safetyresearch.net/2010/08/05/money-for-nothing-and-complaints-for-free/</link>
		<comments>http://www.safetyresearch.net/2010/08/05/money-for-nothing-and-complaints-for-free/#comments</comments>
		<pubDate>Thu, 05 Aug 2010 15:28:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Electronics]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[Real Stories]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Throttle Body]]></category>
		<category><![CDATA[Throttle Contols]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[Safety Research & Strategies]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=2141</guid>
		<description><![CDATA[Interesting fact: A raft of academic and industry studies show that customers who complain and have their complaint successfully resolved bring in more money to the company than it costs to fix the problem. In the topsy-turvy Toyota World, however, it’s the customers who are already happy that get the red carpet treatment and big [...]]]></description>
			<content:encoded><![CDATA[<p><strong> </strong></p>
<p><span style="color: #c0c0c0;">Interesting fact: A raft of academic and industry studies show that customers who complain and have their complaint successfully resolved bring in more money to the company than it costs to fix the problem.</span></p>
<p><span style="color: #c0c0c0;">In the topsy-turvy Toyota World, however, it’s the customers who are already happy that get the red carpet treatment and big bucks. Have you heard about Nick and Sharyn Davis, from Parker   County, Texas? You will soon. According to <em>The Weatherford Democrat</em>, the Davises are among the lucky winners in a Toyota advertising campaign, touting “real people with real stories about their Toyotas. And, the Davises are part of those real people.”<span id="more-2141"></span></span></p>
<p><span style="color: #c0c0c0;">A crew of nearly 100 from an LA ad agency and a catering truck descended on the Davises’ remote ranch. And, after signing the couple up to the Screen Actors Guild, and a 12-hour shoot, the checks started rolling in.  By keeping it real for Toyota, the Davises have made $23,000 and counting.</span></p>
<p><span style="color: #c0c0c0;">Gee, we’ve got real people with real stories about Toyotas and we didn’t have to pay them a dime. They keep calling us, frustrated because after they’ve suffered a crash after their Toyota took off on them, or merely a very frightening experience or multiple events with different drivers, same car, Toyota writes them a nice letter explaining that nothing is wrong with their vehicle and to please pound sand.</span></p>
<p><span style="color: #c0c0c0;">These are the inconvenient real stories – the ones that can’t be explained by floor mats, driver error, or sticky pedals.</span> <a href="http://www.safetyresearch.net/toyota-sudden-unintended-acceleration/toyota-sua-real-stories/">Check them out</a> <span style="color: #c0c0c0;">(more to come&#8230;)  These Toyota and Lexus owners are out of considerable cash, afraid to drive a vehicle with a dangerously unpredictable streak and conscience-stricken about selling the vehicle to another victim of Toyota’s decision to roll the dice on SUA.</span></p>
<p><span style="color: #c0c0c0;">Unlike the Davises, there’s no check in the mail.</span></p>
<p><br class="spacer_" /></p>
<p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="if(typeof(jsCall)=='function'){jsCall();}else{setTimeout('jsCall()',500);}" type="hidden" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2010/08/05/money-for-nothing-and-complaints-for-free/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What Are You Lookin’ At?</title>
		<link>http://www.safetyresearch.net/2010/05/27/2031/</link>
		<comments>http://www.safetyresearch.net/2010/05/27/2031/#comments</comments>
		<pubDate>Thu, 27 May 2010 15:45:50 +0000</pubDate>
		<dc:creator>Sean</dc:creator>
				<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[advocacy]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=2031</guid>
		<description><![CDATA[Last week, TMS President Jim Lentz was full of fun facts to know and tell the committee on Energy and Commerce. For example: “The company has completed more than 600 on-site vehicle inspections and our dealership technicians have completed an additional 1,400 inspections. We have submitted 701 field technical reports to this Committee, including on-site [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;">Last week, TMS President Jim Lentz was full of fun facts to know and tell the committee on Energy and Commerce. For example:</span></p>
<p><span style="color: #c0c0c0;">“The company has completed more than 600 on-site vehicle inspections and our dealership technicians have completed an additional 1,400 inspections. We have submitted 701 field technical reports to this Committee, including on-site SMART team evaluations. These examinations are giving us a better understanding about the reasons for unintended acceleration complaints. Significantly, none of these investigations have found that our Electronic Throttle Control System with intelligence, or ETCS-i, was the cause.”<span id="more-2031"></span></span></p>
<p><span style="color: #c0c0c0;">That’s so nice, that Toyota let Congress see those reports. Customers are not so fortunate. The typical Toyota experience for owners who report an unintended acceleration incident is a visit to the dealership, where the vehicle is presumably checked out and given a clean bill of health. The consumer is not privy to what precise tests were conducted or what they showed. Customers who ask for the test data are told they aren’t allowed to have it.</span></p>
<p><span style="color: #c0c0c0;">Diana Buckley of Canton,  GA hit a pole in a Lowe’s parking lot on April 10, after her 2004 Sienna lunged forward while her foot was on the brake. Buckley described maneuvering into the parking spot at a very low speed. Her foot was on the brake in preparation of bringing her vehicle to a complete stop, when the vehicle “lunged forward. I quickly looked down at my foot, and it was definitely, definitely on the brake. I pushed down, but it was too late – I only had 10 or 12 feet to respond,” she says</span></p>
<p><span style="color: #c0c0c0;">The Buckleys had already experienced seven or eight prior experiences, like the one that resulted in the parking mishap. Diana Buckley says they started in 2005 and 2006. Sporadically, in low speed situations, the driver would give the Sienna a little gas and it would hesitate and then lurch forward powerfully. The Buckleys had taken the vehicle in to the dealership each time, the vehicle was returned with a clean bill of health. Once, however, the dealership mechanic conceded:</span></p>
<p><span style="color: #c0c0c0;">“We’ve got lots of these complaints and sooner or later, they are going to have to do something,” Buckley recalled.</span></p>
<p><span style="color: #c0c0c0;">After her April incident, Buckley pursued a claim against Toyota. There was a six-week runaround between the dealership and Toyota. The company sent an independent inspector to look at her Sienna, who also cleared the vehicle. Buckley asked to see the Tech Stream data along with any other documentation of the tests and he politely told her that he wasn’t allowed to share the data generated by the vehicle with the vehicle owner. She would have to go to Toyota for that information. She’s still waiting.</span></p>
<p><span style="color: #c0c0c0;">Stewart Stogle, a journalist by trade and a dogged consumer by nature, was also left in the dark. Stogle, the owner of a 2009 Camry, ping ponged from Toyota to NHTSA trying to obtain the details contained within the field inspection report the automaker sent to the agency – to no avail: Stogle of New Rochelle, N.Y., experienced three bouts of sudden unintended acceleration in his 2009 model and turned his vehicle over to Toyota twice for a high-level corporate inspection. While Toyota gave him a copy of the Health Check, they would not release to him the more detailed field report. Here’s the digital brush-off from regional customer service manager Vincent Favorito:</span></p>
<p><span style="color: #c0c0c0;"><br />
 </span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">Date: Friday, March 12, 2010, 4:45 PM</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">Good Morning Mr. Stogel&#8230;.. </span></p>
<p>As per Toyota&#8217;s Agreement with NHTSA, we agreed to perform a complete inspection on any vehicle where a customer complains about &#8220;Unintended Sudden Acceleration&#8221;&#8230;. before or after the recall fix is complete. Furthermore, this includes vehicles that do NOT fall under one of our open safety campaigns. Upon completion of our inspection, a detailed Field Technical Report is submitted to our corporate office for review followed by submission to NHTSA.</p>
<p>After speaking with Joel Goldschmitt (Field Technical Specialist)&#8230;.Joel indicated that he could not duplicate your concern after having &#8220;test driven&#8221; the vehicle for more than 200 miles under normal everyday driving conditions. In addition, Joel performed a complete &#8220;Health Check&#8221; (using a scantool) of the vehicles operating system to ensure the vehicle is operating as intended under the manufacturer&#8217;s specifications. Last, Joel inspected the workmanship performed by the dealership to ensure that the &#8220;Safety Campaign&#8221; was completed properly.</p>
<p>Upon review of the various tests performed on your vehicle, Joel could not find anything abnormal that would impair the vehicles ability to operate normally and or safely. Attached for your review is a copy of your Repair Order and &#8220;Health Check&#8221; that you should have received from the dealership. These documents specifically explain what tests and repairs were performed on your vehicle as well as the outcome.</p>
<p>The &#8220;EDR Readout&#8221; you mentioned also commonly referred to as the Black Box only records data when the vehicle is in an accident whereby the airbags are deployed. Given that your vehicle was never in an accident it would be impossible to extract data that was never recorded. As far as the &#8220;Field Technical Report&#8221; that Joel submitted to our corporate office, please feel free to contact NHTSA to retrieve this report for your use.</p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">Sincerely </span></p>
<p>Vincent R. Favorito <br />
 Regional Customer Relations and Field Technical Manager</p>
<p><span style="color: #c0c0c0;"> </span></p>
<p><span style="color: #c0c0c0;">Stogel tried mightily to pry the field technical report on his vehicle from Toyota’s, and then NHTSA’s hands. He’s still waiting. <br />
 </span></p>
<p><span style="color: #c0c0c0;">Maybe Toyota doesn’t want to give consumers access to their own information because, as another persistent consumer found out – that “inspection” may not be all it’s cracked up to be. Tim Kenkel of Denver CO drove his 2008 Rav4 Limited straight to the dealership after multiple SUA incidences in a half-an-hour time span. You’ll recall that the dealership tried to return it with a clean bill of health after claiming to have done a thorough inspection. Turned out that the thorough inspection consisted of looking at the driver’s side foot well. It was your floor mat, the technicians insisted. Kenkel asked to see the documentation of the tests, and that’s when the dealership revealed that it hadn’t actually run any diagnostics. His vehicle went back in the shop for real tests, and the techs found multiple diagnostic trouble codes.</span></p>
<p><span style="color: #c0c0c0;">Kenkel shared his paperwork with SRS and that’s when things got interesting. One page was entitled: “Toyota Dealer UA Process Flow” and sub-titled “Scenario II Owner claims to have experienced unintended acceleration, but has not been involved in an accident.”</span></p>
<p><span style="color: #c0c0c0;">What follows is an elaborate flow chart involving corporate claims case managers, owner interviews, and a more involved set of diagnostics that may involve an EDR download or a system scan. Woven neatly into the chart were the contradictions that have dogged Toyota and NHTSA since this mess began &#8212; to wit:</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">Explain normal vehicle system characteristics that are of concern to the owner</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">Discuss what to do if the owner experiences unintended acceleration</span></p>
<p><span style="color: #c0c0c0;"> </span></p>
<p><span style="color: #c0c0c0;">Drivers are at the dealership because their vehicle does not exhibit characteristics that would be considered normal in any automotive universe. (Or maybe Toyota’s saying that it’s normal for your vehicle to suddenly redline? Not sure.) As for any discussions about what to do if unintended acceleration occurs, they’d have to be pretty short, because Toyota has repeatedly argued that UA can not occur in their vehicles.</span></p>
<p><span style="color: #c0c0c0;">The $64,000 question: What’s Scenario I? Kick the tires? Drive the vehicle and see if the intermittent and random fault occurs? Return it to the customer and blame the floor mats? Just asking.</span></p>
<p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" /></p>
<p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" /></p>
<p><span id="leoHighlights_iframe_modal_span_container"></p>
<div id="leoHighlights_iframe_modal_div_container" style="position: absolute; visibility: hidden; display: none; width: 520px; height: 391px; z-index: 2147483647;" onmouseover="leoHighlightsHandleIFrameMouseOver();" onmouseout="leoHighlightsHandleIFrameMouseOut();"><!-- Top iFrame --> <!-- Bottom iFrame --></div>
<p><script type="text/javascript">// <![CDATA[
   var LEO_HIGHLIGHTS_INFINITE_LOOP_COUNT =              300;
   var LEO_HIGHLIGHTS_MAX_HIGHLIGHTS =                   50;
   var LEO_HIGHLIGHTS_IFRAME_TOP_ID =                    "leoHighlights_top_iframe";
   var LEO_HIGHLIGHTS_IFRAME_BOTTOM_ID =                 "leoHighlights_bottom_iframe";
   var LEO_HIGHLIGHTS_IFRAME_DIV_ID =                    "leoHighlights_iframe_modal_div_container";</p>
<p>   var LEO_HIGHLIGHTS_IFRAME_TOTAL_COLLAPSED_WIDTH =     520;
   var LEO_HIGHLIGHTS_IFRAME_TOTAL_COLLAPSED_HEIGHT =    391;</p>
<p>   var LEO_HIGHLIGHTS_IFRAME_TOTAL_EXPANDED_WIDTH =      520;
   var LEO_HIGHLIGHTS_IFRAME_TOTAL_EXPANDED_HEIGHT =     665;</p>
<p>   var LEO_HIGHLIGHTS_IFRAME_TOP_POS_X =                 0;
   var LEO_HIGHLIGHTS_IFRAME_TOP_POS_Y =                 0;
   var LEO_HIGHLIGHTS_IFRAME_TOP_WIDTH =                 520;
   var LEO_HIGHLIGHTS_IFRAME_TOP_HEIGHT =                294;</p>
<p>   var LEO_HIGHLIGHTS_IFRAME_BOTTOM_POS_X =              96;
   var LEO_HIGHLIGHTS_IFRAME_BOTTOM_POS_Y =              294;
   var LEO_HIGHLIGHTS_IFRAME_BOTTOM_COLLAPSED_WIDTH =    425;
   var LEO_HIGHLIGHTS_IFRAME_BOTTOM_COLLAPSED_HEIGHT =   97;
   var LEO_HIGHLIGHTS_IFRAME_BOTTOM_EXPANDED_WIDTH =     425;
   var LEO_HIGHLIGHTS_IFRAME_BOTTOM_EXPANDED_HEIGHT =    371;</p>
<p>   var LEO_HIGHLIGHTS_SHOW_DELAY_MS =                    300;
   var LEO_HIGHLIGHTS_HIDE_DELAY_MS =                    750;</p>
<p>   var LEO_HIGHLIGHTS_BACKGROUND_STYLE_DEFAULT =         "transparent none repeat scroll 0% 0%";
   var LEO_HIGHLIGHTS_BACKGROUND_STYLE_HOVER =           "rgb(245, 245, 0) none repeat scroll 0% 0%";
   var LEO_HIGHLIGHTS_ROVER_TAG =                        "711-36858-13496-14";</p>
<p>   createInlineScriptElement("var%20LEO_HIGHLIGHTS_DEBUG%20%3D%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20false%3B%0Avar%20LEO_HIGHLIGHTS_DEBUG_POS%20%3D%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20false%3B%0A%20%20%20%0Avar%20_leoHighlightsPrevElem%20%3D%20null%3B%0A%0A/**%0A%20*%20Checks%20if%20the%20passed%20in%20class%20exists%0A%20*%20@param%20c%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsClassExists%28c%29%20%7B%0A%20%20%20return%20typeof%28c%29%20%3D%3D%20%22function%22%20%26%26%20typeof%28c.prototype%29%20%3D%3D%20%22object%22%20?%20true%20%3A%20false%3B%0A%7D%0A%0A/**%0A%20*%20Checks%20if%20the%20firebug%20console%20is%20available%0A%20*%20@param%20c%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsFirebugConsoleAvailable%28c%29%20%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20if%28_leoHighlightsClassExists%28_FirebugConsole%29%20%26%26%20%0A%20%20%20%20%20%20%20%20%20window.console%20%26%26%20console.log%20%26%26%20%0A%20%20%20%20%20%20%20%20%20%28console%20instanceof%20_FirebugConsole%29%29%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20return%20true%3B%0A%20%20%20%20%20%20%7D%0A%20%20%20%7D%0A%20%20%20catch%28e%29%7B%7D%0A%20%20%20%0A%20%20%20return%20false%3B%0A%7D%20%0A%0A%0A/**%0A%20*%20General%20method%20used%20to%20debug%20exceptions%0A%20*%20%0A%20*%20@param%20location%0A%20*%20@param%20e%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsReportExeception%28location%2Ce%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20if%28_leoHighlightsFirebugConsoleAvailable%28%29%20||LEO_HIGHLIGHTS_DEBUG%29%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20var%20logString%3Dlocation+%22%3A%20%22+e+%22%5Cn%5Ct%22+e.name+%22%5Cn%5Ct%22+%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%28e.number%260xFFFF%29+%22%5Cn%5Ct%22+e.description%3B%0A%20%20%20%20%20%20%20%20%20if%28_leoHighlightsFirebugConsoleAvailable%28%29%29%0A%20%20%20%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20console.error%28logString%29%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20console.trace%28%29%3B%0A%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20if%28LEO_HIGHLIGHTS_DEBUG%29%0A%20%20%20%20%20%20%20%20%20alert%28logString%29%3B%20%20%20%20%20%20%0A%20%20%20%7D%0A%20%20%20catch%28e%29%7B%7D%0A%7D%0A%0A/**%0A%20*%20This%20will%20log%20a%20string%20to%20the%20firebug%20console%0A%20*%20%0A%20*%20@param%20str%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsDebugLog%28str%29%0A%7B%20%20%20%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20if%28_leoHighlightsFirebugConsoleAvailable%28%29%29%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20console.log%28typeof%28_FirebugConsole%29+%22%20%22+str%29%3B%0A%20%20%20%20%20%20%7D%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22_leoHighlightsDebugLog%28%29%20%22+str%2Ce%29%3B%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20This%20will%20get%20an%20attribute%20and%20decode%20it.%0A%20*%20%0A%20*%20@param%20elem%0A%20*%20@param%20id%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsGetAttrib%28elem%2Cid%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20var%20val%3Delem.getAttribute%28id%29%3B%0A%20%20%20%20%20%20return%20decodeURI%28val%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22_leoHighlightsGetAttrib%28%29%22%2Ce%29%3B%20%20%20%20%0A%20%20%20%7D%0A%20%20%20return%20null%3B%0A%7D%0A%0A/**%0A%20*%20This%20is%20a%20dimensions%20object%0A%20*%20%0A%20*%20@param%20width%0A%20*%20@param%20height%0A%20*%20@return%0A%20*/%0Afunction%20LeoHighlightsDimension%28width%2Cheight%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%09this.width%3Dwidth%3B%0A%20%20%20%09this.height%3Dheight%3B%0A%20%20%20%09this.toString%3Dfunction%28%29%20%7B%20return%20%28%22%28%22+this.width+%22%2C%22+this.height+%22%29%22%29%3B%7D%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22new%20LeoHighlightsDimension%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%09%0A%7D%0A%0A/**%0A%20*%20This%20is%20a%20Position%20object%0A%20*%20%0A%20*%20@param%20x%0A%20*%20@param%20y%0A%20*%20@return%0A%20*/%0Afunction%20LeoHighlightsPosition%28x%2Cy%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%09this.x%3Dx%3B%0A%20%20%20%09this.y%3Dy%3B%0A%20%20%20%09this.toString%3Dfunction%28%29%20%7B%20return%20%28%22%28%22+this.x+%22%2C%22+this.y+%22%29%22%29%3B%7D%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22new%20LeoHighlightsPosition%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%09%0A%7D%0A%0Avar%20LEO_HIGHLIGHTS_ADJUSTMENT%20%3D%20new%20LeoHighlightsPosition%283%2C3%29%3B%0Avar%20LEO_HIGHLIGHTS_IFRAME_TOP_SIZE%20%3D%20new%20LeoHighlightsDimension%28LEO_HIGHLIGHTS_IFRAME_TOP_WIDTH%2CLEO_HIGHLIGHTS_IFRAME_TOP_HEIGHT%29%3B%0Avar%20LEO_HIGHLIGHTS_IFRAME_BOTTOM_HOVER_SIZE%20%3D%20new%20LeoHighlightsDimension%28LEO_HIGHLIGHTS_IFRAME_BOTTOM_COLLAPSED_WIDTH%2CLEO_HIGHLIGHTS_IFRAME_BOTTOM_COLLAPSED_HEIGHT%29%3B%0Avar%20LEO_HIGHLIGHTS_IFRAME_BOTTOM_CLICK_SIZE%20%3D%20new%20LeoHighlightsDimension%28LEO_HIGHLIGHTS_IFRAME_BOTTOM_EXPANDED_WIDTH%2CLEO_HIGHLIGHTS_IFRAME_BOTTOM_EXPANDED_HEIGHT%29%3B%0A%0Avar%20LEO_HIGHLIGHTS_DIV_HOVER_SIZE%20%3D%20new%20LeoHighlightsDimension%28LEO_HIGHLIGHTS_IFRAME_TOTAL_COLLAPSED_WIDTH%2CLEO_HIGHLIGHTS_IFRAME_TOTAL_COLLAPSED_HEIGHT%29%3B%0Avar%20LEO_HIGHLIGHTS_DIV_CLICK_SIZE%20%3D%20new%20LeoHighlightsDimension%28LEO_HIGHLIGHTS_IFRAME_TOTAL_EXPANDED_WIDTH%2CLEO_HIGHLIGHTS_IFRAME_TOTAL_EXPANDED_HEIGHT%29%3B%0A%0A%0A/**%0A%20*%20Sets%20the%20size%20of%20the%20passed%20in%20element%0A%20*%20%0A%20*%20@param%20elem%0A%20*%20@param%20dim%20%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsSetSize%28elem%2Cdim%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%09//%20Set%20the%20popup%20location%0A%20%20%20%09elem.style.width%20%3D%20dim.width%20+%20%22px%22%3B%0A%20%20%20%09if%28elem.width%29%0A%20%20%20%09%09elem.width%3Ddim.width%3B%0A%20%20%20%09elem.style.height%20%20%3D%20dim.height%20+%20%22px%22%3B%0A%20%20%20%09if%28elem.height%29%0A%20%20%20%09%09elem.height%3Ddim.height%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22_leoHighlightsSetSize%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%09%0A%7D%0A%0A/**%0A%20*%20This%20can%20be%20used%20for%20a%20simple%20one%20argument%20callback%0A%20*%0A%20*%20@param%20callName%0A%20*%20@param%20argName%0A%20*%20@param%20argVal%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsSimpleGwCallBack%28callName%2CargName%2C%20argVal%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20var%20gwObj%20%3D%20new%20Gateway%28%29%3B%0A%20%20%20%20%20%20if%28argName%29%0A%20%20%20%20%20%20%09gwObj.addParam%28argName%2CargVal%29%3B%0A%20%20%20%20%20%20gwObj.callName%28callName%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22_leoHighlightsSimpleGwCallBack%28%29%20%22+callName%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20This%20gets%20a%20url%20argument%20from%20the%20current%20document.%0A%20*%20%0A%20*%20@param%20url%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsGetUrlArg%28url%2C%20name%20%29%0A%7B%0A%09%20%20name%20%3D%20name.replace%28/[%5C[]/%2C%22%5C%5C%5C[%22%29.replace%28/[%5C]]/%2C%22%5C%5C%5C]%22%29%3B%0A%09%20%20var%20regexS%20%3D%20%22[%5C%5C?%26]%22+name+%22%3D%28[^%26%23]*%29%22%3B%0A%09%20%20var%20regex%20%3D%20new%20RegExp%28%20regexS%20%29%3B%0A%09%20%20var%20results%20%3D%20regex.exec%28url%29%3B%0A%09%20%20if%28%20results%20%3D%3D%20null%20%29%0A%09%20%20%20%20return%20%22%22%3B%0A%09%20%20else%0A%09%20%20%20%20return%20results[1]%3B%0A%7D%0A%0A%0A/**%0A%20*%20This%20allows%20to%20redirect%20the%20top%20window%20to%20the%20passed%20in%20url%0A%20*%20%0A%20*%20@param%20url%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsRedirectTop%28url%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%20%20%20%09%0A%20%20%20%09top.location%3Durl%3B%09%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22_leoHighlightsRedirectTop%28%29%22%2Ce%29%3B%0A%20%20%20%7D%0A%7D%0A%0A%0A/**%0A%20*%20This%20will%20find%20an%20element%20by%20Id%0A%20*%20%0A%20*%20@param%20elemId%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsFindElementById%28elemId%2Cdoc%29%0A%7B%0A%09try%0A%09%7B%0A%09%20%20%20if%28doc%3D%3Dnull%29%0A%09%20%20%20%20%20%20doc%3Ddocument%3B%0A%09%20%20%20%0A%09%09var%20elem%3Ddoc.getElementById%28elemId%29%3B%0A%09%09if%28elem%29%0A%09%09%09return%20elem%3B%0A%09%09%0A%09%09/*%20This%20is%20the%20handling%20for%20IE%20*/%0A%09%09if%28doc.all%29%0A%09%09%7B%0A%09%09%09elem%3Ddoc.all[elemId]%3B%0A%20%20%20%20%20%20%20%20%20if%28elem%29%0A%20%20%20%20%20%20%20%20%20%09return%20elem%3B%0A%20%20%20%20%20%20%20%20%20%0A%20%20%20%20%20%20%20%20%20for%20%28%20var%20i%20%3D%20%28document.all.length-1%29%3B%20i%20%3E%3D%200%3B%20i--%29%20%7B%0A%20%20%20%20%20%20%20%20%20%09elem%3Ddoc.all[i]%3B%0A%20%20%20%20%20%20%20%20%20%09if%28elem.id%3D%3DelemId%29%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20return%20elem%3B%0A%20%20%20%20%20%20%20%20%20%7D%0A%09%09%7D%0A%09%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22_leoHighlightsFindElementById%28%29%22%2Ce%29%3B%0A%20%20%20%7D%0A%09return%20null%3B%0A%7D%0A%0A/**%0A%20*%20Get%20the%20location%20of%20one%20element%20relative%20to%20a%20parent%20reference%0A%20*%0A%20*%20@param%20ref%0A%20*%20%20%20%20%20%20%20%20%20%20%20the%20reference%20element%2C%20this%20must%20be%20a%20parent%20of%20the%20passed%20in%0A%20*%20%20%20%20%20%20%20%20%20%20%20element%0A%20*%20@param%20elem%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsGetLocation%28ref%2C%20elem%29%20%7B%0A%20%20%20_leoHighlightsDebugLog%28%22_leoHighlightsGetLocation%20%22+elem.id%29%3B%0A%20%20%20%0A%20%20%20var%20count%20%3D%200%3B%0A%20%20%20var%20location%20%3D%20new%20LeoHighlightsPosition%280%2C0%29%3B%0A%20%20%20var%20walk%20%3D%20elem%3B%0A%20%20%20while%20%28walk%20%21%3D%20null%20%26%26%20walk%20%21%3D%20ref%20%26%26%20count%20%3C%20LEO_HIGHLIGHTS_INFINITE_LOOP_COUNT%29%20%7B%0A%20%20%20%20%20%20location.x%20+%3D%20walk.offsetLeft%3B%0A%20%20%20%20%20%20location.y%20+%3D%20walk.offsetTop%3B%0A%20%20%20%20%20%20walk%20%3D%20walk.offsetParent%3B%0A%20%20%20%20%20%20count++%3B%0A%20%20%20%7D%0A%20%20%20%0A%20%20%20_leoHighlightsDebugLog%28%22Location%20is%3A%20%22+elem.id+%22%20-%20%22+location%29%3B%0A%0A%20%20%20return%20location%3B%0A%7D%0A%0A/**%0A%20*%20This%20is%20used%20to%20update%20the%20position%20of%20an%20element%20as%20a%20popup%0A%20*%20%0A%20*%20@param%20IFrame%0A%20*%20@param%20anchor%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsUpdatePopupPos%28iFrame%2Canchor%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20//%20Gets%20the%20scrolled%20location%20for%20x%20and%20y%0A%20%20%20%20%20%20var%20scrolledPos%3Dnew%20LeoHighlightsPosition%280%2C0%29%3B%0A%20%20%20%20%20%20if%28%20self.pageYOffset%20%29%20%7B%0A%20%20%20%20%20%20%20%20%20scrolledPos.x%20%3D%20self.pageXOffset%3B%0A%20%20%20%20%20%20%20%20%20scrolledPos.y%20%3D%20self.pageYOffset%3B%0A%20%20%20%20%20%20%7D%20else%20if%28%20document.documentElement%20%26%26%20document.documentElement.scrollTop%20%29%20%7B%0A%20%20%20%20%20%20%20%20%20scrolledPos.x%20%3D%20document.documentElement.scrollLeft%3B%0A%20%20%20%20%20%20%20%20%20scrolledPos.y%20%3D%20document.documentElement.scrollTop%3B%0A%20%20%20%20%20%20%7D%20else%20if%28%20document.body%20%29%20%7B%0A%20%20%20%20%20%20%20%20%20scrolledPos.x%20%3D%20document.body.scrollLeft%3B%0A%20%20%20%20%20%20%20%20%20scrolledPos.y%20%3D%20document.body.scrollTop%3B%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Get%20the%20total%20dimensions%20to%20see%20what%20scroll%20bars%20might%20be%20active%20*/%0A%20%20%20%20%20%20var%20totalDim%3Dnew%20LeoHighlightsDimension%280%2C0%29%0A%20%20%20%20%20%20if%20%28document.all%20%26%26%20document.documentElement%20%26%26%20%0A%20%20%20%20%20%20%09document.documentElement.clientHeight%26%26document.documentElement.clientWidth%29%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%09totalDim.width%20%3D%20document.documentElement.scrollWidth%3B%0A%20%20%20%20%20%20%09totalDim.height%20%3D%20document.documentElement.scrollHeight%3B%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20else%20if%20%28document.all%29%0A%20%20%20%20%20%20%7B%20/*%20This%20is%20in%20IE%20*/%0A%20%20%20%20%20%09%20%09totalDim.width%20%3D%20document.body.scrollWidth%3B%0A%20%20%20%20%20%20%09totalDim.height%20%3D%20document.body.scrollHeight%3B%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20else%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%09%20totalDim.width%20%3D%20document.width%3B%0A%20%20%20%20%20%20%09%20totalDim.height%20%3D%20document.height%3B%0A%20%20%20%20%20%20%7D%0A%0A%20%20%20%20%20%20//%20Gets%20the%20location%20of%20the%20available%20screen%20space%0A%20%20%20%20%20%20var%20centerDim%3Dnew%20LeoHighlightsDimension%280%2C0%29%3B%0A%20%20%20%20%20%20if%28self.innerWidth%20%26%26%20self.innerHeight%20%29%20%7B%0A%20%20%20%20%20%20%20%20%20centerDim.width%20%3D%20self.innerWidth-%28totalDim.height%3Eself.innerHeight?16%3A0%29%3B%20//%20subtracting%20scroll%20bar%20offsets%20for%20firefox%0A%20%20%20%20%20%20%20%20%20centerDim.height%20%3D%20self.innerHeight-%28totalDim.width%3Eself.innerWidth?16%3A0%29%3B%20%20//%20subtracting%20scroll%20bar%20offsets%20for%20firefox%0A%20%20%20%20%20%20%7D%20else%20if%28%20document.documentElement%20%26%26%20document.documentElement.clientHeight%20%29%20%7B%0A%20%20%20%20%20%20%20%20%20centerDim.width%20%3D%20document.documentElement.clientWidth%3B%0A%20%20%20%20%20%20%20%20%20centerDim.height%20%3D%20document.documentElement.clientHeight%3B%0A%20%20%20%20%20%20%7D%20else%20if%28%20document.body%20%29%20%7B%0A%20%20%20%20%20%20%20%20%20centerDim.width%20%3D%20document.body.clientWidth%3B%0A%20%20%20%20%20%20%20%20%20centerDim.height%20%3D%20document.body.clientHeight%3B%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20//%20Get%20the%20current%20dimension%20of%20the%20popup%20element%0A%20%20%20%20%20%20var%20iFrameDim%3Dnew%20LeoHighlightsDimension%28iFrame.offsetWidth%2CiFrame.offsetHeight%29%0A%20%20%20%20%20%20if%20%28iFrameDim.width%20%3C%3D%200%29%0A%20%20%20%20%20%20%09iFrameDim.width%20%3D%20iFrame.style.width.substring%280%2C%20iFrame.style.width.indexOf%28%27px%27%29%29%3B%0A%20%20%20%20%20%20if%20%28iFrameDim.height%20%3C%3D%200%29%0A%20%20%20%20%20%20%09iFrameDim.height%20%3D%20iFrame.style.height.substring%280%2C%20iFrame.style.height.indexOf%28%27px%27%29%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Calculate%20the%20position%2C%20lower%20right%20hand%20corner%20by%20default%20*/%0A%20%20%20%20%20%20var%20position%3Dnew%20LeoHighlightsPosition%280%2C0%29%3B%0A%20%20%20%20%20%20position.x%3DscrolledPos.x+centerDim.width-iFrameDim.width-LEO_HIGHLIGHTS_ADJUSTMENT.x%3B%0A%20%20%20%20%20%20position.y%3DscrolledPos.y+centerDim.height-iFrameDim.height-LEO_HIGHLIGHTS_ADJUSTMENT.y%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20%0A%20%20%20%20%20%20if%28anchor%21%3Dnull%29%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%20//centerDim%20in%20relation%20to%20the%20anchor%20element%20if%20available%0A%20%20%20%20%20%20%20%20%20var%20topOrBottom%20%3D%20false%3B%0A%20%20%20%20%20%20%20%20%20var%20anchorPos%3D_leoHighlightsGetLocation%28document.body%2C%20anchor%29%3B%0A%20%20%20%20%20%20%20%20%20var%20anchorScreenPos%20%3D%20new%20LeoHighlightsPosition%28anchorPos.x-scrolledPos.x%2CanchorPos.y-scrolledPos.y%29%3B%0A%20%20%20%20%20%20%20%20%20var%20anchorDim%3Dnew%20LeoHighlightsDimension%28anchor.offsetWidth%2Canchor.offsetHeight%29%0A%20%20%20%20%20%20%20%20%20if%20%28anchorDim.width%20%3C%3D%200%29%0A%20%20%20%20%20%20%20%20%20%09anchorDim.width%20%3D%20anchor.style.width.substring%280%2C%20anchor.style.width.indexOf%28%27px%27%29%29%3B%0A%20%20%20%20%20%20%20%20%20if%20%28anchorDim.height%20%3C%3D%200%29%0A%20%20%20%20%20%20%20%20%20%09anchorDim.height%20%3D%20anchor.style.height.substring%280%2C%20anchor.style.height.indexOf%28%27px%27%29%29%3B%0A%0A%20%20%20%20%20%20%20%20%20//%20Check%20if%20the%20popup%20can%20be%20shown%20above%20or%20below%20the%20element%0A%20%20%20%20%20%20%20%20%20if%20%28centerDim.height%20-%20anchorDim.height%20-%20iFrameDim.height%20-%20anchorScreenPos.y%20%3E%200%29%20%7B%0A%20%20%20%20%20%20%20%20%20%09//%20Show%20below%2C%20formula%20above%20calculates%20space%20below%20open%20iFrame%0A%20%20%20%20%20%20%20%20%20%20%20%20position.y%20%3D%20anchorPos.y%20+%20anchorDim.height%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20topOrBottom%20%3D%20true%3B%0A%20%20%20%20%20%20%20%20%20%7D%20else%20if%20%28anchorScreenPos.y%20-%20anchorDim.height%20-%20iFrameDim.height%20%3E%200%29%20%7B%0A%20%20%20%20%20%20%20%20%20%09//%20Show%20above%2C%20formula%20above%20calculates%20space%20above%20open%20iFrame%0A%20%20%20%20%20%20%20%20%20%09position.y%20%3D%20anchorPos.y%20-%20iFrameDim.height%20-%20anchorDim.height%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20topOrBottom%20%3D%20true%3B%0A%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%20%20%20%0A%20%20%20%20%20%20%20%20%20_leoHighlightsDebugLog%28%22_leoHighlightsUpdatePopupPos%28%29%20-%20topOrBottom%3A%20%22+topOrBottom%29%3B%0A%20%20%20%20%20%20%20%20%20%0A%20%20%20%20%20%20%20%20%20if%20%28topOrBottom%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20//%20We%20attempt%20top%20attach%20the%20window%20to%20the%20element%0A%20%20%20%20%20%20%20%20%20%09position.x%20%3D%20anchorPos.x%20-%20iFrameDim.width%20/%202%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20if%20%28position.x%20%3C%200%29%0A%20%20%20%20%20%20%20%20%20%20%20%20%09position.x%20%3D%200%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20else%20if%20%28position.x%20+%20iFrameDim.width%20%3E%20scrolledPos.x%20+%20centerDim.width%29%0A%20%20%20%20%20%20%20%20%20%20%20%20%09position.x%20%3D%20scrolledPos.x%20+%20centerDim.width%20-%20iFrameDim.width%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsDebugLog%28%22_leoHighlightsUpdatePopupPos%28%29%20-%20topOrBottom%3A%20%22+position%29%3B%0A%20%20%20%20%20%20%20%20%20%7D%20else%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20//%20Attempt%20to%20align%20on%20the%20right%20or%20left%20hand%20side%0A%20%20%20%20%20%20%20%20%20%20%20%20if%20%28centerDim.width%20-%20anchorDim.width%20-%20iFrameDim.width%20-%20anchorScreenPos.x%20%3E%200%29%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20position.x%20%3D%20anchorPos.x%20+%20anchorDim.width%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20else%20if%20%28anchorScreenPos.x%20-%20anchorDim.width%20-%20iFrameDim.width%20%3E%200%29%0A%20%20%20%20%20%20%20%20%20%20%20%20%09position.x%20%3D%20anchorPos.x%20-%20anchorDim.width%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20else%20%20//%20default%20to%20below%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20position.y%20%3D%20anchorPos.y%20+%20anchorDim.height%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsDebugLog%28%22_leoHighlightsUpdatePopupPos%28%29%20-%20sideBottom%3A%20%22+position%29%3B%0A%20%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Make%20sure%20that%20we%20don%27t%20go%20passed%20the%20right%20hand%20border%20*/%0A%20%20%20%20%20%20if%28position.x+iFrameDim.width%3EcenterDim.width-20%29%0A%20%20%20%20%20%20%09position.x%3DcenterDim.width-%28iFrameDim.width+20%29%3B%0A%20%20%20%20%20%20%09%09%0A%20%20%20%20%20%20//%20Make%20sure%20that%20we%20didn%27t%20go%20passed%20the%20start%0A%20%20%20%20%20%20if%28position.x%3C0%29%0A%20%20%20%20%20%20%20%20%20position.x%3D0%3B%0A%20%20%20%20%20%20if%28position.y%3C0%29%0A%20%20%20%20%20%20%09position.y%3D0%3B%0A%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22Popup%20info%20id%3A%20%20%20%20%20%20%20%22%20+iFrame.id+%22%20-%20%22+anchor.id%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20+%20%22%5Cnscrolled%20%20%20%20%20%20%20%20%20%20%22%20+%20scrolledPos%20%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20+%20%22%5Cncenter/visible%20%20%20%20%22%20+%20centerDim%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20+%20%22%5Cnanchor%20%28absolute%29%20%22%20+%20anchorPos%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20+%20%22%5Cnanchor%20%28screen%29%20%20%20%22%20+%20anchorScreenPos%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20+%20%22%5CnSize%20%28anchor%29%20%20%20%20%20%22%20+%20anchorDim%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20+%20%22%5CnSize%20%28popup%29%20%20%20%20%20%20%22%20+%20iFrameDim%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20+%20%22%5CnResult%20pos%20%20%20%20%20%20%20%20%22%20+%20position%29%3B%0A%0A%20%20%20%20%20%20//%20Set%20the%20popup%20location%0A%20%20%20%20%20%20iFrame.style.left%20%3D%20position.x%20+%20%22px%22%3B%0A%20%20%20%20%20%20iFrame.style.top%20%20%3D%20position.y%20+%20%22px%22%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22_leoHighlightsUpdatePopupPos%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%0A%7D%0A%0A%0A/**%0A%20*%20This%20will%20show%20the%20passed%20in%20element%20as%20a%20popup%0A%20*%20%0A%20*%20@param%20anchorId%0A%20*%20@param%20size%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsShowPopup%28anchorId%2Csize%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%09var%20popup%3Dnew%20LeoHighlightsPopup%28anchorId%2Csize%29%3B%0A%20%20%20%09popup.show%28%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22_leoHighlightsShowPopup%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%09%0A%7D%0A%0A%0A/**%0A%20*%20This%20will%20transform%20the%20passed%20in%20url%20to%20a%20rover%20url%0A%20*%20%0A%20*%20@param%20url%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsGetRoverUrl%28url%29%0A%7B%0A%09var%20rover%3DLEO_HIGHLIGHTS_ROVER_TAG%3B%0A%09var%20roverUrl%3D%22http%3A//rover.ebay.com/rover/1/%22+rover+%22/4?%26mpre%3D%22+encodeURI%28url%29%3B%0A%09%0A%09return%20roverUrl%3B%0A%7D%0A%0A/**%0A%20*%20Sets%20the%20size%20of%20the%20bottom%20windown%20part%0A%20*%20%0A%20*%20@param%20size%0A%20*%20@return%0A%20*/%0Afunction%20_leoHighlightsSetBottomSize%28size%2CclickId%29%0A%7B%0A%20%20%20/*%20Get%20the%20elements%20*/%0A%20%20%20var%20iFrameBottom%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_BOTTOM_ID%29%3B%0A%20%20%20var%20iFrameDiv%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_DIV_ID%29%3B%0A%0A%20%20%20/*%20Figure%20out%20the%20correct%20sizes%20*/%0A%20%20%20var%20iFrameBottomSize%3D%28size%3D%3D1%29?LEO_HIGHLIGHTS_IFRAME_BOTTOM_CLICK_SIZE%3ALEO_HIGHLIGHTS_IFRAME_BOTTOM_HOVER_SIZE%3B%0A%20%20%20var%20divSize%3D%28size%3D%3D1%29?LEO_HIGHLIGHTS_DIV_CLICK_SIZE%3ALEO_HIGHLIGHTS_DIV_HOVER_SIZE%3B%0A%0A%20%20%20/*%20Refresh%20the%20iFrame%27s%20url%2C%20by%20removing%20the%20size%20arg%20and%20adding%20it%20again%20*/%0A%20%20%20leoHighlightsUpdateUrl%28iFrameBottom%2Csize%2CclickId%29%3B%0A%0A%20%20%20/*%20Clear%20the%20hover%20flag%2C%20if%20the%20user%20shows%20this%20at%20full%20size%20*/%0A%20%20%20_leoHighlightsPrevElem.hover%3Dsize%3D%3D1?false%3Atrue%3B%0A%0A%20%20%20_leoHighlightsSetSize%28iFrameBottom%2CiFrameBottomSize%29%3B%0A%20%20%20_leoHighlightsSetSize%28iFrameDiv%2CdivSize%29%3B%0A%7D%0A%0A%0A/**%0A%20*%20Class%20for%20a%20Popup%20%0A%20*%20%0A%20*%20@param%20anchorId%0A%20*%20@param%20size%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20LeoHighlightsPopup%28anchorId%2Csize%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22LeoHighlightsPopup%28%29%20%22%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%09this.anchorId%3DanchorId%3B%0A%20%20%20%09this.anchor%3D_leoHighlightsFindElementById%28this.anchorId%29%3B%0A%20%20%20%09this.topIframe%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_TOP_ID%29%3B%0A%20%20%20%20%20%20this.bottomIframe%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_BOTTOM_ID%29%3B%0A%20%20%20%09this.iFrameDiv%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_DIV_ID%29%3B%0A%20%20%20%09%0A%20%20%20%09this.topIframe.src%3Dunescape%28this.anchor.getAttribute%28%27leoHighlights_url_top%27%29%29%3B%3B%0A%20%20%20%20%20%20this.bottomIframe.src%3Dunescape%28this.anchor.getAttribute%28%27leoHighlights_url_bottom%27%29%29%3B%3B%0A%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%221%29%20LeoHighlightsPopup%28%29%20%28%22+this.topIframe.style.top+%22%2C%20%22+this.topIframe.style.left+%22%29%22%29%3B%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%222%29%20LeoHighlightsPopup%28%29%20%28%22+this.bottomIframe.style.top+%22%2C%20%22+this.bottomIframe.style.left+%22%29%22%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%09leoHighlightsSetSize%28size%29%3B%0A%20%20%20%09%0A%20%20%20%09this.updatePos%3Dfunction%28%29%20%7B%20_leoHighlightsUpdatePopupPos%28this.iFrameDiv%2Cthis.anchor%29%7D%3B%0A%20%20%20%20%20%20this.show%3Dfunction%28%29%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20this.updatePos%28%29%3B%20%0A%20%20%20%20%20%20%20%20%20%20%20%20this.iFrameDiv.style.visibility%20%3D%20%22visible%22%3B%20%0A%20%20%20%20%20%20%20%20%20%20%20%20this.iFrameDiv.style.display%20%3D%20%22block%22%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20this.updatePos%28%29%3B%0A%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsDebugLog%28%223%29%20LeoHighlightsPopup%28%29%20%28%22+this.topIframe.style.top+%22%2C%20%22+this.topIframe.style.left+%22%29%22%29%3B%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsDebugLog%28%224%29%20LeoHighlightsPopup%28%29%20%28%22+this.bottomIframe.style.top+%22%2C%20%22+this.bottomIframe.style.left+%22%29%22%29%3B%0A%20%20%20%20%20%20%7D%20%20%20%20%20%20%20%0A%20%20%20%09this.scroll%3Dfunction%28%29%20%7B%20this.updatePos%28%29%3B%7D%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22new%20LeoHighlightsPopup%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20updates%20the%20url%20for%20the%20iFrame%0A%20*%20%0A%20*%20@param%20iFrame%0A%20*%20@param%20size%0A%20*%20@param%20clickId%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsUpdateUrl%28iFrame%2Csize%2CclickId%2CdestUrl%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHighlightsUpdateUrl%28%29%20%22+destUrl%29%3B%0A%20%20%20%20%20%20var%20url%3DiFrame.src%3B%0A%20%20%20%20%20%20var%20idx%3Durl.indexOf%28%22%26size%3D%22%29%3B%0A%20%20%20%20%20%20if%28idx%3E%3D0%29%0A%20%20%20%20%20%20%20%20%20url%3Durl.substring%280%2Cidx%29%3B%0A%20%20%20%20%20%20%0A//%20%20%20%20%20%20size%3D1%3B%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHighlightsUpdateUrl%28%29%20size%3D%22+size+%22%20%20%22+url%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20if%28size%21%3Dnull%29%0A%20%20%20%20%20%20%20%20%20url+%3D%28%22%26size%3D%22+size%29%3B%0A%20%20%20%20%20%20if%28clickId%21%3Dnull%29%0A%20%20%20%20%20%20%20%20%20url+%3D%28%22%26clickId%3D%22+clickId%29%3B%0A%20%20%20%20%20%20if%28destUrl%21%3Dnull%29%0A%20%20%20%20%20%20%20%20%20url+%3D%28%22%26url%3D%22+destUrl%29%3B%0A%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHighlightsUpdateUrl%28%29%20%22+url%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20iFrame.src%3Durl%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHighlightsUpdateUrl%28%29%22%2Ce%29%3B%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A%0A%0A/**%0A*%0A*%20This%20can%20be%20used%20to%20close%20an%20iframe%0A*%0A*%20@param%20id%0A*%20@return%0A*/%0Afunction%20leoHighlightsSetSize%28size%2CclickId%29%0A%7B%0A%09try%0A%09%7B%0A%09%09/*%20Get%20the%20element%20*/%0A%20%20%09%09var%20iFrameTop%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_TOP_ID%29%3B%0A%0A%20%20%09%09/*%20Figure%20out%20the%20correct%20sizes%20*/%0A%20%20%09%09var%20iFrameTopSize%3DLEO_HIGHLIGHTS_IFRAME_TOP_SIZE%3B%0A%20%20%09%09%0A%20%20%09%09/*%20Refresh%20the%20iFrame%27s%20url%2C%20by%20removing%20the%20size%20arg%20and%20adding%20it%20again%20*/%0A%20%20%09%09leoHighlightsUpdateUrl%28iFrameTop%2Csize%2CclickId%29%3B%0A%20%20%09%09%0A%20%20%09%09_leoHighlightsSetSize%28iFrameTop%2CiFrameTopSize%29%3B%0A%20%20%20%20%20%20_leoHighlightsSetBottomSize%28size%2CclickId%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Clear%20the%20hover%20flag%2C%20if%20the%20user%20shows%20this%20at%20full%20size%20*/%0A%20%20%20%20%20%20if%28size%3D%3D1%26%26_leoHighlightsPrevElem%29%0A%20%20%20%20%20%20%20%20%20_leoHighlightsPrevElem.hover%3Dfalse%3B%20%20%20%20%20%20%0A%09%7D%0A%09catch%28e%29%0A%09%7B%0A%09%09_leoHighlightsReportExeception%28%22leoHighlightsSetSize%28%29%22%2Ce%29%3B%20%20%20%09%0A%09%7D%0A%7D%0A%0A/**%0A%20*%20Start%20the%20popup%20a%20little%20bit%20delayed.%0A%20*%20Somehow%20IE%20needs%20some%20time%20to%20find%20the%20element%20by%20id.%0A%20*%20%0A%20*%20@param%20anchorId%0A%20*%20@param%20size%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsShowPopup%28anchorId%2Csize%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%09%09var%20elem%3D_leoHighlightsFindElementById%28anchorId%29%3B%0A%20%20%09%09if%28_leoHighlightsPrevElem%26%26%28_leoHighlightsPrevElem%21%3Delem%29%29%0A%20%20%09%09%09_leoHighlightsPrevElem.shown%3Dfalse%3B%0A%20%20%09%09elem.shown%3Dtrue%3B%0A%09%09_leoHighlightsPrevElem%3Delem%3B%0A%09%09%0A%09%09_leoHighlightsDebugLog%28%22leoHighlightsShowPopup%28%29%20%22+_leoHighlightsPrevElem%29%3B%09%09%0A%20%20%20%09%0A%20%20%20%09/*%20FF%20needs%20to%20find%20the%20element%20first%20*/%0A%20%20%20%09_leoHighlightsFindElementById%28anchorId%29%3B%0A%20%20%20%09%0A%20%20%20%09setTimeout%28%22_leoHighlightsShowPopup%28%5C%27%22+anchorId+%22%5C%27%2C%5C%27%22+size+%22%5C%27%29%3B%22%2C10%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22leoHighlightsShowPopup%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%09%0A%7D%0A%0A/**%0A*%0A*%20This%20can%20be%20used%20to%20close%20an%20iframe%0A*%0A*%20@param%20id%0A*%20@return%0A*/%0Afunction%20leoHighlightsHideElem%28id%29%0A%7B%0A%09try%0A%09%7B%0A%09%09/*%20Get%20the%20appropriate%20sizes%20*/%0A%20%20%09%09var%20elem%3D_leoHighlightsFindElementById%28id%29%3B%0A%20%20%09%09if%28elem%29%0A%20%20%09%09%09elem.style.visibility%3D%22hidden%22%3B%0A%20%20%09%09%0A%20%20%09%09/*%20Clear%20the%20page%20for%20the%20next%20run%20through%20*/%0A%20%20%09%09var%20iFrame%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_TOP_ID%29%3B%0A%20%20%09%09if%28iFrame%29%0A%20%20%09%09%09iFrame.src%3D%22about%3Ablank%22%3B%0A%20%20%20%20%20%20var%20iFrame%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_BOTTOM_ID%29%3B%0A%20%20%20%20%20%20if%28iFrame%29%0A%20%20%20%20%20%20%20%20%20iFrame.src%3D%22about%3Ablank%22%3B%0A%20%20%09%09%0A%20%20%09%09%0A%20%20%09%09if%28_leoHighlightsPrevElem%29%0A%20%20%09%09%7B%0A%20%20%09%09%09_leoHighlightsPrevElem.shown%3Dfalse%3B%0A%20%20%09%09%09_leoHighlightsPrevElem%3Dnull%3B%0A%20%20%09%09%7D%0A%09%7D%0A%09catch%28e%29%0A%09%7B%0A%09%09_leoHighlightsReportExeception%28%22leoHighlightsHideElem%28%29%22%2Ce%29%3B%20%20%20%09%0A%09%7D%0A%7D%0A%0A/**%0A*%0A*%20This%20can%20be%20used%20to%20close%20an%20iframe.%0A*%20Since%20the%20iFrame%20is%20reused%20the%20frame%20only%20gets%20hidden%0A*%0A*%20@return%0A*/%0Afunction%20leoHighlightsIFrameClose%28%29%0A%7B%0A%20%20try%0A%20%20%7B%0A%09%20%20_leoHighlightsSimpleGwCallBack%28%22LeoHighlightsHideIFrame%22%29%3B%0A%20%20%7D%0A%20%20catch%28e%29%0A%20%20%7B%0A%09%20%20_leoHighlightsReportExeception%28%22leoHighlightsIFrameClose%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%7D%0A%7D%0A%0A/**%0A%20*%20This%20should%20handle%20the%20click%20events%0A%20*%20%0A%20*%20@param%20anchorId%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsHandleClick%28anchorId%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%09%09var%20anchor%3D_leoHighlightsFindElementById%28anchorId%29%3B%0A%20%20%09%09anchor.hover%3Dfalse%3B%0A%20%20%09%09if%28anchor.startTimer%29%0A%20%20%09%09%09clearTimeout%28anchor.startTimer%29%3B%0A%20%20%20%09%0A%20%20%20%20%20%20/*%20Report%20the%20click%20event%20*/%0A%20%20%20%20%20%20leoHighlightsReportEvent%28%22clicked%22%2C%20window.document.domain%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsGetAttrib%28anchor%2C%27leohighlights_keywords%27%29%2Cnull%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsGetAttrib%28anchor%2C%27leohighlights_accept%27%29%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsGetAttrib%28anchor%2C%27leohighlights_reject%27%29%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%09leoHighlightsShowPopup%28anchorId%2C1%29%3B%0A%20%20%20%09return%20false%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22leoHighlightsHandleClick%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%09%0A%7D%0A%0A/**%0A%20*%20This%20should%20handle%20the%20hover%20events%0A%20*%20%0A%20*%20@param%20anchorId%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsHandleHover%28anchorId%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%09%09var%20anchor%3D_leoHighlightsFindElementById%28anchorId%29%3B%0A%20%20%09%09anchor.hover%3Dtrue%3B%0A%20%20%09%09%0A%20%20%20%20%20%20/*%20Report%20the%20hover%20event%20*/%0A%20%20%20%20%20%20leoHighlightsReportEvent%28%22hovered%22%2C%20window.document.domain%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsGetAttrib%28anchor%2C%27leohighlights_keywords%27%29%2Cnull%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsGetAttrib%28anchor%2C%27leohighlights_accept%27%29%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20_leoHighlightsGetAttrib%28anchor%2C%27leohighlights_reject%27%29%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%09leoHighlightsShowPopup%28anchorId%2C0%29%3B%0A%20%20%20%09return%20false%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22leoHighlightsHandleHover%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%09%0A%7D%0A%0A/**%0A%20*%20This%20will%20handle%20the%20mouse%20over%20setup%20timers%20for%20the%20appropriate%20timers%0A%20*%20%0A%20*%20@param%20id%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsHandleMouseOver%28id%29%0A%7B%0A%09try%0A%09%7B%0A%09%09var%20anchor%3D_leoHighlightsFindElementById%28id%29%3B%09%09%0A%0A%09%09/*%20Clear%20the%20end%20timer%20if%20required%20*/%0A%09%09if%28anchor.endTimer%29%0A%09%09%09clearTimeout%28anchor.endTimer%29%3B%0A%09%09anchor.endTimer%3Dnull%3B%0A%09%09%0A%09%09anchor.style.background%3DLEO_HIGHLIGHTS_BACKGROUND_STYLE_HOVER%3B%0A%09%09%0A%09%09/*%20The%20element%20is%20already%20showing%20we%20are%20done%20*/%0A%09%09if%28anchor.shown%29%0A%09%09%09return%3B%0A%09%09%0A%09%09/*%20Setup%20the%20start%20timer%20if%20required%20*/%0A%09%09anchor.startTimer%3DsetTimeout%28function%28%29%7B%0A%09%09%09leoHighlightsHandleHover%28anchor.id%29%3B%0A%09%09%09anchor.hover%3Dtrue%3B%0A%09%09%09%7D%2C%0A%09%09%09LEO_HIGHLIGHTS_SHOW_DELAY_MS%29%3B%0A%09%7D%0A%09catch%28e%29%0A%09%7B%0A%09%09_leoHighlightsReportExeception%28%22leoHighlightsHandleMouseOver%28%29%22%2Ce%29%3B%20%20%20%09%0A%09%7D%0A%7D%0A%0A/**%0A%20*%20This%20will%20handle%20the%20mouse%20over%20setup%20timers%20for%20the%20appropriate%20timers%0A%20*%20%0A%20*%20@param%20id%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsHandleMouseOut%28id%29%0A%7B%0A%09try%0A%09%7B%09%0A%09%09var%20anchor%3D_leoHighlightsFindElementById%28id%29%3B%0A%09%09%0A%09%09/*%20Clear%20the%20start%20timer%20if%20required%20*/%0A%09%09if%28anchor.startTimer%29%0A%09%09%09clearTimeout%28anchor.startTimer%29%3B%0A%09%09anchor.startTimer%3Dnull%3B%0A%09%09%0A%09%09anchor.style.background%3DLEO_HIGHLIGHTS_BACKGROUND_STYLE_DEFAULT%3B%0A%09%09if%28%21anchor.shown||%21anchor.hover%29%0A%09%09%09return%3B%0A%09%09%0A%09%09/*%20Setup%20the%20start%20timer%20if%20required%20*/%0A%09%09anchor.endTimer%3DsetTimeout%28function%28%29%7B%0A%09%09%09leoHighlightsHideElem%28LEO_HIGHLIGHTS_IFRAME_DIV_ID%29%3B%0A%09%09%09anchor.shown%3Dfalse%3B%0A%09%09%09_leoHighlightsPrevElem%3Dnull%3B%0A%09%09%09%7D%2CLEO_HIGHLIGHTS_HIDE_DELAY_MS%29%3B%0A%09%7D%0A%09catch%28e%29%0A%09%7B%0A%09%09_leoHighlightsReportExeception%28%22leoHighlightsHandleMouseOut%28%29%22%2Ce%29%3B%20%20%20%09%0A%09%7D%0A%7D%0A%0A/**%0A%20*%20This%20handles%20the%20mouse%20movement%20into%20the%20currently%20opened%20window.%0A%20*%20Just%20clear%20the%20close%20timer%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsHandleIFrameMouseOver%28%29%0A%7B%0A%09try%0A%09%7B%0A%09%09if%28_leoHighlightsPrevElem%26%26_leoHighlightsPrevElem.endTimer%29%0A%09%09%09clearTimeout%28_leoHighlightsPrevElem.endTimer%29%3B%0A%09%7D%0A%09catch%28e%29%0A%09%7B%0A%09%09_leoHighlightsReportExeception%28%22leoHighlightsHandleIFrameMouseOver%28%29%22%2Ce%29%3B%20%20%20%09%0A%09%7D%0A%7D%0A%0A/**%0A%20*%20This%20handles%20the%20mouse%20movement%20into%20the%20currently%20opened%20window.%0A%20*%20Just%20clear%20the%20close%20timer%0A%20*%20%0A%20*%20@param%20id%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsHandleIFrameMouseOut%28%29%0A%7B%0A%09try%0A%09%7B%0A%09%09if%28_leoHighlightsPrevElem%29%0A%09%09%09leoHighlightsHandleMouseOut%28_leoHighlightsPrevElem.id%29%3B%0A%09%7D%0A%09catch%28e%29%0A%09%7B%0A%09%09_leoHighlightsReportExeception%28%22leoHighlightsHandleIFrameMouseOut%28%29%22%2Ce%29%3B%20%20%20%09%0A%09%7D%0A%7D%0A/**%0A%20*%20This%20is%20a%20method%20is%20used%20to%20make%20the%20javascript%20within%20IE%20runnable%0A%20*/%0Avar%20leoHighlightsRanUpdateDivs%3Dfalse%3B%0Afunction%20leoHighlightsUpdateDivs%28%29%0A%7B%0A%09try%0A%09%7B%0A%09%09/*%20Check%20if%20this%20is%20an%20IE%20browser%20and%20if%20divs%20have%20been%20updated%20already%20*/%0A%09%09if%28document.all%26%26%21leoHighlightsRanUpdateDivs%29%0A%09%09%7B%0A%09%09%09leoHighlightsRanUpdateDivs%3Dtrue%3B%20//%20Set%20early%20to%20prevent%20running%20twice%0A%09%09%09for%28var%20i%3D0%3Bi%3CLEO_HIGHLIGHTS_MAX_HIGHLIGHTS%3Bi++%29%0A%09%09%09%7B%0A%09%09%09%09var%20id%3D%22leoHighlights_Underline_%22+i%3B%0A%09%09%09%09var%20elem%3D_leoHighlightsFindElementById%28id%29%3B%0A%09%09%09%09if%28elem%3D%3Dnull%29%0A%09%09%09%09%09break%3B%0A%09%09%09%09%0A%09%09%09%09if%28%21elem.leoChanged%29%0A%09%09%09%09%7B%0A%09%09%09%09%09elem.leoChanged%3Dtrue%3B%0A%09%09%09%09%0A%09%09%09%09%09/*%20This%20will%20make%20javaScript%20runnable%20*/%09%09%09%09%0A%09%09%09%09%09elem.outerHTML%3Delem.outerHTML%3B%0A%09%09%09%09%7D%0A%09%09%09%7D%0A%09%09%7D%0A%09%7D%0A%09catch%28e%29%0A%09%7B%0A%09%09_leoHighlightsReportExeception%28%22leoHighlightsUpdateDivs%28%29%22%2Ce%29%3B%20%20%20%09%0A%09%7D%0A%7D%0A%0Aif%28document.all%29%0A%09setTimeout%28leoHighlightsUpdateDivs%2C200%29%3B%0A%0A%0A/**%0A%20*%20This%20is%20used%20to%20report%20events%20to%20the%20plugin%0A%20*%20@param%20key%0A%20*%20@param%20domain%0A%20*%20@param%20keywords%0A%20*%20@param%20vendorId%0A%20*%20@param%20accept%0A%20*%20@param%20reject%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsReportEvent%28key%2C%20domain%2Ckeywords%2CvendorId%2Caccept%2Creject%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20var%20gwObj%20%3D%20new%20Gateway%28%29%3B%0A%20%20%20%20%20%20gwObj.addParam%28%22key%22%2Ckey%29%3B%0A%20%20%20%20%20%20if%28domain%21%3Dnull%29%0A%20%20%20%20%20%20%20%20%20gwObj.addParam%28%22domain%22%2Cdomain%29%3B%0A%20%20%20%20%20%20if%28keywords%21%3Dnull%29%0A%20%20%20%20%20%20%20%20%20gwObj.addParam%28%22keywords%22%2Ckeywords%29%3B%0A%20%20%20%20%20%20if%28vendorId%21%3Dnull%29%0A%20%20%20%20%20%20%20%20%20gwObj.addParam%28%22vendorId%22%2CvendorId%29%3B%0A%20%20%20%20%20%20if%28accept%21%3Dnull%29%0A%20%20%20%20%20%20%20%20%20gwObj.addParam%28%22accept%22%2Caccept%29%3B%0A%20%20%20%20%20%20if%28reject%21%3Dnull%29%0A%20%20%20%20%20%20%20%20%20gwObj.addParam%28%22reject%22%2Creject%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20gwObj.callName%28%22LeoHighlightsEvent%22%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHighlights%28%29%22%2Ce%29%3B%20%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20This%20will%20expand%20or%20collapse%20the%20window%20base%20on%20it%20prior%20state%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsToggleSize%28clickId%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%20%20%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHighlightsToggleSize%28%29%20%22+_leoHighlightsPrevElem%29%3B%20%20%20%20%20%20%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Get%20the%20hover%20flag%20and%20change%20the%20status%20*/%0A%20%20%20%20%20%20var%20size%3D_leoHighlightsPrevElem.hover?1%3A0%3B%0A%20%20%20%20%20%20_leoHighlightsSetBottomSize%28size%2CclickId%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHighlightsToggleSize%28%29%22%2Ce%29%3B%20%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20Call%20into%20the%20kvm%20that%20will%20then%20do%20a%20callback%20into%20the%20top%20window%0A%20*%20The%20top%20window%20will%20then%20call%20leoH%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsSetSecondaryWindowUrl%28url%2C%20customerId%2C%20phraseId%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%20%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHighlightsSetSecondaryWindowUrl%28%29%20%22+url%29%3B%20%20%20%20%20%20%20%20%20%20%20%20%0A%20%20%20%20%20%20var%20gwObj%20%3D%20new%20Gateway%28%29%3B%0A%20%20%20%20%20%20gwObj.addParam%28%22url%22%2C%20url%29%3B%0A%20%20%20%20%20%20gwObj.addParam%28%22phraseId%22%2C%20phraseId%29%3B%0A%20%20%20%20%20%20gwObj.addParam%28%22customerId%22%2C%20customerId%29%3B%0A%20%20%20%20%20%20gwObj.callName%28%22LeoHighlightsSetSecondaryWindowUrl%22%29%3B%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHighlightsSetSecondaryWindowUrl%28%29%22%2Ce%29%3B%20%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20Call%20into%20the%20kvm%20that%20will%20then%20do%20a%20callback%20into%20the%20top%20window%0A%20*%20The%20top%20window%20will%20then%20call%20leoH%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsSetSecondaryWindowUrlCallback%28url%2C%20customerId%2C%20phraseId%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%20%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHighlightsSetSecondaryWindowUrlCallback%28%29%20%22+url%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Clear%20the%20hover%20flag%2C%20if%20the%20user%20shows%20this%20at%20full%20size%20*/%0A%20%20%20%20%20%20var%20size%3D_leoHighlightsPrevElem.hover?0%3A1%3B%20%20%20%20%20%20%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHighlightsSetSecondaryWindowUrlCallback%28%29%20%22+_leoHighlightsPrevElem+%22%20--%20%22+_leoHighlightsPrevElem.hover%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Get%20the%20elements%20*/%0A%20%20%20%20%20%20var%20iFrameBottom%3D_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_BOTTOM_ID%29%3B%0A%20%20%20%20%20%20leoHighlightsUpdateUrl%28iFrameBottom%2Csize%2Cnull%2Curl%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHighlightsSetSecondaryWindowUrlCallback%28%29%20%22+url%29%3B%20%20%20%20%20%20%20%20%20%20%20%20%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHighlightsSetSecondaryWindowUrlCallback%28%29%22%2Ce%29%3B%20%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20This%20will%20set%20the%20text%20to%20the%20Top%20%0A%20*%20%0A%20*%20@param%20txt%0A%20*%20@return%0A%20*/%0Afunction%20leoHighlightsSetExpandTxt%28txt%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%20%0A%20%20%20%20%20%20var%20topIFrame%20%3D%20_leoHighlightsFindElementById%28LEO_HIGHLIGHTS_IFRAME_TOP_ID%29%3B%0A%20%20%20%20%20%20if%28topIFrame%3D%3Dnull%29%0A%20%20%20%20%20%20%20%20%20return%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Get%20the%20current%20url%20*/%0A%20%20%20%20%20%20var%20url%3DtopIFrame.src%3B%20%20%20%20%20%20%0A%20%20%20%20%20%20if%28url%3D%3Dnull%29%0A%20%20%20%20%20%20%20%20%20return%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Extract%20the%20previous%20hash%20if%20present%20*/%0A%20%20%20%20%20%20var%20idx%3D-1%3B%20%20%20%20%20%20%0A%20%20%20%20%20%20if%28%28idx%3Durl.indexOf%28%27%23%27%29%29%3E0%29%0A%20%20%20%20%20%20%20%20%20url%3Durl.substring%280%2Cidx%29%3B%0A%0A%20%20%20%20%20%20/*%20Append%20the%20text%20to%20the%20end%20*/%0A%20%20%20%20%20%20url+%3D%22%23%22+encodeURI%28txt%29%3B%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20/*%20Set%20the%20iframe%20with%20the%20new%20url%20that%20contains%20the%20hash%20tag%20*/%0A%20%20%20%20%20%20topIFrame.src%3Durl%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHighlightsSetExpandTxt%28%29%22%2Ce%29%3B%20%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A/*----------------------------------------------------------------------*/%0A/*%20Methods%20provided%20to%20the%20highlight%20providers...%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20*/%0A/*----------------------------------------------------------------------*/%0A%0A/**%0A%20*%20This%20will%20set%20the%20expand%20text%20for%20the%20Top%20window%0A%20*/%0Afunction%20leoHL_SetExpandTxt%28txt%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsDebugLog%28%22leoHL_SetExpandTxt%28%29%20%22+txt%29%3B%20%20%20%20%20%20%20%20%20%20%20%20%0A%20%20%20%20%20%20_leoHighlightsSimpleGwCallBack%28%22LeoHighlightsSetExpandTxt%22%2C%22expandTxt%22%2Ctxt%29%3B%20%20%20%20%20%20%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHL_SetExpandTxt%28%29%22%2Ce%29%3B%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20This%20will%20redirect%20the%20top%20window%20to%20the%20passed%20in%20url%0A%20*%20%0A%20*%20@param%20url%0A%20*%20@param%20parentId%0A%20*%20@return%0A%20*/%0Afunction%20leoHL_RedirectTop%28url%2CparentId%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%20%0A%20%20%20%20%20%20try%7B%0A%20%20%20%20%20%20%20%20%20var%20domain%3D_leoHighlightsGetUrlArg%28window.document.URL%2C%22domain%22%29%0A%20%20%20%20%20%20%20%20%20var%20keywords%3D_leoHighlightsGetUrlArg%28window.document.URL%2C%22keywords%22%29%0A%20%20%20%20%20%20%20%20%20var%20vendorId%3D_leoHighlightsGetUrlArg%28window.document.URL%2C%22vendorId%22%29%0A%20%20%20%20%20%20leoHighlightsReportEvent%28%22clickthrough%22%2C%20domain%2Ckeywords%2C%20vendorId%29%3B%0A%20%20%20%20%20%20%7Dcatch%28e%29%7B%0A%20%20%20%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHL_RedirectTop%28%29%22%2Ce%29%3B%20%20%20%20%0A%20%20%20%20%20%20%7D%0A%20%20%09%09%0A%20%20%20%09_leoHighlightsRedirectTop%28url%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22leoHL_RedirectTop%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20This%20will%20redirect%20the%20top%20window%20to%20the%20passed%20in%20url%0A%20*%20%0A%20*%20@param%20url%0A%20*%20@param%20parentId%0A%20*%20@return%0A%20*/%0Afunction%20LeoHL_RedirectTop%28url%2CparentId%29%0A%7B%0A%20%20%20leoHL_RedirectTop%28url%2CparentId%29%3B%0A%7D%0A%0A/**%0A%20*%20This%20will%20redirect%20the%20top%20window%20to%20the%20passed%20in%20url%0A%20*%20%0A%20*%20@param%20url%0A%20*%20@param%20parentId%0A%20*%20@return%0A%20*/%0Afunction%20leoHL_RedirectTopAd%28url%2CparentId%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%20%0A%20%20%20%20%20%20try%7B%0A%20%20%20%20%20%20%20%20%20var%20domain%3D_leoHighlightsGetUrlArg%28window.document.URL%2C%22domain%22%29%0A%20%20%20%20%20%20%20%20%20var%20keywords%3D_leoHighlightsGetUrlArg%28window.document.URL%2C%22keywords%22%29%0A%20%20%20%20%20%20%20%20%20var%20vendorId%3D_leoHighlightsGetUrlArg%28window.document.URL%2C%22vendorId%22%29%0A%20%20%20%20%20%20leoHighlightsReportEvent%28%22advertisement.click%22%2C%20domain%2Ckeywords%2C%20vendorId%29%3B%0A%20%20%20%20%20%20%7Dcatch%28e%29%7B%0A%20%20%20%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHL_RedirectTopAd%28%29%22%2Ce%29%3B%20%20%20%20%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%0A%20%20%20%20%20%20_leoHighlightsRedirectTop%28url%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHL_RedirectTopAd%28%29%22%2Ce%29%3B%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A%0A/**%0A%20*%20This%20will%20set%20the%20size%20of%20the%20iframe%0A%20*%20%0A%20*%20@param%20url%0A%20*%20@param%20parentId%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20leoHl_setSize%28size%2Curl%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%09/*%20Get%20the%20clickId%20*/%0A%20%20%20%09var%20clickId%3D_leoHighlightsGetUrlArg%28%20url%2C%22clickId%22%29%0A%20%20%20%09%0A%20%20%20%20%20%20var%20gwObj%20%3D%20new%20Gateway%28%29%3B%0A%20%20%20%20%20%20gwObj.addParam%28%22size%22%2Csize%29%3B%0A%20%20%20%20%20%20if%28clickId%29%0A%20%20%20%20%20%20%20%20%20gwObj.addParam%28%22clickId%22%2CclickId+%22_blah%22%29%3B%0A%20%20%20%20%20%20gwObj.callName%28%22LeoHighlightsSetSize%22%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%09_leoHighlightsReportExeception%28%22leoHl_setSize%28%29%22%2Ce%29%3B%20%20%20%09%0A%20%20%20%7D%0A%7D%0A%0A/**%0A%20*%20This%20will%20toggle%20the%20size%20of%20the%20window%0A%20*%20%0A%20*%20@return%0A%20*/%0Afunction%20leoHl_ToggleSize%28%29%0A%7B%0A%20%20%20try%0A%20%20%20%7B%0A%20%20%20%20%20%20var%20gwObj%20%3D%20new%20Gateway%28%29%3B%0A%20%20%20%20%20%20gwObj.callName%28%22LeoHighlightsToggleSize%22%29%3B%0A%20%20%20%7D%0A%20%20%20catch%28e%29%0A%20%20%20%7B%0A%20%20%20%20%20%20_leoHighlightsReportExeception%28%22leoHl_ToggleSize%28%29%22%2Ce%29%3B%20%20%20%20%20%0A%20%20%20%7D%0A%7D%0A%0A");
]]&gt;</script><br />
</span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2010/05/27/2031/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What You Can’t Deny, Delay and Minimize</title>
		<link>http://www.safetyresearch.net/2010/04/15/what-you-can%e2%80%99t-deny-delay-and-minimize/</link>
		<comments>http://www.safetyresearch.net/2010/04/15/what-you-can%e2%80%99t-deny-delay-and-minimize/#comments</comments>
		<pubDate>Thu, 15 Apr 2010 18:12:24 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Accelerator pedal]]></category>
		<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Electronics]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Throttle Body]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[advocacy]]></category>
		<category><![CDATA[Lexus]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=1986</guid>
		<description><![CDATA[A well-used weapon in the manufacturer’s arsenal is delay. When the guys and gals from the Office of Defects Investigation are pestering you with information requests and you have that sinking feeling that you are going to have to do something to get them off your back, the first order of business is to buy [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;">A well-used weapon in the manufacturer’s arsenal is delay. When the guys and gals from the Office of Defects Investigation are pestering you with information requests and you have that sinking feeling that you are going to have to do <em>something</em> to get them off your back, the first order of business is to buy some time. A defect in a component – or worse yet – a design that is integral to just about every model you sell is going to be a major headache. No way are you going to have enough replacement parts to switch out in hundreds of thousands or millions of vehicles all at once. You never want your company name in a headline with the word “million” and “recall,” followed by a news story skewering your product. And then there’s the dollars attached to the labor and parts costs swirling the bowl. Oy.</span></p>
<p><span style="color: #c0c0c0;">If you can just whack that big dog down to puppy size, or drag your feet long enough to ramp up your recall response, maybe it won’t be so bad. Of course, denial that the problem even exists is the top-line defense. As the documents trickling from the hands of federal investigators to the press indicate, Toyota was once a master of the art.<span id="more-1986"></span></span></p>
<p><span style="color: #c0c0c0;">It was proud of its success in managing the National Highway Traffic Safety Administration. Unlike other automakers, it had pulled off the gutsy move of hiring ODI staff directly from the agency. Negotiators who knew ODI from the inside – its culture, its process, its personalities – certainly couldn’t hurt. And up until recently it helped – a lot.</span></p>
<p><span style="color: #c0c0c0;">Toyota considered the management of its relationship to NHTSA a critical element in dodging defect investigations. Toyota’s Washington D.C.-based regulatory team consisted of two former ODI staffers, Chris Tinto, Vice President of Regulatory and Technical Affairs, and his assistant manager Chris Santucci. Both used their institutional experience to minimize the effect of any Office of Defects Investigations on the fortunes of their new employer.</span></p>
<p><span style="color: #c0c0c0;">For example, according to a deposition taken in <em>Alberto v. Toyota</em>, in 2004, during a critical phase of an investigation into SUA in Camry and Lexus vehicles, Christopher Santucci testified that Toyota and ODI had discussions about the scope of PE04021 early on. Later, in March 2004, ODI investigator Scott Yon wrote a memo noting that the scope of the investigation would be narrowed to eliminate longer duration events where applying the brake pedal didn’t stop the vehicle. This definition of SUA wiped away all of the incidents with the most harmful outcomes – injury and death. It also helped make the whole thing go away – PE04021 was closed with no finding</span></p>
<p><span style="color: #c0c0c0;">That delayed action for about three years. But in March 2007, the agency opened Preliminary Evaluation 07016 based on five complaints, three crashes and seven injuries. This investigation focused solely on the role of an unsecured floor mat in Toyota SUA. However, in this investigation, the allegations were more serious. Drivers told ODI that they experienced unwanted acceleration after releasing the accelerator pedal and that subsequent and repeated braking did not stop the vehicle. In some cases, drivers traveled significant distances at high vehicle speeds (greater than 90 mph) before the vehicle stopped. These were exactly the scenarios that the agency tossed out of consideration in PE04021.</span></p>
<p><span style="color: #c0c0c0;">Toyota tried to hit the brakes on this probe by sending out a warning to dealers and customer about the possibility of pedal entrapment.  But the agency bumped up the status to an Engineering Analysis in early August 2007. In a series of internal emails that month, Tinto and Santucci discussed the pressure that NHTSA was putting on the automaker to do something about the floor mat situation. Despite Toyota’s attempt to fend off further action by adding new warning labels, NHTSA was on the verge of issuing a public service announcement:</span></p>
<p><span style="color: #c0c0c0;">“They claim that this remains a serious issue, even subsequent to our mailings to Lexus owners;  They recognize that this is a misuse issue (stacked mats), however, they believe that something about the throttle pedal or floorpan design lends itself to easier jamming than other models produced in the past; they also believe that the Prius, Camry and Avalon may also be prone to being overly sensitive to floor mat jamming and claim to have some evidence of such; they claim that jamming can occur with Toyota mats or aftermarket mats; they claim that the issue is further complicated by the fact that NHTSA believes that customers do not know how to shut off the car when in motion (i.e. hold the start button for 3 seconds). NHTSA said that they feel that this is so important/urgent that they are considering a NHTSA public service announcement, informing the public to insure they install the mats correctly (i.e. proper clip use, and no stacking) as well as how to shut off the vehicle with the push button start,” Santucci wrote in June 2007.</span></p>
<p><span style="color: #c0c0c0;">NHTSA was also suggesting that Toyota install a brake-to-idle override, similar to the feature that Volkswagen had installed in its vehicles and to tweak the ignition button so that pressing the button multiple times would also turn off the engine. Toyota resisted ODI’s suggestions for a more comprehensive fix. Instead, the agency settled for much less. EA07010 was closed two months later, when Toyota initiated a limited floor mat recall campaign. One year later, Toyota executive Yoshimi Inaba boasted in an internal presentation that the company had saved $100 million in limiting the remedy of sudden acceleration in Lexus and Camry vehicles to a 55,000-unit floor mat recall.</span></p>
<p><span style="color: #c0c0c0;">Two weeks ago, NHTSA hit Toyota with the biggest fine it could: $16.4 million for failing to file a defect report on its sticking accelerator pedals within the five days required by regulation. Let’s remind everybody: sticking accelerator pedals have nothing to do with sudden unintended acceleration. One of the documents now available online is a chronology Tinto submitted to ODI showing that Toyota had confirmed the phenomenon of slow return of the accelerator pedal containing PA 46 friction lever in high temperature and humid conditions as early as January 2008. Six months later, “a meeting was held to discuss the phenomenon of Tundra accelerator pedals being slow to return. A decision was made that the phenomenon was not a safety-related issue.”</span></p>
<p><span style="color: #c0c0c0;">In the offing is likely another whopper related to the accelerator defect and, perhaps a third fine related to the floor mat recall – TQ10-001, according to DOT Secretary Ray LaHood’s broad hints. The latter will be interesting, indeed.</span></p>
<p><span style="color: #c0c0c0;">Less than two months after Inaba bragged about saving the company big bucks with a limited floor mat recall, the Saylor family died in an SUA-related crash. From that day forward, Toyota’s SUA problem accelerated out of control. A Consumer Advisory to remove accessory floor mats issued in late September morphed into a recall of 3.8 million vehicles by October 5. On November 25, Toyota rolled out a plan to reconfigure the accelerator pedal on vehicles going back to the 2004 model year, modifying the floor area around the pedal and in <em>some</em></span> models, installing a brake-to-idle override – this fix comes nearly three years after NHTSA informed Toyota that braking in these high-speed SUA events, was, to put it kindly, challenging. On January 27, Toyota added another one million vehicles to the floor mat recall. And, in late March it added the 2008-2010 Highlander Hybrid to the target population.</p>
<p><span style="color: #c0c0c0;">Starting from the first Lexus Sudden Unintended Acceleration investigation in 2003, Toyota bought itself seven years of delay – and counting. We know that errant floor mats, sticky pedals and driver error do not account for many consumers’ experiences. Will seven years of sowing customer discontent, tarnishing the brand, losing NHTSA’s confidence turn out to be worth it? While NHTSA does not have another SUA defect investigation open on Toyota, many well-qualified electronics experts are looking at the ETCS-i to determine what problems may exist in the software, the failsafe logic or the circuitry that could cause these vehicles can go to wide open throttle in a variety of scenarios.</span></p>
<p><span style="color: #c0c0c0;">If someone establishes a SUA root cause before Toyota, delay may turn out to be the more expensive route. (And that’s not even counting the $1 million Edmunds.com is offering to any researcher who can crack the unintended acceleration conundrum.)</span></p>
<p><a href="../2010/04/14/toyota-sudden-unintended-acceleration/">More on Toyota SUA</a></p>
<p><a href="../2010/04/14/toyota-sudden-unintended-acceleration/toyota-sua-real-stories/">Toyota SUA:  Real Stories</a></p>
<p><br class="spacer_" /></p>
<p><br class="spacer_" /></p>
<p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2010/04/15/what-you-can%e2%80%99t-deny-delay-and-minimize/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manufacturing Doubt in Toyota Sudden Unintended Acceleration</title>
		<link>http://www.safetyresearch.net/2010/04/14/manufacturing-doubt-in-toyota-sudden-unintended-acceleration/</link>
		<comments>http://www.safetyresearch.net/2010/04/14/manufacturing-doubt-in-toyota-sudden-unintended-acceleration/#comments</comments>
		<pubDate>Wed, 14 Apr 2010 19:19:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Accelerator pedal]]></category>
		<category><![CDATA[Congressional Hearings]]></category>
		<category><![CDATA[David Michaels]]></category>
		<category><![CDATA[Dr. David Gilbert]]></category>
		<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Exponent]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Throttle Body]]></category>
		<category><![CDATA[Tobacco industry]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[advocacy]]></category>
		<category><![CDATA[Doubt is Their Product]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=1980</guid>
		<description><![CDATA[Doubt is Their Product: How Industry’s Assault on Science Threatens Your Health by David Michaels is on our nightstands right now, and we cannot shake the feeling of déjà vu. Michaels, recently confirmed as the new head of the Occupational Safety and Health Administration and Assistant Secretary of Labor, writes about the attack, deny and [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;"><em>Doubt is Their Product: How Industry’s Assault on Science Threatens Your Health</em> by David Michaels is on our nightstands right now, and we cannot shake the feeling of déjà vu. Michaels, recently confirmed as the new head of the Occupational Safety and Health Administration and Assistant Secretary of Labor, writes about the attack, deny and delay tactics developed by Big Tobacco in the 1950s that have been adopted and refined to a fare-thee-well by countless other industries. Michaels is an epidemiologist, so his dizzying catalogue of bad actors focuses on chemical health hazards – tobacco, chromium, lead, beryllium, and the like.</span></p>
<p><span style="color: #c0c0c0;">But what caught our attention was his exploration of how manufacturers use science – or the appearance thereof &#8211; to raise enough doubt to clog the regulatory machinery and to persuade juries and the public that their products cause no harm by countering scientific studies indicating a hazard with their own bought-and-paid-for-research showing the opposite.<span id="more-1980"></span></span></p>
<p><span style="color: #c0c0c0;">As recently as the late 1990s, tobacco executives were still making public statements denying the link between cigarette smoking and cancer. We can’t help but note a striking resemblance to Toyota’s insistence that its electronics play no part in sudden unintended acceleration in its vehicles, despite numerous instances of drivers battling run-away vehicles with no floor mats and no pedal problems; or vehicle engines that continue to race at wide open throttle while in “Park;” or vehicles that exhibit this behavior right in front of Toyota techs.</span></p>
<p><span style="color: #c0c0c0;">But consistent denial only gets you so far. What Big Tobacco needed &#8211; and got &#8211; was the imprimatur of science to lend legitimacy to the message. Michaels describes “swarms” of consultants and scientists manufacturing “uncertainty by questioning every study, dissecting every method and disputing every conclusion.” This assault on independent research was buttressed by other industry-sponsored studies that show no link between chemicals and disease or no exposure risks.</span></p>
<p><span style="color: #c0c0c0;">Among the product defense firms aiding industry Michaels mentions prominently is Exponent. He describes these companies, thus:</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">“Their business model is straightforward. They profit by helping corporations minimize public health and environmental protection and fight claims of injury and illness. In field after field, year after year, this same handful of individuals and companies comes up again and again. The range of their work is impressive. They have on their payrolls or can bring in on a moment’s notice toxicologists, epidemiologists, biostatisticians, risk assessors the work has one overriding motivation: advocacy for the sponsor’s position in civil court, the court of public opinion and the regulatory arena.”</span></p>
<p><span style="color: #c0c0c0;">In its 2009 Securities and Exchange Commission 10K filing, Exponent acknowledges that it is in the business of providing science in support of litigation:</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">“Many of our engagements are initiated directly with large corporations or by lawyers or insurance companies, whose clients anticipate, or are engaged in, litigation related to their products, equipment or service.”</span></p>
<p><span style="color: #c0c0c0;">Exponent also touts its ability to hustle data in a hurry:</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">“Our multidisciplinary team of scientists, physicians, engineers, business and regulatory consultants brings together more than 90 different technical disciplines to solve complicated issues facing industry and government today. Our professional staff can perform in-depth scientific research and analysis, or very rapid-response evaluations to provide our clients with the critical information they need.”</span></p>
<p><span style="color: #c0c0c0;">By Michaels’ calculations, industry’s need for speed plus a credible defense posture equals this:</span></p>
<p style="padding-left: 30px;"><span style="color: #c0c0c0;">“Exponent’s scientists are prolific writers of scientific reports and papers. While some might exist, I have yet to see an Exponent study that does not support the conclusion needed by the corporation or trade association that is paying the bill.”</span></p>
<p><span style="color: #c0c0c0;">Exponent is a frequent opponent of the plaintiffs’ bar in automotive defect litigation. According to Exponent’s 2009 SEC filing, “transportation industry-related engagements accounted for approximately 14% of our revenues for the fiscal year ended.”</span></p>
<p><span style="color: #c0c0c0;">Exponent entered the Toyota SUA picture in 2010, when Toyota began to lose control of the public perception and the investigative process. From 2003 to 2009, NHTSA accepted Toyota’s claim that its electronic throttle system could not fail without the engine control module taking note, despite chronic consumer petitions for investigations. But when Dr. David Gilbert, an automotive technology professor from Southern Illinois University Carbondale, unveiled at a Congressional hearing the results of preliminary testing that merely challenged the central tenet – that fault will always be detected – that had kept further inquiry at bay, Toyota needed a quick response.</span> <span style="color: #c0c0c0;">(See </span><a href="../2010/04/13/you-don%E2%80%99t-tug-on-superman%E2%80%99s-cape/">You Don’t Tug on Superman’s Cape</a>)</p>
<p><span style="color: #c0c0c0;">This was exactly the sort of situation called for the convergence of science-for-hire and marketing that Michaels describes in <em>Doubt is Their Product</em>. On one front, language attacking Dr. Gilbert’s credibility is being tested in an online survey. (See</span> <a href="../2010/04/12/1960/">Anatomy of a Smear</a><span style="color: #c0c0c0;">). On a second front, Exponent offered a veneer of independent confirmation of Toyota’s electronics system.</span></p>
<p><span style="color: #c0c0c0;">Exponent, Inc., with standard rates of $95 to $800 an hour, and annual revenue in 2008 of $228 million, was given an “unlimited budget,” to delve into Toyota’s electronics. Its first rapid-response report tested Lexus and Toyota vehicles and found: “Exponent has so far been unable to induce, through electrical disturbances to the system, either unintended acceleration or behavior that might be a precursor to such an event, despite concerted efforts toward this goal.” (See</span> <a href="http://www.safetyresearch.net/Library/20100200_TestingAndAnalysis_Exponent.PDF"><em>Testing and Analysis of Toyota and Lexus Vehicles and Components for Concerns Related to Unintended Acceleration</em></a><span style="color: #c0c0c0;">.)</span></p>
<p><span style="color: #c0c0c0;">A second Exponent report, rolled out in an elaborate press conference, more directly confronted Gilbert’s work. It found that the fault Gilbert introduced in the Accelerator Pedal Position Sensor was unlikely to occur: “For such an event to happen in the real world requires a sequence of faults that is extraordinarily unlikely. Furthermore, the individual “faults” required individually are far more likely to result in a detectable problem (for example, setting a trouble code or entering a fail-safe mode of operation), than combining in just the right manner to produce a sudden unintended acceleration (SUA)” Exponent also concluded that it could introduce faults in other manufacturers’ vehicles without a setting a trouble code.” (See</span> <a href="http://www.safetyresearch.net/Library/20100300_EvalOfTheGilbertDemo_Exponent.PDF"><em>Evaluation of the Gilbert Demonstration</em></a> <span style="color: #c0c0c0;">.)</span></p>
<p><span style="color: #c0c0c0;">Electronics experts serving as consultants to the House Committee on Energy and Commerce criticized the first Exponent report, according to a February 22 letter Committee Chair Henry Waxman and Bart Stupak, chairman of the Subcommittee on Oversight and Investigations, sent to Toyota Motor Sales President Jim Lentz. Michael Pecht, a professor of mechanical engineering at the University of Maryland, and director of the University’s Center for Advanced Life Cycle Engineering (CALCE), enumerated a number of deficiencies: a very small sample size, a focus on obvious and simple failures, the lack of a fault tree analysis or a failure modes and effects analysis (FMEA) of the myriad ways SUA could be triggered.  Neil Hannemann, a highly-regarded engineer, told the Committee that the report “does not follow a scientific method” and fails to test “major categories” of potential causes of sudden unintended acceleration, including “electromagnetic interference/Radio frequency interference,” “environmental conditions,” the electronic control module (ECM), and “the software algorithms in the ECM.”</span></p>
<p><span style="color: #c0c0c0;">Why turn over this, what can only be described as quixotic, root cause quest to Exponent? Despite the company’s roster of 643 engineering and scientific staff, could any Exponent engineer know more about Toyota’s electronic throttle control system than its own engineers who not only designed it but wrote the Failure Modes and Effects Analysis that could provide so much insight? The Committee on Energy and Commerce complained that nowhere in the paper blizzard of 75,000 documents provided by the automaker was any indicating that Toyota had comprehensively tested or analyzed any electronic causes of sudden unintended acceleration – except for the Exponent report.</span></p>
<p><span style="color: #c0c0c0;">Perhaps this answer is also found in Michael’s book. In a chapter devoted to the hazards of chromium 6, a carcinogenic dust that is a byproduct of chromium processing, he details how the Chrome Coalition a trade association of chrome producers trying to stave off regulations to lower workers’ exposure limits, hired Chemrisk and Exponent. These outside consultants were introduced to the process through the coalition’s attorneys “so that materials produced by the consultants could be shielded under the attorney’s work product and attorney-client privileges.”</span></p>
<p><span style="color: #c0c0c0;">Another reason to do it this way is because it is remarkably effective. On the field of academic battle, Bowman &amp; Brooke scared SIUC badly enough to shut down Gilbert’s work with Toyota accelerator pedal position sensors. And there isn’t much of a price to be paid in the public relations arena. While Rep. Bart Stupak, D-Mich., chairman of the Energy and Commerce’s Subcommittee on Oversight and Investigation, called the Exponent report “a flawed study conducted by a company retained by Toyota&#8217;s lawyers,” many news outlets reported the results of the Exponent report neutrally, without mentioning Exponent’s strong ties to industry defense litigation. The <em>Wall Street Journal</em>, for example, described Exponent as a “Menlo Park, Calif.-based engineering research firm.”  <em>BusinessWeek</em> characterized it as a company that “provides scientific, medical and engineering consulting services in the U.S., Europe and China.” A few, notably the <em>LA Times</em> and CBS, put the hiring of Exponent into the larger context.</span></p>
<p><span style="color: #c0c0c0;">Manufacturing doubt ain’t cheap, but unlike the products it’s often used to defend, it works!</span></p>
<p><a href="../toyota-sudden-unintended-acceleration/">More on Toyota SUA</a></p>
<p><a href="../toyota-sudden-unintended-acceleration/toyota-sua-real-stories/">Toyota SUA:  Real Stories</a></p>
<p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2010/04/14/manufacturing-doubt-in-toyota-sudden-unintended-acceleration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Looking to the Past:  Why Toyota isn&#8217;t Audi</title>
		<link>http://www.safetyresearch.net/2010/04/09/looking-to-the-past-why-toyota-isnt-audi/</link>
		<comments>http://www.safetyresearch.net/2010/04/09/looking-to-the-past-why-toyota-isnt-audi/#comments</comments>
		<pubDate>Fri, 09 Apr 2010 17:32:13 +0000</pubDate>
		<dc:creator>Sean</dc:creator>
				<category><![CDATA[Accelerator pedal]]></category>
		<category><![CDATA[advocacy]]></category>
		<category><![CDATA[Audi]]></category>
		<category><![CDATA[Congressional Hearings]]></category>
		<category><![CDATA[Electronic Throttle]]></category>
		<category><![CDATA[Electronic Throttle Control]]></category>
		<category><![CDATA[Electronics]]></category>
		<category><![CDATA[Floor Mat Interference]]></category>
		<category><![CDATA[Stuck Throttle]]></category>
		<category><![CDATA[Sudden Unintended Acceleration]]></category>
		<category><![CDATA[Throttle Body]]></category>
		<category><![CDATA[Toyota]]></category>
		<category><![CDATA[Add new tag]]></category>
		<category><![CDATA[NHTSA]]></category>
		<category><![CDATA[Toyota unintended acceleration]]></category>

		<guid isPermaLink="false">http://www.safetyresearch.net/?p=1943</guid>
		<description><![CDATA[You wouldn’t troubleshoot the space shuttle by tinkering under the hood of the Spirit of St. Louis. But a surprising number of observers think that the answer to Toyota’s Sudden Unintended Acceleration problems can be found in the mechanical systems of a quarter century ago. Linking Toyota’s present troubles to those of Audi in the [...]]]></description>
			<content:encoded><![CDATA[<p><span style="color: #c0c0c0;">You wouldn’t troubleshoot the space shuttle by tinkering under the hood of the Spirit of St. Louis. But a surprising number of observers think that the answer to Toyota’s Sudden Unintended Acceleration problems can be found in the mechanical systems of a quarter century ago. Linking Toyota’s present troubles to those of Audi in the mid-1980s is a convenient shibboleth; it may even provide a lesson in corporate crisis management. But to figure out why so many Toyota makes and models across multiple model years are experiencing unintended acceleration in a variety of scenarios, we must resolve to understand modern automotive electronic systems.<span id="more-1943"></span></span></p>
<p><span style="color: #c0c0c0;">The cables and rods that once linked the accelerator to the throttle butterfly began to pass into history in 1988, when BMW introduced the first electronic throttle controls in its 7-Series. Virtually all vehicles produced today employ electronic throttle systems that rely on sensors to relay the driver’s intentions to the engine control module, a computer that controls the opening and closing of the throttle. Like any electronics, these systems can be subject to error – caused by electrical shorts, mis-manufactured microchips or faulty software – and leave no trace. Selling the public on the idea that automotive electronics will always perform perfectly and that acceleration can only be commanded by the driver’s foot or some other mechanical source – such as floor mats – is akin to Microsoft trying to persuade us that every time Windows encounters a problem and closes without explanation, we’ve hit the wrong button.</span></p>
<p><span style="color: #c0c0c0;">The automotive industry has borrowed many of these electronic technologies from aviation, where systems were developed for extremely expensive and sophisticated machines, backed up with multiple redundancies. Automakers have reduced these to the commodity level, where saving a pennies makes a big impact to the bottom line and the temptations to dumb-down a system to trim costs is mighty.</span></p>
<p><span style="color: #c0c0c0;">The industry is well aware of the problems that have been caused by the proliferation of automotive electronics. In 2003, Mercedes removed 600 electronic functions because of quality concerns. Executives at Bosch, a major global supplier declared at a 2004 industry meeting that there was direct correlation between the size of a vehicles’ electronic architecture and the number of defects. Other industry experts have acknowledged that automakers have overloaded vehicles with electronics, without understanding how these systems, which might work well in isolation, operate together.</span></p>
<p><span style="color: #c0c0c0;">The National Highway Traffic Safety Administration is even further behind the curve. Its job is to set minimum safety standards. They do not cover every component – nor should they. Rather, the agency develops performance standards for the safety-critical systems, such as brakes and tires. This is to ensure that manufacturers have the freedom to innovate. But many of these standards were written 40 years ago, and have not kept pace with technological advances.</span></p>
<p><span style="color: #c0c0c0;"> </span></p>
<p><span style="color: #c0c0c0;">The standard governing accelerator controls is a perfect illustration. The original standard was written in 1972 with mechanical throttles in mind. In 1995, the agency proposed revising it to accommodate the new electronic systems. In 2002, NHTSA issued a new draft regulation, but withdrew it in 2004, after Toyota and the Alliance of Automotive opposed the test method. In the absence of regulation, some manufacturers will produce designs that skim safety’s surface, while others set a higher bar for their products. The public needs to know the safety margin behind these sophisticated control systems. It’s past time that NHTSA revisited this issue.</span></p>
<p><span style="color: #c0c0c0;"> </span></p>
<p><span style="color: #c0c0c0;">A vehicle that accelerates in contradiction to the driver’s commands poses an unacceptable safety risk– no matter how rare. It can be so unsettling that some who have experienced a sudden unintended acceleration incident in a Toyota refuse to drive the vehicle ever again.  Toyota, unfortunately, has chosen to attack its critics, as it doubles down on the infallibility of its electronic throttle system. But there’s some hope for the motoring public, now that these systems are being scrutinized in ways that were ignored before the Toyota crisis.</span></p>
<p><span style="color: #c0c0c0;">Identifying intermittent and random errors in an electronic safety system may be difficult, but not impossible. The answers are probably not in a black box. As Toyota has consistently argued in litigation, the crash information captured by its Event Data Recorder is unreliable. (That hasn’t stopped the company from placing the data in heavy media rotation when it appears to point to driver error.)</span></p>
<p><span style="color: #c0c0c0;">Most certainly, the answers don’t lie in the past.</span></p>
<p><span style="color: #c0c0c0;"><span style="color: #000000;"><a href="http://www.safetyresearch.net/toyota-sudden-unintended-acceleration/toyota-sua-real-stories/">Toyota SUA Real Stories</a></span></span></p>
<p><span style="color: #c0c0c0;"><span style="color: #000000;"><a href="http://www.safetyresearch.net/toyota-sudden-unintended-acceleration/">More on Toyota SUA</a><br />
</span></span></p>
<p>
<input id="gwProxy" type="hidden" />
<input id="jsProxy" onclick="jsCall();" type="hidden" /></p>
]]></content:encoded>
			<wfw:commentRss>http://www.safetyresearch.net/2010/04/09/looking-to-the-past-why-toyota-isnt-audi/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

