ECMTuning - wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

<h1>A Word about the AEM WB Sensors</h1> <div class="level1"> <p> I want to state up front that we here at ECMTuning do not particularly care for the AEM WB kits. Of all the kits we support for datalogging purposes, customers seem to have FAR more problems getting the AEM WB kit to log correctly than any other kit out there. The problem is that there are several different "versions" of the AEM WB kit and very few seem to produce output voltages that actually match the documented figures. </p> <p> That's why you'll find several different "goofy looking" AEM WB options listed inside ECMLink for datalogging and that's why we have a page here dedicated specifically to the AEM WB. It's just such a nightmare to support this kit that we have even given passing thought to dropping support for it entirely. The update rate is horrible (or at least it used to be…I believe their latest kit listed below is actually a good bit better about this), the driver circuitry is weak and the output voltages rarely match what they are supposed to. So it's just a really undesirable WB kit for a number of reasons. </p> <p> But, we don't really plan on dropping support for it because as bad as it is for datalogging, it seems to be the WB kit of choice for a large number of people. Just keep in mind if you buy one of these WB kits and plan to datalog it with your DSM ECU, you may find that you have to spend a good bit of time getting it working right. </p> </div> <h1>AEMWB Logging Suggestion</h1> <div class="level1"> <p> A number of people have various problems with the AEMWB display routine. There are a number of reasons for this, but most seem to revolve about the AEM's weak analog driver circuitry. It's simply unable to properly drive a number of ECU inputs. </p> <p> One fix is to buffer the ECU input with <a href="http://www.ecmtuning.com/product_info.php?cPath=26&products_id=39" class="urlextern" title="http://www.ecmtuning.com/product_info.php?cPath=26&products_id=39" rel="nofollow">one of these</a>. In doing so, the AEM is not required to drive the ECU input directly. </p> <p> People still seem to get varying results, though. So another fix is to simply not use the built-in AEM WB display routines and instead define your own using the <a href="/wiki/doku.php?id=linearitems" class="wikilink1" title="linearitems">LinWideband display item</a>. To use that, you change the pin assignment to be Linear wideband and then manually adjust the mapping. </p> <p> One user found the following settings to work well on his own AEM WB install: </p> <pre class="code">Min Voltage: 0.0 Min lambda: 0.65 (gasoline A/F ratio of 9.55:1) Max Voltage: 4.99 Max lambda: 1.32 (gasoline A/F ratio of 19.43:1) </pre><p> </p> <p> AEM has now come out with yet another mapping with their 30-5130 gauge (at least this gauge seems to have a separate analog ground, the brown wire, that should be connected to ECU sensor ground to improve the ability of the WB to deliver accurate voltage readings to the ECU): </p> <pre class="code">Min Voltage: 0.50 Min lambda: 0.578 (gasoline A/F ratio of 8.50:1) Max Voltage: 4.50 Max lambda: 1.224 (gasoline A/F ratio of 18.00:1) </pre><p> </p> <p> Newer versions of the ECMLink PC app have this gauge loggable with this mapping as AEMAnalogWB. </p> </div>