The HIL404 real-time simulator is designed for hardware-in-the-loop (HIL) testing of power electronics, control systems and related applications. Its headline specification is a simulation time step down to 200 ns, alongside fast digital input sampling, a 16-bit analog interface and configurable FPGA processing. For engineers and system integrators, these capabilities matter when evaluating how a simulator can represent switching behavior, connect to a controller and support repeatable testing.
Specifications alone do not determine whether a platform suits a project. Channel counts, signal ranges, communications interfaces, model requirements and the workflow for creating and running tests all need consideration. The HIL404’s published features provide a starting point for that evaluation.
What a 200 ns time step means for HIL testing
A simulation time step is the interval at which a real-time model advances. The HIL404 supports a time step down to 200 ns, intended for applications that require short simulation intervals. The platform also lists real-time emulation of nonlinear machines with spatial harmonics and semiconductor power losses. These model capabilities are relevant when a test depends on representing machine or semiconductor behavior in the real-time simulation.
The shortest available time step is one specification to assess, not a guarantee that every model will run at that rate. The model, selected solver, execution configuration and required I/O all form part of a practical setup. Engineers should confirm that the intended model and test workload are supported at the required execution rate.
HIL404 real-time simulator processing and I/O
The HIL404 uses an FPGA as its main processor and offers configurations of up to four cores. The published comparison states that the FPGA processor is 75% faster than the HIL402, while the CPU co-processor is 10 times faster. The analog and digital I/O are described as 2.5 times faster than those of the HIL402. These are comparative claims in the product specifications; actual project performance depends on the application and configuration.
Analog and digital channels
The listed channel complement comprises 16 analog inputs, 16 analog outputs, 32 digital inputs and 32 digital outputs. Analog I/O has 16-bit resolution and a voltage range of ±10 V. The published analog-output update rate is down to 200 ns across all 16 channels.
For digital signals, the specifications give 3.5 ns GDS oversampling on all digital inputs and 3.5 ns PWM modulators on digital outputs. Such timing specifications are important to examine when a test involves fast switching signals or precise input capture. They should be considered alongside signal levels, interface requirements and the timing behavior of the device under test.
The system also includes a built-in scope, with the software description specifying a 16-channel real-time signal-monitoring oscilloscope. This supports observation of test signals within the platform’s stated monitoring capabilities.
Connectivity and system integration
Available interfaces are listed as Ethernet, CAN, RS232, GPIO, HSSL and JTAG, with USB 3.0 also included in the technical specifications. The platform can communicate with other real-time devices, and up to four HIL404 devices can be connected in parallel. These options give integrators several connection paths to assess when planning a test bench or coordinating multiple devices.
Compatibility is listed for the HIL DSP Interface, HIL Breakout board, HIL dSpace Interface and HIL uGrid DSP Interface. Before deployment, teams should verify that the required interface hardware, communication method and controller connections match their specific test arrangement.
Modeling, control and test workflow
The HIL404 is supplied with HIL Control Center, described as a simulation environment with a real-time interface that does not depend on third-party simulation software. Its stated modeling libraries and toolboxes cover converters, microgrids, power systems, signal processing, test suites and communications. The communications toolbox lists protocols and technologies including IEC 61850, UL 1741, CAN Bus, Ethernet, DNP3 and Modbus.
The software description also identifies several workflow features that may be relevant to engineering teams:
- Control options: Switching components can be modeled with internal control for simulation and real-time simulation, or external control for HIL simulation.
- Plant-only simulation: Plant simulation can be run without a controller for feasibility testing.
- Model execution: Dedicated solvers are listed for switching devices, machines, signal generators and lookup tables, with support for numerical signals at multiple execution rates.
- Testing and automation: A test environment supports model testing and test-report generation. The platform also includes a Python-based scripting environment and an API for automation and communication with other simulation software.
- Model and code import: The listed options include importing controller code generated with MATLAB, Simulink, LabView or PSIM, as well as DLL files generated from PSCAD, EMTP or PSSE-DigSilent.
The software information further specifies a permanent license for modeling and the real-time interface, lifetime updates and an unlimited number of software users. It also lists an academic premium toolbox package with a graphical user interface. Teams evaluating the platform should confirm the licensing and package details applicable to their intended use.
Assessing the HIL404 for an application
The HIL404 brings together a 200 ns minimum time step, fast digital input oversampling, 16-bit analog I/O, FPGA-based processing and a broad set of listed interfaces and modeling tools. These specifications can help engineers assess its fit for power-electronics and control-system HIL work, but selection should begin with the test requirements rather than the headline speed.
Define the models, execution rates, signal channels, controller interfaces and communications protocols the test needs. Then verify that the chosen configuration supports the required workload and integration approach. Matching those practical requirements to the HIL404’s documented capabilities is the clearest way to determine whether it fits a proposed real-time test system.