Right click on the logical network and left click on the Link Structure Libraries… option to view or assign which .xml files define the assemblies used in the network. Expand the assembly definitions on the right to see the data transferred on the network.
Figure 9.71. XML File Links
Library File lists the names of the XML files linked to the workspace's network.
Description provides a meaningful description of the library.
Remove selected included libraries from usage.
Apply changes to the selections with the Apply button.
Finalize any changes with the Close button.
Ethernet/IP Network Usage
Figure 9.74. Link Structures to the Network via an XML file
The model for Ethernet/IP moves blocks of data from point A to B by defining those blocks of data into Assemblies. Design Pad implements assemblies as lines added to an XML file which designate a name for a message. The structure definition contains a reference to a Design Pad schema structure which defines the data to be moved. The XML file may also contain Classes which describe virtual data packages. Physical instances of these packages are instantiated by object operators.
NIM-2s are mapped to these XML files via the Structure Library Links dialog in Figure 9.75*.*. Access this dialog by right clicking on the logical network name in the Workspace Network View. Add a file by specifying its name in the browse dialog and the XML file's contents will be displayed on the right side of the Links dialog. The XML structure definition for the structures in XXX follows:
<LIBRARYFILE Name="RF Controller">
<LIBRARY Name="RF_Controller">
<STRUCTURE Name="PID_Gain_Struct">
<FLOAT Name="f_Kc"/>
<FLOAT Name="f_Ti"/>
<FLOAT Name="f_Td"/>
</STRUCTURE>
<STRUCTURE Name="RF_Controller_Struct">
<FLOAT Name="f_State"/>
<FLOAT Name="f_SetPoint"/>
<FLOAT Name="f_Temperature"/>
<FLOAT Name="f_FanSpeed"/>
<BOOL Name="b_EStop"/>
<Structure Name="PID_Gains", Data="PID_Gain_Struct">
</Structure>
</STRUCTURE>
<STRUCTURE Name="Filler_Struct">
<FLOAT Name="Spare"/>
</STRUCTURE>
<STRUCTURE Name="E_Stop_Ind">
<U16 Name="PackedBits"/>
</STRUCTURE>
<EIPASSEMBLY Name="RF_Contrlr" Data="RF_Controller_Struct"/>
<EIPASSEMBLY Name="Spare" Data="Filler_Struct"/>
<EIPASSEMBLY Name="RF_RemDisp" Data="E_Stop_Ind"/>
</LIBRARY>
</LIBRARYFILE>
Figure 9.75. Structure Library Link Add Dialog
Figure 9.76. Structure Library Link After .xml File Applied
Use the linked assemblies by right clicking on the NIM-2 in the hardware interface file and selecting Module Properties. Select Assemblies near the middle of the list to the left. The Assemblies (XXX) dialog appears, allowing selection of assemblies to be input (read) by the client or output (written) to the server
Figure 9.77. Input Assemblies
Figure 9.78. After an Assembly is Selected
Implement the data traffic represented by the assembly definitions in a schema through the use of Assembly operators. Left double click on the operator to indicate whether it reads (Consumer) or writes (Producer) the data. Assembly operators only accept structures as variables, so data must be packaged into structures which map to the assembly definition.
Next, right click on the assembly operator to connect it to a network operation. Select the input or output assembly the operator is to read or write and press OK (Figure 9.79).
Figure 9.79. Select a Network Resource for a Producer Assembly Operator
