BGW210, BGW210-700 ARRIS uDSL Wireless Residential Gateway.DK-MBOX-030 DKnight Magicbox Wireless Speaker.I just want to inform you all about something I have noticed lately that could save you or your customers a lot of time, money, and aggravation.
Let me reiterate, this is not meant to make Snap-On look bad. Not to mention the shops don't always give all of the info that I need to properly diagnose it so i was a bit skeptical. The first time i saw it I was in denial as I thought there could be no way that clearing codes with a scan tool could ruin a module. Please share if you have run into this issue. In my opinion something safety related like this should have been made aware of as it is costing shops / customers thousands not to mention the safety aspect. I dont know the exact years of vehicles affected but I know that I have personally witnessed it on 09, 10, and 2011 model year Toyota and Lexus vehicles. Basically anything with 18.2 and older you dont want to "clear all faults".
#USING LABSCOPE SNAP ON MODIS ULTRA SOFTWARE#
It appears the problem is software level related and not scan tool related. He went on to say that the fix in 18.4 was just a band-aid of sorts as it just skips the OCS module when you select " clear all faults". He explained that somehow the scan tool was corrupting the OCS module only when you do a "scan all modules" then " clear all faults". He had even went as far as telling me that the problem has been fixed as of 18.4 software version. I explained what I had found over a 3-month span and he addmitted that they were aware of a problem. He had checked with another rep who did not know anything about it either so I called tech support. I followed diagnostic which lead me to a faulty OCS module / seat assembly.īy now I have a pretty good idea what is going on so I called my local Snap-On rep and asked if he had heard of this. I scanned it and found a B1797-OCS calibration abnormal code. He said the codes was something to do with the occupant classification module. I asked the tech and he told me that for some reason the light came on after he cleared the codes in an attempt to fix the steering angle sesnor problem. I went out to the shop and got it calibrated but noticed an SRS warning lamp on. So just last Thursday, 10/25, I got a call for an 09 Tacoma that needed a steering angle sensor calibration done. By now I'm convinced there is something going on with the Snap-On software but I did'nt have a way to prove it and did'nt feel like wasting time trying to explain it to tech support. Coincidentally he had just had a Lexus the week before with exactly the problem I had described but in that case he had just assumed the shop screwed up so he did not look too deep into it. I called a fellow mobile tech and told him what I had been seeing. I checked it out and confirmed that it does indeed need a seat cusion / OCS module. A tech had used a snap on tool to "clear all faults" and then an SRS warning light came on with faults for OCS that were not there before. So a few weeks go by and I get another similar call with the same story. It got me thinking about what could have happened but since it was the first time I had heard of it I just noted it and kept moving. Each and every case required a new passengers seat cushion / OCS module to fix it. Several techs had suggested that possibly the snap on scanner had caused the problem. However, after doing a read all codes and clear all, the SRS warning lamp came on.
I found several cases where techs had no airbag light on. They were adamant that the light was not on, so I started to research this problem. I asked what tool they were using and they said a Snap-On Modis Ultra was used. They said they had scanned it for faults and cleared those faults then the SRS warning lamp came on. I got curious so I asked specifically when they noticed the light on. The shop started telling me how the car had no airbag light on when it arrived but at some point it came on during the crash repair process. So I performed my diagnostics and found that the OCS module was bad and needed to be replaced.
The zero point calibration procedure is a common thing that needs to be done on nearly every Toyota and Lexus that was in a rear-end collision. I tried to perform a zero point calibration procedure but it would fail every time. I found codes B1795-occupant classification ecu malfuntion and B1797-calibration abnormal. So rewind about 3 months ago when I got a call from a bodyshop to diagnose an airbag warning lamp on with fault codes stored on a 2011 ES350. It's a bit of a long story but follow it to the end and I promise it'll be worth it. I just want everyone to be aware of what I feel is a huge problem that should have been made known throughout our industry. First of all I am not trying to bad mouth Snap-on by any means. I wanted to share an issue that I have been noticing lately on some Toyota and Lexus vehicles.
0 kommentar(er)
