PATCH: CEL Flash on Loaded Knock
Aug 28, 2007, 08:57 AM
#166
I know some one mentioned this earlier in the thread...but hooking up a LED or warning bell to pin 36(Evo 8 - http://www.evomoto.com/tech_info.php..._5&tech_id=19).
Anyone happen to know the voltage from that wire or am I going to have to bust out the multimeter and read a tapped wire while going down the road
Anyone happen to know the voltage from that wire or am I going to have to bust out the multimeter and read a tapped wire while going down the road
Aug 28, 2007, 11:14 AM
#167
Evolving Member
iTrader: (5)
Join Date: Nov 2004
Location: Pingree Grove, IL
Posts: 187
Likes: 0
Received 0 Likes
on
0 Posts
I'm having an issue with the "CEL on knock flash time". I have tried a couple different ranges from 1500-3000ms and whenever the required knock sum is met, the CEL will flash but will continue to do so for several minutes before it stops. I read the ecu after every flash to confirm the settings change and they do.
My ROM ID is 94170008. I'm also running ecuflash version 1.31. At first from my reading I thought some of the issues with version 1.31 were limited to the IX definition files. Could it be a problem with ver 1.31 or is there anything else I should be looking at?
Thanks,
Chris
My ROM ID is 94170008. I'm also running ecuflash version 1.31. At first from my reading I thought some of the issues with version 1.31 were limited to the IX definition files. Could it be a problem with ver 1.31 or is there anything else I should be looking at?
Thanks,
Chris
Aug 28, 2007, 11:05 PM
#170
Evolving Member
iTrader: (5)
Join Date: Nov 2004
Location: Pingree Grove, IL
Posts: 187
Likes: 0
Received 0 Likes
on
0 Posts
Thanks a bunch for taking the time to put this together. I was running DSMLink previously in the Evo and this was one feature I was quite fond of.
Aug 30, 2007, 08:20 PM
#173
There is no FAQ, self patching is a minefield which I would NOT advise people to get into..
its not as simple as changing a few numbers in maps - this is altering the flow of the ECU code... which if you get wrong could be rather fatal!!!
time constraints on my end are stopping me from doing much more with this particular project... i will probably finish off 94170014 and 88580014 and call it a day onto other mods..
UPDATE:
Please ensure your definitions are using big endian rather than little - this may cause a problem for the flash time.
94170014 is up - UNTESTED thou!
its not as simple as changing a few numbers in maps - this is altering the flow of the ECU code... which if you get wrong could be rather fatal!!!
time constraints on my end are stopping me from doing much more with this particular project... i will probably finish off 94170014 and 88580014 and call it a day
onto other mods..UPDATE:
Please ensure your definitions are using big endian rather than little - this may cause a problem for the flash time.
94170014 is up - UNTESTED thou!
Last edited by tephra; Aug 30, 2007 at 08:32 PM.
Aug 30, 2007, 09:28 PM
#174
There is no FAQ, self patching is a minefield which I would NOT advise people to get into..
its not as simple as changing a few numbers in maps - this is altering the flow of the ECU code... which if you get wrong could be rather fatal!!!
time constraints on my end are stopping me from doing much more with this particular project... i will probably finish off 94170014 and 88580014 and call it a day onto other mods..
UPDATE:
Please ensure your definitions are using big endian rather than little - this may cause a problem for the flash time.
94170014 is up - UNTESTED thou!
its not as simple as changing a few numbers in maps - this is altering the flow of the ECU code... which if you get wrong could be rather fatal!!!
time constraints on my end are stopping me from doing much more with this particular project... i will probably finish off 94170014 and 88580014 and call it a day
onto other mods..UPDATE:
Please ensure your definitions are using big endian rather than little - this may cause a problem for the flash time.
94170014 is up - UNTESTED thou!
