User Manual CM CANopen CANopen Module for SIMATIC S7-1200 Doc.Id. HMSI-216-117 Rev. 1.00 Connecting DevicesTM +$/067$' &+,&$*2 .$5/658+( 72.<2 %(,-,1* 0,/$12 08/+286( &29(175< 381( &23(1+$*(1 HMS Industrial Networks Mailing address: Box 4126, 300 04 Halmstad, Sweden Visiting address: Stationsgatan 37, Halmstad, Sweden E-mail: info@hms-networks.com Web: www.anybus.
Important User Information This document is intended to provide a good understanding of the functionality offered by the CM CANopen Module for SIMATIC S7-1200. The reader of this document is expected to be familiar with high level software design, and communication systems in general. The use of advanced CANopen-specific functionality may require in-depth knowledge in CANopen networking internals and/or information from the official CANopen specifications.
Table of Contents Table of Contents Preface About This Document How To Use This Document ................................................................................................................ 1 Related Documents.................................................................................................................................. 1 Document History ...................................................................................................................................
Table of Contents Chapter 7 Supported Objects Static Data Types.................................................................................................................................... 26 Communication Profile Area................................................................................................................ 26 CiA 301 Communication Profile Objects....................................................................................... 26 Configuration Manager ...................
Preface P. About This Document P.1 How To Use This Document This document contains a general introduction as well as a description of the technical features provided by the CM CANopen Module for SIMATIC S7-1200, including configuration of the device. The reader of this document is expected to be familiar with PLC and software design, as well as with communication systems in general. The reader is also expected to be familiar with the Microsoft Windows operating system. P.
About This Document 2 P.4 Conventions & Terminology The following conventions are used throughout this document: • Numbered lists provide sequential steps • Bulleted lists provide information, not procedural steps • The term ‘user’ refers to the person or persons responsible for installing the CM CANopen module in a network. • Hexadecimal values are written in the format NNNNh, where NNNN is the hexadecimal value.
Chapter 1 1. Product Overview 1.1 Introduction The CM CANopen Module for SIMATIC S7-1200 is a plug-in IP20 compliant communication module designed to be used as an accessory to a SIMATIC S7-1200 PLC. It provides the user with the possibility to connect a CANopen network to a SIMATIC S7-1200 PLC. The figure below shows a CM CANopen module attached to a SIMATIC S7-1200 PLC to provide the connection from the PLC to CANopen.
Product Overview 4 1.2 Features • Powerful CANopen module for SIMATIC S7-1200 PLC. • 3 modules per CPU can be connected. • Connects up to 16 CANopen slave nodes per module in manager mode. • 256 byte input and 256 byte output per module. • CANopen slave functionality supported. • 3 LEDs provide diagnostic information on module, network and I/O status. • The module can be integrated in the hardware catalogue of TIA Portal.
Chapter 2 2. CANopen Fieldbus Functionality The functionality of the CM CANopen Module for SIMATIC S7-1200 is defined by the CANopen CiA 301 rev. 4.2 specification and the CANopen CiA 302 Draft Standard Proposal rev. 4.1. The module can be configured either as a manager or as a slave on the CANopen network. 2.1 Supported Fieldbus Services Communication and parameters in the CANopen protocol are built around objects.
Chapter 3 3. Transparent CAN Mode The CM CANopen Module for SIMATIC S7-1200 integrates Transparent CAN 2.0A (11 bit identifiers). With this protocol, the module allows transmission of any CAN frame from the PLC regardless of the overlaying CAN protocol, and is capable of receiving a number of predefined CAN frames from the CAN network. No other functionality is available. CAN 2.0A is the underlying protocol of CANopen, directly working on the bus.
Chapter 4 4. Installation The mounting and configuration of the CM CANopen Module for SIMATIC S7-1200 is done following these steps: 1. Mounting 2. Configuring the SIMATIC S7-1200 PLC to use the module (See “SIMATIC S7-1200 PLC Configuration” on page 10) 3. Setting the parameters of the module (See “SIMATIC S7-1200 PLC Configuration” on page 10) 4.
Installation 8 4.2 Status LEDs Three status LEDs indicate the status of the module as shown in the table below. The DIAG LED is visible on the front of the module and the other two are found behind the lid at the top of the module.
Installation 9 4.4 Line Termination To minimize the signal’s reflections from the end of the cable, a line termination is needed close to each end of the bus. If the cable you are using is not terminated, connect a line termination between contacts 2 and 7 (CAN_L and CAN_H) beneath the slot, where the module is mounted. The impedance of the termination should be 120 (5%, 1/4 W max.). CM CANopen Module for SIMATIC S7-1200 Doc.Rev. 1.00 Doc.Id.
Chapter 5 5. Configuration 5.1 General Configuration of the SIMATIC S7-1200 PLC to provide connectivity to a CAN/CANopen network, using the CM CANopen Module for SIMATIC S7-1200, can be done in different ways, depending on the application. The CANopen network, and the behavior of the module on this network, have to be configured using an external CANopen configuration tool on the PC and the configuration is downloaded to the CM CANopen module through the module USB connection.
Configuration 11 Double-clicking on the CM CANopen Module for SIMATIC S7-1200 in the list of modules in TIA Portal will open a window, where the user can set the values of the module parameters. The following parameters, that have to be defined, can be found in the CANopen Interface tab: Parameter Node number Operating mode Baudrate Description Node-ID on the CANopen network. Allowed values are 1 - 127 The operating mode of the module can be changed at any time using this parameter.
Configuration 12 5.3 CANopen Network Configuration An external CANopen configuration tool1 is used to configure the nodes on the CANopen network. The resulting Concise DCF files are downloaded to the CANopen manager using a USB connection between the PC and the CM CANopen module. At the next startup the CANopen manager will configure the network, if this function was set in the configuration tool during initial configuration.
Configuration 13 1. Open the TIA Portal program and start a new project by clicking “Create new project” on the left side of the screen. 2. Enter a name for the project and the path to where the project should be stored, optionally with information like author and descriptive comments. Press “Create”. CM CANopen Module for SIMATIC S7-1200 Doc.Rev. 1.00 Doc.Id.
Configuration 14 3. Select “Devices & networks” to the left and then press “Add new device”. 4. Select the PLC type used in the configuration. Select correct software version and optionally enter a name for the PLC (default PLC_1). Press “Add”. CM CANopen Module for SIMATIC S7-1200 Doc.Rev. 1.00 Doc.Id.
Configuration 15 5. Select the CM CANopen module in the list as shown in the picture. Drag and drop an instance of the module to the left side of the PLC module. 6. Double click on the Ethernet connector on the PLC and enter a proper IP address for the PLC. CM CANopen Module for SIMATIC S7-1200 Doc.Rev. 1.00 Doc.Id.
Configuration 16 7. Double click on the connector of the CM CANopen module and choose the module parameter tab. Enter the values in the parameter list. Please note that these parameters are valid for the module on the CANopen network. In this example, the CM CANopen module for S7-1200 is configured as a CANopen manager. The node number on the CANopen network is 1. The CANopen baud rate is set to 500 kbit/s and both the input data size and the output data size are set to 32 bytes. 8.
Configuration 17 9. Select the PG/PC interface you are using (in this example PN/IE) and the Ethernet interface on your PC (in this example Intel 82577...). If the IP address, entered earlier, is found on the network press “Load” to download to your device. If not, select the correct device from the list available in the “Accessible devices in target subnet” window. If the device is on another subnet, and not available in this window, the check box “Show all accessible devices” will have to be checked.
Configuration 18 Configuration of the CANopen network The configuration of the CANopen network, including the CM CANopen Module for SIMATIC S71200, is done separately with CM CANopen Configuration Studio. Important: Before downloading the configuration to the CANopen network, make sure that the PLC is set to STOP! 1. Open CANopen configuration tool. 2. Add nodes to CANopen network. 3. Configure each node with the necessary parameters. 4.
Chapter 6 6. CANopen Module Specification 6.1 NMT State Machine The function of the CM CANopen Module for SIMATIC S7-1200 can be described as a state machine with four states. Initialization State Initialization Pre-operational Operational Stopped Description When the power is switched on, the module starts initializing. This is done in three steps: basic initialization, reset application and reset communication.
CANopen Module Specification 20 The module can not enter the state STOPPED when transitions are initiated from the PLC. If the module is configured as a slave its behavior is controlled by a CANopen manager on the network by the use of NMT telegrams. If the connection to the manager is lost, though, the module sends an emergency code (FFA0h) and enters PRE-OPERATIONAL state. Transition no. 1 2 3 4 5 6 7 8 9 10 11 Description The initialization state is entered automatically at power on.
CANopen Module Specification 21 6.2 Data Exchange Process data is read and written using function blocks, see “Get Process Data In” on page 43 and “Set Process Data Out” on page 44. 6.2.1 PDO Functionality Real-time data transfer is performed by means of PDOs (Process Data Objects). The PDOs are linked to entries in the Device Object Dictionary and provide the interface to the application objects.
CANopen Module Specification 22 • TPDO TPDO no. 1 2 3 4 5 ... 16 ... 31 32 33 ... 64 Default COB-IDs 180h + Node-ID 280h + Node-ID 380h + Node-ID 480h + Node-ID 80000000h Mapped to... Relating to... Object index A040h, subindex 1... 8 Object index A040h, subindex 9... 16 Object index A040h, subindex 17... 24 Object index A040h, subindex 25... 32 Object index A040h, subindex 33... 40 ... Object index A040h, subindex 121... 128 ... Object index A040h, subindex 241...
CANopen Module Specification 23 RPDO Transmission Types RPDOs can be received either in synchronous or asynchronous mode. A synchronization (SYNC) object is transmitted periodically by a synchronization producer, located either in the CM CANopen Module for SIMATIC S7-1200 or in another node on the CANopen network. The data in synchronous RPDOs are not transferred to the SIMATIC S7-1200 PLC until after the next SYNC object is received.
CANopen Module Specification 24 1200 PLC. If the module is configured as a slave, it will react according to the settings in object 1029h. If it is in OPERATIONAL state, it will thus go to PRE-OPERATIONAL state and wait for the user to take action. If it is in manager mode it will take action according to the settings in the manager objects. The CM CANopen Module for SIMATIC S7-1200 can act as both heartbeat consumer and as heartbeat producer. 6.3.
CANopen Module Specification 25 6.3.4 Diagnostics When an event or alarm is generated by the CM CANopen module, the device alarm code 1Ah (external error) is transmitted and will trigger an interrupt in the PLC user program. This interrupt indicates that there is an alarm/event to be polled out from the module. Using the interface function Get Node & Network Status (CANopen mode) or Get Diagnostic Information (Transparent CAN mode) information about the alarm/event can be polled out from the module.
Chapter 7 7. Supported Objects The following sections describe the CANopen objects, according to CiA 301 and CiA 302, implemented within the module and described in the EDS file. 7.1 Static Data Types According to CiA 301. 7.2 Communication Profile Area 7.2.1 CiA 301 Communication Profile Objects The table below shows the objects according to CANopen specification CiA 301 rev. 4.2.
Supported Objects 27 Index Object Name subindex 1010h Store Parame- 00h 01h tersa Description Largest subindex supported Store all parameters 1011h Restore Param- 00h 01h etersa Largest subindex supported U8 Restore all default parameters U32 1014h COB-ID EMCY 00h Defines the COB-ID of the U32 Emergency Object Largest subindex supported U8 The consumer heartbeat time U32 defines the expected heartbeat cycle time and has to be higher than the corresponding producer heartbeat time.
Supported Objects 28 Index Object Name 1600h Receive PDO ... mapping 163Fh 1800h Transmit PDO ... parameter 183Fh 1A00h Transmit PDO ... mapping 1A3Fh subindex 00h 01h 02h 03h 04h 05h 06h 07h 08h 00h 01h 02h 03h 05h 00h 01h 02h 03h 04h 05h 06h 07h 08h Description No.
Supported Objects 29 7.2.2 Configuration Manager CiA 302 part 3: Configuration and program download Network Configuration Objects Configuration of the manager and the slaves can be done using concise device configuration files. The configuration is stored in the manager by writing to object 1F22h. The nodes are configured either when the module (in manager mode) is booted or when a request to boot a slave is sent to object 1F25h.
Supported Objects 30 7.2.3 Network Management Objects The NMT master controls the states of the connected network participants, the NMT slaves. It monitors the devices and reports to the application, for example if an NMT slave fails. Please refer to the CANopen specification, see “Related Documents” on page 1. In more complex systems several devices are able to perform as master, which means that the configuration must have an entry defining which device will act as master.
Supported Objects 31 NMT Start-up, 1F80h This object configures the startup behavior of the device, and how it will manage the slaves. If the module is set up as an NMT master in TIA Portal hardware configuration, the module will enable the master functionality by forcing bit 0 and bit 2 in this object to TRUE. If there is an attempt to set bit 0 and bit 2 to different values from the CANopen bus, an error response is received. Bit No.
Supported Objects 32 NMT Slave Assignment, 1F81h This object defines which slaves the master should monitor, control and/or configure. One entry is made for each assigned slave, with the subindex corresponding to the slave’s Node-ID. Byte 0 Bit No 0 Value 0 1 0 1 2 1 3 0 1 4 5 6 7 0 1 Description Node with this ID is not a slave Node with this ID is a slave.
Supported Objects 33 Request NMT, 1F82h Each node on the CANopen network can be controlled individually from the PLC by sending this object. The subindex indicates what nodes the request affects: subindex 0 i (with i = 1...127) 128 Description Largest subindex supported (128) Request NMT Service for the slave with Node-ID i.
Supported Objects 34 Request Guarding, 1F83h Guarding can be initiated from the object dictionary in a similar way. Guarding is initiated with the values stored in “NMT Slave Assignment, 1F81h” on page 32, provided that at the same time no parameters are entered for that node as a Heartbeat Consumer Note: This functionality is only supported in master mode. subindex 0 i (with i = 1...
Supported Objects 35 Product Code, 1F86h Each node on the CANopen network is checked against its expected product code. The subindex indicates which node is checked. The node in question is only checked if data is other than zero. subindex 0 i (with i = 1...127) Description Largest subindex supported (127) Compares expected product code (entered into this object) with actual product code (object 1018h, subindex 2) for the slave with Node-ID i. Boot up of slave is continued only if they match.
Supported Objects 36 7.3 Manufacturer Specific Objects One or several variable data objects are connected to each PDO. This is configured during the configuration phase. There are 64 Receive PDOs and 64 Transmit PDOs.
Supported Objects 37 Index 5006h Subindex 00h 01h 02h 03h 04h Type ARRAY U8 U32 U32 U32 U32 - ARRAY 00h 01h 02h 03h 04h U8 U32 U32 U32 U32 RO RO RO RO RO Largest subindex supported Node-ID 1-32 Node-ID 33-64 Node-ID 65-96 Node-ID 97-127 00h 01h 02h 03h 04h ARRAY U8 U32 U32 U32 U32 RO RO RO RO RO Inconsistent concise DCF bit list Largest subindex supported Node-ID 1-32 Node-ID 33-64 Node-ID 65-96 Node-ID 97-127 00h 01h 02h 03h 04h ARRAY U8 U32 U32 U32 U32 RO RO RO RO RO Wrong concise DCF bit
Supported Objects 38 Index 5015h Subindex - Type U16 Access Name and description RO Protocol error count 5016h - U16 RO External error count 5017h - U16 RO Device specific 5018h 00h 01h ... 7Fh 00h 01h ARRAY U8 DOMAIN ... DOMAIN ARRAY U8 DOMAIN 5500h RO RO ... RO RO RO Comment Counts emergency messages caused by emergency error code class 82XXh. Counts emergency messages caused by emergency error code class 90XXh Counts emergency messages caused by emergency error code class FFXXh.
Supported Objects 39 Status CM CANopen, 5000h, subindex 02h The table below gives the state of CM CANopen that can be read from subindex 02h of the Status CM CANopen object. The bits are valid either in manager or slave mode or in both. Value 00h 40h Name INIT MASTER_STATE_RESET Mode Both Both Description The CM CANopen is not initialized The CM CANopen is configured as a manager in the NMT startup object (1F80h).
Supported Objects 40 Bit No 5 6 7 Description An overrun of the low priority transmit queue occurred. Bit is reset after a read access. The CM CANopen transmits heartbeat, emergency messages, node guarding requests, SSDOs and CSDOs, asynchronous TPDOs, and NMT commands via the low priority transmit queue. A receive queue overrun occurred. Bit is reset after a read access. An overrun of the high priority transmit queue occurred. Bit is reset after a read access.
Supported Objects 41 7.3.1 I/O Buffer Addresses and Object Dictionary Indices Relation The (Q-area) application data bytes 0 - 31 are mapped to three different areas in the Local Object Dictionary. The same data is mapped to each area, but as different data types. For example: byte to index A040h, subindex 1 - 32, word to index A100h, subindex 1 - 16 and double-word (long) to indexA200h, subindex 1 - 8.
Supported Objects 42 Word object Index, sub-index Byte object Index, sub-index Receive data area Byte 0 - 7 Byte 0 A4C0h, 1 Byte 8 - 15 Byte 1 A4C0h, 2 Byte 16 - 23 Byte 2 A4C0h, 3 Byte 24 - 31 Byte 3 A4C0h, 4 Byte 32 - 39 Byte 4 A4C0h, 5 Byte 40 - 47 Byte 5 A4C0h, 6 Byte 6 A4C0h, 7 Byte 7 A4C0h, 8 Byte 8 A4C0h, 9 Byte 9 A4C0h, 10 Byte 10 A4C0h, 11 Byte 11 A4C0h, 12 Byte 12 A4C0h, 13 Byte 13 A4C0h, 14 Byte 14 A4C0h, 15 Byte 15 A4C0h, 16 Byte 16 A4C0h, 17 Byte 17 A
Chapter 8 8. Interface Functions All interface functions and function blocks are available for download from www.hms-networks.com/ can-for-S7-1200. 8.1 CANopen Interface Functions 8.1.1 Get Process Data In Input Parameters Name REQ ID Data type Bool HW_IO INDEX Byte, Dint, Int, Sint, Uint, Usint, Word MLEN Byte, Usint, Usint RECORD Variant Description Starts the function. Has to be set to TRUE for one scan cycle. Hardware address of the CANopen module. Can be read in TIA Portal. Data record number.
Interface Functions 44 8.1.2 Set Process Data Out Input Parameters Name REQ ID Data type Bool HW_IO INDEX Byte, Dint, Int, Sint, Uint, Usint, Word LEN Byte, Usint, Usint RECORD variant Description Starts the function. Has to be set to TRUE for one scan cycle. Hardware address of the CANopen module. Can be read in TIA Portal. Data record number. Should be set to 0091h. Length in bytes of the data to be written. Source area for the data to be written.
Interface Functions 45 8.1.3 SDO Read/Write General Reading (uploading) and writing (downloading) SDOs is performed by function blocks, available for download from www.hms-networks.com/can-for-S7-1200.1 Please note that these functions are only supported in CANopen manager mode. Input Parameters Name REQ Data type Bool ID SLOT Word Byte NODE Int INDEX SUB DB Word Byte Dint SIZE Uint Description Start request. Upload/download is started if REQ = TRUE for exactly one function block call.
Interface Functions 46 8.1.4 Get Node & Network Status Input Parameters Name REQ ID INDEX MLEN Data type Bool HW_IO Byte, Dint, Int, Sint, Uint, Usint, Word Byte, Usint, Usint RECORD Variant Description Starts the function. Has to be set to TRUE for one scan cycle. Logical address of the CANopen module. Data record number. Should be set to 0099h. Length in bytes of the data to be read. The value should correspond to the length of the data area in RECORD.
Interface Functions 47 Offset 4 5 Data type Uint8 Description CANopen Node status Definition Node NMT status 00h: NMT State Unknown 04h: NMT State Stopped 05h: NMT State Operational 06h: Reset Node 07h: Reset Communication 7Fh: NMT Pre-operational Array of Uint8 (up Network status (only Mainly reflects object 1F82h, subindices. 01h to 7F. Each entry to 127 elements) available if module is reflects a node ID.
Interface Functions 48 8.2 Transparent CAN Interface Functions There are separate function blocks handling the transparent CAN functionality. These are available for download from www.hms-networks.com/can-for-S7-1200. The functionality is described in “Transparent CAN Mode” on page 6. CAN_SEND and CAN_RCV handle the frames that are sent or received and CAN_CTRL controls the state and the settings of the CAN layer.
Interface Functions 49 8.2.2 CAN_RCV Input Parameters Name REQ ID ACK DB Data type Bool Word Bool Dint Description Starts the block. Has to be set to TRUE for one scan cycle. Logical address of the CM CANopen module. Set to TRUE for one scan cycle to acknowledge a newly read CAN frame. Number of data block.
Interface Functions 50 8.2.3 CAN_CTRL Input Parameters Name REQ ID FCN Data type Bool Word Int LEN Uint DB Dint Description Starts the block. Has to be set to TRUE for at least one scan cycle to start the block. Hardware address of the CM CANopen module. Function code: 1: Set acceptance filter in the module 2: Set number of frames to store before warning (BUFFER LIMIT REACHED) 3: Clear RX buffer. No data is used 4: (reserved) 5: Reset CAN controller (implies “Clear Bus Off”).
Interface Functions 51 cept for enable or disable all) or CAN-IDs can be transmitted in several messages after one another. Each CAN-ID starts with a set bit, telling whether to set or reset the CAN-ID, followed by the actual CAN-ID. If the set bit is 1, the CAN-ID will be enabled in the acceptance filter, if 0 it will be disabled. Bit 15 Set bit Bit 14 CAN-ID .... Bit 0 CAN-ID 0000h with LEN set to 0000h will disable all CAN-IDs. If LEN is set to 1 only CANID 0000h is disabled.
Interface Functions 52 8.2.4 Get Diagnostic Information Input Parameters Name REQ ID INDEX MLEN Data type Bool HW_IO Byte, Dint, Int, Sint, Uint, Usint, Word Byte, Usint, Usint Description Starts the function. Has to be set to TRUE for one scan cycle. Logical address of the CANopen module. Data record number. Should be set to 0092h. Length in bytes of the data to be read. The value should correspond to the length of the data area in RECORD.
Interface Functions 53 Transparent CAN Status Field The transparent CAN status field consists of 16 bits, where each bit represents a status code. Multiple bits can be set at the same time to indicate multiple status codes. Bit no. 0 1 2 3 4 5 6 7 8-15 Description BUS OFF ERROR PASSIVE BUFFER FULL BUFFER HALF FULL BUFFER LIMIT REACHED RECEIVE MESSAGE LOST TRANSMIT QUEUE: HALF FULL TRANSMIT QUEUE: WARNING LIMIT (reserved, set to 0) The status code 0000h indicates ‘SUCCESS’, while e.g.
Appendix A A. Technical Specification A.1 Mechanical Properties Housing Plastic housing, plug-in module, protection class IP20 Dimensions Width: 30 mm (1.18”) Weight: 120 g (0.26 lb.) A.2 Environmental Characteristics Relative Humidity Operating: 15% to 95% non-condensing Non operating: 5% to 95% non-condensing Temperature Operating: Non operating: 0 °C to +60 °C (+32°F to +140 °F) -40 °C to +70 °C (-40 °F to +158 °F) CM CANopen Module for SIMATIC S7-1200 Doc.Rev. 1.00 Doc.Id.
Technical Specification 55 A.3 Regulatory Compliance CANopen Conformance CiA 301 rev. 4.2 CAN Standard Supports CAN 2.0A EMC Compliance This product is in accordance with the EMC directive 2004/108/EC, through conformance with the following standards: • SS-EN 55016-2-3:2007 Class A • SS-EN 61131-2:2007 Clause 8 UL/c-UL compliance The certification has been documented by UL in file E214107.
Appendix B B. Status LED Timing Diagrams The LEDs on the front of the module change their behavior according to the status of the module. This appendix gives the timing diagrams for the different indications, described in “Status LEDs” on page 8.
Appendix C C. CANopen Emergency Codes Below is a list of the CANopen emergency codes that can be produced by the CM CANopen Module for SIMATIC S7-1200. The five latest emergencies, reported by the module, can be read from the list in object 1003h, see page 26.
CANopen Emergency Codes 58 Emergency Code FFA0h Description PLC has entered STOP state while network is in OPERATIONAL. Module goes to PRE-OPERATIONAL. (Only in slave mode) These codes conform to the CANopen standard. CM CANopen Module for SIMATIC S7-1200 Doc.Rev. 1.00 Doc.Id.
Appendix D D. Error Codes (RET) D.1 Function Block Error Codes Each function block has a separate set of error codes, that are returned when an error is detected. CAN_CTRL Error codea 109B 109C 1013 3100-3799 39XX FF00 Description Function code (FCN) not allowed If FCN=1: Length of filter is too big (> 2048) Read response failed after 1000 tries Internal read/write error CM message error (XX = Message error code, see “Message Error Codes” on page 60) Error code missing a.
Error Codes (RET) 60 WriteSDO Error codea 1013 104A 3100-3799 38XX 39XX FF00 Description Read response failed after 1000 tries Wrong slot number Internal read/write error SDO error (XX = SDO error code) CM message error (XX = Message error code, see “Message Error Codes” on page 60) Error code missing a. All error codes are given in hexadecimal format. D.
Error Codes (RET) 61 SFC/SFB numberb SFB52, SFB53, SFC14, SFC15 ID mismatch (the following modules are permitted: S7-300 modules for an SFB52, S7-300, S7-400 modules for an S7-400, S7-DP modules for an S7-300 and SFB53 S7-400). Negative acknowledgement when communicating with the module. • The module was removed during the communication or is defective • Unilateral I/O of the standby CPU not available (with H-systems). For example, standby CPU is in state STOP.
Error Codes (RET) 62 Error Additional Description codea error codea 39 Acyclic error. Additional error code equals error code from the CANopen manager.
Error Codes (RET) 63 Error Additional Description codea error codea 45 1X DB could not be deleted because it was created with the keyword UNLINKED (S7-400 only). X specifies the offset from DBSTART where the error occurred 2X DB could not be deleted because it is stored on a flash card. X specifies the offset from DBSTART where the error occurred 3X DB can not be deleted.
Error Codes (RET) 64 Error codea 91 92 93 94 95 96 Additional error codea 00 00 00 00 00 00 97 00 98 99 9A 9B 9C 9D 9E FF 00 00 00 00 00 00 00 00 Description Parameter BPSIZE contains invalid value IN parameter is not of type BYTE OUT parameter is not of type BYTE Illegal syntax ID of the IN parameter (valid value is 10h) Illegal syntax ID of the OUT parameter (valid value is 10h) Either • the size of the IN parameter exceeds 1024 bytes or • the size of the IN parameter exceeds the maximum size for t
