New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix #5160 #5164
fix #5160 #5164
Conversation
this PR is red |
float lambda = Sensor::getOrZero(SensorType::Lambda1); | ||
// phi = 1 / lambda | ||
float phi = clampF(0, 1 / lambda, 1.99f); | ||
float lambda = clampF(0, Sensor::getOrZero(SensorType::Lambda1), 1.99f); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious, why 1.99f
vs e.g. 1.9999f
-- I realize "< 2 ratio" is the concern; is the extra "top end" not really worth?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nobody is running an engine anywhere near 2.0 lambda anyway
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah I figured.
also wondering, does rusEFI ever report the voltage (bytes CD
) for OBD2 PIDs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope. Not much reason to unless you're doing "real" diagnosis using OBD2. We support OBD2 pretty much exclusively for gauges/dashes/apps/etc, not real diagnosis.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We support OBD2 pretty much exclusively for gauges/dashes/apps/etc, not real diagnosis.
This statement is an important fact but it seems not captured in doc yet.
Is it ok that I add it to https://wiki.rusefi.com/CAN/ ?
send lambda properly over OBD2
fix #5160