EFIDynoTuning Forum

I posted about what I believe is a non-functioning dashpot algorithm in my current (older) A9L2 based tune on https://eectuning.org/forums/viewtopic. ... 3f405815a8 and forgot this forum probably gets more traffic these days.

I have disabled and enabled the dashpot functions by zeroing them out and the datalogs show that it's not adhering to the changes I'm making at all. The base tune, based on the dates I can see in my revision history, appears to be mid-2016 timeframe. I may have screwed things up by mixing Binary Editor with Tunerpro RT, but am hoping someone can confirm what I may or may not be doing correctly. The reason for using BE is that my QH is not installed, but a TwEECer RT is - unfortunately, many of the adjustments I've made were made via BE as well. Since so much patching has been done on the A9L2 base tune, could that account for why making changes to the dashpot functions doesn't work when made from BE, even with this older circa-2016 base tune?

Tune and log attached. The main indicators are that the ISC DC moves very slowly and is basically not reacting to idle fluctuations at all and the dashpot doesn't track the RPM either. Thanks.

why bother?

just snatch the latest a9l2 and tunerpro. Use tunerpro to edit the file and either BE or caledit to write it to the tweecer.

neither caledit nor BE have my gufx strategy so none of the dashpot functions will be accessible.

Ok, thanks for confirming why dashpot adjustments in BE don't work LOL

It's taking me several days to transfer my older A9L2 tune over to the new one, but it's in progress...

I finally managed to transfer the tune and got it running on the first try.

What I'm seeing is that DASMIN is gone and replaced with a function (nice) and FN882 (pre-position) has been replaced with a higher resolution table. I think your stock pre-position values work fine for me as does the DASMIN replacement function, but the decay rate needs tuning. FN879 appears to be the decay rate function and intact from OE implementation, is that right?

yep

I made some changes, but ran into a snafu with the cranking fuel PW. There's some kind of patch issue with my tune, where TunerPro was complaining about some business, but it eventually saved the bin file after I closed several editors. Regardless, car won't start now. Commanding far too rich a fuel PW based on the fuel vapor I could see and smell out of the exchaust. I'll attach my tune in the hope that you might be able to see what may be wrong - it may have something do with FNCRKMUL_FAR. I've got the Deka 80# injectors.

holy shit you have completely destroyed that tune file

theres no fixing that

you need to forget everything you think you know and start reading the write ups from the top of the list on down

No man, it fired up and ran perfectly after I updated the tune using the latest A9L2_220405.bin, but after I clicked on some patch stuff for the FNCRKMUL_FAR, it all went to crap. I've driven over 15,000 miles on my old tune with pretty good fuel efficiency and power at full boost. Can you tell if the application of the patch has corrupted major sections of the new bin file?

Ok, so it appears to be an issue with the patch to apply FNCRKMUL_FAR - this corrupted my tune. I've attached my edited bin file that runs perfectly fine now - I had to edit the supposedly deprecated FN306 function.