Voltage Based shifter issue
Posted: Sat Apr 14, 2012 7:52 am
I have put beta 2.130 code/INI on the beta page: http://www.msgpio.com/manuals/mshift/V4code.html
This code has a few refinements to the forced up/downshift behavior when 'rpm checking' is enabled:
- the rpm check against the user limits is only performed if the check hasn't already determined the need for a shift (this should prevent multiple shifts on a single 'revs out of range' event),
- the target gear is reported as the current gear+1 if an upshift is needed, and the current gear-1 if a downshift is need according to the engine's revs (when 'rpm checking is enabled). Previously the shift table look-up value was reported even if a forced shift was required,
- the datalog now includes two binary values (fUP, fDWN) that indicate when a shift is forced by the rpm checks.
As well, the default FWD_factor has been set to 1.00 from 2.690. The previous default was for 4L60E's used in 4WD applications. But with table switching likely to be a more popular use of this function, a default of 1.000 makes more sense to more users. Users can enter any reasonable value they like, of course.
There is more on the rpm checking settings here: http://www.msgpio.com/manuals/mshift/V4tune.html#gr
Lance.
This code has a few refinements to the forced up/downshift behavior when 'rpm checking' is enabled:
- the rpm check against the user limits is only performed if the check hasn't already determined the need for a shift (this should prevent multiple shifts on a single 'revs out of range' event),
- the target gear is reported as the current gear+1 if an upshift is needed, and the current gear-1 if a downshift is need according to the engine's revs (when 'rpm checking is enabled). Previously the shift table look-up value was reported even if a forced shift was required,
- the datalog now includes two binary values (fUP, fDWN) that indicate when a shift is forced by the rpm checks.
As well, the default FWD_factor has been set to 1.00 from 2.690. The previous default was for 4L60E's used in 4WD applications. But with table switching likely to be a more popular use of this function, a default of 1.000 makes more sense to more users. Users can enter any reasonable value they like, of course.
There is more on the rpm checking settings here: http://www.msgpio.com/manuals/mshift/V4tune.html#gr
Lance.