Toyota GR86 Forum - GT86 Forum, Subaru BRZ Forum, Scion ... banner

Abnormal throttle fluctuation issue

3 reading
156 views 7 replies 4 participants last post by  DaffyDOHC  
#1 ·
Hi GR86 forums,

BRZ 2023, 25k km, single owner. I have an issue where the throttle body is opening and closing by itself without any throttle being applied. Please see this video: https://photos.app.goo.gl/9miRReWEpWxLd7qr8

In the video, I'm rolling, then letting off the gas, pushing in the clutch, and going on the brakes as you can see from the left of the dash. The RPMs will rise to 2500 RPM before falling back to normal idle.

This can happen with varying intensity. Sometimes it will not happen, and other times it will go to 3000 RPM, fall back down to 1500, climb back up to 3k RPM a couple times before idling normally.

This behaviour is obvious when you push the clutch down since you'd expect RPM to drop. But I think it's happening even when I'm driving. It's more subtle but I feel it most when I'm driving slow between 20 and 30 kph (think traffic scenario). The car will jerk back as if I pressed on the throttle, and then jerk to the front as if I suddenly let go and it's engine breaking.

This weird behaviour will stop as soon as you go to neutral. Only happens when you're in gear.

It seems like it's also temperature dependent. After a cold start, it will no do it for a few minutes. When I'm in traffic, or stuck in a drive-thru for example, it will be the most drastic.

I have been to the dealership many times. I have also been to a private mechanic specialized in Subarus. They say there's nothing wrong mechanically with the car (no error codes, sensors are all good, no vacuum leaks, throttle body is clean, etc.). I've gotten conflicting information from Subaru dealership: they noted the behaviour, but they didn't know how to correct it so they've been in contact with the Subaru Tech-line. Subaru Tech-line says they're had this issue with the Crosstrek manual before, and that it was solved with an ECU update. No such update yet for BRZ, and no timeline. After pushing them for a while, they're now saying Tech-line has compared this behaviour with another BRZ on their side, and it's normal behaviour. So it seems they don't think there's a problem, they're not working on an update. But they were also saying when an update will come it will solve my issue (conflicting info...). I've also sent a letter to Subaru Canada, but all they did was refer me to the dealership.

The private mechanic was baffled at that. He says it must be programming. He showed me telemetric reading of the throttle body opening and closing by itself after he let off gas and pushed in the clutch. He's saying only Subaru can solve that, unless I'm willing to install an aftermarket tune (but I want to keep my warranty).

I've already posted about this issue on the forums before, but none of the suggestions solved it. So if anyone has any other suggestions please let me know. Sorry for the wall of text, but I wanted to write a detailed description.

I'd also like some advice on what to do moving forward to force Subaru to fix my car. I don't have social media to put any pressure on them. I think my next step is to write a legal letter?

Thank you!
 
#2 ·
I had this same issue after I installed a supercharger. But I would intermittently get a throttle body engine code. Surprised, you're not getting one.

My RPMs would only rise to about 2.5k when clutch is in only in gear. I would have to put it neutral to get the rpms to drop. In parking lots, the rpms would stay around 2k-2.5k for a while so in 2nd gear it feels like im speeding through a parking lot.

After 6 months of replacing throttle bodys and head scratching, a friend suggested we try straightening out wires as much as possible around the throttle body, MAF and MAP and checking the pins in the throttle Body connector and accelerator Pedal sensor. Making sure they are all seated properly. Even applied conductor enhancing soultion to the pins.

After this my car has been running normal. No weird rpm issues. Not sure if it will fix your issue as your engine code never comes on.


Hope this helps.
 
#4 ·
Thanks for your reply! So some of your wires were bent and you made them more straight? I'm guessing you had to work with these wires during the supercharger install and maybe that messed with them?

Regarding the conductor enhancing solution, was it dielectric grease that you put? And that was to all the connectors that you mentioned? (throttle body, MAF, MAP, accelerator pedal sensor)

That's very helpful, I'll try that.
 
#3 ·
Could need a MAF sensor cleaning. Or it could also be a response to learned driving behavior, much like people who experience rev hang when others do not. It looks like the car is briefly holding revs waiting for you to shift gears, which is what most would expect after an acceleration followed by a clutch press.
It seems pretty normal to me.
 
#5 ·
Yes good idea, will clean the MAF. Thanks for the suggestion.

It could be learned behaviour I guess. But it's more than holding the revs, it's litterally revving up and down (maybe not that obvious in the video). Do you know if a battery disconnect is sufficient to reset learned driving behaviour?
 
#6 ·
I have dealt with what I believe was the worst rev-hang ever released to consumers (first year VA WRX) and it wasn't quite as bad as what I see from 0:05 to 0:08 in your video. That is pretty crazy. A battery disconnect would reset learnings and couldn't hurt to try in this case.

Did you check your floor mats? haha

Honest question though - does it do that consistently enough that you'd think a dealer tech could replicate it? I'd expect whatever the fix would be to be covered by powertrain warranty, especially considering the nature of the problem
 
#7 ·
It's so intense I'm calling it rev rise :')

I just disconnected the battery for a few minutes, will see how it goes next time I drive it.

Yeah floor mats are not in the way.

Now it's doing it almost every drive. The dealership told me they were able to replicate it, so they opened a ticket with Subaru tech line. At first the answer was that it needed a future update. Now they're kinda saying it's normal behaviour...