A shared vehicle control panel is valuable only when the exact connected devices are supported. An interface name such as CAN describes part of a communication system; it is not, by itself, a promise that equipment from different suppliers will work together.

What the new panel announcement tells buyers

On 21 July 2026, Truma announced the iNet X (Pro) Panel 2, describing upgraded hardware, enhanced CAN connectivity and expanded integration options. The announcement is relevant to RV builders planning centralized control. It does not establish universal third-party AC compatibility.

Request a configuration-specific compatibility list

Ask the system supplier to identify the air conditioner, panel version, connecting components and software versions that have been validated together. The list should distinguish supported functions: switching on, changing the setpoint, selecting fan speed, reading errors and remote operation. A connection that supports one function may not support all of them.

Make responsibilities explicit. If a panel update changes behavior, who diagnoses the problem and who provides the remedy? A vehicle builder should not have to resolve a dispute between two component vendors after delivery.

Test behavior when connectivity is unavailable

Include a normal offline operating scenario in commissioning. Check what the user can control locally and how the system communicates a lost connection. Also confirm the intended behavior following a power interruption. Do not assume the equipment will resume its previous mode automatically.

For remote functions, document the required account, network service and any continuing charges. These are separate from the mechanical cooling capability. Give the owner a clear handover explanation so that an expired service or unavailable network is not mistaken for a failed compressor.

Make diagnostics usable

A useful fault report identifies the affected component and the information a service technician needs. Ask whether logs or error descriptions remain accessible when the remote connection fails. Record how an owner should report an issue, including the model and software details, without requiring them to dismantle the installation.

For an OEM project, include a short function matrix in the purchase specification. Mark each required function as demonstrated, unsupported or still to be validated. This turns a broad claim about a connected vehicle into a testable acceptance agreement and helps prevent avoidable support calls after handover.

Next step

Compare the available configurations in the Vethy product catalog, then request the current model-specific documentation before selecting a unit.

Sources and method