General principle

EcoStruxure Machine Expert Projects

There are two ways to engineer a C2C network with EcoStruxure Machine Expert:

oEach PacDrive LMC has its own EcoStruxure Machine Expert project. Each of those projects has a static configuration.

oThere is one, shared EcoStruxure Machine Expert project for the different PacDrive LMCs of the C2C network. This project has a dynamic configuration.

The assignment between producer and consumer takes place via the ID of the objects exchanging the real time data (C2C Data Input, C2C Data Output, C2C Encoder Input, C2C Encoder Output).

NOTE: When assigning the ID, verify that only data objects with the same type are assigned. This means, do not assign, for example, a C2C Data Output object to a C2C Encoder Input object using the same ID.

In addition, verify that objects with the same ID have the same data size.

General Principle

oThe C2C network can transmit encoder signals (C2C Encoder Input, C2C Encoder Output) and arbitration data (C2C Data Input, C2C Data Output).

oBoth C2C Master and C2C Slave can be producer and consumer of data in the C2C network.

oFor each data object, there is one producer and there can be several consumers.

The producer object (for example, C2C Encoder Output object) and consumer objects (for example, C2C Encoder Input object) are linked through the same ID.

oEncoder signals are velocity signals (transmitted as increment values) that can be sent and read the master and slave objects.

oIf, for example, the master is sending/producing an encoder output signal (C2C Encoder Output), the reader/consumer (for example, the slave) must have a corresponding input object (C2C Encoder Input).

The exchange of the user data (C2C Data Input, C2C Data Output) is handled in the same way.