Export Ports Dialog

Ports are used to connect Transforms to each other and to MxVDev. To connect a port to MxVDev so it can be used as a Signal in TestCases, it must be exported.

Note: Input ports (inports) cannot be exported if they are already connected to another upstream port. You can, however, export the outport being fed to the inport.

Use the following procedure to export ports and their properties:

1.In MxTransIt, click the Transform to select it.

2.From the main menu, select Transform->Export Ports. (Alternatively, you can right-click on the Transform, and select Export Ports from the context menu.)
 
To sort the port names alphabetically, click the column header (Name or Alias).

ExportPorts

3.Check the ports to be exported.  Uncheck any ports you wish to unexport.

4.Click OK.

5.Repeat for all Transforms with ports to export.

6.Click Save to save the Harness (.mxform) file. MxVDev cannot connect to the ports (Signals) until this file is saved.

To view a list of exported ports, click the Exports tab at the bottom of the Properties box. If the Exports tab is not visible, select View->Exports from the MxTransIt main menu.

Exports_tab

Port Names

To avoid confusion, ports to be exported should have unique names.

You can use the Edit Signal Info or Edit Ports dialog to change port names, except for ports on User-Defined Transforms including Custom Transforms.

Ports on User-Defined Transforms are defined in the C code attached to the Transform. Any change to their names should be made in the attached MSVC project.

You can use the PassThru transform or an alias to access a signal by another name without changing the name of the port itself.

Properties

When you export a port from MxTransIt, its associated properties are also exported. However, if the Signal is already in the MxVDev Signal Dictionary, the Connecting Signals dialog enables you to control if the properties are imported into the MxVDev Signal Dictionary.

This is an intentional behavior that allows you to set properties in the MxVDev Signal Dictionary that are different from those set in MxTransIt. For example: Mx Transit could have the device's physical limits while a TestCase could use tighter operating range limits.

To ensure that all property values are the same in MxVDev and MxTransIt, you can delete the entire Signal Dictionary (.mxd) file and reexport the ports. This removes any modifications or Signals entered directly into the Signal Dictionary.

 

Related Topics:

Connecting Signals

Editing Ports (includes Port Properties)

Getting Started Video Demonstration