Hey ziad!

96532706 works great. I've just finished tuning my USDM 8 for cams, turbo, FMIC and injector upgrades. The live map changes to WGDC, fuel and ignition halved the time it takes me normally for a complete MAF based re-tune.

*Suggested addition to your documentation for completeness* - I had to make changes to the Tephra map vectors in the patched ROM. These need to be pointed at RAM otherwise changes made in LiveMap do not get written when you click Write to RAM. (see the pic below) It's not obvious for anyone using this for the first time.

I also want to test the Auto-Tune feature but I'm leery about trying it at WOT because I don't understand what is going on when you start it. My understanding is that it only works at 100% TPS - is that correct? What is the auto-tune routine comparing? Is it the logged WBO2 reading to the target map? (I've got my ZT3 analog output wired into the rear O2 ADC input on the ECU and log WBO2). How does the original map come in to the calculation? Finally, where are the calcualated AFR adjustments written when you run auto-tune?

Sorry for all the questions but I think this feature is potentially one of your best.

Carl

 

edit: nvm

 

Carl those should be patched when you use my program to patch your file. I am very happy you found the program useful.
Auto tune, p is currently in orphan mode it works butI am not to confident o its performance. Acidtonic is supposed to help me on that but he is very busy

With workI have been extremely busy, which is good butI have had no time to do anydevelopment work. I did some work on moving injector latency, maf anmivec...but the testers haven't gotten back to me andI have been very busy

Auto tune, logsthe are and the duringa pull and then wil values, run it three times and doa physical test...should be write close

 

deleted post

 

shees the tablet pyping makes me sound drunk

anyway auto tune, loads ur map from the fuel table, so could be a map u copied there or one read from the ram. then it works by logging a "pull" i think tps is lower than 100%. once a pull is done and completed. it will basically do like a map trace and workout if the average logged AFR is above or below what was expected. if its lower it will raise AFR in the table and vice versa once the process is finished it writes the new map to ram. i have put in max and min that each table will change by. so if u had a fault mechanically and in 5000rpm 300load logged AFRs were 20:1, the program will only decrease the map value by a certain level (1 or 1.5 AFR point). this limits the program going crazy values.

and fadde u r not a tester yet... been too busy to send u ur test rom.

 

HI Ziad

Could this auto tune be used to auto scale and set the VE table for SD?

Andy

 

Good question Andy...at the moment no but I have been thinking of changing the way the program does a few things fundamentally. I could look into doing this tuning as part of that upgrade. Next update will be a very major update.

 

DOnt forget to include AEM WB support in next upgrade

 

Sorry that I have been MIA on testing the 88590715 ROM. I have been out of town again and the car is still down while I finish my trunk battery install; I should get this done today.

Ziad, What do you need me to send you via email? Just my latest ROM? It is already patched with the original DMA patch. Does that matter? I can email you this when I hear back.

 

yes mate, just send me ur rom. i should be able to patch it. there is a "possibly issue" with 88590715, but i will email u about it once i get ur rom

 

so since the problem with being able to tune VE or MIVEC is the limited space in RAM (from my understanding of this thread that seems to be what I'm reading) can we not just develop a way to swap one of the tables (say fueling) temporarily, since when tuning SD you would be tuning your VE table so your afrs actually match your afr table instead of tuning the afr table?

I would love to use this technology but its only really useful for me to tune timing.....I would totally throw a fat donation if someone added mivec or VE. (hint hint)

 

MIVEC is in beta testing. I was one of the testers but my evo had to go under the knife so I couldn't finish testing.

 

I sent the ROM on Sunday. I am not bugging you but just want to make sure my email didnt eat it since it is a binary file...

 

nice, I'm going to assume that this testing involves hex editing or other fancy-ness that I am completely unskilled with or I would offer to help you out with testing it.

What about the prospects of swapping the fuel map RAM space with the VE Map? I don't want to come across as pushy as I have total respect and appreciation for everyone that works to improve the capability of the stock ecu. I'm just curious if that was every looked at as a solution for the SD 2.0 cars.

 

Hey Ziad I don't know if your aware of this or not but when auto patching the 8859 rom through the ELM software the XML data it spits out to be added to the ecuflash xml def has an error. The address for the ROM MUT table is not in quotations and it will crash ecuflash unless changed. I changed mine and seem to be working. I can view the table correctly etc. I'm going to load it on the car now and will report back.

Here is a copy with the problem in bold.