Nistune Forums

However most laptops these days are win7 so they must be supported. Doing driver update package atm along with crash investigation which occurs on these os pn disconnect. Main issue is visual studio 6 is not supported in vista/win7. If I upgrade to vs 2010 then all pcs using nistune must run .net 2...

HTrang wrote:PS: When I tried to recirc my BOV by blocking it off the car still dies when I let off the gas too fast.

Wouldn't that just cause the pressurized air to surge back through the turbo and be metered again?

I've been using Nistune with my netbook running Windows 7 Pro without any problems.

Thanks Matt,
0.9.12 fixed the issue!

I'll give it a whirl here in a little bit and let you know the results.

Thanks

I just updated Nistune to the 0.9.13b release, and when I click on WB O2 LH it crashes to the desktop right as soon as it displays the AFR window showing 0.0. I uninstalled that version, re-installed 0.9.8 which was working fine before the 13b update, and it's still crashing. I tested the wideband w...

I think the U13 is impacted as well, i'll be able to confirm in a few hours.

On my U13 it also uses 128 for 14.7, the O key doesn't do anything.

Sounds like an Injector Latency issue. ( I don't know if the CA18 ECU has a latency... ) If there is a table for it, try lowering it.

just to rephrase so the engine has to be actually running in order for nistune and aem wideband could communicate? if not, im still having an issue connecting it using the program you provided and the settings given in the AEM documentation. Is it possible the wiring may be incorrect? You shouldn't...

Matt wrote:if you can get the exact error message for the Innovate I can hunt that one down... but I think I know what it is

The exact error message is: "Innovate cannot find configured port COM0" - "Cannot connect to Innovate wideband"

New version works great. The only thing is when I connect the LC-1, I get a msgbox saying couldn't connect to Innovate, but once I click Ok, it connects without a hitch... I can get a screen shot or a debug log if needed.

I'm having the same issue. I'm using a fairly old version from 2008 that was the latest one I have that displayed everything correctly.

What wideband are you running?

Still is doing it... It almost appears that it was logging lambda * 10 instead of logging the AFR... I'll play a bit with it and see if I can't get it to work properly. I'll try a few old versions I have downloaded and see if any of those will work better for me.