[sub_ETCS_ret]

I just don't understand how the secondary cats have anything to do with throttle position but it sounds like you guys have experienced it.

Maybe Vitesse could shed some light on this.

Sent from my SM-G920V using Tapatalk

[Sunsnare98]

Originally Posted by sub_ETCS_ret

I just don't understand how the secondary cats have anything to do with throttle position but it sounds like you guys have experienced it.

Maybe Vitesse could shed some light on this.

Sent from my SM-G920V using Tapatalk

Think about it this way...

When you delete cats you create more airflow. At 50% throttle your ecu calculates a certain amount of air to pull and a certain amount of fuel. Because there is better flow, more air will be pulled with that effort and the ecu will actually think your at let's say 60% throttle instead, when your actually at 50. It doesn't become an issue until your at 100%, because when you give 100% throttle the ecu thinks your at 110% and it thinks that is impossible so it throws a code.

The ecu has a built in learning curve to adapt to different altitudes. So that's why the throttle controller doesn't throw codes stock. But when you start modding things that slightly effect a/f ratio, it becomes an issue.

[sub_ETCS_ret]

Originally Posted by Sunsnare98

Think about it this way...

When you delete cats you create more airflow. At 50% throttle your ecu calculates a certain amount of air to pull and a certain amount of fuel. Because there is better flow, more air will be pulled with that effort and the ecu will actually think your at let's say 60% throttle instead, when your actually at 50. It doesn't become an issue until your at 100%, because when you give 100% throttle the ecu thinks your at 110% and it thinks that is impossible so it throws a code.

The ecu has a built in learning curve to adapt to different altitudes. So that's why the throttle controller doesn't throw codes stock. But when you start modding things that slightly effect a/f ratio, it becomes an issue.

Well that sucks. So basically it's a good little gadget for tooling around but not for much more. Goes back to what people keep saying, if you want real throttle response then get a tune. Personally the ole check engine light would make me want my money back.

Sent from my SM-G920V using Tapatalk

[Sunsnare98]

Originally Posted by sub_ETCS_ret

Well that sucks. So basically it's a good little gadget for tooling around but not for much more. Goes back to what people keep saying, if you want real throttle response then get a tune. Personally the ole check engine light would make me want my money back.

Sent from my SM-G920V using Tapatalk

Yeah dude it sucks. It's not just the cel though. The car goes into limp mode and won't let you go over like 40 mph. It's downright dangerous if it happens on the highway.

My foot is now my throttle controller : )

[MrChrisLS3]

Try recalibration, it should work. I think the mistake many make is that they do modifications, like a CAI, exhaust, PTB, and such, and don't think to recalibrate the controller.

[Sunsnare98]

Originally Posted by MrChrisLS3

Try recalibration, it should work. I think the mistake many make is that they do modifications, like a CAI, exhaust, PTB, and such, and don't think to recalibrate the controller.

Yeah you're right...recalibration works as long as it's within the stock learning curve. If it's too far out you're out of luck.

[Megahurtz]

Originally Posted by Sunsnare98

Deleting your secondary cats changes your airflow and throttle response a bit. As a result, your throttle controller causes your throttle position sensor to think there is too much juice going into your throttle. As a result, you'll get a throttle
Position voltage CEL.

the same principle can be applied to your cai. The factory throttle position sensor has a range that it can be in without throwing codes. The vitesse at WOT pushes that boundary, and any other mods that effect throttle
Response even slightly will cause issues. Especially on a higher setting on the throttle controller.

I learned this from dealing with the issue myself. go read the code at an autozone and you'll see what I'm talking about. It has nothing to do with calibrating it.

Thanks for the explanation. It seems like the throttle controller is what really pushes the boundaries.