<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Tinkering with Progressive TripSense</title>
	<atom:link href="http://s4xton.com/885/tinkering-with-progressive-tripsense/feed/" rel="self" type="application/rss+xml" />
	<link>http://s4xton.com/885/tinkering-with-progressive-tripsense/</link>
	<description>Minneapolis, Minnesota</description>
	<lastBuildDate>Wed, 28 Jul 2010 15:28:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Jacob</title>
		<link>http://s4xton.com/885/tinkering-with-progressive-tripsense/#comment-13473</link>
		<dc:creator>Jacob</dc:creator>
		<pubDate>Fri, 26 May 2006 10:56:40 +0000</pubDate>
		<guid isPermaLink="false">/?p=885#comment-13473</guid>
		<description>I don&#039;t know why the accident caused problems with the TripSense chip, I was just as confused as Progressive was.  They had me ship my old one in and I got a replacement in the mail.  If I looked at the data on the chip, the first 150-200 rows were good, then the rest of the data (about 250,000 lines) all said this:

D1 FF (Corrupt)

Like I said, the accident must have caused an electrical spike that both took out some core computer circuits (doors+locks) and the TripSense chip.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know why the accident caused problems with the TripSense chip, I was just as confused as Progressive was.  They had me ship my old one in and I got a replacement in the mail.  If I looked at the data on the chip, the first 150-200 rows were good, then the rest of the data (about 250,000 lines) all said this:</p>
<p>D1 FF (Corrupt)</p>
<p>Like I said, the accident must have caused an electrical spike that both took out some core computer circuits (doors+locks) and the TripSense chip.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://s4xton.com/885/tinkering-with-progressive-tripsense/#comment-6756</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Mon, 24 Apr 2006 13:27:31 +0000</pubDate>
		<guid isPermaLink="false">/?p=885#comment-6756</guid>
		<description>Jacob - why do you suspect accident caused problems with data on tripsensor?  call me at 440-395-0285 to discuss.  I work on TripSense project at Progressive.  thanks.</description>
		<content:encoded><![CDATA[<p>Jacob &#8211; why do you suspect accident caused problems with data on tripsensor?  call me at 440-395-0285 to discuss.  I work on TripSense project at Progressive.  thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob</title>
		<link>http://s4xton.com/885/tinkering-with-progressive-tripsense/#comment-6755</link>
		<dc:creator>Jacob</dc:creator>
		<pubDate>Mon, 24 Apr 2006 12:49:54 +0000</pubDate>
		<guid isPermaLink="false">/?p=885#comment-6755</guid>
		<description>Been using TripSense since early 2004 (when it was in early testing) and have since saved lots of moola with it.  Got as high as 18% off in my spring 2005 renewal.

Was in an accident in Nov 2005 (t-boned in downtown Mpls), and the crash caused a short circuit in some of the car&#039;s computer circuits, namely the ones that control the door locks and window controls.  As a side effect, it also took out all the data on my TripSense chip.  So I guess that kind of throws out the whole mathmatical reasoning behind these things, which is to calculate what kind of drivers get in the most accidents!</description>
		<content:encoded><![CDATA[<p>Been using TripSense since early 2004 (when it was in early testing) and have since saved lots of moola with it.  Got as high as 18% off in my spring 2005 renewal.</p>
<p>Was in an accident in Nov 2005 (t-boned in downtown Mpls), and the crash caused a short circuit in some of the car&#8217;s computer circuits, namely the ones that control the door locks and window controls.  As a side effect, it also took out all the data on my TripSense chip.  So I guess that kind of throws out the whole mathmatical reasoning behind these things, which is to calculate what kind of drivers get in the most accidents!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
