The beta V2.000 code is now available for limited and cautious bench testing. This code adds:
- up to 8 forward speeds allowed (+P/N/R),
- optional fourth shift solenoid output4 added on spare2 (PA0/VB2/Amp12). Has 'bit-banged' PWM and refresh cycles (like output1 and output2),
- optional fourth digital shift lever input added on PE1/GPI1/Amp5,
- CAN pass-through infrastructure from latest Sequencer code added,
- user defined spark retard (up to 25.5Ã‚Â°) for upshifts and for downshifts,
- user defined spark retard (up to 25.5Ã‚Â°) by gear (above a user specified load threshold) for 2nd and higher gears,
- user specified output patterns for the LED outputs (especially useful for interfacing with a seven segment LED driver).
(Unfortunately the 32K Codewarrior 'special edition' limit has been exceeded (~37K).)
These are in addition to the previous functions of the V1.100 code:
- Fully user configurable automatic or manual mode, with user tables for shift speeds and line pressures a based on speed and load,
- 12x12 speed versus load target gear table,
- 12x12 speed versus load line pressure PWM table,
- User configurable output and input patterns (to adapt to many 4-speed automatic transmissions - defaults are for GM 4L60E trans),
- Speed in 0.1 mph (or kph) increments,
- Fully user configurable lock up torque converter clutch (TCC) settings,
- Odometer in 0.001 mile (kilometer) increments (in addition to a VSS tooth counter),
- Full datalogging of speed, gear, odometer, line pressure, etc., as well as main loops counter, etc.
- Provisions for 'paddle' shifters on steering wheel,
- Four LED indicators for current gear:
- Adaptive load sensing interprets your driving style and adjusts shifts to reflect 'hard' or easy' driving,
- MegaTune display of shift button status, braking, gear, TCC status, speed, load, odometer, trans temperature, etc.
- Built in code for a 0.5-4.5V line pressure sensor,
- Configurable (pulse/mile) 12V square wave hardware speedometer output for electronic speedometers (you set the pulse per mile),
- Two spare outputs that can be set by a user-specified combination of vehicle speed, engine rpm, load, or current gear (with user-set hysteresis to prevent rapidly cycling near the switch points). These can alternatively be used as 'clutch outputs' (i.e., active only during a shift),
- GM (digital inputs) or Ford style (varying voltage) shift lever determination. If the Ford style is used, the addition 2 inputs can be used to datalog voltage signals (temperatures, TPS, MAP, etc.),
- 2/4WD speedometer scaling.
The CAN pass through is tested and works with B&G code version 3.400 and higher (editted from 3.300. Get the 3.430 code here: http://www.megamanual.com/ms2/betacode.htm
- note that 3.430 code will not install on many MS-II's without a bootloader upgrade. For those able and willing to test, I will upgrade the bootloader on their MS-II as necessary if they ship me their MS-II). The CAN pass-through code works with TunerStudio only. You need to set up for the CAN pass-through under TS 'File/Project Properties/CAN Devices'. The CAN ID for the MShift code has a default value of 1. Phil says, "If your MSII is the primary controller in the project you don't set it up as a CAN device, only set up the GPIO board as a CAN device. The Primary Project Controller will always use the CAN ID as defined in the ini, where the with any CAN devices TS will replace the CAN ID in all the ini commands with the ID you set for the device in the Project Properties, so Make sure you set that to the ID . So if you have a Project that has an MSII as the mainController, then a GPIO board as a CAN device on CAN ID 1, it is only the GPIO board that goes in CAN Devices list and the CAN ID should be set to 1."
You can change the CAN ID in the menus to a value up to 13 to avoid conflicts with other CAN devices - if you do change the MShift CAN ID you must also change it under 'File/Project Properties/CAN Devices'.
The timing retard functions (for shift duration and in gears) have been successfully tested with code B&G 2.891+, and the tableID and offset for the spark timing adjustment variable on MS-II, etc. are user settable so alternate code can use the spark retard feature.
The code and associated INI can be found here: http://www.msgpio.com/manuals/mshift/V2code.html
The tuning software guide is here: http://www.msgpio.com/manuals/mshift/V2tune.html
Note that Phil has made a very recent adjustment in TunerStudio to accommodate the 16-bit shift patterns, so you might need to update TunerStudio to be able to edit the shift I/O patterns. If you are still using MegaTune, you will likely need to change one line (around line 16) in the INI from:
to prevent 'current page out of range' errors.