I was a bit confused because the N75 duty map didn't behave as I expected. So I dived into the code and found the reason. Apparantly I had different values of RPM_MIN_FOR_BOOST_CONTROL for the multidisplay code that goes to the Arduino compared with the mUI code.
I see that the values are not the same for the latest version of the code either.
The multidisplay code has RPM_MIN_FOR_BOOST_CONTROL = 0 (see line 56 in MultidisplayDefines.h).
And the mUI code has RPM_MIN_FOR_BOOST_CONTROL = 2000 (see line 89 in MyTableWidget.cpp).
A patch with the mUI value changed to 0 is attached.
I also corrected the rpm values in the column headers (line 133 in MyTableWidget.cpp) to avoid accumulation of rounding errors.
RPM_MIN_FOR_BOOST_CONTROL different in mUI
-
- Posts: 26
- Joined: Thu 10. Jul 2014, 20:10
- Location: Sweden
RPM_MIN_FOR_BOOST_CONTROL different in mUI
- Attachments
-
- patch_mUI_svn150223_EK150623.diff.zip
- (641 Bytes) Downloaded 1593 times
Re: RPM_MIN_FOR_BOOST_CONTROL different in mUI
thx.
https://github.com/digifant/multidispla ... Widget.cpp
integrated patch into the source code ( now on github -> we're currently moving to github )
https://github.com/digifant/multidispla ... Widget.cpp
integrated patch into the source code ( now on github -> we're currently moving to github )