Valeo and Calyos: Why Passive Chip Cooling Is Different from Cabin Air Conditioning

The collaboration announcement

On June 9, 2026, Valeo and Calyos announced a memorandum of understanding to develop and industrialize passive two-phase chip-cooling solutions. The release identifies mobility and data-center applications, including vehicle power electronics and computing. It describes loop heat-pipe technology and a cooling path without an active fluid pump. An announced development collaboration is not the same as a confirmed production release for every listed vehicle application. [Source]

The news is relevant to vehicle thermal management because modern vehicles can contain concentrated electronic heat sources alongside batteries, propulsion systems and cabin HVAC. Those loads do not all need the same cooling method. A technology that is attractive for a processor should not be presented as a direct replacement for an air conditioner.

This article explains the distinction and develops a practical evaluation brief. It does not claim that VETHY supplies the announced technology or that the collaboration's performance claims have been independently reproduced. The aim is to help buyers ask precise questions when an emerging thermal concept enters a vehicle project.

Start with the direction of heat flow

Cooling is often discussed as though every technology performs the same task. In reality, some devices primarily transport heat to a cooler location, while refrigeration systems can use work to move heat against a temperature difference that would not otherwise drive the desired flow. The application determines which function is required.

For an electronic component, the available heat sink may be cool enough to keep the component within its permitted operating range. In that case, an effective heat-transport path can be valuable without producing a cabin-like cold surface. The relevant question is whether the complete path maintains the required component temperature under the intended conditions.

Cabin air conditioning adds different requirements. It must manage an occupied air stream, and its cooling and moisture-removal functions depend on the system design and operating conditions. A device that transfers processor heat to ambient air does not automatically provide those functions.

The first project diagram should therefore identify the heat source, the acceptable source temperature and the available sink. This simple picture prevents unlike technologies from being compared solely because their marketing descriptions both use the word cooling.

Understand the role of phase change without assuming unlimited performance

Two-phase heat transport uses evaporation and condensation within the working arrangement. Phase change can carry substantial heat, but the actual capability depends on the design, fluid, geometry and operating conditions. The term two-phase does not establish a universal capacity or temperature limit.

Ask the supplier to explain the proposed heat path at the system boundary. Where does heat enter, where is it rejected and what conditions must exist at those locations? Which parts are passive, and which surrounding devices still require electrical power?

A passive fluid-transport element may still depend on a fan, an external coolant circuit or another heat-rejection device elsewhere in the vehicle. The buyer should evaluate the complete installation rather than interpreting the absence of one pump as the absence of all energy use.

The supplier's performance information should identify the operating envelope. A successful result at one heat load and orientation does not automatically establish behavior throughout the vehicle's duty. The evaluation needs the conditions that matter to the application and a clear account of what remains unverified.

Identify the electronic load correctly

Electronic heat generation can vary with operating mode. A controller performing a light task may have a different thermal demand from the same hardware under sustained processing or power conversion. The thermal brief should use the load relevant to the intended vehicle function.

Provide the supplier with the heat-source geometry and distribution, not only the total watts. A concentrated hot region can challenge the interface differently from a uniform load over the same external area. The responsible electronics designer should define the allowable temperatures and measurement locations.

Transient behavior matters as well. State how quickly the load changes and how long demanding periods last. Include the starting temperature and the vehicle conditions that influence the available heat sink. These inputs help the supplier assess both sustained and changing operation.

The buyer should distinguish measured load data from early estimates. Preliminary values can support concept selection, but the design needs a route for updating them. If the electronics or software changes during development, review the thermal implications instead of assuming the original estimate remains valid.

The heat sink can be the limiting factor

A highly effective transport path cannot reject heat to an environment that fails to provide the required conditions. The heat sink and its surroundings must be part of the evaluation. This includes the airflow or coolant conditions available in the actual vehicle installation.

Ask where the rejected heat goes after leaving the electronic assembly. If it enters another vehicle circuit, that circuit must have capacity for the additional load. If it is rejected to air, consider the installed airflow and the conditions when the vehicle is stationary.

The surrounding package can change those conditions. Nearby components may warm the incoming air or obstruct a flow path. A bench arrangement with open access to ambient air may therefore differ materially from an enclosed vehicle compartment.

The supplier and vehicle integrator should agree the heat-sink boundary conditions used in testing. Those conditions need to be achievable in the vehicle. If they are provisional, identify the engineering work required to establish them before treating the cooling concept as a released solution.

A thermal-resistance example

For a simplified steady analysis, a temperature difference can be related to heat flow through an effective thermal resistance. Suppose a hypothetical electronic load dissipates 200 watts and the permitted temperature difference between a defined source point and sink point is 20 kelvin. The corresponding maximum effective resistance across that defined path would be 0.1 kelvin per watt.

This example is arithmetic, not a specification for the Valeo-Calyos concept or any VETHY product. It also combines several physical effects into one simplified value. The actual path may include the package, interface material, heat-transport device and final rejection surface, each with its own behavior.

If the interface alone consumes much of the allowed temperature difference, improving another part of the path may have limited benefit. Conversely, an excellent local interface will not compensate for an inadequate final heat sink. The calculation helps the team allocate attention across the complete path.

A real design needs appropriate models and tests for the intended conditions, including transient behavior where relevant. The procurement value of the example is that it makes the boundary explicit. Buyers should ask what points a declared performance value connects and what parts of the installed system lie outside that value.

Passive does not mean independent of installation

The behavior of a passive thermal device can depend on its physical arrangement and operating conditions. The supplier should define the approved orientations, environmental range and other installation limits for the actual design. Buyers should not assume unrestricted mounting from the word passive.

The vehicle application may introduce vibration, movement and changing ambient conditions. The responsible engineers must determine which requirements apply and how they are verified. A demonstration in a stationary computing installation is not automatically qualification for a vehicle environment.

Ask for a package review that includes mounting, interfaces and the planned assembly sequence. If the concept requires a particular relationship between heat source and rejection surface, that relationship should be protected in the vehicle design and change-control process.

The same applies to service. A passive assembly may have fewer active internal elements while still requiring inspection, controlled handling or replacement as a defined unit. The service plan should follow the approved design rather than assume that fewer moving parts eliminates every lifecycle consideration.

Compare complete architectures on equivalent boundaries

A fair comparison must include all equipment needed to provide the required thermal service. Comparing a passive transport element alone with an entire pumped cooling system can produce a misleading result. The buyer should include the relevant heat sink, interfaces, supports and controls in each option.

Use the same heat load, temperature limits and environmental conditions. If one option requires a different vehicle arrangement, state that difference and evaluate its implications. A compact local solution may create a remote packaging requirement that is easy to overlook in a component comparison.

Energy comparisons need the same discipline. Identify which loads are counted and which remain elsewhere in the vehicle. A reduction in one auxiliary load does not necessarily equal the same reduction in total vehicle energy. Any claimed vehicle benefit should follow a calculation or test at the appropriate boundary.

The result may favor different architectures for different locations or duties. The objective is not to declare a universal winner. It is to choose a supported solution for a defined application and understand the tradeoffs that accompany it.

Distinguish a development agreement from an available product

A memorandum of understanding signals an intention to collaborate. It does not by itself provide a released part number, delivery schedule, complete performance map or application approval. Buyers should ask which stage the proposed offering has reached.

A concept-stage discussion may be valuable for a future platform with time for development. A near-term production program may require an already released configuration and a clear validation route. Both can be legitimate opportunities, but they need different planning assumptions.

Ask what samples, drawings and data are available now. Identify the work needed to reach the customer's next gate and who will fund or perform it. A supplier should be able to distinguish existing evidence from development objectives without presenting the latter as completed results.

This distinction protects the buyer from building a schedule around an undefined technology and protects the supplier from expectations it has not committed to meet. A clear maturity assessment is a sign of disciplined engineering, not a lack of ambition.

Build a prototype plan that tests the important assumptions

The first prototype should answer the questions that determine whether the concept is viable in the application. These may concern the local interface, available sink conditions, package or operating range. Avoid designing a demonstration that shows only the easiest condition.

Use representative heat input and boundary conditions where practical. If a test uses a simulated source, explain how it represents the actual electronics and where it differs. The report should retain enough information for the vehicle team to interpret the result.

Measure the locations relevant to the acceptance criteria. A cool external surface does not necessarily establish that the critical internal component remains within its limit. The electronics designer and thermal supplier should agree the measurement approach.

Record configuration and assembly details. Small changes in contact or mounting can affect the result. The prototype becomes useful evidence only when the team can explain what was tested and reproduce the relevant conditions in a later build.

Review manufacturing and interface repeatability

An emerging thermal concept needs a route from a successful prototype to repeatable production. The buyer should ask which characteristics are critical and how the intended process controls them. A manually optimized sample may not represent ordinary manufacturing variation.

The interface between the electronics and thermal assembly deserves particular attention. Define the relevant surfaces, materials and assembly method. Determine how the customer and supplier verify that the intended contact condition is achieved consistently.

If several organizations supply the final assembly, assign responsibility for each interface. One party may manufacture the heat-transport device, another the electronic module and another the final vehicle package. The combined process should preserve the assumptions used in validation.

Change control should cover materials and geometry as well as electronics. A revised board layout, component position or enclosure can alter the thermal path. The project needs a method for identifying which changes require analysis or testing before they enter production.

A practical evidence ladder

At the first level, a supplier can explain the concept and its intended application. This helps the buyer understand the proposed heat path, but it does not establish performance. The next level is data from a defined test arrangement with clear conditions and measurement points.

A stronger level is application-representative testing that uses the customer's load, package and sink conditions. Production-intent evidence then addresses whether the intended manufacturing and assembly process preserves the result. Finally, installed validation checks the complete vehicle context.

These levels should not be collapsed into one label such as proven technology. A concept can be technically credible while still requiring application work. A released product can still need vehicle integration. The buyer should identify the evidence level needed for the decision being made.

Use this ladder to organize supplier discussions. Ask what evidence exists, which level it supports and what work moves the project to the next level. That creates a concrete development conversation and avoids both premature rejection and premature claims of readiness.

Questions to include in the technical brief

State the heat source, load map, allowable temperatures and available heat sink. Provide the installation envelope and relevant environmental conditions. Identify the proposed electrical and mechanical boundaries and the required lifetime or service context as defined by the vehicle program.

Ask the supplier to respond with the supported operating envelope, package requirements and known limitations. Request the test basis for any performance claim. If a claim applies only to a reference assembly, ask what must be checked for the customer's configuration.

Include the program timeline and required evidence gates. A development partner needs to know whether the customer is exploring a future concept or sourcing a near-term production item. Clear timing helps both sides define realistic deliverables.

For a broader HVAC inquiry, explain whether the electronic thermal function is separate from cabin conditioning or expected to interact with it. This prevents the project from treating a heat-transport technology as an undefined addition to an air-conditioning system.

Compare heat-transport claims at named reference points

A thermal proposal should identify the two points between which a performance value is measured. A source-to-sink result can include different physical stages from a device-only result. Without named reference points, two suppliers can provide numbers that look comparable while describing different paths.

For an illustrative 100-watt load, a measured 10-kelvin difference corresponds to an effective resistance of 0.1 kelvin per watt across the stated boundary. If another report gives 6 kelvin but excludes the contact interface and final heat sink, the smaller number does not by itself establish a better installed solution. The boundaries must be reconciled first.

Ask each supplier to mark measurement locations on a diagram. Identify the heat-input method, sink condition and interface arrangement. If the intended vehicle uses another contact or rejection condition, state which additional analysis or test is needed to connect the report to the application.

The same rule applies to a claim of passive operation. Mark which element requires no active fluid pump and identify any powered equipment elsewhere in the path. This avoids describing a complete vehicle arrangement as energy-free when the claim actually concerns one transport element.

For a development program, retain the reference-point diagram with the test data. Later design changes can then be reviewed against the same boundary. A changed enclosure or component position may alter the path even if the thermal device itself is unchanged.

The buyer should also ask how uncertainty is treated. Measurements and models have limits, and a small difference between competing results may not be meaningful without understanding the method. The project should use an appropriate engineering assessment rather than ranking proposals by the smallest printed decimal.

This review does not require the customer to become a specialist in every cooling technology. It requires a clear explanation of what was measured and what the result represents. A supplier that can provide that explanation makes an emerging technology easier to assess and integrate responsibly.

Frequently asked questions

Can a passive heat pipe replace a cabin air conditioner?

Not simply because both move heat. Cabin HVAC has different temperature, airflow and moisture-management requirements. The appropriate architecture depends on the heat source and sink conditions, and a passive electronics-cooling concept should not be presented as a universal refrigeration replacement.

Does no active fluid pump mean zero system energy consumption?

Not necessarily. The complete installation may use fans, other circuits or surrounding equipment. Evaluate the full system boundary and identify which loads remain. A component-level statement should retain its original scope.

Does the collaboration prove vehicle production availability?

The cited release announces a development and industrialization agreement. Availability for a particular program requires confirmation of the released configuration, evidence and supply plan. An intended application is not the same as a completed customer deployment.

How is this relevant to VETHY customers?

It helps distinguish cabin HVAC from other vehicle thermal functions when preparing a project brief. VETHY can discuss the requested HVAC scope and interfaces, while any specialized passive electronics-cooling capability must be assessed separately. The article does not imply a partnership with Valeo or Calyos.

Choose the architecture from the heat path

The most useful response to emerging cooling news is a better description of the application. Identify where heat originates, where it can go and which temperatures must be maintained. Then compare technologies against those conditions and the evidence available at the project's current stage.

That approach allows a buyer to take innovation seriously without treating every announcement as a finished solution. It also keeps the website's broader thermal-management discussion technically clear: cabin comfort, battery conditioning and electronics cooling are connected disciplines with distinct requirements.