Schneider Electric DS301 manual Communication relationships, Master slave relationships

Page 24

3 Basics

IL•1F CANopen DS301

Example Selection of a COB ID

For a device with the node address 5, the COB ID of the communication object T_PDO1 is:

384+node ID = 384 (180h) + 5 = 389 (185h).

Data frame The data frame of the CANopen message can hold up to 8 bytes of data. In addition to the data frame for SDOs and PDOs, special frame types are specified in the CANopen profile:

•Error data frame

•Remote data frame for requesting a message

The data frames contain the respective communication objects.

3.2.3Communication relationships

CANopen uses 3 relationships for communication between network de- vices:

•Master-slave relationship

•Client-server relationship

•Producer-consumer relationship

Master-slave relationship A network master controls the message traffic. A slave only responds when it is addressed by the master.

The master-slave relationship is used with network management ob- jects for a controlled network start and to monitor the connection of de- vices.

	Slave
Master	Slave
	data
	Slave
	request
Master	Slave
	data

Figure 3.7 Master - slave relationships

Messages can be interchanged with and without confirmation. If the master sends an unconfirmed CAN message, it can be received by a single or by several slaves or by no slave.

To confirm the message, the master requests a message from a specific slave, which then responds with the desired data.

0198441113586, V2.01, 11.2008

24	Fieldbus interface

Image 24

Contents IL1F CANopen DS301 Important information Table of Contents Table of Contents IL1F CANopen DS301 Object directory Table of Contents IL1F CANopen DS301 Writing conventions and symbols Writing conventions and symbols IL1F CANopen DS301 Introduction About this manualCAN-Bus Operating modes and functions in fieldbus mode Fieldbus devices networked via can busDocumentation and literature references Can users and manufacturers organizationIntroduction IL1F CANopen DS301 Before you begin safety information Before you begin safety information IL1F CANopen DS301 Basics CANopen technologyCANopen description language Communication layersObjects Index hex Object groups Supported By the driveIL1F CANopen DS301 Basics CANopen profiles CANopen reference modelCommunication profile Object dictionaryIndex Subindex Object Meaning Index range Object groups Supported Hex By the drive Communication objects Communication objectsCOB ID with function code and node address TPDO4 Communication relationships Master slave relationshipsClient-server relationship Service data communication OverviewSDO data exchange SDO message 11 SDO message, exampleReading and writing data Message type Data length used Bytes14 Reading a parameter value Message type Data length used Byte Bytes15 Response with error message error response Process data communication PDO data exchange 16 PDO data exchangeUINT32 Dynamic and static PDO mapping 18 Requesting a message with RTR =Receive PDO RPDO4 master slave Structure of RPDO4State machine drivectrl Operating modes modeCtrl JOG@ Warning Transmit PDO TPDO4 product to masterStructure of TPDO4 20 Structure of TPDO4Handshake with Mode Toggle Bit Bit Name Description22 Mode Toggle Handshake, short movement Master Slave XendBasics IL1F CANopen DS301 Emergency service 23 Error message with the Emcy objectSynchronization 25 Sync message27 Cyclic and acyclic transmission Network management services NMT services for device controlNMT service Transition Meaning InitializationPersistent data memory NMT services for connection monitoring Command Specifier NMT service TransitionNode/Life guarding 31 Acknowledgement of the NMT slave 32 Node Guarding and Life Guarding with time intervals Installation Installation IL1F CANopen DS301 Commissioning Commissioning the deviceStarting fieldbus mode Address and baud rateCommissioning the fieldbus network Troubleshooting Error Error class Cause of error TroubleshootingSyCon CANopen configuration software Creating a new networkSelecting the CANopen master Setting the bus parameters Selecting and inserting nodes Operation OverviewOperation IL1F CANopen DS301 Using SDO commands Writing parametersTransmit data Receive dataSynchronous errors Reading a parameterIndex Sub Data Description Operating Name Power Description State Stage Changing operating states with PDO4Bit no Value Meaning Switching the power stage on and off Triggering a Quick StopExample Come to a standstill System is to resume opera Resetting faults Examples for the operating modes with PDO4 Operating mode Profile Position absolute positioning Operating mode Profile Position relative positioning Operating mode Profile VelocityPosition setting Master --- SlaveOperating mode Homing Error signaling via PDO4 Asynchronous errorsPositioning running xerr=0 Operation IL1F CANopen DS301 Diagnostics and troubleshooting Fieldbus communication error diagnosticsError diagnostics via fieldbus Message objectsMessages on the device status CANopen error messages Error registerError code table Bit Message MeaningSDO error message Abort Error code MeaningSpecifications for the objects Object directoryObject code Meaning Coding Data type Value range Data lengthIndex Subindex Designation Obj. code Data type Access Objects, overviewError register Objects of the productDevice type Bit coding, subindex 00h 1008hManufacturer device name 100ChIndex 100D h Object name Life time factor Object code Index 1018 h Object name Identity Object Object code Data type PDO Communication parameter Bit assignment subindex 01h Bit 30 RTR bitBit coding, subindex 02h Bit Acces Value Meaning1603h Receive PDO4 mapping Value description 1803h Transmit PDO4 communication parameter BitMeaningSubindex 03 h, inhibit time TPDO4 Meaning IL1F CANopen DS301 Object directory PDO4 mapping 1603h Glossary Units and conversion tablesTemperature RotationTorque Moment of inertiaDefault value Factory setting Terms and AbbreviationsPower amplifier See power stage Index CanIndex IL1F CANopen DS301 IL1F CANopen DS301 Index NMT IL1F CANopen DS301 Index 102 Fieldbus interface