The new firmware then downloaded and installed. I therefore had to disconnect it from the car and then open VCDS again, going this time into the section of it dealing with Configuration and Updates, and specifically running the firmware update. When, after updating VCDS, I tried to check it out on my Polo, I got that "interface not found: communication failure" or some similar wording.
With the latest update to VCDS there was also a firmware update for the interface device itself, which I briefly forgot about at the time. I've had it and used it for some three years. Besides that you got warranty on the car and making own "improvements" like that will very likely void that warranty.I've a genuine VCDS, my interface device being a HEX-V2 with lead. There is a reason why one avoids soldering in certain systems like avionics for example, soldering joints tend to brake under stress. In case of the airbag system the control module is checking the components in a certain cycle and like they teach it in VW/Audi tech training under certain circumstances just clearing a code and having the control module check the component can indeed trigger/blow an airbag.Įven though you have VAG-COM you should not work on systems which you are not familiar with, especially not doing any soldering on the airbag system. When a fault code is being set often certain protection mechanisms will be triggered too, this includes control modules ignoring input signals and/or using replacement values. The airbag unit itself comes with a short wiring harness on it, that can be faulty too and would require the complete airbag to be replaced. If this problem comes up when moving the seat this is very likely the case. The problem might be the connector, that's to be determined because it can also be a damaged wiring harness.
0 kommentar(er)
