*mydirectindustry

Catalogs
Infranor Group
CD1k_CANopenProtocol_e_1.3(old)

CD1k_CANopenProtocol_e_1.3(old)

Product catalog summary

Overview: The document is a comprehensive guide on the CANopen Communication Profile for INFRANOR CD1-k, BD1/k, and BD2/k drives, aimed at skilled technicians familiar with electronics and servo systems. It emphasizes safety precautions, such as waiting for residual voltage to dissipate before handling the drives and ensuring proper grounding to prevent electrostatic discharge damage.

Communication Profile: This section details the communication objects used in the CANopen protocol, including CAN Telegram, Default COB-ID, Network Management Objects (NMT), Synchronisation Object (SYNC), Process Data Object (PDO), Service Data Object (SDO), and Emergency Object (EMCY). Each object type is explained with its specific parameters and mapping requirements.

Network Initialization and System Boot-Up: The document outlines the NMT state machine and the initialization procedure necessary for setting up the network and booting the system.

Object Dictionary: A detailed description of the object dictionary is provided, including general information and specific objects like Device Type, Error Register, Manufacturer Device Name, and others. Each object is associated with a unique identifier and serves a specific function within the communication profile.

Device Profile: This section covers PDO mapping, common entries in the object dictionary, and device control mechanisms. It includes descriptions of motor types, drive modes, digital inputs and outputs, and the drive state machine.

Factor Group: The document explains units, object dictionary entries, and descriptions related to polarity, encoder resolution, and feedback types. It also covers encoder pulse interpolation and second encoder selection options.

Profile Position Mode: The final section discusses the profile position mode, including target position, maximum motor speed, profile velocity, acceleration, deceleration, motion profile type, and software position limits.

Warnings and Recommendations: The manual includes warnings about potential physical damage from improper handling and emphasizes the importance of following installation guidelines to maintain CE approval and warranty validity.

Specifications: The document references several CiA standards, including DS-201..207 for the CAN Application Layer and DS-301 for the Application Layer and Communication Profile. It also mentions DSP-402 for Drive and Motion Control.

Definitions: Key terms are defined, such as CAN (Controller Area Network), COB (Communication Object), NMT (Network Management), PDO (Process Data Object), and SDO (Service Data Object). The document also explains various operation modes like Homing Mode, Profile Position Mode, Interpolated Position Mode, Profile Velocity Mode, and Profile Torque Mode.

Architecture: The architecture section describes the state machine used for device control, which manages drive states like servo on/off and fault reset. It also details the default operation mode for the drives, which is Interpolated Position Mode.

Network Management: The document outlines NMT protocols and their commands, such as Start Remote Node and Reset Communication. It also describes the SYNC object used for network clock synchronization.

Process Data Objects (PDO): PDOs are used for real-time data exchange, with TPDOs and RPDOs defined by communication parameters and mapping. The document explains transmission types and modes, including synchronous and asynchronous transmissions.

Service Data Objects (SDO): SDOs facilitate a client/server communication model, allowing access to the object dictionary, which contains all server objects related to CAN communication and drive functionality.

Emergency Objects (EMCY): The emergency telegram structure is detailed, including specific error fields for different drive models, such as CD1-k, BD1/k, and BD2/k.

Device Control: Describes the status and control sequence of the drive, including states like Power Disabled, Fault, and Operation Enable. Includes control word (6040h) and status word (6041h) with various bit functions for controlling and monitoring the drive state.

Good Practices: Ensure correct configuration of velocity and torque parameters to maintain system stability and performance. Regularly monitor error codes and warning codes to preemptively address potential issues.

Catalog excerpts

CANopen Communication Profile SERVO DRIVES & MOTION CONTROL

Open the catalog to page 1

CD1-k, BD1/k, BD2/k CANopen Communication Profile

Open the catalog to page 2

CD1-k, BD1/k, BD2/k – CANopen Communication Profile ! This is a general manual describing the CANopen Communication Profile of the INFRANOR CD1-k, BD1/k and BD2/k drive. For the installation and commissioning of the drive, please refer to the appropriate manuals. Maintenance procedures should be attempted only by highly skilled technicians having good knowledge of electronics and servo systems with variable speed (EN 60204-1 standard) and using proper test equipment. The conformity with the standards and the "CE" approval is only valid if the items are installed according to the recommendations...

Open the catalog to page 3

CD1-k, BD1/k, BD2/k – CANopen Communication Profile

Open the catalog to page 4

CD1-k, BD1/k, BD2/k - CANopen Communication Profile Content PAGE

Open the catalog to page 5

CD1-k, BD1/k, BD2/k - CANopen Communication Profile SERVO DRIVES & MOTION CONTROL

Open the catalog to page 6

CD1-k, BD1/k, BD2/k - CANopen Communication Profile

Open the catalog to page 7

CD1-k, BD1/k, BD2/k – CANopen Communication Profile

Open the catalog to page 8

CD1-k, BD1/k, BD2/k – CANopen Communication Profile Chapter 1 – Overview 1.1 - REFERENCE CiA DS-201..207 CAN Application Layer for Industrial Applications Version 1.1 Application Layer and Communication Profile Version 4.01 Device Profile: Drive and Motion Control Version 1.1 Controller Area Network CAN in Automation e. V. CAN-Bus international manufacturer and user organisation. CAN Application Layer. The Application layer for CAN as specified by CiA. Communication Object is a CAN message. Data must be sent accross a CAN network inside a COB. COB-Identifier. Each CAN message has a single identifier....

Open the catalog to page 9

CD1-k, BD1/k, BD2/k - CANopen Communication Profile Device Control: The drive starting and stopping are executed by the state machine. The state machine - handled with a control word and a status word via CAN bus - gives the possibility to control the state of the drive: servo on/off, start/stop movement, fault reset... Operation modes: The operation mode defines the behaviour of the drive : Homing Mode: In this mode, various methods can be used to find a home position. Profile Position Mode: In this mode, a trapezoidal trajectory generator gives the drive the possibility to execute a positioning...

Open the catalog to page 10

CD1-k, BD1/k, BD2/k - CANopen Communication Profile OINFRANOR SERVO DRIVES & MOTION CONTROL COB-ID : COB-Identifier of 11 bits RTR : Remote Transmission Request CTRL: Control field CRC : Cyclic Redundancy Check 2.1.2 - DEFAULT COB-ID The COB-ID is of 11 bits. Node-ID (bits 0 - 6) is the drive address from 1 to 127. TX = Transmit from drive to master RX = Receive by drive from master Chapter 2 - Communication Profile

Open the catalog to page 11

CD1-k, BD1/k, BD2/k - CANopen Communication Profile Node-ID: The Node-ID indicates the address of the CD1-k, BD1/k or BD2/k (defined by switches). If Node_ID = 0, the protocol addresses all NMT slaves. 2.1.4 - SYNCHRONISATION OBJECT (SYNC) The SYNC object is a broadcast message sent by the master. This message provides a network clock. The period is specified by the communication cycle period (object 1006h). The Infranor servo-drives use this SYNC message to synchronize their clock. At least 10 cycles are necessary for the servo-drive to start the synchronisation. Communication cycle Synchronous...

Open the catalog to page 12

CD1-k, BD1/k, BD2/k - CANopen Communication Profile PDOs are unconfirmed messages used for real-time data exchange. PDOs sent by the master are RPDOs and PDOs sent by the drive are TPDOs. Data in each PDO are defined by a list of objects (PDO mapping). Infranor servo drives have TPDO1, RPDO1, TPDO3 and RPDO3. - PDO communication parameters at object 1400h + RPDO_number-1 (for RPDO) or 1800h + TPDO_number-1 (for TPDO) - PDO mapping at object 1600h + RPDO_number-1 (for RPDO) or 1A00h + TPDO_number-1 (for TPDO) - Transmission type The distribution of COB-ID is defined by default (see section 2.1.2)....

Open the catalog to page 13

CD1-k, BD1/k, BD2/k - CANopen Communication Profile The sub-index 0 of mapping parameter contains the number of valid entries within the mapping record. This number of entries is also the number of application variables which shall be transmitted/received with the corresponding PDO. The sub-index 1 to number of entries contains the information about the mapped application variables. These entries describe the PDO contents by their index, sub-index and length (in bits). Structure of PDO Mapping Entry: Byte : MSB___LSB index (16 bit) | sub-index (8 bit) | object length (8 bit) ~~| Object Dictionary...

Open the catalog to page 14

CD1-k, BD1/k, BD2/k - CANopen Communication Profile 2.1.7 - EMERGENCY OBJECT (EMCY) The Emergency telegram consists of 8 bytes: Chapter 2 - Communication Profile

Open the catalog to page 15

CD1-k, BD1/k, BD2/k – CANopen Communication Profile Fault Position Limits I2 t Encoder Counting Position Following / Speed Following EEPROM Synchro_CAN Hall Effect Sensors Procedure Amplifier Temperature Motor Temperature Power Stage Failure Power Supply Undervoltage Encoder Cable Interruption treatment / Cycle Software / 500 µs Software / 2 ms Software / 500 µs Software / 500 µs Software Software / cycle Software Software Hardware Hardware Hardware Hardware 2.2 - NETWORK INITIALISATION AND SYSTEM BOOT-UP 2.2.1 - NMT STATE MACHINE The NMT state machine defines the communication status. Power...

Open the catalog to page 16

CD1-k, BD1/k, BD2/k - CANopen Communication Profile 2.3 - OBJECT DICTIONARY 2.3.1 - GENERAL INFORMATION This object describes the type of a device. Device Profile Number : 402 Additional Information : 02 Servo Drive Description Generic Error Chapter 2 - Communication Profile

Open the catalog to page 17

CD1-k, BD1/k, BD2/k - CANopen Communication Profile 2.3.1.3 - Object 1008h: Manufacturer Device Name Chapter 2 - Communication Profile

Open the catalog to page 18

CD1-k, BD1/k, BD2/k - CANopen Communication Profile This object supports the saving of parameters in a non volatile memory. By read access, the device provides information about its saving capacities. Sub-index 0: largest sub-index that is supported. Sub-index 1: refers to all parameters that can be stored in the device. In order to avoid storage of parameters by mistake, storage is only executed when a specific signature is written to the appropriate sub-index. The signature is 'save'. This object defines the COB-ID of the synchronisation object (SYNC). The new COB-ID takes immediately effect...

Open the catalog to page 19

CD1k_CANopenProtocol_e_1.3(old)

CD1k_CANopenProtocol_e_1.3(old)

Catalog excerpts

All Infranor Group catalogs and technical brochures

Archived catalogs