How's the tuning coming on the shop car?

 

Thanks for addressing this speculation and setting the record straight about your experiences with ECUs that were too slow.

I wish people would stop posting pointed comments about things they don't know about.

 

He pulled his own plugs, so he should have taken it to his tuner and had it checked out... he declined. If the sensor is bouncing around it within it's range, the computer doesn't know it's bad. The poor running condition certain lit the bulb on the dash...not sure about the one in his head!

 

Wow...you REALLY don't know anything about computers...do you? As SP stated... we aren't running graphics cards here. The processor inside the ecu is the primary indicator on how quickly it can sample data and process it. Do the math on runnning through EVERY piece of code (which is what any ecu that has to go through calibratable timing pattern setups) at even 10 to 12k rpm. You run out of time fast. I won't even get into foreground frequency rates, and background frequency rates. The processor speed is HOW QUICKLY it looks at the data. MHZ is a measure of time frequency...the slower it is....THE SLOWER IT IS!

 

not true... if the pro-efi has more coding and more checks and balances like you guys say.. it will require a faster processor to do something another ECU doesn't need to do..

so in reality.. the pro-efi needs a faster processor if its doing more functions..

its just like Linux in terminal mode will run 10 times faster than GUI Mode even though its the same processor.. same exact machine

 

What was the name of this thread again...oh yeah. "what ems do you prefer?"

WOW...talking about gigabytes and memory and CPU speed...BLAH, BLAH, BLAH
What happened to driveability, acceleration, throttle response and stuff like that....

Funny how nobody picked about the UTEC down to bytes and processor speed. Because no one cares. Well not me anyhow...

I would love to see more feedback from actual users on VPRO, PROEFI, HALTECH and MOTEC. Try to have adult interactions about performance features and advancements that one may have over another...

Any chance this can get back on topic??? Coulda, woulda, shoulda been a useful thread.

 

Real world experience for me is still somewhat limited, but I do have some positive feedback on the Pro-EFI. As you know, I have an Auto tranny. Originally, when driving the car in full auto mode, the computer would shift a bit too late when I went WOT. This is because the car revs a lot faster than stock. Jason told me the Pro-EFI would learn the timing for each gear shift and compensate for that appropriately. It is now very smooth shifting from 1-2, 2-3, and 3-4. I haven't had much opportunity to shift 4-5 (that would be well over 100 MPH!).

Here is a quick video, it also shows 2 cold starts. The WOT auto shift is around 1:12 in the video.
http://www.youtube.com/watch?v=sVAv6k3RyrE

The car drives smooth as can be on the street. Smooth as stock on shifts (even though it is a higher shift point around 7000RPM or so). Smooth as stock on low boost racing. The torque converter is problematic on high boost, so no idea on how it drives w/22 PSI yet.

 

^ you sure that video is 14 PSI?

 

Yes, why do you ask?

 

looks slowish

 

Marshall, was that Shar in his Powerlab Turbo Z?

 

I was thinking the same thing.

 

Ding Ding Ding! We ran a few times. It was a blast.

 

Yeah, it's pretty slow. Only 524 WHP. It barely creeps along.

Tomorrow I'll be at Firebird, which is a slow track, but I'll post results.

 

The secret is to watch the guys in the far lane... they always try to prep it for the guys that are in the single digits. At least from what I remember.

 

sorry to hear that man

 

race your rsx

 

you don't want none of this DJ Boy.. i already had two challengers back down from me on this forum already.. i'm eating Z's/G's left and right without even turning my key.. its amazing

 

 

Christ, didn't I say don't bring it up again? lol.

You are quite sure of yourself, aren't you? How old are you son and where did you go to school? I did pretty well in my VLSI design and microprocessor architecture classes as an undergrad in one of best engineering colleges in this fine country. There are at least two key points that you need to understand. Let me put it in simple terms:

1. A CPU will execute more than operation per clock cycle. ALL CPUs, even the stupidly simple one I designed, fab'd and had built for a class project using a PGA. A CPU that executes 10 ops during 1 cycle running at 1 Mhz will be faster than a CPU executing 5 ops during 1 cycle running at 5 Mhz. It's called parallelism and it's just the tip of the iceberg in detailing how CPUs running at the same frequency can differ vastly in performance. Forget bus width, bus speeds, memory speeds, latency, multiple processors, RISC vs CISC design, etc.

2. A CPU's raw performance will not compensate for poorly optimized code. And optimizing code in machine language with today's microprocessors is not a trivial task. Most compilers for OEM products are a far cry from truly optimized and if Jason is writing machine code himself for various features in the ProEFI then actual throughput will depend on his skills, and the effort he puts into perfecting that code.

If you're this confident about something that you're dead wrong about, then I really worry about your claims about the ProEFI.