YASKAWA CP 341 Manual
  1. Manuals
  2. Brands
  3. YASKAWA Manuals
  4. Control Systems
  5. CP 341
  6. Manual
YASKAWA CP 341 Manual

YASKAWA CP 341 Manual

Rs422/485
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
VIPA System 300S
CP | 341-1CH01 | Manual
HB130 | CP | 341-1CH01 | en | 18-40
CP 341 RS422/485
www.vipa.com/en/service-support/manuals

Advertisement

Table of Contents
loading

Related Manuals for YASKAWA CP 341

Summary of Contents for YASKAWA CP 341

  • Page 1 VIPA System 300S CP | 341-1CH01 | Manual HB130 | CP | 341-1CH01 | en | 18-40 CP 341 RS422/485 www.vipa.com/en/service-support/manuals...
  • Page 2 VIPA GmbH Ohmstr. 4 91074 Herzogenaurach Telephone: +49 9132 744-0 Fax: +49 9132 744-1864 Email: info@vipa.com Internet: www.vipa.com 341-1CH01_000_CP 341 RS422/485,1,EN - © 2018...

  • Page 3: Table Of Contents

    1.3 Safety information..................... 7 Basics........................8 2.1 Safety information for users................8 2.2 Basics - ISO/OSI reference model..............9 2.3 CP 341-1CH01....................10 2.4 General data....................11 Assembly and installation guidelines..............13 3.1 Installation dimensions................... 13 3.2 Assembly standard bus.................. 14 3.3 Installation guidelines..................
  • Page 4 VIPA System 300S Table of contents 7.3 Diagnostics via diagnostic buffer..............103 7.4 Diagnostics by diagnostics interrupt............. 104 HB130 | CP | 341-1CH01 | en | 18-40...

  • Page 5: General

    VIPA System 300S General Copyright © VIPA GmbH General 1.1 Copyright © VIPA GmbH All Rights Reserved This document contains proprietary information of VIPA and is not to be disclosed or used except in accordance with applicable agreements. This material is protected by the copyright laws. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to VIPA), except in accord- ance with applicable agreements, contracts or licensing, without the express written con- sent of VIPA and the business management owner of the material.

  • Page 6: About This Manual

    Tel.: +49 9132 744-1150 (Hotline) EMail: support@vipa.de 1.2 About this manual Objective and contents This manual describes the CP 341-1CH01 of the System 300S from VIPA. It contains a description of the construction, project implementation and usage. Product Order number...

  • Page 7: Safety Information

    VIPA System 300S General Safety information CAUTION! Damages to property is likely if these warnings are not heeded. Supplementary information and useful tips. 1.3 Safety information Applications conforming The system is constructed and produced for: with specifications communication and process control general control and automation tasks industrial applications operation within the environmental conditions specified in the technical data...

  • Page 8: Basics

    VIPA System 300S Basics Safety information for users Basics 2.1 Safety information for users Handling of electrostatic VIPA modules make use of highly integrated components in MOS-Technology. These sensitive modules components are extremely sensitive to over-voltages that can occur during electrostatic discharges.

  • Page 9: Basics - Iso/Osi Reference Model

    VIPA System 300S Basics Basics - ISO/OSI reference model 2.2 Basics - ISO/OSI reference model Overview The ISO/OSI reference model is based on a proposal that was developed by the Interna- tional Standards Organization (ISO). This represents the first step towards an interna- tional standard for the different protocols.

  • Page 10: Cp 341-1Ch01

    Dimensions of the basic enclosure: 1tier width: (WxHxD) in mm: 40x125x120 Compatibility The CP 341-1CH01 is compatible to the Siemens CP 341 (6ES7 341-1CH01-0AE0). The CP is configured in the Siemens SIMATIC Manager. HB130 | CP | 341-1CH01 | en | 18-40...

  • Page 11: General Data

    VIPA System 300S Basics General data 2.4 General data Conformity and approval Conformity 2014/35/EU Low-voltage directive 2014/30/EU EMC directive Approval Refer to Technical data others RoHS 2011/65/EU Restriction of the use of certain hazardous substances in electrical and electronic equipment Protection of persons and device protection Type of protection IP20...
  • Page 12 VIPA System 300S Basics General data Mounting conditions Mounting place In the control cabinet Mounting position Horizontal and vertical Standard Comment Emitted interference EN 61000-6-4 Class A (Industrial area) Noise immunity EN 61000-6-2 Industrial area zone B EN 61000-4-2 8kV at air discharge (degree of severity 3), 4kV at contact discharge (degree of severity 2) EN 61000-4-3 HF field immunity (casing)

  • Page 13: Assembly And Installation Guidelines

    VIPA System 300S Assembly and installation guidelines Installation dimensions Assembly and installation guidelines 3.1 Installation dimensions Dimensions Basic enclo- 1tier width (WxHxD) in mm: 40 x 125 x 120 sure Dimensions Installation dimensions HB130 | CP | 341-1CH01 | en | 18-40...

  • Page 14: Assembly Standard Bus

    VIPA System 300S Assembly and installation guidelines Assembly standard bus 3.2 Assembly standard bus General The single modules are directly installed on a profile rail and connected via the backplane bus connector. Before installing the modules you have to clip the backplane bus con- nector to the module from the backside.
  • Page 15 VIPA System 300S Assembly and installation guidelines Assembly standard bus Assembly possibilities Please regard the allowed environment temperatures: horizontal assembly: from 0 to 60°C vertical assembly: from 0 to 40°C lying assembly: from 0 to 40°C Approach If you do not deploy SPEED-Bus modules, the assembly happens with the following approach: Bolt the profile rail with the background (screw size: M6), so that you still have min- imum 65mm space above and 40mm below the profile rail.

  • Page 16: Installation Guidelines

    VIPA System 300S Assembly and installation guidelines Installation guidelines 3.3 Installation guidelines General The installation guidelines contain information about the interference free deployment of a PLC system. There is the description of the ways, interference may occur in your PLC, how you can make sure the electromagnetic compatibility (EMC), and how you manage the isolation.
  • Page 17 VIPA System 300S Assembly and installation guidelines Installation guidelines Proof the correct fixing of the lead isolation. – Data lines must be laid isolated. – Analog lines must be laid isolated. When transmitting signals with small ampli- tudes the one sided laying of the isolation may be favourable. –...

  • Page 18: Hardware Description

    Modbus Master ASCII / RTU (no hardware dongle necessary) – Modbus Slave RTU (no hardware dongle necessary) Parameterization CP 341 via the parameterization package from Siemens – CP 341: Point-to-Point is parameterized as of V 5.0 Up to 250 telegrams within the 1024byte sized receive and send buffer Baud rate parameterizable up to 76.8kbit/s...

  • Page 19: Structure

    LED status indicators The following components are under the front flap RS422/485 interface RS422/485 interface Pin compatible to Siemens CP 341 (6ES7 341-1CH01-0AE0) Logical conditions as voltage difference between 2 twisted lines Serial bus connection – Full-duplex: Four-wire operation (RS422) –...
  • Page 20 VIPA System 300S Hardware description Structure X2: 9pin D-type jack Designation Input/Output Description n.c. T(B)+ Output Send data (four-wire) R(B)+ Input Receive data (four-wire) R(B)+ / T(B)+ Input/Output Receive/Send data (two-wire) Output Request to send: – RTS "ON": CP ready to send –...
  • Page 21 VIPA System 300S Hardware description Structure RS485 cabling In the case of cables > 50m you have to solder in a terminating resistor of approxi- mately 330Ω on the receiver for data free traffic. The protocol 3964(R) is not possible at two-wire operation. RS422 cabling In the case of cables >...
  • Page 22 Ä Chap. 4.3 ‘Technical data’ page 23 LEDs The CP 341-1CH01 carries a number of LEDs that are available for diagnostic purposes on the bus and for displaying the local status. Dependent on the mode of operation these give information according to the following pattern over the operating condition of the CP:...

  • Page 23: Technical Data

    VIPA System 300S Hardware description Technical data 4.3 Technical data Order no. 341-1CH01 Type CP 341 SPEED-Bus Current consumption/power loss Current consumption from backplane bus 160 mA Power loss 0.8 W Status information, alarms, diagnostics Status display Interrupts Process alarm...
  • Page 24 VIPA System 300S Hardware description Technical data Order no. 341-1CH01 Point-to-point communication PtP communication ü Interface isolated ü RS232 interface RS422 interface ü RS485 interface ü Connector Sub-D, 9-pin, female Transmission speed, min. 150 bit/s Transmission speed, max. 76.8 kbit/s Cable length, max.
  • Page 25 VIPA System 300S Hardware description Technical data Order no. 341-1CH01 UL certification KC certification HB130 | CP | 341-1CH01 | en | 18-40...

  • Page 26: Deployment

    Siemens SIMATIC manager. Place a profile rail with the corresponding CPU and its modules. Engineer in duty of the CP 341-1CH01 from VIPA the Siemens CP with the order number 6ES7 341-1CH01-0AE0 to the corresponding slot. Adjust the address by the properties dialog and the protocol for transmission and its parameters by means of the parameter plugin "Point-to-Point-Communication,...
  • Page 27 VIPA System 300S Deployment Fast introduction Protocol parameter For parameterization of the protocol parameters the parameter plugin "Point-to-Point- Communication, Parameter Assignment" is necessary. This plugin may be received from Siemens. The parameter plugin "Point-to-Point-Communication, Parameter Assignment" is started from the properties dialog of the CP by the button [Parameter...]. Set at "Protocol"...

  • Page 28: Hardware Configuration

    Place the corresponding modules via drag&drop from the hardware catalog to the corresponding slot of the profile rail. To project the VIPA CP 341-1CH01 the Siemens CP 341 (6ES7 341-1CH01-0AE0) at the according slot is to be used. Adjust via the CP "properties" the transmission protocol and the protocol specific parameters (see protocol parameters).

  • Page 29: Properties

    The properties of the CP may be accessed by a double click at the CP within your project in the hardware configurator. The parameters of the VIPA CP 341 may be modified by the registers in the following described. For parameterization the parameter plugin "Point-to- Point Communication, Parameter Assignment"...
  • Page 30 VIPA System 300S Deployment Hardware configuration > Properties Proceeding Start after installation the parameter plugin "Point-to-Point- Communication, Param- eter Assignment" from the properties dialog of the CP by the button [Parameter...]. Set at "Protocol" the protocol you want. Depending on the selected protocol there is the possibility to set the parameters for received data and interface.

  • Page 31: Communication With The User Program

    The library may be opened in the Siemens SIMATIC manager by ‘File è Open è Libraries’ and here "CP PtP". The blocks may be found at "Blocks" of the CP 341. ð For deployment of a block this is to be copied into your project.
  • Page 32 VIPA System 300S Deployment Communication with the user program Data consistency The data consistency is limited by the block size of 32byte during communication between CPU and CP. For the consistent data communication of more than 32byte the following is to be considered: FB 8 - P_SND_RK: –...

  • Page 33: Firmware Update

    VIPA System 300S Deployment Firmware update > Firmware update with Siemens parameterization tool 5.4 Firmware update Overview For functional expansion and error recovery firmware updates can be uploaded to the operating-system memory of the CP. Subsequent loading of firmware updates with the parameterization interface "Point-to-Point Communication, Parameter Assign- ment".

  • Page 34: Firmware Update At Deployment Of A Speed7 Cpu

    VIPA System 300S Deployment Firmware update > Firmware update at deployment of a SPEED7 CPU 5.4.2 Firmware update at deployment of a SPEED7 CPU By means of a MMC there is the opportunity to execute a firmware update at the CPU and its components.

  • Page 35: Show Cp Firmware Version

    VIPA System 300S Deployment Firmware update > Show CP firmware version You start the transfer of the firmware as soon as you tip the RUN/STOP lever down- wards to MRES within 10s. During the update process, the LEDs SF and FRCE are alternately blinking and MMC LED is on.

  • Page 36: Communication Protocols

    The CP serves for an automatic serial data transfer. To do this the CP is equipped with drivers for the following protocols: ASCII 3964(R) Please regard the computer interface RK512 is not supported by the VIPA CP 341-1CH01. Additionally the following loadable protocol driver are supported: Modbus master RTU Modbus master ASCII Modbus slave RTU In the following each supported protocol is described.

  • Page 37: Ascii

    VIPA System 300S Communication protocols ASCII 6.2 ASCII Mode of operation ASCII data communication is one of the simple forms of data exchange that may be compared to a multicast/broadcast function. Individual messages are separated by means of character delay time (ZVZ). Within this time the transmitter must have sent its telegram to the receiver.

  • Page 38: Ascii - Parameter

    VIPA System 300S Communication protocols ASCII > ASCII - Parameter 6.2.1 ASCII - Parameter Here the parameters for the ASCII driver may be set. At ASCII the parameter settings for the character frame and the baud rate must be identical on every communication partner. End code of a message During ASCII transmission the end of the receive messages frame may be recognized in different ways:...
  • Page 39 VIPA System 300S Communication protocols ASCII > ASCII - Parameter Send with end character Here end character(s) may be defined or the length set in the FB may be specified as soon as "End character" is activated at the end ID. Parameter Description Default value...
  • Page 40 VIPA System 300S Communication protocols ASCII > ASCII - Parameter Data flow control Parameter Description Default value Data flow control Range of values: none, XON, XOFF none Data flow control parameters Parameter Description Default value XON code Code for XON at "XON/XOFF" 11(DC1) Range of values: 0...7Fh/FFh (7/8 data bits) XOFF code...
  • Page 41 VIPA System 300S Communication protocols ASCII > ASCII - Parameter Wiring receiver At the CP interface the wiring of the receiver is realized as follows: Parameter Description None No pre-assignment of the receiving lines. (default value: not activated) This setting only makes sense with bus-capable spe- cial drivers.

  • Page 42: 3964(R)

    VIPA System 300S Communication protocols 3964(R) > Basics 3964(R) 6.3 3964(R) 6.3.1 Basics 3964(R) Mode of operation The 3964(R) procedure controls the data transfer of a point-to-point link between the CP and a communication partner. The procedure adds control characters to the telegram data during data transfer.

  • Page 43: Proceeding

    VIPA System 300S Communication protocols 3964(R) > Proceeding Block check character 3964R appends a Block check character to safeguard the transmitted data. The BCC- (BCC-Byte) Byte is calculated by means of an XOR function over the entire data of the telegram, including the DLE/ETX.

  • Page 44: 3964(R) - Parameter

    Data integrity is increased by the addition sending of a activated Block Check Character BCC. If the CP 341-1CH01 recognizes the string DLE ETX BCC, it stops receiving. The CP compares the received block check character BCC with the longitudinal parity calculated internally.
  • Page 45 VIPA System 300S Communication protocols 3964(R) > 3964(R) - Parameter Protocol parameter The character delay time defines the maximum amount of time permitted between two incoming characters within a message frame. Parameter Description Default value Character delay time Please regard the shortest character delay time depends on the baud rate: 220ms (ZVZ) Baud rate (bit/s)
  • Page 46 – (Default value: "Delete CP receive buffer at startup" deactivated) This parameter may not be activated. The receive buffer of the CP 341-1CH01 is not deleted when the CPU status goes from STOP to RUN (CPU startup). 3964(R) Interface With the protocol 3964(R) is the operating mode Full-duplex operation (RS422) preset.
  • Page 47 VIPA System 300S Communication protocols 3964(R) > 3964(R) - Parameter Wiring receiver At the CP interface the wiring of the receiver is realized as follows: Parameter Description None No preassignment of the receiving lines. This setting only makes sense with bus-capable special drivers. (Default value: not activated) Parameter Description...

  • Page 48: Modbus

    VIPA System 300S Communication protocols Modbus > Basics Modbus 6.4 Modbus 6.4.1 Basics Modbus Overview The Modbus protocol is a communication protocol that defines a hierarchic structure between a master and several slaves. Physically, Modbus transmits via a serial half- duplex connection as point-to-point connection with RS232 or as multi-point connection with RS485.

  • Page 49: Modbus Master - Parameter

    6.4.2 Modbus Master - Parameter Modbus by loadable driver For deployment of Modbus Master on the CP 341-1CH01 a loadable driver is neces- sary. This may be downloaded from the Siemens website. With deployment of loadable drivers for software technical reason the drivers from Siemens were transferred to the CP but not installed.
  • Page 50 VIPA System 300S Communication protocols Modbus > Modbus Master - Parameter 6.4.2.1 Modbus Master (RTU) Speed Here the transfer speed may be selected from a selection list. Parameter Description Default value Baud rate in bit/s Transfer speed in bit/s 9600 Range of values: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 76800 Character frames...
  • Page 51 VIPA System 300S Communication protocols Modbus > Modbus Master - Parameter Protocol parameter Parameter Description Default value Reply monitoring time Here a waiting time in ms may be preset spent by the CP 2000 waiting for a reply message from the slave after output of a request message.
  • Page 52 VIPA System 300S Communication protocols Modbus > Modbus Master - Parameter 6.4.2.2 Modbus Master (ASCII) Speed Here the transfer speed may be selected from a selection list. Parameter Description Default value Baud rate in bit/s Transfer speed in bit/s 9600 Range of values: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 76800 Character frames...
  • Page 53 VIPA System 300S Communication protocols Modbus > Modbus Master - Parameter Protokoll-Parameter Parameter Description Default value Character Delay Time Here the delay time may be preset in ms. 1000 The Character Delay Time is the time that may elapse between two characters within a Modbus frame. The receiving station checks the incoming data for time out and if detected the message is ignored and an error is indi- cated.
  • Page 54 VIPA System 300S Communication protocols Modbus > Modbus Master - Parameter Interface Here it is to specify if the interface is operated in half- (RS485) or full-duplex (RS422) operation. Full-duplex (RS422) – Four-wire operation (default value: active) Data is exchanged between the communication partners in both directions simul- taneously.

  • Page 55: Modbus Master - Functionality

    VIPA System 300S Communication protocols Modbus > Modbus Master - Functionality 6.4.3 Modbus Master - Functionality Overview With Modbus the data transfer happens without any handshake. The master initiates the transmission, and after sending a request message it waits for a reply message from the slave for the duration of the reply monitoring time set.
  • Page 56 VIPA System 300S Communication protocols Modbus > Modbus Master - Functionality DATA Here the function code specific data are transferred. More information about the structure of this field may be found at the function codes beneath. Ä Chap. 6.4.4 ‘Modbus Master - Function codes’...
  • Page 57 VIPA System 300S Communication protocols Modbus > Modbus Master - Functionality Communication with the For the processing of the connecting jobs a user program is necessary in the CPU. Here user program the blocks FB 7 - P_RCV_RK and FB 8 - P_SND_RK are used for communication between CPU, CP and a communication partner.

  • Page 58: Modbus Master - Function Codes

    VIPA System 300S Communication protocols Modbus > Modbus Master - Function codes 6.4.4 Modbus Master - Function codes Naming convention Modbus has some naming conventions: Modbus differentiates between bit and word access; Bits = "Coils" and Words = "Reg- ister". Bit inputs are referred to as "Input-Status"...
  • Page 59 VIPA System 300S Communication protocols Modbus > Modbus Master - Function codes 32bit access with Modbus Master ASCII With Modbus Master ASCII the register oriented functions 03,06,16 may also handle 32bit registers. Here the parameter "with 32-bit Register" is to be activated at "Modbus Master" of the protocol properties.
  • Page 60 VIPA System 300S Communication protocols Modbus > Modbus Master - Function codes The driver enters the data of the reply message into the destination DB word-by-word. The 1. received byte is entered as the low byte of the 1. word "data[1]", the 3. received byte as the low byte of the 2.
  • Page 61 VIPA System 300S Communication protocols Modbus > Modbus Master - Function codes 6.4.4.3 FC 03 - Read Output Registers This function serves to read individual registers of the output area of the slave. DB SEND source Address Name Type Comment +0.0 ADDR BYTE...
  • Page 62 VIPA System 300S Communication protocols Modbus > Modbus Master - Function codes DB RCV destination Address Name Type Comment +0.0 data[1] WORD Data +2.0 data[2] WORD Data 6.4.4.5 FC 05 - Force Single Coil This function serves to set or delete individual bits in the output area of the slave. DB SEND source Address Name...
  • Page 63 VIPA System 300S Communication protocols Modbus > Modbus Master - Function codes 6.4.4.7 FC 07 - Read Exception State This function code serves to read 8 event bits of the connected slave. The start bit number of the event bit is determined by the connected slave and does not therefore have to be specified by the user program.
  • Page 64 VIPA System 300S Communication protocols Modbus > Modbus Master - Function codes 6.4.4.9 FC 11 - Fetch Communications Event Counter This function code serves to read the system words "Status word" and "Event counter" from the slave. These words are more described in the "Gould Modbus Protocol". DB SEND source Address Name...
  • Page 65 VIPA System 300S Communication protocols Modbus > Modbus Master - Function codes 6.4.4.11 FC 15 - Force Multiple Coils This function code serves to change up to 2040 (ASCII: 1976) bits in the slave. DB SEND source Address Name Type Comment +0.0 ADDR...

  • Page 66: Modbus Slave - Parameter

    Modbus > Modbus Slave - Parameter 6.4.5 Modbus Slave - Parameter Modbus by loadable driver For deployment of Modbus Slave on the CP 341-1CH01 a loadable driver is neces- sary. This may be downloaded from the Siemens Web site. With deployment of loadable drivers for software technical reason the drivers from Siemens were transferred to the CP but not installed.
  • Page 67 VIPA System 300S Communication protocols Modbus > Modbus Slave - Parameter 6.4.5.1 Modbus Slave Speed Here the transfer speed may be selected from a selection list. Parameter Description Default value Baud rate in bit/s Transfer speed in bit/s 9600 Range of values: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 76800 Character frames The data between the communication partners are transferred via the serial interface by...
  • Page 68 VIPA System 300S Communication protocols Modbus > Modbus Slave - Parameter Protocol parameter Parameter Description Default value Slave address Here the own slave address may be set, which the CP has to respond to. Range of values: 1 ... 255 Operating mode Here the operating mode of the driver may be set.
  • Page 69 VIPA System 300S Communication protocols Modbus > Modbus Slave - Parameter Interface Here it is to specify if the interface is operated in half- (RS485) or full-duplex (RS422) operation. Full-duplex (RS422) – Four-wire operation (default value: active) Data is exchanged between the communication partners in both directions simul- taneously.

  • Page 70: Modbus Slave - Functionality

    VIPA System 300S Communication protocols Modbus > Modbus Slave - Functionality 6.4.6 Modbus Slave - Functionality Overview With Modbus the data transfer happens without any handshake. The master initiates the transmission, and after sending a request message it waits for a reply message from the slave for the duration of the reply monitoring time set.
  • Page 71 VIPA System 300S Communication protocols Modbus > Modbus Slave - Functionality Please consider as soon as you want to access a slave by a writing func- tion code, you have to write enable the corresponding area by the pro- tocol parameters with the dialog "Limits". DATA Here the function code specific data are transferred.
  • Page 72 VIPA System 300S Communication protocols Modbus > Modbus Slave - Functionality Error codes The following error codes are defined in accordance with the Modbus specification: Error code Meaning according to Modbus Cause specification Illegal function Illegal function code Illegal data address Slave has illegal data address Illegal data value Slave has illegal data value...

  • Page 73: Modbus Slave - Communication With The User Program

    VIPA System 300S Communication protocols Modbus > Modbus Slave - Communication with the user program 6.4.7 Modbus Slave - Communication with the user program Overview For the processing of the connecting jobs at slave side a user program is necessary in the CPU.
  • Page 74 VIPA System 300S Communication protocols Modbus > Modbus Slave - Communication with the user program 6.4.7.1 Send data FB 80 - MODB_341 FB 80 - MODB_341 may be called cyclically in the user program. Here it receives the request telegram from the Modbus master, assigns the Modbus address to the appro- priate memory area of the CPU and sends the requested data to the master.
  • Page 75 VIPA System 300S Communication protocols Modbus > Modbus Slave - Communication with the user program CP_START_OK, CP_START_ERROR – As soon as the send job has been completed without error, the output CP_START_OK is set and the FB initialization is complete. –...
  • Page 76 VIPA System 300S Communication protocols Modbus > Modbus Slave - Communication with the user program ERROR_NR ERROR_INFO Error Text (decimal) Amount of Registers Illegal Amount of Registers transferred by the driver to the communication FB: Amount of Registers 128. – Remedy: Check Amount of Registers of Modbus master system, if required restart CP (PowerOn).
  • Page 77 VIPA System 300S Communication protocols Modbus > Modbus Slave - Communication with the user program ERROR_NR 90 ... 99 Other errors – A processing error has occurred and the error is not reported to the driver. Subsequent processing jobs continue to be processed. ERROR_NR ERROR_INFO Error Text...
  • Page 78 VIPA System 300S Communication protocols Modbus > Modbus Slave - Communication with the user program 6.4.7.1.1 Data consistency Data transfer between CPU and CP happens block-by-block by the function blocks FB 7 - P_RCV_RK and FB 8 - P_SND_RK. – Here the block size is about 32byte.

  • Page 79: Modbus Slave - Function Codes

    VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes 6.4.8 Modbus Slave - Function codes Naming convention Modbus has some naming conventions: Modbus differentiates between bit and word access; Bits = "Coils" and Words = "Reg- ister". Bit inputs are referred to as "Input-Status"...
  • Page 80 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes 6.4.8.1 FC 01 - Read Coil Status This function serves to read individual bits of the output area of the CPU by the Modbus master. Request message ADDR FUNC start_addr bit_number...
  • Page 81 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes Address calculation: – Byte address = ((start_addr - Param-start-address) / 8) + PLC-area – Rest-bit-number = (start_addr - Param-start-address) % 8 [Modulo 8] start_addr Access Calculation Area in decimal 0000h Memory...
  • Page 82 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes Calculation Byte address = ((start_addr - Param-start-address) / 8) + PLC-area When accessing bit memories respectively inputs of the CPU, the remaining Rest-bit- number is calculated and used to address the relevant bit within the bit memory area respectively the input area.
  • Page 83 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes 6.4.8.3 FC 03 - Read Output Registers This function enables the Modbus master to read data words from a data block. Request message ADDR FUNC start_register register_number Reply message ADDR FUNC byte_count n...
  • Page 84 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes Conversion For e.g. start_register = 80 (0050h) the conversion takes place with the following approach: start_register = 0050h start_register-offset_DB_no. = 00h start_register-word-no. = 50h Data block DB = Base-DB-Number + start_register-offset_DB_no. –...
  • Page 85 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes 6.4.8.5 FC 05 - Force Single Coil Request message ADDR FUNC oil_addr Data_on/off Reply message ADDR FUNC coil addr Data_on/off coil_addr The Modbus bit address coil_addr contains the start of the area of the CPU, which is be accessed.
  • Page 86 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes 6.4.8.6 FC 06 - Preset Single Register This function enables the Modbus master to write one data word in a data block of the CPU. Please consider as soon as you want to access an area by writing, you have to write enable the corresponding area by the protocol parameters with the dialog "Limits".
  • Page 87 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes Example Conversion Modbus addressing for FC 03, 06, 16 "Modbus address in the transmission message" "SIMATIC memory area" Param-start-address PLC-area from 0 Data blocks commence at DB 800 Calculation For e.g.
  • Page 88 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes 6.4.8.7 FC 08 - Loop Back Diagnostic Test This function serves to check the communications connection. It does not effect the user program. The received message is independently returned to the master by the driver. Request message ADDR FUNC...
  • Page 89 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes 6.4.8.8 FC 15 - Force Multiple Coils This function enables the Modbus master to write several bits to the output area of the CPU. Please consider as soon as you want to access an area by writing, you have to write enable the corresponding area by the protocol parameters with the dialog "Limits".
  • Page 90 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes 6.4.8.9 FC 16 - Preset Multiple Registers This function enables the Modbus master to write several data words in a data block of the CPU. Please consider as soon as you want to access an area by writing, you have to write enable the corresponding area by the protocol parameters with the dialog "Limits".
  • Page 91 VIPA System 300S Communication protocols Modbus > Modbus Slave - Function codes n-Data (High, Low) Any value may be used as n-Data (High, Low). Example Conversion Modbus addressing for FC 03, 06, 16 "Modbus address in the transmission message" "SIMATIC memory area" Param-start-address PLC-area from 0...

  • Page 92: Diagnostics And Error Behavior

    VIPA System 300S Diagnostics and error behavior Diagnostics functions overview Diagnostics and error behavior 7.1 Diagnostics functions overview Overview The diagnostics functions enable you to quickly localize any errors, which occur. The following diagnostics options are available: Diagnostics via the CP-LEDs Diagnostics via FB-STATUS (function blocks) Diagnostics via diagnostic buffer of the CP Diagnostics via diagnostics interrupt...

  • Page 93: Diagnostics Via Fb Status

    VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS 7.2 Diagnostics via FB STATUS Overview Each function block FB 7 - P_RCV_RK and FB 8 - P_SND_RK has a STATUS param- eter for error diagnostics. The STATUS message always has the same meaning, irrespective of which function block is used.
  • Page 94 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 03h "Error parameterization of FBs" (not displayed in diagnostic buffer) Event class / number Description 03 01h Invalid or no source/destination data type Invalid area (start address, length) DB invalid or no DB (e.g.
  • Page 95 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 05h "error while processing CPU request" Event class / number Description 05 01h Current request aborted as a result of CP restart. Remedy: No remedy is possible at PowerON. When re-parameterization of the CP from the programming device, before writing an interface you should ensure there are no more request running from the CPU.
  • Page 96 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 07h "Send error" Event class / number Description 07 06h With 3964(R) only Error at end of connection: Partner rejected message frame at end of connection with NAK or a random string (except for DLE).
  • Page 97 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 08h "Receive error" Event class / number Description 08 05h With 3964(R) only Logical error during receiving: After DLE was received, a further random code (other than DLE or ETX). Remedy: Check whether partner DLE in message frame header and in data string is always in duplicate or the connection is released with DLE ETX.
  • Page 98 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 08h "Receive error" Event class / number Description 08 16h The length of a received message frame was longer than the length agreed upon. Remedy: a correction is necessary at the partner. The length of the parameterized input buffer is too short.
  • Page 99 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 14 (0Eh) "Loadable Driver - General Processing Errors <Processing of a BSEND Job>" Event class / number Description 0E 31h With Modbus Slave only TimeOut during data transfer to CPU. Remedy: Check CP-CPU interface.
  • Page 100 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 14 (0Eh) "Loadable Driver - General Processing Errors <Processing of a BSEND Job>" Event class / number Description 0E 47h With Modbus master only Function codes 15 or 16: The parameter LEN for SFB BSEND does not correspond to the transferred parameters "Amount of Bits"...
  • Page 101 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 14 (0Eh) "Loadable Driver - General Processing Errors <Processing of a BSEND Job>" Event class / number Description 0E 55h With Modbus master only The byte counter received in the reply message is wrong. Remedy: Check slave device.
  • Page 102 VIPA System 300S Diagnostics and error behavior Diagnostics via FB STATUS Event class 30 (1Eh) "Error during communication between CP and CPU via backplane bus" Event class / number Description 1E 0Dh Request aborted due to complete Restart or Reset. 1E 0Eh Static error when the SFC 59 "RD-REC"...
  • Page 103 VIPA System 300S Diagnostics and error behavior Diagnostics via diagnostic buffer 7.3 Diagnostics via diagnostic buffer Overview The CP has its own diagnostic buffer. There all the diagnostic events of the CP are entered in the order in which they occur. The following errors may be reported: Hardware respectively firmware errors Initialization and parameterization errors...
  • Page 104 7.4 Diagnostics by diagnostics interrupt Overview The CP 341-1CH01 can trigger a diagnostics alarm on the assign CPU, thus indicating a malfunction of the CP. You can specify at parameterization whether the CP is to trigger a diagnostics interrupt or not in the event of an error. As default Diagnostics interrupt is deactivated.

This manual is also suitable for:

Vipa system 300s

Table of Contents