It is already fixed. New build will be released on Friday. The divider was 1024 not a 1000.
I have built my entire map around lambda readings coming from V3 studio… Does this mean they are all incorrect? Or is this only when using the AFR View, rather than Lambda View? I really hope that’s the case ![]()
If you read data via User CAN from exteranal controller, the values was a little bit off (2,5%).