beautypg.com

Mapping controlnet data transfer – Rockwell Automation 1785-L20C_L40C, D17856.5.14 ControlNet PLC-5 Programmable Controllers User Manual User Manual

Page 37

background image

Chapter 2

Planning to Use Your ControlNet

PLCĆ5 Processor

2-9

Mapping ControlNet Data Transfer

The ControlNet I/O map table can contain up to 64 entries. Each map-
table entry corresponds to one transfer—either input or output—of data
between the ControlNet processor and an I/O rack, an I/O module, or
another ControlNet processor.

Table 2.D

Number of ControlNet I/O MapĆTable Entries Required

DataĆTransfer Type

Number of Entries Required

1771 Discrete I/O Data Transfer

1 per adapter

1771 NonĆdiscrete I/O Data Transfer

1 or 2 per module

1794 Discrete and NonĆdiscrete I/O Data Transfer

2 per adapter

ControlNet PLCĆ5 PeerĆtoĆpeer Communication

1 per message

Table 2.E

Files That You Configure with the I/O Map for Scheduled I/O Usage

File

Description

Status File

UserĆspecified integer dataĆtable file containing status information about all of the ControlNet network's scheduled I/O

mapĆtable entries. Each entry has a statusĆfile offset field pointing to three status words associated with the entry.

Data Input File (DIF)

UserĆspecified integer dataĆtable file with a maximum of 1000 words. This space is used for both nonĆdiscrete input data

and peerĆtoĆpeer input over the ControlNet network. Scheduled peerĆtoĆpeer inputs can also use the inputĆimage file.

Data Output File (DOF)

UserĆspecified integer dataĆtable file with a maximum of 1000 words. This space is used for both nonĆdiscrete output data

and peerĆtoĆpeer output over the ControlNet network. Scheduled peerĆtoĆpeer outputs can also use the outputĆimage file.

Default Configuration File

UserĆspecified integer dataĆtable file used to store nonĆdiscrete I/O data transfer configuration data when the automaticĆ

mapping feature is used.

Table 2.F

ControlNet I/O MapĆTable Entry Fields

MapĆTable Entry Field

Description

Node and Slot/Message Numbers

This is the entry's network location, currently defined as node.slot/message. The node value is the ControlNet

network address of the destination device. The slot/message value takes on different meanings with the

different communication options:

1771 and 1794 discrete I/O data transferĊthe slot value does not apply because the mapping granularity is

based on the physical chassis

1771 nonĆdiscrete I/O data transferĊ0Ć15, the slot number is always the physical slot location inside the

1771 chassis regardless of addressing mode within the chassis

1794 nonĆdiscrete I/O data transferĊ0Ć7, the slot number is always the physical location in the 1794 system

peerĆtoĆpeer communicationĊ1Ć16, the message number represents one of sixteen scheduled peer

messages available per processor; and it must be the same for both processors involved

Module/Message Type

This allows you to specify the module type or peerĆtoĆpeer message typeĊPeer Out or Peer InĊin offline and

online programming. It also determines how the mapĆtable entries are configured for the different modules and

peerĆtoĆpeer messages.

Expected Network Packet Time

(ENPT)

You set this to the maximum time allowed for the network to update the requested data.

Actual Network Packet Time (ANPT)

This readĆonly field displays the actual time it takes for the network to update the requested data.