Pilz PNOZmulti 2 Operating Manual Download Page 8

Page: 8 / 112

Overview Communication options

Operating Manual Communication interfaces
1002971EN03

Overview Communication options

2.1

Communication via the fieldbus modules

The fieldbus modules provide both cyclical and acyclical data. The chapter entitled

Fieldbus

Modules [

13]

describes the structure of the cyclical data. The chapter entitled

Service

data [

65]

describes the acyclical data, its structure and addressing.

The following device combinations are possible:

Fieldbus modules

Base units

PNOZ m B0

PNOZ m ES Ethernet/IP

PNOZ m ES Profinet

INFORMATION

A maximum of one fieldbus module can be connected to a base unit.

Summary of Contents for PNOZmulti 2

Page 1: ...Communication interfaces Operating Manual 1002971 EN 03 Configurable control systems PNOZmulti 2...

Page 2: ...es may be made for internal purposes Suggestions and comments for improving this documentation will be gratefully received Pilz PIT PMI PNOZ Primo PSEN PSS PVIS SafetyBUS p SafetyEYE SafetyNET p the s...

Page 3: ...ble segments 15 4 1 4 1 Example 1 Access successful 16 4 1 4 2 Example 2 Access failed 17 4 2 PNOZ m ES Profibus 18 4 2 1 Cyclical input and output data 18 4 2 2 Access to table segments 19 4 2 3 LED...

Page 4: ...nput Byte 0 Input Byte 15 38 5 6 2 Watchdog 38 5 6 3 Virtual outputs Output Byte 0 Output Byte 15 38 5 6 4 LED status 38 5 6 5 Tables 39 5 7 Requests 39 5 7 1 Mask Mask Byte 0 Mask Byte 15 39 5 7 2 Se...

Page 5: ...70 8 1 6 1 Process data addressing on base unit 70 8 1 6 2 Process data addressing 1st right hand expansion module 71 8 1 6 3 Process data addressing 2nd right hand expansion module 73 8 1 6 4 Process...

Page 6: ...on module 99 8 6 4 3 Device data addressing 2nd right hand expansion module 100 8 6 4 4 Device data addressing 3rd right hand expansion module 101 8 6 4 5 Device data addressing 4th right hand expansi...

Page 7: ...hazardous situation that could lead to serious injury and death and indicates preventive measures that can be taken CAUTION This refers to a hazard that can lead to a less serious or minor injury plus...

Page 8: ...tled Fieldbus Modules 13 describes the structure of the cyclical data The chapter entitled Service data 65 describes the acyclical data its structure and addressing The following device combinations a...

Page 9: ...scribed in more detail in the chapter entitled Communication modules 32 The following device combinations are possible Communication Module Base units PNOZ m ES RS232 PNOZ m B0 PNOZ m ES ETH INFORMATI...

Page 10: ...access Communication with Modbus TCP is described in detail in the chapter entitled Modbus TCP 51 The following device combinations are possible Communication Module Base unit PNOZ m ES ETH 32 PNOZ m...

Page 11: ...ed and decommissioned by competent persons A competent person is someone who because of their training experience and current pro fessional activity has the specialist knowledge required to test asses...

Page 12: ...ng Manual Communication interfaces 1002971 EN 03 12 3 2 3 Disposal When decommissioning please comply with local regulations regarding the disposal of electronic devices e g Electrical and Electronic...

Page 13: ...ata to the PNOZmulti 2 Double Word Word Byte Content 0 0 0 State of virtual inputs on the PNOZmulti 2 fieldbus module The inputs are defined in the PNOZmulti Configurator Each input that is used is gi...

Page 14: ...module The outputs are defined in the PNOZmulti Configurator Each output that is used is given a number there e g o0 o5 The status of output o0 is stored in bit 0 of byte 0 the status of output o5 is...

Page 15: ...ion Table 90 Device data base unit Table 91 Device data right hand expansion modules Table 92 Device data left hand expansion modules Table 93 Device data fieldbus module communication module The cont...

Page 16: ...essful Access to existing segments The Master requests segment 1 from table 23 The fieldbus module confirms both these de tails and sends segment 1 Then the data from segment 5 table 21 is requested 2...

Page 17: ...r requests segment 1 from table 23 The fieldbus module confirms both these de tails and sends segment 1 Then the Master requests segment 111 from table 23 As this table does not contain a segment 111...

Page 18: ...an be selected individually in the master control system e g virtual inputs i0 31 The data width is also established this way Input data The Master writes to the virtual inputs of the PNOZmulti 2 Desc...

Page 19: ...ed Access to table segments 15 4 2 3 LED status The LED status of the PNOZmulti 2 can be requested directly via the following module Description Output data from PNOZmulti 2 LED status 1 Output Byte B...

Page 20: ...rnal error on the outputs 09 Internal error on the outputs 10 No connection to base unit 11 21 Reserved 22 Error on the base unit 23 Reserved 24 Error on the 1st expansion module right 25 Error on the...

Page 21: ...Internal error on the right hand expansion module F_95 70 Internal self test error F_B0 71 Internal data error F_B1 72 Internal parameter error F_B2 73 Internal serial I2C error F_B3 74 Internal time...

Page 22: ...rrent process data of the CANopen are entered in the object directory of the PNOZmulti 2 These can be read and written via Service Data Objects SDOs To enable the fieldbus module to be incorporated ea...

Page 23: ...2000 2 2 2000 3 3 2000 4 4 2000 5 5 2000 6 6 2000 7 7 2000 8 8 2000 9 TPDO 2 280h node address 9 2000 A 10 2000 B 11 2000 C 12 2000 D 13 2000 E 14 2000 F 15 2000 10 16 2000 11 TPDO 3 380h node addres...

Page 24: ...0h node address 9 2100 A 10 2100 B 11 2100 C 12 2100 D 13 2100 E 14 2100 F 15 2100 10 16 2100 11 RPDO 3 400h node address 17 2100 12 18 2100 13 19 2100 14 20 2100 15 21 2100 16 22 2100 17 23 2100 18 2...

Page 25: ...a areas Process data Base unit and expansion modules Process data Fieldbus module and communication module Diagnostic words Enable elements Project data Device data The content of the service data and...

Page 26: ...ta areas Process data Base unit and expansion modules Process data Fieldbus module and communication module Diagnostic words Enable elements Project data Device data The content of the service data an...

Page 27: ...ables see Service data 65 can be requested via the following mod ules Input data The Master requests a table segment in the form Description Input data from PNOZmulti 2 Table and segment number 2 Inpu...

Page 28: ...Profinet These bits contain the diagnostic data Unit_Diag_ Bit Content 01 STOP base unit is in STOP condition 02 Base unit was stopped by the Configurator 03 Reserved 04 External error 05 Internal err...

Page 29: ...r on the bus module F_85 61 Error on the link module F_86 62 Error on the analogue input module F_87 63 Reserved 64 Error on the input output module F_89 65 Error on the Ethernet module F_8A 66 Intern...

Page 30: ...anation Bits 56 to 91 display the last content of the error stack corresponds to the error class The bits are deleted as soon as PNOZmulti 2 returns to a RUN state 4 7 PNOZ m ES Ethernet IP 4 7 1 Cycl...

Page 31: ...ce Input 101 Output 151 4 7 2 Service data The service data for EtherNet IP is divided into the following data areas Process data Base unit and expansion modules Process data Fieldbus module and commu...

Page 32: ...ter describes the special features of communication with the expansion module PNOZ m ES ETH via Ethernet and Modbus TCP Access to data from the PNOZmulti 2 via tables and segments is described in Chap...

Page 33: ...s are provided as Ethernet interfaces via an internal autosensing switch The autosensing switch automatically detects whether data transfer is occurring at 10 Mbit s or 100 Mbit s INFORMATION The conn...

Page 34: ...m NOTICE With the plug in connection please note that the data cable and connector have a limited mechanical load capacity Appropriate design measures should be used to ensure that the plug in connect...

Page 35: ...i 2 is always the connection s Server in the communication the communica tion partner PC SPS is the Client INFORMATION For communication via Ethernet the Ethernet interface must be set up in the PNOZm...

Page 36: ...2 0x00 2 0x00 3 Payload amount 5 3 Payload amount 5 4 Request No 4 Confirmation error 5 Segment No HB 5 Segment No HB 6 Segment No LB 6 Segment No LB 7 0x00 7 Reserved Payload 8 Payload Byte 0 8 Paylo...

Page 37: ...tes of payload can be transmitted If there is no payload available the BCC Block Control Check will follow directly after Byte 7 The last byte of payload is the byte Payload amount 7 If a telegram con...

Page 38: ...n a defined watchdog time watchdog timeout the PNOZmulti sets the virtual inputs to 0 The configuration and functionality of the watchdog varies and so is described in the re spective requests 5 6 3 V...

Page 39: ...xpansion modules Table 93 Device data fieldbus module communication module The content of the tables is described in detail in the chapter entitled Service data 65 5 7 Requests A request is defined vi...

Page 40: ...25 3 0x05 4 0x14 4 5 0x00 5 0x00 6 0x01 6 0x01 7 0x00 7 0x00 8 Virtual inputs Input Byte 0 i7 to i0 8 0x6B 9 0x10 23 Virtual inputs Input Byte 15 i127 to i120 24 Mask Mask Byte 0 i7 to i0 39 Mask Mask...

Page 41: ...which of the virtual inputs in a Byte are to be set For example if only inputs i0 to i5 are to be set in Byte 8 0x3F must be entered in the mask in Byte 24 Telegram Byte Request Byte Response 0 0x05...

Page 42: ...r Bit2 W Timer Bit1 W Timer Bit0 Bit 0 2 Watchdog Timeout Watchdog Timer Bit 2 Watchdog Timer Bit 1 Watchdog Timer Bit 0 Watchdog Timeout 0 0 0 Timer deactivated 0 0 1 100 ms 0 1 0 200 ms 0 1 1 500 ms...

Page 43: ...ng Manual Communication interfaces 1002971 EN 03 43 INFORMATION The watchdog functions of the requests 0x14 segment 0x02 and 0x5C use the same watchdog timer In other words the watchdog timer is reset...

Page 44: ...5 1 0x15 2 0x00 2 0x00 3 0x05 3 0x26 4 0x2C 4 0xAC 5 0x00 5 0x00 6 0x02 6 0x02 7 0x00 7 0x00 8 0xD2 8 Virtual inputs Input Byte 0 i7 to i0 9 0x10 23 Virtual inputs Input Byte 15 i127 to i120 24 Virtua...

Page 45: ...ules Byte 9 Segment number Example 0x00 for Segment 0 in Byte 4 state of outputs o0 o7 of the right hand ex pansion modules INFORMATION If the requested segment is unavailable the Segment No is set to...

Page 46: ...utput Byte 0 9 Input Byte 1 9 Output Byte 1 10 Input Byte 2 10 Output Byte 2 39 Input Byte 31 39 Output Byte 31 40 0x00 40 Reserved 41 BCC 41 BCC 42 0x10 42 0x10 5 7 6 1 Input data to the PNOZmulti In...

Page 47: ...l inputs are set and a specific table segment is requested in the input data INFORMATION If a fieldbus module is configured virtual inputs cannot be activated via the communication module 5 7 6 2 Outp...

Page 48: ...of the tables and segments is described in detail in the section entitled Service data 65 5 7 6 3 Control Byte Byte 5 Bit 0 2 of the Control Byte contain a watchdog function If no virtual inputs are s...

Page 49: ...s active data cannot be overwritten With read access the watchdog timer is not reset Bit 6 Delayed Response is deactivated INFORMATION The watchdog functions of the requests 0x14 segment 0x02 and 0x5C...

Page 50: ...rs while executing a request the PNOZmulti 2 sends the following response Byte Response 0 0x05 1 0x15 2 0x00 3 0x05 4 Error Code 5 0x00 6 0x00 7 0x00 8 BCC 9 0x10 Error Codes Byte 4 0x62 Request s BCC...

Page 51: ...on Industrial Ethernet TCP IP over Ethernet It is one of the protocols with Client Server communication Data is transferred via a request response mechanism using function codes FC Modbus TCP is conne...

Page 52: ...fieldbus communication are contained in data areas The data is accessed directly It s no longer necessary to switch via table segment PC 192 168 1 60 PMI 192 168 1 10 PSSu System 192 168 1 100 PNOZ m...

Page 53: ...ual output o1 Input Register Word 16 Bits 3x00000 3x65535 read only 3x xxxxx 3x00002 virtual inputs 32 47 Holding Register Word 16 Bits 4x00000 4x65535 read write 4x xxxxx 4x04108 project name 1st cha...

Page 54: ...The connection Client reads word data from the connection Server data length 1 Word content Dia gnostic word data received from 3x FC 05 Write Single Coil The connection Client writes to one bit datum...

Page 55: ...ead Holding Re gisters 1 125 FC 04 Read Input Register Write data Word FC 06 Write Single Register 1 Word FC 16 Write Multiple Re gisters 1 123 Words Read and write data Word FC 23 Read Write Multiple...

Page 56: ...Zmulti 2 Relevant areas for the data are defined in the Modbus TCP data areas Discrete Inputs 1x and Input Register 3x Read access is available to these data areas Register 3x Discrete Input 1x Conten...

Page 57: ...eserved Reserved Bit 15 Watchdog Trigger The watchdog can be triggered by setting Bit 15 constantly to 1 or by a Client writing in the input area of the 128 inputs The state of the bit when read ing i...

Page 58: ...discrete inputs in Registers 512 to 519 Virtual outputs 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 512 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 513 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 514 47 46 4...

Page 59: ...hes Bit 3 1 LED DIAG is lit or flashes Bit 4 1 LED RUN is lit Bit 5 7 Reserved 6 4 8 Updating the data areas Data is updated with varying priority The table below shows the typical update cycles for t...

Page 60: ...Devices with Client role PSSu system in the automation system PSS 4000 Operator terminal PMI PC as programming device for PNOZmulti 2 PSSu system and PMI The PSSu system and the operator terminal PMI...

Page 61: ...Elements with an element ID include Function elements E STOP and safety gate Safety gate with guard locking Light curtain Enabling switch Foot switch Two hand button Operating mode selector switch Lo...

Page 62: ...ontains the diagnostic word as an event message An event message including rem edies actions is defined in the diagnostic type for each event i e for every potential element state The event messages a...

Page 63: ...eldbus Element with ID 1 100 Diagnostic word for element with ID 1 100 Link bit within the user program e g to an output Output Element with ID 1 100 PVIS e g activate Bit 2 and 3 PNOZmulti Configurat...

Page 64: ...0 0000 0100 0000 0000 0000 1000 0000 0000 0001 0000 0000 0000 There is a 1 signal at input 1 0010 0000 0000 0000 There is a 1 signal at input 2 0100 0000 0000 0000 There is a 1 signal at input 3 1000...

Page 65: ...is fol lowed by the fieldbus specific addressing Data ranges Process data Base unit and expansion modules 66 State of inputs i0 i31 67 State of outputs o0 o31 67 Status of system LEDs 67 Status of IO...

Page 66: ...evice data addressing on base unit Addressing type INFORMATION The service data is only updated piecemeal in each cycle by the PNOZmulti Updating all of the data can take up to 500 ms An exception is...

Page 67: ...5 o15 o14 o13 o12 o11 o10 o9 o8 6 o23 o22 o21 o20 o19 o18 o17 o16 7 o31 o30 o29 o28 o27 o26 o25 o24 Fieldbus specific addressing is described in the chapter entitled Process data addressing 70 8 1 3...

Page 68: ...5 I O LED 4 15 I O LED 7 I O LED 6 16 I O LED 9 I O LED 8 17 I O LED 11 I O LED 10 18 I O LED 13 I O LED 12 19 I O LED 15 I O LED 14 20 I O LED 17 I O LED 16 21 I O LED 19 I O LED 18 22 I O LED 21 I O...

Page 69: ...ase unit PNOZ m B0 POWER RUN DIAG FAULT I FAULT O FAULT 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 20 21 22 23 24 25 26 27 16 17 18 19 x x x x IO LED IO LED 0 1 2 3 4 5 System LED Assignment of the I O LED...

Page 70: ...20 0 8 10 I O LEDs 12 23 20 1 0 11 I O LEDs 24 27 20 2 0 3 SDOs Process data SDOs About PNOZmulti Configurator Byte Index Subindex Inputs 0 3 0x2001 1 4 Outputs 4 7 0x2001 5 8 System LEDs 8 10 0x2001...

Page 71: ...tance Attribute Byte Inputs 0 3 1 1 0 3 Outputs 4 7 1 1 4 7 System LEDs 8 10 1 1 8 10 I O LEDs 12 27 1 1 12 27 8 1 6 2 Process data addressing 1st right hand expansion module Tables Process data Table...

Page 72: ...s 4 7 1062 1063 16992 17023 System LEDs 8 10 1064 1065 17024 17047 I O LEDs 12 27 1066 1073 17056 17183 Profinet records Process data Profinet About PNOZmulti Configurator Byte Record Byte Inputs 0 3...

Page 73: ...SDOs About PNOZmulti Configurator Byte Index Subindex Inputs 0 3 0x2002 1 4 Outputs 4 7 0x2002 5 8 System LEDs 8 10 0x2002 9 11 I O LEDs 12 27 0x2002 13 28 Modbus Register Process data Modbus Register...

Page 74: ...0 2 2 8 10 I O LEDs 12 27 2 2 12 27 8 1 6 4 Process data addressing 3rd right hand expansion module Tables Process data Tables About PNOZmulti Configurator Byte Table Segment Byte Inputs 0 3 21 6 0 3...

Page 75: ...About PNOZmulti Configurator Byte Record Byte Inputs 0 3 5 0 3 Outputs 4 7 5 4 7 System LEDs 8 10 5 8 10 I O LEDs 12 27 5 12 27 Ethernet IP instances Process data Ethernet IP About PNOZmulti Configur...

Page 76: ...2002 81 83 I O LEDs 12 27 0x2002 85 100 Modbus Register Process data Modbus Register About PNOZmulti Configurator Byte Register Coil Discrete Input Inputs 0 3 1114 1115 17824 17855 Outputs 4 7 1116 11...

Page 77: ...out PNOZmulti Configurator Byte Table Segment Byte Inputs 0 3 21 12 0 3 Outputs 4 7 21 12 4 7 System LEDs 8 10 21 12 8 10 I O LEDs 12 23 21 13 0 11 I O LEDs 24 27 21 14 0 3 SDOs Process data SDOs Abou...

Page 78: ...O LEDs 12 27 7 12 27 Ethernet IP instances Process data Ethernet IP About PNOZmulti Configurator Byte Instance Attribute Byte Inputs 0 3 2 5 0 3 Outputs 4 7 2 5 4 7 System LEDs 8 10 2 5 8 10 I O LEDs...

Page 79: ...gister Coil Discrete Input Inputs 0 3 1150 1151 18400 18431 Outputs 4 7 1152 1153 18432 18463 System LEDs 8 10 1154 1155 18464 18487 I O LEDs 12 27 1156 1163 18496 18623 Profinet records Process data...

Page 80: ...Os About PNOZmulti Configurator Byte Index Subindex Inputs 0 3 0x2007 1 4 Outputs 4 7 0x2007 5 8 System LEDs 8 10 0x2007 9 11 I O LEDs 12 27 0x2007 13 28 Modbus Register Process data Modbus Register A...

Page 81: ...10 3 1 8 10 I O LEDs 12 27 3 1 12 27 8 1 6 9 Process data addressing 2nd left hand expansion module Tables Process data Tables About PNOZmulti Configurator Byte Table Segment Byte Inputs 0 3 22 3 0 3...

Page 82: ...bout PNOZmulti Configurator Byte Record Byte Inputs 0 3 20 0 3 Outputs 4 7 20 4 7 System LEDs 8 10 20 8 10 I O LEDs 12 27 20 12 27 Ethernet IP instances Process data Ethernet IP About PNOZmulti Config...

Page 83: ...7 81 83 I O LEDs 12 27 0x2007 85 100 Modbus Register Process data Modbus Register About PNOZmulti Configurator Byte Register Coil Discrete Input Inputs 0 3 1384 1385 22144 22175 Outputs 4 7 1386 1387...

Page 84: ...bout PNOZmulti Configurator Byte Table Segment Byte Inputs 0 3 22 9 0 3 Outputs 4 7 22 9 4 7 System LEDs 8 10 22 9 8 10 I O LEDs 12 23 22 10 0 11 I O LEDs 24 27 22 11 0 3 SDOs Process data SDOs About...

Page 85: ...0 3 Outputs 4 7 3 4 4 7 System LEDs 8 10 3 4 8 10 I O LEDs 12 27 3 4 12 27 8 2 Process data Fieldbus and communication module The process data of the fieldbus and communication modules consists of 60...

Page 86: ...chapter entitled Process data addressing 88 8 2 2 State of virtual outputs o0 o127 Byte Bit 7 Bit 0 24 o7 o6 o5 o4 o3 o2 o1 o0 25 o15 o14 o13 o12 o11 o10 o9 o8 26 o23 o22 o21 o20 o19 o18 o17 o16 27 o3...

Page 87: ...EDs 87 Byte Bit 7 Bit 4 Bit 3 Bit 0 48 System LED 1 System LED 0 49 System LED 3 System LED 2 50 Reserved 59 Reserved LED status 4 Bit coding Off 0x0 On 0xF Flashes 0x3 INFORMATION The LED status On a...

Page 88: ...3 0 3 System LEDs 48 49 23 4 0 1 SDOs Process data Tables About PNOZmulti Configurator Byte Index Subindex Inputs 0 15 Outputs 24 39 System LEDs 48 49 0x2009 1 2 Modbus Register Process data Modbus R...

Page 89: ...About PNOZmulti Configurator Byte Table Segment Byte Inputs 0 11 23 5 0 11 Inputs 12 15 23 6 0 3 Outputs 24 35 23 7 0 11 Outputs 36 39 23 8 0 3 System LEDs 48 49 23 9 0 3 SDOs Process data SDOs About...

Page 90: ...e Instance Attribute Byte Inputs 0 15 Outputs 24 39 System LEDs 48 49 8 3 Diagnostic words The diagnostic words contain information about the elements in the PNOZmulti Configur ator The diagnostic wor...

Page 91: ...gnostics 192 199 70 16 0 7 SDOs Process data SDOs About PNOZmulti Configurator Byte Index Subindex Diagnostics 0 119 0x200A 1 120 Diagnostics 120 199 0x200B 1 80 Modbus Register Process data Modbus Re...

Page 92: ...4 ID 3 ID 2 ID 1 1 ID 16 ID 15 ID 14 ID 13 ID 12 ID 11 ID 10 ID 9 2 ID 24 ID 23 ID 22 ID 21 ID 20 ID 19 ID 18 ID 17 3 ID 32 ID 31 ID 30 ID 29 ID 28 ID 27 ID 26 ID 25 4 ID 40 ID 39 ID 38 ID 37 ID 36 ID...

Page 93: ...34400 34503 Profinet records Process data Profinet About PNOZmulti Configurator Byte Record Byte ID 0 12 36 0 12 Ethernet IP instances Process data Ethernet IP About PNOZmulti Configurator Byte Insta...

Page 94: ...16 Day and month DDMM e g 28 11 Byte 16 1C Byte 17 0B 17 18 Year JJJJ e g 2003 Byte 18 14 Byte 19 03 19 20 Time HH MM e g 14 hours 25 minutes Byte 20 0E Byte 21 19 21 22 Time zone 1 Byte 22 0 Byte 23...

Page 95: ...Process data Tables About PNOZmulti Configurator Byte Table Segment Byte Check sums 0 3 80 0 0 3 Date 12 23 80 1 0 11 Project name 24 35 80 2 0 11 Project name 36 47 80 3 0 11 Project name 48 57 80 4...

Page 96: ...gurator Byte Instance Attribute Byte Check sums 0 3 6 1 0 3 Date 12 23 6 1 12 23 Project name 24 57 6 2 0 33 8 6 Device data The device data consists of 36 Bytes 8 6 1 Product Byte About PNOZmulti Con...

Page 97: ...um Firmware Version B 19 20 Reserved 23 Reserved Fieldbus specific addressing is described in the chapter entitled Device data addressing 98 8 6 3 Operating hours The operating hours counter can only...

Page 98: ...Device data SDOs About PNOZmulti Configurator Byte Index Subindex Product 0 11 0x200F 1 12 Firmware 12 19 0x200F 13 20 Operating hours 24 27 0x200F 25 28 Modbus Register Device data Modbus Register A...

Page 99: ...evice data addressing 1st right hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 91 0 0 11 Firmware 12 19 91 1 0 7 SDOs Device data SDO...

Page 100: ...uct 0 11 8 1 0 11 Firmware 12 19 8 1 12 19 8 6 4 3 Device data addressing 2nd right hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 91...

Page 101: ...ct 0 11 8 2 0 11 Firmware 12 19 8 2 12 19 8 6 4 4 Device data addressing 3rd right hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 91...

Page 102: ...ct 0 11 8 3 0 11 Firmware 12 19 8 3 12 19 8 6 4 5 Device data addressing 4th right hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 91...

Page 103: ...ct 0 11 8 4 0 11 Firmware 12 19 8 4 12 19 8 6 4 6 Device data addressing 5th right hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 91...

Page 104: ...t 0 11 8 5 0 11 Firmware 12 19 8 5 12 19 8 6 4 7 Device data addressing 6th right hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 91 1...

Page 105: ...uct 0 11 8 6 0 11 Firmware 12 19 8 6 12 19 8 6 4 8 Device data addressing 1st left hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 92...

Page 106: ...uct 0 11 9 1 0 11 Firmware 12 19 9 1 12 19 8 6 4 9 Device data addressing 2nd left hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 92...

Page 107: ...ct 0 11 9 2 0 11 Firmware 12 19 9 2 12 19 8 6 4 10 Device data addressing 3rd left hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 92...

Page 108: ...ct 0 11 9 3 0 11 Firmware 12 19 9 3 12 19 8 6 4 11 Device data addressing 4th left hand expansion module Tables Device data Tables About PNOZmulti Configurator Byte Table Segment Byte Product 0 11 92...

Page 109: ...nfigurator Byte Instance Attribute Byte Product 0 11 9 4 0 11 Firmware 12 19 9 4 12 19 8 6 4 12 Device data addressing fieldbus module Device types PROFIBUS 0x0001 CANopen 0x0020 Ethernet IP 0x0083 PR...

Page 110: ...oduct 0 11 8624 8629 Firmware 12 19 8630 8633 Profinet records Device data Profinet About PNOZmulti Configurator Byte Record Byte Product 0 11 64 0 11 Firmware 12 19 64 12 19 Ethernet IP instances Dev...

Page 111: ...ice data Modbus Register About PNOZmulti Configurator Byte Register Coil Discrete Input Product 0 11 8642 8647 Firmware 12 19 8648 8651 Profinet records Device data Profinet About PNOZmulti Configurat...

Page 112: ...mo PMCprotego PMCtendo PMD PMI PNOZ Primo PSEN PSS PVIS SafetyBUS p SafetyEYE SafetyNET p the spirit of safety are registered and protected trademarks of Pilz GmbH Co KG in some countries We would poi...

Search results

Summary of Contents for PNOZmulti 2

Reviews:

Related manuals for PNOZmulti 2

Brands by name

Popular brands

Pilz PNOZmulti 2, Operating Manual

Search results

Summary of Contents for PNOZmulti 2

Reviews:

Related manuals for PNOZmulti 2

Brands by name

Popular brands