Document Outline

• Operating Manual PNOZmulti 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 RS232/ETH interfaces
  • 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)
    • 4.1.2 Output data (from the PNOZmulti)
    • 4.1.3 Note on the PNOZ mc6p (CANopen)
    • 4.1.4 Assignment of Byte 0 ... Byte 3
    • 4.1.5 Assignment of Byte 4 ... Byte 18
      • 4.1.5.1 Example 1
      • 4.1.5.2 Example 2
  • 4.2 PNOZ mc2p, PNOZ mc2.1p, PNOZ mmc11p (SDO and PDO)
    • 4.2.1 Overview
      • 4.2.1.1 PNOZ mc2p
      • 4.2.1.2 PNOZ mc2.1p/PNOZ mmc11p
    • 4.2.2 Object Directory (Manufacturer Specific Profile Area)
      • 4.2.2.1 SDO Index 0x2000
      • 4.2.2.2 SDO Index 0x2001 and Index 0x2002
      • 4.2.2.3 SDO Index 0x2003
      • 4.2.2.4 SDO Index 0x2100
      • 4.2.2.5 SDO Index 0x2004
      • 4.2.2.6 SDO Index 0x2005
  • 4.3 PNOZ mc6p, PNOZ mc6.1p, PNOZ mmc6p, PNOZ mc12p (SDO)
    • 4.3.1 Overview
    • 4.3.2 System requirements
    • 4.3.3 Object Directory
      • 4.3.3.1 Index 2000
      • 4.3.3.2 Index 2001 and 2002
      • 4.3.3.3 Index 2003
      • 4.3.3.4 Index 2004
      • 4.3.3.5 Index 2005
      • 4.3.3.6 Index 2100
  • 4.4 PNOZ mc8p Ethernet IP / Modbus TCP
    • 4.4.1 Introduction
    • 4.4.2 Overview
    • 4.4.3 Module features
    • 4.4.4 Assigning the IP address to your PC
    • 4.4.5 Setting the IP address of the expansion module
    • 4.4.6 Changing IP settings
    • 4.4.7 Data exchange
      • 4.4.7.1 Ethernet IP
      • 4.4.7.2 Modbus TCP
    • 4.4.8 Web interface for commissioning and testing
    • 4.4.9 Restricting access
    • 4.4.10 Input and output data
      • 4.4.10.1 Assigning the inputs/outputs in the PNOZmulti Configurator to the Ethernet IP/Modbus TCP input/output data
  • 4.5 PNOZ mc10p sercos III
    • 4.5.1 Overview
    • 4.5.2 System requirements
    • 4.5.3 Object buffer
      • 4.5.3.1 Output data
      • 4.5.3.2 Diagnostic word
      • 4.5.3.3 Status of the inputs, outputs and LEDs
      • 4.5.3.4 Configuration
      • 4.5.3.5 Element types
      • 4.5.3.6 Input data
      • 4.5.3.7 Diagnostic data
    • 4.5.4 Firmware/FPGA update
    • 4.5.5 Forcing the virtual input data
    • 4.5.6 Communication with the sercos III Master
      • 4.5.6.1 Synchronous data exchange
      • 4.5.6.2 Asynchronous data access
    • 4.5.7 Sercos Master interface
      • 4.5.7.1 Supported profiles
      • 4.5.7.2 Default settings
      • 4.5.7.3 Description of IDNs
      • 4.5.7.4 Communication channels with the PNOZmulti
      • 4.5.7.5 Diagnostics
• 5 RS232/Ethernet interfaces
  • 5.1 Overview
  • 5.2 System requirements
  • 5.3 Interface description
    • 5.3.1 Ethernet interfaces
      • 5.3.1.1 RJ45 interfaces ("Ethernet")
      • 5.3.1.2 Requirements of the connection cable and connector
      • 5.3.1.3 Interface configuration
      • 5.3.1.4 RJ45 connection cable
      • 5.3.1.5 Process data exchange
    • 5.3.2 Serial interface RS232
  • 5.4 Communication procedure
  • 5.5 Telegram structure
    • 5.5.1 Header
    • 5.5.2 Usable data
    • 5.5.3 Information data
  • 5.6 Usable data
    • 5.6.1 Virtual inputs (Input Byte 0 ... Input Byte 15)
      • 5.6.1.1 Mask (Mask Byte 0 ... Mask Byte 15)
      • 5.6.1.2 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 Send virtual inputs to the PNOZmulti
    • 5.7.2 Send virtual inputs to the PNOZmulti, request state of the virtual outputs and LED status from the PNOZmulti
      • 5.7.2.1 Control Byte (Byte 40)
    • 5.7.3 Request state of virtual inputs and outputs from PNOZmulti
    • 5.7.4 Send data from the PNOZmulti in table form
    • 5.7.5 Send input and output data (cf. fieldbus communication)
      • 5.7.5.1 Input data (to the PNOZmulti)
      • 5.7.5.2 Output data (from the PNOZmulti)
      • 5.7.5.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
  • 6.4 Data areas
    • 6.4.1 Overview
    • 6.4.2 Function codes
    • 6.4.3 Data transfer limits
    • 6.4.4 Assignment of data areas
      • 6.4.4.1 Virtual inputs
      • 6.4.4.2 Control Register
      • 6.4.4.3 Virtual outputs
      • 6.4.4.4 LEDs
      • 6.4.4.5 Configuration
      • 6.4.4.6 State of the inputs from the base unit and expansion modules
      • 6.4.4.7 State of the outputs from the base unit and expansion modules
      • 6.4.4.8 LED status
      • 6.4.4.9 Diagnostic word, element types
      • 6.4.4.10 Current state of the virtual inputs
      • 6.4.4.11 Current states of the virtual inputs for the safe Ethernet connection
      • 6.4.4.12 State of process data
      • 6.4.4.13 Safe Ethernet connection
    • 6.4.5 Updating the data areas
    • 6.4.6 Bit addressing in a Register
  • 6.5 Example
• 7 Safe Ethernet connection
  • 7.1 Overview
  • 7.2 System requirements
  • 7.3 Function description
  • 7.4 Configuration in the PNOZmulti Configurator
  • 7.5 Modbus configuration
  • 7.6 Reaction time
  • 7.7 Application guidelines
• 8 Diagnostic word
  • 8.1 Introduction
  • 8.2 Elements with diagnostic word
  • 8.3 Structure of the diagnostic word
  • 8.4 Evaluate diagnostic word
    • 8.4.1 Example
  • 8.5 Compilation of the diagnostic words
    • 8.5.1 Function elements
    • 8.5.2 Cascading
    • 8.5.3 Logic elements
    • 8.5.4 Output elements
• 9 Appendix
  • 9.1 Table assignment
  • 9.2 Table 1
  • 9.3 Table 3
  • 9.4 Table 4
  • 9.5 Table 5
  • 9.6 Table 7
  • 9.7 Table 8
  • 9.8 Table 9
  • 9.9 Table 10
  • 9.10 Table 11
  • 9.11 Element types
• Contact address