Trans control - 0026 release

[jsmcortina]

To announce the 0026 version of the Microsquirt trans code.

Changes since the last release
Bug fixes
Fix bug with config error code.
Microsquirt V3 analogue gearsel input didn't match docs. Confirmed as "SPAREADC" AD6.
Microsquirt V3 trans temp input didn't match docs. Confirmed as "MAT" AD1.

New / changed features
New CAN TX implementation from MS2/Extra. This should give reliable CAN passthrough.
Add Solenoid D output.
Add Selector D (OD) input for E4OD, W4A33.
Implement OD cancel momentary / latching for E4OD, W4A33.
Add 'mimic' VSSout option.
Add 4L60E LUF support. Bench tested on MicrosquirtV3.
Update datalog set.
Add dash indicators for Lockup and OD-cancel.

Minor / internal
Bump up 'burn' delay in ini file.
Update CFLAGS,LDFLAGS, serial.c in line with MS2/Extra
Remove a few unused vars.
Remove some internal temp vars from outpc.
Re-write some of analogue gear selection to remove busy-wait retry code.
Update ini to ISO-8859 charset. (TS doesn't like UTF-8 ?)

The zip can be downloaded from:
http://www.msextra.com/doc/trans/files/ ... 8-0026.zip
The updated manual is included.

A current TunerStudio is required.

Successes, failures, bug reports and suggestions welcome here.

James

[jsmcortina]

Known bug (thanks Wes) - when ppm or ppk is used for the speed input, the scaling factor is maybe 100x off. i.e. should be 2900, but you have to enter 29.
Fixed for the next release.

James

[Matt Cramer]

Microsquirt V3 trans temp input didn't match docs. Confirmed as "MAT" AD1.
Add 4L60E LUF support. Bench tested on MicrosquirtV3.

Excellent - I'd just started troubleshooting an installation on 0025, and ran into the transmission temperature issue.

I'd anticipated that you might try the LUF support, so my harness was already wired for it. I'll be sure to try that out too.

[prof315]

The fix for trans temp on the uS v3.0 is working for me.

Thanks!

Jeff

[prof315]

I'll test the mimic VSS feature tomorrow and let you know how it works.

[Matt Cramer]

Upgraded code and transmission temperature input is working great.

I have one issue remaining before trying to take this on the road. The VSS is reading zero with the engine off, but when I start it, I get a false MPH reading, typically around 7 to 30 mph. Had this issue with 0025 code as well, which was the first code I tried. I'm using a MicroSquirt V3.0, so I'm guessing it may be the MAX9926 is too sensitive. Will try using a resistor from VR to ground unless anyone has a better suggestion.

[jsmcortina]

That does sound like excess sensitivity. The shunt across VR1+/- is worth trying.

James

[prof315]

That does sound like excess sensitivity. The shunt across VR1+/- is worth trying.

James

I used a 10K shunt across VR1+/- on my install. I'm not totally sure it was needed ( the tone ring is MUCH bigger on a GM transaxle vs GM transmission), but I have smooth VSS through 50mph so far.

[wes kiser]

Not really related to the tranmission controller, but every harness I build for a microsquirt or MS3Pro gets the 10k shunt around VR+/- if it is in fact a VR install. I leave a small 1" loop in the wiring harness, so the shunt can be disabled if unable to get a low speed pulse. So far on half a dozen installs I have not needed to remove the shunt.

Just as default documentation, I would instruct all user to install the shunt by default, or at least meantion what it does. I know the microsquirt has the pad to bridge to "shunt" it internally, so I would at least meantion that.

[prof315]

The new mimic VSS input for VSS out is working perfectly.

Overall impressions of the firmware/uS trans controller from an end user point of view: It works like it did with the factory management. Nuff said.

Incredible job with this stuff James.

I am attaching a partial datalog from my final test drive with the customer this morning .

[ap67et10]

Matt,

I have run into the sensitivity issue 2 different times now. The first was on my BBC crank signal with MS3pro when I was doing beta testing for you guys on it. If I even lightly touched the VR sensor it would false trigger like crazy. I tried all kinds of shunts and caps, but what actually made the biggest difference was installing a 10k ohm resistor in line on the + VR signal.

The second time I ran into this was with my ford truck on the trans VSS. Originally with megashift and the outlined VR circuit on the GPIO board it would read 75ish mph any time the engine was running. I tried everything and got no changes at all. I scrapped that and got Jeans dual VR board and then ran into the sensitivity issue again and just like you would get readings in gear and random spikes when trying to drive. The biggest benefit again was installing 10k ohm resistor inline, except this time I did it inside the GPIO case on the digital signal before it connected to the processor pin. It has worked very well.

I've been told many times that a cap and shunt would work better but never has. The inline resistor is the best thing I have found with over sensitive signals using the MAX9926.


Andrew

[Matt Cramer]

I put the SB2 solder bridge in place with partial success. Now the VSS false triggering is pretty much confined to startup and free revving truck past 2500 RPM. I'm going to check some other possible solutions as well - may put a Weather Pack in the harness to get easy access to the wires.

Will be trying 0027 release code once I can get a path through a small flock of Miatas that suddenly appeared in our shop and can get the truck out and running around the parking lot.