Home

Quantum

1. 140 CPU 434 12 IN1 MOVE OUT1 pk OA 622 Remote bus branch IN1 CPU scan time 10 ms Rerrote bus 170 DAI 340 Remote bus branch TSX Quantum with INTERBUS Master Response time OUT 4 170 DAO 840 The table shows the various elements used to calculate the response time of the application with the 140 NOA 622 00 Number of I O words 1 33 65 129 Number of modules 2 18 34 66 CPU scan time in ms 3 00 5 00 8 00 10 00 Application response time in ms 9 00 to 18 00 to 30 00 to 44 00 to 13 00 26 00 40 00 74 00 26 840 USE 497 00 June 2005 Performance Data Transfer Rate per Station Data transfer rate The data transfer rate depends on the bandwidth of the PCP channel 1 byte control information n bytes user data and from the INTERBUS polling time A bandwidth of and a polling time of results in a data rate of one word per cycle via the PCP channel 3 27 ms 2 45 kbit s 4 94 ms 1 62 kbit s 8 27 ms 0 97 kbit s two words per cycle viathe 3 27 ms 7 34 kbit s PCP channel 4 94 ms 4 86 kbit s 8 27 ms 2 90 kbit s four words per cycle via 3 27 ms 17 13 kbit s the PCP channel 4 94 ms 11 34 kbit s 8 27 ms 6 77 kbit
2. Master Device 140 NOA 622 00 Device0 Node No 10 Device 0 170 ADI 340 00 Device1 Node No 2 0 Device 1 170 BNO 671 01 H Device2 AS Node No 3 0 Device 2 170 ADO 340 00 A I H Device3 E Node No 4 0 Device 3 170 AMM 090 00 840 USE 497 00 June 2005 55 Commissioning Step Action Performed Save the project and close SyCon Result The INTERBUS configuration data is accepted by Concept when SyCon is closed The list of nodes is displayed in the dialog box Generic Bus Master Interbus Board x Generic Bus Master Interbus Board 0 r Master Slave Slaves 4 Description INTERBUS G4 Master as NOA622 Last slave 3 Status table 0 Activate table 0 Previous Next Conf start Import Settings Settings Parameter Node Slave Mod Cha Description 170 ADI 340 00 1 1 Devicel 1 170 BNO 671 01 0 0 Device2 2 170 ADO 340 00 171 Device3 3 170 AMM 090 00 213 Device4 OK Cancel Help Note If Concept is Not Connected a change to the Bus configuration in SyCon or anew Save in SyCon without changes being made means that the Concept project is not the same and must be reloaded 56 840 USE 497 00 June 2005 Commissioning Editing the bus You must now make the following entries for the INTERBUS configuration now in
3. Topic Page Accessories and Replacement Parts for Software 36 Accessories and Replacement Parts for Copper Lines 36 Accessories and Replacement Parts for Fibre Optic Cable Technology 37 840 USE 497 00 June 2005 35 Accessories and Replacement Parts Accessories and Replacement Parts for Software Software Components Installing Accessories and Replacement Parts Term Order no Sycon configuration software assignment for Schneider Automation SYC SPU LF CD28M Accessories and Replacement Parts for Copper Lines Components for copper lines List of accessories and replacement parts Term Order no Programming cable for 140 NOA 622 00 3 7 m Modbus cable 990 NAA 263 20 INTERBUS cable 100 cm 170 MCI 100 00 Remote bus cable 100 m TSX IBSCA 100 Remote bus cable 400 m TSX IBSCA 400 Remote bus cable Meterware LiYCY 3x2x0 25 mm KAB3225LI INTERBUS plug set 9 pin D SUB plug plus socket 170 XTS 009 00 Branch interface for remote bus branch copper cable 170 BNO 671 0x 36 840 USE 497 00 June 2005 Accessories and Replacement Parts Accessories and Replacement Parts for Fibre Optic Cable Technology Components for Fibre Optic Technology The following components are available for the connection with fiber optic technology Term Order no Branch interfa
4. Local bus The following tables contain INTERBUS local bus systems technical data technical data Transfer properties Transfer procedures TTL Possible transfer media Special cable CU shielded twisted pair 14 conductor Transfer rate 500 kbit s Physical Attributes Maximum length of the cable the branch interface and the first module 1 5 m between two modules 1 5m the branch interface and the last module 10m Electrical data Power consumption of a device 20 to 250 mA Maximum power consumption 800 mA Capacitance Number of input output modules Maximum 8 modules Groups Possible Supply for I O modules Supply voltage via bus cable or externally Note Inline modules are configured as local bus nodes in SysCon For performance characteristics and configuration details please refer to the manufacturers specifications INTERBUS Loop With the INTERBUS loop remote sensors and actuators distributed on machines and systems or e g modules with safety type IP67 are networked in a closed ring 840 USE 497 00 June 2005 21 General INTERBUS loop technical data The following tables contain INTERBUS loop system technical data Transfer properties Transfer procedures Modulated current signal Possible transfer media CU unshielded 2 conductor Transfer rate 500 kbit s Physical Attributes Maximum length of the cab
5. BOOL 1 an error occurred during the read operation The error status can be found in the STATUS parameter STATUS WORD Specifies the error status for further information refer to the section called Runtime error p 98 lt Status gt 0 Module inactive a read operation is being executed or a read operation has successfully completed PCP_Data ANY The data read from the PCP node is stored here Enter a variable here to define the required data type The data itself is always stored in n consecutive 4x registers n LENGTH number of bytes to be read 840 USE 497 00 June 2005 97 IBS_READ Runtime error Error codes in The following messages are displayed in the STATUS parameter of the EFB PCP protocol Error number Hex Dec Explanation 0x00 0 No error 0x41 65 ALI INITIATE ERR Connection could not be activated The connection must be activated on the first request by sending an initialization telegram If the remote bus node does not confirm the initialization the connection cannot be activated and the request is rejected with this error 0x43 67 ALI REJECT PAR SRV Too many parallel services at a communications reference CR 0x45 69 ALI REJECT PDU LENGTH Requested PDU length exceeds the maximum length configured 0x46 70 ALI REJECT SRV NOT SUPPORT Requested Service not supported by the Master 0x
6. 15 0 corresponding module does not run error free Bit 0 15 1 corresponding module runs error free 74 840 USE 497 00 June 2005 Configuration and Diagnostics Word 3x 25 to The diagnosis status of the configured slaves up to 251 is registered in these 16 word 3x 40 words as follows Word Slave address 3x 25 0 15 3x 26 16 31 3x 27 32 47 3x 39 224 239 3x 40 240 250 Assignment of the slave addresses to the bits 151141131121111100 9 8 7 6 5 8 2 1 0 Word 3x 25 3x 26 3x 27 3x 39 3x 40 Bit Slave address 0 0 16 32 224 240 1 1 17 33 225 241 2 2 18 34 226 242 3 3 19 35 227 243 4 4 20 36 228 244 10 10 26 42 234 250 11 11 27 43 235 14 14 30 46 238 15 15 31 47 239 Bit 0 15 0 there is no diagnosis message for the corresponding module Bit 0 15 1 there is a diagnosis message for the corresponding module 840 USE 497 00 June 2005 75 Configuration and Diagnostics Error numbers The following tables shows the error numbers for the Master Highbyte from 3x 2 for the Master 255 Error number Description dec hex 0 0 No error 52 34 Unknown process data handshake 56 38 No configuration found 57 39 The INTERBUS processor chip is defective or
7. 44 Description of the Reset Button Communication Module 140 NOA 622 00 44 Diagnostic query on the INTERBUS Master 140 NOA 622 00 101 Diagnostics Communication Module 140 NOA 622 00 44 Diagram of the Display Communication Module 140 NOA 622 00 44 E Error codes PCP protocol 98 EXECLoader 66 F Firmware 65 Direct Load 65 Load via CPU 65 G General 13 Groups 84 IBS_NOA IBS_READ 95 IBS_SEND_REQ 101 IBS_WRITE 113 IBS_READ 95 IBS_SEND_REQ 101 IBS_WRITE 113 Import CMD G4 Project 129 Installation Remote Bus 20 INTERBUS 140 NOA 622 00 as Master 30 Architecture 25 Cycle Times 25 Protocol 24 Protocol Format 24 Telegrams 25 INTERBUS Loop 21 INTERBUS Master Modules Overview 33 Properties 33 Software Requirements 34 INTERBUS nodes Switching 61 L Local Bus 21 Mounting Communication Module 140 NOA 622 00 45 N Network Control 25 Operation 25 Timing 25 NOA 622 00 Software Startup 53 O Operating Elements 140 NOA 622 00 43 Communication Module 43 Overview INTERBUS 14 136 840 USE 497 00 June 2005 Index P PCP Protocol 25 PCP channel 79 Using 80 PCP protocol Error codes 98 Performance 23 Peripheral Communication Protocol 25 Protocol Format INTERBUS 24 INTERBUS 24 PCP 25 R Reading variables via INTERBUS 95 Remote Bus 17 Remote Bus Branch 18 Replacement Part Fibre Optic Cable 37 Replacement Parts for Copper
8. When the bus is in operation individual nodes segments groups and alternative branches can be added or switched off The nodes to be switched are specified viaactivate word 4x 1 See Activate p 69 in Concept The switching operation effects the specified nodes and all the nodes which depend on it i e all INTERBUS nodes e which belong to the same bus segment e which belong to the same group e which are after an activated INTERBUS node in the physical ring If for example you switch off a branch interface module always switch off all remote bus nodes which follow it including the branch on the branch interface module CAUTION INTERBUS node for the SUPI 1 generation cause errors in the switching procedures for the entire INTERBUS architecture Nodes from the SUPI 1 generation cannotbe used with the INTERBUS architecture if any node of the configuration has to be switched Failure to follow this precaution can result in injury or equipment damage 840 USE 497 00 June 2005 61 Commissioning Addressing Modes of the Inputs and Outputs Overview In Concept addresses for each module are assigned individually therefore this is not really physical addressing Only logical addressing is used in Concept according to the definition because the modules are assigned to the respective registers Quasi physical addressing can be achieved by only using Ox 1x or 3x 4x registers and assigning them to th
9. and 3x 4x Range Bit order in state RAM 3x 4x Bit order in INTERBUS Word viewed using Bus Configuration Tool IEC Mode and 984 Mode The addressing of analog I O modules takes place according to the following 15 14 13 12 11 10 15 Binary 8 Bit I O Module in 0x 1x and 3x 4x Range Bit order in state RAM Bit order in INTERBUS Word viewed using Bus Configuration Tool Inputs Outputs on terminals Bit order in state RAM Bit order in INTERBUS Word viewed using Bus Configuration Tool Inputs Outputs on terminals The addressing of 8 bit modules in the example for the 170 ADM 390 30 8 outputs takes place according to the following scheme IEC Mode 3x 4x and 984 Mode 0x 1x 15 14 13 12 11 10 9 8 T 984 Mode 3x 4x and IEC 0x 1x AR w D i4 o WS zt fake NES MES SION 9 amp v a 13 2 o iY i 15114113 12 11 10 9 8 a e 2 i oO ab ey 2 a oO 64 840 USE 497 00 June 2005 Comm
10. configuration in Concept Concept Step Action Performed 1 In the dialog field enter Generic Bus Master Interbus Board x for every IBS slave in Slave Parameter State RAM addresses You can switch between the individual slave nodes in the dialog box Slave Parameter using lt lt Previous and Next gt gt Slave Parameter r Slave Address 3 lt lt Previous Next gt gt Name 170 AMM 090 00 Description Device4 Channel Length Word 5 Settings Mod Cha Type In Ref In End Out Ref Out End ET 800 100097 100176 2 1 PARAM Y 2 2 BOOL v 400120 1400122 OK Cancel Help 2 You can enter values for Params in the area Channel in Settings Channel s parameter s Module 2 Channel 1 State RAM values Here configured value s Special Word Dec Hex Bin 1 17476 4444 0100010001000100 2 68 0044 0000000001000100 OK Cancel Help 840 USE 497 00 June 2005 57 Commissioning Step Action Performed Check and if necessary make changes to the settings in Master under Settings for Timeout and Bus startup behavior Master s Settings Name Interbus Board No 0 Description INTERBUS G4 Master as NOA622 Address 255 r Cycle for 1 0 synchronization r General Setting
11. 4x reference here as the start address for a range of 25 consecutive words Overview of the activation words Word Significance 4x Control activities See Word 4x p 70 4x 1 Node no from Concept of the node for which activity entered in word 4x should be carried out Area 0 250 4x 2 Reserved 4x 24 Note If you add your INTERBUS configuration to Concept using the command Import the bus table for the generic bus is completely recreated i e the activation area is deleted assignment to INTERBUS and content of the words 840 USE 497 00 June 2005 69 Configuration and Diagnostics Word 4x The bits of word 4x have the following meaning 1514113112 11 109 8 7 6 5143 2 11 0 Bit Significance Word 4x hex 0 7 Reserved 8 1 Start INTERBUS 100 9 1 Stop INTERBUS 200 10 1 disconnect the node specified in 4x 1 400 11 1 connect the node specified in 4x 1 800 12 15 Reserved CAUTION Setting the bits at the same time can lead to erroneous behavior The control bits in word 4x may only be set individually as the functions cannot be uniquely mapped for bits which are set concurrently Failure to follow this precaution can result in injury or equipment damage 70 840 USE 497 00 June 2005 Configuration and Diagnostics Details abou
12. Addressing Modes of the Inputs and Outputs 62 Firmware for the INTERBUS Master 65 840 USE 497 00 June 2005 51 Commissioning Principle of Commissioning Overview To commission an INTERBUS system the definition of the physical environment where the application will be intigrated is needed e g backplane power supply processor modules or devices etc Then the commissioning of the configuration with the respective software takes place The master configuration is made using Concept starting with version 2 5 SR2 The configuration of the bus takes place with the help of the configuration software SyCon Principle of The following table describes the individual phases of commissioning commissioning Phase Software Description Mounting the The module is inserted in the desired slot in the central backplane 140 NOA 622 00 PLC configuration Concept The following entries must be made Enter the NOA 622 in the I O map Enter the configuration parameters for the INTERBUS master number and slot bus start behavior e Configuration of the generic bus incl SyCon software call Bus configuration SyCon The following steps must be carried out Enter read the bus configuration with the SyCon software Generate the configuration file IB and load the file in Concept takes place automatically when ending the SyCon software Assigning the signal Concept Assigning the signal memory to the INT
13. BOOL UINT CR ERROR BOOL UINT INDEX STATUS WORD BYTE J SUBINDEX BYTE LENGTH PCP Data ANY 96 840 USE 497 00 June 2005 IBS_READ Parameter Description of parameters ription descriptio Parameter Data type Meaning START BOOL 1 Reading the data from the specified INTERBUS PCP Slave is started The parameter must remain 1 until the operation is completed If the parameter remains 1 after the operation is completed the EFB starts a new read operation in the next PLC cycle Note If the parameter is set to 0 before the end of the operation the operation is stopped SLOT BYTE Specifies the slot address of the corresponding INTERBUS Master NOA 622 00 in the Quantum rack CR UINT Communications reference of the PCP node as defined in the configuration tool INDEX UINT Logical address of the PCP node this address is specified in the manufacturer s documentation SUBINDEX BYTE Logical address defined for each element of the specified PCP node this address is specified in the manufacturer s documentation LENGTH BYTE Number of bytes to be read from the PCP node ACTIVE BOOL This binary output is set to 1 as long as the read operation is being executed It is set to 0 when the operation has successfully completed or if an error occurs DONE BOOL 1 a read operation has been terminated without error ERROR
14. Device x blocked The response block for the REQUEST parameter has the following entries Variable type Value Description msg rx Byte 16 Receiver Node on the HOST msg tx Byte 3 Source Node IBM Task msg In Byte x Message Length msg nr Byte j Message Number msg a Byte 76 Response IBM_Set_Configuration msg f Byte Error status see Change error numbers configuration p 110 msg b Byte 0 No Operation msg e Byte Not used 840 USE 497 00 June 2005 109 IBS_SEND_REQ Change error numbers configuration Error number Error number Description hex dec Description 0 0 no error 65 101 An active slave reports a false ID or length code or is missing 67 103 The configuration was changed during the ID scan 68 104 More slaves than expected were detected in a branch 69 105 Timeout when opening an INTERBUS branch 6B 107 Configuration was changed during the runtime a running slave no longer responds 9A 154 The following error are triggered msg In and the number of slaves configured does not match or not all local bus nodes in the local bus are blocked or e following remote bus nodes are not blocked 110 840 USE 497 00 June 2005 IBS_SEND_REQ Request Response blocks for connecting disconnecting INTERBUS nodes You can use these blocks to connect or disconnect INTERBUS nodes groups or branche
15. Lines 36 Replacement Parts for Software 36 Response Time 26 Runtime error 98 S Shutdown Procedure 60 Software 49 Software Accessories 36 Startup Procedure 60 Status Word Generic Bus 71 Switch off behavior 60 Parameterization in Concept 61 Switching Alternatives 91 Gruppen 86 Switching INTERBUS nodes 61 T Technical Data 48 Topology 15 U Upgrading from NOA 611 x0 Instructions 127 W Writing variables to INTERBUS PCP nodes 113 840 USE 497 00 June 2005 137 Index 138 840 USE 497 00 June 2005
16. Page 10 IBS_READ Reading variables via INTERBUS 95 11 IBS SEND REQ Diagnostic query on the INTERBUS Master 101 140 NOA 622 00 12 IBS WRITE Writing variables to INTERBUS PCP nodes 113 840 USE 497 00 June 2005 93 EFB Descriptions 94 840 USE 497 00 June 2005 IBS_READ Reading variables via INTERBUS 10 Overview Introduction This chapter describes the IBS_READ block What s in this This chapter contains the following topics 9 Chapter Topic Page Brief Description 96 Representation 96 Runtime error 98 840 USE 497 00 June 2005 95 IBS_READ Brief Description Function Description Representation You can use this function block to read data into the status RAM of the PLC from a PCP slave connected via the INTERBUS Several function blocks can be configured at the same time but of these at most 4 can be active at the same time For these different communication references parameter CR or the same communications reference with different logical addresses parameter index subindex can be assigned see Parameter description p 97 However for all actual parameters of the individual modules different addresses must be configured Note EN and ENO should not be used together with this EFB otherwise output parameters can become fixed Symbol Block representation IBS_READ BOOL START ACTIVE BOOL BYTE J SLOT DONE
17. a branch all nodes must have the same group number with the exception of the branch interface module where the branch diverges The branch interface module itself may not be assigned to a group CAUTION A remote bus node in the main branch of the INTERBUS architecture may not be assigned to a group If this node was assigned to a group none of the other nodes can be activated individually Switching on an off a group via the individual nodes and via the branch interface module is also not possible in this case The configuration software does not check if the group assignment is allowed This must be checked by the user Failure to follow this precaution can result in injury or equipment damage 84 840 USE 497 00 June 2005 Groups and Alternatives INTERBUS architecture with group definition INTERBUS network with groups Display in SyCon lie I gt i HF Master Device Device0 Node no Device 0 Device1 Node no Device 1 Device2 Node no Device 2 Device3 Node no Device 3 Device4 Node no Device 4 Devices Node no Device 5 Device6 Node no Device 6 Device7 Node no Dev
18. a fibre optic connection the last control stage of the optical diode is reached to guarantee error free INTERBUS transfer Note This bit is set independently of the transfer medium copper wire or LWL if the INTERBUS node belongs to different SUPI generations i e if a SUPI 3 OPC INTERBUS node comes after a SUPI 2 node In this instance the bit has no meaning MFAIL MAU Medium Access Unit FAIL At least one Slave has reported a hardware error in the INTERBUS wiring PUE POWER UP EVENT for SUPI 3 INTERBUS node only A voltage dip was discovered at a Slave during the runtime Reserved 840 USE 497 00 June 2005 73 Configuration and Diagnostics Word 3x 9 to The Health Status of the up to 251 configured slaves is registered in these 16 words word 3x 24 as follows Word Slave address 3x 9 0 15 3x 10 16 31 3x 11 32 47 3x 23 224 239 3x 24 240 250 Assignment of the slave addresses to the bits 15 14 13 12 11 109 8 7 6 5 3 2 11 0 Word 3x 9 3x 10 3x 11 3x 23 3x 24 Bit Slave Address 0 0 16 32 224 240 1 1 17 33 225 241 2 2 18 34 226 242 3 3 19 35 227 243 4 4 20 36 228 244 10 10 26 42 234 250 11 11 27 43 235 14 14 30 46 238 15 15 31 47 239 Bit 0
19. bus is isolated from the remote bus Often I O nodes on the installation remote bus have a special safety type e g IP65 IP67 etc The I O modules on the installation remote bus are special modules that cannot be used on the remote bus The following tables contain INTERBUS installation remote bus technical data Transfer properties Transfer procedures RS 485 connection Possible transfer media Special cable Cu shielded twisted pair 8 conductor welding resistant which is suited for e the supply of input output modules and sensors with 24 V e the data transfer Transfer rate 500 kbit s Physical Attributes Maximum length of the cable between the branch interface and the first module 50m the branch interface and the last module 50m Electrical data Maximum current load on the cable 4 5 A Capacitance Number of input output modules Maximum 251 Groups Possible groups can be switched off Supply for I O modules Supply voltage also applied via the I O bus 20 840 USE 497 00 June 2005 General Local Bus The local bus LB peripheral bus is generated by specific branch interfaces The modules on the local bus are I O modules used to create a remote substation in a switching cabinet Products from other manufacturers using peripheral bus technology can be coupled on the 140 NOA 622 00
20. connector from the 140 NOA 611x0 and remove the module from the module rack 4 Insert the 140 NOA 622 00 in a free slot and connect the IBS cable to the corresponding connection 5 Turn the controller on again Adjustments in Changes must also be made to Concept for the upgrade to 140 NOA 622 00 Concept The following table describes the separate phases of the changes Phase Description PLC configuration The following entries must be made Configuration of the generic bus incl SyCon software call Enter the configuration parameters of the INTERBUS Master number and slot bus start behavior as you set in the 140 NOA 611 10 configuration e Changing the entries in the I O map 140 NOA 611 10 replace with 140 NOA 622 00 Bus configuration The following steps must be carried out Enter read the bus configuration with the SyCon software Generate the configuration file IB and load the file to Concept happens automatically when closing the SyCon software if it was started from Concept Assigning the signal Assign the same state RAM addresses to the INTERBUS modules memory as in the 140 NOA 611 10 configuration The precise sequence of the individual phases can be found in section Software Startup for using the 140 NOA 622 00 p 53 840 USE 497 00 June 2005 127 Upgrading from 140 NOA 611 x0 to 140 NOA 622 00 Required Because of the changed INTERBUS processi
21. contains the following chapters Chapter Chapter Name Page A Example for diagnosis and control of a slave 119 B Upgrading from 140 NOA 611 x0 to 140 NOA 622 00 125 C Import CMD G4 Projects in SyCon 129 840 USE 497 00 June 2005 117 Appendices 118 840 USE 497 00 June 2005 Example for diagnosis and control of a slave A Overview Introduction What s in this Chapter In this chapter you will find an example illustrating how to diagnose and control a slave This chapter contains the following topics Topic Page Example for control of a slave via a generic bus 120 Example of Diagnosing a PCP Node 121 840 USE 497 00 June 2005 119 Examples Example for control of a slave via a generic bus Task Description Possible solution The connection by a slave to the bus master 140 NOA 622 00 via the generic bus make is possible to control a slave using as assigned activation word See Activate p 69 By setting and resetting the individual bits you can start and stop the INTERBUS and connect and disconnect the specified node The generic bus is assigned a 4x word in the menu window I O Map in the Activatefield With the help of the EFB the desired device address node number 4x 1 and the controller are defined using the appropriate bits 4x Loading of the address of the slave node in word 4x 1 via the variable IBS_Geraete_Nr
22. damage User Comments We welcome your comments about this document You can reach us by e mail at techpub schneider electric com 10 840 USE 497 00 June 2005 INTERBUS and INTERBUS Communication with TSX Quantum 140 NOA 622 00 Overview What will you find in this section What s in this Part This section contains general information concerning INTERBUS and for configuration with TSX Quantum 140 NOA 622 00 This part contains the following chapters Chapter Chapter Name Page 1 General 13 2 Performance 23 3 The 140 NOA 622 00 as INTERBUS Master 29 4 Accessories and Replacement Parts 35 840 USE 497 00 June 2005 11 INTERBUS and INTERBUS Communication 12 840 USE 497 00 June 2005 General At a Glance Introduction What s in this Chapter This chapter describes the most important aspects of data communication via an INTERBUS system This chapter contains the following topics Topic Page Overview 14 General Architecture of an INTERBUS Field Bus System 15 840 USE 497 00 June 2005 13 General Overview What is INTERBUS Branch interface modules Input output modules INTERBUS is a serial field bus system used to connect sensors and actuators which is designed for industrial operating environments This field bus system uses the master slave method The master manage
23. does not answer 101 65 The configured ID or length codes do not match the connected configuration 102 66 There are too many slaves connected to the master 103 67 The configuration was changed during the ID scan This was caused by an interruption to the ID scan as a result of a non diagnosed network error 104 68 Faulty setup of the current network configuration after a main ID scan 105 69 Interruption of the ID scan cycle due to a non diagnosed network error caused by an installation error or a defective slave 106 6A A previously scanned slave is missing during the next ID scan cycle 107 6B Configuration was changed during runtime a running slave is no longer answering 108 6C No connection to INTERBUS Interruption between the master and the first remote bus nodes in the network 120 78 The configuration of the local bus is not permitted 121 79 An invalid group or branch has been configured 122 7A A branch number is defined for the slave but no group number is defined 220 DC The CPU watchdog is faulty this triggers a runtime error timeout 224 EO Error in the INTERBUS processor communication 76 840 USE 497 00 June 2005 Configuration and Diagnostics Error numbers for the slaves The following tables show the error numbers for the slaves Highbyte from 3x 2 lt 255 Error number Description dec hex 0 0 No error INTE
24. network with alternatives see also display in SyCon Master 140 NOA 622 00 E Remate pus branch Group 1 Alternative 1 ZI Device0 T10 e 1 0 module Device3 TN 4 0 VO module e rd Z Remote bus branch Group 1 Alternative 2 Ey Device1 SE TN 2 0 vini BK TN 3 0 BK or Devices Device6 a pere TN 6 0 TN 7 0 2 TN 5 0 VO module 10 module BK 2 o 5 or Remote bus branch Group 1 Alternative 3 m Device L E TN 80 ei BK dependant 7 1 on Enabled E j Device11 Alternative Device8 Device9 Device10 TN 12 0 TN 9 0 TN 10 0 TN 11 0 VO module VO module 1 0 module 1 0 module TN Node number BK Branch interface module 90 840 USE 497 00 June 2005 Groups and Alternatives Switching behavior for alternative groups In the SyCon configuration every alternative in a group starts with its own branch interface module However in the hardware configuration there is only one other branch interface module physically available Switching between the configured branch interface modules is carried out for example by connecting the individual bus line for the desired al
25. s Note The more words that are transferred together during a cycle the more efficient the communication SyCon supports the shared transfer of 4 words 840 USE 497 00 June 2005 27 Performance 28 840 USE 497 00 June 2005 The 140 NOA 622 00 as INTERBUS Master 3 Overview Introduction What s in this Chapter This chapter describes the 140 NOA 622 00 as INTERBUS master This chapter contains the following topics Topic Page The 140 NOA 622 00 as INTERBUS Master 30 Possible uses of the 140 NOA 622 00 depending on CPU type 32 Comparison of the INTERBUS Master Modules 33 840 USE 497 00 June 2005 29 NOA 622 00 as INTERBUS Master The 140 NOA 622 00 as INTERBUS Master Performance The 140 NOA 622 00 is the INTERBUS master for the TSX Quantum and has the following performance e Can be used with Concept Version 2 5 SR2 and up e Support of PCP channels Version 2 0 In this version the PCP channel can be up to 4 words which can be addressed logically or physically e Full compatibility with INTERBUS standards is guaranteed e Data capacity to address up to 251 nodes e Branch interfaces for remote bus branches can be configured e Groups and alternative branches can be defined e No process data preparation e Macros and events cannot be created e Forcing Ox 1x references on INTERBUS nodes is not possi
26. 81 129 ALI REMOTE ERR Error in the use of the remote bus node The communications partner server has rejected the request and returned an error Possible cause e Access to a non existing object e Data length of the sent data does not correspond to the data length of the object For more information see Note on error 081hex p 99 0x82 130 ALI UNKNOWN SERVICE Unknown function in a requested message 0x83 131 ALI LOCAL ERR PCP communication is not initialized or is incorrectly initialized for this slave Communication reference CR for this slave must be checked 0x87 135 ALI F VFD WRONG STATE Local status does not allow a send The current configuration is not activated on the Master please download the configuration Ox8F 143 ALI F TIMEOUT Remote Bus Node does not respond in time Timeout 98 840 USE 497 00 June 2005 IBS_READ Note on error 081hex Error number Explanation Hex Dec 0x97 151 ALI CR INVALID Invalid communication reference CR 0x9B 155 ALI UNKNOWN SERVICE Invalid INTERBUS PCP service F001 61441 A connection to NOA cannot be established or NOA is not available F010 61456 PCP data not entered in the 4x register F020 61472 incorrect data length LENGTH entered If the 081hex error message appears in the STATUS parameter four further bytes with information will be transmitted to the INTERBUS co
27. AO HO RAD RR RD hans dem 104 Examples of Request Response Blocks 105 IBS WRITE Writing variables to INTERBUS PCP nodes 113 e rU MEI 113 Brief Description sua a tet acuta ette det t eth Vie deis E Sauteed Baek PUR ADR 114 Representation 5 eo eI PEG RENE cU nr ea GO EY et terne 114 117 At a late us ao tre A SP Euer ID Da te rai Dou at 117 Example for diagnosis and control of a slave 119 OVGIVIOW los phe e IeesTRiL eee pale RM Rb ahah Pepe ed ed 119 Example for control of a slave via a generic bus 120 Example of Diagnosing a PCP Node 121 Upgrading from 140 NOA 611 x0 to 140 NOA 62200 125 OVervieW it mn ple pu eh MEUM Eu bL IPLE ERUIT IRE 125 Requirements for changing from 140 NOA 611 x0 to 140 NOA 622 00 126 Instructions for upgrading from 140 NOA 611 x0 to 140 NOA 622 00 127 Import CMD G4 Projects in SyCon 129 Importing CMD G4 projects into SyCon 129 RE Ce e da ew VUE CX e s e 131 i hin eae ete Dawe et RA RACE ee acr ce ERR Sara 135 Safety Information Important Information NOTICE Read these instructions carefully and look at the equipment to become familiar with the device before trying to install operate or maintain it The following special messages may appear throughout this documentation or on the equipment t
28. Chips in the network For the SUPI Chips to receive these messages at the same time the shift register must be bypassed The INTERBUS architecture consists of frame telegrams Each frame telegram contains all network data The identification telegram and the data telegram are the two types of INTERBUS frame telegrams Transfer telegrams begin with a loop back word This word is used as code for the end of the identification telegram All network data input and output data follow the loop back word The last words in the transfer telegram are the CRC word and control word A telegram is sent on the network between each byte shift INTERBUS cycle times are deterministic They can be calculated with microsecond precision when considering all network variables The cycle time mainly depends on the number of process data words Please also include the influence of PCP communication when calculating the INTERBUS system cycle time 840 USE 497 00 June 2005 25 Performance Response Time for the Application At a Glance Diagram Calculation example The response time for the application is a logical response time which does not contain the reaction time of the sensor and actuator interfaces It is the same as the time span between acquiring an input signal and setting an output using INTERBUS The following example provides a clear representation of the response time for an application
29. Configuration and Diagnostics Diagnostics and Control via the Generic Bus What diagnostic The INTERBUS slaves are connected to the bus master 140 NOA 622 00 in and control Concept via the generic bus After selecting the generic bus in the I O map enter possibilities the start addresses for the Status and Activation words exist Data for bus status and diagnostics is acquired in the status area data used to control the INTERBUS nodes is stored in the activation area Note A node can be e an individual node segment e a group e an alternative branch Status The bus and slave specific data is placed in this area for status information and diagnostics You enter a 3x reference here as start address for a range of 207 consecutive words Overview of the status words Word Significance 3x Error Status See Word 3x p 71 3x 1 Global status See Word 3x 1 to word 3x 8 p 71 3x 8 3x 9 Health status See Word 3x 9 to word 3x 24 p 74 of the individual slaves 3x 24 3x 25 Diagnostics status See Word 3x 25 to word 3x 40 p 75 ofthe individual slaves 3x 40 3x 41 Reserved 3x 206 A detailed description of the individual areas can be found in section Details about the Status Words p 71 68 840 USE 497 00 June 2005 Configuration and Diagnostics Activate Data to control the slave is entered in this area You enter a
30. ERBUS modules memory Programming Concept Programming respective user program respective diagnostics Load the program and start the PLC Concept Online Load the project to the controller Then when the conztroller is started the INTERBUS module is configured and placed in operation Offline or Online SyCon Debugging Concept SyCon To debug the project Various utilities are available for control of Diagnosis the inputs and outputs as well as error diagnostics Online diagnostics e User diagnostics e LED Display Documentation Concept Print various information concerning the bus configuration as the project 52 840 USE 497 00 June 2005 Commissioning Software Startup for using the 140 NOA 622 00 Overview The following section provides a brief description of the steps required for the software startup of the INTERBUS master 140 NOA 622 00 The steps are divided into the following sections e Selecting INTERBUS in Concept p 53 e Evaluating the bus configuration with SyCon p 55 e Editing the bus configuration in Concept p 57 e Configuring the 140 NOA 622 00 yourself p 59 Selecting Proceed as follows to enter the INTERBUS in Concept for using the INTERBUS in 140 NOA 622 00 Concept Step Action Performed 1 Open the respective project in Concept 2 Select Project PLC Configur
31. NOA 622 00 CPU type Concept IEC and LL984 Concept LL984 Concept IEC 140 CPU 113 02 Use of the 140 NOA 622 00 is not possible 140 CPU 113 03 max 2 max 2 max 2 140 CPU 213 04 max 2 max 2 max 2 140 CPU 424 02 Use of the 140 NOA 622 00 is not possible 140 CPU 434 12 max 6 max 6 140 CPU 534 14 max 6 max 6 Note For pure Concept LL984 applications you cannot use PCP communication Furthermore only a limited Diagnosis is possible in this case 32 840 USE 497 00 June 2005 NOA 622 00 as INTERBUS Master Comparison of the INTERBUS Master Modules Overview of the Properties Properties of the INTERBUS master modules 140 NOA 622 00 140 NOA 611 10 140 NOA 611 00 Physical addressing x X X Logical addressing X X PCP channel x x PCP version 2 0 1 5 7 PCP channel size 1 2 4 words 1 Word z Configuration test X X X during commissioning Software for bus SyCon CMD Tool CMD Tool configuration INTERBUS Generation 3 Text on LED field X Diagnostics display 3 digits X Configurable switch off behavior I O addressing in Ox 1x 3x 4x registers in 3x 4x registers in 3x 4x registers Configurable addressing mode IEC 984 X Support of remote bus branches NOA slot Central backplane Central back
32. Network 1 Node 1 Node 2 Node 3 Remote bus Remote bus Remote bus IBS_READ IIBS_WRITE IBS_READ IBS_WRITE read write read and write 82 840 USE 497 00 June 2005 Groups and Alternatives Overview Introduction This section describes the use of groups and alternatives What s in this This chapter contains the following topics 9 Chapter Topic Page Groups 84 Alternatives 88 840 USE 497 00 June 2005 83 Groups and Alternatives Groups What are groups Configuring groups INTERBUS nodes which are functionally similar can be put together in groups Nodes which do not directly follow each other can also be added to a group Each node can only be added to one group You can only add remote bus branches local bus or peripheral bus nodes to groups Groups nodes and bus segments which are at a physical distance from one another can be switched on together programmatically by a command using groups If you shut down any node in the group all nodes in this group and any nodes which happen to be dependant on this node will be shut down also e g a local bus peripheral bus branch which is not assigned to the group branch in branch The same applies if a node in a group fails Use SysCon to assign a node to a group Enter the relevant number here in the device configuration under Group number Valid range for the group number 1 255 Within
33. OL I BOOL I BOOL I WORD ANY 102 840 USE 497 00 June 2005 IBS_SEND_REQ Parameter Block parameter description Description Parameters Data type Significance START BOOL 1 a request operation is started i e data is read from the specified INTERBUS Master 140 NOA 622 00 and stored in the state RAM on the PLC The parameter must remain 1 until the operation is complete If the parameter remains 1 after the operation is completed a new request operation is started by the EFB in the following PLC cycle Note If the parameter is set to 0 before the operation is completed the operation is cancelled SLOT BYTE Specifies the slot address of the corresponding INTERBUS Master NOA 622 00 in the Quantum backplane REQUEST ANY Enter a control block here which starts a specific request to the NOA see section Examples of Request Response Blocks p 105 Enter a variable here to define the required data type The data itself is always stored in n consecutive 4x registers A minimum of 128 words must be reserved for this area ACTIVE BOOL This binary output is set to 1 as long as the operation is active It is set to 0 when the operation has successfully completed or if an error occurs DONE BOOL 1 An operation was stopped without an error ERROR BOOL 1 An error occurred during the request operation The error status can be found in the STA
34. RBUS network specific error numbers 30 1E A slave was not found in the last network scan cycle 31 1F A slave returns a different ID code than that given in the configuration 32 20 The slave returns a different length code than that given in the configuration 33 21 Further non configured slaves discovered at the interface to the remote bus local bus or installation bus branch 34 22 Further non configured slaves detected at the interface to the remote bus 36 24 A slave reports a peripheral error 40 28 Faulty interface to the remote bus local bus or installation bus branch 41 29 Faulty interface to the remote bus 42 2A Slave reports a false ID and length code during the last network scan cycle 46 2E Communication with this slave is stopped Configuration error in the event of a download from SyCon 70 46 An address is occupied twice in the configuration 71 47 Length of the data set for a slave is wrong 72 48 Length of the process data configuration is wrong 73 49 Length of the additional table is wrong 74 4A Length of the PCP data is wrong 75 4B Size of the entire data set is inconsistent 76 4C Additional table not consistent 77 4D Maximum number of output process data offsets exceeded 78 4E Maximum number of input process data offsets exceeded 79 4F Maximum number of offset addresses exceeded gt 255 80 50 Number of slaves different compared to offset 81 51 The number of o
35. SE 497 00 June 2005 Examples Call for EFBs IBS_SEND_REQ to get the diagnosis data from the desired node address FBI 1 15 8 start send request gt gt 3 p 4 MSG_REQU IBS SEND REQ Start Active Slot Done Request Error Status Response send requ active send requ done L send requ error L send requ status MSG RESP 840 USE 497 00 June 2005 123 Examples 124 840 USE 497 00 June 2005 Upgrading from 140 NOA 611 x0 to 140 NOA 622 00 Overview Introduction What s in this This chapter provides brief instructions on how to upgrade your system from 140 NOA 611 x0 to 140 NOA 622 00 This chapter contains the following topics 9 Chapter Topic Page Requirements for changing from 140 NOA 611 x0 to 140 NOA 622 00 126 Instructions for upgrading from 140 NOA 611 x0 to 140 NOA 622 00 127 840 USE 497 00 June 2005 125 Upgrading from 140 NOA 611 x0 to 140 NOA 622 00 Requirements for changing from 140 NOA 611 x0 to 140 NOA 622 00 Overview In principle changing from 140 NOA 611 x0 to 140 NOA 622 00 is possible However project creation and the type of INTERBUS processing for the NOA 622 are different to the NOA 611x0 therefore you have to make changes in your Concept project to the I O mapping and in the user program in addition to the hardware chan 140 NOA 622 00 Note Th
36. Square D Telemecanique Sc Quantum 140 NOA 622 00 User Manual 840 USE 497 00 eng hneider El iP ectric Building a New Electric World Table of Contents Safety Information 7 About the Book era Seon bn bee RIETI Mee 9 Part INTERBUS and INTERBUS Communication with TSX Quantum 140 NOA 62200 11 OVetrVIQ Wt EIQUE b REB a M QE EN ybi Eu asp dete E 11 Chapter 1 General siiis Rex ERREFERAFIARE eee eR eae eee RES 13 Ata Glance 1 452 br t Ce eee e EDI eie sere aei Ere gotta 13 OVOrVIe Wt rod eee Prec a ageless og Lr ea RA deen RR UE E 14 General Architecture of an INTERBUS Field Bus System 15 Chapter2 Performance sus senegal E REY RE EE RE 23 At a Glance 2 an eet o heb e RI eb atre eren el Penh 23 Protocols LT elk ce etre euet ARE ERREUR a 24 Network Control ep REV Evene etes rS RP 25 Response Time for the Application 26 Data Transfer Rate per Station 27 Chapter 3 The 140 NOA 622 00 as INTERBUS Master 29 OVErvieW pen i ea Ee ee dope TAORY ey ec ce EU E 29 The 140 NOA 622 00 as INTERBUS Master 30 Possible uses of the 140 NOA 622 00 depending on CPU type 32 Comparison of the INTERBUS Master Modules 33 Chapter 4 Accessories and Replacement Parts 35 OVENI EW Er e
37. TUS parameter STATUS WORD Specifies the error status additional information can be found in paragraph Runtime errors p 104 lt Status gt 0 Module inactive a request operation is being executed or a request operation has successfully completed RESPONSE ANY The data received from the NOA 622 00 is placed in a response block here see section Examples of Request Response Blocks p 105 Enter a variable here to define the required data type The data itself is always stored in consecutive 4x registers A minimum of 128 words must be reserved for this area Note Please note that the same data type always has to be used for the parameters REQUEST and RESPONSE e g Bool Word Word ByteArray derived data types see Example of Diagnosing a PCP Node p 121 840 USE 497 00 June 2005 103 IBS_SEND_REQ Runtime errors Error numbers The following messages are displayed in the STATUS parameter of the EFB Error number Meaning Hex Dec 1001 4097 Abort by user 2002 8194 One or more control block parameters were modified while the operation was active this only applies to operations which require several cycles for completion Control block parameters may only be modified in inactive operations 2004 8196 REQUEST not located on a 4x register e RESPONSE not located on a 4x register No more 128 words free after the REQUEST ad
38. and Control via the Generic Bus 68 Details about the Status Words 71 Using the PCP Channel 79 OVerVIeW 2 olet reside idt tuse ated e no tt AED CR unns 79 the PCP channel with the 140 NOA 622 00 80 Example of Addressing a PCP Node 81 Groups and Alternatives 83 OVEIVIOW in tete Led wea eire ult ote ie deett 83 GrOUDS e eeu Aden LER Gus ened PUER FX RAE er RE REPRE RENE 84 Alternatives tsi odes wee tov SEIS Se 88 EFB description Sis ss vereri a pP ERE PEERS 93 OVE VOW ane a nr tas ats irae oie punto eet ats tun tis hea cm E heart 93 IBS_READ Reading variables via INTERBUS 95 OVervIeWis 2 aad che tact tik a etum ne Ao d ms Anant eae De 95 Brief Description eee a eve date Re te Reps 96 Representation vs RE ERU EE RU ERR REN kon oie Ps 96 Burimi ertOr is 2 54 cha doeet A Al Res deni ao ort eie sda one a e Mrs Re 98 Chapter 11 Chapter 12 Appendices Appendix A Appendix B Appendix C Glossary Index IBS_SEND_REQ Diagnostic query on the INTERBUS Master 140 NOA 622 00 101 OV IVIOW causer ae e ee pA PIE E REIHE 101 Brief Descriptior cuc icri RO pige ed inte heo Na OR ro s d 102 Repr sentation ode tn handle trt uet tec UR soe ep Dotnet etm ind 102 Runtime errors esci meme o pe EA RARE
39. arameter dialog box 140 NOA 622 00 Assigning the Master Setup NONE v 01 Interbus 02 Interbus r Output timeout status e Setto zero Hold last value r Addressing Mode e MSB left IEC MSB right 984 OK Cancel Help 4 In the 140 NOA 622 00 parameter dialog box set the values for the Output Timeout Status and the Addressing Mode 5 Confirm the settings with OK 840 USE 497 00 June 2005 59 Commissioning Shutdown and Startup Procedure of the 140 NOA 622 00 Introduction Switch off behavior of the 140 NOA 622 00 Switch off behavior of the 140 NOA 622 00 The are different possibilities for the shutdown and startup of the 140 NOA 622 00 as well as the connected INTERBUS and its nodes e Switch power supply on and off switch on routine e Press reset button on the NOA module switch on routine e Starting and stopping the INTERBUS via the bits of the activation word Generic Bus switch on restart routine e Starting and stopping individual INTERBUS nodes See Switching INTERBUS nodes p 61 viathe bits of the activation word Generic Bus switch on restart routine The following routines are started when switching on the NOA e Module Self Test e Load the INTERBUS configuration from the CPU e Start the INTERBUS if a valid configuration is available on the NOA The valences of the o
40. ation I O Map Go To the entry Generic Bus 1 0 Map Expansion Size 144 EE m Insert Delete Go To Local RIO slot Cut Copy Insert Local RIO slot 7 DIO 0 CPU YO Drop DIO 1 slot Bits A Bits Status Edit i E DIO 2 slot m I Grecs ist select this line Remote 1 0 OK Cancel Help 3 Click Insert and enter Interbus in the 1 0 Handler selection dialog box 10 Handler selection Name Vendor Interbus Schneider Automation GmbH OK Cancel Help about Type 840 USE 497 00 June 2005 53 Commissioning Step Action Performed Enter the respective references in the Status box and Activate see also Diagnostics and Control via the Generic Bus p 68 I O Map Expansion Size 144 L B Insert Delete Go To Generic bus D Cut Copy Insert 1 0 Drop Type Supervisio Input bits Output bits Status Activate Edit Interbus 26 0 0 300001 400001 m is 26 0 0 300301 400301 To insert at the end of the list select this line Remote 1 0 Ok Cancel Help Select the desired INTERBUS and continue with Edit to the dialog box Generic Bus Master Interbus Board x Choose Launch Cfg to start the SyCon program for bus configuration Note A Bus Conf
41. ble Note The software package SYC SPU LF CD28 M SyCon is needed to create the INTERBUS configuration Method of The following graphic describes the how the 140 NOA 622 00 works operation Switch off Switch on the module Module is switched off the module Communication Module in self test Configured Module function phase Reset Non configured Module Configuration Self test OK 30 840 USE 497 00 June 2005 NOA 622 00 as INTERBUS Master Restrictions Data exchange Use as INTERBUS master Note The INTERBUS coupler AS BDEA 202 does not support INTERBUS firmware generation 4 i e this coupler cannot be implemented together with 140 NOA 622 00 If such a coupler exists in the INTERBUS configuration the coupler as well as the following I O modules have to be replaced by suitable modules e g Modicon TSX Momentum modules in case of convertion to 140 NOA 622 00 The table shows how the inputs and outputs are processed in the different operating conditions If Then INTERBUS module is in RUN data is exchanged via the bus mode PLC program is running the inputs and outputs are updated PLC program is stopped the inputs are not updated the outputs are in error mode i e they are held or set to zero 140 NOA 622 00 is an INTERBUS master for the TSX Quantum and can only be operated in the central backplane A maximum of 251 nodes or 4096 I O points are allowed per NOA module The maxim
42. ce for remote bus branch fibre optic cable 170 BNO 681 00 Polymer cable PSM LWL KDL O by the meter HCS cable PSM LWL HCS O by the meter Polymer plug set PSM SET FSMA 4 HCS plug set PSM SET FSMA 4 HCS Polishing set PSM SET FSMA POLISH Cable with plug PSM LWL KDL 2 by the meter Cable with HCS plug PSM LWL HCS 2 by the meter Fiber optic adapter with additional voltage supply OPTOSUB Fiber optic adapter without additional voltage supply OPTOSUB PLUS Note Supplier for the fiber optic accessories Phoenix Contact GmbH amp Co Homepage http www phoenixcontact com 840 USE 497 00 June 2005 37 Accessories and Replacement Parts 38 840 USE 497 00 June 2005 Module descriptions Overview What will you find in this section What s in this Part In this section you will find the module description for the communication module This part contains the following chapters Chapter Chapter Name Page 5 140 NOA 622 00 Communication Module for INTERBUS 41 840 USE 497 00 June 2005 39 Module descriptions 40 840 USE 497 00 June 2005 140 NOA 622 00 Communication Module for INTERBUS Overview Introduction This chapter describes the communication module 140 NOA 622 00 What s in this This chapter contains the
43. cept DFB TYPE msg STRUCT rx Byte receiver ty Byte sender in Byte length of the Message Header nr Byte number of the message a Byte response number Ls Byte error status b Byte command number e Byte extension DeviceAdr Byte node address DataArea Byte data area DataAdr Word data address DataIdx Byte data index DataCnt Byte length of diagnose structure DataType Byte data type Funct Byte function d Array 0 106 OF BYTE error data buffer END STRUCT END TYPE 840 USE 497 00 June 2005 121 Examples Declaration of necessary variables in Concept Variable Editor Variable Name Data type address 1 device address BYTE 2 IBS_Geraete_Nr WORD 400200 3 MSG_REQU msg 400500 4 MSG_RESP msg 400700 5 send_requ_active BOOL 5 send_requ_done BOOL 5 send_requ_error BOOL 5 send_requ_status WORD 5 start_send_request BOOL Preparation of the EFBs IBS_SEND_REQ request parameter 1 14 3 MOVE device address 5 4 gt MSG_REQU DeviceAdr 1 10 4 Constants Receiver IBM Task MOVE 3 gt D gt MSG_REQU rx 1 11 5 Constants Sender Host MOVE 16 gt MSG_REQU tx 1 12 6 Constants Length of the message header MOVE 8 gt gt MSG_REQU In 1 13 7 Constants Command IBM_Device_Diag MOVE 66 gt gt MSG_REQU b 122 840 U
44. d Signal Ground insulated 4 GND Reference conductor for fiber optics interface grouped potential Signal Ground not insulated 5 VCCI Supply voltage for fiber optics interface 5 V isolated 6 DO Transmit negated data Data Out negated 7 DI Receive negated data Data In negated 8 VCC Auxiliary supply for fiber optics interface 5 V grouped potential Note Only for connecting OPTOSUB 9 RBST RBST coupling Bridge 46 840 USE 497 00 June 2005 NOA 622 00 Connection of the RS 232C interface To connect the RS 232C interface use the data cable 990 NAA 263 20 Length 3 m RS 232 C e O6 e es O9 Ee Pinused Pin not used Assignments for remote bus interface Socket Signal Meaning 2 RXD Received Data 3 TXD Transmitted Data 5 GND Reference conductor Signal Ground 7 RTS Switch on transmission unit Request to Send 8 CTS Ready for transmission Clear to Send 840 USE 497 00 June 2005 47 NOA 622 00 Technical Data Power supply Data interface Mechanical structure Connection Type Environmental conditions Data of the supply Internal via Quantum bus 5 VDC max 0 8 A typ 0 7 A Note When using fiber optics adapters the power consumption increases according to the adapter used Data interface data INTERBUS RS 485 isolated 500 VAC test voltage RS 232C possible line
45. d through the slot number where the node is located The slot number is entered in the EFB as the parameter SLOT 80 840 USE 497 00 June 2005 Using the PCP Channel Example of Addressing a PCP Node Example of The following configuration consists of two INTERBUS networks that are each Addressing a controlled by an NOA The communication references EFB parameter run in these PCP Node networks from 2 4 As well as the slot number in this example 8 and 10 the EFBs of each node can be uniquely identified Configurations Example TSX Quantum NOA 622 00 Remote bus Remote bus Network 1 Node 1 Node 2 Node 3 Remote bus Remote bus Remote bus SLOT 10 SLOT 10 SLOT 10 Comm Ref IEC 68 2 6 FC 2 Comm Ref 3 Comm Ref 4 Network 2 Branch interface Node 1 Node 2 Remote bus Remote bus Remote bus Branch Branch SLOT 8 SLOT 8 Comm Ref 2 Comm Ref 3 Node 3 SLOT 8 Comm Ref 4 You need the EFBs IBS_READ and IBS_WRITE to receive data from your PCP module or to send data there We recommend configuring an EFB for each time a write or read access is made for each node 840 USE 497 00 June 2005 81 Using the PCP Channel Example Number of EFBs TSX Quantum NOA 622 00 Remote bus
46. de ne ee Os E rie Eee ba egies bates Bt 35 Accessories and Replacement Parts for Software 36 Accessories and Replacement Parts for Copper Lines 36 Accessories and Replacement Parts for Fibre Optic Cable Technology 37 Part Il Chapter 5 Part III Chapter 6 Chapter 7 Chapter 8 Chapter 9 Part IV Chapter 10 Module descriptions 39 Overview ogg B ag oe gn Pre ne RP RR D gu R eee 39 140 NOA 622 00 Communication Module for INTERBUS 41 OVEINVIOW ideni sio edd t e RE C UE EE SEL E Sab e 41 Brief descriptiori 2e E Rd pe eee aut eg dur 42 Description of the Operating and Display Elements LEDs 44 Configuration ede em derer Debe EVREUX 45 T chnical Data oii RR ERR RI Re 48 Software oos ERA NS peri x EE E RE EE E PE 49 Ata Glance rss soci ture min tC eer SITAS Er eruta 49 Commissioning a sex s kukE RN P REREEERRE REPRE PEE 51 Ata Glance Lo pvc b QNM RESO UE UU WS UN qe etel 51 Principle of Commissioning 52 Software Startup for using the 140 NOA 622 00 53 Shutdown and Startup Procedure of the 140 NOA 62200 60 Addressing Modes of the Inputs and Outputs 62 Firmware for the INTERBUS Master 65 Configuration and Diagnostics 67 e Chur m 67 Diagnostics
47. ded for users who want to commission and maintain communication master modules on an INTERBUS system Knowledge about the Quantum the programming software Concept and the bus configuration tool SYC SPU LF CD28 M called SyCon in following texts is required Additionally the reader should be familiar with INTERBUS This User Manual is valid for Concept versions starting with 2 6 SR1 for Microsoft Windows 98 Windows 2000 Windows XP and Windows NT The NOA 622 00 is an INTERBUS connection module and is compatible to INTERBUS Firmware Generation 4 The configuration of the INTERBUS takes place using the sofware SYC SPU LF CD28 M called SyCon in following texts Screen shots and procedures concerning this software shown in this book refer to version 2 7xx of SyCon Title of Documentation Reference Number Quantum Hardware User Manual 840 USE 100 00 Concept User Manual 840 USE 503 00 Note Current Information about the INTERBUS can be found on the INTERBUS Club Homepage http www interbusclub com 840 USE 497 00 June 2005 About the Book Product Related Warnings CAUTION The guidelines provided should be observed for applications using controllers with technical safety requirements Repairs to components should only be carried out by the manufacturer for safety reasons and to secure documented system data Failure to follow this precaution can result in injury or equipment
48. dress No more 128 words free after the RESPONSE address 2008 8200 Unauthorized network routing path on slave 2009 8201 Routing path equivalent to their own address 5001 20481 Inconsistent response by the network 6001 24577 No response received F001 61441 A connection to NOA cannot be established or NOA is not available F010 61456 Data not stored in the 4x Register 104 840 USE 497 00 June 2005 IBS_SEND_REQ Examples of Request Response Blocks Overview You can use the IBS_SEND_REQ block to send the following Requests Actions from the CPU to the NOA and INTERBUS node Function Command Description msg b msg a Diagnosis See Request 66 Request and storage of diagnosis data Response Blocks for specified node INTERBUS Diagnosis p 106 Configuration Changes See 76 Changing the active INTERBUS Request Response Blocks for configuration by enabling blocking of changing the INTERBUS individually specified INTERBUS nodes configuration p 109 during operation Connect disconnect Slaves 82 Connecting disconnecting the specified See Request Response INTERBUS node groups or branches blocks for connecting disconnecting INTERBUS nodes p 111 Start loading 67 Starts loading parameter blocks for the INTERBUS node End loading 69 The loading of the blocks is ended the loaded data is enabled Transfer of configuration 68 Loading the Master bus parameters or parame
49. e INTERBUS coupler AS BDEA 202 does not support INTERBUS firmware generation 4 i e this coupler cannot be implemented together with 140 NOA 622 00 If such a coupler exists in the INTERBUS configuration the coupler as well as the following l O modules have to be replaced by suitable modules eg Modicon TSX Momentum modules in case of convertion to Required You need the following components for the upgrade components p Term Module Number INTERBUS master module 140 NOA 622 00 Concept XL Version 2 5 SR2 corresponds to the desired language see current pricelist from Schneider Electric Software package SyCon Version 2 8xx for bus configuration and conversion if necessary SYC SPU LF CD28 M Programming cable for 140 NOA 622 00 Modbus cable corresponds to the desired length see chapter Accessories and Replacement Parts p 35 126 840 USE 497 00 June 2005 Upgrading from 140 NOA 611 x0 to 140 NOA 622 00 Instructions for upgrading from 140 NOA 611 x0 to 140 NOA 622 00 Overview The following sections provide brief instructions on how to upgrade hardware and the required steps to take in the software Hardware For upgrading hardware to the 140 NOA 622 00 carry out the following steps Upgrade Step Action Performed 1 Document the addresses configured in your current configuration Stop the user program and switch off the PLC Unplug the INTERBUS
50. e Number msg a Byte 66 Response IBM_Device_Diag msg f Byte 0 Error Status msg b Byte 0 No Operation msg e Byte 0 Extensions msg DeviceAdr Byte 0 250 Dev_Adr 255 Node Address from Concept msg DataArea Byte 0 Data area not used msg DataAdr Word 0 Data address not used msg Dataldx Byte 0 Data index not used 106 840 USE 497 00 June 2005 IBS_SEND_REQ Diagnosis status Variable Type Value Description msg DataCnt Byte 107 Data Number Length of the diagnosis structure msg DataType Byte Data type not used msg Function Byte Read function not used msg d 0 Byte Diagnosis status p 107 msg d 1 Byte Real length code msg d 2 Byte Real ident code msg d 3 4 Word Num of CRC errors msg d 5 Byte Online error msg d 6 Byte 0 100 Number of entries in the error data buffer msg d 7 106max Error data buffer length max 100 50 Bytes depends on number of entries Byte Diagnosis Error Numbers p 108 Byte reserved not used The bits of the diagnosis bytes have the following meaning 71615 4 3 2 1 0 Bit Function Significance 0 No Response Slave does not respond and is missing 1 Error Buff Ovfl Error Buffer Overflow 2 Peripheral Fault Slave has detected a peripheral supply error or short circuit 3 Cfg Fault Difference between the Device Ident or Length Code and the values configured Check both valu
51. e bus nodes in increasing order without spaces Example The following diagram provides a clear representation of addressing Quantum NOA 622 RE NN LL a a CPU 2 Remote bus branch E co n Branch interface 7 T 1 L o 16 digital 16 digital a inputs outputs E Remote bus branch Lo oc Branch interface 7 1 m 16 analog 4 analog 4 analog inputs outputs outputs Addressing Module with Addressing 16 digital inputs 1x1 1x16 16 digital outputs 0x1 0x16 16 analog inputs 3x1 3x16 4 analog outputs 4x1 4x4 4 analog outputs 4x5 4x8 62 840 USE 497 00 June 2005 Commissioning Bit Alignment The 140 NOA 622 00 has two bit alignment modes for binary I O modules Mode IEC 984 e IEC Mode e 984 Mode Using these two modes you can define the order of the I O bits in the I O words not mirrored mirrored The following sections show the difference between both modes The bit alignment of the analog I O modules remains the same in both modes To select the bit alignment mode in Concept open the pa
52. e g via the Reference Data Editor 1 16 1 MOVE IBS_Geraete_Nr 5 4 T gt Aktiv_wort_4x1 Input of control sequences in this case via changes of the literals in the animated state 1 7 2 i BIT_TO_WORD c BITO I L Aktiv wort 4x BITI BIT2 BIT3 BIT4 BITS BIT6 BIT7 BIT8 BIT9 BIT10 BIT11 BIT12 BIT13 BIT14 BIT15 oo oo oo PEE ESET c 120 840 USE 497 00 June 2005 Examples Example of Diagnosing a PCP Node Task Description With the help of the EFBs IBS_SEND_REQ diagnosis data from a specific node address should be read Also data from the EFB s parameters should be prepared Possible In order to make the programming more simple a suitable derived data type msg solution must be defined Furthermore with the help of the EFB the desired values are loaded into the elements of the structure and started via the EFB IBS SEND REQ call so that the diagnosis data from the specified slave node can be read in Information regarding the required data can be found in the block description IBS_SEND_REQ See BS_SEND_REQ Diagnostic query on the INTERBUS Master 140 NOA 622 00 p 101 in section Request Response Blocks for INTERBUS Diagnosis p 106 and in the SyCon documentation InterBus Master Protocol Interface Manual Chapter The Message Interface on your SyCon CD Definition of the derived data type msg with the program Concept Con
53. egister is written to the PCP node Enter a variable here to define the required data type The data itself is always stored in n consecutive 4x registers n LENGTH number of bytes to write ACTIVE BOOL This binary output is set to 1 as long as the write operation is active It is set to 0 when the operation has successfully completed or if an error occurs DONE BOOL 1 a write operation has been terminated without error ERROR BOOL 1 an error occurred during the write operation The error status can be found in the STATUS parameter STATUS WORD Specifies the error status for further information refer to the section called Runtime error p 98 Status 0 Module inactive a write operation is being executed or a write operation has successfully completed 840 USE 497 00 June 2005 115 IBS_WRITE CAUTION Overwriting input data If the 081hex error occurs the input data for the PCP data will be overwritten by the additional information Before creating new modules you must make sure that the parameter PCP_Data contains the desired PCP data Failure to follow this precaution can result in injury or equipment damage 116 840 USE 497 00 June 2005 Appendices At a Glance Introduction What s in this Appendix The appendix contains information about Hardware Software and upgrading possibilities The appendix
54. es configured in SyCon or in the configuration loaded online Reconfiguration Slave generated a reconfiguration request Interface 2 Error Remote bus interface of the slave is faulty and triggers a Timeout The interface is disconnected from the Master 6 Interface 1 Error The interface to the slave s remote bus local bus or installation bus branch is faulty and triggers a Timeout The interface is disconnected from the Master 7 Deactivated Slave is deactivated in the current configuration and is not processed When the processing of the node is to be enabled activate it using SyCon 840 USE 497 00 June 2005 107 IBS_SEND_REQ Diagnosis Error Numbers Error numbers Error numbers Description Hex Dec 0 0 no error 1E 30 A slave was not found in the last network scan cycle 1F 31 A slave returns a different ID code than that given in the configuration 20 32 A slave returns a different length code than that given in the configuration 21 33 More non configured slaves detected at the interface to the remote bus local bus or installation bus branch 22 34 Further non configured slaves detected at the interface to the remote bus 23 35 A slave was not found in the last network scan cycle 24 36 A slave returns a peripheral error 25 37 A slave returns a configuration request 26 38 A slave has detected a Checksum Error du
55. f the error Embedded message protocols allow complex parameter and message data to be send via the INTERBUS network The basic principle of an open bus system is to allow data to be exchanged between devices from different manufacturers The data includes commands and I O data which is defined as a standard profile and with which the devices operate Standard profiles are available for drives measurement encoders robot controllers pneumatic controlled valves etc The INTERBUS protocol EN 50254 is the communication standard for these profiles It represents an open standard for I O networks in industrial applications The protocol for the INTERBUS system has a hardware dependent structure and was developed as a shift register The I O modules are like a chain of shift registers connected to each other The main elements of the network are the two protocol chips The INTERBUS Protocol Master Chip IPMS on the master module controls the network The serial universal Processor Chip SUPI connects the I O node to the network Process data words are clocked via the network in each cycle Process data containing output data are entered on the SUPI Chip and then sent from there to the respective actuator The process data also contains input data coming from the SUPI Chip which is sent on to the INTERBUS master Please note that the process data words contain input and output data Therefore 16 clocks are required to transfer a word This gives t
56. following topics Chapter Topic Page Brief description 42 Description of the Operating and Display Elements LEDs 44 Configuration 45 Technical Data 48 840 USE 497 00 June 2005 41 NOA 622 00 Brief description Features The NOA 622 00 is the INTERBUS master and is used to couple this bus to the automation device Modicon TSX Quantum The module is compatible to the performance of the INTERBUS Generation 4 42 840 USE 497 00 June 2005 NOA 622 00 Front View of the Module Front view with location of the operating elements on OO a 5h WO NN Color code Display field LEDs Standard housing Removable cover Reset button RS 232 C interface INTERBUS interface Module screws 840 USE 497 00 June 2005 43 NOA 622 00 Description of the Operating and Display Elements LEDs View of the Display Meaning of the LEDs Representation of the display 140 NOA 62 2 00 INTERBUS Master R Act ive IBS RUN Slave F Meaning of LEDs LED Color Status Meaning R green On Ready The switch on routine was completed successfully The firmware is running correctly and the module is ready for operations RAM and checksum are ok Flashing No firmware or firmware is being l
57. hat the neither the communication connection or the power supply is broken during the load process and do not break the process using ABORT Failure to follow this precaution can result in injury or equipment damage 840 USE 497 00 June 2005 65 Commissioning Load with EXECLoader To load the Firmware using the EXECLoader tool carry out the following steps Step Action 1 Create a cable connection between the CPU and the controller The following options are supported Modbus Plus e TCP IP Ethernet e Modbus Start the EXECLoader Select the protocol used A Enter the address and with Modbus the transfer parameters for the CPU which are to be used for loading the NOA Select Device Type Local Head Enter the NOA slot number in Slot number Select Select Operation Transfer EXEC to Device o M OO Enter in Filename the names and directory of the NOA Firmware NOA1 xx BIN xx Version number Then press the Close to end the operation 66 840 USE 497 00 June 2005 Configuration and Diagnostics Overview Introduction What s in this Chapter This chapter describes configuration and diagnostics This chapter contains the following topics Topic Page Diagnostics and Control via the Generic Bus 68 Details about the Status Words 71 840 USE 497 00 June 2005 67
58. he INTERBUS its extraordinary speed Another property of the protocol is that the input and output data is updated at the same time 24 840 USE 497 00 June 2005 Performance PCP Protocol Network Control Network Operation INTERBUS Telegrams Network Timing The Peripherals Communication Protocol PCP is used to exchange data between peripheral devices layer 2 of the OSI model This protocol guarantees that messages are broken down and reassembled correctly during transfer All services required to make and brake connections as well as data transfer services are available The PGP protocol is connection and object oriented Client Server type It is only used on intelligent I O modules When a connection is made the Client and Server exchange their data using the available object type Object types are bytes words ASCII characters arrays etc This protocol is mainly used to send initialization parameters to intelligent I O modules The PCP protocol is only seldom used after the initialization is complete E Loop Process Process Process Process Process PCP Process Process Back Data Data Data Data Data Data Data Data Communication on the PCP channel CRC Control Node 1 Node 2 Node 3 Node 4 Node 5 Node 6 During initialization and operation of the network the IPMS Chip simultaneously transfers a control data telegram to all SUPI
59. ice 7 Device8 Node no Device 8 Device9 Node no Device 9 Device10 Node no Device 10 Device11 Node no Device 11 Device12 Node no Device 12 140 NOA 622 00 1 0 170 ADI 340 00 2 0 170 BNO 671 01 3 0 1 170 ADO 340 00 4 0 1 170 AMM 090 00 5 0 170 BNO 671 01 6 0 2 170 ADO 340 00 7 0 2 170 AMM 090 00 8 0 170 BNO 67101 9 0 1 170ADO 340 00 10 0 1 170 BNO 671 01 11 0 1 170 ADO 340 00 12 0 1 170 ADO 340 00 13 0 170 ADO 340 00 Group 1 Group 2 Group 1 840 USE 497 00 June 2005 85 Groups and Alternatives Node behavior when assigning to groups The nodes in a group and thus the entire group can be switched on and off in Concept via the Activation word 4x See Activate p 69 Here you specify the individual node which should be switched on and off If this node is assigned to a group the entire group is always switched Note When switching off a remote bus node all the following nodes are switched off whether or not they are assigned to a group When a remote bus mode is switched on all the following nodes are switched off again Following alternatives and groups are an exception to this These are notreconnected They must either be activated manually or the entire bus must be restarted so that all nodes are active again In the following table the status of the individual nodes after deactivation and then activation for some example nodes with an withou
60. iguration imported using the Import command cannot be overwritten by a configuration that was created using Launch Cfg To do this you must first delete the Interbus assignment to the generic bus and re enter it Since the Bus tables for the Generic Bus are created from scratch for every Import you must also re enter all address assignments in Concept when changes to the existing configuration are made 54 840 USE 497 00 June 2005 Commissioning Evaluating the bus configuration with SyCon For evaluating the INTERBUS configuration using the SyCon bus configuration tool proceed as follows Step Action Performed 1 There are the following possibilities for evaluating the INTERBUS configuration e Read the connected INTERBUS configuration using Online Automatic Network Scan Note Select the Serial Device Driver and assign the corresponding COM interface Connect the NOA 622 to the PC for the cable see Accessories and Replacement Parts p 35 e Enter the connected INTERBUS configuration For converting an existing generation 4 CMD project to SyCon see Import CMD G4 Projects in SyCon p 129 Note Further information on this can be found in the SyCon online help or in the documentation provided on the SyCon CD The following figure shows a configuration in SyCon
61. ion via the PCP channel Peripheral Communication Protocol is enabled by EFB s from Concept Using PCP communication with Concept LL984 programming is not possible The following modules are available Name Description IBS_READ This module reads data into the state RAM of the PLC from a PCP slave connected via the INTERBUS IBS_WRITE This module writes data from the status RAM ofthe PLC to a PCP slave connected via the INTERBUS IBS SEND REQ This module requests data from the specified INTERBUS master and stores it in the PLC state RAM A NOA 622 00 can serve up to 62 PCP nodes The standard buffer length for PCP modules is 64 Bytes If your PCP module requires a large buffer length you must set this in the SyCon tool The maximum length is 246 Bytes the same as the largest value that can be set here A communications reference CR and the NOA slot number is required to set the address for a PCP node All PCP nodes can be given unique addresses using these two parameters parameters Description Communication reference CR The communication reference CR is a continuous number and is entered in the EFB as the parameter CR CR is a value between 2 and 62 and is set automatically by SyCon during the bus configuration It starts behind the NOA with 2 and increases by 1 from PCP node to PCP node The last node on the bus has the highest number Slot Number The INTERBUS network is identifie
62. issioning Firmware for the INTERBUS Master Update Possibilities Loading the Firmware directly Loading the Firmware Notice Updating the Firmware in the INTERBUS Master can by carried out in two ways e Load the updated directly from SyCon to the 140 NOA 622 00 module or e Load the updated Firmware via the Quantum CPU using the EXECLoaders Note The NOA 622 00 is delivered with Firmware installed The procedures described for loading new Firmware are only required if an update is being made Further details as well as new Firmware can be supplied by the technical support on request Loading the Firmware directly to the INTERBUS Master is carried out via the RS 232C interface on the 140 NOA 622 00 module Step Action 1 The module is cionnected to the serial interface COM on the PC using a Modbus standard programming cable see Accessories and Replacement Parts p 35 The Firmware is transfered from the configurator SyCon using Online gt Firmware Download follow the menu instructions Note You have to load the Firmware NOA1_xx Q12 xx Version number Loading the Firmware in the INTERBUS Master is carried out via the Quantum CPU with the EXECLoader CAUTION Blocking Communication with the Module Loading the Firmware may not be interrupted under any circumstances as it means the module can no longer be accessed via the EXECLoader Ensure t
63. le between the branch interface and the first module 20 m two modules 20 m the branch interface and the last module 200m Note When using Loop 1 divide the physical properties values in half Electrical data Maximum power consumption 1 8 A Loop2 1 5 A Loop1 Capacitance Number of nodes Maximum 63 Groups Possible Supply for I O modules Supply voltage via bus cable or externally 22 840 USE 497 00 June 2005 Performance At a Glance Introduction What s in this Chapter This chapter describes the performance of an INTERBUS field bus system This chapter contains the following topics Topic Page Protocols 24 Network Control 25 Response Time for the Application 26 Data Transfer Rate per Station 27 840 USE 497 00 June 2005 23 Performance Protocols Overview INTERBUS Protocol INTERBUS Protocol Format The following protocols are possible with the INTERBUS master module 140 NOA 622 00 e INTERBUS Protocol p 24 e PCP Protocol p 25 The INTERBUS protocol allows a high data throughput The I O data is transferred in blocks which allow simultaneous and predictable updating of all nodes connected to the network The necessary transfer security is guaranteed using a CRC error test in the protocol Complex diagnostics make it possible to find the cause and location o
64. lengths according to DIN 66 020 grouped potential 20 m shielded Mechanical structure data Format Width 40 34 mm Standard Housing Mass weight 0 4 kg Connection method data INTERBUS 9 pin D SUB socket RS 232C 9 pin D SUB socket for 990 NAA 263 x0 Environmental conditions data System data See Quantum User Manual Power dissipation Max 4 W typ 3 5 W MTBF Time GF gt 100 000 hours 48 840 USE 497 00 June 2005 Software At a Glance Introduction What s in this Part This section describes the various possibilities regarding configuration contol and diagnosis of an INTERBUS application with 140 NOA 622 00 as master module This part contains the following chapters Chapter Chapter Name Page 6 Commissioning 51 7 Configuration and Diagnostics 67 8 Using the PCP Channel 79 9 Groups and Alternatives 83 840 USE 497 00 June 2005 49 Software 50 840 USE 497 00 June 2005 Commissioning At a Glance Introduction This chapter provides an overview of commissioning the INTERBUS configuration What s in this This chapter contains the following topics 5 Chapter Topic Page Principle of Commissioning 52 Software Startup for using the 140 NOA 622 00 53 Shutdown and Startup Procedure of the 140 NOA 622 00 60
65. lled segments A bus branch coming from a branch interface is called a remote bus branch Remote bus nodes are e g e TSX Momentum modules e Branch interface modules 840 USE 497 00 June 2005 17 General Remote Bus Branch The remote bus branch is generated by a branch interface The branch interface itself is a remote bus node The I O modules on the remote bus branch are identical to those on the remote bus INTERBUS network with remote bus branch INTERBUS Master 1 0 module eo 2 Tal go o E e Remote bus branch Remote bus branch BK Branch interface UH eo a go o E o oc Note With INTERBUS Firmware Generation 4 it is possible to create branches branch in branch also see picture INTERBUS architecture p 16 18 840 USE 497 00 June 2005 General Remote bus remote bus branch technical data The following tables contain remote bus technical data Transfer properties Transfer procedures Differential signal transfer according to RS 485 Possible transfer media e Copper cable twisted pair 5 conductor Fiber optics line HCS polymer or glass fiber Infrared connection Transfer rate 500 kbit s Physical Attributes Copper cable Cu Maximu
66. m length of a segment 400m Maximum length of the cable between the connection module and the 400 m first branch interface on the remote bus Two branch interfaces 400 m the connection module and the 12 8 km last station on the remote bus Fiber optics line HCS 200 Polymer Glass fiber 230Nm 980 1000Nm Maximum length of a segment 300 m 50 m 2 500 m Maximum length of the connection module andthe 300 m 50 m 2 500 m the cable between first branch interface on the remote bus Two branch interfaces 300 m 50m 2 500m the connection module and the 9 600 m 1600 m gt 80 km last branch interface on the remote bus Minimum length of the cable exception INT lt INT and INT lt gt BNO 0 1m 840 USE 497 00 June 2005 19 General Installation Remote Bus Installation remote bus technical data Capacitance branch interface on the RB main bus Number of branch layers per Branch in branch Maximum 12 Number of slaves Maximum 251 on the remote bus and in the entire network Amount of I O data Maximum of 4096 input output points Groups Possible groups can be switched off Supply for 1 0 modules External supply voltage The installation remote bus IRB is a remote bus branch It is generated by special branch interfaces These branch interfaces themselves are remote bus nodes The installation remote
67. n Significance CTRL Control Error Configuration or runtime error ACLR Auto Clear Error Communication with the slave is stopped Auto Clear End State achieved NEXC Non exchange Error Communication with at least one slave is faulty no process data can be exchanged with it PRHL Peripheral error A short circuit has occurred at a minimum of one slave or there is no voltage supply present EVE Event Notification At least one faulty process data cycle has been detected or the bus has been restarted NRDY Host Not Ready Notification 1 INTERBUS communication is not possible 0 INTERBUS communication is ok HERR Outgoing Interface 1 Error Runtime error in local or installation bus after an INTERBUS ID Scan I2ERR Outgoing Interface 2 Error Runtime error in remote bus after an INTERBUS ID Scan Master status 00 hex OFFLine 40 hex STOP 80 hex Clear c0 hex Operate 72 840 USE 497 00 June 2005 Configuration and Diagnostics Details about word 3x 5 The bits of these words have the following meaning 15 14 13 12 11 10 9 8716 5 413 2 1 0 Bit Function Significance 0 WARN Quality Warning Increased number of faulty data cycles detected within a defined time period MWARN MAU Medium Acces Unit WARNING When using at least one Slave with
68. nection point e g for a serial machine with different variations This is carried out using so called alternatives or alternatively switchable groups which make it possible for the user to connect differently structured bus segments to the same remote bus output on a branch interface module Using the SyCon configuration software the entire configuration with all the alternatives is stored in the power up module The initial alternative is selected using the application program Use SysCon to assign a node to an alternative Enter another alternative here in the device configuration under Group number beside the Group number See Configuring groups p 84 Value range for the alternative 1 255 The group number and the alternative a separated by a hyphen Example If a node belongs to group 3 and there it belongs to alternative 2 enter 3 2 under Group number You can only define alternative nodes within a group Thus they have the same group number but a different alternative number Exactly one alternative for this group can be activated No more than one alternative can even be active at the same time The nodes in different alternatives must always have different logical nodes i e one node can only ever belong to a single alternative never to more than one Note An alternative group can only be connected to a remote bus node branch interface module Conversely the first node in an alternative group must also be a b
69. ng you must make the following changes to the changes and modifications to your user program if you have programmed the User program corresponding performance e Diagnosis Programming for the Status and Diagnosis words that are used for the 140 NOA 611 10 must be altered to the words now active for Diagnostics and Control via the Generic Bus p 68 e Reconfiguration input for a branch interface The remote bus branch is no longer connected via the reconfiguration input of the branch interface The input only effects the diagnosis status bit for the relevant node in the status word Any further evaluation of diagnosis data must be carried out by the EFB IBS SEND REQ The support center is available to provide any further information you might require e Using the PCP Channel You must remove the EFBs Loadables ICNT ICOM from your user program for the 140 NOA 611 and integrate the EFBs for the 140 NOA 622 00 IBS READ IBS WRITE according to the configuration in the user program 128 840 USE 497 00 June 2005 Import CMD G4 Projects in SyCon C Importing CMD G4 projects into SyCon General Information Save the CMD G4 project as an ASCII file CSV Import ASCII file in SyCon SyCon offers the possibility to import a project from the Configuration and Diagnosis program IBS CMD G4 by the company Phoenix Contact GmbH For importing a CMD G4 project in SyCon you need the project as an ASCII file CSV Car
70. nnection module from the slave that has been affected This data will be stored in the first four bytes of the parameter PCP Data of the module Please refer to the documentation of the affected PCP node for the meaning of this data Note To avoid unintentionally overwriting data we advise you to always configure 4 contiguous bytes here e g for the PCP Data parameter a word address for two contiguous free words or a word array with at least two elements 840 USE 497 00 June 2005 99 IBS_READ 100 840 USE 497 00 June 2005 IBS SEND REQ Diagnostic query on the INTERBUS Master 140 NOA 622 00 11 Overview Introduction This chapter describes the IBS SEND REQ block What s in this This chapter contains the following topics 9 Chapter Topic Page Brief Description 102 Representation 102 Runtime errors 104 Examples of Request Response Blocks 105 840 USE 497 00 June 2005 101 IBS_SEND_REQ Brief Description Function You can use this function block to request data from a specified INTERBUS Master Description NOA 622 00 and store it in the status RAM of the PLC Note EN and ENO should not be used together with this EFB otherwise output parameters can become fixed Representation Symbol Block representation BOOL __ START BYTE 4 SLOT ANY REQUEST IBS SEND REQ ACTIVE DONE ERROR STATUS RESPONSE I BO
71. o warn of potential hazards or to call attention to information that clarifies or simplifies a procedure The addition of this symbol to a Danger or Warning safety label indicates A that an electrical hazard exists which will result in personal injury if the instructions are not followed This is the safety alert symbol It is used to alert you to potential personal A injury hazards Obey all safety messages that follow this symbol to avoid possible injury or death DANGER DANGER indicates an imminently hazardous situation which if not avoided will result in death serious injury or equipment damage A WARNING WARNING indicates a potentially hazardous situation which if not avoided can result in death serious injury or equipment damage CAUTION CAUTION indicates a potentially hazardous situation which if not avoided can result in injury or equipment damage 840 USE 497 00 June 2005 Safety Information PLEASE NOTE Electrical equipment should be serviced only by qualified personnel No responsi bility is assumed by Schneider Electric for any consequences arising out of the use of this material This document is not intended as an instruction manual for untrained persons 2005 Schneider Electric All Rights Reserved 840 USE 497 00 June 2005 About the Book At a Glance Document Scope Validity Note Related Documents This manual is inten
72. oaded Off Module error Active green On The communication with the TSX Quantum CPU is active F red On Fault An error occurred on the INTERBUS and at least one node was switched off intentionally IB S Run green On The INTERBUS is functioning normal data transfer Flashing The INTERBUS is ready cyclically No cyclic No INTERBUS configuration error flashing message Slave red On An INTERBUS node is indicating a module error 44 840 USE 497 00 June 2005 NOA 622 00 Reset button Pressing the reset button causes a total reset on the 140 NOA 622 00 e The busis reinitialized e The bus configuration is reloaded from the CPU to the NOA Configuration Mounting Mount the module in any slot on the TSX Quantum central rack and screw it to the Location in the backplane The module must be screwed into position to ensure correct operation Backplane EMC Mounting the Module 1 Insert the module 2 Screw the module to the backplane 3 Backplane 840 USE 497 00 June 2005 45 NOA 622 00 Connection to Remote bus cable connection to the interface labeled remote bus INTERBUS 1e 6 2 2 5 e e7 e Pin used Bose Pin not used EE es z9 40 e9 p lt Assignments for remote bus interface Socket Signal Meaning 1 DO Data direction of transmission Data Out 2 DI Data direction of reception Data In 3 COM Reference conductor isolate
73. oordinates bus access it sends the data to all connected nodes and receives data from these nodes IRB Installation Remote Bus Installation remote bus 840 USE 497 00 June 2005 131 Glossary L LB Local Bus Local bus O OD Object Dictionary Object dictionary contains all information required to describe standard objects from type PMS for a certain device e g Robot P PCP Peripherals Communication Protocol Protocol for data exchange between peripheral devices layer 2 of the OSI model This protocol guarantees that messages are broken down and reassembled correctly during transfer All services required to make and brake connections as well as data transfer services are available PD Process Data Chanel Channel for process data PMS Peripherals Message Specification Specification for peripheral device messages PMS is a user interface according to the MMS model and implemented on layer 7 of the OSI model PMS formally defines the services used to make and brake connections as well as the data transfer services provided by PCP The standardized PMS communication services guarantee that the same communication interface is used for all devices R RB Remote Bus Remote bus Ring All nodes in a INTERBUS system are connected in a ring formed network 132 840 USE 497 00 June 2005 Glossary S Station on the The modules on the local bus are I O modules used to create a remote substation local bus in a s
74. ould not be used together with this EFB otherwise output parameters can become fixed Symbol Block representation IBS_WRITE BOOL__ START ACTIVE BOOL BYTE SLOT DONE BOOL UINT CR ERROR BOOL UINT INDEX STATUS WORD BYTE SUBINDEX BYTE LENGTH ANY 4 PCP_Data 114 840 USE 497 00 June 2005 IBS_WRITE Parameter Block parameter description Description parameters Data type Significance START BOOL 1 Writing data to the specified INTERBUS PCP Slave is started The parameter must remain 1 until the operation is complete If the parameter remains 1 after the operation is completed the EFB starts a new write operation in the next PLC cycle Note If the parameter is set to 0 before the operation is completed the operation is cancelled SLOT BYTE Specifies the slot address of the corresponding INTERBUS Master NOA 622 00 in the Quantum backplane CR UINT Communications reference of the PCP node as defined in the configuration tool INDEX UINT Logical address of the PCP node this address is specified in the manufacturer s documentation SUBINDEX BYTE Logical address defined for each element of the specified PCP node this address is specified in the manufacturer s documentation LENGTH BYTE Number of bytes to be written to the specified PCP node PCP_Data ANY The content of this r
75. plane Central backplane Transparent mode X Hot Standby support Number of NOA modules in the central backplane upto 6 depending on CPU type see paragraph Number of INTERBUS masters depending on CPU lype p 32 3 3 840 USE 497 00 June 2005 33 NOA 622 00 as INTERBUS Master Note If you have the 140 NOA 611 00 or the 140 NOA 611 10 and you want to replace them by the 140 NOA 622 00 contact the support center for further help You will find a brief description in appendix Upgrading from 140 NOA 611 x0 to 140 NOA 622 00 p 125 Overview of the Software requirements for use of the INTERBUS master modules Sonware 140 NOA 622 00 140 NOA 61110 140 NOA 611 00 Requirements NOA firmware starting with starting with 2 0 starting with 1 05 NOA1_xx bin Exec Loader or NOA1_xx Q12 SyCon ULEX version starting with 2 02 starting with 2 0 Modsoft PRoWorx starting with 2 4 starting with 2 4 Concept starting with 2 5 SR2 starting with 2 1 starting with 1 1 CMD Tool starting with 1 21 starting with 1 21 SyCon starting with 2 7xx 34 840 USE 497 00 June 2005 Accessories and Replacement Parts Overview Introduction What s in this Chapter This chapter contains a list of accessories and replacement parts for the use of copper cables and fiber optics This chapter contains the following topics
76. rameter dialog box for the NOA module Additionally there is also the difference in data mapping when using Ox 1x or 3x 4x registers Binary 16 Bitl O The addressing of binary 16 bit I O modules takes place according to the following Modules scheme in 3x 4x Range IEC Mode 984 Mode Bit order in i state RAM Ec sen ese dre ar ps io 2 o i i po E Bit order in INTERBUS Word IS Eb Ee on mp we Tee 2 a viewed using RE Bus Configuration Tool Inputs Outputs on terminals 15 16 14 15 16 D w AR EM D w Binary 16 Bitl O The addressing of binary 16 bit I O modules takes place according to the following Modules scheme in 0x 1x Range IEC Mode 984 Mode Bit order in BAR feats state RAM 153 5143 ek ee ge 0 ey E143 ee 2 A 0 OoOo O es Bit order in m INTERBUS Word Bheki 2 MO 15 14 13 2 1 0 viewed using CB Mi Bus Configuration Tool Inputs Outputs on terminals WEES Eu 14 15 16 i B2 S c 14 15 16 840 USE 497 00 June 2005 63 Commissioning Analog I O Modules in 0x 1x scheme
77. ranch interface module An alternative group can also be located an a deeper bus level than the main remote bus bar 88 840 USE 497 00 June 2005 Groups and Alternatives INTERBUS architecture with alternatives definition INTERBUS network with alternatives Display in SyCon Ti Ln T IE M Master Device Device0 Node no Device 0 Device1 Node no Device 1 Device2 Node no Device 2 Device3 Node no Device 3 Device4 Node no Device 4 Devices Node no Device 5 Device6 Node no Device 6 Device7 Node no Device 7 Device8 Node no Device 8 Device9 Node no Device 9 Device10 Node no Device 10 Device11 Node no Device 11 140 NOA 622 00 1 0 170 ADI 340 00 2 0 170 BNO 67101 Group 1 Alternative 1 3 0 1 1 170 BNO 671 01 4 0 1 1 170 ADO 340 00 Group 1 Alternative 2 5 0 1 2 170 BNO 671 01 6 0 1 2 170 ADO 340 00 7 0 1 2 170 ADI 340 00 Group 1 Alternative 3 8 0 1 3 170 BNO 671 01 9 0 1 3 170 ADO 340 00 10 0 1 3 170 ADI 340 00 11 0 1 3 170 ADO 340 00 12 0 170 ADO 340 00 840 USE 497 00 June 2005 89 Groups and Alternatives Hardware configuration to INTERBUS
78. ring data transfer 28 40 Faulty interface to the remote bus local bus or installation bus branch 29 41 Faulty interface to the remote bus 2A 42 Slave reports a false ID and length code during the last network scan cycle 2B 43 Slave missing because of broken INTERBUS connection during runtime 2C 44 Connection to this slave lost because of a faulty network connection in the local bus branch 2D 45 This slave was the last one that could be contacted by the INTERBUS scan in the last network scan cycle carried out during runtime 2E 46 Communication with this slave is stopped 108 840 USE 497 00 June 2005 IBS_SEND_REQ Request Response Blocks for changing the INTERBUS configuration You can use this block to change the active configuration of the connected INTERBUS by enabling or blocking individual nodes The control block for the REQUEST parameter has the following entries Variable type Value Description msg rx Byte 3 Receiver IBM Task msg tx Byte 16 Source Node HOST msg In Byte x Number of the active slaves 1 251 max msg nr Byte j Message Number optional msg a Byte 0 No Response Number msg f Byte 0 No error msg b Byte 76 Operation IBM Set Configuration msg e Byte 0 Not used msg d 0 Byte 1 Slave Device 1 enabled 0 Slave Device 1 blocked msg d 1 Byte 1 Slave Device 2 enabled 0 Slave Device 2 blocked msg d x 1 Byte 1 Slave Device x enabled 0 Slave
79. ry out the following steps in IBS CMD G4 Step Action 1 Select Parameters memory Click on the corresponding symbol to select the parameters memory Create ASCII file Use the menu Configuration Write ASCII file Project files CSV to create an ASCII file All control fields in this dialog box must remain activated Set ASCII file format Use CSV Options to specify the ASCII file format The following steps must be carried out to import ASCII file in SyCon Step Action 1 Create New Project Use the menu File New and select INTERBUS to create a new project 2 Select Master Use the menu Insert Master to select the Master 3 Import ASCII file Use the menu File Import CMD to start the import 4 After selecting the ASCII file to import you must make the settings for the file format in the IBS CMD G4 5 Start the import by clicking OK in the dialog box Start the import by clicking OK in the dialog box 840 USE 497 00 June 2005 129 Import CMD G4 in Sycon 130 840 USE 497 00 June 2005 Glossary B BC Bus coupler Branch interface module C CMD Tool Configuration Monitoring and Diagnostic PC software from Phoenix Contact for the configuration monitoring and diagnostics of INTERBUS field bus systems l y o Inputs outputs IBS INTERBUS This field bus system uses the master slave method The master manages and c
80. s Free running 1 0 cycle Word Dec Hex Bin Sync to xfer from to Master 101 SCH Concept userid 03 04 2003 r Timeout EUX ms Maximum fur Eingang oder Ausgang r Bus Startverhalten Startet nicht wenn ein Slave fehlt Startet immer Q Slave bestimmt Startverhalten OK Abbrechen Hilfe Note Note The Timeout time selected for the NOA 622 must be larger than or equal to the CPU Watchdog Timeout to avoid an INTERBUS failure For larger configurations or older firmware versions the CPU supervision time and the Timeout time for the NOA622 must be increased as required so that the INTERBUS starts If you want to connect several NOA modules with further INTERBUS configurations repeat step 3 for each NOA selecting the INTERBUS table Selecting INTERBUS in Concept p 53 up to step 3 table Editing the bus configuration in Concept p 57 58 840 USE 497 00 June 2005 Commissioning Configuring the Proceed as follows for entering the INTERBUS Master 140 NOA 622 00 yourself Step Action Performed 1 Select I O Map Go To the entry Local RIO slot 2 In the I O map for the local backplane under Project SPS configuration gt I O map Edit Module enter module 140 NOA 622 00 3 Assign the respective INTERBUS to the corresponding NOA using Params in the 140 NOA 622 00 p
81. s The response block for the REQUEST parameter has the following entries Variable type Value Description msg rx Byte 3 Receiver IBM Task msg tx Byte 16 Source Node HOST msg In Byte x Number of the affected slaves 1 251 msg nr Byte j Message Number optional msg a Byte No Response Number msg f Byte No error msg b Byte 82 Operation IBM Control Active Configuration msg e Byte Not used msg d 0 Byte 0 1 bSwitch Code 0 disconnect the specified slave 1 connect the specified slave msg d 1 Byte 0 250 first slave number Number is equivalent to Device in Concept msg d x Byte 0 250 x slave number The response block for the REQUEST parameter has the following entries Variable type Value Description msg rx Byte 16 Receiver Node on the HOST msg tx Byte 3 Source Node IBM Task msg In Byte x Message Length msg nr Byte j Message Number msg a Byte 82 Response IBM Control Active Configuration msg f Byte Error status see Connect Disconnect Error Numbers p 112 msg b Byte No Operation msg e Byte Not used 840 USE 497 00 June 2005 111 IBS_SEND_REQ Connect Error numbers msg f Disconnect Error x Error number Description Numbers hex dec Description 0 0 no error 65 101 An active slave reports a false ID or length code or is missing 67 103 The configuration wa
82. s See Local Bus p 21 INTERBUS loop See INTERBUS Loop p 21 840 USE 497 00 June 2005 15 General INTERBUS The following example provides a clear representation of an INTERBUS architecture architecture TSX Quantum with INTERBUS Master N CPU 4 NOA 622 1 0 module 3 ATV58 MM Remote bus branch BK Installation remote bus Branch BK 1 O module protect type IP 65 5 __ level 1 BK f 00000000 Q iz o o o o o o o o o o o o o o o o 00000000 00000000 Remote bus branch Branch 3 level 2 BK Dar BK mm f h Remote bus branch Branc level 3 BK ES 16 840 USE 497 00 June 2005 General Remote Bus In the hierarchical structure of the INTERBUS architecture the remote bus RB is the main part of the bus structure It is generated by the INTERBUS bus master This bus allows the longest distances within a system to be bridged The sections between 2 remote bus nodes are ca
83. s and coordinates bus access It sends and receives data for all connected nodes The following nodes can be connected to the INTERBUS among others Branch interface modules Input output modules from the TSX Momentum product family INTERBUS AS I Gateways Frequency converters ATV 18 58 and 66 TegoPower devices INTERBUS compatible devices from other manufacturers Note Current Information about the INTERBUS can be found on the INTERBUS Club Homepage http www interbusclub com The branch interfaces work as INTERBUS slaves and support then following functions e Make or brake connections to an installation bus a local bus or a remote bus connected to the remote bus e The supply for the bus electronics on the input output modules only for branch interfaces on the installation remote bus e Isolation of the remote bus segments e Reporting faulty functions using a potential free alarm output The input output modules from the various product families allow sensors and actuators to be connected to the INTERBUS field bus system which are used to control or monitor machines or processes 14 840 USE 497 00 June 2005 General General Architecture of an INTERBUS Field Bus System Overview The INTERBUS is hierarchically structured The architecture is made up of Remote bus with remote bus branches See Remote Bus p 17 Installation remote bus branches See Installation Remote Bus p 20 Local buse
84. s changed during the ID scan 68 104 More slaves than expected were detected in a branch 69 105 Timeout when opening an INTERBUS branch 6B 107 Configuration was changed during the runtime a running slave no longer responds 6D 109 An INTERBUS slave can not be connected because at least one of the other slaves in the configuration is disconnected 6E 110 An alternative group cannot be activated because a second alternative is active in the same group 112 840 USE 497 00 June 2005 IBS_WRITE Writing variables to INTERBUS PCP nodes 12 Overview Introduction This chapter describes the IBS_WRITE block What s in this This chapter contains the following topics 9 Chapter Topic Page Brief Description 114 Representation 114 840 USE 497 00 June 2005 113 IBS_WRITE Brief Description Function Description Representation You can use this function block to write data from the status RAM of the PLC to a PCP slave connected over the INTERBUS Several function blocks can be configured at the same time but of these at most 4 can be active at the same time For these different communication references parameter CR or the same communications reference with different logical addresses parameter index subindex can be assigned see Parameter Description p 115 However for all actual parameters of the individual modules different addresses must be configured Note EN and ENO sh
85. t group assignment are shown see INTERBUS architecture with group definition p 85 A precondition for this is that the bus was started before a node is deactivated and all nodes are active 86 840 USE 497 00 June 2005 Groups and Alternatives Status for all nodes after deactivation and activation for some example nodes Node Group Type Status after number TN 1 0 TN 4 0 Gr 1 TN7 0 Gr 2 TN8 0 TN 11 0 Gr 1 Deact Act Deact Act Deact Act Deact Act Deact Act TN 1 0 y o X J J J J J J J J J TN 2 0 BK X J J J J J J J J J TN 3 0 1 y o X X X J J J J J X J TN 4 0 1 yo X X X J J J J J X J TN 5 0 BK X J J J J J J J J J TN 6 0 2 yo X X J J X J J J J J TN 7 0 2 y o X X J J X J J J J J TN 8 0 BK X J J J J J X J J J TN 9 0 1 VO X X X J J J X X X J TN 10 0 1 BK X X X J J J X X X J TN 11 0 1 VO X X X J J J X X X J 12 0 1 VO X X X J J J X X X J 13 0 yo X J J J J J X J J J TN Node number BK Branch interface module VO I O node Deact Node was activated Act Node was activated again X Node not active no data traffic J Node active data traffic 840 USE 497 00 June 2005 87 Groups and Alternatives Alternatives What are alternatives Configuring alternatives It may be necessary for an application to activate different INTERBUS configurations while a process is running via a con
86. t the Status Words Overview The following section provides detailed information about the Generic Bus status words Word 3x The bits of word 1 have the following meaning 151141183112 1111009 8 7 6 54 3 2 1 0 Bit Function Significance 0 ASH 0 all configured slaves are OK 1 at least one configured slave has failed 1 LIC Toggles with each successful data transfer Remains 0 or 1 in the event of an error 2 BDP 0 There is no diagnosis message 1 at least one slave returns an error 3 15 Reserved Word 3x 1 to This range contains global status data Word 5x48 Word Significance 3x 1 Global communication errors See Details about word 3x 1 p 72 3x 2 Low Byte Number of the faulty nodes from Concept 0 to 250 Slave 255 Master High Byte Error number see section Error numbers for the Master p 76 or Error numbers for the slaves p 77 3x 3 Number of faulty data cycles 3x 4 Number of Bus re initializations 8x 5 Communication Collective Error See Details about word 3x 5 p 73 3x 6to Reserved 3x 8 840 USE 497 00 June 2005 71 Configuration and Diagnostics Details about word 3x 1 The bits of these words have the following meaning 15 14 13 12 11 109 87 6 5 413 2 110 Bit Functio
87. ternative to the remote bus interface for the branch interface module or via special branch interface modules Activation and changing between the different alternatives is configured in the application program Before you activate an alternative here you must make sure that this alternative is connected in the hardware Note When a bus starts none of the configured alternatives is active You must explicitly specify which alternative should be started The nodes in alternative groups and thus the entire alternative can be switched on and off in Concept via the Activation word 4x See Activate p 69 Here you specify the any node from an alternative group which should be switched on and off Then the whole alternative is always switched on Note When a remote bus mode is switched off all the following nodes with and without groups and alternative assignments are switched off When a remote bus mode is switched on all the following nodes are switched off again Following alternatives and groups are an exception to this these are notreconnected They must be activated manually 840 USE 497 00 June 2005 91 Groups and Alternatives 92 840 USE 497 00 June 2005 EFB descriptions IV Overview Introduction The EFB descriptions are arranged in alphabetical order What s in this This part contains the following chapters Part Chapter Chapter Name
88. ters slaves to the node Determine Bus Configuration 75 Read the connected INTERBUS configuration Note The following sections contains an overview of the first three function Further information on this subject can be found in the SyCon documentation provided on your SyCon CD 840 USE 497 00 June 2005 105 IBS_SEND_REQ Request Response Blocks for INTERBUS Diagnosis You can determine the internal diagnosis for individual nodes using these blocks The control block for the REQUEST parameter has the following entries Variable Type Value Description msg rx Byte 3 Receiver IBM Task msg tx Byte 16 Sender HOST msg In Byte 8 Length of the message header 8 msg nr Byte j Message Number optional msg a Byte No Response Number msg f Byte 0 No error msg b Byte 66 Operation IBM Device Diag msg e Byte 0 Not used msg DeviceAdr Byte 0 250 Dev_Adr 255 Node Address from Concept msg DataArea Byte 0 Not used msg DataAdr Word 0 Not used msg Dataldx Byte 0 Not used msg DataCnt Byte 0 Not used msg DataType Byte 0 Not used msg DataFnc Byte 0 Not used The response block of the RESPONSE parameter has the following entries Variable Type Value Description msg rx Byte 16 Receiver Node on the HOST msg tx Byte 3 Source Node IBM Task msg In Byte 8 107max Message Length msg nr Byte j Messag
89. um number of nodes allowed in the entire INTERBUS configuration for a Quantum SPS depends on the module type being used For a typical module with 16 inputs and 16 outputs e g 170 ADM 350 11 around 250 modules can be used in the entire condiguration The INTERBUS slaves are connected to the bus master 140 NOA 622 00 in Concept via the generic bus The maximum configuration size of the Generic Bus is 64 kB for all NOA 622 modules together After selecting the generic bus in the I O map enter the start addresses for the status and activation words The bus and slave specific data is placed in the status area for status information and diagnostics You enter a 3x reference here as start address for a range of 207 consecutive words Data to control the INTERBUS node is entered in the activation area You enter a 4x reference here as start address for a range of 25 consecutive words Additional information concerning utilization of the status and activation words can be found in chapter Diagnostics and Control via the Generic Bus p 68 The INTERBUS slaves can be assigned the following references in Concept e 0x 1x references e 3x 4x references 840 USE 497 00 June 2005 31 NOA 622 00 as INTERBUS Master Possible uses of the 140 NOA 622 00 depending on CPU type Number of INTERBUS masters depending on CPU type Note In Modsoft ProWorx NxT the 140 NOA 622 00 cannot be operated Possible uses with the 140
90. utput modules does not equal the number of output offsets 82 52 The number of input modules does not equal the number of input offsets 83 53 The actual output length is not equal to the configured module length 840 USE 497 00 June 2005 77 Configuration and Diagnostics Error number Description dec hex 84 54 The actual input length is not equal to the configured module length 85 55 Overlapping output data configured 86 56 Overlapping input data configured 87 57 An output module has also been assigned inputs 88 58 An input module has also been assigned outputs 89 59 The output module is defined as an input module 90 5A The input module is defined as an output module 91 5B The slave was configured in an invalid installation level 92 5C The configured ID code is not supported by the slave 78 840 USE 497 00 June 2005 Using the PCP Channel Overview Introduction What s in this Chapter This chapter describes how to use the PCP channel This chapter contains the following topics Topic Page the PCP channel with the 140 NOA 622 00 80 Example of Addressing a PCP Node 81 840 USE 497 00 June 2005 79 Using the PCP Channel the PCP channel with the 140 NOA 622 00 How do you use the PCP channel Configuration limits for the PCP channel Addressing the PCP Node Communicat
91. utputs analog and binary behave in accordance to the presettings in Concept when the program is stopped INTERBUS goes into Stop Mode in the event of a CPU or NOA breakdown or if the NOA Timeout is smaller than the CPU Watchdog Timerout the INTERBUS also goes into Stop mode In this case the valences of the outputs analog and binary are always set to 0 This behavior applies to all analog and digital outputs on the INTERBUS CAUTION Stopping and starting the INTERBUS using the SyCon tool if the application program stops If the user program stops and you start the INTERBUS using the SyCon tool all the outputs are set up 0 even if you set the shutdown procedure to Hold last value If you start the INTERBUS under these conditions using the SyCon tool the outputs take the last valid status again status active when the program was stopped Failure to follow this precaution can result in injury or equipment damage 60 840 USE 497 00 June 2005 Commissioning Parameter ization in Concept Switching INTERBUS nodes The switch off behavior must be configured in Concept After selecting the 140 NOA 622 00 module in the I O Map open the respective parameter dialog using Params Here you can choose between the following possibilities e The valences of the outputs analog and binary are frozen at the last valid value or e The valences of the outputs analog and binary are set to 0
92. witching cabinet SyCon System Configurator Software SYC SPU LF CD28 M for configuration monitoring and diagnostics of field bus systems 840 USE 497 00 June 2005 133 Glossary 134 840 USE 497 00 June 2005 Index Numerics 140 NOA 622 00 Startup Procedure 60 140 NOA 622 00 41 Accessories 35 Description of the LEDs 44 Description of the Reset Button 44 Diagnostics 44 Diagram of the Display 44 Diagram of the Operating Elements 43 Mounting 45 Replacement Parts 35 Shutdown Procedure 60 Switch off behavior 60 Technical Data 48 140 NOA 622 00 als INTERBUS Master 30 A Accessories for Copper Lines 36 Accessory Fibre Optic Cable 37 Addressing 62 Alternatives 88 Architecture 15 B Bit Alignment 170 ADM 390 30 64 Analog I O Modules 64 Binary 16 Bit I O Modules 0x 1x Range 63 Binary 16 Bit I O Modules 3x 4x Range 63 Binary 8 Bit I O Module in 3x 4x Range 64 Bit Alignment Mode IEC 984 63 C Changing from NOA 611 x0 Requirements 126 CMD Import G4 Project 129 COMM IBS READ 95 IBS SEND REQ 101 IBS WRITE 113 Commissioning Principle 52 Communication Module 140 NOA 622 00 41 Diagnostics 44 Diagram of the Display 44 Diagram of the Operating Elements 43 Mounting 45 Technical Data 48 Cycle Times INTERBUS 25 840 USE 497 00 June 2005 135 Index D Data Transfer Rate 27 Description of the LEDs Communication Module 140 NOA 622 00

Quantum

Contents

Download Pdf Manuals

Related Search

Related Contents