joppez wrote:
OK. Datalogging works fine but afr shows 0.0 i have now innovate simulating to narrow band. I try next with innovate coded to output wideband voltage. Im trying to use romulator with imb serial to usb converter but it gives me this message:
http://jolpa.1g.fi/kuvat/civic/kuvia/tuning/Turboedit/TEromulatorVista.jpgi cant see the picture at work, so i will check when i get home...
joppez wrote:
Im using now turboedit plugin ecucontrol and map readings is correct now. I used chip to run the car and ecucontrol shows ign advance is 27 at idle, how does it count it? Can i trust it? I thought it reads only turboedit map to show ign advance but map has only 18 deg:s or something and it wasnt even connected (chip in ecu)
the ignition advance is not 100% correct...its just reading off teh map in TE. once i get ng62 out, i will work on ng63 and try to add some more logging points, like real fuel value and real timing values.
joppez wrote:
Maybe next time i go with older laptop with serial and xp so it should be easier, allso trying to get that innovate give right voltage so i can try autotune. I see autotune map is only for stock map sensor and it has columns only 12psi? I know autotune should be not use to boost and high rpm but just wanna know sure it doesnt affect at vacuum map because of those stock map columns.
there should be no issue with serial to usb...thats what i use. the autotune map should be the exact same size as your map in TE. if your using innovate, you can do the following:
connect the brown wideband output wire to your disconnected nbo2 input...then select the innovate sensor in ecucontrol and copy in your settings from lmprogrammer (volts vs afr). or you can just connect your innovate serial connector (using serial to usb converter if needed) and set the o2 setting to narrowband with innovate channel, then connect to the innovate port and log digitally into ecucontrol.
joppez wrote:
Oh and i tryed to run romulator with several different port and baud settings, mostly it doesnt even found but this baud it gives that error.
im not sure why some people have trouble getting this to work...it seems like i need to slow the timer down on the connection trys. apparently some ostriches take upwards of 30-40 seconds to connect and TE will time out well before that.