i have burned several maps with the willem eprom burner and they have all came out good with no problems. i have recently bought another civic and got a socketed p72 ecu. i burned an all motor map to a atmel at29c256 (the chips i've always used) with vtec set at 5300. i test drove the car and vtec will kick in at 6k all the time. i set the vtec at 5k and vtec will still kick on at 6k. i've tried reburning the map a few times, but i still get the same results. anyone have any idea why this would happen? i never had this problem before.

any thoughts.

 

1. Verify the data on your eprom chip
2. Try setting vtec at 4500 rpms just for testing

 

verify it after i burn the map on it? its been like over a year since i burned chips, so i may be leaving something out.. dunno.

i will test it at 4500 on my next day off and see what happens


i put the chip in the burner
i check the id
erase chip
do a blank test
verify chip
clear buffer
then i load the map
then i burn the map on the chip

i think that the order i do it in. i'm using crome with a willems burner

 

Sounds like you are doing it correctly.
When you open the .bin file is the vtec point what you previously saved it at ?

Perhaps your tachometer is off ?

 

yeah, the vtec is still set at 5300 when i open the .bin

i thought about the stock tach being off, but i tried a friends ecu when i first got the car running and his vtec is set at 4800, but with i think an h22 map, and it kicked in right at 4800.

i tried another chip this morning and vtec still kicked in at 6k. i'll reburn it and set vtec at 4500 to see what happens.

also, i did burn my friend a chip and the same thing happened to him. vtec set at 5200 on his chip, but it didn't kick in until 6k. he drives a 99 si . before i reburned a new map for him, vtec was kicking in at 5300 where vtec was set at on the previous map.


when i burn the .bin on the chip, the buffer won't stay at 800 correct ? (its like xx800 when you clear the buffer, don't remember exactly what it is. i'm not at home or i would check)


i would like to try one of your chips, but i would just hate to buy one and the same thing happens you know.

 

Maybe J1 has been cut

 

you think that would cause vtec to kick in later than what its set at?

i'm going to get a friends chip and try it out in my ecu to check if vtec kicks in where his vtec is set at. i'm not sure who he got his chip from , but i know vtec kicks in when it should on his car.

 

If j1 is not properly jumpered the ecu is not reading the chip at all, hence the reason your chip is not doing anything.

 

then wouldn't i get a check engine light if its not reading the chip right? i have a gsr motor in a eg hatch. i don't have the knock sensor, iabs, or an o2 sensor. they are disabled via the .bin. if it wasn't reading the chip, i would think i'd get a cel ....

 

Yes, you probably would :-)

 

i got a chip from my friend and tried it out in my ecu. the vtec on his chip is set at 4800 and when i tested it in my ecu, vtec kicked in right at 4800.

think something with the willem burner is not right?