Thread: Cobb vs UpRev
View Single Post
Old 08-24-2009, 03:56 PM   #136 (permalink)
1slow370
A True Z Fanatic
 
1slow370's Avatar
 
Join Date: Aug 2009
Location: In the D
Posts: 3,732
Drives: v8 74 260z ;)
Rep Power: 7251
1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute1slow370 has a reputation beyond repute
Default

Even IF it doesn't apply to uprev that is how the cobb unit works. I do believe that the Uprev program is actually still based on the original code in the ecu. They most likely are adding/altering to it in order to do what they want to do. All reflashes basically do the same things, change air, fuel tables, recalibrate MAF, change timing, remove limiters, change injector size, and turn off trouble codes.
Car ecu's acomplish incredible amounts of data handling not because they have super beefy processors but because they are simple. You can't load windows on them. I have used programs that support realtime changes while the engine is running on ecu's made back in 1980. You don't need a whole new OS to switch maps the chip in the ecu happens to be big enough to hold 5 maps and probably supports 5 different refferance signals. We used to use an adapter like a ZIF socket that could switch the refferance signal and change maps. I give uprev credit that there is some real work put into using the cruise control as the switch.

Last edited by 1slow370; 08-28-2009 at 04:15 AM.
1slow370 is offline   Reply With Quote