One fob starts the vehicle, the other doesn't Mazda 3 2015 PTS

Question

I recently completed an install on a 2015 Mazda 3 PTS using the EVO-MAZT1 stand alone installation.  Only one of the key fobs starts the vehicle using the 3x lock procedure.  The other key fob only makes the lights blink.  It doesn't turn on the remote starter at all.  Looking to see what's going on.  Any help is appreciated.

Answer 1

When pressing lock or unlock on the 2nd fob, does the blue LED flash on the EVO ?

Does the 2 fobs look exactly the same physically?

Comments

I'm at work right now, so I won't be able to answer your first question for quite some time.  As for the second one, yes the FOBs look exactly the same and they both work for my car.  Interestingly enough, I also installed the same Fortin unit into a 2014 Mazda CX-5 and am having the same exact problem.

If the FOBs are exactly the same, what do you think the possible problems would be so I can run troubleshooting solutions when I get some time?

---

This will typically happen when a key was added to the vehicle after the initial pdi. A solution will be available when a local dealer has a vehicle with the same symptoms. There is no ETA on when this would be.

 

This might all have to do on HOW that second key was actually programmed into the vehicle. We are unsure until we see the issue first hand.

 

Checking the BLUE LED will tell you if the lock-unlock commands are being monitored. It's possible that the fob that doesnt work will not be monitored. It may be generating different can codes or simply no can codes (doubtful).

---

Can you please define PDI?  I'm not sure what that acronym is.  If this is the case it looks like I'm only going to be using that one remote until Fortin solves this problem and updates it.  I'm guessing I'd have to flash the module should something develop later.

As for programming, I followed the instruction set that was given for both vehicles.  Would this have anything to do with the fact that when you do the CAN programming you only use one remote?  Even though it's not specified in the instructions, did I have to do CAN programming for both remotes?  I know that when I use the secondary FOB on the Mazda three and do 3X lock, the lights flicker like something is going to happen, but the remote start never actually engages.

What happens if I decide to add an RF Extender kit out of curiosity.  Do both the RF kit remotes work to remote start since it's actually programmed to the supplied antenna or does it pair a remote to a FOB.  For reference, I was considering adding the Fortin 2-way RF extender to both vehicles later on down the line.

---

PDI = pre delivery inspection.

If you added an RF kit both would work without any issues.

---

And the CAN programming procedure?  It lists in both instructions sets to only do it once.  Does it indeed need to be done for both remotes separately?

---

You would not do any programming of the module itself.

You would only program the remotes which is completly seperate. Here is the link to our RF compatibility and programming http://fortin.ca/en/technology/rf_kits.html

---

Oops, I meant for the original product, sorry.

Allow me to clarify.  In the instructions for OEM Fob programming for the remote start, when it comes to the CAN programming procedure, it only has you use one of the OEM Fobs but has no mention of programming separately for the other OEM Fob.  Do I indeed have to do the CAN programming procedure for the second OEM fob or is only one needed like it's implied in the instructions?  Might this be the cause of the other OEM Fob not working?

---

No this would not be the cause. I would not suggest trying to do this. It would not matter which remote was used to program can as it has nothing to do with the remote itself it learns the can bus of the vehicle itself....not the remote.

---

It just clicked with me that the key issue is from the first fact stated earlier.  Both of these cars had there second keys added at a later date.  How will I know when this issue will be resolved by Fortin?  Is there a newsletter or notification system that I can take advantage of?

---

I was actually speaking with our engineering department yesterday and it seems as though it is an issue with how the keys are programmed to the vehicle at the dealer.

 

We detect both the MASTER keys for the vehicle. So if one works and one does not this would mean that the key that does not work was not programmed to the vehicle as a master key but as a companion or valet key.

 

Also looking at some information I was provided by ALL Data, their is different ways to program these keys to the car. So chances are the key that does not work was not programmed as a master key and this is why the module cannot recognize one of the 2 keys.

---

I'm guessing that this is probably the issue.  From what was stated earlier, it looks like Fortin is working on the issue, but there is no timeframe for an update around it.

What do I need to do on my end to monitor this?  Will there be an update at some point in time addresssing this issue?  Will someone reply to this thread when it happens or will there be some type of patch log that is put out?

---

The fix would be to go to the dealer and have all keys earsed and then re program BOTH keys as MASTER keys to the vehicle.

---

Ehhh, that'll cost a lot of money so I guess I'll pass on that option (roughly 120 per car). Looks like it will be just one fob per car unless I add an RF kit.  Thanks for your help.  I'll be on the lookout to see if Fortin ever adds the ability to program valet key fobs.