VAFC 2 Issue
06-02-2014, 10:40 AM
#1
Registered User
Thread Starter
VAFC 2 Issue
VAFC 2 throws a check engine for Vtech malfunction, setting were basically stock, all i did was drop it to 5800. Was going to get tune after new clutch so didn't mess with it much.
Last time it threw the code the RPMS would just sit there right around 6-7K and felt like fuel was cut, had some backfire.
I changed the vtech engagement back to stock and cleared code and car runs fine, but now I'm worried about getting a tune with it if this will happen after and money is wasted.
Any help would be helpful.
Last time it threw the code the RPMS would just sit there right around 6-7K and felt like fuel was cut, had some backfire.
I changed the vtech engagement back to stock and cleared code and car runs fine, but now I'm worried about getting a tune with it if this will happen after and money is wasted.
Any help would be helpful.
06-04-2014, 05:04 PM
#2
I used the vafc 2 on my 97 supercharged civic and it always set a check engine light for vtec. But only if I hit vtec before the engine got to normal operating temp. The factory ecu has a safety on the 99-00 b16 si that wouldn't allow vtec to engage until the car was at operating temp. The vafc bypasses that safety. Which COULD be why your setting a vtec code. If the ECU sees the vtec pressure switch engaged below X temp it sees a fault and sets the code. Now not 100% sure if it works the same way on the S2000 but it's highly likely.
06-05-2014, 05:22 AM
#4
Registered User
Thread Starter
I used the vafc 2 on my 97 supercharged civic and it always set a check engine light for vtec. But only if I hit vtec before the engine got to normal operating temp. The factory ecu has a safety on the 99-00 b16 si that wouldn't allow vtec to engage until the car was at operating temp. The vafc bypasses that safety. Which COULD be why your setting a vtec code. If the ECU sees the vtec pressure switch engaged below X temp it sees a fault and sets the code. Now not 100% sure if it works the same way on the S2000 but it's highly likely.
I didn't write down the actual code, Ill try to see if I can still get it.
06-13-2014, 07:37 AM
#6
Registered User
Thread Starter
Trending Topics
06-30-2014, 11:37 AM
#8
Registered User
Thread Starter
Nope, checked the wiring, it was all good. Threw the code again, vtech was set to 5900, forgot to check the exact code again though. Set it to 6100, had a full day of autox and no codes with that setting, anytime its set to below 6100 it eventually throws the code and feels like a fuel cut.
