Hello Fortin Technical Support,
I am installing an EVO-ONE with TB-X and R-LINK2 on a Mazda 3 Hatchback 2025 2.5 Turbo (Push-to-Start).
Current firmware:
- EVO-ONE: 94.07x (latest available)
- TB-X: 2.02 (latest available)
Installation status:
- BCM connections completed according to the guide.
- OBD connections completed according to the guide.
- Passenger side connector connections completed according to the guide.
- TB-X connected.
- EVO-ONE programmed successfully.
- TB-X updated successfully.
- Key learning procedure completed successfully using the R-LINK2 and the OEM key with the battery removed, following the installation guide.
Symptoms:
- When I press LOCK-LOCK-LOCK from outside the vehicle, the EVO-ONE responds.
- Exterior lights turn on.
- The instrument cluster wakes up and the gauges move.
- The message “Key Not Detected” appears on the dashboard.
- The engine does not crank/start.
- After a few seconds, the OEM alarm is triggered.
Additional information:
- If I am sitting inside the vehicle with the OEM key present, LOCK-LOCK-LOCK will start the vehicle successfully.
- If I am outside the vehicle, remote start always fails with the “Key Not Detected” message.
- This suggests that the vehicle is recognizing the physical key but the bypass function is not being accepted during remote start.
Could you please advise:
- Is there any known issue with Mazda 3 2025 Push-to-Start vehicles and firmware 94.07x / TB-X 2.02?
- Is an additional DCRYPTOR or TB-X programming step required?
- Should OEM Remote Control (Lock-Lock-Lock) work on this vehicle without an RF kit?
- Is there a diagnostic procedure to verify that the TB-X is successfully transmitting the virtual key during remote start?
Thank you for your assistance.