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

[dr.mike]

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/instructions/30-0334-X-Series-OBDII-Wideband-UEGO-Controller-Gauge.pdf

21297

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

[ScarabEpic22]

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

[joecar]

Thanks dr.mike :cheers:


...

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.

[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 )




[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.

[Gelf VXR]

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

And the E40

[ScarabEpic22]

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 )




[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.

[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:

[Scatfish]

Is this AEM Wideband compatible with the LS1B 411 PCM?

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

21588

[dr.mike]

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.

[joecar]

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.

[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?

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

[joecar]

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.

[dr.mike]

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 )

[joecar]

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).

[dr.mike]

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 :)

[joecar]

dr.mike, thanks :rockon:

[Scatfish]

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.

[dr.mike]

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.

[02sfguy]

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.

[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.

[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.

[joecar]

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.

[joecar]

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...

[dgp]

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

[dgp]

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

[dgp]

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/3rb9nsbcyur0tp0/Screenshot%202018-01-21%2015.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/6mcgj1dix8q1gri/Screenshot%202018-01-21%2015.03.30.png?dl=0

[ScarabEpic22]

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).

[dgp]

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

[dgp]

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/shjkhswsn9tmun4/Screenshot%202018-01-22%2016.41.13.png?dl=0

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

[ScarabEpic22]

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.

[dgp]

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.

[joecar]

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

Post some log files.

[dgp]

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.21798

[joecar]

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

did you have the 0334 connected...?

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

[dgp]

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.

21800

21801

21803

21802

[joecar]

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.

[Gelf VXR]

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?

[joecar]

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

[Gelf VXR]

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 ?

[dr.mike]

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,



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

[joecar]

dr.mike, thanks for the info.

[Gelf VXR]

Excellent response thanks

[Gelf VXR]

ive installed the WB's and both gauge reading normally, ive set up and connected to the the flash scan (BB logging) for both gauges, both show on the flash scan, only the first has any data, the other reads zero?

Its an E40 PCM, have i missed something?

[Gelf VXR]

Attached individually both sensor EQ_RAT11/WO2S11V data is displayed on the V2 ruling out issue with the cable or connection of each gauge, reversed the order of connection still only EQ_RAT11/WO2S11V displays data.

While both connected to the laptop logging strangely EQ_RAT21/WO2S21V is active, when I reversed the connection order EQ_RAT11/WO2S11V is active. Individually EQ_RAT11/WO2S11V is active

[Gelf VXR]

Sorted, I thought they were plug n play, I just needed to change the pid entry on the gauges to EFI1 and EF2

[joecar]

Gelf, did you get ot working...?

[Gelf VXR]

Gelf, did you get ot working...?

Yes, all good now

[Dman]

Need some help, I bought the 30-0334 to be able to log with efi. I have an e39 ecm running a single wideband and the wo2s11 pid connected to my autocal, I have both the ecm and wideband controllers connected under 1 controller with no other controllers connected. When I go to log or display data, the wideband is only streaming data to my autocal for a few minutes then the streaming freezes. If I unplug then plug back in my autocal it reconnects and does the same thing. If I power down my wideband and reconnect it, it does not start streaming again. Why does this only stream for a few minutes?

[Dman]

Or is there a good place to look for this info

[Dman]

Maybe?

[Dman]

Need to make a post

[Dman]

...

[joecar]

You should have gotten the 30-0333 if you're running only one wideband; the 30-0334 is the second wideband if you're dunning two widebands.

But it appears the 0334 works by itself.

[joecar]

Post the log files you're getting.

On your AC where/what are the logs being saved to...?

[dr.mike]

IIRC, The 30-0333 does not support EFILive. Just "Brand H". The 30-0334 was designed to work with EFILive in both single and dual configurations.

[Dman]

Here's the log file. On my autocal, the files are being saved to the scan folder as an .efi file extension.

[Dman]

Even if I use my autocal as a pass through and log with my laptop, I get the same results. If I unhook my autocal, or turn off my car and wait for it to time out and turn off, that's the only way I get the wideband and autocal to talk again, but it's always only for a few minutes.

[joecar]

IIRC, The 30-0333 does not support EFILive. Just "Brand H". The 30-0334 was designed to work with EFILive in both single and dual configurations.
dr.mike, thanks for the clarification.

[Dman]

Joecar did you see anything with my log?

[Blacky]

The problem appears to be the data coming from the wide band. The data does not stop abruptly, but ramps up to an invalid/faulty value over a number of frames as shown below. That implies (to me) that the wide band has failed and the output from the wide band has drifted to its maximum value over a sequence of 4-5 frames.


22894

22895


Regards
Paul

[Dman]

Paul, can I have you validate this with another log where the values dont jump so much? The spikes you see in the log is where I let off the throttle and I'm coasting. I have logs were im just sitting idle and the stream stops with no major fluctuation like you see here. I will post another log when I get home in about an hour and a half.

[Dman]

Here is another log of me just idling then it does the same thing. Although I forgot to change the pid on the controller, i was going through all the pids for the wideband and testing to see if they all did the same thing or if one of them would actually log this thing.

[Dman]

Here is another thing I wasnt thinking about last night, when the streaming stops, if I unplug my autocal and plug it back in then go back to record or display data, the streaming will start back up for a few minutes again. This is without turning off the wideband or turning off the car.

[Blacky]

Here is another thing I wasnt thinking about last night, when the streaming stops, if I unplug my autocal and plug it back in then go back to record or display data, the streaming will start back up for a few minutes again. This is without turning off the wideband or turning off the car.

Are you able to use pass-thru logging (from a PC or laptop) along with the V8 scan tool to log the wide band data?
If you can do that, then as soon as the the wide band data flat lines (well within 10-20 seconds), stop the log and open the EFILive Control Panel and save a trace file and send me the trace file (paul@efilive.com).
22899

Regards
Paul

[Dman]

Yes Paul I can do that, I may already have a file. I will get my laptop and check, if not I'll get you one within an hour. Thanks for your help, this has been a headache for about 3 weeks now.

[Blacky]

Yes Paul I can do that, I may already have a file. I will get my laptop and check, if not I'll get you one within an hour. Thanks for your help, this has been a headache for about 3 weeks now.

Thanks for the log it helped but not enough, what I really need is a set of two files:
1. The *.efi data log file where the WO2 data flat lines.
2. The matching *.htx trace file of that same logging session.

I need to be able to compare the trace data and the recorded data to see where the problem occurred.

Thanks
Paul

[Dman]

Ok Paul, I'm am making it right now and I will send it to you in about 5 minutes soon as freezes. Thanks for your help

[Dman]

I sent both files, thanks again

[dr.mike]

Are the keep-alive messages logged ? The ones to 0x0101

If one is not received at least every 5 seconds, the stream will timeout. If they are sent exactly every 5 seconds, there may be a race condition.

[Dman]

Dr.mike, you might be on to something with this keep alive thing. I was sitting in the car watching the Mv stream on my autocal and before it stops streaming, the readout on my autocal starts delaying the readout for almost a second then starts back up again every 5 to 6 seconds, it does that about 4 times or so before the stream completely stops. Is there a way to fix the keep alive part?

[Chuck CoW]

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 )




[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.

Hey Joe.

Is it possible to use this info to help make a ben factor pid for the E92 controller like we were working on a while ago??

I'm noticing that there are no DMA commanded fuel pids available for the new DI controllers and it's a huge pain in the ass

to calibrate a maf or VVE table without the ability to auto correct the maps with an accurate Ben factor pid.

I tried to use a commanded lambda pid but had no luck.

Is there a way we can do this? Should we start a new thread? I'm sure others will be needing it too.

Thanks
Chuck CoW

[joecar]

Chuck,

Putting this in UserCalculatedPids.ini would define BEN pids for serial-comm and CAN-bus connected widebands:



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

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

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

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

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



You wold then use WO2CAN.WO2BEN as the BEN pid.

[spy2520]

Quick question on that. is pid("WO2S11") good enough? It doesn't need to be pid("WO2S11.EQ_RAT11") or anything like that?

[joecar]

I found pid("WO2S11") to work ok (it appeared to choose lambda)... I'll have to dig thru my logs.

You could try pid("WO2S11.EQ_RAT11").

[spy2520]

Hmm. It validates either way I try, I just get 0.000. Maybe I'll remove and re-add all the pids and see if it's just a hiccup.

[spy2520]

Yeah I can't figure out where I went wrong. I can see the readings but the calc pid doesn't work. I even tried just "Return pid("WO2S11")" and got nothing but 0.000. Doing that with any other pid works.

[kangsta]

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/instructions/30-0334-X-Series-OBDII-Wideband-UEGO-Controller-Gauge.pdf

21297

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

Does this mean you cannot log, ECM-TCM-AEM at the same time? Only 2 controllers?

[joecar]

Does this mean you cannot log, ECM-TCM-AEM at the same time? Only 2 controllers?Yes, correct, only 2 controllers.

[Gelf VXR]

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 ).


Does anyone know the part number for the pins, I want to connect analogue directly to FSV2 to log in 7.5 while using DVT

TIA

[dr.mike]

https://www.digikey.com/product-detail/en/jst-sales-america-inc/SPUD-001T-P0.5/455-2518-1-ND/1989509

[Gelf VXR]

https://www.digikey.com/product-detail/en/jst-sales-america-inc/SPUD-001T-P0.5/455-2518-1-ND/1989509

Thank you :)

[spy2520]

Can anyone show me a log with the BEN working AND how you defined the calc pid? I'm still running issues.

[Chuck CoW]

Chuck,

Putting this in UserCalculatedPids.ini would define BEN pids for serial-comm and CAN-bus connected widebands:



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

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

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

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

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



You wold then use WO2CAN.WO2BEN as the BEN pid.


Hey Joe,

When you say "can bus connected widebands" do you mean the RS232 serial wideband connections?

Thanks
Chuck CoW

[joecar]

Hey Joe,

When you say "can bus connected widebands" do you mean the RS232 serial wideband connections?

Thanks
Chuck CoWNo...

the AEM 30-0333/0334 connects to FSV2 via the CAN bus.

[joecar]

The AEM 03-0333/0334 do not have serial comms (please correct me Dr.Mike).

[Chuck CoW]

No...

the AEM 30-0333/0334 connects to FSV2 via the CAN bus.

Hey Joe.. SO, has EFI LIVE added a pid to help scan and log the AEM pid? That sounds like a cool feature, but not having serial is not a great idea and

let's suppose you're tuning an LS1 or any other NON-CAN controller, how would you log it if there is no can bus and the wideband has no serial output.

Going back to analog don't make sense.

Chuck CoW

[joecar]

The 0333/0334 still outputs analog 0-5V, but is more intended for E38, E67, E92 tuning.

The 0333 is specifically for single wideband to CAN; the 0334 is for dual widebands to CAN.

EFILive has a means to connect to one or two CAN bus connected widebands, including pids.

[zayne0]

Alright so i am trying to get back up and tuning again after several years out of the game and i struggle with pretty much all of what i have read in this forum post over getting the aem wb up and communicating with efi live. i am wanting to switch over to aem because of all the issues ive had with my innovate lm2. why is there not a video tutorial for setting up and getting a wide band up and communicating for retards like me?

[ToonerSQUAD89]

Alright so i am trying to get back up and tuning again after several years out of the game and i struggle with pretty much all of what i have read in this forum post over getting the aem wb up and communicating with efi live. i am wanting to switch over to aem because of all the issues ive had with my innovate lm2. why is there not a video tutorial for setting up and getting a wide band up and communicating for retards like me?

I been pushing myself hard to learning how to tune and each week that goes by and getting more practical and then doing textbook has extremely helped. As far as EFIlive, i think its an awesome product and cant wait for its next release but compared to HP Tuners, you will find online there are alot more people using it on gasoline products then EFI Live. Hence why you get more online community tutorials

Now EFIlive has a bit of a learning curve which i found out. Its not impossible but there is alot to understand and you need alot of patience. Youll find that you have a question and it wont get answered for weeks sometimes. So that leaves you to dig around and find it out yourself, which is very rewarding. There are alot of super knowledgeable guys on here, learned alot from small talk here. But now to answer your question.

What issues you having with the LM-2?

[jeeper]

Hey Joe.. SO, has EFI LIVE added a pid to help scan and log the AEM pid? That sounds like a cool feature, but not having serial is not a great idea and

let's suppose you're tuning an LS1 or any other NON-CAN controller, how would you log it if there is no can bus and the wideband has no serial output.

Going back to analog don't make sense.

Chuck CoW

Bringing this thread back to the top.

I'm a complete newbie (noob) to tuning. I am trying to learn but am struggling with pretty much everything because I don't have any background in anything like this. Learning the terminology and abbreviations for them is still a struggle right now. But that aside, I just ordered the AEM 30-0334 and am waiting for it to arrive. (It should be here in early June.)

I decided I should read the manual that was linked earlier in this thread. What I noticed on the first page is serial and analog are both available on the unit but are not populated on the connector.

I currently have 2 different projects going. One is going to be using an E38 ECU running a 6.0 LQ4/6L80 auto. The wideband I ordered should work as is for that is my understanding. I'll need to tune the engine separately from the transmission though. (I don't anticipate that as being a problem.) The other project which is actually closer to completion is using a LS1B running a stock 5.3 from a 2000 Silverado connected a Jeep manual transmission.

So am I wrong to believe I can modify the connector and add the serial and/or analog pins to connect to my V2 scanner for the LS1B tuning? How would I set that up then in EFI?

[dr.mike]

The analog output from the 30-0334 is preferred over the serial. In either case, you would need to add the associated pins to the connector.

The serial output of the 30-0334, as shipped, is compatible with the old 30-4100. So, it is slow, and low resolution. If you send me the gauge for re-FLASH, I can upgrade the serial to be 5x faster with a full extra digit of resolution.

I would use the analog output. It has more resolution and better response times than even the upgraded serial connection. Unlike most widebands, it does not suffer from the dreaded ground voltage offset errors, due to its built-in differential compensation circuitry. Because of the, remember to connect the WB analog- pin to the scanner's ground.

The connectors and pins are available from digikey.com

connector: https://www.digikey.com/product-detail/en/jst-sales-america-inc/PUDP-10V-S/455-2469-ND/1989458

pins: https://www.digikey.com/product-detail/en/jst-sales-america-inc/PUDP-10V-S/455-2469-ND/1989458

I would order a few extra of each, as they are usually cheaper than the shipping costs. And, it prevents the need to hack up a perfectly good connector/harness that comes with the WB :)

[jeeper]

Thanks for the input. I have ordered several connectors and lots of pins. I will create a new cable for the LS1b rather than modifying the cable that comes with. I will try it with the analog first and if I have problems I will ask for help then.

Thanks for the offer to re-flash the gauge. If I have issues with analog I may take you up on that but I don't even have the hardware in my possession yet. Is it possible to buy just the gauge separately? The manual lists it as 10-0334 but my searches come up short of any links to purchase the gauge independently of the 30-0334 kit. If I could buy just the gauge at a reasonable cost I may purchase it and have it shipped directly to you for flashing.

[dr.mike]

Wouldn't you still need the sensor cable/harness ?

[jeeper]

I was thinking the gauge is the only part that needs flashing? If I bought an extra gauge and had it shipped directly to you, you could flash it and send it to me? I assume the part that needs flashing is the gauge itself? Is the gauge calibrated to the specific sensor that is included in the kit? By that question I mean would I need to recalibrate my existing gauge if I had to purchase a replacement sensor for it at some point in the future? Or if I purchased an extra gauge alone would I need to recalibrate it to use the sensor I got in the kit I just purchased?

Please forgive me if I sound ignorant. It's only because I am... I'm reading a lot but it's taking a while for things to make sense. This whole tuning thing is all new to me and I have nothing to compare it to in my past experiences.

[dr.mike]

Yes. The gauge is the part that needs the re-flash.

The gauges are not matched to the sensors. Each sensor comes with its own calibration. I was just thinking that having 2 gauges, 2 power cables, and 1 sensor cable is not THAT useful ?

[jeeper]

So I have been trying to tune with the AEM 30-0334 with an analog connection to my V2. I have tried several calc_pids.txt files but don't seem to be getting correct output to adjust my VE table. I'm assuming my calculation is wrong. Would you be able to verify my calc_pids.txt file and show me what I'm doing wrong?

[dr.mike]

Did you run the Analog- line to a ground pin on the V2 scanner ? Not having a goof ground on the Analog- pin of the gauge is the #1 cause of analog issues with the x-series widebands.

[jeeper]

Thanks for the reply. I think I have it going now though.

I was (and am) getting good readings from the gauge.

My problem was setting the gauge set up correctly in the software. Actually getting readings wasn't the problem really either. The gauge was showing up fine and giving good readings. My problem was making those readings into useful equations to aid in being able to have data I could paste into the main VE table after a log session. I actually found the calc_pids.txt (https://forum.efilive.com/attachment.php?attachmentid=20472&d=1480124326) file here. I'm all set now. Thanks for the help.

[dr.mike]

Yes. A common problem when trying to set up the analog inputs into the scanner is the Analog- wire not being connected to the scanner ground. When it is not, the output voltage will be wrong. And, it is impossible to set up the math to work properly in the software. Much tail chasing ensues :(

[s4door]

I have recently installed the AEM 30-0334 in my truck. I have a 2010 6.7 Cummins running as a stand-alone in a 92 F350. The ECM is a CM2200. I select the CM2200 as the ECM and then the AEM 30-0334 as the TCM to monitor both simultaneously. When I then click OK to confirm my two choices I get the following error:

Transmission controller: AEM UEGO Bank 1 has not been selected because it is incompatible with engine controller: CMD CM2200 Cummins Diesel ECM.

I am able to independently select the CM2200 and then the AEM 30-0334 and program the V2 with both controllers independently. I can then successfully log data form either but not both at the same time. I need to be able to monitor both at the same time. Am I doing something wrong or is EFILive not setup to do this? I also tried to link other GM Diesel ECMs with the AEM 30-0334 and would get the same error.

[Blacky]

I have recently installed the AEM 30-0334 in my truck. I have a 2010 6.7 Cummins running as a stand-alone in a 92 F350. The ECM is a CM2200. I select the CM2200 as the ECM and then the AEM 30-0334 as the TCM to monitor both simultaneously. When I then click OK to confirm my two choices I get the following error:

Transmission controller: AEM UEGO Bank 1 has not been selected because it is incompatible with engine controller: CMD CM2200 Cummins Diesel ECM.

I am able to independently select the CM2200 and then the AEM 30-0334 and program the V2 with both controllers independently. I can then successfully log data form either but not both at the same time. I need to be able to monitor both at the same time. Am I doing something wrong or is EFILive not setup to do this? I also tried to link other GM Diesel ECMs with the AEM 30-0334 and would get the same error.

The AEM wide band controller simulates a CAN module on the GM CAN bus using GM specific OBDII messages to transmit the wide band data to FlashScan/AutoCal devices.
Cummins ECMs use a different data logging message structure which is not compatible with the message structure that the AEM has been programmed to simulate.
Therefor it is not possible to log both Cummins and AEM simultaneously.

Regards
Paul

[s4door]

Would I be able to connect the AEM to my V2 in pass thru mode connected to my laptop via the serial port or Analog output that the gauge also has for communication and then be able to log data simultaneously?

[Blacky]

Would I be able to connect the AEM to my V2 in pass thru mode connected to my laptop via the serial port or Analog output that the gauge also has for communication and then be able to log data simultaneously?

If your AEM is compatible with the AEM UEGO serial interface that FlashScan supports, then yes you should be able to do that.
Regards
Paul

[s4door]

Thanks I will give that a try. I have the serial cable that came with my V2