Webasto's 900 EX Power Bridge: What Vehicle HVAC Buyers Should Expect from Electrical Testing

News facts: Webasto expands a battery-test platform

On June 16, 2026, Webasto's Power Test Systems business announced the 900 EX Power Bridge. The company says it combines two 900 EX units to extend battery-testing capability to ratings of up to 1,500 V and 500 kW. The announcement concerns laboratory power equipment, not an air conditioner, and does not mean an HVAC component requires or delivers that power. It also does not establish that every voltage and power combination within those headline limits is available simultaneously. A project still needs the relevant operating envelope and configuration information. Read the official Webasto release.

For vehicle-HVAC buyers, this news raises a useful question: what electrical evidence should accompany a cooling or heating system before it is installed in a vehicle? The analysis below explains how to define that evidence without confusing the size of a laboratory power supply with the quality of a thermal result.

Begin with the question the bench must answer

A test bench is a tool for resolving a defined uncertainty. It might be used to measure electrical demand, reproduce a permitted supply condition, observe a startup sequence or examine how a controller responds to a vehicle command. Those are different questions, and they may require different equipment and measurement arrangements.

Before discussing bench capability, write the question in a form that can produce an interpretable answer. “Test the air conditioner” is too broad. “Measure input energy during the agreed cabin pull-down sequence under the specified supply conditions” is more useful. It identifies the result, the operating event and the boundary that must be controlled.

The same discipline helps a buyer evaluate a supplier's test report. A photograph of a large laboratory cannot establish which questions were tested for the proposed product. Ask for the test purpose, configuration, conditions and result. A modest setup that answers the relevant question clearly can be more useful than an impressive facility description with no traceable connection to the offered unit.

Keep electrical input separate from cooling output

An air conditioner consumes electrical power and moves heat. These quantities are related, but they are not interchangeable. A bench that measures the electrical input does not automatically measure the cooling delivered to the occupied space. Conversely, a cooling result without the associated electrical conditions may be difficult to interpret for a battery-powered vehicle.

A complete evaluation should state where electrical measurements are taken and how thermal performance is established. The chosen boundary might include only the HVAC unit or might include additional vehicle equipment. Neither boundary is inherently wrong, but the report should make the choice explicit. Otherwise, two apparently similar energy figures may describe different systems.

For a parking-air-conditioning project, the installed electrical path also matters. A laboratory result measured at the unit input is not automatically the same as energy drawn from the vehicle's storage system. The vehicle integration review must account for the actual architecture. The purpose is not to assume a particular loss value, but to prevent an unmeasured difference from being silently ignored.

Read a power rating as an envelope

Headline voltage, current and power ratings should lead to an operating-envelope discussion. They are not a promise that all maximum values can be used together under every condition. The approved equipment documentation must establish the combinations, duration and configuration that are supported.

Simple arithmetic illustrates why the distinction matters. In a hypothetical steady electrical load, 8 kW at 800 V corresponds to 10 A, while 8 kW at 400 V corresponds to 20 A. These figures are only a calculation using power equals voltage multiplied by current. They do not describe a particular heater, compressor or test platform, and they exclude dynamic behavior. They show why a power number alone is insufficient for choosing a test arrangement.

The same reasoning applies to lower-voltage equipment. A nominal voltage label is not the complete range of conditions a vehicle component may need to tolerate. The supplier and integrator should agree the relevant conditions from the approved application requirements. A test plan should then evaluate those conditions deliberately rather than using a convenient laboratory setting as a substitute.

A steady operating point cannot describe a whole duty cycle

A vehicle HVAC system changes demand as conditions change. A laboratory measurement at one operating point can be useful, but it does not describe every stage of a working day. The project should decide which operating sequences matter: initial cabin conditioning, steady comfort, a stationary wait, a restart or a transition between vehicle modes.

For an importer, this matters when comparing products advertised with a single current figure. Ask what that number represents. Is it a measured value under stated conditions, a rated maximum, an average over a sequence or a value observed in a particular mode? Without the definition, a lower figure can be mistaken for an efficiency advantage when the products were doing different work.

A fair comparison uses equivalent tasks and clearly stated conditions. If one system is asked to deliver a different cabin outcome, its energy result should not be presented as directly comparable. The test report should preserve the relationship between electrical use and the service delivered, so that a procurement team can judge the tradeoff rather than simply rank isolated numbers.

Use hypothetical energy calculations to plan, then measure

Early calculations are helpful for sizing a test program and identifying which uncertainty matters most. Suppose, purely as an example, a load averages 1.2 kW for three hours. Its energy use over that period is 3.6 kWh. If another operating phase averages 2.4 kW for 15 minutes, it adds 0.6 kWh. The combined illustrative total is 4.2 kWh at the selected measurement boundary.

Those numbers are not a runtime promise for any battery or HVAC product. They exclude other loads and do not establish usable storage capacity. Their value is that they make the assumptions visible. A team can see whether uncertainty in the long steady phase matters more than uncertainty in the short initial phase, and can focus measurement effort accordingly.

After testing, replace assumed values with measured values for the validated configuration. Retain the conditions under which they were obtained. Do not convert one successful laboratory sequence into a universal field-runtime claim. Vehicle installation, operating behavior and environmental conditions still determine how closely a real duty matches the tested case.

Distinguish a battery emulator from a real vehicle battery

A controlled electrical source can help reproduce a defined supply condition. A real vehicle battery exists within a wider system of controls, limits and operating states. Replacing one with a laboratory source can be useful, but the test must identify which vehicle behaviors are represented and which are not.

Ask whether the bench reproduces only voltage, or also the relevant interaction with the vehicle's energy-management logic. A component may operate correctly when power is continuously available yet behave differently when the vehicle restricts demand or changes state. Those interactions may require additional control simulation or a vehicle-level test, depending on the project.

The point is not that every test needs a complete vehicle. It is that the evidence should match the claim. Component testing can establish component behavior under defined conditions. System testing can examine coordinated behavior. Vehicle testing can address the installed operating outcome. Keeping those boundaries explicit prevents a useful bench result from being stretched beyond what it demonstrated.

Write the power-limitation behavior into the requirement

Electric vehicles often have several functions requesting energy at the same time. The HVAC project should define what happens when its requested demand exceeds the budget currently permitted by the vehicle. The relevant behavior may include reduced output, a delayed function or another approved response. The vehicle manufacturer and integrator must determine the priorities.

A bench test can help examine whether the control response follows the agreed rule. Record the requested budget, actual electrical demand and relevant operating state on the same time base. Then examine how the system enters and leaves the limited condition. The recovery behavior matters because repeatedly gaining and losing permission can expose an interaction that does not appear during a stable limit.

The user interface should agree with the actual state. If the system has deliberately reduced performance, the driver should not be told that it is operating normally at the selected output. Equally, a temporary limitation should not automatically be described as a permanent fault. Clear status information can prevent unnecessary service calls and make genuine failures easier to investigate.

Measurement resolution should serve the decision

Different questions require different measurement detail. A long-period energy comparison needs a reliable integrated total and well-defined boundaries. A short startup event may need a more detailed time record. Choosing a measurement method simply because it produces many data points does not guarantee that it answers the question accurately.

Ask the laboratory to explain how its instruments and recording method support the intended conclusion. The report should identify relevant calibration and uncertainty information at a level appropriate to the decision. A small difference between two products is not meaningful if the test cannot distinguish that difference reliably under the chosen conditions.

Also consider repeatability. If a result changes substantially between nominally similar runs, investigate the starting conditions and operating sequence before presenting the average as a stable characteristic. Consistent preparation and clear records can be more valuable than adding decimal places to a number whose underlying conditions are poorly controlled.

Synchronize the electrical and thermal story

Separate logs can create misleading interpretations when their clocks or event markers do not align. A current change may appear unrelated to a temperature response simply because the records use different time references. A test plan should establish how the important signals are aligned before the run begins.

Choose a small set of events that can be recognized across the records: system enable, a mode request, a power limit or the start of an agreed operating phase. Record the configuration and the meaning of each event. This makes it easier to compare results and to investigate an unexpected response without guessing what happened first.

For a buyer reviewing a report, a well-annotated sequence is often more informative than several isolated plots. It should show the requested function, available electrical conditions and observed outcome together. The goal is to make the system behavior understandable, not to overwhelm the customer with data that has no connection to the acceptance question.

Ask what a laboratory quotation includes

A test service quotation should state the equipment configuration, test sequence, measurement scope and deliverables. It should also identify who supplies the device controls, fixtures and application information. A low test price can become misleading if essential integration work is excluded and discovered only after the sample arrives.

Clarify whether the laboratory is expected to execute an already approved procedure or help develop one. Those are different tasks. If the acceptance criteria are not yet defined, the first activity may be an engineering review rather than a pass-or-fail test. Treating an exploratory run as formal qualification can create a report that neither side intended.

Ask how deviations will be handled. If the sample cannot complete a sequence, the report should preserve the observed result and explain any changes made before retesting. Quietly changing a setting or configuration to obtain a better result destroys the link between the original requirement and the reported outcome. Transparent deviations make the evidence usable.

High-voltage capability is not a workshop instruction

The news concerns professional test equipment. It should not be interpreted as guidance for an installer to connect an unfamiliar high-voltage HVAC component to a general power source. Appropriate facilities, qualified personnel and approved procedures must determine how such testing is performed.

A procurement team can still ask useful questions without designing the test connection. Request evidence that the laboratory's capability matches the proposed task and that responsibilities for the device, controls and test environment are clear. Keep detailed electrical procedures within the competent engineering and safety process for the equipment involved.

For conventional 12 V or 24 V parking air conditioning, use the actual product and vehicle requirements. A high-voltage laboratory announcement does not change the intended supply architecture of an existing unit. The transferable lesson is to define and measure the correct operating boundary, not to adopt a higher-voltage technology simply because it appears in the news.

Turn the test result into an application decision

After a test, ask what decision the result supports. It may support a particular operating mode, identify a required design change or show that more vehicle-level evidence is needed. A report is most valuable when its conclusion is limited to the tested configuration and clearly connected to the next project step.

For a vehicle program, compare the result with the original duty and acceptance priorities. If the electrical demand is acceptable but the occupied-space outcome is not, the project has not met the comfort objective. If comfort is acceptable but the vehicle cannot support the demand through the required period, the integration problem remains. Both sides of the boundary matter.

The VETHY engineering page is a starting point for discussing those requirements. For engine-off truck cooling, the technical enquiry guide helps collect the vehicle, supply and operating information needed before making a product recommendation. Neither page implies that VETHY owns the test equipment discussed in this article or has performed the manufacturer's reported tests.

Keep a compact evidence package for future variants

A useful test package includes the approved question, configuration, procedure, observations, deviations and conclusion. Keep the original data where appropriate, but also provide a readable summary that explains what the result means. The next engineer should not have to reconstruct the purpose of the test from a folder of plots.

Record which assumptions might change on another vehicle variant. A different supply arrangement, controller release, airflow installation or operating duty may require additional review. This does not mean repeating every test for every minor variation. It means identifying whether the earlier evidence remains relevant to the new configuration.

For an importer, this discipline supports more accurate customer communication. A sales team can describe the tested conditions and ask whether the customer's application matches them. That is more credible than presenting a single laboratory number as a guarantee for every climate, vehicle and operating pattern. It also gives technical support a useful starting point when a field result differs.

Agree the comparison before receiving the samples

When two suppliers provide samples, define a common comparison protocol before either result is known. Specify the starting state, operating sequence, measurement boundary and acceptable outcome. Otherwise, it becomes easy to select a favorable result from each report while overlooking that the products were evaluated under different conditions.

Keep any unavoidable differences visible. One sample may require a different control interface or installation arrangement. Record that difference and decide whether it affects the comparison. The answer may be that the samples serve different application needs and should not be ranked in a single table. That is a useful conclusion when it prevents a misleading procurement decision.

Separate mandatory acceptance conditions from preferences. A product that fails a required operating condition should not be made acceptable by averaging it with a strong result elsewhere. Conversely, a product need not maximize every measurement if it reliably meets the project's actual priorities. A clear decision rule reduces the temptation to treat laboratory data as a marketing contest.

Close data gaps without repeating the whole program

A report may leave one important question unanswered even when most of the evidence is useful. Identify that gap precisely before commissioning another complete test series. If the missing information concerns a transition, repeat the relevant sequence with the necessary measurements. If it concerns the installed vehicle boundary, a focused integration measurement may be more useful than another component run.

Keep the reason for the additional work in the project record. This helps distinguish a design change from a measurement improvement or a clarification of the original requirement. It also prevents later reviewers from assuming that an extra test automatically indicates a product failure.

Once the required evidence is complete, stop expanding the program without a reason. More testing is justified by a new configuration, an unresolved question or a relevant failure, not simply by the availability of a larger laboratory platform. The purpose of testing is a defensible application decision. A concise package that answers the agreed questions is better than a growing archive whose conclusions remain unclear.

Frequently asked questions

Does a 500 kW test platform mean an HVAC unit uses 500 kW?

No. A test platform's capability is separate from the demand of the device being tested. The required setup depends on the device and the test objective. Always distinguish laboratory equipment ratings, component electrical input and the thermal performance delivered to the vehicle.

Can a bench test prove overnight parking-AC runtime?

It can provide part of the evidence under stated conditions. A runtime claim also needs the usable energy available to the actual installation, other loads and the relevant duty. Do not convert a measured current at one operating point into a universal overnight guarantee.

Which number should be compared first: current or energy?

Both can matter, but they answer different questions. Current helps characterize electrical demand under defined conditions; energy describes use over a stated period or sequence. Compare equivalent operating tasks and boundaries before deciding which result is more relevant to the vehicle requirement.

What should a supplier provide before a fleet trial?

Provide the tested configuration, operating conditions, measured results, known limits and installation requirements. Identify which vehicle-level questions remain open. A fleet trial can then address those questions deliberately rather than repeating an undefined demonstration with no agreed basis for acceptance.