NETLink PRO ETH
37
These two addressing methods, which are mutually exclusive, permit most
types of communication that are also possible via the NETLink-S7-NET.
8.1.4.1 Addressed mode
If different CPUs are to be accessed on the same MPI/PROFIBUS via
RFC1006, addressed mode is suitable.
If this mode is used, the following setting must be parameterized on the
configuration page of the Web interface:
•
‘Rack/slot mode’
must be deactivated (OFF)
Addressed Mode is active
The destination address now has to be entered in the RFC1006 driver of the
Windows application (e.g. WinCC, see Section 8.2.1) instead of the rack and
slot.
Please note that the rack and slot together fill only one byte which is divided
as follows:
•
Rack fills the upper three bits
(11100000
bin
for Rack 7, Slot 0)
•
Slot fills the lower five bits
(00011111
bin
for Rack 0, Slot 31)
If you now want to communicate with destination address 2, the following
has to be entered:
Rack 0, Slot 2.
If you want to communicate with destination address 49, on the other hand,
the following has to be set:
Rack 1, Slot 17.
Section 10.3.1 contains a table were you can read off already converted
values for the rack and slot.
There are also parameterization tools that do not provide fields with names
like rack and slot. These tools normally have a parameterization field with a
name such as Remote TSAP that is usually two bytes long and in hex format.
This field, in which only the lower byte is of interest, is parameterized as
follows:
If you want to communicate with destination address 2, the following has to
be entered:
Remote TSAP 0202
hex
.
If you want to communicate with destination address 49, on the other hand,
the following has to be set:
Remote TSAP 0231
hex
.
Section 10.3.1 contains a table were you can read off already converted
values for the Remote TSAP.
To simplify you can use the formula
Rack * 32 + Slot = address
.
8.1.4.2 Rack/slot mode
In rack/slot mode, it is possible to access specific modules of the automation
system.
