cracking the ecu....
04-08-2006, 06:34 PM
#201
Registered
iTrader: (1)
Join Date: May 2003
Location: PA
Posts: 3,754
Likes: 0
Received 0 Likes
on
0 Posts
possible table for EGT (measured in Celcius)???
X-Axis: [0x7f338 18x4]
500 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7f380 8x4]
0.125 0.25 0.375 0.5 0.625 0.75 0.875 1
Cells: [0x7f3a0 18x8x2]
00520 00525 00626 00700 00732 00771 00801 00853 00860 00891 00873 00876 00886 00854 00880 00910 00942 00942
00520 00530 00618 00690 00722 00780 00797 00834 00854 00887 00877 00876 00886 00854 00880 00910 00942 00942
00520 00533 00630 00703 00744 00791 00801 00806 00863 00886 00882 00883 00880 00878 00880 00902 00942 00942
00510 00548 00649 00720 00761 00826 00840 00855 00887 00907 00889 00887 00883 00890 00892 00893 00916 00916
00526 00584 00681 00752 00784 00866 00862 00874 00902 00919 00899 00898 00885 00893 00896 00897 00914 00914
00513 00598 00722 00800 00831 00889 00870 00882 00907 00918 00903 00901 00889 00893 00901 00902 00912 00912
00513 00598 00724 00818 00878 00890 00890 00902 00917 00927 00908 00909 00893 00895 00904 00911 00912 00912
00513 00598 00724 00818 00878 00890 00890 00907 00922 00935 00909 00910 00899 00897 00904 00912 00911 00911
X-Axis: [0x7f338 18x4]
500 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7f380 8x4]
0.125 0.25 0.375 0.5 0.625 0.75 0.875 1
Cells: [0x7f3a0 18x8x2]
00520 00525 00626 00700 00732 00771 00801 00853 00860 00891 00873 00876 00886 00854 00880 00910 00942 00942
00520 00530 00618 00690 00722 00780 00797 00834 00854 00887 00877 00876 00886 00854 00880 00910 00942 00942
00520 00533 00630 00703 00744 00791 00801 00806 00863 00886 00882 00883 00880 00878 00880 00902 00942 00942
00510 00548 00649 00720 00761 00826 00840 00855 00887 00907 00889 00887 00883 00890 00892 00893 00916 00916
00526 00584 00681 00752 00784 00866 00862 00874 00902 00919 00899 00898 00885 00893 00896 00897 00914 00914
00513 00598 00722 00800 00831 00889 00870 00882 00907 00918 00903 00901 00889 00893 00901 00902 00912 00912
00513 00598 00724 00818 00878 00890 00890 00902 00917 00927 00908 00909 00893 00895 00904 00911 00912 00912
00513 00598 00724 00818 00878 00890 00890 00907 00922 00935 00909 00910 00899 00897 00904 00912 00911 00911
04-09-2006, 07:21 AM
#202
Registered
Join Date: Sep 2004
Location: Europe
Posts: 581
Likes: 0
Received 0 Likes
on
0 Posts
^^^^ At first, it looks like it could indeed be the Exhaust Gas Temperature table (called FN4441 in Ford EEC V strategies) in °C.
FN4441 contains EGT measured in the following conditions : stoich. AFR, MBT spark and 0% EGR.
Such a table should show a big difference in EGT between low loads and high loads. The table above does not show this. 520 °C is much much too high to be EGT at 500 RPM / 0.125 load! Even on a rotary. It should be closer to 150-200 °C.
However, this table above seems to be linked to exhaust temperature somehow. Indeed, temperature at 500 RPM high load is about half of the temperature at 9000 RPM. That perfectly match what I've seen in other calibrations.
This analysis above pushes me to make a general comment about most of the tables you guys have pulled from the file. Mainly the tables as a function of engine speed and load. They remarkedly seem to be a lack of difference in those tables between high loads and low loads, or if you prefer, a lack of variability along the Y-axis.
Has anyone else the same feeling?
Fabrice
FN4441 contains EGT measured in the following conditions : stoich. AFR, MBT spark and 0% EGR.
Such a table should show a big difference in EGT between low loads and high loads. The table above does not show this. 520 °C is much much too high to be EGT at 500 RPM / 0.125 load! Even on a rotary. It should be closer to 150-200 °C.
However, this table above seems to be linked to exhaust temperature somehow. Indeed, temperature at 500 RPM high load is about half of the temperature at 9000 RPM. That perfectly match what I've seen in other calibrations.
This analysis above pushes me to make a general comment about most of the tables you guys have pulled from the file. Mainly the tables as a function of engine speed and load. They remarkedly seem to be a lack of difference in those tables between high loads and low loads, or if you prefer, a lack of variability along the Y-axis.
Has anyone else the same feeling?
Fabrice
04-09-2006, 09:33 AM
#203
Registered User
Thread Starter
iTrader: (1)
Join Date: Dec 2003
Location: Nebraska
Posts: 310
Likes: 0
Received 0 Likes
on
0 Posts
just looking at the table above, I see what you mean, but also notice the variance between Y axis values grows as rpm's increase until 3000 rpm, and then variances start to decrease with little variance at 8000 rpm and negative adjustments past that. Strange...
04-09-2006, 10:50 AM
#204
Originally Posted by TeamRX8
it's a lot easier to hijack the system with either an internal or external piggyback controller
even if you get the maps figured out and how to alter them, figuring out the base code programming functions that determine the overall software control strategy is a much more difficult task.
even if you get the maps figured out and how to alter them, figuring out the base code programming functions that determine the overall software control strategy is a much more difficult task.
04-09-2006, 03:47 PM
#205
I wanna rock! Rock!
Join Date: Jun 2005
Location: Monterey, CA
Posts: 576
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Rasputin
^^^^ At first, it looks like it could indeed be the Exhaust Gas Temperature table (called FN4441 in Ford EEC V strategies) in °C.
FN4441 contains EGT measured in the following conditions : stoich. AFR, MBT spark and 0% EGR.
Such a table should show a big difference in EGT between low loads and high loads. The table above does not show this. 520 °C is much much too high to be EGT at 500 RPM / 0.125 load! Even on a rotary. It should be closer to 150-200 °C.
However, this table above seems to be linked to exhaust temperature somehow. Indeed, temperature at 500 RPM high load is about half of the temperature at 9000 RPM. That perfectly match what I've seen in other calibrations.
This analysis above pushes me to make a general comment about most of the tables you guys have pulled from the file. Mainly the tables as a function of engine speed and load. They remarkedly seem to be a lack of difference in those tables between high loads and low loads, or if you prefer, a lack of variability along the Y-axis.
Has anyone else the same feeling?
Fabrice
FN4441 contains EGT measured in the following conditions : stoich. AFR, MBT spark and 0% EGR.
Such a table should show a big difference in EGT between low loads and high loads. The table above does not show this. 520 °C is much much too high to be EGT at 500 RPM / 0.125 load! Even on a rotary. It should be closer to 150-200 °C.
However, this table above seems to be linked to exhaust temperature somehow. Indeed, temperature at 500 RPM high load is about half of the temperature at 9000 RPM. That perfectly match what I've seen in other calibrations.
This analysis above pushes me to make a general comment about most of the tables you guys have pulled from the file. Mainly the tables as a function of engine speed and load. They remarkedly seem to be a lack of difference in those tables between high loads and low loads, or if you prefer, a lack of variability along the Y-axis.
Has anyone else the same feeling?
Fabrice
04-09-2006, 03:51 PM
#206
Registered
Join Date: Sep 2004
Location: Europe
Posts: 581
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by mikeschaefer
Maybe they are measuring in Kelvin and not degrees Celsius, which would mean it's 520 Kelvin at 500 RPM or 247 degrees Celsius.
Fabrice
04-09-2006, 04:07 PM
#207
Registered
Join Date: Sep 2004
Location: Europe
Posts: 581
Likes: 0
Received 0 Likes
on
0 Posts
And this table below must be the Metering Oil Pump stepper motor taget value (it's a 60 step stepper motor). See Mazda Training Manual for details.
X-Axis: [0x7c474 19x4]
700 720 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7c4c0 17x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625
Cells: [0x7c504 19x17x1]
003 003 003 003 003 003 003 003 003 005 007 007 007 011 012 015 019 019 021
003 003 003 003 003 003 003 003 003 005 007 007 007 011 015 018 020 021 022
003 003 003 003 003 003 003 003 003 005 007 007 007 011 017 019 021 022 045
003 003 003 003 003 003 003 003 003 005 007 007 007 011 018 021 022 023 045
003 003 003 003 003 003 003 004 005 006 008 007 009 012 018 022 023 045 045
003 003 003 006 003 003 003 005 006 009 010 011 012 015 021 023 045 045 045
003 006 006 009 006 005 008 008 008 011 013 014 016 019 023 045 045 045 045
003 019 019 016 016 016 019 016 014 013 015 017 017 020 045 045 045 045 045
003 019 019 016 016 016 019 016 014 015 018 019 019 020 045 045 045 045 047
003 019 019 016 016 016 019 017 016 017 020 020 020 021 045 045 045 048 050
003 019 019 018 017 016 019 018 019 020 020 021 021 021 045 045 047 049 051
003 021 021 021 019 018 019 020 021 021 021 021 021 021 045 045 048 051 054
003 021 021 022 021 021 021 021 025 025 025 025 025 045 045 045 050 054 056
003 021 021 022 021 021 021 021 026 026 026 026 026 045 045 048 052 056 059
003 021 021 022 022 022 021 021 026 026 027 026 045 045 047 052 055 058 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 048 053 055 060 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 060 060 060 060 060
Oil delivery increases with engine speed, and load.
Fabrice
X-Axis: [0x7c474 19x4]
700 720 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7c4c0 17x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625
Cells: [0x7c504 19x17x1]
003 003 003 003 003 003 003 003 003 005 007 007 007 011 012 015 019 019 021
003 003 003 003 003 003 003 003 003 005 007 007 007 011 015 018 020 021 022
003 003 003 003 003 003 003 003 003 005 007 007 007 011 017 019 021 022 045
003 003 003 003 003 003 003 003 003 005 007 007 007 011 018 021 022 023 045
003 003 003 003 003 003 003 004 005 006 008 007 009 012 018 022 023 045 045
003 003 003 006 003 003 003 005 006 009 010 011 012 015 021 023 045 045 045
003 006 006 009 006 005 008 008 008 011 013 014 016 019 023 045 045 045 045
003 019 019 016 016 016 019 016 014 013 015 017 017 020 045 045 045 045 045
003 019 019 016 016 016 019 016 014 015 018 019 019 020 045 045 045 045 047
003 019 019 016 016 016 019 017 016 017 020 020 020 021 045 045 045 048 050
003 019 019 018 017 016 019 018 019 020 020 021 021 021 045 045 047 049 051
003 021 021 021 019 018 019 020 021 021 021 021 021 021 045 045 048 051 054
003 021 021 022 021 021 021 021 025 025 025 025 025 045 045 045 050 054 056
003 021 021 022 021 021 021 021 026 026 026 026 026 045 045 048 052 056 059
003 021 021 022 022 022 021 021 026 026 027 026 045 045 047 052 055 058 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 048 053 055 060 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 060 060 060 060 060
Oil delivery increases with engine speed, and load.
Fabrice
04-09-2006, 04:10 PM
#208
I wanna rock! Rock!
Join Date: Jun 2005
Location: Monterey, CA
Posts: 576
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Rasputin
They're not, as the OBD parameter is in °C. Also, the expected temp at high speeds and loads should be around 1770°F, not 900.
Fabrice
Fabrice
Well I'm kind of confused about what you said in your earlier post. It sounds like you said EGT @ 500 rpm should be half of the EGT at 9K rpm.
If that's the case then the table says 911°C at 9K rpm, or 1672°F.
Is 968°F too high for 500 rpm?
04-09-2006, 05:50 PM
#209
Registered
iTrader: (1)
Join Date: May 2003
Location: PA
Posts: 3,754
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Rasputin
^^^^ At first, it looks like it could indeed be the Exhaust Gas Temperature table (called FN4441 in Ford EEC V strategies) in °C.
04-09-2006, 06:11 PM
#210
Registered
iTrader: (1)
Join Date: May 2003
Location: PA
Posts: 3,754
Likes: 0
Received 0 Likes
on
0 Posts
towards the beginning there is a series of maps and the variable above looks like a heading and changes from 132, 122, to 126
perhaps the variable above is engine coolant temp in deg F and this would be something with the cold start strategy...>132F, <122F, or between?
... i'm not very certain of this one... more of a shot in the dark
perhaps the variable above is engine coolant temp in deg F and this would be something with the cold start strategy...>132F, <122F, or between?
... i'm not very certain of this one... more of a shot in the dark
04-10-2006, 01:55 AM
#211
Is this title ok?
The spark timing should not be in decimal value; the timing should be store as a byte value because the max value you can store is between -127 to 127 which are more than enough for retard and advance. The decimal value indicate either info that may express in percentage, or signal that can be express as decimal such as voltage, Lamba/AF, etc. There are also other information around the map that give hint to the min & max value and delta (decrement/increment) value for the X/Y axis.
These two look more like timing than fuel or correction map.
X-Axis: [0x7c474 19x4]
700 720 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7c4c0 17x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625
Cells: [0x7c504 19x17x1]
003 003 003 003 003 003 003 003 003 005 007 007 007 011 012 015 019 019 021
003 003 003 003 003 003 003 003 003 005 007 007 007 011 015 018 020 021 022
003 003 003 003 003 003 003 003 003 005 007 007 007 011 017 019 021 022 045
003 003 003 003 003 003 003 003 003 005 007 007 007 011 018 021 022 023 045
003 003 003 003 003 003 003 004 005 006 008 007 009 012 018 022 023 045 045
003 003 003 006 003 003 003 005 006 009 010 011 012 015 021 023 045 045 045
003 006 006 009 006 005 008 008 008 011 013 014 016 019 023 045 045 045 045
003 019 019 016 016 016 019 016 014 013 015 017 017 020 045 045 045 045 045
003 019 019 016 016 016 019 016 014 015 018 019 019 020 045 045 045 045 047
003 019 019 016 016 016 019 017 016 017 020 020 020 021 045 045 045 048 050
003 019 019 018 017 016 019 018 019 020 020 021 021 021 045 045 047 049 051
003 021 021 021 019 018 019 020 021 021 021 021 021 021 045 045 048 051 054
003 021 021 022 021 021 021 021 025 025 025 025 025 045 045 045 050 054 056
003 021 021 022 021 021 021 021 026 026 026 026 026 045 045 048 052 056 059
003 021 021 022 022 022 021 021 026 026 027 026 045 045 047 052 055 058 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 048 053 055 060 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 060 060 060 060 060
X-Axis: [0x7c648 19x4]
700 720 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7c694 4x4]
60 65 70 80
Cells: [0x7c6a4 19x4x1]
000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
003 019 019 020 019 021 021 021 026 026 026 034 045 045 048 052 055 057 060
003 019 019 020 019 021 021 021 026 026 026 034 045 045 048 052 055 057 060
003 019 019 020 019 021 021 021 026 026 026 034 045 045 048 052 055 057 060
There are still many values that are still being discover. It'll be just a matter of time before all have been identify and classify their characteristic against real data.
There are maps that always starting from lower RPM value to the upper limit. None of the map I've seen has any indication that it would start at a higher or mid value. To switch between one map to another, it doesn't need to have the map to be start from that mid value. The map may contains the zeo value from the lower RPM to the highest RPM, there is some trigger around the map to indicate which map to use and when; For map that have 0 value in the lower RPM sections, etc. those area will not see any value which also act as un-affected map which would not do any thing to the injectors/timing. This may be the strategy the engineer use to play around with port opening so that they do not need to re-scale the Axis if they need to move the opening time up or down in the RPM band.
The characteristic of each map have the following:
X-Axis, Y-Axis; always 4 byte in decimal.
The map itself can have 1 byte, 2 byte ot 4 byte data.
1 byte data usually associate to timing or other small value that never exceed -127 to 127 or 0 to 255 value. The 2 byte value should be representing integer value that usually associate with fuel pusle in either in milliseconds or microseconds. The 4 byte data should be representing decimal value that may express as decimal or percentage.
The map you show should be some type of correction map in percentage. Perhaps it may be the maximun correction factors for the close loop fuel trim or as you suggested knock correction factor (but not timing correction, they should be whole degree on in whole percentage if they are timing correction). There are too many possibility at the moment until we can verify them with real data logging and start making the changes.
Just to note, that all maps present or claim is not 100%, so I am totally wrong until all info can be verify. But the fact that timing cannot be express in decimal is something that I'm sure everyone would agree if they are to representing in degree of retard or advance.
Hau,
These two look more like timing than fuel or correction map.
X-Axis: [0x7c474 19x4]
700 720 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7c4c0 17x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625
Cells: [0x7c504 19x17x1]
003 003 003 003 003 003 003 003 003 005 007 007 007 011 012 015 019 019 021
003 003 003 003 003 003 003 003 003 005 007 007 007 011 015 018 020 021 022
003 003 003 003 003 003 003 003 003 005 007 007 007 011 017 019 021 022 045
003 003 003 003 003 003 003 003 003 005 007 007 007 011 018 021 022 023 045
003 003 003 003 003 003 003 004 005 006 008 007 009 012 018 022 023 045 045
003 003 003 006 003 003 003 005 006 009 010 011 012 015 021 023 045 045 045
003 006 006 009 006 005 008 008 008 011 013 014 016 019 023 045 045 045 045
003 019 019 016 016 016 019 016 014 013 015 017 017 020 045 045 045 045 045
003 019 019 016 016 016 019 016 014 015 018 019 019 020 045 045 045 045 047
003 019 019 016 016 016 019 017 016 017 020 020 020 021 045 045 045 048 050
003 019 019 018 017 016 019 018 019 020 020 021 021 021 045 045 047 049 051
003 021 021 021 019 018 019 020 021 021 021 021 021 021 045 045 048 051 054
003 021 021 022 021 021 021 021 025 025 025 025 025 045 045 045 050 054 056
003 021 021 022 021 021 021 021 026 026 026 026 026 045 045 048 052 056 059
003 021 021 022 022 022 021 021 026 026 027 026 045 045 047 052 055 058 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 048 053 055 060 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 060 060 060 060 060
X-Axis: [0x7c648 19x4]
700 720 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7c694 4x4]
60 65 70 80
Cells: [0x7c6a4 19x4x1]
000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000
003 019 019 020 019 021 021 021 026 026 026 034 045 045 048 052 055 057 060
003 019 019 020 019 021 021 021 026 026 026 034 045 045 048 052 055 057 060
003 019 019 020 019 021 021 021 026 026 026 034 045 045 048 052 055 057 060
There are still many values that are still being discover. It'll be just a matter of time before all have been identify and classify their characteristic against real data.
There are maps that always starting from lower RPM value to the upper limit. None of the map I've seen has any indication that it would start at a higher or mid value. To switch between one map to another, it doesn't need to have the map to be start from that mid value. The map may contains the zeo value from the lower RPM to the highest RPM, there is some trigger around the map to indicate which map to use and when; For map that have 0 value in the lower RPM sections, etc. those area will not see any value which also act as un-affected map which would not do any thing to the injectors/timing. This may be the strategy the engineer use to play around with port opening so that they do not need to re-scale the Axis if they need to move the opening time up or down in the RPM band.
The characteristic of each map have the following:
X-Axis, Y-Axis; always 4 byte in decimal.
The map itself can have 1 byte, 2 byte ot 4 byte data.
1 byte data usually associate to timing or other small value that never exceed -127 to 127 or 0 to 255 value. The 2 byte value should be representing integer value that usually associate with fuel pusle in either in milliseconds or microseconds. The 4 byte data should be representing decimal value that may express as decimal or percentage.
The map you show should be some type of correction map in percentage. Perhaps it may be the maximun correction factors for the close loop fuel trim or as you suggested knock correction factor (but not timing correction, they should be whole degree on in whole percentage if they are timing correction). There are too many possibility at the moment until we can verify them with real data logging and start making the changes.
Just to note, that all maps present or claim is not 100%, so I am totally wrong until all info can be verify. But the fact that timing cannot be express in decimal is something that I'm sure everyone would agree if they are to representing in degree of retard or advance.
Hau,
Originally Posted by Rasputin
seikx8,
I had a proper look at your file yesterday night. I have a few comments.
I don't think what you identifed in a previous post as a spark advance table actually is one.
I found these two tables to be more in line with what to expect :
X-Axis: [0x7fc78 9x4]
0.125 0.2 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625
Y-Axis: [0x7fc9c 9x4]
500 1000 1400 2000 2500 3000 3500 4000 4500
Cells: [0x7fcc0 9x9x4]
16.68 16.68 18.00 17.27 21.41 18.22 16.62 17.08 16.05
16.68 16.68 18.00 17.27 21.41 18.22 16.62 17.08 16.05
16.68 16.68 18.00 17.27 21.41 18.22 16.62 17.08 16.05
17.82 17.82 19.80 17.06 16.95 16.84 19.38 17.02 15.66
17.53 17.53 16.08 15.26 18.31 17.07 16.04 20.04 17.76
17.59 17.59 22.59 18.83 16.38 18.67 18.12 18.86 17.97
18.06 18.06 25.14 18.45 18.89 17.67 21.62 21.62 21.62
19.36 19.36 22.95 18.71 18.13 18.55 20.17 20.17 20.17
19.36 19.36 22.95 18.71 18.13 18.55 20.17 20.17 20.17
X-Axis: [0x7fe10 10x4]
0.16 0.21 0.25 0.375 0.5 0.625 0.75 0.875 1 1.1
Y-Axis: [0x7fe38 17x4]
780 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500
Cells: [0x7fe7c 10x17x4]
21.80 21.80 21.80 43.10 56.90 73.90 79.70 79.70 79.70 79.70
15.87 15.87 22.60 43.10 56.90 73.90 79.70 79.70 79.70 79.70
16.00 18.30 20.10 31.90 43.50 55.20 66.70 66.70 66.70 66.70
10.40 13.51 16.00 24.10 32.40 42.60 50.70 57.20 57.20 57.20
9.00 10.77 12.20 18.40 24.20 30.00 38.10 44.90 44.90 44.90
7.00 9.17 10.90 16.40 21.20 28.00 33.80 41.40 41.40 41.40
5.50 7.45 9.00 14.50 20.10 25.70 31.70 36.80 36.80 36.80
5.50 6.84 7.90 12.60 17.40 22.90 26.70 29.00 29.00 29.00
5.00 5.89 6.60 11.50 15.60 20.30 23.50 27.90 27.90 27.90
6.00 6.00 6.00 10.00 13.80 18.70 22.40 23.50 23.60 23.60
6.00 6.00 6.00 9.30 12.00 15.90 19.70 20.00 20.10 20.10
6.00 6.00 6.00 7.60 9.90 12.90 16.60 18.40 19.50 19.50
6.00 6.00 6.00 6.00 9.10 11.80 13.30 13.91 16.10 16.10
6.00 6.00 6.00 6.00 9.80 11.50 13.30 16.41 16.17 16.17
13.00 13.00 13.00 13.00 10.79 11.80 15.00 16.90 20.20 20.20
13.00 13.00 13.00 13.00 13.00 13.00 18.00 22.00 30.00 30.00
14.00 14.00 14.00 14.00 14.00 14.00 22.00 31.00 31.00 31.00
One must be for Leading, and the other one for Trailing plugs. Please feel free to comment.
This can be verified easily with a sCANalyser.
I also think these following 2 tables gives the range of authority (retard/advance clips) for the knock control :
X-Axis: [0x7dca8 20x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625 1.125 1.1875 1.25
Y-Axis: [0x7dcf8 12x4]
500 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000
Cells: [0x7dd28 20x12x4]
2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50
2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50
2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30
2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40
2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80
2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.90 2.90 2.90 2.90 2.90 2.90 2.90
3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80
3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00
2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80
2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75
2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75
2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75
X-Axis: [0x7e0f4 20x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625 1.125 1.1875 1.25
Y-Axis: [0x7e144 12x4]
500 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000
Cells: [0x7e174 20x12x4]
2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50
2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50
3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20
3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00
3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30
3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.80 3.80 3.80 3.80 3.80 3.80 3.80
3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00
4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00
3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90
3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75
3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75
3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75
Again, this can easily be checked.
Regarding the table identified as the fuel table, I don't believe it is the main fuel table (however, it can be a default fuel pulsewidth table in case of MAFS failure for example). Fuelling usually works this way on OEM products :
1) The quantity of air induced in the next stroke is estimated by a very complex dedicated strategy module that will basically also calculate a LOAD value. On the RX8, this estimation is essentially based on MAFS data.
2) The PCM then calculates the amount of fuel that's necessary to achieve the target lambda value (whether it is in open loop or close loop does not change this) . It derives a fuel pulsewidth from this amount of fuel.
You see, no base fuel maps with fuel pulsewidth in such a system. The only "fuel" tables actually define where the system works in open or closed loop, and the target lambda value.
Another point that could confirm this is the fact we only find one table that really looks like a fuel injector pulsewidth table (up to 28000). But we have three levels of injectors with independant fuelling patterns. We should therefore have 3 tables and 2 of them with "0" pulse width under 4000 RPM (SSV is closed).
So, what we're looking for, in order to modify fuelling is :
- an open / closed loop table : LOAD (or possibly a TPS-derived load input) vs N 'engine speed) with 0s and 1s in the table
- another LOAD vs N table with target lambdas in it. There will be a wide area at low/medium speeds and loads where lambda is 1.
- somewhere, there must be a fuction or table giving info to the system regarding the share of the scheduled fuelling between the 3 levels of injection.
Modifying fuelling for FI :
To calculate the engine air consumption, the engine essentually use MAFS data.
To estimate the fuel pulse width, the system uses a complex algorithm introducing all sorts of data, including injector related info.
The PCM is actually capable of adjusting by it self the fuelling based on the existing maps, but it will somewhere be limted by the system's diagnostic fucntions (whether they are a legal requirement - like OBD - or not). I can immediatelly identify 2 of them :
- a first one that compares at all times the measured mass air flow for a given TPS and engine speed to a inferred (= calculated + mapped) load value. If the difference is too high (due to FI for example) -> CEL & Limp Home...
- a second one has been extensively mentionned on this forum, it's the LTFuelTrim, or adaptive fuelling that is also limited (+/- 12.5 % if I remember correctly). Go above the limit and it's CEL and possibly Limp Home...
Fabrice
I had a proper look at your file yesterday night. I have a few comments.
I don't think what you identifed in a previous post as a spark advance table actually is one.
I found these two tables to be more in line with what to expect :
X-Axis: [0x7fc78 9x4]
0.125 0.2 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625
Y-Axis: [0x7fc9c 9x4]
500 1000 1400 2000 2500 3000 3500 4000 4500
Cells: [0x7fcc0 9x9x4]
16.68 16.68 18.00 17.27 21.41 18.22 16.62 17.08 16.05
16.68 16.68 18.00 17.27 21.41 18.22 16.62 17.08 16.05
16.68 16.68 18.00 17.27 21.41 18.22 16.62 17.08 16.05
17.82 17.82 19.80 17.06 16.95 16.84 19.38 17.02 15.66
17.53 17.53 16.08 15.26 18.31 17.07 16.04 20.04 17.76
17.59 17.59 22.59 18.83 16.38 18.67 18.12 18.86 17.97
18.06 18.06 25.14 18.45 18.89 17.67 21.62 21.62 21.62
19.36 19.36 22.95 18.71 18.13 18.55 20.17 20.17 20.17
19.36 19.36 22.95 18.71 18.13 18.55 20.17 20.17 20.17
X-Axis: [0x7fe10 10x4]
0.16 0.21 0.25 0.375 0.5 0.625 0.75 0.875 1 1.1
Y-Axis: [0x7fe38 17x4]
780 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500
Cells: [0x7fe7c 10x17x4]
21.80 21.80 21.80 43.10 56.90 73.90 79.70 79.70 79.70 79.70
15.87 15.87 22.60 43.10 56.90 73.90 79.70 79.70 79.70 79.70
16.00 18.30 20.10 31.90 43.50 55.20 66.70 66.70 66.70 66.70
10.40 13.51 16.00 24.10 32.40 42.60 50.70 57.20 57.20 57.20
9.00 10.77 12.20 18.40 24.20 30.00 38.10 44.90 44.90 44.90
7.00 9.17 10.90 16.40 21.20 28.00 33.80 41.40 41.40 41.40
5.50 7.45 9.00 14.50 20.10 25.70 31.70 36.80 36.80 36.80
5.50 6.84 7.90 12.60 17.40 22.90 26.70 29.00 29.00 29.00
5.00 5.89 6.60 11.50 15.60 20.30 23.50 27.90 27.90 27.90
6.00 6.00 6.00 10.00 13.80 18.70 22.40 23.50 23.60 23.60
6.00 6.00 6.00 9.30 12.00 15.90 19.70 20.00 20.10 20.10
6.00 6.00 6.00 7.60 9.90 12.90 16.60 18.40 19.50 19.50
6.00 6.00 6.00 6.00 9.10 11.80 13.30 13.91 16.10 16.10
6.00 6.00 6.00 6.00 9.80 11.50 13.30 16.41 16.17 16.17
13.00 13.00 13.00 13.00 10.79 11.80 15.00 16.90 20.20 20.20
13.00 13.00 13.00 13.00 13.00 13.00 18.00 22.00 30.00 30.00
14.00 14.00 14.00 14.00 14.00 14.00 22.00 31.00 31.00 31.00
One must be for Leading, and the other one for Trailing plugs. Please feel free to comment.
This can be verified easily with a sCANalyser.
I also think these following 2 tables gives the range of authority (retard/advance clips) for the knock control :
X-Axis: [0x7dca8 20x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625 1.125 1.1875 1.25
Y-Axis: [0x7dcf8 12x4]
500 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000
Cells: [0x7dd28 20x12x4]
2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50
2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.20 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50
2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30
2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40 2.40
2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80
2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.60 2.90 2.90 2.90 2.90 2.90 2.90 2.90
3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80
3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00
2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80 2.80
2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75
2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75
2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75 2.75
X-Axis: [0x7e0f4 20x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625 1.125 1.1875 1.25
Y-Axis: [0x7e144 12x4]
500 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000
Cells: [0x7e174 20x12x4]
2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50
2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.30 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50 2.50
3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20 3.20
3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00 3.00
3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30 3.30
3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.60 3.80 3.80 3.80 3.80 3.80 3.80 3.80
3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00
4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00 4.00
3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90 3.90
3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75
3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75
3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75 3.75
Again, this can easily be checked.
Regarding the table identified as the fuel table, I don't believe it is the main fuel table (however, it can be a default fuel pulsewidth table in case of MAFS failure for example). Fuelling usually works this way on OEM products :
1) The quantity of air induced in the next stroke is estimated by a very complex dedicated strategy module that will basically also calculate a LOAD value. On the RX8, this estimation is essentially based on MAFS data.
2) The PCM then calculates the amount of fuel that's necessary to achieve the target lambda value (whether it is in open loop or close loop does not change this) . It derives a fuel pulsewidth from this amount of fuel.
You see, no base fuel maps with fuel pulsewidth in such a system. The only "fuel" tables actually define where the system works in open or closed loop, and the target lambda value.
Another point that could confirm this is the fact we only find one table that really looks like a fuel injector pulsewidth table (up to 28000). But we have three levels of injectors with independant fuelling patterns. We should therefore have 3 tables and 2 of them with "0" pulse width under 4000 RPM (SSV is closed).
So, what we're looking for, in order to modify fuelling is :
- an open / closed loop table : LOAD (or possibly a TPS-derived load input) vs N 'engine speed) with 0s and 1s in the table
- another LOAD vs N table with target lambdas in it. There will be a wide area at low/medium speeds and loads where lambda is 1.
- somewhere, there must be a fuction or table giving info to the system regarding the share of the scheduled fuelling between the 3 levels of injection.
Modifying fuelling for FI :
To calculate the engine air consumption, the engine essentually use MAFS data.
To estimate the fuel pulse width, the system uses a complex algorithm introducing all sorts of data, including injector related info.
The PCM is actually capable of adjusting by it self the fuelling based on the existing maps, but it will somewhere be limted by the system's diagnostic fucntions (whether they are a legal requirement - like OBD - or not). I can immediatelly identify 2 of them :
- a first one that compares at all times the measured mass air flow for a given TPS and engine speed to a inferred (= calculated + mapped) load value. If the difference is too high (due to FI for example) -> CEL & Limp Home...
- a second one has been extensively mentionned on this forum, it's the LTFuelTrim, or adaptive fuelling that is also limited (+/- 12.5 % if I remember correctly). Go above the limit and it's CEL and possibly Limp Home...
Fabrice
04-10-2006, 01:58 AM
#212
Is this title ok?
The WDS may be use to upload the modified flash, sure we can do much more than just checking. If we have access to the engineer's laptops, we can do much more than reflashing the already written application if you know what I mean.
Originally Posted by dannobre
I'm afraid the WDS won't help you much. It doesn't allow the techs to do much more than read the available PID's. You can't effect permanent changes to the ECU with it.
Mazda factory engineers have laptops with interfaces to actually change or create new flashes....that's whaat we need to get our hands on
Mazda factory engineers have laptops with interfaces to actually change or create new flashes....that's whaat we need to get our hands on
04-10-2006, 02:01 AM
#213
Is this title ok?
I am totall forgot about the MOP. Yes, it may as well be if the MOP is a 60 steps stepping motor. This map may be verify against older flash where Mazda make some change to the oil metering scheme in the high RPM in one of the compaign.
Originally Posted by Rasputin
And this table below must be the Metering Oil Pump stepper motor taget value (it's a 60 step stepper motor). See Mazda Training Manual for details.
X-Axis: [0x7c474 19x4]
700 720 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7c4c0 17x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625
Cells: [0x7c504 19x17x1]
003 003 003 003 003 003 003 003 003 005 007 007 007 011 012 015 019 019 021
003 003 003 003 003 003 003 003 003 005 007 007 007 011 015 018 020 021 022
003 003 003 003 003 003 003 003 003 005 007 007 007 011 017 019 021 022 045
003 003 003 003 003 003 003 003 003 005 007 007 007 011 018 021 022 023 045
003 003 003 003 003 003 003 004 005 006 008 007 009 012 018 022 023 045 045
003 003 003 006 003 003 003 005 006 009 010 011 012 015 021 023 045 045 045
003 006 006 009 006 005 008 008 008 011 013 014 016 019 023 045 045 045 045
003 019 019 016 016 016 019 016 014 013 015 017 017 020 045 045 045 045 045
003 019 019 016 016 016 019 016 014 015 018 019 019 020 045 045 045 045 047
003 019 019 016 016 016 019 017 016 017 020 020 020 021 045 045 045 048 050
003 019 019 018 017 016 019 018 019 020 020 021 021 021 045 045 047 049 051
003 021 021 021 019 018 019 020 021 021 021 021 021 021 045 045 048 051 054
003 021 021 022 021 021 021 021 025 025 025 025 025 045 045 045 050 054 056
003 021 021 022 021 021 021 021 026 026 026 026 026 045 045 048 052 056 059
003 021 021 022 022 022 021 021 026 026 027 026 045 045 047 052 055 058 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 048 053 055 060 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 060 060 060 060 060
Oil delivery increases with engine speed, and load.
Fabrice
X-Axis: [0x7c474 19x4]
700 720 1000 1500 2000 2500 3000 3500 4000 4500 5000 5500 6000 6500 7000 7500 8000 8500 9000
Y-Axis: [0x7c4c0 17x4]
0.0625 0.125 0.1875 0.25 0.3125 0.375 0.4375 0.5 0.5625 0.625 0.6875 0.75 0.8125 0.875 0.9375 1 1.0625
Cells: [0x7c504 19x17x1]
003 003 003 003 003 003 003 003 003 005 007 007 007 011 012 015 019 019 021
003 003 003 003 003 003 003 003 003 005 007 007 007 011 015 018 020 021 022
003 003 003 003 003 003 003 003 003 005 007 007 007 011 017 019 021 022 045
003 003 003 003 003 003 003 003 003 005 007 007 007 011 018 021 022 023 045
003 003 003 003 003 003 003 004 005 006 008 007 009 012 018 022 023 045 045
003 003 003 006 003 003 003 005 006 009 010 011 012 015 021 023 045 045 045
003 006 006 009 006 005 008 008 008 011 013 014 016 019 023 045 045 045 045
003 019 019 016 016 016 019 016 014 013 015 017 017 020 045 045 045 045 045
003 019 019 016 016 016 019 016 014 015 018 019 019 020 045 045 045 045 047
003 019 019 016 016 016 019 017 016 017 020 020 020 021 045 045 045 048 050
003 019 019 018 017 016 019 018 019 020 020 021 021 021 045 045 047 049 051
003 021 021 021 019 018 019 020 021 021 021 021 021 021 045 045 048 051 054
003 021 021 022 021 021 021 021 025 025 025 025 025 045 045 045 050 054 056
003 021 021 022 021 021 021 021 026 026 026 026 026 045 045 048 052 056 059
003 021 021 022 022 022 021 021 026 026 027 026 045 045 047 052 055 058 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 048 053 055 060 060
003 021 021 022 022 022 022 022 026 027 027 045 045 045 060 060 060 060 060
Oil delivery increases with engine speed, and load.
Fabrice
04-10-2006, 11:19 AM
#214
Registered
Join Date: Sep 2004
Location: Europe
Posts: 581
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by seikx8
Just to note, that all maps present or claim is not 100%, so I am totally wrong until all info can be verify.
Originally Posted by seikx8
The spark timing should not be in decimal value;
...But the fact that timing cannot be express in decimal is something that I'm sure everyone would agree if they are to representing in degree of retard or advance.
Hau,
...But the fact that timing cannot be express in decimal is something that I'm sure everyone would agree if they are to representing in degree of retard or advance.
Hau,
However I agree with you that spark advance figures with a resolution of 0.1 degree as seen in the maps I mentionned is a bit wierd. I'll look further.
Fabrice
04-12-2006, 03:35 PM
#215
Registered
Join Date: Sep 2004
Location: Europe
Posts: 581
Likes: 0
Received 0 Likes
on
0 Posts
I believe I identified some crucial data :
- the target lambda fuel table (with AFR ranging from 11.4 to stoich)
- this lambda table shows some difference between the US file found on this thread and a EU file given to me by Tertou (tu vois, Tertou, j'utilise ton travail!!)
Are we progressing on developping a tool that will build and flash new cals, because I'd like to try some mods to identify more parameters...
Fabrice
- the target lambda fuel table (with AFR ranging from 11.4 to stoich)
- this lambda table shows some difference between the US file found on this thread and a EU file given to me by Tertou (tu vois, Tertou, j'utilise ton travail!!)
Are we progressing on developping a tool that will build and flash new cals, because I'd like to try some mods to identify more parameters...
Fabrice
04-13-2006, 03:24 AM
#218
Registered
Join Date: Sep 2004
Location: Europe
Posts: 581
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by fray
Is there a reason that the values in the US an Europe would be different? Emissions standards, or catalytic converter life span requirements?
Also, customer requirments might also influence the calibration of this table. It's common for European calibrator to try to keep stoich fuelling for high speed (140 - 160 kph) motorway cruising as it has a strong impact on real life FE. The tables I'm comparing confirm this.
Re catalyst longevity, you must remember that it's illegal to protect catalyst by overfuelling from the base fuel table. Car manufacturers must use another strategy module to protect hardware. The base table can only contain LBT, or leaner, AFRs. It's the same fuelling at high speeds and loads from the 2 files I have (1 US, 1 EU).
EDIT : the maps I previously identified as the Spark Advance tables aren't. I mixed up Speed and Load axis when looking at them.
A tip to find spark tables :
- for a given Engine Speed, Spark Advance decrease with Load
- for a given Load, Spark Advance increase with Engine Speed.
Spark advance at high speed / high load is about 30° BTDC (says sCANalyser).
Fabrice
Last edited by Rasputin; 04-13-2006 at 04:40 AM.
05-01-2006, 06:43 AM
#219
Registered User
Join Date: Mar 2004
Location: Switzerland, VS
Posts: 8
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by fray
Is there a reason that the values in the US an Europe would be different? Emissions standards, or catalytic converter life span requirements?
Bob
05-02-2006, 03:38 AM
#220
Is this title ok?
The attach is the Win UI with the latest .xml map info. You'll need to access to the sw-n3z2ep000.phf file to view the data.
updated: replaced the uploaded file with the new working version of the application. You can make changes to the map and save it to the .phf file. You will need to install .net framework 2.0 for this application to run. You also need to have access to the Mazda PCM Programming software and the hardware to reflash the pcm. Since I do not have a PassThru device to test it with so I cannot verify if anything will work. I'm currently looking at DrewTech's Mongoose PassThru cable. If it works with Mazda Module Programming Software, it will be a good investment since it's affortable.
disclaimer: by download the software you are agree not to use the software for profit and use it on your own risk.
updated: replaced the uploaded file with the new working version of the application. You can make changes to the map and save it to the .phf file. You will need to install .net framework 2.0 for this application to run. You also need to have access to the Mazda PCM Programming software and the hardware to reflash the pcm. Since I do not have a PassThru device to test it with so I cannot verify if anything will work. I'm currently looking at DrewTech's Mongoose PassThru cable. If it works with Mazda Module Programming Software, it will be a good investment since it's affortable.
disclaimer: by download the software you are agree not to use the software for profit and use it on your own risk.
Last edited by seikx8; 05-16-2006 at 03:17 AM.
05-15-2006, 02:09 AM
#221
Is this title ok?
Originally Posted by Rasputin
I believe I identified some crucial data :
Are we progressing on developping a tool that will build and flash new cals, because I'd like to try some mods to identify more parameters...
Fabrice
Are we progressing on developping a tool that will build and flash new cals, because I'd like to try some mods to identify more parameters...
Fabrice
Check my last post, there is a working version of the application to allow you make changes to the map.
05-15-2006, 03:19 PM
#223
Just about the time I go and purchase the Interceptor-X, somebody will have cracked the ECU and re-mapped it. How long should I wait? What about the hand held flash tuner thread? I guess I should just be content and wait.
If I purchase the -X, I could burn 87 octane, but it will take me 5,333 gallons of gas at a .30 cent savings from 91 octane, to pay for itself.
If I purchase the -X, I could burn 87 octane, but it will take me 5,333 gallons of gas at a .30 cent savings from 91 octane, to pay for itself.
05-23-2006, 08:27 AM
#224
Mad for a Furai
Join Date: Sep 2004
Location: Madrid - Spain
Posts: 117
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by MazdaManiac
Indeed.
The tranny does know when it is in neutral. So if it knows that it is not in neutral, it can infer that it is in gear.
That is the extent of it.
The PCM doesn't really have a reason to care what gear it is in. However, it does have a vested interest in knowing how long you have been delta V at a given loading.
The tranny does know when it is in neutral. So if it knows that it is not in neutral, it can infer that it is in gear.
That is the extent of it.
The PCM doesn't really have a reason to care what gear it is in. However, it does have a vested interest in knowing how long you have been delta V at a given loading.
Astra flashes the ECU for a particular final gear ratio they use in their cars. That flash is not compatible with any other gear ratios so the flash can not be used in i.e. a stock car.
That means that the speed of the car vs engine speed could be taken into account by the ECU. I think it could be useful to consider that the gear the car is in, can be something used in any of the control strategies of our beloved RX8 ECU.
I have asked to tuj for a copy of the flash file. I would like to cooperate with this project if the "chief engineers" allow me to try it.
Regards
jird20