Anyone seen this issue before?
#1
Anyone seen this issue before?
I had my 2010 TL AWD with Tech with 14k miles for about 2 months and just a month ago it started doing this and it is very strange and now its getting frustrating since Acura cant figure out what is wrong... They have had my car for 2 weeks now
1- replaced battery on remote
2- replaced remote
3- replace 4 parts
and still doing the same thing and no one can figure out whats wrong
1- replaced battery on remote
2- replaced remote
3- replace 4 parts
and still doing the same thing and no one can figure out whats wrong
The following users liked this post:
LawnPro (07-04-2012)
#5
Drifting
That fob looks like it was dragged behind the car. Have they checked to make sure there is not a problem inside the fob unit itself? It contains relatively delicate electronics. From the fob's appearance, it seems entirely possible that the unit is damaged internally.
#6
Safety Car
#7
Correct... yes guys I know the key looks beatup but thats how it came from the original lease owner and it was not my doing... but the point is they did replace the key I have a brand new one programmed and still same issue..
yes I do have an Ipod plugged into the USB and the AUX is open... is there a reason why that could cause it? if so please elaborate.
Yes I have a brand new "Driver 2" key and same issue...
yes I do have an Ipod plugged into the USB and the AUX is open... is there a reason why that could cause it? if so please elaborate.
That fob looks like it was dragged behind the car. Have they checked to make sure there is not a problem inside the fob unit itself? It contains relatively delicate electronics. From the fob's appearance, it seems entirely possible that the unit is damaged internally.
Last edited by Steven Bell; 07-04-2012 at 09:13 PM. Reason: Merged Posts.
Trending Topics
#8
Unplug the iPod and the chargers and see if it helps.
Here's the exact text (it only mentinoed RL's but kind of seems similar to your issue)
MID Displays Keyless Remote Not in Vehicle, But It Is
Currently Applies To: ’05–10 RL
Has your client come in saying that he or she saw an
intermittent error message on the MID - Keyless
Remote Not in Vehicle - while sitting in the vehicle
with the keyless remote? This is not a case where
the client got out of the vehicle with the keyless
remote while the vehicle was running.
Before assuming there’s a problem with the keyless
access system, check if your client keeps a cell
phone charger or any other electronic device charger
plugged into either of the accessory power sockets or
the USB port. Also ask where your client typically
keeps the keyless remote while driving.
The vehicle is probably fine, and the problem could
be a faulty charger. When we say faulty charger, we
mean that the charger does not meet the FCC
requirements for electrical interference, even if the
device is being charged. The excess electrical
interference blocks the communication between the
vehicle and the keyless remote when the keyless
remote is stored close to the charger, like in the
center console or coin tray.
Troubleshooting is easy. Just unplug the charger or
USB device, and see if the problem goes away. If it
goes away, have the service consultant recommend
to your client that he or she either replace the
charger or stop storing the keyless remote in the
center console area to avoid the electronic
interference. (The owner’s manual also recommends
that you carry the remote with you and not leave it
lying around in the vehicle.)
Last edited by Steven Bell; 07-04-2012 at 09:14 PM. Reason: Merged Posts.
#9
Here's the exact text (it only mentinoed RL's but kind of seems similar to your issue)
MID Displays Keyless Remote Not in Vehicle, But It Is
Currently Applies To: ’05–10 RL
Has your client come in saying that he or she saw an
intermittent error message on the MID - Keyless
Remote Not in Vehicle - while sitting in the vehicle
with the keyless remote? This is not a case where
the client got out of the vehicle with the keyless
remote while the vehicle was running.
Before assuming there’s a problem with the keyless
access system, check if your client keeps a cell
phone charger or any other electronic device charger
plugged into either of the accessory power sockets or
the USB port. Also ask where your client typically
keeps the keyless remote while driving.
The vehicle is probably fine, and the problem could
be a faulty charger. When we say faulty charger, we
mean that the charger does not meet the FCC
requirements for electrical interference, even if the
device is being charged. The excess electrical
interference blocks the communication between the
vehicle and the keyless remote when the keyless
remote is stored close to the charger, like in the
center console or coin tray.
Troubleshooting is easy. Just unplug the charger or
USB device, and see if the problem goes away. If it
goes away, have the service consultant recommend
to your client that he or she either replace the
charger or stop storing the keyless remote in the
center console area to avoid the electronic
interference. (The owner’s manual also recommends
that you carry the remote with you and not leave it
lying around in the vehicle.)
MID Displays Keyless Remote Not in Vehicle, But It Is
Currently Applies To: ’05–10 RL
Has your client come in saying that he or she saw an
intermittent error message on the MID - Keyless
Remote Not in Vehicle - while sitting in the vehicle
with the keyless remote? This is not a case where
the client got out of the vehicle with the keyless
remote while the vehicle was running.
Before assuming there’s a problem with the keyless
access system, check if your client keeps a cell
phone charger or any other electronic device charger
plugged into either of the accessory power sockets or
the USB port. Also ask where your client typically
keeps the keyless remote while driving.
The vehicle is probably fine, and the problem could
be a faulty charger. When we say faulty charger, we
mean that the charger does not meet the FCC
requirements for electrical interference, even if the
device is being charged. The excess electrical
interference blocks the communication between the
vehicle and the keyless remote when the keyless
remote is stored close to the charger, like in the
center console or coin tray.
Troubleshooting is easy. Just unplug the charger or
USB device, and see if the problem goes away. If it
goes away, have the service consultant recommend
to your client that he or she either replace the
charger or stop storing the keyless remote in the
center console area to avoid the electronic
interference. (The owner’s manual also recommends
that you carry the remote with you and not leave it
lying around in the vehicle.)
At this point I am willing to try everything, thanks, Ill try this out but usually the keys are in my right pocket which is right next to the center console so it potentially could be the smoking gun... any other suggestions are welcome...
#10
6G TLX-S
It could be a bad Smart Unit, which controls all the keyless entry functions.
#11
Team Owner
iTrader: (2)
Join Date: Jan 2008
Location: Kansas City, MO (Overland Park, KS)
Posts: 36,545
Received 6,470 Likes
on
5,162 Posts
Guys, we have a Multi-Quote button in the lower right hand corner of each post. This allows you to respond to more than one person in a single reply.
Please give it a try....cheers.
Please give it a try....cheers.
#12
Intermediate
Join Date: Nov 2008
Location: St Louis, MO
Posts: 30
Likes: 0
Received 0 Likes
on
0 Posts
Mine does that, about 50-60% of the time. It either says "keyless remote not detected" or displays the low battery sign. I changed the battery and still gives me the message. Worst of all, I went to the Acura dealer and told them the problem, but all the service manager could say was "we didn't detect any problems with it". When I told them that it doesn't work most of the time all he said was that I should carry both key fobs and wait till it completely fails.
#13
Mine does that, about 50-60% of the time. It either says "keyless remote not detected" or displays the low battery sign. I changed the battery and still gives me the message. Worst of all, I went to the Acura dealer and told them the problem, but all the service manager could say was "we didn't detect any problems with it". When I told them that it doesn't work most of the time all he said was that I should carry both key fobs and wait till it completely fails.
#15
Intermediate
Join Date: Nov 2008
Location: St Louis, MO
Posts: 30
Likes: 0
Received 0 Likes
on
0 Posts
you're kidding? I don't think that's an acceptable answer, this is very frustrating to see Acura having this issue... I will keep my Loaner as long as I need to until they fix the problem (2012 MDX) , my rep said they have a case with Acura open and are spending about 2 hours a day and they cant figure out what the problem is... but at least they acknowledge the issue which is good.
#16
Suzuka Master
iTrader: (4)
I had a similar problem. The issue was the key slot. It still thought it was plugged in. I found a thread that basically said use your fingers, put them in the slot, and firmly pull the the thing outwards to simulate the key being removed. Don't worry, nothing to zap and crush your fingers, but you will feel, there is a 'tooth' on each side that clasps the key, you just have to firmly pull that.
Now that I think about it, maybe this isn't the same exact issue.
Now that I think about it, maybe this isn't the same exact issue.
#17
Three Wheelin'
Does the car do this everywhere you are located or just near your house? It could be interference from military etc. I think that is what the issue is. You are getting some type of outside interference. Try another location and see if you still have the issue.
#18
I had a similar problem. The issue was the key slot. It still thought it was plugged in. I found a thread that basically said use your fingers, put them in the slot, and firmly pull the the thing outwards to simulate the key being removed. Don't worry, nothing to zap and crush your fingers, but you will feel, there is a 'tooth' on each side that clasps the key, you just have to firmly pull that.
Now that I think about it, maybe this isn't the same exact issue.
Now that I think about it, maybe this isn't the same exact issue.
Thread
Thread Starter
Forum
Replies
Last Post
snorf
2G RDX (2013-2018)
429
11-04-2019 06:44 AM