About a week ago I went out to start the 2011 Limited.
My ScanguageII which stays plugged in was blank after starting.
The weather had just changed and it was a cold morning.
I drove away and within a mile or so I was driving slowly through a townhouse complex. My radio started rebooting adn my dash lights started lighting up. The 4Runner actually cut off. It started right back up and I did not experience that any more.
A couple of days later again with drop in temps and this time with snow I roll out and within about a mile or so the radio/NAV reboots. This time I notice that it happens when I hit the brake pedal. It did not cut off this time.
Fast forward to today. Still cold and snow. Within a mile I hit the brakes and reboot. Sometimes the dash lights would show to various degrees, Speedo needle drops and rises, it did not cut off. The steering did not get heavy and I was making turns.
So it's brakes and reboot like the car is just starting but it's simply running normal other than the gauges flashing. So now I brake, reboot, then hit gas and --I think-- it did a little quick reboot with the lunge of acceleration as well... can't be positive about that.
So I was about out of gas and I go fill up. Just like the first time thins happened once I restarted the issue went away. Oh, and the first day with the ScanguageII.. once I unplugged it and replugged it has worked as normal.
I don't even know where to start trying to figure this out. I -thought- it must be electrical and tied to the brake switch but then when I accelerated and maybe got a reboot, I wonder is it a body angle movement thing.
Has anyone ever heard of this? Each day I have been able to repeat this issue multiple times simply by tapping the brake. After a restart it goes away.
I guess the first thing I will do is disconnect the ScanguageII to be sure it's not feeding something back to the ECU. Beyond that, I'm not sure where to start.
Anyone ever seen this or have any suggestions? This is not like the NAV random reboots. Every time it has been right after driving away and going slow and definitely the braking will trigger it.
======================================================================================
UPDATE1: Due to weather conditions, my schedule, etc... I had to go with the easiest trouble shooting first.
1. Unplug Scanguage II
----- Result: All symptoms are gone
-------------- Test Conditions: Same weather, rain, snow, temp, driving style, driving duration, speed, same tank of gas. Basically the conditions are are nearly similar as could possibly be hoped for.
I will now try to re-create the issue. There are only two components to the ScanGuage II. The head unit and the cable. If it fails I will replace the cable. After that I will see if the ScanGuage people can verify that perhaps the firmware got scrambled. I have not researched it to the point of knowing if I can re-flash the firmware myself or what. But so far things are pointing to it being the issue.
Will update as I test and verify further. Probably no one will ever have this exact problem but at least the info will be out there.
My ScanguageII which stays plugged in was blank after starting.
The weather had just changed and it was a cold morning.
I drove away and within a mile or so I was driving slowly through a townhouse complex. My radio started rebooting adn my dash lights started lighting up. The 4Runner actually cut off. It started right back up and I did not experience that any more.
A couple of days later again with drop in temps and this time with snow I roll out and within about a mile or so the radio/NAV reboots. This time I notice that it happens when I hit the brake pedal. It did not cut off this time.
Fast forward to today. Still cold and snow. Within a mile I hit the brakes and reboot. Sometimes the dash lights would show to various degrees, Speedo needle drops and rises, it did not cut off. The steering did not get heavy and I was making turns.
So it's brakes and reboot like the car is just starting but it's simply running normal other than the gauges flashing. So now I brake, reboot, then hit gas and --I think-- it did a little quick reboot with the lunge of acceleration as well... can't be positive about that.
So I was about out of gas and I go fill up. Just like the first time thins happened once I restarted the issue went away. Oh, and the first day with the ScanguageII.. once I unplugged it and replugged it has worked as normal.
I don't even know where to start trying to figure this out. I -thought- it must be electrical and tied to the brake switch but then when I accelerated and maybe got a reboot, I wonder is it a body angle movement thing.
Has anyone ever heard of this? Each day I have been able to repeat this issue multiple times simply by tapping the brake. After a restart it goes away.
I guess the first thing I will do is disconnect the ScanguageII to be sure it's not feeding something back to the ECU. Beyond that, I'm not sure where to start.
Anyone ever seen this or have any suggestions? This is not like the NAV random reboots. Every time it has been right after driving away and going slow and definitely the braking will trigger it.
======================================================================================
UPDATE1: Due to weather conditions, my schedule, etc... I had to go with the easiest trouble shooting first.
1. Unplug Scanguage II
----- Result: All symptoms are gone
-------------- Test Conditions: Same weather, rain, snow, temp, driving style, driving duration, speed, same tank of gas. Basically the conditions are are nearly similar as could possibly be hoped for.
I will now try to re-create the issue. There are only two components to the ScanGuage II. The head unit and the cable. If it fails I will replace the cable. After that I will see if the ScanGuage people can verify that perhaps the firmware got scrambled. I have not researched it to the point of knowing if I can re-flash the firmware myself or what. But so far things are pointing to it being the issue.
Will update as I test and verify further. Probably no one will ever have this exact problem but at least the info will be out there.
Last edited: