Differences

This shows you the differences between two versions of the page.

--- hardware:ip [2026/08/17 16:40] – external edit 127.0.0.1
+++ hardware:ip [2026/08/17 16:48] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Instrument cluster (IP) ======
-The **driver's dashboard** — the instrument panel behind the steering wheel — is its own **self-contained computer**, separate from the head unit. It is the module that shows speed, range, state-of-charge, drive mode and the warning lamps. Unlike the centre touchscreen, the head unit **cannot draw on the main cluster**: the cluster renders its own screen and only //reads// values that other modules broadcast on the CAN bus. See [[architecture|Architecture]] for where it sits.
+The **driver's dashboard** — the instrument panel behind the steering wheel — is its own **self-contained computer**, separate from the head unit. It is the module that shows speed, range, state-of-charge, drive mode and the warning lamps. Unlike the centre touchscreen, the head unit **cannot draw on the main cluster**: the cluster renders its own screen and only //reads// values that other modules broadcast on the CAN bus. See [[:architecture|Architecture]] for where it sits.
 {{ :ip_cluster.png?900 |Instrument cluster — internal architecture }}
@@ Line 7: / Line 7: @@
 ===== System =====
-The cluster is a small **embedded Linux computer** paired with a safety microcontroller — the same "big SoC + guardian MCU" split used by the [[hardware|head unit]] and the [[hardware:tbox|TBox]].
+The cluster is a small **embedded Linux computer** paired with a safety microcontroller — the same "big SoC + guardian MCU" split used by the [[:hardware|head unit]] and the [[hardware:tbox|TBox]].
   * **SoC** — an **NXP i.MX6 (Dual)** application processor.
@@ Line 27: / Line 27: @@
   * **Over-the-air (field):** the [[hardware:tbox|TBox]] pulls the update bundle over cellular, the **head unit** receives the cluster's part, and pushes it into the cluster over the **FPD-Link back-channel** as a simple framed, checksummed block transfer. A small updater service on the cluster receives it, verifies it, and installs both the Linux UI part and the companion-MCU part.
-  * **Workshop:** the dealer diagnostic tool flashes it the standard way — **UDS over CAN** through the gateway, behind Security Access. See [[obd2|OBD-II diagnostics]].
+  * **Workshop:** the dealer diagnostic tool flashes it the standard way — **UDS over CAN** through the gateway, behind Security Access. See [[:obd2|OBD-II diagnostics]].
 The update packages are **encrypted archives** that the cluster unpacks and self-installs at boot. The integrity check inside them is a plain checksum rather than a cryptographic signature.