MS2/Extra pre-3.3.2 beta 5 released

[jsmcortina]

To announce the release of pre-3.3.2 beta 5.

I'm STILL awaiting any feedback on the significant change in pre-3.3.2 beta1 which was a change to the "Toothed wheel" decoder for oddfire and odd cylinder count engines. Megahelp are you out there? Please read your PMs.

Main changes since pre-3.3.2 beta 4
Bug fixes:
Handle another impossible tooth count with config error.
Microsquirt module reports correct config error text for PT6/7 conflict.
Remove false error checking on nitrous outputs with PT6/7
Swap transposed ALED/WLED in I/O test.
Fix dutycycle calc for rotary

New/changed features:
Average 1-cyl RPMs over two revs.
Rotary trailing spark works in test mode. (Test coils A = leading 1, B = leading 2, C = trailing 1, D = trailing 2)
RPM-sync indicator name change

Minor/internal:
Fix amap MSQ load warning by changing order of entries in ini.

The dash indicators for "Synced" and "Half-sync" have been changed as per http://www.msextra.com/forums/viewtopic ... 22&t=53193
READ THE RELEASE-NOTES.txt

The zip can be downloaded from:
http://www.msextra.com/doc/ms2extra/fil ... 2beta5.zip
Please read the RELEASE-NOTES.txt

The latest beta TunerStudio is no longer required, the current release version is ok.

James

[zmanco]

I can confirm that the error on starting TS is gone, as is the warning to restart MS when changing some of the boost control settings that didn't require a restart. Other than that, I'm not using the other features that were changed.

[Manu]

Hello James,

I'm trying to use BARO correction in alpha/N with integrated MAP sensor of MS2 and get a config error until I set "Multiply MAP" to "Don't multiply". As you didn't mention this parameter in 3.3.2 annonce, is it requiered ?

Thanks,
Manu

[jsmcortina]

Baro and MAP are two different sensors.

If you enable "Multiply MAP" then you need to have a MAP sensor installed reading MAP.

James

[Manu]

Thanks James,

That is what I suppose too. So in this case, we use pure Alpha-N with baro correction. Correct ?

Now, what is the difference with standard Alpha-N (Multiply enable) without baro correction ?

Best regards,
Manu

[franksidebike]

Hallo

Now, what is the difference with standard Alpha-N (Multiply enable) without baro correction ?

Is this helpful:
http://www.msextra.com/forums/viewtopic ... 94&t=53567
Frank

[Manu]

Hello Frank,

This should be usefull and we can say there was errors in "copy/paste" of case :

Without 'Multiply MAP', with 'Include AFR target'
PW = DT + (ReqFuel * VE[RPM,TPS] * AirDen * BaroCor * corrections)

Without 'Multiply MAP', with 'Include AFR target'
PW = DT + (ReqFuel * Stoich/AFRtarget * VE[RPM,TPS] * AirDen * BaroCor * corrections)

But I can imagine ;-)

Thanks

[jsmcortina]

The copy/paste errors should be fixed now.

James

[Manu]

Thanks James.

[bearda]

Has anyone noticed anything funny with the tach output? It might be my setup, but I just updated from 3.3.1 (released) to get the AC Idle-up output functionality back on my Miata and it seemed like during my quick idle test the tach would dip for a split second every once and a while (maybe every 3 seconds or so). The car didn't stumble or anything and the logs didn't seem to show anything happening to the RPM, and I don't remember ever seeing any issues with the tach before. I'm running a DIYPNP (microsquirt module) if it matters.

I'm going to try to take the car out tomorrow and see if the problem pops up or if there are any other oddities. I just figured I'd put a feeler out and see if there was a setting I may have missed that changed or if someone else noticed anything.

[Reverant]

Nope, no tach issues so far on multiple cars.

[bearda]

Drove the car in this morning and something definitely doesn't seem right. The frequency of the tach drop seemed to change a lot (and I was driving in stop and go traffic, so my attention wasn't fixed on the tach anyway) but I took a log and hit a mark every time I saw it happen. It was probably around once every 1-2 minutes, but like I said it varied a lot (the video was one of the worst time periods where it was happening much more frequently). I noticed it a lot more later in the log since I was at a full stop more often once I got closer to my office.

The tune I was using at the time is attached here, but the log and video of the gauge cluster are both too large to upload. I put them all in a dropbox folder here:
https://www.dropbox.com/sh/2sih9696twjvr0i/sb6p0tcwGF

I went back to 3.3.1 when I got to work. I let it idle for about 2 minutes after reloading the firmware and I didn't see any weirdness with the tach, but I'll drive it home tonight on the released 3.3.1 firmware (without AC ) to try to narrow it down.

For reference the car is a USDM 1995 Mazda Miata with a DIYPNP (microsquirt module) using sequential injection and wasted spark ignition.

[2-stroke-driver]

Hi there,

I tried now the 3.3.2 beta 5 but my bike dosn't run with it. With 3.2.4 everything is fine. (I also tried 3.3.1a because I wanted the sequential shift)

It starts but it feels like a revlimiter at about 1300 rpm. I checked with the strobe: the sparks disapear and come back, disapear ...
There's no syncerror...?

I tried on my Bench (toothwheel 24-1 with the same pickup) and it works fine!?

My Setup:
- 2 Zylinder 2 stroke (RZ350)
- Wheel 24-1
- Rising edge
- going high (drives a two channel Kokusan CDI)
- COP

Regards

Uli

edit: found some misspelling...

[2-stroke-driver]

ok, only 3 attachments...

here the Trigger log and the msq.

[jsmcortina]

I tested out the MSQ on the tach issue and do see dropped pulses on the bench. I am investigating.

James

[jsmcortina]

I tested out the MSQ on the tach issue and do see dropped pulses on the bench. I am investigating.
James

This looks to be related to the A/C idleup code. Please turn that off for now.

I know how to resolve the issue, but I'm out of time for today.

James

[bearda]

I tested out the MSQ on the tach issue and do see dropped pulses on the bench. I am investigating.
James

This looks to be related to the A/C idleup code. Please turn that off for now.

I know how to resolve the issue, but I'm out of time for today.

James

I switched back to the 3.3.1 code to verify that it didn't have the same issue on the drive home today. I only went to the beta for the A/C idle up code, so I'll just stay on 3.3.1 until an updated beta is available and I can test the fix. Thank you for looking into it, I was afraid I'd really messed up my wiring or something.

[slyrye]

Under Output IO testmode "LED15/SprkC and LED16/SprkB" test output is swapped...!

[jsmcortina]

I tried now the 3.3.2 beta 5 but my bike dosn't run with it. With 3.2.4 everything is fine.

Investigating.
It looks like "Time after spark" has been broken since January 2013 in pre-3.3 alpha 9 and all subsequent releases.

Is that mode necessary for your CDI?

James

[2-stroke-driver]

...
Is that mode necessary for your CDI?
...

The CDI works best with this mode. I have no schematic of this CDI (it's stock in the Suzuki RGV 250) but it seems that the inside capacitor will not charge until the Inputs are low.
I' ll try to use 'fixed duty'

Regards

Uli