MS2/Extra pre-3.3.3 beta 1 released

[jsmcortina]

To announce the release of pre-3.3.3 beta 1.

Main changes since 3.3.2 (release)
Bug fixes:
Fix rotary trailing calculation error (evident near 0deg advance)
3-cyl single-coil - beware of possible side effects
Allow Stepper adapater alt. pins on microsquirt-module.
Fix to oddfire custom angles (accumulate odd_trig_offset)

Minor/internal:
Add AEM 3.5 bar and 5.0 bar MAP sensors
Change help file PDF name.

The zip can be downloaded from:
http://www.msextra.com/doc/ms2extra/fil ... 3beta1.zip

Please be sure to read the README.txt and RELEASE-NOTES.txt supplied within the firmware zip file.

The current TunerStudio is REQUIRED.

James

[ol boy]

Any chance of squeezing in that trigger return (kick start) idea?

Thanks Ryan

[jsmcortina]

That's not forgotten, but will go into the pre-3.4 code.

James

[ol boy]

Awesome. I can test on a real engine with in the first few days after release.

[JoseMiguel]

James

The 3 cylinder single coil is a fix for this?

http://www.msextra.com/forums/viewtopic ... 01&t=54582

[jsmcortina]

James

The 3 cylinder single coil is a fix for this?

http://www.msextra.com/forums/viewtopic ... 01&t=54582

Yes it is. Your problem should hopefully be resolved.

James

[JoseMiguel]

James

The 3 cylinder single coil is a fix for this?

http://www.msextra.com/forums/viewtopic ... 01&t=54582

Yes it is. Your problem should hopefully be resolved.

James

Great news, ill try it in the car today and ill have some feedback hopefully on the night!

[dontz125]

While digging through the various settings in TS, I noticed that for both uSC (cased) and uSM the Knock settings use MS2 nomenclature. Also, I'm pretty sure that Port3 Bit 1 can't produce an analogue signal.

The uSM Stepper connection pins come up with the selection for the uSC; shouldn't they just be PT6, PT7, & IACEN?

Any particular reason why Tach Out and Sequential Shift Solenoid don't have remote outputs? Other than that, they're the same pin selection as AC Idle Up, which can use a remote output.

[racingmini_mtl]

Any particular reason why Tach Out and Sequential Shift Solenoid don't have remote outputs?

The tach out signal is related to engine position (tach triggers) so needs to be local. And the sequential shift solenoid is timed relative to other actions so again needs to be local.

Jean

[dontz125]

Ok, the solenoid I can see, but the tach out signal is only driving, well, the tach. It doesn't need fractional-degree-of-crank-angle accuracy. Most guys are happy +/- a few hundred rpm ...

[racingmini_mtl]

Ok, the solenoid I can see, but the tach out signal is only driving, well, the tach. It doesn't need fractional-degree-of-crank-angle accuracy. Most guys are happy +/- a few hundred rpm ...

But you wouldn't only have the CAN bus latency. Unless the CAN device code is written to change the output state as soon as the CAN message is received, you also have additional latency in the code. The IOx code changes the digital outputs in the main loop since it is not supposed to be time critical; doing this in the CAN interrupt routine might improve latency but would be terrible for everything else.

So for a CAN device dedicated to this single task, it might not bee too bad. For any CAN device that needs to do more and does a few generic things, this is not practical or a good idea. You'd get better results having a pseudo-tach out on the CAN device that uses the RPM data from the MS to directly drive an output.

Jean

[dontz125]

Understood. Does the current IOx and TIOx code support the remote tach from your last sentence?

[racingmini_mtl]

Understood. Does the current IOx and TIOx code support the remote tach from your last sentence?

Not at this time but is planned for the next release.

Jean