Need help with a situation involving an E6k
Alright, a member on here purchased an E6k from me about 3 months ago and is claiming that the unit is defective. It came out of my FD, which ran fine when i took it apart. He is using it in an FC and is having issues.
He posted this video, which is supposed to show that the unit defective. Another memeber stated that he would have to mess with the map involving the RPM's in order to get it to work right. I know nothing about this stuff, so any help is appreciated. The Fd this ECU came out of had the trailing plugs deleted and ran off MSD coils, if that matters at all. Thanks, Austin http://www.youtube.com/watch?v=ONQmN73jDaQ[/ |
I believe the 7.07 was known to be glitchy. Perhaps he should load the 6.34 version instead?
|
i saw a few variations between the settings in both ecus, the differences between the bad and good ecus are:
the "bad" ecu is set with a trigger mode of constant which the good ecu is set as adaptive the "bad" ecu timing is locked at 5 degrees and tooth off is set at 3 which the good ecu is set with an offset of 11 and did he load his own maps into the "bad" ecu? |
Thanks guys, i appreciate it. If anyone else sees anything or has any ideas, please let me know.
Thanks, Austin |
I don't get it. What's he claiming is defective about it (besides his air temp sensor not being connected)? Who's the user? Bring him into the thread or point...
Wait a second... did he try updating the firmware on it? On occasion, it flips out and produces this symptom. You have to jump the empty block jumper pins with a screwdriver (or 4-block jumper pin) and turn ignition on and back off. That should reset it where you can load in a map. Happened on a customer's car that embarrassed me for about an hour once. :) B |
Originally Posted by beefhole
(Post 9777258)
I believe the 7.07 was known to be glitchy. Perhaps he should load the 6.34 version instead?
6.34 works just fine in combination with firmware 8.14. That's what needs to be used. B |
The user is Mixed 88TII, i sent him a link to this thread.
Thanks guys, Austin |
Originally Posted by beefhole
(Post 9777258)
I believe the 7.07 was known to be glitchy. Perhaps he should load the 6.34 version instead?
Originally Posted by xxtremes33
(Post 9777525)
i saw a few variations between the settings in both ecus, the differences between the bad and good ecus are:
the "bad" ecu is set with a trigger mode of constant which the good ecu is set as adaptive the "bad" ecu timing is locked at 5 degrees and tooth off is set at 3 which the good ecu is set with an offset of 11 and did he load his own maps into the "bad" ecu?
Originally Posted by BDC
(Post 9795127)
I don't get it. What's he claiming is defective about it (besides his air temp sensor not being connected)? Who's the user? Bring him into the thread or point...
Wait a second... did he try updating the firmware on it? On occasion, it flips out and produces this symptom. You have to jump the empty block jumper pins with a screwdriver (or 4-block jumper pin) and turn ignition on and back off. That should reset it where you can load in a map. Happened on a customer's car that embarrassed me for about an hour once. :) B
Originally Posted by BDC
(Post 9795129)
7.07 was garbage.
6.34 works just fine in combination with firmware 8.14. That's what needs to be used. B As of today, its been 21days since Both my old E6k V6.34 and Austin's E6K V7.07 have been sent to Haltech for repair. Was told its a minimum of 1month wait time and there could be a possibility that they cannot repair the unit's due to being so old. So im hoping that they are repairable and they will back to me sometime in march. |
All times are GMT -5. The time now is 11:38 AM. |
© 2024 MH Sub I, LLC dba Internet Brands