![Anybus Communicator - CANopen Скачать руководство пользователя страница 21](http://html1.mh-extra.com/html/anybus/communicator-canopen/communicator-canopen_user-manual_2948751021.webp)
CAN Network Communication
16
Doc.Id. SCM-1200-121
Anybus Communicator CAN to CANopen
Doc.Rev. 1.00
4.2.2 Produce and Consume
When using these messages, there is no master-slave relationship between the Communicator and the
nodes on the subnetwork. Any node, including the Communicator, may spontaneously produce a mes-
sage. The message is sent on the network. The nodes on the network listen to all traffic and decide in-
dependently which messages to consume (read). Nodes do not have to respond to messages, nor do they
have wait for a query to send a message on the network.
In the figure above, the Communicator ‘consumes’ data that is ‘produced’ by a node on the subnetwork.
This ‘consumed’ data can then be accessed from the higher level network. This also works the other way
around; the data received from the higher level network is used to ‘produce’ a message on the subnet-
work to be ‘consumed’ by a node.
Note
: When configuring the Communicator using the Anybus Configuration Manager, ‘produce’ and
‘consume’ are defined from the Communicator’s perspective.
4.3 Protocol Building Blocks
The following building blocks are used in Anybus Configuration Manager to describe the subnetwork
communication. How these blocks apply to the two modes of operation will be described later in this
document.
• Group
A group in the Anybus Configuration Manager does not represent any special device on the CAN
network. It is a means to structure the transactions that are defined for the Communicator. Each
group can be associated with a number of transactions, see below.
• Transaction
A transaction consists of one or more CAN frames. Each transaction is associated with a set of
parameters controlling how and when to use it on the subnetwork. There are three kinds of trans-
actions: produce, consume and query-response. A group can contain transactions of all three
types. A total of 128 transactions can be configured.
• CAN Frames
The CAN frames are low level entities used to compose transactions (see above). Each frame
carries an 11-bit or 29-bit identifier and can hold up to 8 bytes of data. See “Configuration of
CAN Frames” on page 33. A total of 256 CAN frames can be configured.
Node 1
Node 2
Node 3
Subnetwork Devices
Control System
Communicator