# Is AFR Target 1 data linked to Lambda Target 1? **URL:** \ **Category:** Link\ **Created:** [October 11, 2022, 11:47pm UTC](https://forum.realdash.net/t/is-afr-target-1-data-linked-to-lambda-target-1/1433 "2022-10-11T23:47:01Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ROB-80E](https://forum.realdash.net/letter_avatar_proxy/v4/letter/r/b38774/32.png) [@ROB-80E](https://forum.realdash.net/u/ROB-80E)\ **Post date:** [October 11, 2022, 11:47pm UTC](https://forum.realdash.net/t/is-afr-target-1-data-linked-to-lambda-target-1/1433/1 "2022-10-11T23:47:01Z")
Hi, i’m wondering if you can help me with this one…I’ve got a data fighting situation occurring. I’m doing some testing with 2 connections. 1 via serial USB and 1 via OBD. Previously I’ve only ran OBD, but I’m now experimenting with both so that I can supplement what I cant get via serial. The issue i have is that when using the serial datastream, Lambda Target 1 does not show correct data (not sure what it’s showing to be honest). So what I did was setup OBD to show this data, but now it’s fighting with the serial datastream even though Lamda Target 1 is not shown as being on the Link datastream. In realdash, is Lambda Target 1 linked to AFR Target 1 in any way? The reason I ask is that I saw in another thread that Link outputs AFR Target 1 on the datastream, but not Lamda target. Is it the same data? Is there a calculation used that can change it from AFR to Lambda? FYI, via OBD2 request 44 the data displayed is perfect for input Lambda Target 1. Many thanks. Rob. ---
**Author:** ![realdashdev](https://forum.realdash.net/user_avatar/forum.realdash.net/realdashdev/32/6_2.png) [@realdashdev](https://forum.realdash.net/u/realdashdev)\ **Post date:** [October 12, 2022, 5:54am UTC](https://forum.realdash.net/t/is-afr-target-1-data-linked-to-lambda-target-1/1433/2 "2022-10-12T05:54:37Z")
Yes, Lambda and AFR are linked in RealDash. Typical ECU sends either AFR or Lambda, so every time RD receives AFR it will calculate and set the Lambda and vice versa. Calculation is based on Fuel Stoichiometric that can be set in Garage-\>Trunk. ---
**Author:** ![ROB-80E](https://forum.realdash.net/letter_avatar_proxy/v4/letter/r/b38774/32.png) [@ROB-80E](https://forum.realdash.net/u/ROB-80E)\ **Post date:** [October 12, 2022, 10:52am UTC](https://forum.realdash.net/t/is-afr-target-1-data-linked-to-lambda-target-1/1433/3 "2022-10-12T10:52:50Z")
Thanks Jani, I’ll check out what fuel I have set in Garage. I’m still a but confused as to where the serial data is coming from though. Lambda nor Lamda Target is not listed on the serial datastream from Link for the G4+. This is a post from another thread in the Link forum: > [@Oil Pressure and Temperature Inputs (Link ECU)](https://forum.realdash.net/t/oil-pressure-and-temperature-inputs-link-ecu/621/11): > > Indeed, the documentation we got from Link years back, and the information in PCLink app help file differ on some points: > > Here are the differences and how RealDash currently interprets the data stream. Differences are the same on short and long data stream: > Byte 25-26: Digital input 1-12 status > Byte 27-28: Wastegate duty cycle > Byte 43: Percentage fuel cut > Byte 44: Percentage ignition cut > Byte 81-82: AFR target > Byte 83-84: Lambda > Byte 85-86: Boost target > Byte 87-88: timer1 > Byte 89-90: timer2 > Byte 91: Differential fuel pressure > Byte 92: Altitude The above turned out to be the G4 datastream. Is it possible that within RD the old AFR target (and possibly lambda) is still picking up bites 81-82 which is now DI 1 in the G4+? Thanks, Rob. ---
**Author:** ![realdashdev](https://forum.realdash.net/user_avatar/forum.realdash.net/realdashdev/32/6_2.png) [@realdashdev](https://forum.realdash.net/u/realdashdev)\ **Post date:** [October 14, 2022, 8:49am UTC](https://forum.realdash.net/t/is-afr-target-1-data-linked-to-lambda-target-1/1433/4 "2022-10-14T08:49:44Z")
Yes, in code, both short and long datastream bytes 81-82 are read as AFR Target.