even a TPSdot threshold of 25 is too low. Sometime in 2.1.0 development, I realized that the math there was generating TPSdot numbers that were 10x too low, so I fixed it. Whatever you were using before, you should probably multiply it by 10. Before I switched to EAE, I was using values that are around 50-60 %/sec.

Now with EAE enabled, I don't really need much normal AE at all, so I have it set to a tiny amount of fuel with the threshold at 250, so it only engages on quick stabs during rev-matching, and even then only a little bit to get EAE started enriching a little sooner.

Ken

 

Can someone explain to me exactly what the whole %/sec means? Is it, for example, if you have the number in there at 25, that you would have to move the gas pedal at a rate of 25% or more per second?

 

Yes, it's a rate. If the threshold is at 25% per second, you would have to move it at a rate of 25% throttle per second to trigger it.

25%/sec is pretty low though.

The number itself essentially (this throttle position - last throttle position from 10 ms ago) * 100 (since 10 ms is 1/100th of a second). This can lead to a little jitter which is why you need to have the threshold in the first place.

Ken

 

Ahh, i'll give it a swirl today on my car and see if I notice anything different. I definatly don't seem to have my accel enrichments going on all the time though. It might have something to do that my first cell for accel enrichments is like at 30% and moves up to 100%, maybe if i had that set to say like 5% I would see more of a jerking movement.

 

I'm actually thinking about a few changes to the way that sampling is done that may make the calculation of TPSdot more accurate and less jittery. That will go into ms3 first and then into ms2/extra if it works alright.

Ken

 

So i tried changing my TPS threshold on my car to about 50%/sec and made things ALOT worse. At idle the car kept on triggering the accel enrichments. I have Firmware 1.0.2 if that makes a difference.

 

ahh, I didn't realize anyone was still using 1.0.2. That firmware is 2.5 years old now! I'd switch up to 2.1.0 if I were you.

However, making the threshold higher will not make it trigger more often, there's another issue if that is what happened.

Ken

 

Lol ... but there's nothing wrong with the 1.0.2 firmware for me to switch to the 2.1.0 right now, or is there?

What do you think the issue would be?

 

There are TONS of fixes and improvements all over the place. The 2.1.0 code is probably one of our most stable versions yet.

I can't even remember all the things we fixed and improved.

Ken

 

I'll consider it ... I will be supercharging sometime so I'm going have to go down that route anyways.

 

HEY HEY back on track here :P
JK JK.
il try to set the tps to 250 in the morning and see what happens il keep you posted

 

ok so setting the tps to 250 makes my car do the same thing as dj55b car cant be drivven at all... well i have not tried it since i fixed 99.99% of my "car stutters at high boost afrs are 11.5-12 @ 5psi " problem
on the faq section for ms2 at http://stuff.pw.cx/Megasquirt%20MS2%...azda%20CAS.pdf
it says the setting for the Second trigger active on should be: Rising edge (what i had it set to)
but reading the settings at http://www.diyautotune.com/tech_arti...zda_fc_rx7.htm
i found that it should be set to Ignition input capture; Rising Edge and Second trigger active on: Rising Edge. this has solved most of my prob. as the car is now so smooth and pulls much harder im nolonger making more then 5 psi of boost so the waste gate is working like it should be instead of boosting 15 psi and more.
the car dose not shutter while cursing/soft and or hard accell.
the next new prob is the 7000-7500 rpm place. where the car dose a loud backfire and on the fuel vetable it jumps from 7500rpm back to 6000 rpm then back to 7000-7500rpm range ish. but no other place is it bad so it could just be a timing thing il have to data log that and figure out whats causing that so for now i just set my rev limiter to 5800 rpm just to be safe

thanks for all your help! hope this helps the next guy out!!!!!

 

I wasn't suggesting that you set it to 250...

I was suggesting 50-100.

The 7500 rpm problem sounds like you still have a bit of noise on your CAS signal... sometimes the misfires can cause noise and sometimes it's the other way around. You can try turning on the second trigger noise filter and see if that helps.

Ken

 

cool thanks

 

Well was out with martin today again and did some more playing around. With the setting that he had changed previously, it would cut out as he mentioned around 6500rpm and looking at some logs it was getting noise or something but we got sync error #17.

Turning on the noise filter with that setting still proved to do nothing and so I went back to the old setting and my old stuff to restart some things with. All I changed from my previous things, is turn on the noise filter on and place in these values:

500rpm - 500 usec
2500rpm - 350 usec
5500rpm - 175 usec
8500rpm - 15 usec

Using that we have now gotten rid of the boost spikes somehow, and runs perfectly in the top end and doesn't go over about 5-6 psi. We can use either my timing map, or Aaron's map numbers for the boost area and both will work fine, but my values definatlly make that tach jump alot quicker from 6k rpm to 8k rpm.

 

Hrmm, that means you've definitely got some noise issues.

Did you guys make the mods to the 2nd trigger conditioner that I suggested?

Also, on the primary trigger (since you've apparently got noise issues there too) have you tried adjusting the hysteresis potentiometer on the v3 board?

Ken

 

If you're referring to the ground mod for the 2nd trigger, then yes.

This noise showing up those codes only started happening when Martin changed his Ignition Input Capture to Rising Edge although his board is wired to VROUTINV and Falling Edge should be selected with that wiring configuration. Not sure if that would of created more issues as far as noise.

The car as it sits right now though (reverting back to falling edge) doesn't show any error codes and can take it up to his current rev limiter of 8500 rpm. Wouldn't just keeping it on like this with the Noise filter on work just fine since thats what the noise filter option is there for?

I'm kinda curious to see if we turn it off and try it again if it will work like that. We just opted to re-upload the old map and turn on the noise filter. Martin is going to be driving the car for a few days to see if the boost spikes in high rpm re-appear or not so we'll keep you posted.

 

well car started well today, and ran fine, boost is staying at 5-6 psi with the waste gate hooked up to the turbo (no controller yet) and seams fine, i can hit 8k rpm with what seams to be no bugs at this time.

 

If it's working sure. The noise filter when turned on does make the code run slightly slower, but most likely it's not anything that would be noticed while driving.

OK.

Ken

 

Just updating that the car has been working good still since the changes. Just very minor tuning to correct AFR at driving speeds but thats about it.

 

Yeah, did you set the timing on the MS to -5, and then adjust the CAS until the timing measured with a timing light was -5?

Ken

 

Yes that is how its suppose to be set.