for crome j12 needs to be cut to datalog, don't know about ecucontrol.

 

ECUControl uses the same serial interrupt handler to datalog as Crome... all the same PGMFI open source code. Therefore, Crome and ECUControl both require J12 to be cut.

Uberdata has a different handler, and doesn't require J12 to be cut.

Guy who says it works both ways: No it doesn't. It's physically impossible. You're getting fucked off readings if you think it "works".

 

mine definintly works right both ways and the readings are dead on to what they are in uber, but when datalogging with ecu control i have only tried it using the standalone with it set on the uber rom setting(which is i guess why it works fine). It probably wouldn't work if i tried using crome.

 

Oh ya, (DUH!) I forgot he had those different settings for the different ECUs... It's been a long while since I've looked at ECUControl. MY apologies to you mshue..

 

is there any advantage to datalogging the way crome and ec does it?

 

no problem