Originally Posted by Ponycarman
Well, I asked for comment from people using the tweecer.
Not from a competitor not familiar with it.
I've known about it for years and I have heard nothing but good things about it from the 5.0 crowd.
However, I was hoping for some info from people who have used it in our application, not from a pre ODBII 5.0 guy like my coworker.
Contrary to your belief I have used the Tweecer software. It lacks the widesspread parameters and definitions of the SCT software. Not to mention a bunch of stuff that you think is in the Tweecer software is mapped to the wrong place, so you think you're changing something but its not really changing what you want.
The 5.0 crowd has had success with it, the EEC-4s are a much simpler control system. There are also a ton of people using it, alot of trial and error work has already been done, and they know how to make it work. This isn't the case with the V6s and the Tweecer.