[Gmecm] DFCO and EGR elimination

Rob Handley Robin
Wed Aug 15 08:53:32 UTC 2007


<SNIP>
Where to begin?  There's lots of stuff that's hard to use. Also, more than a 
few outright bugs in the code.
Example:  The VE tables are unnecessarily complex.  We've weeded the 3 
tables (F29,F29C,and F30) down to one. (F29x).
You can select which of the 3 you want to use or not use.
</SNIP>

I like the simplicity of that.

<SNIP>
Bug example: Baro is weird. I've got some stuff that I'm working on for the 
next release that should fix some of the oddness.
</SNIP>

I don't understand the relationship between BARO, VACUUM and MAP. I got as 
far as generating this plot: http://213.162.107.39/misc/MAP_Vac_Baro.gif 
last year - but I couldn't explain it. I had bigger (mechanical) engine 
problems at the time so moved on. I had thought that BARO was just the MAP 
reading before the engine started - to provide a reference pressure so that 
atmospheric pressure variation could be compensated for. (BARO seems to be 
constant in the plot.) I had also thought that VACUUM was atmospheric 
pressure (BARO) minus MAP - but the plot conflicts with that. You've got me 
worried that there's a problem waiting to bite me that I don't know about...

For fuel adjustment I was planning to _only_ use:
F29, F29E, F30, F61, F21, F22, F31M, F56, and F57.

The pressure indexed ones seem to all use MAP, so I had thought that I 
didn't need to worry about VACUUM and BARO. Am I horribly wrong? What does 
your updated BARO logic do differently?

<SNIP>
Another bug example:  ALDL comm routine was disabling receives during the 
"off" time that the scheduler wasn't sending heartbeat messages. Turning 
this back on make ALDL comm sooooo much easier. You can just send it a byte 
to shut up now, vs. having to play games with timing the packet.
</SNIP>

The $58 ALDL is definitely a pain to shut the chatter up. Is that the 
problem that you've fixed? It also seems to 'glitch' like I never saw with 
$8D ALDL.

<SNIP>
There's still other things to fix (Mode 2 doesn't work right, the 
long-standing freak BPW and VE data in the data stream, etc), but we keep 
whacking away at it.
<SNIP>

I've never tried Mode 2. I thought I might remap Mode 1 to give me what I 
want.

What's the long-standing freak BPW and VE data? This sounds worrying...

<SNIP>
Updated ALDL Outputs
   - Actual AFR
   - Desired AFR
   - AE/DE/PE/DFCO Flags
   - $3f map variable (Real 3 Bar Map Variable, used by F29x, F29_AFR)
   - $3e Filtered Map
</SNIP>

It would be great to have AE/DE/PE/DFCO flags in the ALDL. ATM I don't even 
know where these exist in the code. Any pointers would be GREATLY 
appreciated!

$3F & $3E ?

Do you have a complete list of bugs/code fixes documented somewhere? That 
could really help me over the next few months. The only other one that I 
know about is the CLRA at $D0BC which forces the 600 RPM row of the main SA 
table to be used when it really shouldn't. I've put a NOP there which seemed 
to kill off the popping.

Many thanks,

Robin 





More information about the Gmecm mailing list