Document Outline

• Operating Manual PNOZmulti 2 Communication Interfaces
• Preface
• Contents
• 1 Introduction
  • 1.1 Definition of symbols
• 2 Overview - Communication options
  • 2.1 Communication via the fieldbus modules
  • 2.2 Communication via the communication modules
  • 2.3 Communication via Modbus TCP
• 3 Safety
  • 3.1 Intended use
  • 3.2 Safety regulations
    • 3.2.1 Use of qualified personnel
    • 3.2.2 Warranty and liability
    • 3.2.3 Disposal
• 4 Fieldbus Modules
  • 4.1 Basics
    • 4.1.1 Input data (to the PNOZmulti 2)
    • 4.1.2 Output data (from the PNOZmulti 2)
    • 4.1.3 Overview of tables
    • 4.1.4 Access to table segments
      • 4.1.4.1 Example 1 - Access successful
      • 4.1.4.2 Example 2 - Access failed
  • 4.2 PNOZ m ES Profibus
    • 4.2.1 Input and output data
    • 4.2.2 Access to table segments
    • 4.2.3 LED status
    • 4.2.4 Diagnostic data PNOZ m ES Profibus
  • 4.3 PNOZ m ES CANopen
    • 4.3.1 Service Data Objects (SDOs)
    • 4.3.2 Process Data Objects (PDOs)
  • 4.4 PNOZ m ES EtherCAT
    • 4.4.1 Service Data Objects (SDOs)
    • 4.4.2 Process Data Objects (PDOs)
  • 4.5 PNOZ m ES Powerlink
    • 4.5.1 Service Data Objects (SDOs)
    • 4.5.2 Process Data Objects (PDOs)
• 5 Communication modules
  • 5.1 Overview
  • 5.2 PNOZ m ES RS232
  • 5.3 PNOZ m ES ETH
    • 5.3.1 Introduction
    • 5.3.2 Overview
    • 5.3.3 Module features
    • 5.3.4 Modbus/TCP
    • 5.3.5 RJ45 interfaces ("Ethernet")
    • 5.3.6 Requirements of the connection cable and connector
    • 5.3.7 Interface configuration
    • 5.3.8 RJ45 connection cable
    • 5.3.9 Process data exchange
  • 5.4 Communication procedure
  • 5.5 Telegram structure
    • 5.5.1 Header
    • 5.5.2 Usable data
    • 5.5.3 Footer
  • 5.6 Usable data
    • 5.6.1 Virtual inputs (Input Byte 0 ... Input Byte 15)
      • 5.6.1.1 Watchdog
    • 5.6.2 Virtual outputs (Output Byte 0 ... Output Byte 15)
    • 5.6.3 LED status
    • 5.6.4 Tables
  • 5.7 Requests
    • 5.7.1 Mask (Mask Byte 0 ... Mask Byte 15)
    • 5.7.2 Send virtual inputs to the PNOZmulti
    • 5.7.3 Send virtual inputs to the PNOZmulti, request state of the virtual outputs and LED status from the PNOZmulti
      • 5.7.3.1 Control Byte (Byte 40)
    • 5.7.4 Request state of virtual inputs and outputs from PNOZmulti
    • 5.7.5 Request data from the PNOZmulti in table form
    • 5.7.6 Send input and output data (cf. fieldbus communication)
      • 5.7.6.1 Input data (to the PNOZmulti)
      • 5.7.6.2 Output data (from the PNOZmulti)
      • 5.7.6.3 Control Byte (Byte 5)
  • 5.8 Troubleshooting
    • 5.8.1 Request format does not meet specifications
    • 5.8.2 Error while executing a request
• 6 Modbus/TCP
  • 6.1 System requirements
  • 6.2 Modbus/TCP - Basics
  • 6.3 Modbus/TCP with PNOZmulti 2
  • 6.4 Data areas
    • 6.4.1 Overview
    • 6.4.2 Function codes
    • 6.4.3 Data transfer limits
    • 6.4.4 Input and output data, watchdog
    • 6.4.5 Allocation table of the virtual inputs and outputs
    • 6.4.6 Process data, base unit
    • 6.4.7 Process data, right-hand expansion modules
    • 6.4.8 Process data, left-hand expansion modules
    • 6.4.9 Process data, fieldbus and communication module
    • 6.4.10 Diagnostic words
    • 6.4.11 Enable elements
    • 6.4.12 Project data
    • 6.4.13 Device data, base unit
    • 6.4.14 Device data, right-hand expansion modules
    • 6.4.15 Device data, left-hand expansion modules
    • 6.4.16 Device data, fieldbus and communication module
    • 6.4.17 LEDs
    • 6.4.18 Updating the data areas
  • 6.5 Examples of Clients and Servers
• 7 Diagnostic word
  • 7.1 Introduction
  • 7.2 Elements with diagnostic word
  • 7.3 Structure of the diagnostic word
  • 7.4 Evaluate diagnostic word
  • 7.5 Example - Evaluate diagnostic word of a safety gate
• 8 Appendix
  • 8.1 Tables
    • 8.1.1 Table 20 - Process data, base unit
    • 8.1.2 Table 21 - Process data, right-hand expansion modules
    • 8.1.3 Table 22 - Process data, left-hand expansion modules
    • 8.1.4 Table 23 - Process data, fieldbus and communication module
    • 8.1.5 Table 70 - Diagnostic words
    • 8.1.6 Table 71 - Enable elements
    • 8.1.7 Table 80 - Project data
    • 8.1.8 Table 90 - Device data, base unit
    • 8.1.9 Table 91 - Device data, right-hand expansion modules
    • 8.1.10 Table 92 - Device data, left-hand expansion modules
    • 8.1.11 Table 93 - Device data, fieldbus and communication module
  • 8.2 Object directory, Service Data Objects (SDOs)
    • 8.2.1 Structure of the object directory
    • 8.2.2 Output data - SDO Index 0x2000
    • 8.2.3 Process data, base unit and 1st right-hand expansion module - SDO Index 0x2001
    • 8.2.4 Process data, 2nd ... 4th right-hand expansion module - SDO Index 0x2002
    • 8.2.5 Process data, 5th ... 6th right-hand expansion module - SDO Index 0x2003
    • 8.2.6 Process data, 1st ... 3rd left-hand expansion module - SDO Index 0x2007
    • 8.2.7 Process data, 4th left-hand expansion module - SDO Index 0x2008
    • 8.2.8 Process data, fieldbus - SDO Index 0x2009
    • 8.2.9 Diagnostic words - SDO Index 0x200A
    • 8.2.10 Diagnostic words and enable elements - SDO Index 0x200B
    • 8.2.11 Project data - SDO Index 0x200D
    • 8.2.12 Device data, base unit and 1st right-hand expansion module - SDO Index 0x200F
    • 8.2.13 Device data, 2nd ... 4th right-hand expansion module - SDO Index 0x2010
    • 8.2.14 Device data, 5th ... 6th right-hand expansion module - SDO Index 0x2011
    • 8.2.15 Device data, 1st ... 3rd left-hand expansion module - SDO Index 0x2015
    • 8.2.16 Device data, 4th left-hand expansion module - SDO Index 0x2016
    • 8.2.17 Device data, fieldbus and communication module - SDO Index 0x2017
    • 8.2.18 Input data - SDO Index 0x2100
  • 8.3 Assignment of system and I/O-LEDs
• Contact address