eCtune

Hi I'm using serial wideband input for lc1 and nottest that afr in the tuner live plot graph is different from afr in the display section. I've checked with logworks and the value in the display section (12.93) seems to be the correct one. Am i doing something wrong?

it looks like it could be the graph's code handling the stream... odd.

can you please make a log and send it for me. I asked people numerious time to do that. Nobody did

It works like this: -> SERIAL LOGGING -> GET AFR FROM LC-1 -> AFR->0-5v linear -> Volt-> byte -> Save in log Offcourse I can save afr in the log but that makes it less compatible.. I guess you want raw byte

i'll check now what i see

i'll check now what i see

I'll try to make a datalog when i get out of work. Yesterday i've made a quick test with 2.1r0 and it the afr's from the display matched the live plot. Altough that i'm experiencing problems with the new rom in 2.1r0, at idle i get misfires and can see the rpm jumping in the dial (it's like igniton cut is activated for a very short period of time). I took the car to the highway and most of the time couldn't pass 2000rpm, don't know if it was fuel cut, ignition cut or both the only thing i can tell is that the more i step on the accelerator the more it would die. It was very scary and weird, i had to pull over the car and downgrade ectune to the 2.0r8 to reach my destination. I'll try to simulate in neutral what happened and datalog. I've searched the parameters for any option that could be causing this, but didn't find any.

let me send u a new one later i almost know what the problem is;)

Here are the logs What i found!? The mismatch between afr in display and live plot is solved in 0.0.2.1r0 I've set the output of the lc1 to 1v fixed (no matter the afr) to see if in the datalog file the o2 voltage would be updated with the calculated value (0v-10afr ; 5v 19.9afr). It is not updated, the value stored in the datalog is the real voltage in d14 and not the converted one from the serial logging. Another thing, i havent being tuning my maps \"on the fly\", i mean, i was recording the datalog for tune the maps later when i arrived home. What happened is that this method allied with the problems i'm having with serial logging have result in different \"a/f reading\" tables, the \"a/f reading\" table/values that i obtained after loading the datalog files were substancial different from the real ones. When doing this datalogs, i've nottest that i was running very lean in some regions, 17 and 18 afr (thanks god i've decided to go easy and let the hi cam maps to other time). Now i guess that the problem i've reported about the newest rom, is due to detonation at idle and the lean protection that wasn't let me go +2000rpm. What is your opinion? was this what you had in mind? Regards Filipe Costa

I have noticed also some strange things. The AF reading table is showing wrong numbers. I have mailed Calvin my logs to show him what is going wrong.

i'll check it out again... DOn't use the 52 for now i'll drop u a mail now..

with lean protection u need to convert the voltage to afr for that u need: the correct afr table in settings. for the output connect to d14! e.g. serial doesn't work... select the regular lc-1/lm-1. then do the afr to voltage lookup...

calvin i notice the same type of fuel cut last week when testing on rom 52..

was this with lean protection enabled?

calvin wrote:was this with lean protection enabled?

In my case lean protection was enabled (level 2 only) but i'd swear that i've never touched that parameter.