Skunk2 TB issues + crome issues
Hello fellow honda users , I have a b20vtec engine with a skunk2 TB (Alpha series) paired to a bored out b16a2 IM.
The throttle of the car was sticking , so we manage to twist and get 1 one more turn from the spring of the TB (which solved the problem) but for the TPS we are couple of degrees off (right now on the furthest I could possibly set it) reads 0.61V at closed (0% throttle) and with the engine turned on goes down to 0.56V.
So we decided to change it from the crome software in order to have a proper idle.
Up until this point I didnt had a check engine light , no codes no nothing. So we managed to pass the .bin file via programmer into the crome software and we tried to change the limiter (more aggresive one and re-calibrate the tps from 0.45V min value to 0.6V and the maximum levels as well. which it didn't work.
After some searching , we enabled Byte hack and also disabled the checksum routine , still nothing. Now we get 2 errors regarding TPS and MAP sensor , car feels fine top-end aswell , didnt try to mess with anything else (mapping and stuff since it works just fine). The plugs are in the correct order but we are not sure how to proceed with that anymore. I am guessing since the TB is a few degrees off , the map sensor and tps when "talking together" they see different values or not the ones that they expect and causing all these problems.
Check engine light only came after we loaded the same bin file with a few differences on the limiter and tps numbers. (Before it would just idle high).
Are there any settings that we are missing or some auto calibration function? (We don't have moates programmers and stuff like that).
Any help would be greatly appreciated , kinda new to crome and this stuff
The throttle of the car was sticking , so we manage to twist and get 1 one more turn from the spring of the TB (which solved the problem) but for the TPS we are couple of degrees off (right now on the furthest I could possibly set it) reads 0.61V at closed (0% throttle) and with the engine turned on goes down to 0.56V.
So we decided to change it from the crome software in order to have a proper idle.
Up until this point I didnt had a check engine light , no codes no nothing. So we managed to pass the .bin file via programmer into the crome software and we tried to change the limiter (more aggresive one and re-calibrate the tps from 0.45V min value to 0.6V and the maximum levels as well. which it didn't work.
After some searching , we enabled Byte hack and also disabled the checksum routine , still nothing. Now we get 2 errors regarding TPS and MAP sensor , car feels fine top-end aswell , didnt try to mess with anything else (mapping and stuff since it works just fine). The plugs are in the correct order but we are not sure how to proceed with that anymore. I am guessing since the TB is a few degrees off , the map sensor and tps when "talking together" they see different values or not the ones that they expect and causing all these problems.
Check engine light only came after we loaded the same bin file with a few differences on the limiter and tps numbers. (Before it would just idle high).
Are there any settings that we are missing or some auto calibration function? (We don't have moates programmers and stuff like that).
Any help would be greatly appreciated , kinda new to crome and this stuff

So just an update , we did some testing with IACV and it dropped the idle dramatically , so we did through crome IAT Compensation -25% , we are currently playing with tps values , since tps CEL still there , car feels great though , will most likely update tommorow, in case more of you have this issue , but the general idea is at the moment , to make map and tps communicate together , right now tps , seems to understand that its idle , but map sees too much pressure and basically the ecu thinks that tps is off. We have couple of solutions in mind but needs a lot of testing.
Haven't had the time for any more tweaking the last few days , I was wondering 2 things , CEL is throwing tps error , does the ecu completely ignores the tps (even in top-end) + if I set crome to ignore the map sensor (bellow the mBar that is currently reading at idle) , should the error go away + will I have any issues or should be good to go?
Get Hondata and get rid of that cheap chrome chip and at the very minimum have a proper base map put in.
Setting the TPS values in Hondata takes like 5 secs.
Setting the TPS values in Hondata takes like 5 secs.
Thread
Thread Starter
Forum
Replies
Last Post







