<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/">
  <title>H2R July 26 &amp; 27</title>
  <link rel="alternate" href="http://trackmaster.trackaroo.com/c/message_boards/find_thread?p_l_id=10581&amp;threadId=24414" />
  <subtitle>H2R July 26 &amp; 27</subtitle>
  <entry>
    <title>RE: H2R July 26 &amp; 27</title>
    <link rel="alternate" href="http://trackmaster.trackaroo.com/c/message_boards/find_message?p_l_id=10581&amp;messageId=24484" />
    <author>
      <name>Alan James Wolfe</name>
    </author>
    <updated>2010-06-30T01:48:54Z</updated>
    <published>2010-06-30T01:48:54Z</published>
    <summary type="html">Yes, I understand the performance of the Eris internal GPS.  I&amp;#039;ve played around with GPS Status and the best error I see is 6 ft using 11 of 12 visible satellites.  That&amp;#039;s with open sky.  I&amp;#039;ve also validated that the current mounting position in the car is the best orientation and position.  It gives an average error of about 19 ft using 7to9 of 9to10 visible satellites.&lt;br /&gt;&lt;br /&gt;I was hoping there might be something you could do through data smoothing.&lt;br /&gt;&lt;br /&gt;Otherwise I am stuck with current performance till HTC fixes their bluetooth stack or I upgrade in 14 months.&lt;br /&gt;&lt;br /&gt;And again, $7 for a lap timer is a great deal.&lt;br /&gt;&lt;br /&gt;Alan&lt;br /&gt;&lt;br /&gt;p.s.  *****   Moved to Suggestions Forum   *******</summary>
    <dc:creator>Alan James Wolfe</dc:creator>
    <dc:date>2010-06-30T01:48:54Z</dc:date>
  </entry>
  <entry>
    <title>RE: H2R July 26 &amp; 27</title>
    <link rel="alternate" href="http://trackmaster.trackaroo.com/c/message_boards/find_message?p_l_id=10581&amp;messageId=24432" />
    <author>
      <name>Jeff Trackaroo</name>
    </author>
    <updated>2010-06-28T22:26:26Z</updated>
    <published>2010-06-28T22:26:26Z</published>
    <summary type="html">If you look at the data in Google Earth, you&amp;#039;ll see the internal phone GPS isn&amp;#039;t doing a very good job and has pretty poor accuracy.  That would explain the high top speeds.  Some phones have better GPS accuracy than others.  The older phones like the Eris, Hero, &amp;amp; Moment seem to have less reliable GPS.  In these situations, I&amp;#039;d recommend mounting the phone in a location that gets a better view of the sky to improve signal &amp;#045; up high and near the windshield.  I&amp;#039;d also recommend using an external bluetooth GPS with Trackmaster.  But unfortunately the Droid Eris does not support that.  &lt;br /&gt;&lt;br /&gt;Jeff</summary>
    <dc:creator>Jeff Trackaroo</dc:creator>
    <dc:date>2010-06-28T22:26:26Z</dc:date>
  </entry>
  <entry>
    <title>RE: H2R July 26 &amp; 27</title>
    <link rel="alternate" href="http://trackmaster.trackaroo.com/c/message_boards/find_message?p_l_id=10581&amp;messageId=24427" />
    <author>
      <name>Alan James Wolfe</name>
    </author>
    <updated>2010-06-28T22:08:31Z</updated>
    <published>2010-06-28T22:08:31Z</published>
    <summary type="html">&lt;div class='quote-title'&gt;Jeff Trackaroo:&lt;/div&gt;&lt;div class='quote'&gt;&lt;div class='quote-content'&gt;Can you also attached the data in Google Earth format?&lt;br /&gt;&lt;br /&gt;Jeff&lt;/div&gt;&lt;/div&gt;&lt;br /&gt;&lt;br /&gt;Here &amp;#039;ya go.</summary>
    <dc:creator>Alan James Wolfe</dc:creator>
    <dc:date>2010-06-28T22:08:31Z</dc:date>
  </entry>
  <entry>
    <title>RE: H2R July 26 &amp; 27</title>
    <link rel="alternate" href="http://trackmaster.trackaroo.com/c/message_boards/find_message?p_l_id=10581&amp;messageId=24422" />
    <author>
      <name>Jeff Trackaroo</name>
    </author>
    <updated>2010-06-28T20:29:00Z</updated>
    <published>2010-06-28T20:29:00Z</published>
    <summary type="html">Can you also attached the data in Google Earth format?&lt;br /&gt;&lt;br /&gt;Jeff</summary>
    <dc:creator>Jeff Trackaroo</dc:creator>
    <dc:date>2010-06-28T20:29:00Z</dc:date>
  </entry>
  <entry>
    <title>H2R July 26 &amp; 27</title>
    <link rel="alternate" href="http://trackmaster.trackaroo.com/c/message_boards/find_message?p_l_id=10581&amp;messageId=24413" />
    <author>
      <name>Alan James Wolfe</name>
    </author>
    <updated>2010-06-28T20:20:09Z</updated>
    <published>2010-06-28T20:20:09Z</published>
    <summary type="html">Jeff,&lt;br /&gt;&lt;br /&gt;Spent this past weekend at Harris Hill Road.  I captured much better data this time &amp;#040;fewer gaps&amp;#041;.  I was running the latest version of Trackmaster, put the phone in Airplane mode, then used ATK to kill all apps except ATK &amp;amp; Trackmaster.&lt;br /&gt;&lt;br /&gt;However, I think you have a bug in how you sort through the data for Top Speed.  There are erronously very high &amp;#040;180 to 200 mph&amp;#041; top speeds given for a lap when true top speed is about 110 mph.   I noticed that almost all these erronously very high top speeds are associated with a very large acceleration, then followed by a large negative acceleration.  See the attached file.&lt;br /&gt;&lt;br /&gt;The lap times and average speeds seem dead on.&lt;br /&gt;&lt;br /&gt;Device is HTC Eris using internal gps.  Mounted in horizontal mode to the right and above center of steering wheel &amp;#045; directly above right hand when at 3 o&amp;#039;clock on the wheel.&lt;br /&gt;&lt;br /&gt;Thanks for the great program!&lt;br /&gt;&lt;br /&gt;Alan</summary>
    <dc:creator>Alan James Wolfe</dc:creator>
    <dc:date>2010-06-28T20:20:09Z</dc:date>
  </entry>
</feed>

