Product overview
EL6601, EL6614
25
Version: 4.2
Process data:
• "CycleIdx": must be served by the application in order to be evaluated on the subscriber side
• "CycleIndex": CycleIdx counterpart on the subscriber side.
• "VarData": the data to be sent.
2.5.3
Notes
• The RT statistics displays are not supported under TwinCAT for an EL66xx-RT device.
Solution:
As an alternative, corresponding CoE parameters can be read for diagnostic purposes.
• The publisher features of "OnChangeOnly" and "DataExchange (divider/modulo)" are not supported
together with the EL66xx.
Solution:
[from FW08] Transmitting the configured publisher variables can be cyclically suppressed by
DevCtrl.
• If a publisher is set up on an EL66xx, the publisher's
must be taken care of by the
user. On a PC, on the other hand, they are incremented by TwinCAT.
• The following is recommended for diagnosis of a network variable connection:
1. Monitor the link status in the "
DevState
" of the RT device (Device --> Inputs --> DevState). The
expected state is
DevState
= 0.
2. Monitor the
Quality
and
CycleIndex
in the subscriber.
• The link LED in the EL66xx only indicates the status of the cable connection, not that of any network
variable connection that may exist.
• If the EL66xx is used exclusively to transfer network variables,
deactivated.
• A maximum of 32 for each, publishers and subscriber, are permitted per EL66xx.
2.5.4
Suppress publisher
Applicable: TwinCAT from version 2.11, EL6601 from FW08, EL6614 from FW04
If the EL66xx is operated with a short cycle time and with publishers configured, this can place a high loading
on the connected network. For this reason, the EL66xx can be configured in such a way that the
transmission of individual publishers can be blocked through the
DevCtrl
variable. The object 0xF800:02
must be occupied in the CoE (CanOpenOverEtherCAT) for this purpose.
Groups of publisher boxes can be blocked by setting appropriate bits (publisher frames). The topmost 4 bits
(the high nibble of high byte) from 0xF800:02 specify the granularity of the groups 1..15, i.e. how many
publisher frames are handled together as one group:
The upper 8 bits of
DevCtrl
(format: 16 bits) then block the transmission of the publisher frames located in
the corresponding group in the current cycle.
High byte of
DevCtrl
:
• 0 = no blocking
• n = each bit in
DevCtrl
corresponds to a group of n publishers, where n has a value in the range [1..31]
It follows that a maximum of 8 groups of publishers can be blocked.
Sample:
DevCtrl.10 = true and 0xF800:02 = 0x2000 signifies that the third group will be blocked in this PLC cycle.
One group consists of 2 publisher frames, which means that in this case all the publisher variables that are
located in publisher frames 5 and 6 will not be transmitted.
