Schneider Electric DS301 manual Basics, CANopen technology, CANopen description language

Page 15

IL•1F CANopen DS301

3 Basics

0198441113586, V2.01, 11.2008

3 Basics

3.1CANopen technology

3.1.1CANopen description language

CANopen is a device- and manufacturer-independent description lan- guage for communication via the CAN bus. CANopen provides a com- mon basis for interchanging commands and data between CAN bus devices.

3.1.2Communication layers

CANopen uses the CAN bus technology for data communication.

CANopen is based on the basic network services for data communica- tion as per the ISO-OSI model model. 3 layers enable data communica- tion via the CAN bus.

•Physical Layer

•Data Link Layer

•	Application Layer
	device communication
	application Layer
	data Link Layer
	physical Layer
	fielb bus communication
	CAN-Bus

Figure 3.1 CANopen layer model

Physical Layer The physical layer defines the electrical properties of the CAN bus such as connectors, cable length and cable properties such as bit-coding and bit-timing.

Data Link Layer The data link layer connects the network devices. It assigns priorities to individual data packets and monitors and corrects errors.

Application Layer The application layer uses communication objects (COB) to exchange data between the various devices. Communication objects are elemen- tary components for creating a CANopen application.

Fieldbus interface

15

Image 15

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 Fieldbus devices networked via can bus Operating modes and functions in fieldbus modeCan users and manufacturers organization Documentation and literature referencesIntroduction IL1F CANopen DS301 Before you begin safety information Before you begin safety information IL1F CANopen DS301 Communication layers BasicsCANopen technology CANopen description languageIndex hex Object groups Supported By the drive ObjectsIL1F CANopen DS301 Basics CANopen reference model CANopen profilesCommunication 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 Master slave relationships Communication relationshipsClient-server relationship Service data communication OverviewSDO data exchange 11 SDO message, example SDO messageMessage type Data length used Bytes Reading and writing dataMessage type Data length used Byte Bytes 14 Reading a parameter value15 Response with error message error response Process data communication 16 PDO data exchange PDO data exchangeUINT32 18 Requesting a message with RTR = Dynamic and static PDO mappingStructure of RPDO4 Receive PDO RPDO4 master slaveState machine drivectrl JOG Operating modes modeCtrlTransmit PDO TPDO4 product to master @ Warning20 Structure of TPDO4 Structure of TPDO4Bit Name Description Handshake with Mode Toggle BitMaster Slave Xend 22 Mode Toggle Handshake, short movementBasics IL1F CANopen DS301 23 Error message with the Emcy object Emergency service25 Sync message Synchronization27 Cyclic and acyclic transmission NMT services for device control Network management servicesNMT 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 the device CommissioningStarting fieldbus mode Address and baud rateCommissioning the fieldbus network Error Error class Cause of error Troubleshooting TroubleshootingSyCon CANopen configuration software Creating a new networkSelecting the CANopen master Setting the bus parameters Selecting and inserting nodes Overview OperationOperation IL1F CANopen DS301 Receive data Using SDO commandsWriting parameters Transmit 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 Velocity Operating mode Profile Position relative positioningMaster --- Slave Position settingOperating mode Homing Asynchronous errors Error signaling via PDO4Positioning running xerr=0 Operation IL1F CANopen DS301 Fieldbus communication error diagnostics Diagnostics and troubleshootingError diagnostics via fieldbus Message objectsMessages on the device status Bit Message Meaning CANopen error messagesError register Error code tableError code Meaning SDO error message AbortData type Value range Data length Specifications for the objectsObject directory Object code Meaning CodingObjects, overview Index Subindex Designation Obj. code Data type AccessError register Objects of the productDevice type 100Ch Bit coding, subindex 00h1008h Manufacturer device nameIndex 100D h Object name Life time factor Object code Index 1018 h Object name Identity Object Object code Data type PDO Communication parameter Bit Acces Value Meaning Bit assignment subindex 01hBit 30 RTR bit Bit coding, subindex 02h1603h Receive PDO4 mapping Value description BitMeaning 1803h Transmit PDO4 communication parameterSubindex 03 h, inhibit time TPDO4 Meaning IL1F CANopen DS301 Object directory PDO4 mapping 1603h Units and conversion tables GlossaryMoment of inertia TemperatureRotation TorqueTerms and Abbreviations Default value Factory settingPower amplifier See power stage Can IndexIndex IL1F CANopen DS301 IL1F CANopen DS301 Index NMT IL1F CANopen DS301 Index 102 Fieldbus interface