NETLink PRO ETH
47
triggered. The support team will attempt to solve the problem as quickly as
possible.
Q: Every time I execute a certain function, it fails and the red Connect LED
flashes.
A: It is an exception in the communication between the programmable
controller and the NETLink PRO ETH. Please contact support and describe
how the error can be triggered. The support team will attempt to solve the
problem as quickly as possible.
Q: Although the NETLink PRO ETH is plugged directly into my CPU and
no further nodes are connected, MPI and PROFIBUS connections sometimes
break down at high baudrates.
A: Make sure that the bus is correctly terminated.
Even if the NETLink PRO ETH is the only device on the bus apart from the
CPU, the terminating resistor must be connected. Otherwise problems may
occur, especially at high baudrates.
Q: If I set the NETLink PRO to autobaud in the PG/PC interface and try to
go online, the active LED lights up briefly before a message appears telling
me that the bus parameters cannot be determined.
A: Either the CPU used does not support the cyclic transmission of bus
parameters (disabled via parameterization or function does not exist), or the
CPU is so busy with general communication tasks that the lower-priority bus
parameter telegram is transmitted too infrequently and cannot be detected by
the NETLink PRO.
Please deactivate the autobaud functionality in the NETLink PRO driver
(PG/PC interface) and set the correct baudrate and the correct profile.
Q: In the Web interface, I enabled the RFC1006 functionality and would like
the NETLink PRO ETH to go onto the bus using autobaud.
Unfortunately, the active LED just flashes but no communication is possible
via my visualization system.
A: Either the CPU used does not support the cyclic transmission of bus
parameters (disabled via parameterization or function does not exist), or the
CPU is so busy with general communication tasks that the lower-priority bus
parameter telegram is transmitted too infrequently and cannot be detected by
the NETLink PRO.
Please deactivate the autobaud functionality in the Web interface of the
NETLink- PRO and set the correct baudrate with the corresponding bus
parameters.
Q: I read that the NETLink PRO ETH can communicate with up to seven
PCs at the same time. But I can’t manage to query a status of my automation
system from more than six PCs at once.
A: A total of seven TCP links are available that can be used at the same time.
However, please note that only up to six links can be used at once per type of
connection (NETLink PRO or RFC1006 connections are possible). The
purpose of this is to keep one connection channel free for the other protocol.
6+1 or 5+2 or 4+3 or 3+4 or 2+5 or 1+6 links are available for the two types
of protocols.
