Workdawg
NARWHAL
The goal: Get a proximity key/smart key setup working in our cars, which don't have them now. Further to that point, the main goal is to have the car unlock as we approach, and lock as we leave. Personally, adding a push button start that only requires the smart key to be in the car (no key in the ignition) would be a step further, but not required for the initial solution.
I'm not sure who came up with it first, however it was at least partially inspired by this badass: http://www.geekmyride.org/wiki/index.php/Jon's_RX-8
Potential solutions:
First potential solution: Adapt this (Link) to use in a car.
Matt found this one but after much research, it appears that this will not work, at least not cheaply. It uses an RFID tag and reader to unlock the door when the tag is swiped across the reader. The limitation we are dealing with here is range. The best solution that could be found was about a 25cm (~10") range; and that's with a clear line of sight between the two parts. Since we'd need to have the module contained in the car, and the tag in our hand (preferably pocket), our range would be even less than that. This is not a feasible option at this time.
Second potential solution:
Hack up an OEM system to work with a car it wasn't designed for. This was my idea, but it's likely the most expensive and there are some questions that would need to be answered to determine it's feasibilty. The main question is how the ECU and stock prox/smart key module work together. If the keys are programmed to the ECU, then this would not work without also replacing the ECU. Since the 1st gen MS3 never came with a smart key, this would be impossible. However, if the keys are programmed into the entry module itself, then it may work. Depending on what signal the entry module sends to the ECU, it could potentially be a direct swap. This sounds quite unlikely though. If the signals are different, it may be possible to build an arduino circuit to intercept the signal from the entry module and send out another signal that the stock ECU will understand. To accomplish this, we'd have to analyze the signals that are being sent out by the stock keyless entry system and the new smart/prox entry system. If they are the same, it should be a direct swap. If they are different, an arduino should work. Feasibility, possible... but cost prohibitive.
Third potential solution:
Jay recalled that someone had already done what we were looking to do, with a Nike+ fob. LINK
This solution shows quite a bit of promise, and is fairly cheap (about $75 + cannibalizing a stock fob, which is another $100 or so). I won't outline the whole thing, since you can read (hopefully). Originally I thought there were some issues with this, but having read the comments on it further, it seems they were all addressed, just not outlined in the main article. The Nike+ fob only sends a signal when it detects movements, so it's not constantly unlocking your doors when you're not moving. Mazda ignores fab signals when the key is in the ignition. It is set up to autolock if it stops getting a signal from the fob.
Fourth potential solution:
There is a company out there who offers an aftermarket solution, maybe. LINK
Matt emailed them, since the product isn't officially released yet, and got a positive answer. It's supposed to work with all models of cars and only cost $169. Pretty sweet sounding, but lacking on details.
================
I think for now I'm going to do a little bit more thinking and researching about this, but I'll probably wait at least until option 4 is officially released to see how it all works.
I'm not sure who came up with it first, however it was at least partially inspired by this badass: http://www.geekmyride.org/wiki/index.php/Jon's_RX-8
Potential solutions:
First potential solution: Adapt this (Link) to use in a car.
Matt found this one but after much research, it appears that this will not work, at least not cheaply. It uses an RFID tag and reader to unlock the door when the tag is swiped across the reader. The limitation we are dealing with here is range. The best solution that could be found was about a 25cm (~10") range; and that's with a clear line of sight between the two parts. Since we'd need to have the module contained in the car, and the tag in our hand (preferably pocket), our range would be even less than that. This is not a feasible option at this time.
Second potential solution:
Hack up an OEM system to work with a car it wasn't designed for. This was my idea, but it's likely the most expensive and there are some questions that would need to be answered to determine it's feasibilty. The main question is how the ECU and stock prox/smart key module work together. If the keys are programmed to the ECU, then this would not work without also replacing the ECU. Since the 1st gen MS3 never came with a smart key, this would be impossible. However, if the keys are programmed into the entry module itself, then it may work. Depending on what signal the entry module sends to the ECU, it could potentially be a direct swap. This sounds quite unlikely though. If the signals are different, it may be possible to build an arduino circuit to intercept the signal from the entry module and send out another signal that the stock ECU will understand. To accomplish this, we'd have to analyze the signals that are being sent out by the stock keyless entry system and the new smart/prox entry system. If they are the same, it should be a direct swap. If they are different, an arduino should work. Feasibility, possible... but cost prohibitive.
Third potential solution:
Jay recalled that someone had already done what we were looking to do, with a Nike+ fob. LINK
This solution shows quite a bit of promise, and is fairly cheap (about $75 + cannibalizing a stock fob, which is another $100 or so). I won't outline the whole thing, since you can read (hopefully). Originally I thought there were some issues with this, but having read the comments on it further, it seems they were all addressed, just not outlined in the main article. The Nike+ fob only sends a signal when it detects movements, so it's not constantly unlocking your doors when you're not moving. Mazda ignores fab signals when the key is in the ignition. It is set up to autolock if it stops getting a signal from the fob.
Fourth potential solution:
There is a company out there who offers an aftermarket solution, maybe. LINK
Matt emailed them, since the product isn't officially released yet, and got a positive answer. It's supposed to work with all models of cars and only cost $169. Pretty sweet sounding, but lacking on details.
================
I think for now I'm going to do a little bit more thinking and researching about this, but I'll probably wait at least until option 4 is officially released to see how it all works.
Last edited:
