AEM keeps eating my cam sensor
#1
AEM keeps eating my cam sensor
I'm on my 4th cam sensor this year. Problem happens around 500 miles and all the sudden it backfire's and studders at high RPM, high boost pulls. Put a new cam sensor in and the problem goes away. Luckily I haven't lost a motor yet like a few others. I know David Bushur also had this issue and ended up switching ECU platforms-
https://www.evolutionm.net/forums/ev...-bad-bish.html
To explain what happens when the cam sensor fails-
When it starts to go bad you get an incorrect RPM reading. You will get spikes in the RPM on the log. In my case its at the upper RPM. The car is logging 8k RPM and in a fraction of a second, AEM thinks its seeing 10k RPM and freaks out.
I am running a CF heat shield with the silver reflective tape. I also tried to wrap the sensor with some protective heat wrap while using the CF shield but the sensor eventually failed.
I believe AEM is somehow destroying the sensor, just not sure how. I'm using series 1 BTW.
Any ideas?
https://www.evolutionm.net/forums/ev...-bad-bish.html
To explain what happens when the cam sensor fails-
When it starts to go bad you get an incorrect RPM reading. You will get spikes in the RPM on the log. In my case its at the upper RPM. The car is logging 8k RPM and in a fraction of a second, AEM thinks its seeing 10k RPM and freaks out.
I am running a CF heat shield with the silver reflective tape. I also tried to wrap the sensor with some protective heat wrap while using the CF shield but the sensor eventually failed.
I believe AEM is somehow destroying the sensor, just not sure how. I'm using series 1 BTW.
Any ideas?
#2
Evolved Member
iTrader: (9)
I'm on my 4th cam sensor this year. Problem happens around 500 miles and all the sudden it backfire's and studders at high RPM, high boost pulls. Put a new cam sensor in and the problem goes away. Luckily I haven't lost a motor yet like a few others. I know David Bushur also had this issue and ended up switching ECU platforms-
https://www.evolutionm.net/forums/ev...-bad-bish.html
To explain what happens when the cam sensor fails-
When it starts to go bad you get an incorrect RPM reading. You will get spikes in the RPM on the log. In my case its at the upper RPM. The car is logging 8k RPM and in a fraction of a second, AEM thinks its seeing 10k RPM and freaks out.
I am running a CF heat shield with the silver reflective tape. I also tried to wrap the sensor with some protective heat wrap while using the CF shield but the sensor eventually failed.
I believe AEM is somehow destroying the sensor, just not sure how. I'm using series 1 BTW.
Any ideas?
https://www.evolutionm.net/forums/ev...-bad-bish.html
To explain what happens when the cam sensor fails-
When it starts to go bad you get an incorrect RPM reading. You will get spikes in the RPM on the log. In my case its at the upper RPM. The car is logging 8k RPM and in a fraction of a second, AEM thinks its seeing 10k RPM and freaks out.
I am running a CF heat shield with the silver reflective tape. I also tried to wrap the sensor with some protective heat wrap while using the CF shield but the sensor eventually failed.
I believe AEM is somehow destroying the sensor, just not sure how. I'm using series 1 BTW.
Any ideas?
** Note ** Buschur redesigned them to be stronger but mine eventually started to crack again so I got a carbon fiber one. I think that’s because I have Torque Solutions engine mounts in my car and it’s basically a "race" setup and at that time was my daily driver. The vibrations on the aluminum, it eventually had to give. Two of my friends have the same cracking issue so it’s the nature of the beast and the material used.
Anyway moving along I then switched to a series 2 box after they came out and had the problem again but NOT on the series 1 box. It turned out that series 2 appeared to be more sensitive to the cam sensor signal so I again had to replace the sensor and all was well. Fast forward a few months and another cam sensor issue, talk about getting irritated at this point... So I tried changing the sensor again and thought I would be good but the hype of short lived, the problem came back.
So after driving the car easy (it was my daily driver on most occasions) for a couple weeks I finally looked into it more and found that the problem appears to be my wire harness for the cam sensor. If the problem comes I can unplug push on the wires and plug it back in and the car is 100% solid again.
So my point is I don’t see it being AEM destroying your sensors and I suggest checking your wiring. I have an AMS turbo kit and about 98,xxx miles on my car and live in Florida where its hot. My theory is all the heat cycles the plastic, rubber, and wires in general have deteriorated over time being so close to the aftermarket manifold. The car is down now but I am going to wire in a new pigtail once I bring it back to life.
#3
Interesting...
The only reason I feel AEM is to blame is you never hear of factory ECU having issues with the cam sensor (4 sensors 5 months is excessive). I think you would have more people complaining about this issue. I will definitely check my pigtail for any issues.
I was buying replacement sensors at the local parts store. I was told to run ONLY a Mits OEM cam sensor so that was my 4th and it still had RPM spike issues after 300 miles.
The only reason I feel AEM is to blame is you never hear of factory ECU having issues with the cam sensor (4 sensors 5 months is excessive). I think you would have more people complaining about this issue. I will definitely check my pigtail for any issues.
I was buying replacement sensors at the local parts store. I was told to run ONLY a Mits OEM cam sensor so that was my 4th and it still had RPM spike issues after 300 miles.
#4
Evolved Member
iTrader: (9)
Interesting...
The only reason I feel AEM is to blame is you never hear of factory ECU having issues with the cam sensor (4 sensors 5 months is excessive). I think you would have more people complaining about this issue. I will definitely check my pigtail for any issues.
I was buying replacement sensors at the local parts store. I was told to run ONLY a Mits OEM cam sensor so that was my 4th and it still had RPM spike issues after 300 miles.
The only reason I feel AEM is to blame is you never hear of factory ECU having issues with the cam sensor (4 sensors 5 months is excessive). I think you would have more people complaining about this issue. I will definitely check my pigtail for any issues.
I was buying replacement sensors at the local parts store. I was told to run ONLY a Mits OEM cam sensor so that was my 4th and it still had RPM spike issues after 300 miles.
#5
Evolved Member
iTrader: (25)
Join Date: Sep 2006
Location: maryland/west chester pa
Posts: 1,129
Likes: 0
Received 2 Likes
on
2 Posts
i am on my 3rd sensor in 180 miles i am also running v1 the car ran fine wed put about 20 miles on the car parked it then go to drive today and its back the weird thing is i put my sensors in a buddys car (stock ecu ) and his car runs fine but put it in mine and misfire i dont have a solution really annoying cause i cant drive the car far.
#6
i am on my 3rd sensor in 180 miles i am also running v1 the car ran fine wed put about 20 miles on the car parked it then go to drive today and its back the weird thing is i put my sensors in a buddys car (stock ecu ) and his car runs fine but put it in mine and misfire i dont have a solution really annoying cause i cant drive the car far.
There also an option like this the Honda folks are using with AEM:
#7
Evolved Member
iTrader: (11)
Join Date: Oct 2007
Location: Connecticut / Massachusetts U.S.A
Posts: 1,430
Likes: 0
Received 1 Like
on
1 Post
I'd shoot Emery@STM a private message with the link to this thread.
He uses AEM more than any other shop that I know of. If anyone has had an AEM EMS problem and fixed it, it's probably Emery.
-Bink
He uses AEM more than any other shop that I know of. If anyone has had an AEM EMS problem and fixed it, it's probably Emery.
-Bink
Trending Topics
#9
Former Sponsor
iTrader: (79)
I have no idea why its happening. Actually, I just lost the first one this year two weekends ago racing. Still ran a 9.0@162 though. lol. If you do not want to loose an engine I suggest not advancing timing upon start up. If the ECU looses Sync it will think the car is restarting and advance the timing once it re-syncs.
It may even be happening to the Stock ECU cars as well but May not be as pronounced as they do not have as many high hp/reving cars running on them.
-Em
It may even be happening to the Stock ECU cars as well but May not be as pronounced as they do not have as many high hp/reving cars running on them.
-Em
#10
I have no idea why its happening. Actually, I just lost the first one this year two weekends ago racing. Still ran a 9.0@162 though. lol. If you do not want to loose an engine I suggest not advancing timing upon start up. If the ECU looses Sync it will think the car is restarting and advance the timing once it re-syncs.
It may even be happening to the Stock ECU cars as well but May not be as pronounced as they do not have as many high hp/reving cars running on them.
-Em
It may even be happening to the Stock ECU cars as well but May not be as pronounced as they do not have as many high hp/reving cars running on them.
-Em
Speaking of sensors, have you had a chance to play around with a 12 tooth crank trigger with AEM? I was thinking of going to this this winter.
http://www.triggerdisc.com
#13
Evolved Member
iTrader: (25)
Join Date: Sep 2006
Location: maryland/west chester pa
Posts: 1,129
Likes: 0
Received 2 Likes
on
2 Posts
no you still have to run it but from what i read in that buschur thread there is a way to turn it of after the car has been started in aem nothing in that thread went into detail so i dont kno more then that i cant believe there is not a fix for this.
#14
Evolved Member
iTrader: (25)
Join Date: Sep 2006
Location: maryland/west chester pa
Posts: 1,129
Likes: 0
Received 2 Likes
on
2 Posts
update itzwolf was on the money i suggest everbody check there wiring to there cps sensor i am not sure what wire out of the 3 was not making good contact but all is well now.