Skip to content

Search is only available in production builds. Try building and previewing the site to test it out locally.

Phone control (lock and unlock)

Stub. What a factory-like phone lock and unlock needs, as a checklist of the other pages. Every item is unknown for now.

Applies to: B6 and B7StubOnly a starting point. Contributions welcome.

The architecture of adding lock and unlock from a phone so that the car treats it like a factory function, and which findings it depends on.

Out of scope: the immobiliser and starting the engine. The goal is locking and unlocking, not driving.

  • Central locking is run by J393 and the door control units J386 and J387 (and J388, J389 if fitted) over the convenience CAN (Convenience system and anti-theft alarm).
  • The alarm arms only when the car is locked with the remote, and disarms on unlocking with the remote or on the key in the driver’s door plus ignition within 15 s (same article).
  • On the A4 the convenience bus is powered from terminal 30 and goes to sleep when not needed after ignition off (Drivetrain and convenience CAN).
  • Rules for connecting to a bus: never join it to another CAN bus, keep the pair twisted, and match the bus colours (CAN bus in the A4 B6/B7).

Status of each piece: unknown until a page records findings.

  • Which bus and where to tap it. The convenience CAN, 100 kbit/s, splices A146/A147 or cluster T32 pins 17 and 18 (CAN bus in the A4 B6/B7). Status: bus identified from the manual; the connection point and method are unknown. See Convenience CAN messages.
  • The lock and unlock messages. Identifier, bytes, sender. Status: unknown. See Central locking and alarm.
  • Lock state feedback. The messages that show whether each door is locked or open. Status: unknown.
  • Alarm interaction. What a bus lock or unlock does to the alarm’s arming and disarming. Status: unknown. See Central locking and alarm.
  • Remote key relationship. Whether a bus-sent lock command is accepted without the key’s involvement, and whether J393 needs anything from the cluster. Status: unknown. See Remote key and Immobiliser.
  • Wake-up and sleep. How to wake the convenience CAN, how long it stays awake, how to avoid keeping it awake and flattening the battery. Status: unknown. See Network management.
  • Connecting hardware without upsetting the bus. Termination, stub length, a gateway or interface that can be left in the car, current draw with the car asleep. Status: unknown.
  • Diagnostics side effects. Whether anything on the bus raises fault codes in the cluster, which is the gateway (Diagnostics). Status: unknown.
  • B6 versus B7. Whether the findings hold on both. Status: unknown.
  • Is J393 reachable by a message that does not originate from the remote receiver, or only from the door control units?
  • Does the bus need to be woken by a message first, and does a wake-up cause the cluster to send anything?
  • What is the lowest-risk place to connect: the splices, a door-module connector, or the cluster?

Start with passive observation of the convenience CAN while locking and unlocking by every normal method, with ignition states noted. Transmitting comes only after the messages are understood, and then first on a bench or with the battery disconnected from other loads where possible. See Contributing a capture.

Parts in the wiring data

CodeNameModelsLocation
J393Central control module for comfort systemB6 and B7At sill panel, front left
J386Door control module, driver sideB6 and B7Integrated in electric window motor
J387Door control module, passenger sideB6 and B7Integrated in electric window motor
J285Control module with indicator unit in instrument panel insertB6 and B7Behind display unit

Sources