"Key not in range!" message. Remote won't unlock, lock or start car...

   #1  

quailallstar

Verified VCDS User
Verified
Joined
Aug 23, 2016
Messages
137
Reaction score
38
Location
Ormond Beach, FL
VCDS Serial number
C?ID=53119
Well, I've finally been plagued by the "Key not in range!" Kessy bug of issues facing countless other MK7 owners - across the globe.

Background info:

I replaced remote 1's battery two weeks ago and it's been woking perfectly since. Until that point, my Kessy hatch opening was a true hit or miss - but perfect once a new battery was put in. Now today all of a sudden I'm unable to lock/unlock or start my car via the same remote with a fresh battery. The only way to start the car is by using the emergency procedure (hold key up to the steering column).

Spare key doesn't work either and neither does the procedure outlined within the owners manual used to have the car re-learn its keys

Ran a VCDS scan and the only issue coming up is some fault related to Car-Net which I don't have active.

Code:
Address 75: Telematics (J949)       Labels: 5QE-035-285.clb
   Part No SW: 5QE 035 285 A    HW: 5QE 035 285 A
   Component: OCULowMQBUS   007 0568  
   Coding: 02730002C2863A01000002000000
   Shop #: WSC 12345 123 61029
   ASAM Dataset: EV_OCULowMQB 001006
   ROD: EV_OCULowMQB.rod
   VCID: 438F311FCA0C3A59B4-8016


1 Fault Found:
2566 - GPS Antenna 
          B1054 13 [009] - Open Circuit
          Confirmed - Tested Since Memory Clear
             Freeze Frame:
                    Fault Status: 00000001
                    Fault Priority: 4
                    Fault Frequency: 1
                    Reset counter: 173
                    Mileage: 18490 km
                    Date: 2017.04.01
                    Time: 19:15:05


Is there any way to reprogram the keys through VCDS? I avoid the dealer as much as possible.

Tips, tricks or advice would be greatly appreciated!
 
   #2  

Uwe

Benevolent Dictator
Staff member
Joined
Jan 29, 2014
Messages
34,577
Reaction score
24,625
Location
USA
VCDS Serial number
HC100001
Mind posting your Kessy data despite there being no fault codes?

I think it might be educational for us to look at some of the measuring values in there.

-Uwe-
 
   #3  

quailallstar

Verified VCDS User
Verified
Joined
Aug 23, 2016
Messages
137
Reaction score
38
Location
Ormond Beach, FL
VCDS Serial number
C?ID=53119
Mind posting your Kessy data despite there being no fault codes?

I think it might be educational for us to look at some of the measuring values in there.

-Uwe-

@Uwe

Here you go! Can you tell me if you see any coding that could be incorrectly coded? Should I attempt to have the keys relearned? http://wiki.ross-tech.com/wiki/index.php/Immobilizer_III_Key_Matching_(Kessy)

Additional vehicle info: Chassis Type: AU (5Q0) 2016 NAR Golf Sportwagen TSI - Build date 1/26/2016

Code:
Address 05: Acc/Start Auth. (J518)       Labels: 5Q0-959-435.clb
   Part No SW: 5Q0 959 435 A    HW: 5Q0 959 435 
   Component: VWKESSYMQB    021 0604  
   Revision: 00021000    Serial number: 0381142691
   Coding: 030C1C
   Shop #: WSC 01383 790 50316
   ASAM Dataset: EV_KessyHellaMQBAB 002011
   ROD: EV_KessyHellaMQBAB_002.rod
   VCID: 3A714CFBBDC67B91E7-806E

No fault code found.
 
Last edited:
   #4  

quailallstar

Verified VCDS User
Verified
Joined
Aug 23, 2016
Messages
137
Reaction score
38
Location
Ormond Beach, FL
VCDS Serial number
C?ID=53119
Fixed the issue!!!

For some odd reason, 09-Central Electronics byte 8/bit 0-1 was coded ROW and not North America. This was causing all keys to not be recognized as a result. Reverted back to NAR and all is well. Two cups of coffee helped for sure :thumbs:

qkgOSaX.png
 
Top