[Gmecm] DFCO and EGR elimination

Wed Aug 15 00:06:00 UTC 2007

>Forgot to ask. What didn't/don't you like about $58?

>Robin

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.

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.

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.

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.

The v18 feature list is below.  Current dev version is 24, with some neat stuff coming.

Later,

Dig

---------------------------
Features of version 18:

WB Brand selection

   - The code expects the WB sensor voltage to be present on pin F14 (i.e. MAP2)

   - Bit 0 : DIY / TechEdge v1.0 Sensor Nonlinear Output - Uses Table

   - Bit 1 : FJO Nonlinear Output - Uses Table

   - Bit 2 : AEM Nonlinear Output - Uses Table

   - Bit 3 : TechEdge v2.0 Linear Output - Uses Formula  [AFR = (Volts * 2) + 9]

   - Bit 4 : PLX Linear Output - Uses Formula [AFR = (Volts * 2) + 10]

   - Bit 5 : Innovate Linear Output - Uses Formula [AFR = (Volts * 2) + 10]   

   - Bit 6 : AEM Linear Output - Uses Formula  [AFR = (Volts * 2) + 10]

   - Bit 7 : Zeitronix (Nonlinear Output - Uses Table)

      - Second WBo2 Sensor Setting

        - Bit 7 : RAW - Raw output of Voltage, Use formula in TunerPro to display AFR.  DO NOT USE WITH WIDE BAND O2 FUELING FLAGS TURNED ON

Closed Loop WBo2 Fueling(Not active when in PE)

   - AFR High setting

   - AFR Low Setting

   - Sensor Ready Delay, amount of time to delay before WBo2 Closed Loop code is active 

16x32 VE Table F29x covering (400-6400 RPMs, and 0 - 300 kPa (30psi))

F70_MPH - Change table from TPS% to MPH based.  

F71_MPH - Change table from TPS% to MPH based. Helps to reduce boost spiking in 3rd/4th gear.

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

F29x Table Only - No longer use F29c (Closed Throttle Table) at idle

Expanded Boost Multipler F77x Table - Covers a wider range of 84 - 292 kPa

Updated BARO LOGIC

V8 EGR Fix

----- Original Message ----

From: Rob Handley <Robin at FuryWorld.fsnet.co.uk>

To: gmecm at diy-efi.org

Sent: Tuesday, August 14, 2007 5:51:02 PM

Subject: Re: [Gmecm] DFCO and EGR elimination

Forgot to ask. What didn't/don't you like about $58?

Robin

----- Original Message ----- 

From: "Dig" <turbodig at yahoo.com>

To: <gmecm at diy-efi.org>

Sent: 14 August 2007 23:22

Subject: Re: [Gmecm] DFCO and EGR elimination

A group of us  (don't know how many of them are reading here)  started a 

project to update/fix things we didn't like in $58. $59 was the most clever 

name we could come up with.

Bruce had started a similar project years back ($60), but it never really 

caught hold. This is different from his effort.

One of the features, as Bill brings up, is WB o2 control of non PE/AE/DE 

fueling. It works pretty good, thanks to Don's hard work, although it does 

require you to have a *fairly* close tune. (WB control loop kinda freaks, 

otherwise)

You may download/join for free at www.code59.org. The xdf files and other 

tools are there as well.

The only thing that we ask, per the license, is that if you use it, you must 

post your tune back to the board. The idea being, that somewhere along the 

line, someone will need something similar, and can use your tune as a 

starting point. It's intended to be free for all.

Last big disclaimer, since it seems to offend some:  The xdfs and code is 

set up for a 3 bar map. A number of people seem to have concerns about the 

driveability of the 3 bar sensor, but we don't have any problems with it in 

the field. To each their own.

Really last big disclaimer:  This is a work in progess. We haven't observed 

any major bugs, but that doesn't mean there aren't any.

Later,

Dig

www.code59.org

_______________________________________________

Gmecm mailing list

Gmecm at diy-efi.org

Subscribe: http://lists.diy-efi.org/mailman/listinfo/gmecm

Main WWW page: http://www.diy-efi.org/gmecm