ECUflash/ Tactrix cable newb thread
Oct 4, 2010, 07:52 PM
#61
Evolved Member
Thread Starter
iTrader: (3)
Join Date: Jun 2010
Location: Boston MA
Posts: 1,087
Likes: 0
Received 0 Likes
on
0 Posts
did you watch the ecuflash tutorial videos? they are pretty helpful as far as walking your through like, everything involved.
as far as the problem with the column values, there is probably something wrong in one of those definition files. Each of those files says "this item" is located at "this location" with "these settings", so if part of that lil fake statement i just made is incorrect, it'll lookup the values in the wrong spot or wrong scaling. click one of those boxes, and select the edit menu thing, and say edit definitions or whatever, at the very bottom of the menu, and take a screenshot of the scalings.
as far as the problem with the column values, there is probably something wrong in one of those definition files. Each of those files says "this item" is located at "this location" with "these settings", so if part of that lil fake statement i just made is incorrect, it'll lookup the values in the wrong spot or wrong scaling. click one of those boxes, and select the edit menu thing, and say edit definitions or whatever, at the very bottom of the menu, and take a screenshot of the scalings.
I did review those vids, im watching them now as well haha but im not sure what part of the file is wrong here are some shots bro
Last edited by Mitsu.kid.02; Oct 4, 2010 at 07:56 PM.
Oct 5, 2010, 06:42 AM
#65
Evolved Member
Thread Starter
iTrader: (3)
Join Date: Jun 2010
Location: Boston MA
Posts: 1,087
Likes: 0
Received 0 Likes
on
0 Posts
So i started adjusting the low/high octane fuel maps by scaling them. I havent flashed it back to the ECU or anything, just getting a feel for ECUflash. Would it be ok to flash only the fuel maps back to the ECU that i scaled and start doing logs? or should i leave everything in ecuflash alone and do logging?
Oct 5, 2010, 06:47 AM
#66
There is one weird thing with the Lancers that you need to know ... many of them run primarily from the Low Octane maps. No clue why. Test it and see. And easy test would be to pull a bunch of timing at idle in one map and not the other and see what the car does in the logs.
Yes, you can just flash those minor changes back to the ECU. ECUFlash will only write the data blocks that have changed, so only the fuel maps, and other data in that "block" of the ROM will be written.
Changing the endian values will have no effect on the ROM as that is just for display of the maps on the PC.
Yes, you can just flash those minor changes back to the ECU. ECUFlash will only write the data blocks that have changed, so only the fuel maps, and other data in that "block" of the ROM will be written.
Changing the endian values will have no effect on the ROM as that is just for display of the maps on the PC.
Oct 5, 2010, 06:57 AM
#67
Evolved Member
Thread Starter
iTrader: (3)
Join Date: Jun 2010
Location: Boston MA
Posts: 1,087
Likes: 0
Received 0 Likes
on
0 Posts
There is one weird thing with the Lancers that you need to know ... many of them run primarily from the Low Octane maps. No clue why. Test it and see. And easy test would be to pull a bunch of timing at idle in one map and not the other and see what the car does in the logs.
Yes, you can just flash those minor changes back to the ECU. ECUFlash will only write the data blocks that have changed, so only the fuel maps, and other data in that "block" of the ROM will be written.
Changing the endian values will have no effect on the ROM as that is just for display of the maps on the PC.
Yes, you can just flash those minor changes back to the ECU. ECUFlash will only write the data blocks that have changed, so only the fuel maps, and other data in that "block" of the ROM will be written.
Changing the endian values will have no effect on the ROM as that is just for display of the maps on the PC.
Also my STFT or 02 sensor feedback is pegged at 24.80 all the time. and my LTFT high never moves from zero...is this normal? My aem when fully warm at idle car reads from 14.7 through 15.2 it moves back and forth slowly, When cruising it sweeps from 14.4 through 15.6 back and forth, when i decel it reads all the way lean, when i accel medium to hard it reads 11.2 then back up to the sweeping 14.4-15.6 sweeping. Is this normal?
Last edited by Mitsu.kid.02; Oct 5, 2010 at 07:35 AM.
Oct 5, 2010, 07:31 AM
#68
The way the maps SHOULD work is this ...
The ECU references the high octane maps when there is <3 knock count. When there is 3+ knock, the ECU pulls timing from the high octane map. If there is 6+ knock count, the ECU begins to interpolate the low octane maps values in with the high octane map values. the higher the knock, the lower the "octane" value and the more the interpolation with the low octane maps.
I have logged several Lancers that ran only on the maps marked low octane for fuel and timing. I even modified mt ROM data for a couple of them to "correct" it, but was told later that the disassembly was correct and the car really did run on the low octane maps. I believe I was also told that the Lancer never references the high octane maps, even under significant knock (which would happen if they were simply named incorrectly) ... but don't quote me on that.
The ECU references the high octane maps when there is <3 knock count. When there is 3+ knock, the ECU pulls timing from the high octane map. If there is 6+ knock count, the ECU begins to interpolate the low octane maps values in with the high octane map values. the higher the knock, the lower the "octane" value and the more the interpolation with the low octane maps.
I have logged several Lancers that ran only on the maps marked low octane for fuel and timing. I even modified mt ROM data for a couple of them to "correct" it, but was told later that the disassembly was correct and the car really did run on the low octane maps. I believe I was also told that the Lancer never references the high octane maps, even under significant knock (which would happen if they were simply named incorrectly) ... but don't quote me on that.
Oct 5, 2010, 07:54 AM
#69
Evolved Member
Thread Starter
iTrader: (3)
Join Date: Jun 2010
Location: Boston MA
Posts: 1,087
Likes: 0
Received 0 Likes
on
0 Posts
The way the maps SHOULD work is this ...
The ECU references the high octane maps when there is <3 knock count. When there is 3+ knock, the ECU pulls timing from the high octane map. If there is 6+ knock count, the ECU begins to interpolate the low octane maps values in with the high octane map values. the higher the knock, the lower the "octane" value and the more the interpolation with the low octane maps.
I have logged several Lancers that ran only on the maps marked low octane for fuel and timing. I even modified mt ROM data for a couple of them to "correct" it, but was told later that the disassembly was correct and the car really did run on the low octane maps. I believe I was also told that the Lancer never references the high octane maps, even under significant knock (which would happen if they were simply named incorrectly) ... but don't quote me on that.
The ECU references the high octane maps when there is <3 knock count. When there is 3+ knock, the ECU pulls timing from the high octane map. If there is 6+ knock count, the ECU begins to interpolate the low octane maps values in with the high octane map values. the higher the knock, the lower the "octane" value and the more the interpolation with the low octane maps.
I have logged several Lancers that ran only on the maps marked low octane for fuel and timing. I even modified mt ROM data for a couple of them to "correct" it, but was told later that the disassembly was correct and the car really did run on the low octane maps. I believe I was also told that the Lancer never references the high octane maps, even under significant knock (which would happen if they were simply named incorrectly) ... but don't quote me on that.
Ok cool i understand that. So it wouldnt hurt to have both the high octane and the low octane maps the way they are in the screen shot above right? Since if it might only work on the low octane map having the high octane map adjusted and scaled shoulnt make a difference right?
Also my STFT or 02 sensor feedback is pegged at 24.80 all the time. and my LTFT high never moves from zero...is this normal? My aem when fully warm at idle car reads from 14.7 through 15.2 it moves back and forth slowly, When cruising it sweeps from 14.4 through 15.6 back and forth, when i decel it reads all the way lean, when i accel medium to hard it reads 11.2 then slowly back up to the sweeping 14.4-15.6 sweeping. Is this normal?
Oct 5, 2010, 08:40 AM
#70
The High LTFT should be 0, yes. It will only move to correct in a closed loop situation with intake flow above 500hz I believe, which would be in boost and therefore in open loop. your LTFT Low and Mid trims should not be 0 and the O2 feedback should bounce around between -5 and 5.
Your WB should read between 14.5 and 15.2 at idle and light cruise. At WOT at any time you should be around 11.0 to 11.6 or so. You don't want to be above 12 or below 10 as that's where you really increase the chance of knock on pump fuel. When you let off the throttle (engine braking) there will be pure air in the system, so the sensor will peg to one side or read "02" maybe ... I don't deal with the AEM sensors much.
Oh, and I would still verify which map is being used, set it accordingly and then make the other map tamer as a backup, just in case.
Your WB should read between 14.5 and 15.2 at idle and light cruise. At WOT at any time you should be around 11.0 to 11.6 or so. You don't want to be above 12 or below 10 as that's where you really increase the chance of knock on pump fuel. When you let off the throttle (engine braking) there will be pure air in the system, so the sensor will peg to one side or read "02" maybe ... I don't deal with the AEM sensors much.
Oh, and I would still verify which map is being used, set it accordingly and then make the other map tamer as a backup, just in case.
Oct 5, 2010, 08:47 AM
#71
Evolved Member
Thread Starter
iTrader: (3)
Join Date: Jun 2010
Location: Boston MA
Posts: 1,087
Likes: 0
Received 0 Likes
on
0 Posts
The High LTFT should be 0, yes. It will only move to correct in a closed loop situation with intake flow above 500hz I believe, which would be in boost and therefore in open loop. your LTFT Low and Mid trims should not be 0 and the O2 feedback should bounce around between -5 and 5.
Your WB should read between 14.5 and 15.2 at idle and light cruise. At WOT at any time you should be around 11.0 to 11.6 or so. You don't want to be above 12 or below 10 as that's where you really increase the chance of knock on pump fuel. When you let off the throttle (engine braking) there will be pure air in the system, so the sensor will peg to one side or read "02" maybe ... I don't deal with the AEM sensors much.
Oh, and I would still verify which map is being used, set it accordingly and then make the other map tamer as a backup, just in case.
Your WB should read between 14.5 and 15.2 at idle and light cruise. At WOT at any time you should be around 11.0 to 11.6 or so. You don't want to be above 12 or below 10 as that's where you really increase the chance of knock on pump fuel. When you let off the throttle (engine braking) there will be pure air in the system, so the sensor will peg to one side or read "02" maybe ... I don't deal with the AEM sensors much.
Oh, and I would still verify which map is being used, set it accordingly and then make the other map tamer as a backup, just in case.
Oct 5, 2010, 10:34 AM
#72
There is one weird thing with the Lancers that you need to know ... many of them run primarily from the Low Octane maps. No clue why. Test it and see. And easy test would be to pull a bunch of timing at idle in one map and not the other and see what the car does in the logs.
Yes, you can just flash those minor changes back to the ECU. ECUFlash will only write the data blocks that have changed, so only the fuel maps, and other data in that "block" of the ROM will be written.
Changing the endian values will have no effect on the ROM as that is just for display of the maps on the PC.
Yes, you can just flash those minor changes back to the ECU. ECUFlash will only write the data blocks that have changed, so only the fuel maps, and other data in that "block" of the ROM will be written.
Changing the endian values will have no effect on the ROM as that is just for display of the maps on the PC.
Oct 5, 2010, 11:25 AM
#73
No. If you're not using an OEM base ROM, this most likely does not apply. The Tephra Evo ROM should work just like it does on the Evo. The Tephra/RoadSpike ROM for the auto Lancer should also work as intended, but I can't be 100% on that. I'll know Thursday when I tune Daniel's beast.
Oct 5, 2010, 11:35 AM
#74
Evolved Member
Thread Starter
iTrader: (3)
Join Date: Jun 2010
Location: Boston MA
Posts: 1,087
Likes: 0
Received 0 Likes
on
0 Posts
It does stay at 24.80 all the time, ill logg tonite and just make sure, as well as test to see what map the car reads off of, by pulling timing at idle right? will that mess/ hurt my car? like how many degrees would i be able to do
Last edited by Mitsu.kid.02; Oct 5, 2010 at 11:44 AM.
Oct 5, 2010, 12:14 PM
#75
No, pulling timing at idle won't hurt the car ... it'll just make it run like crap. Set it to -5º in the idle area to test ... that should be fine. And, if you are worried, I'd suggest setting the high octane map to -5º. If I'm right, then it won't change how the car idles at all.
