Crome Pro is worth purchasing if you are going to tune a number of cars. For one car, not worth the $150. The datalogging isn't that spectacular and autotune is a joke. You are better off spending the $150 on an ostrich and using Freelog as your datalogging program. If you are planning on tuning a couple of cars or more, by all means spend the money on Crome Pro. As for the stance of supporting John Cui, thats a weak stance at best. Look at the scripts you use on a daily basis and then open the .cpf files in notepad. Look at the names listed under author. Now understand that none of the people other than John Cui are getting a cent of that $150 even though without their contributions you'd never spend $150 for the program.

 

^^ I agree. I just knew someone was gonna mention the scripts support .
Im sure John has put in some long long hrs on this, and to have a pay off at the end of it, isnt a negative. The fact that he offers a fully functional, and non-dlogging version is pretty baddass.
Yes I am aware of all the other hard-core mother ******* on PGMFI.
I retract the J. Cui reason for paying for CROME Pro.


I made a nice Excel graph from one of my dyno runs, dyno vs Dlog (A/F, RPM). On 3rd gear pulls, 300ish hp, the lag was a consistent 4-500rpms once the power came in. This was tail pipe sniffer, vs WB in the DP.
Also, I have noticed on 3 diff. Dynojets, that the Sniffer reads anywhere from .5-1.0 leaner than various DP mounted WB's Ive used.

 

i am using a widebade not the sniffer, the guys that have the dyno are friends of mine and they are getting in the tuning bussiness. they tuned my car and i posted that not to long ago and im goin back sunday hopefully. but back to the ? so the datalogging is really nice huh. i kinda understand sensor lag but if im using a wideband in my secondary o2 sensor spot and read off that then there is no lag. i guess i quite dont understand it. they will be tuning multiple cars on the dyno.