Questions & Answers

Is anyone using an EVO-ALL with the RFK912 kit succesfully ?

0 votes
I have two cars with the EVO-ALL and the RFK912 and they both stop responding to the remotes about a day after they're been configured. Reconfiguring gets it work again, but then they stop again. My other car with a RF942 works great wih the EVO-ONE. Do I need an EVO ONE for these ??
posté Jan 6, 2020 dans la catégorie FAQ par Ed Andre (380 points)

1 Réponse

0 votes
No, should be working fine with the EVO-ALL. (that's what i have anyway). What's the service number of the evo?
répondu Jan 6, 2020 par Robert T (302,310 points)

001A06655788 and 001A7057633.

Looking good on that end. 

 

When they stop working, 

  • Do the remotes confirm anything even though nothing happens on the car? Exemple, send Lock - remote confirms Lock - but nothing happens on car. 
  • Are any lights on, on the EVO-ALL when it fails?
  • Does 3x lock start still work when the 912 stops working?
- The remotes always confirm. When they work and when they don't. So yes, I always get the green confirmation LED

- I don't see any lights at all. It stays dark.

- Yes it does and it works every time.

- The remotes always confirm. When they work and when they don't. So yes, I always get the green confirmation LED

Good, they should be. Remotes actually pair to the antenna. The antenna is what pairs to the module. 

 

I think i asked on another of your posts somewhere, but do you have the RFA2A on both those installs?

Yes, yes I do!
So.. no other ideas........?
not really aside digging from deeper. I'm also assuming there's no other rf device installed link a carlink (telematics device)

 

Reprogram only 1 remote to each car (antenna) 4 times. Make sure to not program the same remote remotes in both cars! (do not program 1 remote on both antennas)

 

test it out a few days.
Well yesterday I re-"married" the RF kit to the EVO-ALL by unplugging the RF kit connector from the unit, holding down the programming button, waiting for the blue and red LEDs, pushing the button again until the blue and red LEDs came back and turning the ignition on.. then off.   I noticed before I did all this, any button presses on the remote would get acknowledged by the antenna LED, but not by the EVO-ALL's blue led. After repairing it, the EVO would also acknowledge the button presses.

 

Anyway, for now it's working okay and it works today as well.  I'm just wondering why this keeps happening. Very weird.
what's important to understand is that during the pairing process, two things are happening.

1. the remotes pair to the antenna

2. the antenna pairs to the evo

 

As long as the remotes pair to the antenna, the remotes will always confirm that the antenna received a command.
The antenna not pairing to the evo correctly though, would explain afterwards why sending commands, never does naything on the car.  When pairing, the red and blue on the evo blink once to confirm.
Right.. right. I understand that process. What I think is happening though, is that the pairing of the antenna to the EVO gets lost after some time. And I just don't understand why that would happen, once paired and working.
Once paired, it's paired. Only difference i am seeing is that manipulating the connectors/wiring when reprogramming them makes everything start to work again.
Well it worked fine last night and half the day today. Unfortunately I wasted way too much time on this. It just doesnt seem like these RF kits are ready for the EVO-ALL, or ready for the EVO-ALL with THIS firmware.  

I unplugged both kits tonight and I'm returning them tomorrow.
I plugged in a RFALL642W kit a couple days ago and it's been working great all this time. I still think you guys have some firmware issues with that kit, on the evo all, with that particular firmware.
Same problem.  RFK912 worked with my EVO-All for about 36 hours, then the EVO-All doesn't acknowledge the RFK912 any more.  The antenna is still acknowledging the remote as if the command was received and accepted, but the EVO-All won't lock the doors or start the car anymore.  OEM remote 3x lock still starts the car...

Latest firmware in EVO-All and Flashupdater (as of 1/15/2020) is installed.  

Car: Infiniti Q50 2015

NIST4 T-Harnesss

EVO-All

RFK912

Patrick, please check the following. 

 

  1. The antenna can be updated. Plug it in the flash link and see if an update is available for your antenna. Latest version i believe is 1.04. 
  2. When it does not work, are there any lights ON on the EVO?
  3. What is the 12 digit service number of the 

 

If possible, please send an email to support@fortin.ca. 

By the way... happy to report that the RFALL642W kit works great to this day. I definitely don't think it's the wiring. Too odd for this to happen on BOTH of my Infiniti's in the same manner.

So I checked the ANT900 firmware: it was at 1[.04] Beta.  I re-flashed it to 1[.03] Beta and then back to 1[.04] to see if that helped.  Re-paired both remotes, everything worked for around 36 hours then same thing happened:  Remotes get acknowledgment signal back as if command worked, but car does not start, lock, or unlock.  OEM keyfob lock lock lock still starts the car...  Rolled back the firmware on ANT900 to 1[.03] Beta, repaired both remotes, then same result... everything worked for ~36 hours, remotes get good confirmation signal, but car does not respond.  OEM keyfob still starts the car...

ANT900 Hardware V. 1.0    Firmware 1[.03] Beta currently, will move it back to 1[.04] Beta

EVO-ALL. Date: 10/2019.  SN: 001A07 077034

Seems like:

the EVO-ALL is 'forgetting' or rolling code is getting out of sync with ANT900

or ANT900 is has a rolling code bug...

Now in the current state- (ANT900 not talking to EVO-ALL, but EVO-ALL working with OEM remote)

ANT900 blue light flashes every 5 seconds or so...

When I use RF912 remote to start or lock doors, the remotes beep happily and show the green light. ANT900 blinks a green light, but EVO-ALL does not flash any LEDs and of course the car does not start or lock or flash turn signal lights.
Problem is between evo and antenna, not antenna and remote.

Roll back the firmware on the evo-all, 72.40 . Reset and reprogramme everything.
Issue fixed at firmware 1.05. Plug ANT900 antenna into flash-link and update to 1.05.
Thanks Rob-  Both solutions worked.  I first rolled back the EVO-ALL to 72.40 with ANT900 at 1.04.  That worked well for more than a week which is when I saw your next message.  Then.I reflashed the EVO-ALL to 72.43 and the ANT900 to 1.05.  It has been working as it should for more than a week.  Thanks.  TIP:  When I plugged in my ANT900 with 1.04 firmware the app on the PC thought the ANT900 was already at 1.05 - just a bug.  I flashed it to 1.05 and one part of the app thought it was at 1.05 and another message said it was at 1.04 which was confusing.  Like I said, it has been working more than a week, so thanks for getting that fixed!

So my final steps were (2015 Infiniti Q50):

Flashed EVO-ALL to 72.43

Flashed the ANT900 to 1.05 and reinstalled it

Reset EVO-ALL using the red LED method.

Reprogrammed EVO-ALL to the car using the blue LED method.

Ran the dcryptor routine on the EVO-ALL using the Fortin app.

Re-paired the both of the  Fortin RFK912 fobs to the ANT900 using the red / blue LED method on the EVO-ALL

Remote start, lock, unlock, and remote start disable work on the RFK912.  3x lock on the OEM fob remote starts the car.
Thanks for the update!

The ANT900 remote all share the same service number for the flash link to recognize and allow flashing. What it shows in the middle of the screen is what was "last flashed" for a ANT900 antenna, somewhere... The firmware seen on the bottom of the screen is what is actually loaded in it.
...