Strange thing with the redline (flaspro'd dbw s2000).
Strange thing with the redline (flaspro'd dbw s2000).
Hello guys! I will very appreciate any help, car (2006 dbw f22c, supercharged, 4bar map sensor) is not hitting redline, set in a flashpro manager to be at 8500 but it's hitting only like 7800-8200max, of course I keep push the pedal till the moment when ecu cuts throttle/ignition..what can be a problem? Attached one log...
You do not have the required permissions to view the files attached to this post.
Re: Strange thing with the redline (flaspro'd dbw s2000).
You need to post the calibration as well.
This code indicates that the throttle plate is not matching the commanded position from the controller. ie the throttle body is bad.
This code indicates that the throttle plate is not matching the commanded position from the controller. ie the throttle body is bad.
Re: Strange thing with the redline (flaspro'd dbw s2000).
I have a customers car with the exact same issue.
I have tried different base calibrations, etc.. no matter what we can not turn the thing past about 8600 rpms, it kills the throttle and throws a p2101 code.
I have tried different base calibrations, etc.. no matter what we can not turn the thing past about 8600 rpms, it kills the throttle and throws a p2101 code.
Re: Strange thing with the redline (flaspro'd dbw s2000).
Figured i'd add a little here.
with the rev limit set to anything under the stock rev limit there is never a problem with the throttle body, no codes, it works perfectly.
If I set the limiter above that about 50% of the time it will cut the throttle throw a p2101. If I turn key off then on it will go back to working fine for a while, then randomly it will do the same thing again (meanwhile the CEL is still on the whole time).
It could be just me, but it seems to do this more when the pc is connected to the flashpro and i'm live tuning or logging.
It also seems to do it less frequently with v1.2.8 than it did with the previous version of the software. I just downloaded v1.3.1 today and will try that as soon as my customer can get his car back to me.
I put around 200 miles on the car with the limiter set to stock, no problems at all. I do not think this is a problem with the throttle body.
I tried with both vsa on and off with no changes. There is nothing different in the data logs from a pull that works to a pull that doesnt work other than the TPS dropping to 0 when the cel comes on.
I have attached the latest cal from the car.
with the rev limit set to anything under the stock rev limit there is never a problem with the throttle body, no codes, it works perfectly.
If I set the limiter above that about 50% of the time it will cut the throttle throw a p2101. If I turn key off then on it will go back to working fine for a while, then randomly it will do the same thing again (meanwhile the CEL is still on the whole time).
It could be just me, but it seems to do this more when the pc is connected to the flashpro and i'm live tuning or logging.
It also seems to do it less frequently with v1.2.8 than it did with the previous version of the software. I just downloaded v1.3.1 today and will try that as soon as my customer can get his car back to me.
I put around 200 miles on the car with the limiter set to stock, no problems at all. I do not think this is a problem with the throttle body.
I tried with both vsa on and off with no changes. There is nothing different in the data logs from a pull that works to a pull that doesnt work other than the TPS dropping to 0 when the cel comes on.
I have attached the latest cal from the car.
You do not have the required permissions to view the files attached to this post.
Re: Strange thing with the redline (flaspro'd dbw s2000).
Our policy is not to change the behavior of the throttle apart from the target throttle table, but with the S2000 we cannot change any of the throttle control as it is handled by a separate module under the dashboard (not part of the ECU).
The error code is generated by the throttle control module when the actual throttle plate position does not match the target throttle plate (by 4-6 degrees). The error has to occur for a certain time period (250 to 500 ms) before the DTC is set, which could explain why it is variable. If you have a load dyno and hold the rpm you should get the error quicker.
The error code is generated by the throttle control module when the actual throttle plate position does not match the target throttle plate (by 4-6 degrees). The error has to occur for a certain time period (250 to 500 ms) before the DTC is set, which could explain why it is variable. If you have a load dyno and hold the rpm you should get the error quicker.
Hondata
Re: Strange thing with the redline (flaspro'd dbw s2000).
Tested this today and can confirm that the error is generated by the throttle control module and is not related to rpm. I held the rpm over stock rev limit for some time and did not get the error until I manually levered the throttle plate (which is quite hard to do btw).
Hondata
Re: Strange thing with the redline (flaspro'd dbw s2000).
Where should we even start to try and fix this? If its like you say and can't be an issue with the flash pro would you suggest the controller is bad, maybe the throttle body?
By my logic it has to be related to the flash pro, but I have been wrong before.
By my logic it has to be related to the flash pro, but I have been wrong before.
Re: Strange thing with the redline (flaspro'd dbw s2000).
Let me explain further.
The ECU looks up the target throttle plate from the throttle look up table (indexed by accelerator pedal position and rpm).
The ECU transmits this information to the throttle control module via a data link.
The throttle control module knows the target throttle plate (from the ECU) and the actual throttle plate (from the throttle body). It then uses a closed loop algorithm to control the throttle body motor, aiming for the target throttle plate.
The throttle control module returns to the ECU the actual throttle plate position and any error codes via the data link.
The throttle control module has error conditions for the throttle position sensor and the motor controller. The P2101 error is from when the actual throttle plate is not the same as the target throttle plate. There are also error conditions for over-current on the motor and various throttle position sensor problems.
With the original throttle body I think the P2101 is only going to occur if either the throttle position sensor is out of alignment or the throttle plate stops have shifted. Furthermore, I'd only expect to see the error at one end or other of the range (idle or WOT). There could be other conditions (high current, low battery voltage for instance) but it seems that the TPS vs plate range would be a good guess. A datalog showing the problem occurring would be helpful at this point.
This is why I'd start with the throttle body. BTW I've seen a lot of throttle body failures. The real challenge is obtaining a consistent failure (hunch my recommendation for a load dyno).
The ECU looks up the target throttle plate from the throttle look up table (indexed by accelerator pedal position and rpm).
The ECU transmits this information to the throttle control module via a data link.
The throttle control module knows the target throttle plate (from the ECU) and the actual throttle plate (from the throttle body). It then uses a closed loop algorithm to control the throttle body motor, aiming for the target throttle plate.
The throttle control module returns to the ECU the actual throttle plate position and any error codes via the data link.
The throttle control module has error conditions for the throttle position sensor and the motor controller. The P2101 error is from when the actual throttle plate is not the same as the target throttle plate. There are also error conditions for over-current on the motor and various throttle position sensor problems.
With the original throttle body I think the P2101 is only going to occur if either the throttle position sensor is out of alignment or the throttle plate stops have shifted. Furthermore, I'd only expect to see the error at one end or other of the range (idle or WOT). There could be other conditions (high current, low battery voltage for instance) but it seems that the TPS vs plate range would be a good guess. A datalog showing the problem occurring would be helpful at this point.
This is why I'd start with the throttle body. BTW I've seen a lot of throttle body failures. The real challenge is obtaining a consistent failure (hunch my recommendation for a load dyno).
Hondata
Re: Strange thing with the redline (flaspro'd dbw s2000).
Would there be anything in the system that would act differently above a specific RPM?
I'll see if we can hunt down a different throttle body and try that. We dont have access to a load dyno with out driving for 2 hours.
I'll see if we can hunt down a different throttle body and try that. We dont have access to a load dyno with out driving for 2 hours.