Tag Archive for: Railway

Reliability and RAMSApplication Notes

Advances in Power Electronics: Reliability and RAMS

Engineering Insight · Reliability & RAMS

Advances in Power Electronics: Reliability and RAMS

From the potentiometer to digital and laser trimming, from the electrolytic capacitor to software-based ripple control — a roadmap to 40-year reliability in critical infrastructure and railway

Executive Summary

Industrial and railway power electronics is going through a quiet but decisive transition: the replacement of electromechanical components and manual trimming techniques with solid-state architectures and deterministic calibration processes. Three levers drive this transition — the progressive elimination of the potentiometer, the reduction or elimination of the electrolytic capacitor, and the introduction of laser trimming on thick-film technology as the precision adjustment method in production. Each one targets a specific failure mechanism that historically limited converter service life; combined, they explain why a well-engineered unit today can be committed to an MTBF an order of magnitude higher than its fifteen-year-old predecessor at the same power rating.

This article walks through the three levers, ties them together with the Design for Reliability (DFR) methodology applied at Premium SA — mission profile, derating, FMEA, HALT/HASS, burn-in, FRACAS — and connects the result with the RAMS requirements of railway (EN 50126 / EN 50128 / EN 50129) and of critical grid infrastructure. The thesis is simple: 40-year reliability cannot be bought, it has to be designed; and the technological advances described here are the tools that make such a design viable.

1. The Paradigm Shift: From Reliability as Outcome to Reliability as Design Decision

For decades, the reliability of a power converter was measured after the fact. A unit was designed against a functional specification, manufactured, delivered, and the field failure rate was observed in service. If the number was unacceptable, the design was reworked. This “test-and-fix” approach has a well-known structural cost: correcting a reliability problem scales roughly 1× at schematic stage, 10× at layout, 100× at qualification testing, and grows by several additional orders of magnitude when the issue surfaces in a deployed fleet. The economics simply do not work in sectors with 30-year vehicle or substation lifecycles.

Design for Reliability (DFR), originated at the Center of Reliable Power Electronics (CORPE, Aalborg University) and adopted as the internal standard at Premium SA, inverts this order: reliability is set as a quantitative target at project kickoff — mission profile, target MTBF, service life, environmental conditions, thermal cycling — and the entire development process is structured to meet that number. The associated paradigm shift is the migration from handbook statistical models (MIL-HDBK-217F) toward a Physics-of-Failure (PoF) approach, grounded in the actual physical failure mechanisms: thermal fatigue of solder joints and wire bonds (Coffin-Manson), electrolyte evaporation under Arrhenius, electromigration, corrosion, mechanical fatigue of fasteners.

The golden rule of reliability. A reliability defect detected at schematic stage costs 1 unit to fix. The same defect detected at layout costs 10. At qualification testing, 100. Once the product is in the field and emerges as a warranty return, the cost multiplies by the number of units already manufactured with the defect, plus the asset downtime in each of those cases. The corollary is direct: every euro invested in improving the design process has an economic leverage several orders of magnitude greater than its cost. The three technological levers described below — eliminating potentiometers, reducing electrolytics, trimming with lasers — are textbook examples of this equation: they add cost in BOM or in process, but they remove dominant failure modes.

2. Goodbye to the Potentiometer: Digital Adjustment and Laser Trimming

2.1 The potentiometer as a concentrator of failure modes

The mechanical potentiometer has been the standard component for production calibration and field maintenance adjustments in power converters for half a century. Its appeal is obvious: it allows fine tuning of an analogue value (a voltage reference, a protection trip point, a gain) without changing components or reprogramming anything. But that very flexibility hides a concentration of failure mechanisms unmatched by any other passive component on the converter: mechanical wear of the resistive track; sensitivity to vibration (EN 61373 Cat. 1B); sensitivity to humidity and contamination; single point of intermittent failure via the wiper contact; and human risk in the adjustment — any manual field intervention is an opportunity to introduce an untraced calibration error.

The question is not whether a potentiometer will fail, but when. In a unit with a 30-year service life and a railway or substation mission profile, the answer is invariably “before the end”.

2.2 Replacement strategy 1 — digital potentiometer and parametric calibration

The first replacement strategy moves the adjustment to the digital domain. The analogue reference no longer comes from a trim resistor divider but is generated by software from a parameter stored in the microcontroller’s non-volatile memory or in an external EEPROM. Calibration is performed once in production, on a calibrated and traceable test bench, and is recorded against the unit’s serial number, operator, date and process signature.

Characteristic Mechanical potentiometer Parametric digital calibration
Adjustment mechanism Wiper sliding on resistive track Read parameter from EEPROM/Flash
Temporal stability Cumulative wear, vibration, humidity Only DAC/MCU drift (ppm/°C)
Traceability None beyond manual procedure Digital log signed by serial number
Maintenance risk Misalignment by human intervention Protected calibration (digital signature)
Dominant failure mode Intermittent wiper opening MCU failure or EEPROM corruption
Typical function MTBF < 50,000 h in harsh environments > 500,000 h (silicon-limited)

2.3 Replacement strategy 2 — laser trimming on thick film

What laser trimming actually is. Laser trimming is a solid-state fine-adjustment process for resistors. A resistive paste is screen-printed onto a ceramic substrate (thick-film technology) and sintered at high temperature. The resulting resistor has an as-fired tolerance of around 20 %. A servo-controlled laser then performs a cut in the paste — typically an L-shape or double-cut pattern — removing a precise fraction of the conductive section until the measured resistance reaches the target value, within a tolerance of 0.1 % or better. The result is a passive, fully solid-state component: no moving parts, no contacts, no joints critical to humidity, calibrated to an absolute precision better than what any mechanical potentiometer can hold after a single vibration cycle. The process is reproducible, automatable, fully traceable, and locks the value permanently.

Thick-film technology has matured to make laser trimming a standard industrial process. Modern resistive pastes (RuO₂ and advanced ceramic compounds) provide stable resistors up to 300 °C continuous operation, with temperature coefficients below ±25 ppm/°C in precision grades. Components produced this way are surge-resistant, mechanically robust and their value does not drift over time under normal operating conditions.

2.4 When to choose each strategy

Function to be set Preferred strategy Reason
OVP/OCP/OTP trip points Digital calibration Mandatory traceability; RAMS audit
Control-loop gain Deterministic design (no trim) No post-design adjustment at all
Internal voltage reference Laser-trimmed precision resistor network Absolute stability without firmware involvement
Shunt current sensor Laser-trimmed integrated resistor 0.1 % tolerance with no temporal variation
Instrumentation amplifier gain Laser-trimmed R2R network, IC-integrated Current industry standard
Per-unit offset compensation One-shot digital calibration in production Covers natural silicon dispersion
Field-variable operating point Signed digital parameter Zero physical manual intervention

The practical conclusion is that in a modern Premium SA control board there should be no physical potentiometer at all. Factory adjustments are laser or digital; field adjustments are digital-only, protected by signature; control loops are deterministic by design.

3. Reducing and Eliminating the Electrolytic Capacitor

3.1 The electrolytic as the Achilles heel of the DC bus

If the potentiometer is the Achilles heel of calibration, the aluminium electrolytic capacitor is the Achilles heel of the DC bus. It is typically the component that fixes the service-life ceiling of a power converter, because it combines five awkward properties: service life intrinsically limited by electrolyte evaporation (life ÷2 every +10 °C); ESR growing with ageing; capacitance decreasing to ~80 % at end-of-life; sensitivity to ripple current (Pdis = Iripple² × ESR → self-heating → accelerated ageing); and mechanical sensitivity requiring rigid restraint under EN 61373.

3.2 Premium SA strategy — long-life 105 °C capacitors

The first line of defence, when an electrolytic is unavoidable due to capacitance density, is aggressive part selection. Premium SA standardises on aluminium capacitors rated to 105 °C (some ranges to 125 °C in critical applications) with manufacturer-declared service life of 8,000 to 12,000 hours at maximum temperature — equivalent, by Arrhenius, to over 100,000 hours when operated at 50 °C. Combined with the Premium SA derating policy — Vop ≤ 80 % of Vrated, Iripple_real ≤ 80 % of Iripple_rated, Ta_cap < 85 °C in worst case — this pushes the ageing curve well below the product’s service-life horizon.

But “pushing” is not “eliminating”. As long as there is an electrolytic on the DC bus, there is a wear-out component that defines the slope of the bathtub curve at end of life.

3.3 Why digital ripple control changes the rules

The dimensional argument. The DC bus exists for two reasons: to filter rectification ripple (low frequency, ~100 Hz) and to absorb switching ripple (high frequency, tens to hundreds of kHz). Historically, both requirements were covered by the same bank of electrolytics. Digital ripple control allows the two problems to be decoupled. The switching component, by its deterministic nature, can be tackled actively from firmware: interleaved modulation strategies, predictive ripple control and phase-shedding cut RMS ripple per capacitor by factors of 2× to 4×. The low-frequency component is then covered with a much smaller capacitance value, attainable with polypropylene film capacitors that do not wear out significantly. The net result is the substitution of several thousand microfarads of electrolytic with a few hundred nanofarads to microfarads of film, while preserving or improving DC-bus voltage quality.
Aspect DC bus with electrolytics DC bus with film + digital control
Dominant component Aluminium electrolytic 105 °C / 12,000 h Polypropylene film, > 200,000 h
Dominant failure mechanism Electrolyte evaporation (Arrhenius) No significant wear-out mechanism
Thermal sensitivity Life ÷2 every 10 °C Minimal across operating range
Capacitance with ageing Drops to 80 % at end of life No significant drop
ESR evolution Grows ×2 by end of life Stable across full service life
DC-bus function MTBF Limited by the electrolytic Limited by semiconductors
TCO Low BOM, high service cost Higher BOM, lower service cost

3.4 The measurable impact — MTBF, MTTR, reliability

Removing the electrolytic from the DC bus simultaneously moves all three metrics that matter in critical infrastructure. MTBF rises — we have observed typical 5× to 10× improvements in converters where the electrolytic was the limiting factor. MTTR drops because the LRU is replaced less frequently and the spare-parts catalogue is simplified. Reliability R(t) approaches 1 asymptotically over the full 30-year horizon, instead of degrading in the last 10 years due to electrolytic wear-out. These effects are particularly valuable where downtime carries contractual cost: an electrical substation where a fault triggers DSO penalties, or a rolling-stock fleet where a withdrawal from service breaks the operator’s timetable.

4. Design for Reliability — the Methodology that Ties the Advances Together

The two technological levers above are necessary but not sufficient conditions. 30-year reliability also requires a development process that integrates and verifies them. The Premium SA DFR methodology structures the design across four sequential gates — D2W (Design to Work), D2F (Design to Function), D4R (Design for Reliability) and D4Co (Design for Compliance) — each with quantitative exit criteria.

4.1 Mission profile and derating as non-negotiable input

The first artefact of any Premium SA project is the mission profile: maximum and minimum ambient temperature, daily thermal cycles, cyclic humidity, altitude, vibration, expected number of starts over the service life, frequency of S2 supply-interruption events. Without this input, no PoF calculation has any meaning. With it, derating decisions become quantitative.

Component family Premium SA derating rule Physical justification
Power semiconductors Tj ≤ 80 % of Tj_max (≤ 125 °C Si, ≤ 150 °C SiC) Coffin-Manson on wire bonds: Nf falls as (ΔTj)^β
Aluminium electrolytics Vop ≤ 80 % Vrated, Iripple ≤ 80 % rated Arrhenius law on electrolyte evaporation
MLCC capacitors Vop ≤ 50 % Vrated Capacitance loss vs DC bias on X5R/X7R
Resistors Pop ≤ 60 % Prated, Vop ≤ 80 % Vrated Intra-component insulation
Connectors I ≤ 70 % Irated per contact Contact heating under fatigue
Insulation (creepage/clearance) ≥ 1.5× minimum per EN 50124-1 Margin against long-term contamination

4.2 FMEA, FTA and the failure-mode hierarchy

Once derating is set, reliability engineering concentrates on identifying and mitigating the dominant failure modes through two complementary analyses. FMEA (Failure Mode and Effects Analysis) works bottom-up: for each component and each interface, possible failure modes, their causes and their effects are enumerated, with a Risk Priority Number assigned (RPN = Severity × Occurrence × Detection, 1–10 scale). At Premium SA, any RPN > 80 triggers a documented action plan, and RPN > 100 blocks the D4Co gate. FTA (Fault Tree Analysis) works top-down: it starts from the system failure and decomposes the Boolean combinations (AND/OR gates) that can cause it, allowing the impact of redundancies to be quantified and improvements to be prioritised by sensitivity factor.

4.3 The bathtub curve — each phase calls for a different technique

Bathtub phase Dominant cause Control strategy
Infant mortality (0–500 h) Latent manufacturing defects: cold solder, contamination, assembly errors HALT in design + HASS/burn-in in production + 100 % AOI/ICT
Useful life (500–50,000 h) Random events: overvoltage, ESD, mains transients Protections (OVP/OCP/OTP), derating, preventive FMEA
Wear-out (> 50,000 h) Accumulated damage: thermal fatigue, electrolyte degradation, corrosion Low Tj_max, reduced ΔTj, eliminate electrolytics, condition monitoring

4.4 HALT, HASS and burn-in — what each one does

These three techniques are often confused, and they tackle different problems at different moments. HALT (Highly Accelerated Life Testing) is a limit-exploration test in the design phase: combined stresses (temperature + vibration) are progressively applied beyond the specification, until the operational and destruct limits of the product are found. It is not a qualification test, it is a discovery test — the output is the knowledge of how much margin we hold. HASS (Highly Accelerated Stress Screening) is a production-phase variant, with stress levels chosen just below the operational limit, used to detect latent manufacturing defects without consuming the product’s service life. Burn-in operates the product under controlled temperature (typically +60 to +80 °C) and load for several hours to screen the infant-mortality phase. Premium SA standardises 4 h of burn-in per unit, extended to 8 h on programmes with long maintenance intervals.

The three are complementary: HALT explores; HASS screens in production; burn-in cuts the left tail of the bathtub curve. Applied together, the failure rate during the first year in service drops to a fraction of the value without these techniques.

5. The Other Component that Also Ages — the Software

Any modern converter with digital calibration, predictive ripple control, complex protections and communication with the network supervisor carries firmware of growing complexity. From the function-reliability standpoint, this firmware is just another component of the system — and like any other component, it can be the root cause of a failure that compromises availability. The difference is that software does not age physically, but confidence in it erodes if there is no disciplined verification and validation process.

5.1 V-Model and EN 50128 as the framework for railway firmware

The reference standard for railway-application software is EN 50128, part of the EN 5012x family (railway RAMS). Its central element is the V-Model: each level of specification (system requirements, software requirements, architectural design, module design, code) corresponds to a verification level (unit testing, integration testing, system testing, acceptance testing). Each SSIL (Software Safety Integrity Level, levels 1 to 4 plus Basic Integrity) imposes mandatory techniques: formal reviews, static analysis, specific coverage metrics.

SSIL level Typical converter application Mandatory EN 50128 techniques
Basic Integrity Functions unrelated to safety Code review, functional testing
SSIL 1-2 Cabin auxiliaries, monitoring MISRA C static analysis, unit-test I/O coverage
SSIL 3 Traction converters not brake-critical MISRA + decision coverage + timing analysis
SSIL 4 Active safety functions (e.g. brake inhibition) MC/DC coverage, formal models, redundancy

5.2 MISRA C, MC/DC and why they matter

MISRA C:2012 is the de facto standard for embedded firmware in C in critical systems. Its 143 rules (16 mandatory, 111 required, 16 advisory) cover language patterns that have historically been a source of defects: pointer aliasing, implicit conversions, undefined behaviour, dynamic memory management. Applying MISRA with static analysis (PC-lint, Coverity, Polyspace) removes a whole class of defects before execution. MC/DC (Modified Condition/Decision Coverage) is the most demanding coverage criterion routinely applied in certification: it requires that each individual condition within a Boolean decision independently affects the result of the decision. For a decision with n conditions, the minimum number of MC/DC tests is n+1, against the 2n required by combination coverage.

5.3 HIL and firmware verification on real hardware

The technique that closes the verification loop is HIL (Hardware-in-the-Loop). The firmware runs on the real microcontroller, but the input signals (voltage, current and temperature sensors) are synthesised by a real-time simulator that emulates the behaviour of the DC bus, the transformer, the motor or the load. This allows thousands of scenarios to be executed — including sensor failures, mains transients, short-circuits — with no physical risk to the equipment or to the test bench. A well-designed HIL programme catches hardware/software integration defects that no unit test could capture.

6. RAMS — the Metric that Ties Everything Together

RAMS stands for Reliability, Availability, Maintainability, Safety — the four metrics a railway operator or a grid DSO uses to judge the suitability of a unit across its service life. EN 50126 is the framework standard; EN 50128 and EN 50129 cover software and functional safety respectively.

A = MTBF / (MTBF + MTTR) — High availability requires both high MTBF and low MTTR simultaneously. Optimising only one of the two is not enough: a unit with excellent MTBF but several days of MTTR will deliver lower availability than a unit with moderate MTBF but well-designed LRU architecture. The technological levers above act on both. Removing potentiometers and electrolytics raises MTBF; LRU design with front access, captive screws and keyed connectors lowers MTTR. Digital control, telemetry and self-test reduce diagnostic time — the slice of MTTR hardest to optimise.

6.1 The full R-A-M-S quadrant

Metric Operating definition Dominant design lever
Reliability Probability of fault-free operation across t Component selection, derating, wear-out elimination
Availability Fraction of time the system is operational MTBF + MTTR; redundancy where applicable
Maintainability Ease and speed of diagnosing and repairing LRU design, telemetry, FRACAS, parts continuity
Safety Absence of unacceptable risk FTA, safe failure modes, software SSIL, redundancy of critical functions

6.2 FRACAS — the continuous learning loop

FRACAS (Failure Reporting, Analysis and Corrective Action System) is the process by which every field return is analysed at the appropriate level — LRU, board, component — the root cause is identified, and the corrective action is propagated back to design and production. Premium SA runs FRACAS as a closed loop between Quality, Aftersales and R&D. The consequence is that the fleet population improves over time, rather than degrading: the issue detected in unit #150 is prevented in unit #151.

6.3 PHM and the move to predictive maintenance

The active technical frontier today is PHM (Prognostics and Health Management): the transition from fixed scheduled maintenance toward maintenance based on the actual condition of the equipment. In Premium SA converters we progressively implement: real-time Tj estimation of power semiconductors from Vce_sat and current; cumulative power-cycle counting with the associated ΔTj to predict RUL (Remaining Useful Life) via PoF models; capacitor ESR monitoring by ripple analysis; and periodic export of operational data to the operator’s supervisor over the communications bus. The result is that the operator no longer has to choose between excessive preventive maintenance and late corrective maintenance — the equipment reports how much life is left.

7. Synthesis: the Concrete Levers that Make 30-Year Reliability Viable

Technological lever Failure mode it removes RAMS effect
Eliminating the potentiometer (digital + laser) Wiper wear, vibration/humidity drift, human error in maintenance Raises R, lowers MTTR
Reducing/eliminating the electrolytic (digital control + film) Arrhenius wear-out of electrolyte Raises MTBF 5–10×; flattens bathtub tail
Selection of 105–125 °C long-life electrolytics (where unavoidable) Accelerated Arrhenius ageing of the limiting component Pushes wear-out beyond the 30-year horizon
DFR + mission profile + derating Random faults and overstress in the useful-life phase Raises R in the central area of the curve
HALT in design + HASS/burn-in in production Latent manufacturing defects (infant mortality) Flattens the left tail of the bathtub curve
Software V&V (V-Model, MISRA, MC/DC, HIL) Systematic firmware faults The component that closes the case for a 30-year claim
LRU design + FRACAS + 30-year parts continuity High MTTR and mid-life obsolescence Raises A via the MTTR lever; protects the full lifecycle
PHM + condition monitoring Inefficient maintenance (excessive preventive or late corrective) Optimises total cost of ownership
The takeaway. Components and systems will eventually degrade — that is thermodynamics, not opinion. The job of the power-electronics engineer for critical infrastructure is not to deny degradation but to push it past the product’s service-life horizon, and to ensure that when it does appear it does so in a diagnosable, predictable and inexpensively repairable way. Removing electromechanical components removes failure mechanisms. Reducing or eliminating electrolytics removes the dominant wear-out. Laser trimming and digital adjustment substitute the mechanical wiper with solid state. Digital ripple control turns a hardware problem into a software problem. And software, with the right V&V process, stops being a source of systematic failure. What remains — semiconductors with strict derating, well-cooled magnetics, keyed connectors, conformal coating, an active FRACAS loop and telemetered PHM — is a system whose reliability can be honestly committed to 30 years.

About Premium PSU — With over 40 years of experience, Premium SA designs and manufactures custom power converters in Barcelona for railway, energy, industrial, data center and defence applications.

Contact our engineering team.

FirmwareApplication Notes

Verification, Validation and TDD in Critical Firmware

Engineering Insight · Software V&V

Verification, Validation and TDD for Critical Converter Firmware

Why the firmware of a power converter is a critical reliability component — and how Premium SA treats it as such

1981
Year Boehm formulated the V&V distinction
V-Model
EN 50128 methodological framework for railway firmware
MC/DC
Minimum coverage required at SSIL 4
143
MISRA C:2012 rules (16 mandatory)

Executive Summary

A modern power electronics converter is, today, as much software as hardware. The controller firmware executes regulation loops, protections, digital calibration, active thermal management, telemetry and, in an increasing number of cases, functional safety functions certified to railway SSIL or automotive ASIL. Any defect in that firmware is indistinguishable — from the end operator’s perspective — from a hardware defect: the equipment does not work, does not fulfil its mission, triggers contractual penalties. The difference is that firmware does not physically age, but it does degrade in terms of confidence if it is not subjected to a disciplined process of verification and validation.

This article reviews the fundamentals of software quality assurance applied to embedded power electronics firmware: Boehm’s critical distinction between verification and validation, the Test-Driven Development discipline, the V-Model of EN 50128, the MiL → SiL → PiL → HiL → SYSiL testing pyramid, black-box and white-box techniques, and the “terminological swamp” that persists in the industry. The thesis is direct: critical firmware is designed with the same discipline with which we design a power module — mission profile, derating, FMEA, V&V — because it shares the same customer and the same contractual commitments.

1. Firmware as a Critical Component — Why Discipline Matters

A typical Premium SA converter from fifteen years ago carried minimal firmware: an elementary state machine, a few PI loops implemented in fixed-point arithmetic, hardware protections reinforced with a couple of software checks. The complexity of the embedded code fitted in a few kilobytes and could be reviewed line by line by an expert in an afternoon. That era is over.

The modern converter — integrating digital calibration, active thermal management, predictive DC bus ripple control, CAN/Ethernet/Modbus communication with the operator’s supervisor, PHM telemetry with RUL estimation, OTA firmware update with cryptographic signature, and possibly active safety functions certified to railway SSIL — carries tens of thousands of lines of C code, organised in modular architectures with HAL, RTOS, priority tasks and communications libraries. The probability that such code is perfectly correct on its first writing is, simply, zero.

Firmware as a component with a manageable failure rate. From the RAMS reliability standpoint, firmware is a component like any other in the system. It has its own failure rate, dominated — unlike physical components — by systematic defects (programming or specification errors) rather than random defects. The good news is that those systematic defects can be attacked with methodology: a disciplined verification and validation process reduces them in a quantifiable way. The bad news is symmetric: without discipline, those defects remain latent in the code and emerge — always — at the most costly moment. A firmware failure detected in the fleet has exactly the same economic structure as a hardware failure: penalty, withdrawal, FRACAS, propagation of the correction to the installed population. For this reason, at Premium SA, firmware is treated with the same methodological seriousness as the power module: D2W → D2F → D4R → D4Co applied to software.

2. Verification and Validation — Boehm’s Distinction

The most clarifying distinction in software quality assurance was formulated by Barry Boehm in 1981 through two apparently similar but methodologically distinct questions:

Boehm’s two questions. Verification: “Are we building the product right?” Validation: “Are we building the right product?” The first question looks inward: does the code respect the technical specification? Does each development phase fulfil the conditions set at the start of that phase? The second looks outward: does the final system do what the customer actually needs in their operating environment? Both are necessary. Neither is sufficient on its own.

2.1 The practical differences

Dimension Verification Validation
Question Are we building the product right? Are we building the right product?
Orientation To the internal technical process To the customer and real use
Reference Technical specification User needs
Timing Continuous, phase by phase At the end of development or integration
Dominant techniques Static analysis, reviews, unit testing, MISRA, MC/DC System tests, acceptance tests, full HIL
Granularity “Small-scale” tests “Large-scale” tests
Who decides The technical team The customer / end user
Automatable Mostly yes Partially — the final word is human
Type of error detected Implementation errors vs. the spec Spec errors vs. the real world

2.2 Why both are necessary

Impeccable verification without validation produces technically correct code that satisfies a specification that was itself defective — the team meets its obligations and the customer receives a product that does not solve their problem. Vigorous validation without verification produces code that “works in demo” but hides structural defects that emerge under operating conditions not contemplated in the acceptance test. The two disciplines are complementary and attack different classes of error, and no serious software engineering strategy can do without either of them.

3. The Terminological Swamp — Error, Defect, Failure, Incident

Any serious discussion about software quality carries the historical vocabulary problem. Multiple key terms — verification, validation, test, error, defect, fault, failure — are overloaded with conflicting meanings in the literature. A team that uses these terms interchangeably commits, unwittingly, reasoning errors that translate into process errors. It is worth anchoring the vocabulary to the IEEE standard.

Term Precise definition Example in a power converter
Error Incorrect human action. Mistake in specification, design or coding An engineer assumes the current sensor is bipolar when it is unipolar
Defect / Fault / Bug Internal manifestation of the error. Incorrect state embedded in the code A branch of the OCP protection calculation that never executes because the condition is impossible
Failure Observable inability of the system to fulfil its function — the visible symptom The converter does not trigger OCP protection when current exceeds the threshold
Incident Anomalous event during execution that merits recording and analysis The operator reports an unexpected stop that does not match any known cause
Why the causal chain matters. A human commits an error → the error introduces a defect in the code → the defect may or may not manifest as a failure when executed. A defect can live in code for years without ever causing a failure, simply because the specific conditions that activate it have not yet arisen. This subtlety explains why exhaustive testing is impossible and why deliberate test case design matters. The strategy is not to test everything (impossible) but to test correctly: the conditions most likely to activate latent defects.

4. The V-Model — Verification at Every Level

The methodological framework that articulates verification throughout the software lifecycle is the V-Model. Its proposal is structural: to each level of specification corresponds a symmetric level of verification. The left branch descends from requirements to code; the right branch ascends from unit verification to final acceptance. The V-Model is the backbone of EN 50128 (railway), IEC 61508 (generic), ISO 26262 (automotive) and DO-178C (avionics).

4.1 The V correspondences

Specification level (left branch) Verification level (right branch) Question answered
System requirements (SyRS) Acceptance / system validation tests Does the system meet user needs?
Software requirements (SRS) System tests on firmware Does the firmware satisfy its functional specification?
Architecture design Integration tests between modules Do the modules collaborate as designed?
Module design Unit tests per module Does each module do what its contract says?
Source code Static analysis + inspection Is the code free of dangerous patterns?

4.2 SSIL — Software Safety Integrity Levels

EN 50128 defines five software integrity levels: Basic Integrity and SSIL 1 to SSIL 4. Each level imposes mandatory V&V techniques, scaled in rigour according to function criticality. Premium SA maps its applications to these levels according to the responsibility of each firmware block:

SSIL level Typical application in Premium SA converters Mandatory EN 50128 techniques
Basic Integrity Non-safety-related functions — telemetry, log, UI Code review, functional tests
SSIL 1-2 Cabin auxiliaries, standard OVP/OCP/OTP protections MISRA C static analysis, unit tests with I/O coverage
SSIL 3 Non-brake-critical traction converters, EV BMS MISRA + decision coverage + response time analysis
SSIL 4 Active safety functions (regenerative brake inhibition) MC/DC + formal models + diverse redundancy

5. Test-Driven Development — Tests as a Design Decision

Test-Driven Development (TDD) emerged in the early 2000s as one of the pillars of Extreme Programming and represents a radical inversion of the traditional workflow. In the classic order, the programmer writes functionality first and then — if there is time — adds tests to verify it. In TDD, the order is inverted: the test is written first, before the functionality exists.

5.1 The Red-Green-Refactor cycle

Phase Developer action Code state
Red Write a unit test for functionality that does not yet exist Test fails — confirms the test measures something real
Green Write the minimum code to make the test pass Test passes — the minimum behaviour is implemented
Refactor Restructure the code to eliminate duplication and improve design, without altering behaviour Tests still pass — behaviour is preserved

The cycle repeats in small increments — minutes, not hours. After a TDD session, the developer has produced both the production code and its test battery, and each line of the former is backed by at least one of the latter. The deepest methodological consequence is not having tests, but the inverted order: thinking the test before the implementation forces the developer to understand exactly what success or failure of the functionality means. That is, ultimately, an act of design.

5.2 TDD as a partial substitute for traditional design

TDD is more design than testing. Academic sources and industrial experience converge on a counterintuitive observation: TDD is not primarily a testing technique, it is a design technique. The effort of thinking the test before the code forces the developer to clarify the contract of each function: what inputs it accepts, what outputs it produces, what side effects it has, what error conditions it contemplates. Much of the work traditionally done in “analysis and design” is absorbed within the Red-Green-Refactor cycle. The documented benefits are consistent: better designed and cleaner code, greater scalability, lower defect rate, drastic reduction of regression time thanks to automated tests. The price is a significant learning curve: TDD requires higher-order thinking capacity to apply under pressure, and pedagogical studies suggest its mastery is only internalised with an 80 % practice / 20 % theory balance.

5.3 TDD, BDD and ATDD — the evolution towards behaviour

Pure TDD is effective but has a limit: it is purely technical. A team using only TDD can produce code that passes all unit tests and yet turns out to be inconsistent with the real needs of stakeholders. Two variants have emerged to close this gap. BDD (Behavior-Driven Development) extends TDD by focusing on the expected behaviour of the system, expressed in a ubiquitous language (Given-When-Then) that both developers and customers can understand — the specification is not translated into tests, the specification is the test. ATDD (Acceptance Test-Driven Development) combines requirement specification with automated acceptance tests written before the code. The three practices are complementary: TDD ensures each function is well designed technically; ATDD ensures the complete system fulfils its business purpose; BDD provides the linguistic bridge between the two.

6. Testing Fundamentals — What We Test and How

As Edsger Dijkstra famously noted, testing can be very effective at demonstrating the presence of errors, but is hopelessly inadequate for demonstrating their absence. This limitation is structural: the input domain of any non-trivial program is so large that exhaustively testing all combinations is, in practice, impossible. The discipline of testing therefore consists in selecting a finite, representative subset of the domain that effectively exercises the critical characteristics of the system.

6.1 The test case and the oracle

The basic unit of testing is the test case: a defined set of conditions, input data and an expected result under which the software is executed to determine in a measurable way whether it meets a requirement. Each test case presupposes, implicitly or explicitly, an oracle: the arbiter that decides whether the result obtained is correct. In simple systems, the oracle is the specification itself. In complex systems where no closed specification exists, the oracle is a human expert — the tester who decides whether the observed behaviour matches the expected behaviour.

6.2 Black-box, white-box, and the critical distinction

Aspect Black-box (functional testing) White-box (structural testing)
Knowledge of code None — only the specification is known Total — includes internal implementation
Case design From expected inputs/outputs From control flow paths
Coverage metrics Requirements / equivalence class coverage Statement, branch, MC/DC, path coverage
Detects Discrepancies vs. functional specification Structural defects, dead code, untested branches
Example in Premium SA firmware Converter regulates output voltage with < 2 % error under standard load profiles Each branch of the ADC interrupt handler executes at least once
Limitation Does not detect defects in unspecified code Does not detect missing requirements
The mindset shift that costs most. The foundational principle of modern testing — and the one hardest for a young team to internalise — is that the test is not a demonstration that the program works, but a deliberately destructive process designed to find its errors. A truly successful test cycle is one that manages to make the system fail and brings latent defects to light. A cycle where everything passes at the first attempt is not good: it is suspicious. This inversion of attitude changes even who does the testing. In critical projects, tests are designed — whenever possible — by someone different from the code author, because the author’s confirmation bias is one of the greatest enemies of good testing. At Premium SA, SSIL ≥ 2 tests are reviewed by a Validator independent from the Designer.

7. The MiL → SiL → PiL → HiL → SYSiL Pyramid

For embedded firmware — where code runs on a microcontroller coupled to a real physical system — testing discipline adds a layer of complexity that does not exist in classical application software. Tests cannot be limited to digital inputs and outputs; they must close the loop with the physical behaviour of the converter. The X-in-the-Loop methodology structures this challenge in five progressive levels:

Level What is tested Test platform
MiL — Model-in-the-Loop System model (Simulink, Stateflow) Pure simulation on PC; no C code yet
SiL — Software-in-the-Loop C code compiled for PC Execution on host; I/O are simulated
PiL — Processor-in-the-Loop Binary code in an emulator of the target processor Verifies object code correctness without physical hardware
HiL — Hardware-in-the-Loop Binary code on the real microcontroller Firmware runs on target HW; plant simulated in real time
SYSiL — System-in-the-Loop Complete physical embedded system Final validation on bench with real hardware and real plant

Each level resolves a class of defects before adding an additional layer of complexity. MiL captures modelling and control algorithm errors. SiL captures model-to-code translation errors. PiL captures target-compiler-specific errors, aggressive optimisations and finite arithmetic problems. HiL captures firmware-hardware integration defects: timing, interrupts, races, peripherals. SYSiL is the final validation with the real plant.

Why HIL is the most powerful tool in embedded firmware. HIL closes the firmware verification loop with operational power that is difficult to overstate. The real microcontroller executes the compiled and linked firmware exactly as it will enter production. Input signals (voltage, current, temperature sensors) are synthesised in real time from a simulator that emulates the behaviour of the DC bus, transformer, motor or load. The firmware does not know the signals are synthetic: for it, the system is real. This allows executing thousands of scenarios — including sensor failures, mains transients, short-circuits, overvoltages — without physical risk to the equipment or the test bench. A well-designed HIL programme discovers hardware/software integration defects that no unit test could capture: ADC sample losses in high-frequency interrupts, races between RTOS tasks, protection conditions that trigger incorrectly by a few microseconds. At Premium SA, no critical firmware reaches SYSiL without first passing an exhaustive HIL programme.

8. Premium SA’s D4Co-SW Process

Premium SA applies to firmware the same methodological framework as to hardware: the sequential gates D2W → D2F → D4R → D4Co, adapted to the specific techniques and artefacts of software.

Gate Meaning for firmware Exit criteria
D2W — Design to Work Firmware executes nominal functions SRS signed, modular architecture defined, MiL/SiL prototype running
D2F — Design to Function Firmware meets full functional specification Unit tests ≥ 90 % branch coverage, HIL integration passed
D4R — Design for Reliability Firmware maintains behaviour under adverse conditions Fault injection passed, timing analysis, RTOS stress testing
D4Co — Design for Compliance Firmware meets regulations and is maintainable for 30 years EN 50128 SSIL dossier, MISRA C clean, FRACAS active

8.1 Non-negotiable techniques — MISRA, MC/DC, HIL

  • MISRA C:2012 — static analysis with Polyspace, Coverity or PC-lint on all C code. The 16 mandatory rules and 111 required rules are exit conditions of the D2F gate.
  • MC/DC for SSIL ≥ 3 — every Boolean decision is tested with n+1 cases where each individual condition changes the result while the others remain fixed; for SSIL 4 it is complemented with formal analysis.
  • HIL as exit criterion — no firmware with responsibility over active safety closes the D4Co gate without a complete HIL programme covering the mission profile space.
  • Fault injection for SSIL ≥ 2 — sensor failures, analogue signal noise, communication loss and memory corruption are simulated. The system must always enter a safe state: PWM off, output high impedance, alarm active.

8.2 FRACAS applied to software

The FRACAS methodology — Failure Reporting, Analysis and Corrective Action System — that Premium SA applies to hardware extends to firmware. Any defect detected in the fleet is analysed at the appropriate level (function, module, shared library), the root cause is documented, and the correction is propagated: to all platforms sharing the code, via cryptographically signed OTA update, and to the development process, via a new review rule or new test case that prevents reintroduction of the defect. Fleet firmware improves over time, just as hardware improves through field returns.

9. Synthesis — Firmware as an Engineering Product

Critical firmware in a Premium SA converter is designed with the same discipline as a power module. The pillars are six and are chained:

Pillar Question answered Premium SA practice
Precise vocabulary Are we talking about the same problem? IEEE glossary — error / defect / failure / incident differentiated
V&V per Boehm Are we building the product right and are we building the right product? Continuous phase-by-phase verification + final validation with customer
V-Model + EN 50128 Is each level verified symmetrically? Mapping SRS ↔ SyRS, module ↔ unit test, architecture ↔ integration
TDD / BDD / ATDD Does the test precede the code? TDD on critical modules; ATDD for system requirements
Black-box + white-box Is the spec met and is all code exercised? Branch coverage for SSIL 1-2, MC/DC for SSIL 3-4
MiL → SiL → PiL → HiL → SYSiL Does the firmware work on real hardware with a real plant? Exhaustive HIL before SYSiL; nothing reaches the fleet without passing HIL
The technical closing. Modern firmware is as much a component as the power module. It fails by different mechanisms — systematic defects rather than physical degradation — but produces the same symptom from the operator’s perspective: the equipment does not fulfil its mission. Treating software with the same methodological discipline as hardware is not optional for the railway or critical infrastructure engineer: it is the condition of compliance with the 30-year RAMS commitment. At Premium SA, the D4Co-SW methodology articulates this discipline in gates with quantitative criteria. The result is firmware that enters the fleet with systematic defect rates several orders of magnitude lower than a “test and fix” process, and that improves over time thanks to a FRACAS that closes the loop between real operation and development. Software engineering for critical systems does not consist of avoiding all errors — that is impossible. It consists of building a process that detects them early, documents them with precision, and propagates corrections across the entire system before the next defects reach the customer.

About Premium PSU — With over 40 years of experience, Premium SA designs and manufactures custom power converters in Barcelona for railway, energy, industrial, data center and defence applications. Firmware development is integrated with hardware design from the conceptual phase of each project, following EN 50128, IEC 61508 and ISO 26262 practices.

Developing a converter with safety-related firmware? Talk to our engineering team.

checklistApplication Notes

Buyer’s Guide: Power Conversion Systems for Railway Applications

Buyer’s Guide · EN 50155

Buyer’s Guide: Power Conversion Systems for Railway Applications

EN 50155 and associated standards: everything you need to specify, evaluate and select power supplies, converters and inverters for rolling stock

EN 50155
Core railway standard (2017 revision)
OT1–OT6
Temperature classes −40 °C to +85 °C
25–30 yr
Required rolling stock service life
12
Key supplier questions for qualification

1. Introduction: why this guide matters

The railway sector is one of the most demanding environments for electronic equipment. Power supplies, DC/DC converters, DC/AC inverters, battery chargers and frequency converters operating in rolling stock must withstand extreme conditions of temperature, humidity, vibration, mechanical shock, electromagnetic interference and voltage fluctuations — for 25 to 30 years of service life.

The European standard EN 50155 (equivalent to the international IEC 60571) defines the minimum requirements for this equipment. However, EN 50155 does not operate in isolation: it is complemented by an ecosystem of additional standards — EN 50121 (EMC), EN 45545 (fire protection), EN 61373 (shock and vibration) — that together determine whether a power conversion device is suitable for railway use.

This guide serves two audiences: design engineers who need to correctly specify converters and power supplies, and procurement managers who need objective criteria to evaluate suppliers and make total-cost-of-ownership decisions.

2. The railway standards ecosystem

A power conversion device for railway use must comply with several standards simultaneously, each covering a specific domain:

  • EN 50155:2017 — Core standard: general requirements for all on-board electronics
  • EN 50121-3-2 — Electromagnetic compatibility (EMC) for rolling stock equipment
  • EN 45545-2 — Fire protection and material flammability
  • EN 61373 — Shock and vibration profiles by installation location
  • IEC 60571 — International equivalent to EN 50155
Key point: When requesting a power supply or converter for railway use, it is not enough to ask for “EN 50155 compliance”. You must also specify the EMC requirements (EN 50121-3-2), fire protection (EN 45545-2) and shock/vibration (EN 61373) applicable to the specific equipment location within the vehicle.

3. EN 50155 in detail: key requirements

EN 50155:2017 (replacing the 2007 version) establishes general requirements for all electronic equipment installed on railway rolling stock. For a general introduction to the standard, see What is EN 50155 for railway applications.

  • Supply voltage: continuous, transient and interruption ranges for each nominal voltage
  • Operating temperature: six classes (OT1 to OT6) depending on equipment location
  • Humidity: up to 75% yearly average, 95% for 30 days/year and occasionally 100%
  • Altitude: operation up to 1,400 m (up to 3,000 m under special conditions)
  • Insulation: dielectric strength and insulation requirements between circuits
  • EMC: reference to EN 50121-3-2 for emission and immunity
  • Type tests: full programme including thermal cycling, humidity, shock/vibration and EMC

The 2017 version introduced significant changes: six temperature classes instead of two, more detailed supply interruption requirements, and greater manufacturer/end-user responsibility to define actual operating conditions.

4. Input voltage ranges: classes and tolerances

EN 50155 defines nominal battery voltages of 24, 28, 36, 48, 72, 96 and 110 VDC (recommending 24, 72 or 110 V). For each nominal voltage, the continuous operating range is 0.7 to 1.25 × Unom, and short fluctuations from 0.6 × Unom (0.1 s) up to 1.4 × Unom (1 s) must be withstood without loss of function.

Practical tip: When specifying a converter, always request that the input range covers from brownout (0.6×Unom) to transient overvoltage (1.4×Unom). This ensures full EN 50155 operation without requiring additional external protection circuits.

5. Operating temperature classes (OT1–OT6)

EN 50155:2017 defines six operating temperature classes. The applicable class depends on the equipment location within the vehicle:

  • OT1: −25 °C to +55 °C — passenger compartments and driver’s cabs
  • OT2: −40 °C to +55 °C — passenger compartments and driver’s cabs in cold climates
  • OT3: −25 °C to +70 °C — default class; technical cabinets and equipment compartments
  • OT4: −40 °C to +70 °C — technical cabinets in cold climates
  • OT5: −25 °C to +85 °C — high-temperature locations
  • OT6: −40 °C to +85 °C — high-temperature locations in cold climates
Important: The standard states that OT3 is the default level. If your specification does not indicate a temperature class, the supplier will assume OT3 (−25 °C to +70 °C). Always specify the required class explicitly. Cold-start capability at the minimum class temperature must also be verified during type tests.

6. Supply interruptions and hold-up time

EN 50155 defines mandatory output maintenance during input supply interruptions. It defines interruption classes (S1–S3) and supply change-over classes (C1–C2):

  • S1: no ride-through required during supply interruptions
  • S2: 10 ms interruption without loss of function (default class)
  • S3: 20 ms interruption without loss of function
  • C1: supply change-over at 0.6 Unom for 100 ms, without interruption
  • C2: supply change-over with a 30 ms interruption
Practical tip: S2 (10 ms) is the default interruption class; C1 or C2 apply where the supply changes over between sources. When evaluating offers, ask the supplier how hold-up is achieved: with internal capacitors integrated in the converter, or with external hold-up modules. The integrated solution reduces system BOM and simplifies certification.

7. Complementary standards

EN 50121-3-2 — Electromagnetic compatibility (EMC)

Defines emission and immunity limits for on-board rolling stock equipment. Power converters are among the main sources of EMC interference on board.

  • Conducted emission: limits in the 150 kHz–30 MHz range
  • Radiated emission: limits in the 30 MHz–1 GHz range
  • Immunity: ESD (EN 61000-4-2), fast transients (EN 61000-4-4), radiated (EN 61000-4-3), conducted (EN 61000-4-6)
  • Surge: immunity to surge up to 1 kV (EN 61000-4-5)

EN 45545-2 — Fire protection

Defines the fire behaviour of materials in railway vehicles. Hazard Level (HL1–HL3) classification — most rolling stock requires HL2 or HL3. Tests cover flammability, smoke generation, gas toxicity and burning material dripping.

EN 61373 — Shock and vibration

Defines shock/vibration profiles by installation location:

  • Category 1, Class A: equipment mounted directly on or under the vehicle body
  • Category 1, Class B: equipment mounted inside a cubicle or case that is itself mounted on the vehicle body
  • Category 2: bogie-mounted equipment
  • Category 3: axle-mounted equipment (highest severity)
Always specify the required EN 61373 category and class. A converter qualified for Category 1 (body-mounted) is not automatically suitable for Category 2 (bogie) or Category 3 (axle) installation; severity increases from Category 1 to Category 3.

8. Converter types for railway applications

Power conversion equipment for railway covers a broad range of topologies and functions:

  • DC/DC converters: auxiliary supplies for control electronics, sensors and communications (24–110 V input, 5–48 V outputs, 5 W–1 kW)
  • DC/AC inverters: passenger amenity loads, HVAC auxiliaries, lighting systems (single- or three-phase, 230/400 VAC output)
  • Battery chargers / rectifiers: traction battery and UPS charging, emergency supply (72–110 V input, configurable output)
  • Frequency converters (AC/AC): 50/60 Hz conversion for international rolling stock, fan speed control
  • High-power traction auxiliaries: head-end power, hotel power systems (10–100+ kVA)

Custom engineering is typically required to match the specific form factors, connector layouts, insulation classes and certification requirements of each rolling stock programme.

9. Selection criteria: 12 key questions for your supplier

When evaluating power converter suppliers for railway applications, these 12 questions distinguish a qualified supplier from one that merely claims compliance:

1Certifications: Can you provide EN 50155:2017 type test certificates issued by an accredited laboratory — including EN 50121-3-2, EN 45545-2 and EN 61373?
2Temperature class: For which OT class (OT1–OT6) is the product designed? Have you performed cold-start tests at the minimum temperature?
3Full input range: Does the converter operate from brownout (0.6×Unom, 100 ms) to transient overvoltage (1.4×Unom, 1 s) without external protection circuits?
4Hold-up time: Which interruption classes are supported (S1/S2/S3, C1/C2)? Is hold-up integrated or external?
5Fire protection: Do materials meet EN 45545-2 HL2 or HL3? Provide flammability, smoke and toxicity certificates.
6MTBF / reliability: What is the calculated MTBF per MIL-HDBK-217 or SN 29500? At which ambient temperature?
7Customisation: Can you adapt voltages, power levels, mechanical form factors and connectors to project-specific requirements?
8Manufacturing: Where is the product manufactured? What quality certifications does the plant hold (ISO 9001, IRIS/ISO 22163)?
9Traceability: Do you offer full component and batch traceability for the vehicle lifecycle (25–30 years)?
10Lifecycle support: Do you guarantee product or functional-equivalent availability for 25–30 years?
11Lead times: What are typical lead times for prototypes and series production? Do you offer just-in-time delivery?
12Railway references: Can you provide references with tier-1 OEMs? How many years of railway sector experience do you have?

10. Total cost of ownership (TCO) vs. unit price

One of the most common purchasing mistakes is basing the decision exclusively on unit price. The true cost of a converter over 25–30 years includes:

  • Integration cost: standard converters may require external EMC filters, hold-up modules, mechanical adapters and additional protection circuits — a custom converter eliminates these
  • Certification cost: fewer components = fewer type tests = lower certification cost
  • Field failure cost: higher MTBF = fewer maintenance interventions, less vehicle downtime, fewer contractual penalties
  • NRE engineering cost: amortised over a platform if integration and maintenance savings are significant
  • Obsolescence cost: a supplier guaranteeing 25–30 year lifecycle support avoids costly redesigns
  • Logistics cost: European manufacturing eliminates import tariffs and reduces shipping times
TCO = Unit price + Integration cost + (Cost per failure × Failure rate × Lifetime)
+ Certification cost + Logistics cost + Obsolescence cost

When requesting a quotation, ask the supplier to break down not just the unit price but also the expected MTBF, the integration components required and the long-term support commitment.

11. Specification checklist

Use this checklist when drafting the technical specification for your next railway project:

  • ☐ Nominal input voltage (Unom) and voltage range
  • ☐ Required temperature class (OT1–OT6)
  • ☐ Hold-up class required (S2/C2 or other)
  • ☐ EN 50121-3-2 EMC class
  • ☐ EN 45545-2 Hazard Level (HL2/HL3)
  • ☐ EN 61373 category and class (1A/1B/2)
  • ☐ Output voltage(s), current(s) and power
  • ☐ Isolation requirement (input-to-output)
  • ☐ Mechanical form factor and connector type
  • ☐ IP protection rating required
  • ☐ MTBF target (MIL-HDBK-217 or SN 29500)
  • ☐ Lifecycle support period (25 or 30 years)
  • ☐ Quantity (prototype + series volumes)
  • ☐ Delivery schedule and JIT requirements
  • ☐ Quality certifications required (ISO 9001 / IRIS)
  • ☐ Traceability requirements

12. Glossary

  • DC/DC converter: device converting one DC voltage level to another with galvanic isolation
  • DC/AC inverter: device converting DC (battery) to AC (single- or three-phase)
  • Hold-up time: time during which the output remains within specification after an input power interruption
  • MTBF: Mean Time Between Failures — statistical reliability metric (hours)
  • NRE: Non-Recurring Engineering — one-time design and tooling cost
  • OT class: Operating Temperature class as defined by EN 50155:2017
  • TCO: Total Cost of Ownership — full lifecycle cost including purchase, integration, maintenance and support
  • Type test: formal certification test campaign performed by an accredited laboratory on a representative sample
  • Unom: nominal battery supply voltage (24, 72 and 110 VDC are the most common in railway)

Need guidance for your next railway project?

With over 40 years of experience, more than 900 designs and in-house manufacturing in Barcelona, Premium SA designs power conversion systems for railway, industrial and extreme-environment applications.

Contact our engineering team

About Premium SA — Born in Barcelona, Powering the World. Specialist in custom power conversion systems since 1981, with more than 900 designs, in-house manufacturing in Barcelona and over 40 years serving railway, industrial and extreme-environment applications.
convertidorApplication Notes

AC/AC frequency converters: the little-known solution to a problem everyone has

Application Note · AC/AC Converters

AC/AC frequency converters: the little-known solution to a problem everyone has

How fixed-frequency AC/AC converters solve the 50/60 Hz problem in export manufacturing, railway, marine and industry

Ask ten industrial engineers what a frequency converter is and nine will think of a variable frequency drive (VFD). They are not wrong: VFDs are ubiquitous in industry for controlling the speed of electric motors. But there is a category of frequency converter that goes unnoticed and solves a completely different problem: fixed-frequency AC/AC converters.

An AC/AC converter takes alternating current at one frequency and voltage and converts it into alternating current at another frequency and voltage. No moving parts, no mechanical wear, with efficiencies of 92–96%. And it solves problems that cost companies tens of thousands of euros every year.

The problem: a world divided between 50 Hz and 60 Hz

The world operates on two main grid frequencies. Europe, most of Asia, Africa and South America use 50 Hz. North America, part of South America, South Korea, Saudi Arabia and several other countries use 60 Hz. This division is not an academic detail: it is a real operational problem.

A three-phase induction motor designed for 50 Hz / 400 Vac will run 20% faster if connected directly to a 60 Hz grid. Torque curves change. Cooling capacity is reduced. In compressors, pumps and machine tools, this can mean anything from reduced performance to mechanical failure.

Applications where AC/AC is essential

Export manufacturing

A Spanish company builds industrial equipment for 50 Hz. It wins a contract in the United States, Saudi Arabia or Mexico. Instead of redesigning the machine (cost: EUR 15,000–75,000 per model), it installs a frequency converter between the local grid and the machine. The machine receives 50 Hz / 400 Vac as if it were in Spain.

Railway

Train HVAC compressors are designed for a specific frequency. When the train runs under different catenary systems or crosses borders, the available frequency may change. An AC/AC converter ensures that the compressor always operates at its design frequency. Premium supplies AC/AC converters that perform exactly this function on high-speed trains.

Marine

A ship built in Europe (50 Hz) docks at a port in the United States (60 Hz). Without frequency conversion, motors, galley equipment and air conditioning run out of specification or simply fail. An on-board AC/AC converter eliminates the problem.

Industry

Machinery imported from countries with a different frequency, test laboratories that need to simulate the conditions of another frequency, frequency-sensitive process equipment.

Why a VFD is not the solution

If a VFD can vary the frequency, it seems logical to use it as a fixed converter. But a VFD produces a PWM waveform, not a clean sine wave. For motors (inductive loads) this is acceptable, because the motor filters the waveform. For transformers, resistors, electronics and mixed loads, harmonic distortion causes problems: overheating, interference and erratic operation.

A dedicated AC/AC converter includes an output filter that produces a true sine wave with THD below 3%. It is compatible with any type of load: motors, transformers, resistive heaters, electronics and lighting.

From Barcelona, from 1 kW to 72 kW

We manufacture AC/AC frequency converters at our plant in Barcelona, with power ratings from 1 kW to 72 kW. Our platforms are EN 50155 certified for railway applications and designed for demanding industrial environments. From AC/AC converters in service on regional trains in northern Europe to those powering HVAC compressors on high-speed trains, we have real production experience in the most demanding applications.

If you have an application that requires frequency conversion, we can probably solve it with an existing platform configuration, without the cost or lead time of a fully custom design.

Do you have a frequency conversion problem in your project?

We manufacture AC/AC converters from 1 kW to 72 kW in Barcelona. Tell us about your application and we will advise you with no obligation.

Contact our engineering team

About Premium SA — Founded in Barcelona in 1981, Premium SA designs and manufactures custom power converters for railway, industrial, energy and defence applications, with over 40 years of experience.