MS3 pre-1.4.1 beta 2 released

[jsmcortina]

To announce the release of "MS3 Pre 1.4.1 beta 2"
Who should use this code?
All users are welcome to try this code.

Main changes since pre-1.4.1 beta 1 release
Bug fixes:
Trap undefined port values in case of alternator config error.
Torque convertor lockup wasn't working unless enable pin was in use.
Add sync re-check for sig-PIP.
Fix TPS accel blend issue.
Fix Blend curve 3. Broken by VVT fuel switching in Dec 2014.
Change displayed seqPW. EGT added fuel had caused a mixup. Fuel added in staging now too.

New / changed features:
Allow VVT with K24A2
1UZ decoder and VVT changes.
Change injector trim to 0.5% steps giving +/-63.5%
Revise Coyote VVT3 built-in reference angles.

Minor / internal:
Add another check for out-of-range remote CAN data.
Remove can_reset setting and replace with CAN error counters exposed in outpc.

Known bugs
-

The firmware zip is available from:
http://www.msextra.com/downloads/dev/ms ... -1/beta-2/

Be sure to read the README.txt and RELEASE-NOTES.txt that are supplied in the zipfile.

Upgrading users are advised to enable the "old baro calc" for backwards compatability.

Some of the ini changes will result in harmless warnings when loading MSQs from 1.3.x
Users upgrading from 1.2.x or earlier codes need to pay more attention.
TunerStudio 2.6.x is REQUIRED.

[AbatelliCristian]

Problem with idleVEtable on the tableswitch (no dual fuel, but tableswitch).
When I active the tableVE 3, idleVEtable refers to idleVEtable dualfuel, but it is disable in tunerstudio.
This is old problem...(no only this firmware)

[Joe]

I've been chasing an ignition gremlin lately when I noticed ignition crank dwell appears fixed at 5ms.
I had a Pico scope on my ignition primary and have full dwell control except during crank. Nothing I do seems to change the actual output of coil dwell for 5ms during crank.

I don'the have my msq handy but will post tomorrow if any interest. My install is unique and runs very well except for a starting issue. It's a 4x crank(No missing) 1x cam. 5.7 vortec with waste spark.
Not ideal but runs very well overall.

Thanks for any input
Joe

[jsmcortina]

Could certainly do with an MSQ and datalog to support this.

James

[Joe]

Setup
MS3/MS3X Board v3 1.4.1b2

SBC 5.7 Seqential inj waste spark

4x ckp 1x cmp (Stock vortec stuff)

I've zeroed out dwell voltage correction for coil dwell and reduced cranking dwell. Gauge in tuner studio is correct for the settings. Actual measured dwell stays at 5ms until run flag. Once running measured coil dwell matches settings and gauge in TS.

Joe

[jsmcortina]

Is the timing correct during cranking?

Your engine takes a LOOONG time to start? I'd probably set the "cranking RPM" higher too (try 600 RPM) as it once passes the low threshold you have set without starting in that datalog.

James

[Joe]

Is the timing correct during cranking?

Sometimes- Usually yes.

Your engine takes a LOOONG time to start? I'd probably set the "cranking RPM" higher too (try 600 RPM) as it once passes the low threshold you have set without starting in that datalog.

Sometimes it starts right up, others it's way out of time and i'm not 100% sure why. I was scoping yesterday to see whats going into the MS. I lowered crank rpm and reduced voltage correction. What puzzles me is it sounds out of time during crank but I seem to sync ok. I'm going to put all four channels of the pico on this when I have time to see if I can spot what is changing.
ckp/cmp look good last time I scoped. I have a 58x wheel I might install if I give up on this setup. I've just had good luck with the vortec setup until now. This engine has more compression then the others and I'm wondering if the "compression" effect is getting magnified with only 4 crank teeth.

The crank dwell is just something I noticed and I don't no if it's a result of something else I'm missing. The strange thing is it does not always do this. the datalog I posted is a great example of what i am fighting.

Joe


James

[jsmcortina]

60-2 should give way better timing accuracy. 4 teeth on the crank is the second worst you can get away with on a V8. (Distributor is worst.)

Testing on the scope I see the same dwell issue with some values of ATDC timing at very low RPMs.

James

[fechner]

Does the
"Add sync re-check for sig-PIP."
indicate the inability to use the ignition cylinder trims for PIP on the EEC-IV has been fixed in this release or is this still nonfunctional?

[jsmcortina]

Does the
"Add sync re-check for sig-PIP."
indicate the inability to use the ignition cylinder trims for PIP on the EEC-IV has been fixed in this release or is this still nonfunctional?

No, that is not supported.

James

[fechner]

Is it difficult to add this feature? (I am considering doing it myself since it is the primary reason I bought the MS3 to begin with and I need it to complete my project.) Are you aware of any plans for the experts to add this feature in the near future? Thanks.

[jsmcortina]

Is it difficult to add this feature?

It was last time I tried. The ignition code required is among the most complex within MS3 to develop and test. It "kind of worked" before but that's not good enough. It _may_ be possible now that I have worked on the re-sync issue.

James

[fechner]

Any suggestions as to what you believe is the best way to implement this function?

[jsmcortina]

Any suggestions as to what you believe is the best way to implement this function?

Adding a missing tooth wheel on the crank and a single tooth on the cam would be the best way.

James

[fechner]

I was hoping it could be done in software. I don't believe I need a robust solution. The current version appears to achieve full sync OK and I only really need to adjust the spark timing individually because I am running the MS3 piggy back on the OEM EEC-IV so it can control the injectors and the rest of the functions.

[jsmcortina]

I've zeroed out dwell voltage correction for coil dwell and reduced cranking dwell. Gauge in tuner studio is correct for the settings. Actual measured dwell stays at 5ms until run flag. Once running measured coil dwell matches settings and gauge in TS.

I believe I have resolved this issue, it was due to a calculation underflow with the ATDC timing you are using during cranking. It looks ok on the scope now. I'm going to test it on an engine and confirm timing under normal operation and then I'll send you a test code by email.

James

[jsmcortina]

I released pre-1.4.1 beta 3.

James