180sx wrote:edub what problems you having with ec3 so far? works well for me displays correct timing in datascan and launch works awsome. You need to get consult and stanza ecu already dude, life will be much easier.How do i know that scale reflects the ait sensor? haha read map description in romedit . It tells you which additional map is which, like there is coolant temp vs timing .closed tps/decel timing map. and there is iat temp vs timing. Also when you use ostrich u make changes like in standalone ecu takes a split second for ecu to see updated value, and you see resaults asap. So when i go into the ait scale and start +/- 2-5deg corrections i can see the resaults on datascan as well as you can tell how motor runs with respect to timing. Changing timing affect s fueling mildly all together.And by changing iat scale i ididn't see any change on wideband.
Modified by 180sx at 11:19 PM 3/14/2007
I had EC3 hooked up but had major problems below 2500 RPMs - and I'm not the only one. Strange, perhaps I'll give it another go with my new tune and my narrow band installed.
Anyway, the EC3 is experimental and might not be correct. All we can be certain of at this point is that the changes made to that map show up on Consult. If we assume that consult is actually showing timing and that the map is correctly labeled you are correct about it affecting timing. But this still does not demonstrate that fuel is not also affected - and there are two assumptions.
I spoke to a chief engineer in the field and he explained that these things are designed by entire departments of PhDs and that many functions use numerous layers of maps that can even be multi-dimentional. It's tough to be 100% on anything at this stage in the game.
I could have sworn I saw an explaination of the AIT somewhere but regardless, it should go in the original position to ensure original functionality.
If you have Consult and a wideband try to monkey with the sensor output to simulate hot Vs cold conditions and see what happens - that is a 100% test.