The AEM 30-0334 OBDII X-Series Wideband for FlashScan V2 is finally available,

Hi All.

AEM has finally introduced the new 30-0334 version of their OBDII enabled wideband ( Formerly, the 30-0333 ) that supports single and dual widebands in FlashScan V2. This is based on the re-flash code that has been tested over the last few months. So, the x-series widebands can now connect, directly, via the OBDII connector, as opposed to using the 0-5v analog outputs. On CAN enabled vehicles. This is a HUGE improvement.

The new EF1 and EF2 PID settings allow for two widebands to share the same OBDII connector via a master/slave configuration. This bit of tech has been the source of the delays. The single-wideband-only version was just completing testing when the new dual-wideband capable version was 1st introduced. So, fun fun fun, we got to start all over. But, definitely worth it, if you want to monitor 2 banks.

Beware that there are still some of the older 30-0333 units ( that only really support brand"H" scanners ) in the pipe. So, be sure that you get the newer part number. In case there is any confusion, I received the following info from the AEM guys:
"The two units can be distinguished via the hold-both-buttons-while-applying-power boot-up message (0333 vs 0334) or a PN decal on the rear of the unit. "

If you get them directly from AEM, I'm pretty sure you will get the correct 30-0334. Not sure what dealer/distributor stock look like, at the moment.

http://www.aemelectronics.com/files/...ller-Gauge.pdf

Attachment 21297

It was fun getting this to work. I hope it helps :)

Thanks Dr. Mike! Appreciate your help and diligence working to get this done for EFILive customers like me!

Thanks dr.mike :cheers:

Quote:

---

Originally Posted by dr.mike

...

Attachment 21297

It was fun getting this to work. I hope it helps :)

---

After you select the AEM UEGO Bank1 for the trans controller, you then use the pids GPM.WO2S11 and GMP.WO2S21.

Here is my sample file UserCalculatedPids.ini that uses both AEM -334 widebands, the BEN pid selects the leanest bank on the fly

( that file was generated and saved from within the V8 pid editor ( go Scan->Config->Calculated Pids, create a Group (upper pane), create a Pid (lower pane) ) )

we initially/briefly tested this using dr.mike's -334's at AEM (Hawthorne) using Martin's 2010 Camaro (CPR Engines, Gardena)

( dr.mike edited the AEM embedded firmware to make dual AEM's communicate with FSV2, to understate what he did )

Code:

---

[Groups]
GLOBAL=Global Functions
WO2SER=Wide Band O2 Sensors (Serial-Comms)
WO2CAN=Wide Band O2 Sensors (CAN-bus)

[GLOBAL]
FUNCTION="Global Functions",factor,0

[GLOBAL.FUNCTION]
0=|-- GLOBAL.FUNCTION
1=|function iff(x,y,z)
2=|if (x) then return y else return z end
3=|end

[WO2SER]
WO2BEN="Base Efficiency Numerator (Serial-Comms)(Dynamically-Leanest)",factor,3

[WO2SER.WO2BEN]
0=|-- WO2SER.WO2BEN
1=|return iff(pid("WO2LAM1")>pid("WO2LAM2"),pid("WO2LAM1"),pid("WO2LAM2"))*pid("EQIVRATIO")

[WO2CAN]
WO2BEN="Base Efficiency Numerator (CAN-bus)(Dynamically-Leanest)",factor,3

[WO2CAN.WO2BEN]
0=|-- WO2CAN.WO2BEN
1=|return iff(pid("WO2S11")>pid("WO2S21"),pid("WO2S11"),pid("WO2S21"))/pid("EQ_RAT")



---

note that the pid EQ_RAT is SAE.LAMBDA on E38, E67, E92.

Quote:

---

Originally Posted by joecar

note that the pid EQ_RAT is SAE.LAMBDA on E38, E67, E92.

---

And the E40

Quote:

---

Originally Posted by joecar

Here is my sample file UserCalculatedPids.ini that uses both AEM -334 widebands, the BEN pid selects the leanest bank on the fly

( that file was generated and saved from within the V8 pid editor ( go Scan->Config->Calculated Pids, create a Group (upper pane), create a Pid (lower pane) ) )

we initially/briefly tested this using dr.mike's -334's at AEM (Hawthorne) using Martin's 2010 Camaro (CPR Engines, Gardena)

( dr.mike edited the AEM embedded firmware to make dual AEM's communicate with FSV2, to understate what he did )

Code:

---

[Groups]
GLOBAL=Global Functions
WO2SER=Wide Band O2 Sensors (Serial-Comms)
WO2CAN=Wide Band O2 Sensors (CAN-bus)

[GLOBAL]
FUNCTION="Global Functions",factor,0

[GLOBAL.FUNCTION]
0=|-- GLOBAL.FUNCTION
1=|function iff(x,y,z)
2=|if (x) then return y else return z end
3=|end

[WO2SER]
WO2BEN="Base Efficiency Numerator (Serial-Comms)(Dynamically-Leanest)",factor,3

[WO2SER.WO2BEN]
0=|-- WO2SER.WO2BEN
1=|return iff(pid("WO2LAM1")>pid("WO2LAM2"),pid("WO2LAM1"),pid("WO2LAM2"))*pid("EQIVRATIO")

[WO2CAN]
WO2BEN="Base Efficiency Numerator (CAN-bus)(Dynamically-Leanest)",factor,3

[WO2CAN.WO2BEN]
0=|-- WO2CAN.WO2BEN
1=|return iff(pid("WO2S11")>pid("WO2S21"),pid("WO2S11"),pid("WO2S21"))/pid("EQ_RAT")



---

note that the pid EQ_RAT is SAE.LAMBDA on E40, E38, E67, E92.

---

I just want to point out that ALL 30-0334 have this "tweaked" firmware that dr. mike developed for AEM. So there is nothing that needs to be modified on a true 30-0334 AEM UEGO wideband, it will support this Calc.PID out of the box.

30-0333 units will NOT support this.

Does this WB have an output for non can vehicles, or is it only for the later model PCM's? I need a WB, but don't plan to try to do anything with a can vehicle currently.

Answered my own question. I guess I read thru the info too fast, and didn't see.......:mrgreen:

Is this AEM Wideband compatible with the LS1B 411 PCM?

I should have asked this before I ordered it I guess......

Attachment 21588

IIRC the 411 PCM is J1850 protocol, not CAN protocol. So, the direct OBDII interface connection will not work; unless the scanner can read 2 different protocols at once. Maybe this is possible ? If not, you would need to connect via to analog 0-5v signal. The 0-5v signal is available on the 30-0334. But, the pins for it are not installed in the connector. The pins are available for a few pennies, from DIGIKEY. ( of course, the shipping always gets you ).

Fortunately, the 0-5v signal on the 30-0334 is very good; with active ground offset error compensation. For the future, the 30-0300 is a better choice for non-CAN based PCMs; as it has the pins/wires for the 0-5v and serial signals included in the wiring harness. Otherwise, they are identical, except for the OBD2 firmware changes.

It would totally rock, if the scanner could read the J1850 and CAN protocols, simultaneously.

Otherwise, I may try to make a J1850/CAN bridge interface.

Quote:

---

Originally Posted by Scatfish

Does this WB have an output for non can vehicles, or is it only for the later model PCM's? I need a WB, but don't plan to try to do anything with a can vehicle currently.

Answered my own question. I guess I read thru the info too fast, and didn't see.......:mrgreen:

---

The 0334 supports CAN-bus as used on later model vehicles (from 2007+)... i.e. does not support J1850 VPW (what 0411 uses).

The 0334 also has analog 0-5V output, see what dr.mike says about it.

It does not have serial comm output.

Thanks. I made a hasty decision, but was able to cancel the order for the 0334. Is the 0333 the best choice for the non CAN (0411 and similar) PCM's in your opinion?

Thanks for the info....I'm trying to get started logging and trying to tune my truck.

Quote:

---

Originally Posted by Scatfish

Thanks. I made a hasty decision, but was able to cancel the order for the 0334. Is the 0333 the best choice for the non CAN (0411 and similar) PCM's in your opinion?

---

Yes, if you never plan on an E38/E67/E92 (i.e. CAN-bus) vehicle.

The 30-0300 is the one with all of the non-CAN functions available on the wiring harness. The old 30-0333 is the same as the 30-0334, but without the updates for EFILive. (i.e. mostly, for "brand H" scanners )

ok, just to be clear:
30-0300: analog 5V, serial comm.
30-0333: analog 5V, serial comm, CAN-bus (EFILive can read only one 0333 on the CAN-bus)(HPT can read two 0333's).
30-0334: analog 5V, CAN-bus, dual cascade-able for EFILive (EFILive can read two 0334's on the CAN-bus).

almost:

30-0300 is the original part. Its CANBus interface is used for AEMNet communication. It has wires on the harness for 0-5v and serial data. It has CAN wires. But they are NOT programmed to do OBDII. It is, usually, the cheapest.

30-0333 The 1st OBDII compatible unit. Worked mostly with HPTuners. Ships without the pins for 0-5v and serial installed in the harness. I need to double-check if the serial data function is present. I know the 0-5v is there.

30-0334 An updated version of the 30-0333 that adds support for EFILive . It allows for the dual channel mode.

There was an interim development version of the EFILive compatible unit that was never released. It was the one that only supported a single channel. The dual chan mode is a bit of a trick. Hence, the delay getting it out there.

If you don't have a CAN based PCM ( and dont plan to get one ), get the 30-0300 for the complete wiring harness. The 0-5v output is, actually, excellent. The active ground offset compensation all of these WBs more accurate than any non-compensated units. But, then, the subject of WB ground offsets deserves its own thread :)

dr.mike, thanks :rockon:

Thanks dr.mike, and you too joecar!

I'll order the 30-0300, unless you would recommend a different WB since I'm not tuning any CANBus vehicles at this point. I'm just trying to tune a spare truck, and then my Camaro, both which are 0411 swaps.

Yes. The 30-0300 makes the most sense, in that case. Or, the 30-0310, if you don't want the gauge. In either case, you get the fast response time, and, the corrected analog 0-5v signal.

Dr. Mike I have a few questions for you regarding this topic and sent you a message last night. I have everything connecting to monitor 1 sensor however the pids are extremely slow to respond. While trying to monitor the data I have to hold the mouse over the PID for the numbers to change. I have no doubt that I am missing a setting or have something configured wrong but just dont know what it is. I have checked all the settings I read about and everything looks correct. Im hoping you or someone else on this thread has some step by step instructions on making this sensor function with EFI Live so I can log this truck. Thank you in advance for any help.

Dr Mike , I can’t seem to make the calculated pid for the 30-300 show up on 7.5 scan tool . What am I doing wrong? I the calculated pid text in the folder but it doesn’t show up when I open the scanner . Just the pre loaded units are in there.

Is it possible to use the 0334 with Swingtans E38 VVE dial in guide cant seem to get all the pid's I need to work.

Quote:

---

Originally Posted by articSS

Dr Mike , I can’t seem to make the calculated pid for the 30-300 show up on 7.5 scan tool . What am I doing wrong? I the calculated pid text in the folder but it doesn’t show up when I open the scanner . Just the pre loaded units are in there.

---

See the other thread where I posted a reply...

you have an AEM 03-300 which is not the same as the 03-333/03-334.

Quote:

---

Originally Posted by watts5ive

Is it possible to use the 0334 with Swingtans E38 VVE dial in guide cant seem to get all the pid's I need to work.

---

Yes it is...

post screenshots...

Can anyone recommend a retailer for the 0334 with delivery to Victoria Australia?

I found them for sale locally at carmods Australia for anyone interested.

Hi guys, i have successfully installed my new 30-0334 and got it working in the car (2016 VFII Redline Commodore) and have also added the WBO2 into EFILive scan and tune using the instructions that came with the gauge under the F2: Scan icon.
My problem is that when i select my PID list to program to the FSV2 in BBX, the AFM WO2S11 PID under GPM-Generic is not available for me to add to my PID list and program to the FSV2, so i can't log the AFR.
Any suggestions?

So, here are a couple of screen shots to help explain what i am trying to achieve.

https://www.dropbox.com/s/3rb9nsbcyu...03.07.png?dl=0

When i select my E38 controller as in the screenshot above, i cannot select the PID from the AEM controller and combine the two to get the AEM WBO2 in with the rest of the PID's of the E38, to then program to the FSV2.

https://www.dropbox.com/s/6mcgj1dix8...03.30.png?dl=0

You need to double click the E38 under the "BBL Enabled Controllers" and add the AEM WB02 as the TCM. It should show as "E38&AEM" under the "Modules" column. In your screenshots, you have the E38 setup as one controller and AEM as a 2nd controller, they must be setup as a single controller (think of it as an automatic vehicle with E38 as ECM and AEM as TCM).

Thanks scarab, I will give that a shot after work tonight.

OK, so i took Scarab's suggestion and made a test list of PID's to log (thanks Scarab), the problem i now have is that the AEM is reading in mV on the FSV2 and i cant figure out how to change it to AFR.
The gauge itself is reading AFR, its just in the EFILive software it is recording it as mV.
All help greatly appreciated.

see screen shot in attached link.
https://www.dropbox.com/s/shjkhswsn9...41.13.png?dl=0

Trying to upload screenshot below.
https://i.imgur.com/q0eva3Q.png

You have it already, the EQ_RAT11 is the one you need. It is in Lambda, you would need to either be ok viewing in Lambda or writing a calculated PID to convert Lambda to AFR. When you're logging it, press the Enter button on the V2 keypad to switch between the different units. It may already be there, I usually log with these in V8 directly.

Thanks again Scarab, I was a bit confused there and away for work for a couple of days but managed to get some logs today, now I just need to work out what I'm looking at :).
I did have a problem with some data not being logged but worked out my dash cam was affecting the FSV2 recording the data, disconnected dash cam and all good.

+1 use EQ_RAT, which is actually the lambda read from the AEM 0334.

Post some log files.

Hi Joe,
I have only done one log since sorting out the camera problem, please see attached.
I spent a bit of time working my way through how to set up the dashboard to view the logs, but very new to this.
Even though i bought my FSV2 over 12 months ago, I only got around to installing my AEM WO2 over Christmas.
Would appreciate your thoughts on the log.Attachment 21798

That log shows WO2S11-EQRAT with no data...

did you have the 0334 connected...?

how did you connect the 0334 (analog or serial)...?

Hi Joe, thanks for taking a look.
I have the data showing up when I open the log in V8 S&T. The 0334 is connected via the OBDII port.
There are probably some PID's that i need to remove as I was just looking to see what they did (TRNR)
If you can see the log, do you have any idea why the lambda would drop to 0.655 at frame 30470? There are a couple of low points for the lambda.

Edit: I'm using the wrong terminology above, I should say richening up by dropping the lambda to 0.655.

Attachment 21800

Attachment 21801

Attachment 21803

Attachment 21802

Ak, ok, so you are getting data.


I don't know why lambda would drop to 0.655.

It looks like you need to richen PE.

It looks like you might need to disable all trimming, and correct the VE/VVE.



BTW: instead of logging O2S11/21, log HO2S11/21 instead.

Finally just order two of these 30-0334, LC-1s now listed on Ebay. I can see in scan & tune the AEM UEGO Bank 1, is Bank 2 automatically detected if connected?

You have to select bank2-sensor1 also... WO2S21.

Question for Dr Mike, is advice the same for AEM as was for LC-1, keep the power and battery ground cable gauge 14 AWG as close to the AFR gauge / controller as possible, or no need ?

Keeping the power cable runs short is generally a good idea. But, the newer AEM devices do not suffer the same ill effects of power rail fluctuations as the LC-1. Same, technically, goes for the sensor cables. Note how the LC-1 was the only fast Innovate controller ( around 30ms ) while there other products are slower ( around 100ms ). That is because the LC-1 only has a 12 inch sensor cable. Power fluctuation/spikes/noise affect the LC-1s measurement circuitry AND the analog output.

The X-series AEM controllers have active ground offset compensation. So, the analog outputs are not so sensitive to weaker ( within reason) ground paths. The sensor heater drive can swing randomly between 0amps and about 3amps depending on EGT and flow. So, a ground path of just 0.1ohms can cause an offset swing of 300mv. That's, partly, why the short, heavy, ground lines ( low resistance ). The 300mv is within the AEM controllers compensation range. And, of course the CAN/OBDII data is unaffected by the offsets,



Attachment 21895

Here is a MILD example of heater current swinging around, creating offsets. The red and blue traces are MAP and RPM. The yellow trace is the heater load. Looks like it converts to about 0.5amp to 2amp, depending on conditions. So, the ground current varies by about 1.5amps. A frind path of 0.2ohm would cause an offset error of 300mv that, mostly, followed the yellow trace. This is why you cant "zero out" an offset error by playing with the conversion formula. The offset moves, a lot, especially when it counts. Then, at idle, it goes back.

The X-series ( and some other ) controllers get around this with active offset compensation. Basically, the analog- line of the controller is not really a ground wire. It is an input to the controller, connected to the EFILive ( of other devices ) ground line. So, the controller uses THAT as a reference to set the analog output voltage. This way the 2 devices always agree on what ground is.

All of this is no excuse for sloppy wiring, though ! :P