# Is AFR Target 1 data linked to Lambda Target 1?

**URL:** <https://forum.realdash.net/t/is-afr-target-1-data-linked-to-lambda-target-1/1433>\
**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:** 1\
**Showing post:** 3

<div class="post-metadata">

**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")

</div>

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.

---

_[View the full topic](https://forum.realdash.net/t/is-afr-target-1-data-linked-to-lambda-target-1/1433)._