Notices
ECU Flash

94170008 ROM 2 byte load mod for dummies (like me :)

Thread Tools
 
Search this Thread
 
Old May 24, 2007 | 01:57 PM
  #31  
mchuang's Avatar
Evolved Member
iTrader: (11)
 
Joined: Sep 2005
Posts: 2,180
Likes: 1
From: h town
Originally Posted by klatinn
Actually, LW3 has a better method than that.
Go to Tools->Marker Lines->Channel name in the log window. You will see 2 movable marker lines. Each channel has its own set but only the set of one channel is shown at a time. But their position for each channel is preserved. You can move them to whatever point in the scale by grabbing them with the triangular handle on the right end of the line and moving them up and down.
A shortcut to invoke the marker lines is to click on the channels current value in the measurement pane to the right of the graph pane. Clicking on the empty area below the measurements in the pane switches marker lines off.

As for scales. Using the magnifier tool on the scale of a trace itself allows you to "magnify" the scale of a trace to your liking to see details. You can then move the channel trace or scale up and down with the hand tool.

Another LW3 trick:
To get your log data into for example excel, select the area in the log you want to copy. Select Edit->Copy in the log window. Then open Excel (or whatever, including a text editor) and click on the upper left cell you want the log data to be in. Select Edit->Paste and you are done.


- Klaus
Thx Klaus, logworks 3 so far so good. Is the 2nd beta version of logworks 3 out yet.
Reply
Old May 24, 2007 | 02:47 PM
  #32  
klatinn's Avatar
Newbie
 
Joined: Jan 2007
Posts: 28
Likes: 0
Originally Posted by mchuang
Thx Klaus, logworks 3 so far so good. Is the 2nd beta version of logworks 3 out yet.
No, sit tight. Either today or Monday. Still fixing some very strange bugs and working around some Windows bugs on some computers.

Re) 2 Byte load. The spikes are an inherent problem with the way 2 Byte values are read. Nothing prevents the ECU from updating the 2 Byte value in between the low and high byte read. There are principally 3 ways to fix that:

1. Change the ECU code so it does not update the value between a for example low and high byte read.

2. In the logger code, throw away sample values that differ by bigger than x amount from the previous sample. Probably the current solution in some loggers. Has the disadvantage that if the value hovers around 0xxxFF, a lot of samples can be thrown away.

3. Change the way 2 Byte values are stored in the ECU from straight binary to grey-code. This has the advantage that resulting errors from non-atomic reads stay small.

- Klaus
Reply
Old May 24, 2007 | 05:13 PM
  #33  
Jorge T's Avatar
Evolved Member
iTrader: (18)
 
Joined: May 2004
Posts: 1,494
Likes: 1
From: Houston, TX
Excel is your friend...no more spike

Attached Thumbnails 94170008 ROM 2 byte load mod for dummies (like me :)-no-spike.png  
Reply
Old May 24, 2007 | 08:36 PM
  #34  
C6C6CH3vo's Avatar
Evolved Member
iTrader: (9)
 
Joined: Feb 2005
Posts: 4,223
Likes: 4
From: sc
I've seen that rich spot near 7000 rpm on another log before, is that intentional? I try to keep mine the same from 5000 on up which is OK I guess

The rich spot at peak happens to me to however, good to see another log with the resolution I'm used to - I was wondering if others had this
Reply
Old May 24, 2007 | 08:54 PM
  #35  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
Originally Posted by C6C6CH3vo
I've seen that rich spot near 7000 rpm on another log before, is that intentional? I try to keep mine the same from 5000 on up which is OK I guess

The rich spot at peak happens to me to however, good to see another log with the resolution I'm used to - I was wondering if others had this
I do that too. I dip the AFR to 10.9:1 @ peak boost and then hold it steady @ 11:1 until 7000 rpm. After than I dip it to 10.9-10.8:1. That is done on 91 octane gas.
Reply
Old May 24, 2007 | 09:47 PM
  #36  
C6C6CH3vo's Avatar
Evolved Member
iTrader: (9)
 
Joined: Feb 2005
Posts: 4,223
Likes: 4
From: sc
Here is 2 byte load (thanks jscbanks and others)

My dip in AFR is much more pronounced, but notice how it all follows suit with MAF, load, and IPW - IPW and AFR kind of mirror each other too

Finally can see the actual load the ECU uses If you rotate the load 90 deg and superimpose (on scale) to the map I bet you can have a good idea of the trail the ECU used




I also get a log of loadmsb and lsb that I have to hide, is that normal?

Also, am I supposed to have to use the math calc to get 2 byte every log - doesn't do it automatic (I know, stupid question)?

Timing doesnt look so blocky now

Last edited by C6C6CH3vo; May 24, 2007 at 10:04 PM.
Reply
Old May 25, 2007 | 06:41 AM
  #37  
Jorge T's Avatar
Evolved Member
iTrader: (18)
 
Joined: May 2004
Posts: 1,494
Likes: 1
From: Houston, TX
Originally Posted by C6C6CH3vo
I've seen that rich spot near 7000 rpm on another log before, is that intentional? I try to keep mine the same from 5000 on up which is OK I guess

The rich spot at peak happens to me to however, good to see another log with the resolution I'm used to - I was wondering if others had this
The day I made that datalog was Hot and very humid and was after my work cummute in stop N go traffic. I have observed that if I get 1-2 counts of knock after 7000 rpm it will get .3-.5richer before timing gets pulled. Target AFR is 11.1-11.0 after 7000rpm . I also have not touched the leanspool, it also could have something to do with it.

I've always seen the richspot at peak load as fuel compensation caused by load/boost spike. The higher the spike the higher the dip and viceversa.
Reply
Old May 25, 2007 | 07:22 AM
  #38  
mchuang's Avatar
Evolved Member
iTrader: (11)
 
Joined: Sep 2005
Posts: 2,180
Likes: 1
From: h town
Originally Posted by Jorge T
The day I made that datalog was Hot and very humid and was after my work cummute in stop N go traffic. I have observed that if I get 1-2 counts of knock after 7000 rpm it will get .3-.5richer before timing gets pulled. Target AFR is 11.1-11.0 after 7000rpm . I also have not touched the leanspool, it also could have something to do with it.

I've always seen the richspot at peak load as fuel compensation caused by load/boost spike. The higher the spike the higher the dip and viceversa.
When I disable lean spool by changing the address so that the start and stop rpm is at 1500 my car feels slower and I didnt notice too much change in air fuel. With it enabled the car feels better so I changed it back.
Reply
Old May 25, 2007 | 08:36 AM
  #39  
klatinn's Avatar
Newbie
 
Joined: Jan 2007
Posts: 28
Likes: 0
Hi Jorge T,

Just as a suggestion:
If you have knock counts at ~7000 RPM you are probably over-advanced in the first place in that area. Your VE is on the way down because you are past the torque peak, where mixture density and peak cyl. pressure is highest (therefore highest knock probability).

As a general observation:
Many OEM Turbo cars run very rich at WOT, with the Evo being a good example.
These rich mixtures create less cylinder pressure, burn cooler and result in lower EGTs, but cost power. The reasons OEMs are doing them anyway are threefold:

1. Head cooling. If the head does not have adequate cooling, valves can overheat at sustained high RPM/loads.

2. Plug cooling. The plugs have to also work at low/idle loads. A plug with the correct heat range for sustained high RPM/load would be too cold and load up at idle/cruise.

3. Cat overheat prevention.
The most common reason. Sustained high RPM high load at the AFRs for max power would melt down the cat.

Depending on how your car is used you can possibly get more power by leaning out a little and retarding the timing a little at high RPM. Though this is not recommenended if you run the car in Germany on the Autobahn or track it (road racing). Leaner mixtures burn faster and require less ign. advance. The burn speed of gasoline has a max between 12 and 13 AFR. Leaner or richer causes slower burns and require therefore more advance. But the resulting power output is less if more advance is needed for several reasons. One of which is more "negative" torque from the pressure buildup BTDC.
BTW, contrary to popular belief, EGTs and CHTs max out at stoich (14.7) and fall off steeply when leaner than that. The AFRs with max knock probability for most engines is between 13 and 15.

- Klaus
Reply
Old May 25, 2007 | 08:47 AM
  #40  
Jeff_Jeske's Avatar
Evolved Member
iTrader: (66)
 
Joined: Jan 2003
Posts: 4,358
Likes: 7
From: On the track
How many of you are actually seeing a noteworthy difference between the 1 byte and 2 byte loads? Mine appear to be soo close that it doesn't really matter which one I look at.

As for AFR tuning ..... I actually like the lean spool as it does work and I see no knock even though my AFR is 12.X:1 through 4000 rpm. I like the fairly lean peak torque and fatter (10.8:1) topend.
Reply
Old May 25, 2007 | 09:35 AM
  #41  
mrfred's Avatar
EvoM Guru
iTrader: (50)
 
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Originally Posted by Jeff_Jeske
How many of you are actually seeing a noteworthy difference between the 1 byte and 2 byte loads? Mine appear to be soo close that it doesn't really matter which one I look at.

As for AFR tuning ..... I actually like the lean spool as it does work and I see no knock even though my AFR is 12.X:1 through 4000 rpm. I like the fairly lean peak torque and fatter (10.8:1) topend.
1 byte load (ECUload) only goes to 160. CalcLoad is based on 1 byte values (IPW, etc). I see a ~10% difference between CalcLoad and 2-byte load at low rpm, and at higher rpm, the gap narrows.
Reply
Old May 25, 2007 | 10:21 AM
  #42  
C6C6CH3vo's Avatar
Evolved Member
iTrader: (9)
 
Joined: Feb 2005
Posts: 4,223
Likes: 4
From: sc
Originally Posted by Jeff_Jeske
How many of you are actually seeing a noteworthy difference between the 1 byte and 2 byte loads?
The big difference is knowing your on target with map changes, one column off on a cell is (load calc) devestating to accuracy imo. I'm just impressed with how close Jack's math was with the actual load
Reply
Old May 25, 2007 | 10:36 AM
  #43  
nj1266's Avatar
Evolved Member
iTrader: (6)
 
Joined: Nov 2004
Posts: 3,254
Likes: 13
From: USA
Originally Posted by Jeff_Jeske
How many of you are actually seeing a noteworthy difference between the 1 byte and 2 byte loads? Mine appear to be soo close that it doesn't really matter which one I look at.
They are close, but it does make a difference. Check this out. The chart below is 2 byte load on top and CalcLoad on bottom. It is an average of 4 runs @ 20 psi. With LW you can average more than one run for more consistent tuning. Notice that the CalcLoad is one load cell off in some areas from the 2 byte load. If you tune all your WOT load cells, then that doea not matter, but if you tune one load cell @ a time, then that will make a huge difference.

Attached Thumbnails 94170008 ROM 2 byte load mod for dummies (like me :)-2byteload_loadcalc.gif  
Reply
Old May 25, 2007 | 10:46 AM
  #44  
Jorge T's Avatar
Evolved Member
iTrader: (18)
 
Joined: May 2004
Posts: 1,494
Likes: 1
From: Houston, TX
I think he means the calc load method vs the 2 byte load
Reply
Old May 25, 2007 | 11:00 AM
  #45  
Jorge T's Avatar
Evolved Member
iTrader: (18)
 
Joined: May 2004
Posts: 1,494
Likes: 1
From: Houston, TX
Originally Posted by klatinn
Hi Jorge T,

Just as a suggestion:
If you have knock counts at ~7000 RPM you are probably over-advanced in the first place in that area. Your VE is on the way down because you are past the torque peak, where mixture density and peak cyl. pressure is highest (therefore highest knock probability).

As a general observation:
Many OEM Turbo cars run very rich at WOT, with the Evo being a good example.
These rich mixtures create less cylinder pressure, burn cooler and result in lower EGTs, but cost power. The reasons OEMs are doing them anyway are threefold:

1. Head cooling. If the head does not have adequate cooling, valves can overheat at sustained high RPM/loads.

2. Plug cooling. The plugs have to also work at low/idle loads. A plug with the correct heat range for sustained high RPM/load would be too cold and load up at idle/cruise.

3. Cat overheat prevention.
The most common reason. Sustained high RPM high load at the AFRs for max power would melt down the cat.

Depending on how your car is used you can possibly get more power by leaning out a little and retarding the timing a little at high RPM. Though this is not recommenended if you run the car in Germany on the Autobahn or track it (road racing). Leaner mixtures burn faster and require less ign. advance. The burn speed of gasoline has a max between 12 and 13 AFR. Leaner or richer causes slower burns and require therefore more advance. But the resulting power output is less if more advance is needed for several reasons. One of which is more "negative" torque from the pressure buildup BTDC.
BTW, contrary to popular belief, EGTs and CHTs max out at stoich (14.7) and fall off steeply when leaner than that. The AFRs with max knock probability for most engines is between 13 and 15.

- Klaus
Thanks for the suggestions and information, I will start leaning out AFR since I do not run at WOT in the autobahn and don't track the car(if I ever do i'll flash a richer map) . I have since reduced timing in the adjacent cell (lower load) in the 7000 rpm row and above , for now it seemed to squench all traces of knock.
Reply



All times are GMT -7. The time now is 03:17 PM.