Schneider Electric DS301 manual COB ID with function code and node address

Page 22

3 Basics

IL•1F CANopen DS301

CAN message Data is exchanged via the CAN bus in the form of CAN messages. A CAN message transmits the communication object and a variety of ad- ministration and control information.

CAN message

1

11

1

6

 

 

 

0..8 Byte

16

 

 

1

1

1

7

 

 

>=3

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Data

 

CRC

 

 

 

 

 

End-Bits

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Acknowledge

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Control

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

RTR-Bit

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Identifier

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Start-Bit

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

COB-ID

 

 

 

 

 

 

data carrier

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

11 Bit

 

0..8 Byte

 

 

 

 

 

 

4 Bit

7 Bit

0

1

2

3

4

5

6

7

CANopen message (simplified)

 

 

 

 

 

 

Figure 3.5 CAN message and simplified representation of CANopen mes- sage

CANopen message For work with CANopen objects and for data exchange, the CAN mes- sage can be represented in simplified form because most of the bits are used for error correction. These bits are automatically removed from the receive message by the data link layer of the OSI model, and added to a message before it is transmitted.

The two bit fields "Identifier" and "Data" form the simplified CANopen message. The "Identifier" corresponds to the "COB ID" and the "Data" field to the data frame (maximum length 8 bytes) of a CANopen mes- sage.

COB ID The COB ID (Communication OBject Identifier) has 2 tasks as far as controlling communication objects is concerned:

Bus arbitration: Specification of transmission priorities

Identification of communication objects

An 11 bit COB identifier as per the CAN 3.0A specification is defined for CAN communication; it comprises 2 parts

Function code, 4 bits

Node address (node ID), 7 bits.

Bit:10

 

 

 

 

 

 

 

 

 

 

 

0

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

COB-ID

1

 

2

3

 

4

1

2

3

4

5

6

7

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Function code

 

 

 

Node-ID

 

 

 

 

 

 

0...15

 

 

 

 

0...127

 

 

 

 

Figure 3.6 COB ID with function code and node address

0198441113586, V2.01, 11.2008

22

Fieldbus interface

Image 22
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 About this manual IntroductionCAN-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 CANopen description language BasicsCANopen technology Communication layersObjects Index hex Object groups Supported By the driveIL1F CANopen DS301 Basics CANopen profiles CANopen reference modelObject dictionary Communication profileIndex 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 Overview Service data communicationSDO 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 controlInitialization NMT service Transition MeaningPersistent data memory Command Specifier NMT service Transition NMT services for connection monitoringNode/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 deviceAddress and baud rate Starting fieldbus modeCommissioning the fieldbus network Troubleshooting Error Error class Cause of error TroubleshootingCreating a new network SyCon CANopen configuration softwareSelecting the CANopen master Setting the bus parameters Selecting and inserting nodes Operation OverviewOperation IL1F CANopen DS301 Transmit data Using SDO commandsWriting parameters Receive dataReading a parameter Synchronous errorsIndex Sub Data Description Changing operating states with PDO4 Operating Name Power Description State StageBit no Value Meaning Triggering a Quick Stop Switching the power stage on and offExample 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 diagnosticsMessage objects Error diagnostics via fieldbusMessages on the device status Error code table CANopen error messagesError register Bit Message MeaningSDO error message Abort Error code MeaningObject code Meaning Coding Specifications for the objectsObject directory Data type Value range Data lengthIndex Subindex Designation Obj. code Data type Access Objects, overviewObjects of the product Error registerDevice type Manufacturer device name Bit coding, subindex 00h1008h 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 coding, subindex 02h Bit assignment subindex 01hBit 30 RTR bit 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 tablesTorque TemperatureRotation 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