Thread: Cobb vs UpRev
View Single Post
Old 08-22-2009, 09:12 AM   #128 (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

Cobb exists for the 370, Uprev does not. Also UpRev "will be released shorty we're just finishing some things up" since early june and they've acquired a car to work with months ago. I can't see a reason why they didn't release it for the 370 yet other than they can't get something big to work on the 370(I don't care about the 350z results as it's a totally different car). Especialy since they could label it beta, collect input on the issues from users, and release a software update for it later. If the missing map switching light is the hold up It's a foolish mistake to not release it without that capability and get your product to market if it functions fine otherwise. I have hands on experience in tunning cars from hexidecimal bin code back since OBD I, and i understand that the major factors involved in making tunning software are: the connection with the ecm and control software, creating a program to physically read/write that control software/building a GUI to work from, and reverse engineering the factory software so a vehicle definition that says where certian data/maps are in the code and how to change the values in those maps/flags can be created. This concept is shared by virtually every ecu tunning program ever made since in the end you aren't changing any of the vehicles circuitry and the vast majority of the code in the ecm is not altered at all, only the values you want to change to affect how the engine runs. This is how Cobb does it and probably how UpRev does it on other vehicles. The only alternatives are piggybacks which go in between the ecu and the devices it controls and alters the end signal like a sound system amplifier, stand alones which offer there own processors and circuitry to completely ignore the factory ecu and can do w/e the company wants it to do but rarely work with the integrated systems like the electronic dash and focus only on the motor. The generic nature of piggybacks and stand-alones is why we turn to altering the factory code via Cobb and UpRev. The problem with this is that often the companies making the software to alter the factory code can't account for changes in hardware beyond what is done already by nissan. Nissan writes a value for injector size into the code so you can change it. If nissan's electronics don't accept a MAP or BARO sensor you can't add one or sometimes change the size of the one on the car. Does UpRev reprogram the way the ecu reads the voltage from the sensor, or change the scale of the tables to go from 1bar to being able to actually read pressure? This is what defines a tunning programs power, ADAPTABILITY AND FEATURES. Map switching with the cruise control is something Cobb doesn't have, Cobb doesn't require you to have a laptop to run their software UpRev does. In the end if the values the programs change are the same it comes down to cost. If UpRev lets me switch to speed density and lets the car actually adjust for FI, I'll buy it. Otherwise both options are the same except for map switching, and laptop requirments and will do the EXACT SAME THING.

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