TSL (TSL-1 and TSL-2) Troubleshooting GuideUpdated a year ago
Tom’s Key TSL (TSL-1 and TSL-2) Programmer Troubleshooting Guide
Updated: June 2023
Overview
The following is an informational guide on our TSL products and how to troubleshoot them in the event that troubleshooting does not go according to the manual. This will include both TSL-1 and TSL-2 troubleshooting broken down into two different sections.
Customer’s should only review the following document after making sure the battery on any item(s) used for programming are fully charged, part numbers and compatibility of items used for programming match, the owner of the vehicle is programming with a master key and not a valet key, and no clear damage is found upon the product. Information is subject to change in light of new developments or tools.
Section 1: TSL-1
Part 1: Key Programming Issues
The TSL-1 did not beep after plugging it into the OBD2 port
OBD2 port may not be functioning properly - Check if there is electricity coming from your OBD2 port. This would be a good time to use any other OBD2 port devices to test this.
If the Check Engine light does not illuminate, you can be sure that you have a fuse issue. It is most likely the case that your fuse is blown and must be replaced. Replacing the fuse would fix the issue.
The programmer could be defective - If the above is checked and we simply get no reaction from the device it is very likely that we are experiencing a faulty device and a replacement would need to be created by a Tom’s Key agent. Reach out at [email protected] and we’ll get you taken care of.
TSL-1 only beeps once after plugging into the OBD2 (No further beeps)
Check for the following -
No steps were missed
All doors, trunk, and hood were properly closed
Existing key was not running the engine but simply in the “on” position
The 15 second time limit to plug in the programmer was NOT exceeded
If you believe any of the steps above were improperly done, refresh the vehicle’s programming mode. Unplug the programmer, start the vehicle and leave the vehicle running for 30 seconds, open and shut the doors, then lastly reintroduce the device as found in your directions.
Continuous failure - If all steps above are properly followed and reattempted with no result at this point there is suspicion to believe that the programmer is faulty. From here we may recommend attempting a TSL-2 as the reason for failure can be something faulty with the programmer or the actual programming into your vehicle. Please reach out to [email protected] where we’ll assist you in continuing to diagnose and provide the best solution for a replacement.
The security light won’t turn solid (Step 15 of TSL-1 key programming)
The most likely possibility for this issue has to do with compatibility and could be any of the following reasons:
Not programming with a Master Key
The vehicle is not compatible with the TSL-1
Vehicle’s using G chip (2009 - 2016 Chip GQ429T)
Tundra’s using G chip Transponder key
In any of the following situations a replacement for a TSL-2 will be needed.
TSL-1 makes a continuous nonstop beeping sound (Step 16 of TSL-1 Key Programming)
In some vehicles this does tend to be the unfortunate case. Know that this is normal however, and programming should proceed without opening the doors or doing anything to try to address the beeping until programming is fully completed.
The security light still blinks after 90 seconds with new key in the ignition (Step 17 of TSL-1 key programming)
In this instance the security light will be a dead giveaway of what the issue is relative to its flashing code.
Code Types:
Every 2 Seconds Flashing Code - If the light blinks every 2 second then the key can be operating normally and could be properly paired with your vehicle. To test this remove the programmer, open and shut your doors, and attempt to turn on your vehicle.
If this fails and you find that the light is still blinking after reinserting the key into the ignition then programming has failed and you will need to reattempt.
2-1 Code - A code that blinks twice followed by 1 blink means “Programming failure.”
Programming failure can occur due to improperly following directions of programming, key compatibility issues, issues with the vehicle’s computer, issues with the connectivity of all instruments included, or a faulty key chip.
If all these items have been checked and programming has been reattempted at least 3 times, and each time proper reset has been done (Unplugging all items, turning on vehicle to run for 30 seconds, open and close the doors, programmer retry) then a key replacement and/ or programmer replacement may be needed.
2-2 Code - A code that blinks twice, followed by two more blinks means “Key Already Programmed.”
If you find this to be the case, unplug all items, open and close the vehicle’s doors, then follow to turn the ignition to “run”. Key should be fully functional. If this is not the case please reach out to one of our agents.
2-3 Code - A code that blinks twice followed by three more blinks means “Maximum Amount of Keys are Programmed to the Vehicle.”
At this point if you have a TSL-1 you will need to contact our customer support as you will need a TSL-2 which is capable of erasing keys on your vehicle’s memory of keys. A support agent will accommodate a replacement at little to no cost.
Section 1: TSL-1
Part 2: Remote Programming Issues
No Long Beep (Step 14 and/or Step 15 of Remote Programming)
This is a clear indication that the TSL-1 and your vehicle’s ECU are not communicating properly. This can be an issue with the vehicle or the programmer and the best solution would be a replacement to a TSL-2, as the issue can be due to faulty parts but can also be that it needs upgraded compatibility that the TSL-2 can offer. Attempting to program with a TSL-2 will make this clear.
TSL-1 Holds a Continuous Beep After Pressing Buttons on Remote (Step 16 of Remote Programming)
The following are reasons for the TSL-1 to Hold a Continuous Beep During Step 16 of Remote Programming:
Door Locks Did Not Cycle (No Success Programming Indicator) - Some Toyotas will not cycle the locks which will cause continuous beeping. To best check if the remote programming was successful proceed to remove the programmer and test the programming by pressing the remote buttons. You should find success, if this is not the case attempt reprogramming while considering all the options below as possibilities that may need testing.
Weak or Dead Remote Batteries - Weak of dead batteries can lead to continuous beeping and in some cases you’ll find that programming has failed due to this. It is important to check that the batteries are healthy or you will unlikely be able to complete programming.
Remote Not Compatible with the Vehicle - If you continue finding programming failure for your remote, it is important to double check that the compatibility is correct. Check any part numbers, circuit board numbers, FCCID, or key markings to make sure that compatibility is correct as this will be a dead stop in programming in not correct.
Faulty Remote - If batteries, reattempts, and compatibility checks have been done we cannot rule out a faulty remote. In this case you would need to contact our support agents. They will double check these parameters with you then proceed with replacement or refund options.
To speed things along please confirm with an agent that you have reviewed this document and have done the basic checks of multiple attempts, battery replacement, and have checked and have 100% assured compatibility.
All seemed to go well with the TSL-1 programming yet the remote still won’t work
In this instance there can be a few reasons as to why your remote is not functioning:
Key was left in the ignition while testing remote buttons
Doors are open while testing remote buttons
Incorrectly processed step(s) during programming
Weak or dead batteries
Faulty remote
Section 2: TSL-2
Part 1: Basic Issues with Programmer and Phone
TSL-2 Lights not powering on after being connected to OBD2
The following are usual causes for this instance to occur:
OBD2 of vehicle is not functioning properly
Items are not properly connected
Defective programmer
TSL-2 is not bluetooth paired to provided phone (Red Sticker)
If your rental TSL-2 (Red Sticker) and Tom’s Key provided programming phone are not paired and the bluetooth sectioned light appears red, enter the X100T programming app within the phone and click “immobilization.” The red light on your TSL-2 should now turn blue.
If failure occurs after many attempts contact Tom’s Key support so that we may provide a replacement.
Note: as an auxiliary option the X100T app can be also attempted to be uploaded on a customer’s phone from the app store. This would provide an immediate resolution in some instances.
TSL-2 is not bluetooth paired to provided phone (Blue Sticker)
If your rental TSL-2 (Blue Sticker) and Tom’s Key provided programming phone are not paired enter the “Make My Key” app, once the app fires up a connection should be made.
If normal pairing fails after trying to open the “Make My Key” app a few times, proceed to open the app, hit the top left corner drop down menu found on the screen, click “settings”, click “bluetooth settings,” you should then see a “TSL2A” option to click to pair. Once you see a check on this section the TSL-2 programmer and phone will be paired.
If failure occurs after a few attempts contact Tom’s Key support so that we may provide a replacement.
Programming app for TSL-2 is not within the provided phone
In the rare event that your Tom’s Key provided programming phone does not have the programming app please contact our support team so that we may provide a replacement.
What to do if “license exception” is prompted on the TSL-2 app
Enter “activation” on the app and enter the TSL-2’s number located on the body of the TSL-2. It is important to note that you must be connected to wifi as this activation does require a connection to the internet. With this activated you should be able to proceed.
What to do if options on the phone look unusual or behave oddly
If you encounter any odd behavior with phone settings or the programming phone itself, please restart the phone as this should correct any issues. If you find that this does not work after a few attempts, please reach out to one of our Tom Key agents so that we may provide a replacement.
Section 2: TSL-2
Part 2: Programming failure issues
TSL-2 “failed to communicate” during traditional turn key programming
There are a few reasons one can encounter a “failed communication” error for traditional turnkey transponder keys:
The ignition was not turned to the “On” position - The vehicle should not be running, simply 2 clicks into the “On” position. This allows for the programmer to properly communicate with the vehicle. If this is not done properly then the “failed to communicate” prompt will activate
The incorrect “Type” was clicked during the immobilizer prompt - The correct “Type” must be chosen which corresponds with the master key:
Non chip key - If you are experiencing a “failed to communicate” and you find no markings on your original key, you may have a nonchip (non transponder) vehicle which does not need pairing. The key should work simply by having it cut and turning the ignition switch.
It is important to remember however that if your key has a remote portion, you will need to program this using the programmer.
Faulty Programmer - A faulty programmer can never be ruled out. On some occasions this can be because the programmer needs to be updated in its firmware. If this is the case a replacement would be needed.
TSL-2 “failed to communicate” during remote programming
There are a few reasons one can encounter a “failed communication” error for remotes:
The ignition was not turned to the “On” position - The vehicle should not be running, simply 2 clicks into the “On” position. This allows for the programmer to properly communicate with the vehicle. If this is not done properly then the “failed to communicate” prompt will activate
Vehicle may have an aftermarket alarm system (Non Manufactured) - The vehicle can have an aftermarket alarm system not manufactured by the manufacturer. In this case programming a remote via our solutions would not work out. In order to confirm this customer should review any vehicle manuals and/or review manufacturer’s information via vin online.
Malfunctioning Remote - If the above are ruled out then a faulty remote is important to consider and would require a replacement via our support team.
TSL-2 Fail to Identify Error for (Blue Sticker TSL-2)
Failed to Identify Error (Blue Sticker) - Vehicle was not on “On” mode.
Turn Key Ignition Vehicles - In turnkey vehicle’s “On” mode will be two clicks forward without revving the ignition or pressing the brakes.
Push to Start Ignition Vehicles - In a vehicle with “Push to Start” ignition the on position is set by pressing the on button twice without pressing the vehicle brakes.
TSL-2 Operation Failed Prompt for (Smartkey/fob)
This is the failure prompt found when placing the smartkey on the ignition button of your vehicle. When this prompt appears the following should be checked:
Move at a quick but even pace - This procedure is time sensitive and will require you to complete this step at a time sensitive pace. This is because the programming window expires and your vehicle’s programming computer may timeout, which would cause you to start over.
Vehicle Must be Set to “On” - The vehicle not being set to the “On” position can cause an “Operation Failure” prompt. To set your push to start vehicle to “On,” press the “Start” button twice without putting your foot on the brake and running the engine. You will need to start the programming procedure over after doing so.
Vehicle didn't beep - The new fob was not recognized. Check the fob's battery and vehicle compatibility (part number, circuit board number, FCCID). Start the engine to refresh the process and start programming over once this is confirmed.
If nothing works, the new key could be defective and would need a replacement.
TSL-2 Operation Failed Prompt for (Turnkey vehicles)
This failure prompt is found when a turnkey is placed into the ignition of your vehicle. When this prompt appears the following should be checked:
Move at a quick but even pace - This procedure is time sensitive and will require you to complete this step at a time sensitive pace. This is because the programming window expires and your vehicle’s programming computer may timeout, which would cause you to start over.
Review Blinking Pattern - The blinking patterns of the security light gives you insight on what has transpired. If you encounter a 2-1 blinking pattern this means that programming has failed. If you have reattempted programming a few times and continue to encounter this blinking pattern it can be that your key’s chip is faulty or not properly compatible with your vehicle.
Contact a Tom’s Key support agent to help you further clarify and double check your compatibility in order to proceed forward.
TSL-2 “Programming Success” prompt but smartkey doesn’t function
The following are all reasons why you would encounter this issue:
Fob’s battery are weak/ dead - It is the most common issue we encounter at Tom’s Key. A simple battery change may immediately fix this issue.
Incompatible keys - Part numbers, FCCID, and circuit numbers should all match and be double checked for as identifying this would lead to a more immediate fix.
Vehicle’s ECU will not accept any more keys (memory full) - If you encounter full memory of keys begin the erase keys process found on the TSL-2 programmer. This will allow for the memory of your vehicle to be reset all while erasing keys that are no longer needed, or have been lost in the past.
The security light still blinks after 90 seconds although ran through key programming
In this instance the security light will be a dead giveaway of what the issue is relative to its flashing code.
Code Types:
Every 2 Seconds Flashing Code - If the light blinks every 2 second then the key is operating normally and is most likely properly paired with your vehicle. To test this remove the programmer, open and shut your doors, and attempt to turn on your vehicle.
If this fails and you find that the light is still blinking after reintroducing the key into your vehicle then programming has failed and you will need to reattempt.
2-1 Code - A code that blinks twice followed by 1 blink means “Programming failure.”
Programming failure can occur due to improperly following directions of programming, key compatibility issues, issues with the vehicle’s computer, issues with the connectivity of all instruments included, or a faulty key chip.
If all these items have been checked and programming has been reattempted at least 3 times, and each time proper reset has been done (Unplugging all items, turning on vehicle to run for 30 seconds, open and close the doors, programmer retry) then a key replacement and/ or programmer replacement may be needed.
2-2 Code - A code that blinks twice, followed by two more blinks means “Key Already Programmed.”
If you find this to be the case, unplug all items, open and close the vehicle’s doors, then follow to turn the ignition to “run”. Key should be fully functional. If this is not the case please reach out to one of our agents.
2-3 Code - A code that blinks twice followed by three more blinks means “Maximum Amount of Keys are Programmed to the Vehicle” in which case you will need to enter the ECU procedure found above.
Have any other questions or concerns?
If we missed anything, don’t hesitate to contact us at [email protected], we look forward to speaking with you and getting you back on the road with peace of mind.