http://www.tpsperformance.com/blog/2009/01/181/ Faster cars, great service Mon, 09 Nov 2009 19:23:30 -0700 http://wordpress.org/?v=2.8.6 hourly 1 http://www.tpsperformance.com/blog/2009/01/181/comment-page-1/#comment-16 Dat Mon, 26 Jan 2009 21:09:06 +0000 http://www.tpsperformance.com/blog/?p=181#comment-16 im sold already im sold already

]]> http://www.tpsperformance.com/blog/2009/01/181/comment-page-1/#comment-10 Wes Sat, 24 Jan 2009 14:57:24 +0000 http://www.tpsperformance.com/blog/?p=181#comment-10 Pretty cool - Andy's Fox (the guy above) was the guinea pig for the first Quarterhorse. I'll be trying out BE/QH on a car this morning! Pretty cool – Andy’s Fox (the guy above) was the guinea pig for the first Quarterhorse. I’ll be trying out BE/QH on a car this morning!

]]> http://www.tpsperformance.com/blog/2009/01/181/comment-page-1/#comment-9 cgrey8 Sat, 24 Jan 2009 14:48:09 +0000 http://www.tpsperformance.com/blog/?p=181#comment-9 I just got mine yesterday too. Clint, the developer of BinaryEditor, got his yesterday as well. He's working on getting it ready for beta testing. Once it's ready, I'll be beating it up with all sorts of tests that I never could do with the TwEECer RT...for instance running my GUFB-based tune on an A9P (GUF1 EEC). It'll be interesting to see how different the tune behavior is between the TwEECer and the QH, to say nothing of the enhanced datalogging ability & lower EEC processor overhead as compared to the TwEECer. But mostly, I'm excited to be able to make tune changes (small or large) on the fly with the engine running without creating so much as a hiccup during the update. In fact, the only thing the QH lacks is the ability to hold multiple tunes and flip between them. But I think that is on the to-do list for Craig to figure out. I just got mine yesterday too. Clint, the developer of BinaryEditor, got his yesterday as well. He’s working on getting it ready for beta testing. Once it’s ready, I’ll be beating it up with all sorts of tests that I never could do with the TwEECer RT…for instance running my GUFB-based tune on an A9P (GUF1 EEC). It’ll be interesting to see how different the tune behavior is between the TwEECer and the QH, to say nothing of the enhanced datalogging ability & lower EEC processor overhead as compared to the TwEECer. But mostly, I’m excited to be able to make tune changes (small or large) on the fly with the engine running without creating so much as a hiccup during the update. In fact, the only thing the QH lacks is the ability to hold multiple tunes and flip between them. But I think that is on the to-do list for Craig to figure out.

]]> http://www.tpsperformance.com/blog/2009/01/181/comment-page-1/#comment-8 andy Fri, 23 Jan 2009 22:35:50 +0000 http://www.tpsperformance.com/blog/?p=181#comment-8 i cant wait to get mine! i cant wait to get mine!

]]>