any tips to tune out an off idle stumble?

woh · Post by **woh** » Tue Mar 28, 2006 11:26 am

AW

Could you explain a bit more. Isn't the 26 stuff incorporated in the 29 code??

whittlebeast · Post by **whittlebeast** » Tue Mar 28, 2006 11:31 am

029XX at one point was having issues as the rpm stuff was being merged. I was going to try to do some testing tonight on 029L

AW

woh · Post by **woh** » Tue Mar 28, 2006 11:33 am

I'm running 29j with no problems. Is there any point in going to 26h8

whittlebeast · Post by **whittlebeast** » Tue Mar 28, 2006 11:47 am

I would not go backwords if you are not having issues. Most of these issues come up with certian combinations in MSQs that were never spotted in testing. I would think that 029 will eventualy have EVERY feature that was developed in O26h8 It was never the intent to have two codes that were both considdered "Extra" What happened was James and Ken went on a mission to clean up some RAM and went down the 029 road wile Phil and I were messing with some AE issues and we started with the last known dead stable code 026h4 at the time. At about the time Phil and I came up with a AE solution James and Ken were homing in on the RAM issue. When the two codes were rolled together in a few 029 releases ago a few new issues poped up. This may be all fixed now but it will take a little testing to find out if all the features have been rolled in.

woh · Post by **woh** » Tue Mar 28, 2006 12:20 pm

Thanks AW

About the number of cycles. Is that the same as the "Accel time (s)"?

I just came back from trying out MAP based AE. It helps to have the background of this Post and Mike's write up (I have an MG too). So far so good.

whittlebeast · Post by **whittlebeast** » Tue Mar 28, 2006 1:15 pm

Cycles makes it so that AE times out twice as fast at 6000 RPM compared to 3000. That label in MT needs to be changes but we keep forgeting. Remember you also have the choice of MAPDot or TPSDot to trigger on AE. Do not confuse this triggering choice with the ms of AE at each RPM. If you have a stim, I strongly advise getting the code running on a stim and watching what eack setting does.

AW

jsmcortina · Post by **jsmcortina** » Tue Mar 28, 2006 1:52 pm

Following what Andy said, I got a mail from Phil earlier clarifying that the AE code in 029L should be the same as 026h8.

Any suggestions on wording changes in the Megatune menus etc. please PM me direct as well as posting because I don't manage to read _every_ post here!
Although usually once I've started reading a topic I do follow it.

James

woh · Post by **woh** » Tue Mar 28, 2006 1:55 pm

Cycles makes it so that AE times out twice as fast at 6000 RPM compared to 3000

OK, I understand that. And the label is wrong.

Do not confuse this triggering choice with the ms of AE at each RPM.

I'm not clear on that. I have selected MAPdot and have MS1v3. I put in 1.5 where is says "Accel time (s)". Assuming 15 cycles per Mike above. Do I have a choice of RPM as well when selecting MAPdot. Or is it only one of the three; MAPdot, TPSdot, or RPM

Yes, I have a stim and I'll try these out, but not until I play with it a bit more.

Sorry for being a stickler on this, but I want to clear up my understanding. And to think I was happy with the TPSdot AE. There is so much more opportunity beyond just getting it working

jsmcortina · Post by **jsmcortina** » Wed Mar 29, 2006 4:52 am

woh wrote:About the number of cycles. Is that the same as the "Accel time (s)"?

Would changing the labels to "Accel time/cycles" help matters? The selection between seconds and cycle ought to be moved onto a closer menu too.

James

whittlebeast · Post by **whittlebeast** » Wed Mar 29, 2006 5:48 am

jsmcortina wrote:The selection between seconds and cycle ought to be moved onto a closer menu too.

Eventualy I think it would be good to move all of the AE tuning to one screen but this would most likely involve Eric, MS2 and Extra. With extra this would also invole moving all the AE settings to one page in flash. I hear this is all rather involved to accomplish.

AW