Advanced fuel control options
Dec 16, 2009, 06:53 PM
#121
I tried changing mine in increments and it still zeros the values out. I pretty much got fed up with it and changed the scaling back to the standard uint8 and left it at that. It still adjusts the way I want it to with the uint8 scaling, so will it adversely affect anything if I leave the scaling alone?
Also, Phenem...how were you able to keep the % sign intact without it screwing up the graph? Whenever I left the % sign there it lined all the values up vertically on the graph, so I removed that as well lol.
Also, Phenem...how were you able to keep the % sign intact without it screwing up the graph? Whenever I left the % sign there it lined all the values up vertically on the graph, so I removed that as well lol.
Dec 16, 2009, 08:41 PM
#122
<scaling name="Mult128-16" units="Multiplication Factor" toexpr="x/128" frexpr="x*128" format="%.2f" min="0" max="5" inc="0.02" storagetype="uint16" endian="big"/>
<scaling name="Mult128" units="Factor" toexpr="x/128" frexpr="x*128" format="%.2f" min="0" max="5" inc="0.02" storagetype="uint8" endian="big"/>
<scaling name="Mult128" units="Factor" toexpr="x/128" frexpr="x*128" format="%.2f" min="0" max="5" inc="0.02" storagetype="uint8" endian="big"/>
Dec 20, 2009, 10:53 PM
#124
Yes, the constant is adjustable. If this constant is allowed to be adjusted, then it would throw off the scaling for the injector open time during cranking. A %128 scaling could be used for the injector open time if the multiplier is allowed to be adjusted. From my perspective, its two ways of looking at how to adjust the values. My preference is to keep the millisecond scaling as it gives me a reference point to compare to idle pulse width.
I think there is value to using the time scaling for the IPW decay table because it is accurate and can be related to real world response.
I think there is value to using the time scaling for the IPW decay table because it is accurate and can be related to real world response.
The stock tables have very small values in the 50C-82C part of the table and very large at the cold side of the table.
With the warm start issues on the ID1000s, I'd like to mess with the table, but with the values being so small, it really limits the range of adjustment.
Changing the constant would let me rescale the table to give some added resolution. I looked at the dissassembly, but this constant wasn't real apparent to me. If you have a second at some point, would you be willing to post up this table scalar for 96530006?
Last edited by 03whitegsr; Dec 21, 2009 at 09:16 AM.
Dec 22, 2009, 10:10 PM
#125
Bringing this back up. This was in regards to the section 2) on Cranking injector pulse.
The stock tables have very small values in the 50C-82C part of the table and very large at the cold side of the table.
With the warm start issues on the ID1000s, I'd like to mess with the table, but with the values being so small, it really limits the range of adjustment.
Changing the constant would let me rescale the table to give some added resolution. I looked at the dissassembly, but this constant wasn't real apparent to me. If you have a second at some point, would you be willing to post up this table scalar for 96530006?
The stock tables have very small values in the 50C-82C part of the table and very large at the cold side of the table.
With the warm start issues on the ID1000s, I'd like to mess with the table, but with the values being so small, it really limits the range of adjustment.
Changing the constant would let me rescale the table to give some added resolution. I looked at the dissassembly, but this constant wasn't real apparent to me. If you have a second at some point, would you be willing to post up this table scalar for 96530006?
Dec 23, 2009, 07:22 AM
#126
If the logged values during warmup are a bit different than what's in the table, remember there is another trim table that I have not posted. If you want to see it for 96530006, the first axis at 0x66F2 is 14 elements long and is 2-byte load. The second axis at 0x7ADC is 8 elements long and is 2-byte RPM. The table data itself is at 0x6071.
I know a couple other guys have noted a problem in the same area so if a couple others can try it out, it would be helpful.
Here is the ECUFlash xml, you'll need to be in developer mode to see it.
Code:
<table name="***Warmup Enrichment Load vs RPM" address="6071" category="Engine Coolant Temperature Trim" type="3D" level="1" scaling="uint8"> <table name="Engine Load" address="66f2" type="X Axis" elements="14" scaling="Load"/> <table name="Engine Speed" address="7adc" type="Y Axis" elements="8" scaling="RPM"/> </table>
Stock Table
New table (just to see what happens)...
Last edited by 03whitegsr; Dec 23, 2009 at 07:39 AM.
Dec 23, 2009, 07:49 AM
#127
Dec 23, 2009, 08:11 AM
#129
I was unsure about that too. I just noticed the big hole right in the area that my car always drives like crap in, then the 128 area surrounding it where the car drives fine. 1+1 = 2
On top of that, it looks like at higher loads and engine speeds,the table is setup to eliminate the enrichment of the other two enrichment tables so WOT AFRs don't get insanely rich.
Honestly though, I'm just wondering if that hole has something to do with the MAF filter setup as well where maf frequency gets halved and then corrected for. Maybe we jumped around some part of the fuel routine that deals with this big difference but now we have a table setup for it when it's not there?
On top of that, it looks like at higher loads and engine speeds,the table is setup to eliminate the enrichment of the other two enrichment tables so WOT AFRs don't get insanely rich.
Honestly though, I'm just wondering if that hole has something to do with the MAF filter setup as well where maf frequency gets halved and then corrected for. Maybe we jumped around some part of the fuel routine that deals with this big difference but now we have a table setup for it when it's not there?
Last edited by 03whitegsr; Dec 23, 2009 at 08:15 AM.
Dec 23, 2009, 08:35 AM
#131
The issue for me is if I let the clutch out and keep the engine speed very low. Basically keeping engine speed around 1000 RPM starting out.
Any amount of gas I give it from this point on results in 20:1 AFRs until about 1500 RPM.
Easiest way to replicate is start off, shift to second and let the revs fall back to 1000RPM. Good luck getting back above 1500 RPM in under a block or two.
It's something you can drive around, but if you happen to find yourself cutting across a road and happen to hit that critical RPM range, it can be a little scary when the car just doesn't go anywhere and on-coming traffic is coming up quick.
Any amount of gas I give it from this point on results in 20:1 AFRs until about 1500 RPM.
Easiest way to replicate is start off, shift to second and let the revs fall back to 1000RPM. Good luck getting back above 1500 RPM in under a block or two.
It's something you can drive around, but if you happen to find yourself cutting across a road and happen to hit that critical RPM range, it can be a little scary when the car just doesn't go anywhere and on-coming traffic is coming up quick.
Last edited by 03whitegsr; Dec 23, 2009 at 09:29 AM.
Dec 26, 2009, 03:22 PM
#135
Evolved Member
Found a similar 3D map for the AUDM9 88580013, at address 647D.
It has a bit more complex data than the evo8 described above though.
I am currently using scaling "EnrichmentAdj" which sets value 128=1.00 so its easy to read the increment.
Nothere, there probably is a modulating table to go with it, back to the disassemblers...
It has a bit more complex data than the evo8 described above though.
I am currently using scaling "EnrichmentAdj" which sets value 128=1.00 so its easy to read the increment.
Nothere, there probably is a modulating table to go with it, back to the disassemblers...