Megasquirt Support Forum (MSEXTRA)

He isn't using the standard code, but I wonder if the behaviour he's seeing might be caused by the standard code I highlighted yesterday. i.e. when the ISR accumulates the samples then falls through (wrongly, I'd say) to the sampling window code. The symptoms sound like when the sampling window is too narrow. Shouldn't be since he's using the sample average option. With the new flags, there are new combinations. I can't tell at a glance that all possibilities are covered and perhaps a few relics from an old config take the code down an unexpected path.

Have fun,

Rob.

robs wrote:He isn't using the standard code.

If he is using 2.4.4 then it may be the changes I made to ensure MAP is sampled when averaged and the engine isn't running.

The standard 3.3.0b didn't average sample when engine was stopped (as it relied on an ignition pulse to pull the sample out) and I changed a few things to allow it to work whilst not running. I don't believe issues exist, but will look at it tonight when I get home.

G

Trumpetrhapsody wrote:Looks like my MAP value hangs at the initial startup value... which would explain alot.

Now gurus, why would enabling map sample averaging mode cause this?

Any chance of trying the real 3.3.0b as I can't immediately see any reason why this would occur in the mod 2.4.4, as folks who've tried 2.4.4 haven't reported this issue (and I don't see it myself).

If the issue presents itself in 3.3.0b then the issue might be a type of config as generally again most folks dont' see any problems.

The only thought was that the non-averaging settings might still be in play (as Rob's pointed out) so I will look at that to see if it could possibly impact things.

G

Sure, I'll load up the generic 3.3.0b at lunch and report back. Thanks guys!

It's doing the same thing on the straight 3.3.0b code.I can switch back and forth and as soon as i go averaged the MAP value sticks.

Trumpetrhapsody wrote:It's doing the same thing on the straight 3.3.0b code.I can switch back and forth and as soon as i go averaged the MAP value sticks.

Have you posted your msq? This is likely something specific to your configuration.

Ken

I posted the MSQ I was using with the gslender mod near the end of the previous page, but if you want it I'll attach the one I was just using on the straight 3.3.0b.

Trumpetrhapsody wrote:It's doing the same thing on the straight 3.3.0b code.I can switch back and forth and as soon as i go averaged the MAP value sticks.

I've repeated this on the bench.

James

Fixed it ready for next release.

James

jsmcortina wrote:Fixed it ready for next release.

James

So what was broken or wrong?

Ah excellent! Glad it was something simple. 20 minutes is quite the impressive turnaround ;)

Does "ready for next release" mean I have to wait for 3.3.0c, or have you re-uploaded 3.3.0b with the fix?

Thanks!

Trumpetrhapsody wrote:.....
Ah excellent! Glad it was something simple. 20 minutes is quite the impressive turnaround ;)
...
Thanks!

That's why I keep coming back, great service.

Try the veal!

There was a thread a while back about cutting spark during overrun to make the engine decel faster between gears, but I can not find it at all. Does anyone remember the title?

AdamR wrote:There was a thread a while back about cutting spark during overrun to make the engine decel faster between gears, but I can not find it at all. Does anyone remember the title?

Hi, this ? http://www.msextra.com/forums/viewtopic ... 91&t=43197

AdamR wrote:There was a thread a while back about cutting spark during overrun to make the engine decel faster between gears, but I can not find it at all. Does anyone remember the title?

It is this release, or at least it should be.

G

gslender wrote:

AdamR wrote:There was a thread a while back about cutting spark during overrun to make the engine decel faster between gears, but I can not find it at all. Does anyone remember the title?

It is this release, or at least it should be.

G

It is and works well.

Dropping my lag to 50 in addition to the averaging got rid of any ill effects of resonance at pq tq and pk hp for me, and it's running fabulous now. (after remapping everything, sometimes I wish there was an option to reverse the effect of VEAL i.e. change AFR target table if the VE table is ~perfect, might be useful post dyno)

Dropping my lag to 50 in addition to the averaging got rid of any ill effects of resonance at pq tq and pk hp for me, and it's running fabulous now. (after remapping everything, sometimes I wish there was an option to reverse the effect of VEAL i.e. change AFR target table if the VE table is ~perfect, might be useful post dyno)

This feature exist. You need to set "Incorporate AFR target" to "include AFR target" in the General Settings. You need to specify the stochiometric AFR for your fuel. I'm not sure how it works exactly, but I know that is does just what you want to do.

Sam

pit_celica wrote:

....sometimes I wish there was an option to reverse the effect of VEAL i.e. change AFR target table if the VE table is ~perfect, might be useful post dyno)

This feature exist. You need to set "Incorporate AFR target" to "include AFR target" in the General Settings. You need to specify the stochiometric AFR for your fuel. I'm not sure how it works exactly, but I know that is does just what you want to do.

Sam

Cool, I'll give it a shot, thank you!

Hi all,

I have just uploaded this new firmware to my MSII and every time i power up the MS i get a Settings Configuration error.
The reported setting error is "INVALID MAP SAMPLING ANGLES. NEEDS TO BE LESS THAN 180 DEG FOR 4CYL OR 90DEG FOR V8"

What does this mean and where is the setting to change this.

I am running a SBC 5.7 TPi with EDIS.

I have had this on the 3.2.1 firmware also.

Please help

Andy

I loaded 3.3.0b on my car last night and it is working pretty well . I have not made any changes to enable any of the new features but I do notice my idle isnt quite as steady especially recovery on startup . Otherwise it is working just as good as 3.2.1. The engine stalled on me last night on the testdrive following a fairly long fuelcut overun decel down a hill which is a first time occurance . Not sure what tweaking I need to do to the MSQ to correct that. I havent toyed around with it yet.