The Auto Tune tests...
I almost forgot - the Auto Tune was connected to the PC V and the CO values were purposely set incorrectly. The Auto Tune was told to go to a certain afr.
That was quite enlightening. It was clear that there are safe guards in place so 'bad' (truly out range/weird) afr targets would not be attempted. It was also of interest to note that it would take much time to generate a map using auto tune - a few seconds at an rpm/throttle position at least. Because we did not have a lot of time a complete map was not attempted.... but every time the throttle was turned in a stable fashion it would alter the map as we told it to do.
One thing seems clear - the better the base map, the better things will be for the end user and because the Auto Tune will have less work to do and will generate the optimal map faster.
I almost forgot - the Auto Tune was connected to the PC V and the CO values were purposely set incorrectly. The Auto Tune was told to go to a certain afr.
That was quite enlightening. It was clear that there are safe guards in place so 'bad' (truly out range/weird) afr targets would not be attempted. It was also of interest to note that it would take much time to generate a map using auto tune - a few seconds at an rpm/throttle position at least. Because we did not have a lot of time a complete map was not attempted.... but every time the throttle was turned in a stable fashion it would alter the map as we told it to do.
One thing seems clear - the better the base map, the better things will be for the end user and because the Auto Tune will have less work to do and will generate the optimal map faster.