Toshiba T300MVi - Manual (Page 47)

34
14.8.3 Ethernet/IP Port Configuration
The Ethernet/IP port has the following configuration parameters:
• Enable/Disable: Enables or disables this protocol.
•
Produced/Consumed Assembly Member Lists: These arrays allow the
creation of custom-built assembly instances. Each box in the array is
capable of containing a point number. Because the “value” attributes of
each point are 16-bit data elements, each box represents two bytes of
consumed or produced data.
Up to 100 points can be assigned to each member list (for a total of 200
bytes of produced and/or consumed data). The array locations are
numbered 0-99, and traverse from left to right across each row, and then
increment to the left-most position on the next row. Clicking on a box in an
array toggles the point that will be referenced when class 1 connected data
is produced or consumed at that corresponding location. A blank array
entry indicates that no point is referenced at that location, which will cause
corresponding consumed data to be ignored and produced data to be a
default value of 0.
As an example, looking at the member list definitions shown in Figure 23,
we can see that the Produced Assembly Member List contains 25 defined
points, and the Consumed Assembly Member List contains 10 defined
points. Therefore, up to 20 “meaningful” bytes of data can be consumed
and up to 50 “meaningful” bytes of data can be produced via class 1
connected messages (the qualifier “meaningful” is used here because a
client may configure a class 1 connection that indicates larger produced
and/or consumed data sizes, but all unreferenced consumed data (data
after byte #20) will be ignored, and all unreferenced produced data (data
after byte #50) will be dummy “0” values). The first word (two bytes) of
consumed data will be written to the “value” attribute of point #1, the next
two bytes to point #2 and so on. If points #1 and #2 etc. have a “Source
Port” selection defined (such as the ASD), then this command data will
subsequently also propagate to that port and down to the point’s
configured remote device.
This example works similarly when describing the behavior of the produced
member list in Figure 23. In this case, the first 2 bytes of the produced
data will be the value of point #11, the next two bytes will be the value of
point #12 and so on.