A bit of history: My cruise control stalk broke. Hubby replaced the stalk. No fix. He replaced the clock spring (sure it was a dirt cheap one.) No fix. Then I figure out that there were two different cruise control stalks that year and the correct one did the fix. We had no light at that time. Within a month or so, the light started popping on. At first it seemed to be dependent on the position of the passenger seat (if it was moved at all, or often times if there was a passenger there.) Now I just can't get the light to stay off. Hubby has checked the connections under the seat. He applied dielectric grease. No fix. We replaced the 12v (which was 7 years old and dying a lot.) No fix. So next of my list (and please change the order or add to the list): 1.) Pick up a new coding device, whether Blue driver or Mongoose Pro 2.) Replace clock spring (which probably wasn't bad to begin with but not OEM now) back to a new, OEM part, although all of my steering wheel buttons work. 3.) Replace the airbag control module (can that have loose connections as well?) So right now I don't know if the light is dependent on the passenger side or the driver's side. It is a 2008 with 210k miles on it. I'm getting dangerously close to not worth the fix. But I need to know that the airbags (whichever one it is) deploys if need be.
You will know more when you get the diagonastic software. The good thing about tech stream is you can use it with any Toyota from 1996 to present.
So, I'm hearing that there were 3 codes, though he can only remember 51. Could the aftermarket clock spring make it throw this code?
welcome! there has been a high failure rate of aftermarket (re: chinese) clock springs, from what i have read. idk if it will cause a code due to the steering wheel airbag, but sounds like one possibility
So, today after months of it being on, the light went off. I had my daughter's car at the garage and I had to swap cars with her. So she took my spare fob that always stays in the house. That is the only difference. Not warmer. Not dryer. Nothing. Only the other fob. Is it possible to throw a random light with a weak fob?
I don't think so. When the SKS parameter KEY LOW-BATT WRN is set ON, it warns when key battery becomes weak by beeping the interior alarm once: Maybe. There are 4 DTC codes linked to the 51 blink code and related to the SRS: DTC No. Detection Item Check Mode SRS Warning Light 1 B1800/51 Short in Driver Side Squib Circuit O ON 2 B1801/51 Open in Driver Side Squib Circuit O ON 3 B1802/51 Short to GND in Driver Side Squib Circuit O ON 4 B1803/51 Short to B+ in Driver Side Squib Circuit O ON Decode for Mark in the check mode column: - : DTC does not correspond to check mode O : DTC corresponds to check mode. The fact the SRS light went off on its own could be indicative of a broken wire in a harness or a fault or loose connection in a plug. (Consider the spiral cable as a wiring harness.) Here is the full work up for the 4 B180x/51 DTCs for you to use when the light comes back on. As you can see the spiral cable is suspect candidate in all of them. Hope that helps. Good luck and let us know how you got on.
Yes, you can use Techstream on the Toyota family (Toyota/Lexus/Scion). However, the latest software version (13.3) will support the latest Toyota (current 2019 model year, and upcomming 2020 model year) best. And it will be backwards compatible for the older Toyota Family. An old version like my 8.0, will NOT be able to FULLY support a 2020 Toyota for obvious reasons. A 2020 will definitely have components that my 2007 does not have. Thus, requiring the latest Techstream software for complete support.
Here is an update: Hubby had kept the OEM clock spring so he reinstalled it in my car. Airbag light problem totally disappeared. Thank you to all you smart, smart people.
