Cannot get Innovate LC-2 to run closed loop in kpro 4
Posted: Tue Apr 05, 2016 5:49 pm
To start off, i have Kpro V4, 2002 Civic EX D17a2 Built and turbo, cammed etc. Running the innovate lc-2 wideband wired up exactly as intructed and grounded to the analog ground.
Version 4.2.4.0
Ive come across things saying you cant use "custom" under analog inputs to run closed loop, and ive also seen where people say the LC-1 conversion is not right.
I have to go to the sensors tab, to A/F and choose lambda there while having "custom" chosen with correct inputs given by innovate to get it to match what my gauge says. If i do not have "lambda" selected, it reads 200.61 or around in that area.
If i choose the LC-1 conversion under analog input tab, itll say 40.01 when the gauge says 18.0 and so on. Makes absolutely no sense and im completely lost.
And it almost acts like the computer is looking for lambda because it tends to dump a bunch of fuel if i enable closed loop and itll make my AFRs 10:1 or 9.5:1. But like i said above, if lambda isnt selected under the sensors tab, its not even in the ballpark
I previously had the AEM 30-4100 wideband, i chose that conversion and everything worked flawlessly.
Another thing, is having the Live Tuning button checked on tables causing it not to go into closed loop?
All the settings as far as min and max adjustment are basically as given in the basemap. -27% and 47%
With the aem, i didnt have to change anything
Version 4.2.4.0
Ive come across things saying you cant use "custom" under analog inputs to run closed loop, and ive also seen where people say the LC-1 conversion is not right.
I have to go to the sensors tab, to A/F and choose lambda there while having "custom" chosen with correct inputs given by innovate to get it to match what my gauge says. If i do not have "lambda" selected, it reads 200.61 or around in that area.
If i choose the LC-1 conversion under analog input tab, itll say 40.01 when the gauge says 18.0 and so on. Makes absolutely no sense and im completely lost.
And it almost acts like the computer is looking for lambda because it tends to dump a bunch of fuel if i enable closed loop and itll make my AFRs 10:1 or 9.5:1. But like i said above, if lambda isnt selected under the sensors tab, its not even in the ballpark
I previously had the AEM 30-4100 wideband, i chose that conversion and everything worked flawlessly.
Another thing, is having the Live Tuning button checked on tables causing it not to go into closed loop?
All the settings as far as min and max adjustment are basically as given in the basemap. -27% and 47%
With the aem, i didnt have to change anything