34blazer

so ive been searching for the last few days non stop(well not really, between sleep and work) on how to display the wideband value in TP. long story short, everything i find seems to be over my head. im using the SLC PP2 with the bosch WBO2. i cant figure out how to set the range(s) and i know the answer is very simple. the conversion set at .05898+7.35, the raw data bit is selected in the xdf. WB controller output to pin F14. raw WB reading in adx doesnt move from 7.35. thanks in advance!

34blazer

bump?

34blazer

ok what does counts have to do with setting the range values? im seeing 1024, and 255? what should i set in the range low/high values?

JP86SS

iTrader: (1)

The counts are the digital representation of the voltage input.
The ECM can handle 5 volt input and is broken down into 255 "counts" because of 8 bit representation.
10 bit representation would be the 1024 counts that are used with the AutoProm external inputs.
Direct to ECM = 5 / 255 = 0.0196 volts per count
AutoProm inputs = 5 / 1024 = 0.0048828125

Smaller steps = better resolution

----------------------------------------





Pretty easy if you are using the S_AUJP V4 (1026 version or later).

• Physically Connect Output wire to F14
• Clear bit in bin file if using "F14" Pin.

Location 99B (WB OPT 2, bit 7, Input "A3", Else "F14")

• Set bit in bin to use the "Raw" output from the WB

Location 99B (WB OPT 2, bit 0, RAW A/D Output)
Select only 1 option for a WB setup.
This "RAW" one is for full 0-5 volt/0-255 count output to the datastream.

If two WBs are selected, the first one wins and you may not get the reading right because it would be scaled for a different WB output.





************************************************

• Confirm your scale within the WB controller is outputting the full 0-5 volt range that equals 7.35 to 22.39 AFR (or whatever you want)

************************************************





To Add the item to your ADX logging definition if it does not already exist:

• Open ADX editor

Go to "Values" in the listing and click where you want to insert a new item

• Click "Add New Item"

Name it to something you want like "WB Full Range"
Give it a Unique ID value (anything works here)
Type description as desired "WB with full scale output"
Units override = AFR
Packet offset = 0x24 | 36
Source Data Size = 8 bit
Range Low = 7.35 (or your range minimum)
Range high = 22.39 (or your range maximum)

alarms (if you want)
Alarm Low = 12.0, Enabled





Alarm high = 15.0, Enabled

• Click conversion tab and click "Set"

Enter this: X * 0.058980 + 7.350000 (Make this match your WB settings)
Argument type = Native
Output Format = Floating Point





Output Digits = 2 (If you only want 1 decimal then make this 1)

• Save

Run your car!

****************************************************

If your scaling is different, post up the range and voltage you have set and I can explain how to use your values.
I tried doing a generic description but I felt like I was writing a book that would be too involved to cover all variables and wouldn't be clear to your situation.

34blazer

cant get more clear than that!

another problem, there is a discrepency(sp) between the WB controller and the output displayed on my laptop. around stoich they are pretty close but anything other than that the display on the lappy all but pegs in either direction. im probably going to have to do a ground check to make sure thats not the problem.

87SLEEPER

So for my AEM controller would the values be 0.058980 + 8.5 ??

Thanks

Rob







The analog output from the AEM UEGO controller is a linear dc voltage signal that
varies from 0.5 Vdc at 8.5:1 AFR Gasoline (0.58 Lambda) to 4.5Vdc at 18.0:1 AFR
Gasoline (1.22 Lambda) over the operating range of the module. The signal is used
for sending information to a data logger or an engine management system like the AEM
EMS or F/IC.

JP86SS

iTrader: (1)

To represent this correctly it should be:
((N-25.5)*0.046568) +8.5

The thing that makes this hard is the 0.5 volt offset and the 4.5 volt high end.
That is equal to (5/255=0.01960 volts per step) 8 bit input.
0.5 volt / 0.01960 = 25.5 counts (can't use 1/2 counts)
4.5 volt / 0.01960 = 229.5 counts (can't use 1/2 counts)

Your span of 18.0-8.5 AFR = 9.5 AFR / 204 steps (between 25.5 and 229.5)

9.5 AFR / 204 steps = 0.046568 AFR per step.
Use the TP math to remove 25 counts (below 0.5 V input)
(N-25)*0.046568 +8.50 (Add the 8.5 offset)

you have to take the accuracy hit due to the 1/2 count but it is minimal.
Should read accurate within 0.1 AFR in the 8.5 to 18.0 AFR range.

Would be best in TP to run the output of the calculation through a lookup table to limit the range that can be displayed.
Create a lookup table with only 2 points
8.5 = 8.5
18.5 = 18.5
Only values between the points will be displayed.
Your History tables will thank you by not putting crazy values in when you are at the extents of the range.
Could also make the points 8.0 and 18.5 so if you see anything at those levels you know the sensor output was out of range.
HTH

87SLEEPER

JP thank you for spending the time to help me learn something new today!!

I honestly can say this is the first real life scenario since the 9th grade (nearly two decades ago) that I've actually had to use algebra. Wow!

With your posts here and also the help of this site http://tunerpro.net/forum/viewtopic.php?t=2924 I believe I have turned my first corner through this labrynth known as tuning. I have yet to have time to actually hook the wires up from my O2 tonight but I will let you know how it goes tomorrow. Hopefully it will be good news and I won't need to bother you any further....... but......... I have attached my work below for your review however, in hopes you have any further insight.

Thanks again

Rob

JP86SS

iTrader: (1)

Make the conversion using "X" as the value retrieved from the datastream.
Copy this in there.

((X-25)*0.046568) +8.5