Typhoon HIL Forum - Recent questions and answers

TheThermal Calculation

Wed, 13 May 2026 05:38:38 +0000

Answered: How can I import Excel frequency data to control a Signal-Controlled Sinusoidal Voltage Source?

Tue, 12 May 2026 07:48:21 +0000

Hi Alexis,

You can consider using Dynamic table component (documentation) and connect its output to the input of the signal-controlled sinusoidal source (doc).

I would also consider using the API to "program the frequency values over time" in case you're looking at some linear segments and the frequency-over-time curve isn't very complex.

Answered: I can't find the Microgrid library in the 2026.2 Software Release. Where is it?

Wed, 06 May 2026 09:39:13 +0000

The Microgrid library was reorganized in the 2026.2 release and renamed to the Grid Modernization library in order to increase clarity regarding their components' functionalities and better correspond with the licensing scheme.

1. Components that require a Grid Protection license (such as ANSI protective functions, SEL-751 Relay Logic, and Feeder Protection relay) can now be found in the Grid Protection category.

2. Most components that require a Grid Resources license, such as DER components (i.e. switching, average, and generic components that were part of the Microgrid toolbox) and Controller components (ie. components that were part of the Power Systems toolbox) can now be found in the Grid Resources category.

3. Load components have been moved to a new Sinks library category.

Sine Wave in VHIL but Mountain-shaped in C-HIL (TI C2000)

Mon, 04 May 2026 07:12:53 +0000

I am experiencing a strange discrepancy between my VHIL/HIL-to-HIL tests and my actual C-HIL setup.

My system overview:
- GFL inverter with LCL Filter (DC Link: 800V | Grid: 311 Vpeak).
- The plant (inverter and grid) built in Typhoon HIL simulator (HIL604)
- The controller programmed in TI C2000 MCU (Ti28069m) via PLECS Coder.
- PLECS Coder (MCU side) discretization is set to 1e-4. Typhoon HIL is set to "Auto" discretization.

I have successfully built and tested the complete control structure all the way to the outer loop (using power reference to generate the current reference). In this HIL-to-HIL environment, everything works great. Even when applying very high power references that cause some natural distortion, the grid current strictly maintains its sinusoidal shape.

When transitioning to the physical C-HIL, I rebuilt the system step-by-step.

The open-loop tests are perfectly fine (the TI MCU reads the ADC signals safely, and the PWM signals sent back to Typhoon HIL are correctly received).

However, the moment I close just the inner loop (current control), the system breaks. The grid current loses its sine shape entirely and becomes a mountain-shaped waveform.

Looking at the data, the output from the dq-to-abc transformation block shoots up to ~800V. Since the grid is 311V peak, the controller should ideally only demand around ~380V. This massive 800V request heavily saturates the PI controller and completely overmodulates the inverter. (I actually already tried manually scaling down this massive control output so it would safely fit into the PWM limits without overmodulating, but the resulting current still remained in that distorted, mountain-like shape.)

Are there specific execution/task synchronization settings between PLECS Coder and Typhoon HIL that I might have missed when transitioning from HIL-to-HIL to C-HIL? or any ideas on what this issue could be would be greatly appreciated!

Instability due to coupling challenges.

Tue, 21 Apr 2026 09:55:26 +0000

My microgrid model is not is not working properly because I am having challenges configuring the couplings between elements. The frequency measurement of my PV system is dropping fast and the grid forming diesel generator is severely distorted. Could someone advice me the best way to set the couplings.

Answered: Instability with Constant Power Load in 2-bus system

Mon, 20 Apr 2026 12:21:49 +0000

Hi,

This might be related to the snubber resistors in the component, since it uses a current source to interact with the circuit (https://www.typhoon-hil.com/documentation/typhoon-hil-software-manual/References/constant_power_loads_sources.html#:~:text=Rsnb-,Snubber%20resistance,-.)

I propose using one of the following:
1. Constant impedance load https://www.typhoon-hil.com/documentation/typhoon-hil-software-manual/References/constant_impedance_load.html
2. Three phase variable load https://www.typhoon-hil.com/documentation/typhoon-hil-software-manual/References/three-phase_variable_load.html?hl=load

Answered: The Problem is with the Package manager. It is showing error. i tried all to solve it but it is still there.

Mon, 20 Apr 2026 06:59:05 +0000

Greetings Ali,

Sorry to hear that. Unfortunately, we have a bug that has been resolved for the THCC 2026.2 software version, which causes an unhandled error when a user who has no license applied in THCC opens the Package Manager.

The next software release is planned to be out in the next couple of days, which will include this fix.

Best regards,

Answered: Error with Dynamic Table and Three-phase Variable Load

Wed, 15 Apr 2026 14:40:05 +0000

Hello Daniel,

Without the model itself, or at least the error log you are receiving, it would be very difficult for us to determine the reason for the compilation failure.

Based on my experience, I can say that the dimensions of input signals for this component can sometimes be counterintuitive. For example, I would advise you to double-check whether the signals connected to the 'Pref' and 'Qref' terminals have a dimension of 3 as indicated in the documentation (LINK).

Best,
Dusan

Answered: PFC boost converter in Typhoon HIL

Wed, 08 Apr 2026 06:48:26 +0000

Hi Mamadou,

I don't see any screenshots in your post.

Theoretically, there are two distinct segments of your model: Circuit and closed loop control. My advice would always be to try to run in open loop to make sure your circuit operates as expected - before closing the control loops. In case of boost PFC, you can do that by just feedforwarding the grid voltage to boost modulator.

One thing that you might want to make sure is to follow the guide from documentation on this link: https://www.typhoon-hil.com/documentation/typhoon-hil-software-manual/References/single-phase_diode_rectifier.html#:~:text=The%20default%20state,of%20the%20simulation.

Make sure to disable that optimization.

You can also consider using TyphoonSim to develop the controls, as that simplifies the circuit modeling.

Answered: How to create own carrier waveform generator block for sawtooth or triangular waveforms

Thu, 26 Mar 2026 07:48:51 +0000

Greetings,

If you want to create a Triangular Wave Source in signal processing, you can use the following signal processing block: Triangular Wave Source. Additionally, if you set the duty cycle property of this component to 0 or 1, you can get a sawtooth waveform.

If you want to create these signals for PWM modulation for a specific converter block inside Typhoon, we highly recommend using the internal modulator for the specific converter you want to use - Control methods for Converters. This video covers all control techniques you can apply to the converters - Converter control.

Hope this helps,

Answered: I cannot log in on control center

Tue, 24 Mar 2026 08:15:19 +0000

Hii,

The login mentioned on Typhoon HIL Control Center software is for using both THCC and TyphoonSim in integrated way. For this you need to register for TyphoonSim, which will give you a password for login it via THCC. But if you want to use THCC you only need an activation key.

Answered: Execution rate causes inestability

Mon, 09 Mar 2026 11:54:05 +0000

Hi Genis,

My guess is that the averaged DAB becomes unstable when interacting with the rest of the circuit. As you know, system is expected to be less stable as the discretization step increases. Is your model unstable if you put fixed voltage sources at the input/output of the DAB?

Cheers

Answered: Detailed description of the HIL DSP 180 Interface is correct?

Mon, 09 Mar 2026 08:07:00 +0000

Hi Eduardo,

The pin routing on the control card (connector pin to the chip) may depend on the model of the control card you're using. I have used the DSP 180 interface with TMDSCNCD28379D card and the pin mapping was fitting. Which control card are you using?

Answered: AutoCAD drawing

Tue, 03 Mar 2026 10:36:39 +0000

Hi Aleksandar,

Please find attached the AutoCAD (.dwg) file containing the front and rear views of the HIL606 device.

HIL606 - DWG Front and Rear Panel drawing

Best regards,
Marko

Answered: Frequency Limitation on Triangular Waveform Generator

Thu, 26 Feb 2026 15:40:18 +0000

Hi Rupa,

What's the execution rate that you're using? Smoothness of the triangle (ramp) will heavily depend on that, as small incremental steps are done at that rate.

Answered: Can I physically connect TI Launchpad with Typhoon Hil ?device and use them remotely?

Wed, 18 Feb 2026 08:14:54 +0000

Hi,

Physical connection between HIL and Launchpad can be done using HIL TI Launchpad interface.

Connection between PC and HIL device is done the same way regardless of which controller and interface you're using. You can access the HIL remotely if it's connected to the network via Ethernet.

I'd say that the main bottleneck you're facing is connection between the Launcphad and the PC. Having that in mind, the best setup would be a PC connected to the HIL and the Launchpad, which you can access remotely using Remote Desktop connection.

Answered: The regular one icon

Mon, 09 Feb 2026 09:35:38 +0000

Hello Dariusz,

There is an easy way to fix the incorrect Typhoon HIL file association.

To do this, please open the Command Prompt with administrator rights and execute the following command:

typhoon-file-association-fix.cmd

Let us know if you still face a similar issue.

Best regards.
Dušan

Answered: Sim won't run example RLC model

Tue, 03 Feb 2026 08:43:52 +0000

Hi Tim,

As I can see, you don't have a TyphoonSim license associated with your account. You are correct, you are logged in, and a license is installed, but if you open the license dialog, you will probably see that the TyphoonSim license is not active. At the moment, you have a license for Virtual HIL active. To obtain a license for TyphoonSim, please fill out this form.

Best regards!

Answered: HIL 402 license is not valid

Wed, 28 Jan 2026 08:16:21 +0000

Hi Genis Joan Romano,

Let me try to help you here.
The license key which you received for HIL404 as per the second attached screenshot is invalid for real-time execution as it is just a virtual key(not meant for real-time, can only run simulation in software virtually).

However, the device license key for HIL402 which you have available is something different. You must contact the concerned person who has purchased the HIL402 device and they will share the hardware device key with you. Once you receive the key for HIL402 device, open Typhoon HIL software, go to the license option and at the bottom of the pop-up screen you can see change license option(attached picture 1- red block). Once you click there, you can insert the new alpha-numeric license key and restart the software.

After restart, you will be able to see HIL402 in the license window and then your hardware connection will be formed from device manager.

Regarding firmware, once the device is connected, just click on the sync firmware option on the device manager window and your firmware will be automatically synchronized with your current software version(attached picture 2- red block).

Hope this helps.

Era Bajpai

Answered: TyphoonSim unable to run simulation

Fri, 23 Jan 2026 09:46:44 +0000

Hello,

It seems your machine is not handling SSL certificates automatically, and probably they are all missing.

You can try to install certificates manually, you can download them here: root, intermediate and subscription. Try to install one by one following order mentioned above and try to log in (restart software first) when you finish installation. If it asks for password to unpack certificate, type 1234.

Answered: Inquiry on UDP Communication Usage and MAC-Related Changes in Typhoon HIL 2025.4

Thu, 15 Jan 2026 16:42:36 +0000

Hello,

You are correct — in newer versions, the UDP communication module includes an option to configure the MAC address, more precisely the last digit of the MAC address.
This option was not available in previous versions.

There was a bug in earlier versions related to MAC address handling, which we fixed by introducing this new feature. This change may have affected backward compatibility; however, since the functionality worked correctly before, there is no reason it should not work again once everything is properly configured.

Based on the fact that everything was working correctly before, it is clear that you have a good understanding of how UDP communication works. Therefore, there is nothing specific we need to advise you on in this regard.

It is only necessary to configure the last digit of the MAC address again.

Please override the last digit of the MAC address as follows:

Enable “Override last digit in MAC address”

If you were using eth port 2, enter 5 in the “Source device MAC address” field

If you were using eth port 3, enter 6 in the “Source device MAC address” field

If you were using eth port 4, enter 7 in the “Source device MAC address” field

If you continue to experience issues with UDP communication, I recommend using Wireshark as a debugging tool to verify the communication and confirm that the MAC address is set correctly.

Answered: Supervision over ethernet communication protocols

Mon, 05 Jan 2026 15:27:05 +0000

Hello Alejandro,

To answer the first question, currently there is no way to actively monitor the amount of sent messages other than monitoring elapsed time and dividing it by the sample time at which messages are sent from the send block. The UDP send and TCP send blocks also have a status function which returns how many messages weren't sent in case that is useful in your case. Perhaps you could also count received messages on the server which receives them.

As for defining IPs in the model initialization script there seems to be a bug currently so this cannot be done. One workaround is to have the send blocks be in a subsystem that way you can use the pre_compilation code in the mask editor to define IP addresses. I will attach an Example model so you can get a better idea of how this can be done.

Answered: how can i download this freely please help me

Mon, 29 Dec 2025 09:48:03 +0000

Greetings,

You can find instructions on how to download Typhoon HIL Control Center on this link.

Best regards,

Answered: Issues Using Three-Phase Core Coupling in Parallel Inverter Simulation

Mon, 22 Dec 2025 15:21:54 +0000

Hello,

I recommend you 2 ways:
Reviewing the Recommended coupling page in Typhoon Documentationas in the previous answer given. Especially with series or parallel connected inverters.

Second, try to add the snubbers, maybe you only finally need a resistor and not the full one, because without snubbers you can have great distortions than change the results from what was expected.

Hope, this could work.
Kind regards.

Answered: License Extension for Free Version

Tue, 25 Nov 2025 08:47:55 +0000

Hello,

Your HIL Academy license will be extended in due time.

Answered: triangular waveform generation

Mon, 10 Nov 2025 12:15:36 +0000

Execution rate of the Triangular Wave Source component will decide the resolution of the component output. You might want to make sure that your execution rate is at least 100 times shorter than your switching period.

Even better, consider using the PWM Modulator component, to make sure you have the maximum resolution.

Answered: Exporting data real time in VHIL mode or TyphoonSim

Wed, 29 Oct 2025 08:17:33 +0000

Hello Haydar,

For Virtual simulation, the possibility is to export data using data logging widgets only. You can use signal data logger for .MAT or .CSV data storing OR you can use stream data logger for .CSV, .H5 or .MF4. In case for higher data rates, it is not recommended to use .CSV format.
You can use TCP/UDP protocol incase of physical device connection over Ethernet only.

Answered: Voltage Ripple (Drift)

Tue, 28 Oct 2025 08:41:15 +0000

Hello,

Can you recheck if you attached the Excel file as I cannot see it?

Best regards!

Answered: Scope/Capture triggering, but not showing data in Real Time mode

Fri, 17 Oct 2025 06:47:04 +0000

There isn't any additional enabling that should be done. This looks like a communication issue between HIL and PC.

I know it's a silly suggestion, but you can try power-cycling the HIL device and/or creating a new SCADA panel with new Capture/Scope widget, just to see if something went wrong.

Answered: Setting Parallel R–L Load in IEEE Node 611 Model Produces Unrealistic Values

Tue, 14 Oct 2025 08:12:06 +0000

This might have something to do with the snubber inductance in your variable resistor (doc). In addition to this, variable inductor acts as a current source and it might also need snubbers. If not properly parameterized, both of these can destabilize the model. I would try to first confirm that the resistor indeed acts "almost like an ideal resistor", i.e., that the snubber inductance didn't destabilize the circuit (especially at low load - large resistor value).

Three-phase Variable Load component should do the snubber parameterization for you, but it's quite expensive in terms of resources. If you're tight with resources, debugging focused on the variable elements would be the way to go.

Answered: SPI slave - no response to write/read frames

Mon, 29 Sep 2025 07:11:32 +0000

Hi Niall,
In case you issue is not resolved yet, you can try running the attached model using your master input. Check the GPIOs in capture/scope to confirm if the MISO is generating data. You can try the same configuration as I have used below.
Recently, the SPI component has been upgraded with more advanced parametrization, so I recommend you to use this model for Typhoon HIL Control Center Version 2025.3.
Typhoon has also added a new example model for SPI Default_return which can also be used to understand the configuration of the block.

Schematic file

PSO optimization technique how to adapt this code properly for execution in the Typhoon HIL C-block.

Sat, 27 Sep 2025 13:29:01 +0000

Dear Typhoon HIL Team,

I am working on a research project titled “Photovoltaic MPPT Performance Adaptability to Partial Shading Resilience and Load Variations with PSO.” In MATLAB/Simulink, I have implemented and validated the PSO-based MPPT algorithm using a C-function block, and I now wish to port this into Typhoon HIL Control Center for hardware-in-the-loop testing and real-time verification.

My MATLAB code (attached below) takes PV voltage and current (Vpv, Ipv) as inputs and generates the duty cycle (D_out) as output. It uses persistent variables for swarm initialization, particle updates, personal/global best tracking, and smoothing of the duty cycle output.

I would like guidance on:

Code Structure: How to adapt my MATLAB C-function for Typhoon HIL’s C-block (syntax, supported functions, use of init() and step()).
Inputs/Outputs: Correct way to declare Vpv, Ipv as inputs and D_out as output, and how to connect the duty cycle output to PWM blocks.
Implementation Steps: The procedure to load and compile this code in the Schematic Editor, handle unsupported functions (e.g., rand, linspace), and properly manage persistent variables.
Verification: Best practices to confirm that the Typhoon C-block produces results consistent with MATLAB under partial shading and load variation tests.

My main goal is to compare MATLAB simulations with Typhoon HIL results under identical conditions for benchmarking MPPT performance. Any step-by-step instructions, references, or example templates would be greatly appreciated.

Thank you for your support.

Below, I have provided a detailed explanation of the MATLAB C-function block along with the points where I am seeking clarification:

1. Code Structure

In MATLAB, my MPPT logic is encapsulated in a C-function block with persistent variables for maintaining PSO states such as swarm positions, velocities, particle bests, and global best. Below is the complete implementation:

%% ------------------ PSO Parameters ------------------

persistent swarm iter stepCounter P_hist D_out_prev

% PSO constants

N = 30; % number of particles

maxIter = 300; % max iterations

c1 = 1.8; % cognitive factor

c2 = 1.8; % social factor

w_max = 0.9; % max inertia

w_min = 0.4; % min inertia

D_min = 0.05; % min duty cycle

D_max = 0.95; % max duty cycle

% Moving average for stability

avgWindow = 7;

updatePeriod = 1; % update every step

perturbMagnitude = 0.02; % small perturbation

%% ------------------ Initialization ------------------

if isempty(swarm)

D_sweep = linspace(D_min, D_max, N);

swarm.x = D_sweep; % particle positions (duty cycles)

swarm.v = zeros(1,N); % particle velocities

swarm.pBest = D_sweep; % personal bests

swarm.pBestVal = -inf(1,N); % personal best power

swarm.gBest = D_min; % global best duty cycle

swarm.gBestVal = -inf; % global best power

swarm.k = 1; % current particle index

iter = 1;

stepCounter = 0;

P_hist = zeros(1, avgWindow);

D_out_prev = swarm.gBest;

D_out = swarm.gBest;

return;

end

%% ------------------ Slow Update ------------------

stepCounter = stepCounter + 1;

if stepCounter < updatePeriod

D_out = D_out_prev;

return;

else

stepCounter = 0;

end

%% ------------------ Moving Average Power ------------------

P_hist = [P_hist(2:end), Vpv*Ipv];

P = mean(P_hist);

%% ------------------ Update Personal Best ------------------

if P > swarm.pBestVal(swarm.k)

swarm.pBest(swarm.k) = swarm.x(swarm.k);

swarm.pBestVal(swarm.k) = P;

end

%% ------------------ PSO Update ------------------

w = w_max - (w_max - w_min)*(iter/maxIter);

r1 = rand; r2 = rand;

swarm.v(swarm.k) = w*swarm.v(swarm.k) ...

+ c1*r1*(swarm.pBest(swarm.k)-swarm.x(swarm.k)) ...

+ c2*r2*(swarm.gBest - swarm.x(swarm.k));

swarm.x(swarm.k) = swarm.x(swarm.k) + swarm.v(swarm.k);

%% ------------------ Clamp Duty Cycle ------------------

swarm.x(swarm.k) = max(min(swarm.x(swarm.k), D_max), D_min);

%% ------------------ Move to Next Particle ------------------

swarm.k = swarm.k + 1;

if swarm.k > N

swarm.k = 1;

iter = iter + 1;

% ------------------ Update Global Best after all particles ------------------

[bestP, idx] = max(swarm.pBestVal);

swarm.gBest = swarm.pBest(idx);

swarm.gBestVal = bestP;

% ------------------ Small Random Perturbation ------------------

if mod(iter,20)==0

swarm.x = swarm.x + perturbMagnitude*(rand(1,N)-0.5);

swarm.x = max(min(swarm.x, D_max), D_min);

end

%% ------------------ Reset if maxIter ------------------

if iter > maxIter

D_sweep = linspace(D_min,D_max,N);

swarm.x = D_sweep;

swarm.v = zeros(1,N);

swarm.pBest = D_sweep;

swarm.pBestVal = -inf(1,N);

swarm.gBest = D_min;

swarm.gBestVal = -inf;

iter = 1;

end

%% ------------------ Smooth Duty Cycle Output ------------------

alpha = 0.2; % smoothing factor

D_out = alpha*swarm.gBest + (1-alpha)*D_out_prev;

D_out_prev = D_out;

end

function D_out = PSO_MPPT_PV_Stable(Vpv, Ipv)

Answered: Signed Integer to 32-bit Boolean Conversion in Typhoon HIL

Thu, 25 Sep 2025 10:49:58 +0000

Hello,

Using data type conversion should work in this case. Like so:

In this example the output is 0xFFFFFFFF which is exactly -1 in the two's complement system.

Answered: ISO 15118-20 integration with EV digital twin package

Mon, 22 Sep 2025 12:51:59 +0000

Hi Jeremy

Thank you for reaching out.

At the moment, the ISO 15118-20 component is available in the schematic editor, but we have not yet completed its integration within the EV digital twin package (please note that the EV twin is provided as a separate paid toolbox).

That said, you can still use the EV twin with ISO 15118-2 for bi-directional charging. To do so, simply enable the option in the mask to allow negative current (this same option is also available in the ISO 15118-20 component). With this setting, you won’t need to use certificates for V2G operation.

If you would like to work directly with ISO 15118-20 I recommend that you use our example model for EVCC and substitute the -2 component for the -20.

Let me know if you would like to have access to an example model with the certificate files.

Best regards,

Answered: KWh calculation

Mon, 22 Sep 2025 06:36:56 +0000

The energy consumed in a three-phase circuit can be determined from the active power values over time. If the active power is constant during the observation period, the energy is simply the product of power and time. However, if the active power varies, the energy is obtained by summing the contributions of power at each time step multiplied by the sampling interval. This method ensures accurate estimation of energy consumption for both steady and time-varying load conditions.

Answered: Problem with login on TyphoonSim

Thu, 18 Sep 2025 07:51:56 +0000

There is similar question on this forum, please try this:
https://typhoon-hil.com/forum/?qa=278/the-software-cannot-log-in

Answered: How to use the VBR PMSM in non-linear mode?

Fri, 12 Sep 2025 12:07:23 +0000

Hello Antonio,

We recommend using the latest version of THCC, as the older versions did not support the nonlinear mode for PMSM VBR. For example, if you are using THCC 2025.1, then, the non-linear mode is not supported, which is indicated in the component dialog window (see below attached image).

Answered: How to use lookup tables in TyphonSim for non-linear PMSM?

Wed, 10 Sep 2025 07:48:44 +0000

Hi Antonio

What type of look-up table you are trying to run. Is it 2D flux/inductance tables or is it 3D spatial tables?

Also, are you using torque tables, or just fluxes?

An example data set for these tables are provided in the component help page here:

https://www.typhoon-hil.com/documentation/typhoon-hil-software-manual/References/three_phase_permanent_magnet_synchronous_machine.html

Let us know if that helps. I can also take a look at your tables if want to see if they are in the correct format (rows and columns matching their corresponding axis and their signs)

I'm attaching a sample model with torque tables for reference.

https://typhoon-hil.com/forum/?qa=blob&qa_blobid=2812335623446789278

Also if you don't mind, would you let me know which version of the Typhoon Control Center you are using?

Answered: Typhoonheck HIL 604 and uGrid DSP Interface 2.1 Compatibility

Mon, 08 Sep 2025 08:50:36 +0000

Hello,

Both interface boards are compatible with HIL604. There are no any specific configuration steps required to use them with HIL604 device - just make sure the controller(s) are properly powered and programmed.

BR

Answered: Support Request – Noisy ADC Results with Typhoon HIL 101 and TI F28379D

Fri, 29 Aug 2025 08:01:45 +0000

To follow up on Jovan's answer, I've attached a simple model where you can generate the code and validate ADC by using TI C2000 Toolbox. There is a subsystem called 'adc' where ADC component is configured and TI C2000 Setup component where you can click 'Build and deploy' button to generate and deploy the code to your controller. The value of the signal is scaled to PWM duty cycle range and applied to the input of the PWM component.

In order to observe ADC result, you can track the value of 'ao1_sample' probe in Code Composer Studio, or you can use the part of the model with PWM Analyzer which will output the duty cycle value of the PWM signal applied to the HIL digital input selected in the PWM component. This is an easy way to observe signals from external controller in SCADA. Keep in mind that you need appropriate HIL firmware configuration that supports PWM Analyzer according to device configuration table.

Answered: Why are the currents on my interleaved converter not balanced?

Mon, 25 Aug 2025 07:50:06 +0000

Let's consider an interleaved buck converter, consisting of two legs A and B. We want to understand the origin and estimate the value of a current imbalance that can occur.

In order to analyze the circuit, we can assume a continuous conduction mode. In such operation, the average output voltages at the switch node are given with va = Da*Vin, vb = Db*Vin. Current unbalance will occur if there is some difference in duty cycles. If we express this difference in terms of duration, we can derive a generalized equation to calculate the current, as shown in the image.

In a real-world system, even if PWM modulator is programmed perfectly, the uncertainty will always exist with regards to signal propagation in the system due to the multiple reasons. Imperfection of passive components that are incorporated into the digital output/digital input circuit design will inevitably change the time constants of input/output impedances. There is also always uncertainty with regards to IO voltage levels - We specify that the minimum voltage value at which logic-high is detected is 2V, while maximum logic-low level is 0.8V, but we cannot be certain when exactly will the logic level change be detected. This will reflect into uncertainty of pulse duration as well.

In order to estimate the impact of the pulse length difference, let's assume that all the uncertainties add up to a single sample of a difference in pulse lengths of two legs - 3.5ns. If input voltage is 650V, fsw is 200kHz and RL is 10mOhm, the formula yields 45.5A of current unbalance between two legs! This means that even a very small difference in pulse length will cause a significant current unbalance. Therefore, we shall not expect the current to be perfectly balanced when using HIL IO loopback, or the external controller in open-loop.

Interestingly, HIL will be able to capture even 1ns of pulse length difference if the external controller is used, even though the DI sampling rate is 3.5ns. Since the controller isn't synchronized with HIL in any way, duty cycle that's measured will not be constant between multiple switching periods. The average value of detected duty cycle will reflect the 1ns difference, which will be reflected in the simulation results, yielding 13A of current unbalance. This can be confirmed by using PWM Analyzer to measure the average duty cycle over long time span.

Finally, when running on the actual power hardware, uncertainties will be increased due to the fact that turn on/turn off delays on real power MOSFETs have ranges that are often 10s of nanoseconds. For this reason, one should always make sure to actively balance the currents.

Answered: What is wrong that I get this warning?

Mon, 25 Aug 2025 07:20:38 +0000

That warning tells you that, in case you short-circuit the inverter (switch permutation where all switches are closed), you will have a topological conflict between the switches and the voltage source of the DC link. Since you will probably never short-circuit your inverter, that will never actually happen. If you want to remove that ugly warning, you can just place some resistor in series with the voltage source. Even 1uOhm will remove the warning.

Answered: Problem with usb connectivity

Wed, 20 Aug 2025 11:32:18 +0000

Hello,

This might be a firmware issue with the HIL101. During the booting process of the HIL device the LED located at the front of the HIL should blink twice after some time.

Can you check if it is blinking twice on your HIl101? Keep in mind that the LED will first be turned on without blinking for a certain amount of time (around a minute) before you see the blinking.

If it is not blinking this could indicate a firmware issue.

Best regards.

Answered: MODBUS communication issue

Fri, 15 Aug 2025 15:09:59 +0000

Hello, I've tried to reproduce the issue you are facing on a simple model that contains a Modbus Client with settings you provided. In this model, values are set on two SCADA Inputs, and read on the Modbus Server tool, while input values (sent from Modbus Server tool) are read on the output probes of Modbus Client.

Connection was established between pyModSlave tool and Typhoon HIL Modbus Client, and it is possible to both read values on the Modbus Client outputs and receive the sent values on Modbus Device.

Were you able to resolve this issue? Can you please share more details about your model and setup? What HIL device are you using? Is it connected to PC using USB or ethernet cable? Is this the only request on the Modbus Client you set? Are the register addresses overlapping any other addresses on the Modbus Client or Modbus Device? Are there any warnings or errors raised on the Modbus Device you are using?

Answered: Challenges in Simulating Shaded Photovoltaic IV Curves with Boost Converter in Typhoon HIL

Thu, 14 Aug 2025 06:18:19 +0000

Hi Igor,

The Normalized IV curve type is better suited for voltage and current scaling, because you can specify the values of open-circuit voltage Voc and short-circuit current Isc. The .ipv file format is more suitable in cases where you do not need to modify the data set imported from the CSV file.

In the Image 3 of a Normalized IV curve that you shared, the IV characteristic, which is colored in blue, is not monotonically decreasing. There are multiple voltage values that correspond to a single current value. Maybe that is the cause of the voltage oscillations you observed.

Perhaps you specified the voltage and power data sets in the CSV file instead of the voltage and current data sets, because the shape of the IV curve in Image 3 usually corresponds to a power-voltage curve with shading. The first column is your CSV file is used for voltage data points, and the second column is used for current data points.

For the solution with n modules, there is no support available to show a single IV curve for multiple modules connected in series using the preview functionality in SCADA.

Please find attached an example of a CSV file and the corresponding Normalized IV file for a shaded curve.

photovoltaic_panel_shaded.csv

photovoltaic_panel_shaded.ipvx

Core Coupling problem

Tue, 12 Aug 2025 06:44:12 +0000

I have two single-phase inverters to form a four-leg inverter, but when I use core coupling to add a boost converter to the DC bus, the system behaves as if it were open-circuited. The inverter's current is zero, and the bus voltage explodes. Without the core coupling, the system works, but only with HIL 604. I'd like to use it with 404. Does anyone have any suggestions?

Does Typhoon HIL support XCP protocol?

Tue, 05 Aug 2025 13:50:02 +0000

Yes. Typhoon HIL supports XCP over CAN and ETH.

Note: XCP over ETH and CAN is supported from version THCC 2025.4. While on previous THCC versions only XCP over CAN is supported.

XCP in the Typhoon HIL toolchain

XCP master is supported in the Typhoon HIL toolchain in HIL SCADA, via the Python library pyxcp, while the parsing and importing of the a2l file is supported via the Python library pya2l. XCP slave is not supported in the Typhoon HIL toolchain.

Attached below is an example HIL SCADA panel file, where you can open the widget properties and write the Python code you want to execute. For creating properly configurations, you should use xcp-profile utility to convert a legacy .json/.toml file:

xcp-profile convert -c <YOUR_FILE_NAME>.json -o pyxcp_conf.py

Then you can import the libraries and modules for XCP communication and other libraries.

import sys 
from time import sleep 
from pyxcp.cmdline import ArgumentParser 
from pyxcp.daq_stim import DaqToCsv, DaqList, DaqRecorder

To access additional Python scripts in your simulation, you will need to append the path for the script to the system path.

sys.path.append(“d:/path/to/python/file”)
from xcp_script import XCPclass, open_db_session, create_measurement_list, parse_csv

In order to parse the a2l file to retrieve the necessary information, the a2l file must be imported into an opened database. That database need to be open just once and you can do that by calling open_db_session() function before initializing anything:

db, session = open_db_session(a2l_file_path)

The general idea is to acquire data from a device (ECU or simulator), process the data (either online or offline), and then store it or handle it in different formats. A DAQ list is a collection of measurements and data points to be recorded during the DAQ process. The allocation and optimization of ODTs is done automatically by pyXCP. For demonstration, we initialize DAQ list as follows:

daq_list = [DaqList(
    name="test",
    event_num=2,
    stim=False,
    enable_timestamps=False,
    measurements=daq_measurements,
    priority=0,
    prescaler=1
)]

The data acquired can be stored in different formats:

CSV: For simple tabular data XMRAW:
A proprietary format for pyXCP to record raw DAQ data
Parquet, MDF, SQLite: Other formats available for processing and storing data

The measurement parameter should contain a list of the desired measurements for your DAQ process. To construct this list, you can simply create a list of measurement name and then call the create_measurement_list function. This function will automatically generate the compatible list of measurements that can be used in the measurements parameter.

measurement_names = ["channel_d", "TestDWord_501", "TestDWord_502", "TestWord_992", "TestWord_991", "TestWord_989"]
daq_measurements = create_measurement_list(measurement_names, session)

The flexible callback mechanism in pyXCP allows users to interact with the DAQ process in a more modular and customizable way using policies. This flexibility makes it easier for users to integrate DAQ functionality into their workflow according to their specific needs. Before initializing the master, first we need to initialize policy that we will use:

daq_parser = DaqToCsv(daq_list)

Then, we need to make an instance of ArgumentParser class which is used to set up the environment for running the DAQ process. Crete a master as follows:

ap = ArgumentParser()
with ap.run(policy=daq_parser) as xm:
    xcp = XCPclass(master=xm)

After that, you can use the functions defined in the pyxcp library (connect, disconnect, upload, download) to connect and get additional info about the slave device. For unlocking a slave resource, you can implement your own function as it is done in the XCP script attached below if you know the algorithm. Another option is to provide the DLL file for unlocking after calling the get_seed_and_unlock function.

Important note: If you wish to use the DLL method for unlocking the resource, you will need to modify the pyxcp_conf.py file, where you need to uncomment and set the custom_dll_loader parameter.

This part of code is an example of how to use the functions defined in pyxcp and implement the xcp_script. The function get_seed_and_unlock gets the XCP seed key and unlocks the specified resource.

xcp = XCPclass(master=xm)
timestamp_enable = False
conn = xm.connect()
mode_info = xm.getCommModeInfo()
gid = xm.getId(0x1)
status = xm.getStatus()
xm.synch()

xcp.get_seed_and_unlock(xm, 0x04, dll_path)
DAQ_proc_info = xm.getDaqProcessorInfo()
DAQ_res_info = xm.getDaqResolutionInfo()
DAQ_info = xm.getDaqInfo()
for i in range(0, len(DAQ_info["channels"])):
    DAQ_event_info = xm.getDaqEventInfo(i)
    upload_rcv = xm.upload(DAQ_event_info.eventChannelNameLength)

xcp.get_seed_and_unlock(xm, 0x01, dll_path)
scp = xm.setCalPage(0x83, 0, 0)

xcp.build_checksum_for_slave(xm, session)
xcp.set_mta_and_build_checksum(xm, session)
for i in range(0, DAQ_proc_info.maxEventChannel - 1):
    DAQ_event_info = xm.getDaqEventInfo(i)
    upload_rcv = xm.upload(DAQ_event_info.eventChannelNameLength)
pwm = xcp.get_measurement(xm, "PWM", session)
print(pwm)
pwm_filter = xcp.get_measurement(xm, "PWMFiltered", session)
print(pwm_filter)

value = 5
PWM_Level = xcp.get_characteristic_value(xm, "PWM_Level", session)
print(PWM_Level)

xcp.set_characteristic_value(xm, value, "PWM_Level", session)

PWM_Level = xcp.get_characteristic_value(xm, "PWM_Level", session)
print(PWM_Level)

daq_parser.setup()
daq_parser.start()
sleep(1)
daq_parser.stop()
session.close()
xm.disconnect()

get_measurement uploads the specified measurement value from slave to master. set_characteristic_value downloads the specified characteristic value from master to slave. get_characteristic_value uploads the specified characteristic value from slave to master.

Once the DAQ sequence is started, the results are stored in the .csv file in our example. You can parse that file using our custom function as follows:

data_dict = parse_csv("test.csv")
for i in range(len(data_dict)):
    print(data_dict[measurement_names[i]])

Example XCP scripts are attached. Feel free to adapt the scripts provided to your needs.

Example HIL SCADA panel file: SCADA_example

Example of config file: config_file_with_dll

Does Typhoon HIL support UDS on CAN protocol?

Tue, 05 Aug 2025 06:47:52 +0000

Yes, Typhoon HIL supports UDS on CAN protocol.

1. Introduction

The Unified Diagnostic Services (UDS) communication protocol is a standardized diagnostic protocol used in the automotive industry for communicating with and diagnosing electronic control units (ECUs) in vehicles. It can operate over Controller Area Network (CAN) bus, a widely-used communication network in modern vehicles.

Unified Diagnostic Services (UDS) is a client-server protocol commonly used in the automotive industry for diagnostic communication between a client (usually a diagnostic tool or tester) and a server (an electronic control unit or ECU within a vehicle). In this context:

Client: The client, typically a diagnostic tool or software application, initiates communication with the ECU by sending diagnostic requests and commands.
Server: The server, which is the ECU within the vehicle, responds to the client's requests, providing diagnostic information, performing actions requested by the client, and managing the internal functions of the ECU.

2. UDS in Typhoon HIL toolchain

UDS Client is supported in the Typhoon HIL toolchain in HIL SCADA, via the Python library udsoncan. Parsing and importing of CDD files is done with the Python library cantools. UDS Server is not supported in the Typhoon HIL toolchain.

Attached below is an example HIL SCADA panel file, where you can open the widget properties and write the Python code you want to execute.

First, import the libraries and modules for UDS communication and other libraries.

import isotp
import cantools
from udsoncan.connections import *
from udsoncan.client import Client
from udsoncan import DataIdentifier, IOValues
from udsoncan.configs import default_client_config
import os.path, os

To access additional Python scripts in your simulation, you will need to append the path for the script to the system path.

sys.path.append("d:/path/to/python/file")
from uds_script import UDSclass, create_config_dict

The CDD file plays a crucial role in defining the communication parameters and structure for diagnostic communication between a diagnostic tool (such as a scan tool or diagnostic tester) and the electronic control unit (ECU) within a vehicle. To load this file, we use the cantools library and the create_config_dict function:

database_uds_example = cantools.db.load_file(uds_example_path)
config = dict(default_client_config)
config = create_config_dict(database=database_uds_example, config=config)

To initialize the UDS Client we need to define the link layer, network layer, transport layer, and the interface between the application and transport layer:

bus = VectorBus(channel=0, bitrate=500000, app_name="UDSsim") - Link Layer (CAN protocol)
tp_addr = isotp.Address(isotp.AddressingMode.Normal_11bits, txid=0x700, rxid=0x600)- Network layer
stack = isotp.CanStack(bus=bus, address=tp_addr, params=isotp_params) - Network/Transport layer (IsoTP protocol)
conn = PythonIsoTpConnection(stack) - interface between Application and Transport layer

After we have created the connection layers and config parameters, we can create the UDS Client:

with Client(conn=conn, request_timeout=3, config=config) as client:

After that, we can use the functions defined in the udsoncan library (open, close, tester_present) to communicate with the server and get additional information.

Here is an example how to communcate with the server:

# Read and write data example for did = "Windows"
 uds.read_data(client=client, database=database_uds_example, did_ident=0x81)

 uds.write_data(client, database_uds_example, name="Windows", value=(0x04, 0x03, 0x02, 0x01))

 uds.read_data(client, database_uds_example, did_ident=0x81)

 uds.io_control_write(client, database_uds_example, name="Windows", values=(0x08, 0x07, 0x06, 0x05))

The read_data function reads the data from a specific ECU data identifier, while the write_data function writes data to a specific ECU data identifier.

An example UDS script is attached. Feel free to adapt the scripts provided to your needs.uds_script

uds_example

6-phase PMSM with single isolated neutral point

Fri, 01 Aug 2025 09:59:48 +0000

Hello,

Does anyone have the Typhoon model of PMSM (symmetrical or assymetrical) with a six-phase star-wound stator and single isolated neutral point?

KeyError: 'time_data_type' in stub.py when stop_capture() is called

Wed, 30 Jul 2025 08:23:45 +0000

Hi all,

I am going to use the start_capture() and stop_capture() functions from the Typhoon HIL API 1.30.0 and Typhoon Control Center 2023.3. Based on the code examples from documentation I prepared a small test to verify if it works as expected and got the following error:

    def recv_time_data(socket, flags=0, copy=False, track=True):

        """recv a numpy array or a dict with a numpy array and scalars"""

        # first receive a metadata as json

        md = socket.recv_json(flags=flags)

        print(md)

        # time data are sent as dictionary

>       if md["time_data_type"] == "dict":

           ^^^^^^^^^^^^^^^^^^^^

E       KeyError: 'time_data_type'

.venv\Lib\site-packages\typhoon\api\hil\stub.py:56: KeyError

I printed the md structure and it shows the following data:

[WARNING] [CAPTURE MESSAGE] stop_capture() will be ignored since desired number of samples are already captured!

{'dtype': 'float64', 'shape': [100000]}

so it is right that the key "time_data_type" does not exist.

Is this a bug in the HiL API or incompability issue?

After replacing the key: 'time_data_type' with 'dtype' it works as expected.

The code snipped I used for testing:

def test_typhoon_recorder():

    import typhoon.api.hil as typhoon_hil

    import time

    trigger_settings = ["Forced"]

    timeout = 2

    capture_settings = [10, 2, 1e5]

    channel_settings = [["TestOC.IaOCTest",

                        "TestOC.IcOCTest"], []]

    buffer = []

    typhoon_hil.set_text_mode(typhoon_hil.RM_SYSTEM)

    typhoon_hil.load_model(MODEL_NAME)

    typhoon_hil.load_settings_file(RUNX_SETTINGS)

    typhoon_hil.start_simulation()

    time.sleep(2)

    typhoon_hil.start_capture(

        capture_settings,

        trigger_settings,

        channel_settings,

        dataBuffer=buffer,

        timeout=timeout,

    )

    time.sleep(2)

    typhoon_hil.stop_capture()

    print(buffer)

    typhoon_hil.stop_simulation()