porsche vts delete

This isn't a simple plug-and-play removal. The VTS (often the Vodafone/Cobra unit) is deeply integrated into the vehicle's security and CAN bus network. Just ripping it out will usually cause alarm issues, massive dashboard errors, or a no-start condition because it often includes an immobilizer circuit.

A proper "delete" involves two distinct steps:

• Physical Removal: You have to locate the VTS module. They are intentionally hidden very well (often deep behind the dash, under seats, or buried in the front luggage area depending on the model/year). You need to disconnect it and, crucially, reconnect/bridge the factory ignition or starter interrupt wires that were routed through the VTS unit during installation.
• Software Coding: This is critical. Once physically disconnected, the car's Gateway module will still be looking for the VTS signal and will throw faults. You need a PIWIS diagnostic tool to access the Gateway coding and change the vehicle configuration to set VTS to "Not Installed".

If you are doing this because of parasitic battery drain (a very common issue with aged VTS units), sometimes just finding and pulling the specific power fuse for the VTS module works as a temporary fix, but a full vеrsiоn delete requires the coding step mentioned above.

Unless you are very comfortable digging into vehicle wiring harnesses and have access to a PIWIS tester, this is really a job for an independent Porsche specialist.

you have to read the memory of the front and back BCM and make changes in the Dflash area.Next, you need to use Piwis to record the necessary encodings

mauzer74 said:

you have to read the memory of the front and back BCM and make changes in the Dflash area.Next, yo...

Click to expand...

Exactly right. That is the "deep" method, especially necessary on newer chassis (like 991, 981, Macan, Cayenne 958, etc.) where the VTS configuration is hard-coded into the BCMs' non-volatile memory rather than just being a toggle in the Gateway.

Just to expand on that for anyone else reading: this is significantly more advanced than standard diagnostic coding.

• You need specialized hardware tools (like Autel XP400, VVDI Prog, or similar EEPROM/MCU programmers) to connect directly to the BCM circuit board pins to read the chip data.
• You need the knowledge to identify the exact hex string in the Dflash dump that controls the VTS configuration and modify it correctly.
• If you corrupt the Dflash data while reading or writing, you can easily brick the BCM.

As you mentioned, once the Dflash is patched and written back to the BCMs, you still usually need PIWIS to perform automatic coding to ensure all modules on the bus recognize the change without errors.

This is definitely expert-level work and not something to attempt with just a standard OBDII tool.

You're absolutely right

mauzer74 said:

You're absolutely right

Click to expand...

Thanks for confirming.

It's important for anyone stumbling across this thread later to understand that this specific method (reading/writing BCM Dflash directly on the chip) is way beyond standard diagnostic work. It carries a very real risk of bricking essential control modules if done incorrectly.

Definitely a job for a pro with specialized bench programming tools.