Import/Export Attribute Configuration Mapping Behavior

When importing and exporting configurations between NI-DCPower sessions that are initialized with different channels, the configurations of the exporting channels are mapped to the importing channels based on the order of the resources you specify in the resource name input to the Initialize With Independent Channels node for each session.

Note NI-DCPower returns an error if the total number of channels initialized for the exporting session is not equal to the total number of channels initialized for the importing session. However, as long as the number of initialized channels is equal between sessions, you can export and import configurations between any number of physical instruments. For each channel mapping created, NI-DCPower checks that the model of an exporting instrument channel matches the model of the importing instrument channel.

In general, NI-DCPower configurations are mapped between channels in the exporting and importing sessions as follows.

Table 3. NI-DCPower Configuration Mapping Between Channels
Case Resource(s), Exporting Session Resource(s), Importing Session Configuration Exported From Imported To
Single physical instrument per session PXI1Slot3/0-1 PXI1Slot4/1-2 PXI1Slot3/0 PXI1Slot4/1
PXI1Slot3/1 PXI1Slot4/2
>1 physical instrument in either session, equal numbers PXI1Slot4/3,PXI1Slot5/3 PXI1Slot2/0,PXI1Slot3/0 PXI1Slot4/3 PXI1Slot2/0
PXI1Slot5/3 PXI1Slot3/0
>1 physical instrument in either session, export to fewer PXI1Slot4/3,PXI1Slot5/3 PXI1Slot3/0-1 PXI1Slot4/3 PXI1Slot3/0
PXI1Slot5/3 PXI1Slot3/1
>1 physical instrument in either session, export to more PXI1Slot3/0-1 PXI1Slot4/3,PXI1Slot5/3 PXI1Slot3/0 PXI1Slot4/3
PXI1Slot3/1 PXI1Slot5/3

Instrument-based properties that are exported and imported between sessions are mapped in the same manner according to channel order at the instrument level rather than at the channel level.

Import/Export Mapping Exceptions

Some properties have unique import/export mapping behavior.

For the Merged Channels property, only the instrument name is remapped, not the channel name. For example, when importing the value PXI1Slot2/0 to a session on PXI1Slot3/1, the configuration is remapped to PXI1Slot3/0.

Mapping Behavior for Fully Qualified Terminal Names

When you export and import configurations that include properties that accept string-type fully qualified terminal names, the terminal names are mapped based on additional criteria specific to terminal names.

These criteria include:

  • Whether the Engine number you specify matches the number of its corresponding channel
  • Whether you specify the Engine number at all
  • Whether the instrument alias specified for a terminal matches an instrument alias belonging to the session

Unqualified terminal names are not mapped.

Fully qualified terminal names are mapped according to the following general patterns:

Table 4. Mapping Behavior for Fully Qualified Terminal Names
Case Instrument Aliases, Exporting Session Instrument Aliases, Importing Session Terminal Name Value, Exporting Session Mapped Terminal Name in Importing Session
Equal number of physical instruments per session Dev1/0,Dev2/0 Dev3/1,Dev4/1 /Dev1/PXI_Trig0 /Dev3/PXI_Trig0
/Dev2/PXI_Trig3 /Dev4/PXI_Trig3
/Dev1/Engine0/MeasureTrigger /Dev3/Engine1/MeasureTrigger
/Dev2/Engine0/MeasureTrigger /Dev4/Engine1/MeasureTrigger
/Dev1/Engine5/MeasureTrigger /Dev3/Engine5/MeasureTrigger
Engine0/MeasureTrigger Engine0/MeasureTrigger
/Dev5/Engine0/MeasureTrigger /Dev5/Engine0/MeasureTrigger
>1 physical instrument in either session, export to fewer Dev1/0,Dev2/0 Dev3/0-1 /Dev1/PXI_Trig0 /Dev3/PXI_Trig0
/Dev2/PXI_Trig3 /Dev3/PXI_Trig3
/Dev1/Engine0/MeasureTrigger /Dev3/Engine0/MeasureTrigger
/Dev2/Engine0/MeasureTrigger /Dev3/Engine1/MeasureTrigger
/Dev1/Engine5/MeasureTrigger /Dev3/Engine5/MeasureTrigger
Engine0/MeasureTrigger Engine0/MeasureTrigger
/Dev5/Engine0/MeasureTrigger /Dev5/Engine0/MeasureTrigger
>1 physical instrument in either session, export to more Dev1/0-1 Dev2/0,Dev3/0 /Dev1/PXI_Trig0 /Dev2/PXI_Trig0
/Dev1/PXI_Trig3 /Dev2/PXI_Trig3
/Dev1/Engine0/MeasureTrigger /Dev2/Engine0/MeasureTrigger
/Dev1/Engine1/MeasureTrigger /Dev3/Engine0/MeasureTrigger
/Dev1/Engine5/MeasureTrigger /Dev2/Engine5/MeasureTrigger
Engine0/MeasureTrigger Engine0/MeasureTrigger
/Dev5/Engine0/MeasureTrigger /Dev5/Engine0/MeasureTrigger