Frequently Asked Question
Press "Ctrl + F" to find the keyword of your interest.
If you wish to have a direct link access to the video timestamps, please follow these instructions.
Found this video helpful? Why not take the whole HIL Specialist course? A Certificate is waiting for you for free at HIL Academy.
Would you or your organization benefit from having these videos narrated in your native language? Contact us and let us know if you wish to contribute.
TRANSCRIPT
In this lesson, we will cover electric circuit partitioning across devices. We will continue
with the Device partitioning how-to example in the Example Explorer that we set up in the previous
lesson on Device Partitioning Components.The first critical element for this type of
model partitioning is the Device Marker. When we have a Multi-HIL setup, we need to have a
device marker within the model. Device markers are used only in Multi HIL setups, as we covered
in the previous lesson. Device markers are used to specify which part of the entire circuit is
going to be emulated on which of the HIL devices in the system. Configurations of HILs connected
in parallel can be different, which we can set in the Hardware settings tab of device markers.
You can find the Device marker component in the Schematic Editor Library Explorer, in Model
Partitioning, Device Partitioning, Electrical.
A Device marker component should be used to set
up each HIL device in a Multi-HIL setup. As you can see in this example, the model is divided
into three sub-circuits. The two circuits are divided using Device coupling elements,
while the third circuit is independent.In the Device marker properties you can find
the HIL device ID combo box. This parameter defines in which device the marked part of the
circuit is going to be compiled. Also, there is an option to override global hardware settings.
If checked, the Hardware configuration ID set in the Device marker will override the
globally set Hardware configuration ID.Circuit solver settings are set globally
in Schematic settings, but they can be overridden locally for each device in
a Multi-HIL setup. This is done by checking the Override global solver settings checkbox.
You can find more information about properties in the documentation link in the Materials tab.
Signal processing settings are also set globally in Schematic settings,
but they can be overridden locally for each device in a multi-HIL system.
This is done by checking either the Override global solver settings or Override
global user SP settings checkboxes.The second mandatory component type that
we use during device partitioning are Device Coupling components.
Device coupling components are ideal transformers with a transfer ratio of one.
They are used to partition the complete power electronics circuit into separate
circuits that are emulated on different HIL devices. These components are only used in
multi-HIL configurations where HIL devices are paralleled. Device coupling components define
the communication variables between HIL devices to be exchanged over High Speed Serial Link or HSSL.
This ideal transformer block introduces a variable time delay approximately 2
timesteps of a simulation between measured variables and corresponding controlled sources,
which is negligible for most practical systems. This delay
depends on the amount of data that has to be transmitted through HSSL.
Device coupling elements consist of current side and voltage side snubbers,
just like core coupling elements. You can find out more about core coupling elements in the
Core partitioning components lessons.Also similar to core coupling elements,
several components support embedding Device partitioning elements. In particular,
transformers are usually perfect components for embedding Device coupling components.
You can find the list of all components with embedded device couplings in the Materials tab.
Device coupling components are found in the Library Explorer in Model Partitioning,
Device Partitioning, Electrical.
As you can see, TLM device partitioning is also available.
For more information about TLM couplings in general, check out the Core partitioning
lessons. Core and Device TLM couplings are based on the same principles.
In the next lesson, we will look into signal processing coupling across devices.
