Home

User Manual FL IL 24 BK-B UM E - Documentazione Software Marel

1. the connectors H pem paa T 2 3 gt ele tele 09 m Bi OO HO QO 61560011 Figure 1 6 Internal structure of the connectors A Green connector for I O connection B Black connector for supply terminals Shield connector for analog terminals D Double signal connector for I O connection Jumpered terminal points integrated into the connectors are shown in Figure 1 6 The shield connector is jumpered through the shield connection All other connectors are jumpered through terminal point connection es 1 18 PHGNIX 654403 CONTACT FL IL 24 Connector coding You can prevent the mismatching of connectors by coding the base and the connector 61560012 Figure 1 7 Connector keying e Plug a keying profile disc into the keyway in the base 1 and turn it away from the small plate 2 Figure 1 7 Fig A e Use a diagonal cutter to cut off the keying tab from the connector Figure 1 7 Fig B Now only the base and connector with the same keying will fit together Figure 1 7 Fig C 654403 PHCENIX 1 19 CONTACT FL IL 24 BK B UM E 1 8 Function Identification and Labeling Function The modules are color coded to enable visual identification of the functions identifica
2. Table 1 8 Power and Segment Terminals Designation Features Order No IB IL 24 PRW IN Power terminal 24 V DC 27 26 31 1 IB IL 24 PWR IN PAC Power terminal 24 V DC 28 61 33 1 IB IL 24 PRW IN F Power terminal 24 V DC with fuse 27 27 909 IB IL 24 PRW IN F PAC Power terminal 24 V DC with fuse 28 61438 IB IL 24 PRW IN F D Power terminal 24 V DC with fuse and diagnostics 28 36 66 7 IB IL 24 PRW IN F D PAC Power terminal 24 V DC with fuse and diagnostics 28 61 89 4 IB IL 24 PRW IN 2 F Power terminal 24 V DC with fuse 28 60 01 5 IB IL 24 PRW IN 2 F PAC Power terminal 24 V DC with fuse 28 62 136 IB IL 24 PRW IN 2 F D Power terminal 24 V DC with fuse and diagnostics 28 60 280 IB IL 24 PRW IN 2 F D Power terminal 24 V DC with fuse and diagnostics 28 62 152 PAC IB IL 24 PWR IN M Power terminal 24 V DC 28 61027 IB IL 24 PWR IN R Power terminal 24 V DC 27 42764 IB IL 24 PWR IN R PAC Power terminal 24 V DC 2861674 IB IL 120 PRW IN Power terminal 120 V AC with fuse 27 31 704 IB IL 120 PWR IN PAC Power terminal 120 V AC with fuse 28 61 45 4 IB IL 230 PRW IN Power terminal 230 V AC with fuse 27 40 33 9 IB IL 230 PWR IN PAC Power terminal 230 V AC with fuse 28 61 535 IB IL 24 SEG Segment terminal 24 V DC 27 26 32 4 IL 24 SEG PAC Segment terminal 24 V DC 28 61 344 IB IL 24 SEG F Segment terminal 24 V DC with fuse 27 27 7
3. 3 67 3 12 1 Macros for Converting the Data Block of a Command 3 68 3 12 2 Macros for Converting the Data Block of a Message 3 71 3 12 3 Macros for Converting Input 3 74 3 12 4 Macros for Converting Output Data 3 75 3 13 Diagnostic Options of the Driver Software 3 78 3 13 1 Introd ctiorni iiri en 3 78 3 14 Positive 3 79 3 15 Error Messages ete ied se in etate 3 80 3 15 1 General Error 3 80 3 15 2 Error Messages When Opening a Data Channel 3 82 3 15 3 Error Messages When Transmitting 3 83 3 15 4 Error Messages When Transmitting Process Data 3 85 3 16 Example 3 88 3 16 1 Demo Structure 3 88 3 16 2 Example Program Source 3 90 3 2 PHCENIX 654403 CONTACT Driver Software 3 Driver Software 3 1 Documentation 3 1 1 Hardware and Software User Manual This Hardware and Software User Manual for FL IL 24 BK B PAC Order No 26 98 65 6 describes the hardware and software functions in association with an Ethernet network and the functions of the Device Driver Interface DDI software A
4. 4 57 4 2 PHCENIX 654403 CONTACT Firmware Services 4 Firmware Services As it is not necessary to use each firmware service in both operating modes the following table indicates the assignment of the services to the operating modes If the services are not used as specified in the table this may cause the firmware to behave as follows The service is not permitted in this mode and is rejected with a negative acknowledgment The service is executed and terminated with a positive acknowledgment the effect of this service is removed by the firmware 4 1 Overview 4 1 1 Services That can be Used in Every Operating Mode Table 4 1 Overview of the services that can be used in every operating mode Code Services Page 030944 Read Configuration 4 22 030Bhex Complete Read Configuration 4 29 0316hex Get Error Info 4 45 032Ahex Get Version Info 4 52 0351hex Read Value 4 12 0714 Control Device Function 4 38 0750hex Set Value 4 10 095644 Reset Controller Board 4 40 654403 PHCENIX 4 3 CONTACT FL IL 24 BK PAC UM E 4 1 2 Services That are Only Available in Expert Mode Table 4 2 Services that are only available in expert mode Code Services Page 030644 Initiate Load Configuration 4 14 0307 Load Configuration 4 16 0308 Terminate Load Configuration 4 20 030Chex Dele
5. 5 10 5 5 2 Write Multiple Registers 5 12 5 5 3 Read Coils ence init wedi thik 5 13 5 5 4 Read Input Discretes 5 14 5 5 5 Read Input Registers 5 15 5 5 0 cette t eite bete recen 5 16 5 5 7 Write Single Register 2 2 4 2 5 17 5 5 8 Read Exception Status 5 19 5 5 9 Data Format of the Exception Status 5 19 5 5 10 Exception Responses 5 20 5 5 11 Write Multiple Coils 5 21 5 5 12 Read Write Register 2 22 44 1 5 22 5 6 Reserved Registers for Command and Status 5 24 5 6 1 Command Word 5 24 5 6 2 Status Word eden de eene een 5 25 5 6 3 Diagnostics Using the Analog Input Table 5 26 KOA ErrorzTable e eoo erem etes 5 26 57 Monitoring eerte keen nue eda n eet 5 28 5 8 Modbus 5 29 5 9 I O Fault Response 5 30 5 9 1 Power Up Table 5 31 5 9 2 Connection Monitoring Table 5 33 vi PHOENIX
6. 2 5 2 4 1 Possible Address Combinations 2 6 2 4 2 Subnet 2 7 2 4 8 Structure of the Subnet 2 8 2 5 Web Based 2 9 2 5 1 Calling Web Based Management WBM 2 9 2 5 2 Structure of the Web 2 10 2 5 3 Layout of the Web 2 11 2 5 4 Password 2 11 2 5 5 Process Data Access via _ 2 12 2 6 Factory Line I O 2 2 17 2 6 1 Factory Line I O 2 17 2 6 OPC 2 18 654403 PHGNIX 2 1 CONTACT FL IL 24 BK B PAC UM E 2 2 PHCENIX 654403 CONTACT Startup Operation 2 Startup Operation 21 Firmware Startup After you power supplied your device the firmware is started 2 1 1 Sending BootP Requests Initial Startup During initial startup the device sends a BootP request without interruption until it receives a valid IP address The requests are transmitted at varying intervals 2 5 4 5 8 2 5 45 etc so that the network is not loaded unnecessarily If va
7. 120 mm 4 724 elg 5 9 K p Sin he gene Y 24 4 mm Hu 0 961 71 5 mm 2 815 55201022 Figure1 12 Dimensions of the electronics bases 4 slot housing 8 slot housing Ke miN s 5 o o o 5 Sjgn el Jl 120 mm 4 724 48 8 mm 1 921 71 5 mm 2 815 55201024 Figure1 13 Dimensions of the electronics bases 8 slot housing 654403 1 25 FL IL 24 BK B UM E Connectors h io S a 5 S 5 gt 19 58 5 BB T LH N E OO Dn n 60 00 e oo fool Inu OO RB 12 2 mm 0 480 12 2 0 480 55200058 Figure1 14 Connector dimensions Key A Standard connector B Shield connector Extended double signal connector The depth of the connector does not influence the overall depth of the module 1 26 PHCENIX 654403 FL IL 24 1 10 Electrical Poten
8. Monitoring Mechanism Monitoring the Client the the the Process Application Individual Ethernet Data Channels Connection Exchange Process data watchdog X X X process data monitoring Host checking X DTI Modbus monitoring X X X 5 28 PHCENIX 654403 CONTACT Modbus TCP Protocol 5 8 Modbus Monitoring You can activate a monitoring mechanism for every Modbus TCP connection so that the FL IL 24 BK B PAC can detect an error within a network e g a defect cable or a client operating system crash or error in the TCP IP protocol stack and thus the module can respond accordingly The monitoring mechanism is activated when reading or writing via the respective TCP connection for the first time In order to change the timeout value for the respective TCP connection write the new timeout value into the timeout table to the special address 1280 either using the fc 6 or the fc 16 function The value of this entry is the value of the timeout table The time is indicated in milliseconds in the range of 200 ms up to 65 000 ms A timeout value of 0 deactivates the monitoring function Values between 1 and 199 as well as values larger than 65 000 ms generate the exception response 3 ILLEGAL DATA VALUE After the first access via a Modbus TCP function all other accesses must be executed using the timeout value entered Otherwise the fault response mode is activated and th
9. FL IL 24 1 14 5 Replacing Fuse The power and segment terminals are available with or without fuses For modules with fuses the voltage presence and the fuse state are monitored and indicated by diagnostic indicators If a fuse is not present or defective you must insert or replace it Follow these steps when replacing a fuse see Figure 1 31 Lift the fuse lever A Insert the screwdriver behind a metal contact of the fuse B Carefully lift the metal contact of the fuse C Remove the fuse by hand D Insert a new fuse E Push the fuse lever down again until it clicks into place F 654403 PHCENIX 1 59 FL IL 24 BK B UM E 5520 011 Figure 1 31 Replacing a fuse 1 54 PHGNIX 654403 CONTACT FL IL 24 BK B PAC 1 15 Grounding an Inline Station All devices in an Inline station must be grounded so that any possible interference is shielded and discharged to ground potential A wire of at least 1 5 mm 16 AWG must be used for grounding Ethernetbuscoupler The bus coupler power terminals and segment terminals have FE springs and supply terminals metal clips on the underside of the electronics base These springs create an electric connection to the DIN rail Use grounding terminal blocks to connect the DIN rail to protective earth ground The modules are grounded when they are snapped onto the DIN rail Required additional In order
10. UM 5 6 3 Diagnostics Using the Analog Input Table 5 26 5 6 4 Error Table tete Er 5 26 5 7 MOntorning eem 5 28 5 8 Modbus 5 29 5 9 O Fault Response 5 30 5 9 1 Power Up 5 31 5 9 2 Connection Monitoring Table 5 33 5 2 PHGNIX 654403 CONTACT Modbus TCP Protocol 5 Modbus TCP Protocol This section describes the realization of the Modbus TCP communication on the FL IL 24 BK B PAC Modbus Protocol Modbus connections Modbus interface Modubus conformity classes Modbus message format Modbus Tables Register Input Register table Input Discrete table Coil table Supported Function Codes Read Multiple Registers Write Multiple Registers Read Coils Read Input Discretes Read Input Registers Write Coil Write Single Register Read Exception Status Write Multiple Coils Read Write Registers 654403 PHGNIX 5 3 CONTACT FL IL 24 BK B PAC UM E 5 1 Modbus Protocol The bus coupler supports a Modbus TCP server with the following features 5 1 1 Modbus Connections The FL IL 24 BK B PAC supports up to 8 connections simultaneously Thanks to this capacity a connection can be restored quickly This implies that
11. eene enne 3 10 3 5 8 Possible Combination of Modes 3 10 3 5 4 Startup Diagrams of the Bus Coupler 3 11 3 5 5 Changing and Starting a Configuration in P amp P Mode 3 13 3 6 Changing a Reference Configuration Using the Software 3 14 3 6 1 Effects of Expert Mode 3 14 3 6 2 Changing a Reference Configuration 3 14 3 7 Description of the Device Driver Interface DDI 3 16 S7 3 16 3 17 25 OVEIWIOW e dte s Ee esi 3 17 3 7 8 Working Method of the Device Driver Interface 3 17 3 7 4 Description of the Functions of the Device Driver Interface 3 20 654403 PHOENIX iii CONTACT FL IL 24 BK B UM E 4 Firmware Services 3 8 3 9 3 10 3 11 3 12 3 13 3 14 3 15 3 16 Monitoring 3 35 3 8 1 Process Data Monitoring Process Data Watchdog 3 37 3 8 2 Connection Monitoring Host Checking 3 39 3 8 3 Data Interface DTI Monitoring 3 42 3 8 4 I O Fault Response Mode 3 46 3 8 5 Handling the NetFail Signal Testing With ETH SetNetFail 3 48 IN
12. IS Table 1 12 Data jumper see Figure 1 15 No Function Meaning 8a 011 Local bus signal Data 8b DO1 Local bus signal Data OUT 8c DCLK Clock signal local bus 1 28 PHOENIX 654403 CONTACT FL IL 24 Load capacity of the jumper contacts 1 11 Circuits Within an Inline Station and Provision of the Supply Voltages There are several circuits within an Inline station These are automatically set up when the modules have been properly installed The voltages of the different circuits are supplied to the connected modules via the potential jumpers Observe the maximum current carrying capacity of the jumper contacts on the side for each circuit The load capacities for all potential jumpers are given in the following sections For voltage connection refer to the notes given in the module specific data sheets 654403 PHCENIX 1729 FL IL 24 BK B UM E 1 11 1 Supply of the Ethernet Bus Coupler The supply voltage Upgy and the segment voltage Us must be connected to the Ethernet bus coupler From the supply voltage Ugk the voltages for the logic circuit 7 5 V and the supply of the modules for analog signals Uana 24 V are internally generated The segment voltage is used to supply the sensors and actuators PHOENIX CONTACT FL IL 24 Ord No 2862327 Internal jumper in the modul
13. 2 8 2 5 Web Based 2 9 ii PHC NIX on CONTACT Table of Contents 2 5 1 Calling Web Based Management WBM 2 9 2 5 2 Structure of the Web Pages 2 10 2 5 3 Layout of the Web Pages 2 11 2 5 4 Password Protection 2 11 2 5 5 Process Data Access via 2 12 2 6 Factory Line I O 2 17 2 6 1 Factory Line I O Browser 2 17 2 6 0 Configurator sssssssssseeeeenns 2 18 3 JDUvVer oo WEBS draco Cnt odd Clam uh e dari ro CO erp TAa seu 3 3 3 1 3 3 3 1 1 Hardware and Software User Manual 3 3 3 2 The Software 3 3 3 2 1 Ethernet Inline Bus Terminal Firmware 3 4 3 2 2 Driver Software 3 4 3 3 Support and Driver Update 2 3 5 3 4 Transfer of 3 7 3 4 1 Position of the Process Data Example 3 8 3 5 Startup Behavior of the Bus 3 9 3 5 1 Plug amp Play Mode 3 9 3 5 2 Expert Mode
14. 4 14 4 3 5 Load Configuration 4 16 4 3 6 Terminate Load Configuration Service 4 20 4 3 7 Read Configuration Service 4 22 4 38 Complete Read Configuration Service 4 29 4 3 9 Delete Configuration 4 32 4 3 10 Create Configuration Service 4 33 4 3 11 Activate Configuration Service 4 36 4 3 12 Control Device Function Service 4 38 4 3 13 Reset Controller Board 4 40 4 4 Services for Direct INTERBUS 4 42 4 4 1 Start Data Transfer 4 42 4 4 2 Alarm Stop 2 4 44 4 5 Diagnostic 40 440 0 000000 nennen 4 45 4 5 1 Get Error Info 4 45 4 5 2 Get Version Info Service 4 52 4 6 X Error Messages for Firmware 4 56 4 6 1 Overview 4 56 654403 PHOENIX 4 1 CONTACT FL IL 24 BK B PAC UM E 4 6 2 Positive 4 57 4 6 3 Error
15. DDI NF LISTENER ERR 0x0002 Listener task error DDI NF RECEIVER ERR 0x0003 Receiver task error DDI NF ACCEPT ERR 0x0004 Accept function error DDI NF ECHO SERVER ERR 0x0005 Echo server task error DDI NF HOST CONTROLLER ERR 0x0006 Host controller task error DDI NF DTI TIMEOUT 0x0007 DTI timeout occurred DDI NF HOST TIMEOUT 0x0008 Host timeout occurred DDI NF USER TEST 0x0009 NetFail set by user DDI NF CONN ABORT 0x000A Connection aborted DDI NF INIT ERR 0x000B Initialization error DDI NF DTI WATCHDOG 0 000 Process data watchdog triggered DDI NF MBUS TIMEOUT 0x000D Modbus timeout occurred Acknowledges the NetFail Signal The Net Fail signal can be acknowledged using the web based management or by setting Bit 1 in the Command Word of the Modbus register 4076 or using the ETH ClrNetFailState service 3 36 PHCENIX CONTACT 654403 Driver Software IS 3 8 1 Process Data Monitoring Process Data Watchdog 3 8 1 1 Process Data Watchdog Function A process data watchdog is integrated into the bus terminal to avoid uncontrolled setting resetting of the Inline station outputs in the event of an error If outputs of the stations are set ensure the controlling process access to the station In an event of an error e g network line interrupted or functional error in the controlling process the bus
16. Start FW Date byte 6 Start FW Time byte 1 Start FW Time byte 6 HW Art No byte 1 HW Art byte 8 HW Art Name byte 1 HW Art Name byte 30 HW Motherboard ID HW Motherboard ID byte 1 byte 2 HW Motherboard ID HW Motherboard ID byte 2 byte 4 HW Version byte 1 HW Version byte 2 HW Vendor Name byte 1 HW Vendor Name byte 20 HW Serial No byte 1 HW Serial No byte 12 HW Date byte 1 HW Date byte 6 6544038 PHCENIX CONTACT 4 53 FL IL 24 Negative message Word 1 Word 2 Word 3 Word 4 Bit E 0 832 code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0055 55 parameter words with a negative message 000244 2 parameter words Result Result of the service processing 000044 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause Version information for the hardware and firmware Every byte indicates the ASCII code for a character FW_Version Version of the firmware kernel 4 bytes e g
17. or if an error occurred Result parameter 0000hex describes the error cause A service request confirmation consists of a block of data words The parameters that are contained in this block are given in hexadecimal nex or binary pin notation The structure of all service descriptions is as follows 4 2 1 Service Name of the Service Describes the functions of the service conditions which must be met before a service is called to enable successful processing Syntax Name of the Service Request Codehex Word 1 Word 2 Word 3 Word 4 654403 4 5 FL IL 24 BK PAC UM E Word 5 Bit m eee Code OXXXhex Command code of the service request hexadecimal notation Parameter_Count Number of subsequent words 0000 If the service request does not have parameters XXXXhex Otherwise length of the parameter data record number of parameter words Parameter Parameters are described individually Parameters that are organized byte by byte are separated by a vertical line If a parameter extends over several data words this is indicated by a line with three dots Parameter blocks Parameter blocks are marked in bold outline The individual parameters are described in the following section Syntax Name_of_the_Service_Confirmation Codenex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3
18. 3 11 3 5 5 Changing and Starting a Configuration in P amp P Mode 3 13 3 6 Changing a Reference Configuration Using the Software 3 14 3 6 1 Effects of Expert 3 14 3 6 2 Changing a Reference Configuration 3 14 3 7 Description of the Device Driver Interface DDI 3 16 dntroduction eR ttt 3 16 3 7 2 OVervieW ssi t YE n 3 17 3 7 8 Working Method of the Device Driver Interface 3 17 3 7 4 Description of the Functions of the Device Driver Interface 3 20 654403 PHCENIX 3 1 CONTACT FL IL 24 BK B PAC UM E 3 8 Monitoring m 3 37 3 8 1 Process Data Monitoring Process Data 3 39 3 8 2 Connection Monitoring Host Checking 3 41 3 8 3 Data Interface DTI Monitoring 3 44 3 8 4 I O Fault Response 3 48 3 8 5 Handling the NetFail Signal Testing With _ 3 50 3 9 IN Process Data 3 58 3 10 Notification en 3 62 3 11 Programming Support 3 65 3 11 1 3 65 3 12 Description of the
19. js Parameters NONE Return value INTEGER 0 for OK 111 for error kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk int CreateConnection void 3 88 PHCENIX 654403 CONTACT Driver Software IBDDIRET ret Mailbox connection ret DDI DevOpenNode OPEN MXI DDI RW amp mxiHnd if ret ERR OK printf nError creating mailbox connection Error code 54 printf n TEST ABORTED fflush stdout return 111 else printf nMailbox connection OK Handle d mxiHnd Data channel connection ret DDI DevOpenNode OPEN DTI DDI RW amp dtiHnd if ret ERR OK printf nError creating data channel connection Error code ret printf n TEST ABORTED fflush stdout return 111 else return 0 printf nData channel connection OK Handle d dtiHnd ret kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk DeleteConnection FUNCTION Parameters NONE Return value INTEGER 0 for OK 111 for error RA kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk int DeleteConnection void 654403 H N IX CONTACT 3 89 FL IL 24 IBDDIRET ret Close mailbox channel ret DDI DevCloseNode mxiHnd if ret ERR OK printf nError clos
20. 654403 PHCEN IX 1 57 CONTACT FL IL 24 BK B UME Analog input and output modules require different shielding connections The cable lengths must also be considered Table 1 19 Overview shield connection of analog sensors actuators Module Type Connection to the Cable Connection to the Sensor Module Length Actuator Analog input Within the module lt 10m module IB IL Al 2 grounding is connected to 32 81 ft SF FE via an RC element gt 10m Connect the sensor directly to 98 43 ft PE Via shield connection lt 10m Analog output clamp directly onto FE 32 81 ft module IB IL AO gt 10m Isolate the actuator with an RC 32 81 ft element and connect it to PE 1 15 2 1 Connecting an IB IL 24 AI 2 SF Analog Input Module e Connect the shielding to the shield connector see Section 1 16 2 Connecting Shielded Cables Using the Shield Connector e Whenconnecting the sensor shielding with FE potential ensure a large surface connection Within the module ground is connected to FE via an RC element 55200043 Figure 1 33 Connection of analog sensors signal cables 10 m 32 81 ft A Module side B Sensor side 1 58 PHCENIX 654403 CONTACT FL IL 24 IS If you want to use both channels of the IB IL Al 2 SF module there are different ways of connecting the shielding depending on the cross section 1 Use amulti wire cable for the connection of bo
21. Polarity reversal bus coupler supply Serial diode in the lead path of the power supply unit in the event of an error only a low current flows In the event of an error the fuse in the external power supply unit does not trip Ensure protection of 2 A by fuses through the external power supply unit Bus Interface of the Lower Level System Bus Interface Inline local bus Electrical isolation No Number of Inline terminals that can be connected Limitation through software Limitation through power supply unit 63 maximum Maximum logic current consumption of the connected local bus modules Ima lt 2 A DC Interfaces Ethernet interface Number One Connection format 8 pos RJ45 female connector on the bus coupler Connection medium Twisted pair cable with a conductor cross section of 0 14 mm to 0 22 mm 26 AWG to 24 AWG 654403 PHCENIX CONTACT FL IL 24 BK B UM E Interfaces Continued Cable impedance 100 Q Transmission rate 10 100 Mbps Maximum network segment expansion 100 m 328 08 ft Protocols MIBs Supported protocols TCP UDP BootP Mechanical Tests Shock test according to 60068 2 27 Operation 25g 11 ms period half sine shock pulse Storage transport 50g 11 ms period half sine shock pulse Vibration resistance according to IEC 60068 2 6 Ope
22. Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Bit pce UR CEPR WR 0 Key Code 0306 44 Command code of the service request Parameter Count Number of subsequent words XXXXhex Extension Length 1 2 New Config 0001 The configuration frame is created again An existing configuration frame is overwritten 0000hex Updates the existing configuration frame Frame Reference 0x0001 hex Device Count Number of INTERBUS devices which are included in the existing configuration frame or the new one to be loaded Extension Length 0x0000 Extension Not supported Entries are ignored 4 14 654403 Firmware Services Syntax Initiate_Load_Configuration_Confirmation 8306hex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit 0 Code 8306 Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0001hex 1 parameter word with a negative message 0002 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 6544
23. co the connector 61560021 IB IL SCN PWR IN CP Art No 27 27 63 7 bb 027 External jumper Figure 1 22 Power connector for supply from a single power supply unit 654403 PHCENIX 1 37 CONTACT FL IL 24 BK B UM E Potentials The isolation of the circuit of a digital module to the communications Digital module power is only ensured if Ugk and Uy Us are provided from separate power supplies An example of this principle is shown in Figure 1 23 on a section of an Inline station IB IL 24 PWR IN IB IL 24 DI 2 IB IL 24 DO 2 2A IB IL 24 PWR IN Local bus UL DEES DEES 61560013 Figure 1 23 Example Interruption creation of the potential jumpers by means of the power terminal The areas hatched in the figure XXXXX show the points at which the potential jumpers are interrupted 1 38 PHCENIX 654403 CONTACT FL IL 24 Potentials analog The I O circuit measurement amplifier of an analog module receives module floating power from the 24 V supply voltage Uana The power supply unit with electrical isolation is a component of an analog module The voltage Uana is looped through in each module and so is also available to the next module FL IL 24 BK B IB IL Al 2 SF uc Local bus UL Unna UL GND IB IL Al 2 SF electronic Us Un ES a 65440011 Ethernet Usk 0 05 Figure 1 24 Electrical isolation between Ethernet bus coupler and
24. 38 2E 39 37 for Version 3 97 FW State Firmware status 6 bytes e g 62 65 64 61 00 00 for beta with preliminary version FW Date Creation date of the firmware 6 bytes e g 31 37 30 33 30 314 for 17 03 01 FW Time Creation time of the firmware 6 bytes e g 31 34 31 30 32 30 for 14 10 20 4 54 PHCNIX 654403 CONTACT Firmware Services Host_Type Host_Version Type of the host specific firmware interface 0 FL IL 24 BK 20 byte Version of the host specific firmware interface 4 byte Host_State Status of the host specific firmware interface 6 byte Host_Date Creation date of the host specific firmware interface 6 byte Host_Time Creation time of the host specific firmware interface 6 byte Start_FW_Version Version of the start firmware 4 byte Start_FW_State Status of the start firmware 6 byte Start_FW_Date Creation date of the start firmware 6 byte Start_FW_Time Creation time of the start firmware 6 byte HW_Art_No Order No of the controller board 8 byte HW_Art_Name Order designation of controller board 30 byte HW Motherboard ID Identification of the motherboard 9 32 43 for 2C 4 byte HW Version Version of the hardware 2 byte HW Vendor Name Manufacturer of the controller board 20 byte HW Serial No Serial number of the controller board 12 byte HW Date Creation date of the controller board 6 byte 654403 PHCENIX 4 55 CONTACT
25. Cause Remedy Cause Remedy ERR_DEV_NOT_READY 0089 local bus master was addressed even though it was not ready Request a reset of the local bus master using the GetIBSDiagnostic function on the ready bit in the diagnostic bit register Once this bit is set the local bus master can be addressed ERR_INVLD_PERM 008 An attempt has been made to execute a function a channel for which the relevant access rights were not logged in when opening the data channel This error occurs e g if you want to write to the Data Interface but read only rights were specified on opening the channel DDI READ constant Close the channel and open it again with modified access rights ERR_INVLD_CMD 008Chex This error message is generated if you are working with older driver libraries or older DLLs Use an up to date driver ERR_INVLD_PARAM 008Dhex This error message is displayed if invalid parameters are used in the command Check the validity of the parameters used 654403 PHCENIX s CONTACT FL IL 24 3 15 2 Error Messages When Opening a Data Channel ERR NODE NOT PRES 0090 Cause An attempt was made to open a data channel to a node which is not present Remedy Select the following node IBS ETH Node 1 Local bus master ERR_INVLD_DEV_NAME 0091 hex Cause An unknown device name was specified as a parameter on opening a data channel Remedy Select a correct devi
26. DDI MXI USIGN16 msgType ACCESS Message type structure USIGN16 msgLength Length of the message in bytes 3 32 H 654403 Driver Software Example USIGN16 DDIUSerID Message ID USIGN8 msgBlk Pointer to the message data T DDI MXI ACCESS UNIX Windows NT 2000 IBDDIHND mxiHnd IBDDIRET ddiRet T DDI MXI ACCESS mxiAcc USIGN8 iBuf 256 USIGN16 msgCode USIGN16 paraCounter USIGN16 parameter 128 unsignet int i mxiAcc msgLength mxiAcc DDIUserID mxiAcc msgType 0 mxiAcc msgBlk iBuf 256 0 ddiRet DDI RcvMessage mxiHnd amp mxiAcc if ddiRet ERR OK Evaluation of the message msgCode IB GetMsgCode iBuf paraCounter IB GetParaCnt iBuf for i20 i paraCounter 1 parameter i IB GetParaN iBuf 1 654403 PHCENIX aoe CONTACT FL IL 24 BK B PAC UM E Task Syntax Parameters Format of the T_IBS_DIAG structure Return value Example GetlBSDiagnostic The DDI GetlBSDiagnostic function reads the diagnostic bit register and the diagnostic parameter register The function receives a valid node handle and a pointer to a BS DIAG data structure as parameters After the function has been called successfully the structure components contain the contents of the diagnostic bit register and the diagnostic parameter register in processed form IBDDIRET IBDDIFUNC DDI GetlBSDia
27. Switch the power supply on A configuration is started as shown in the flowchart see Figure 3 6 up to Figure 3 9 During startup please observe the following Once the coupler has been switched on the previously found configuration is read and started as long as no errors are present In addition the active configuration is saved in the EEPROM as the reference configuration All connected Inline devices are integrated in the active configuration if the DIAG LEDs are continuously lit on all modules To prevent the accidental use of the wrong configuration process data can only be accessed when P amp P mode has been deactivated 654403 PHCENIX 3 13 CONTACT FL IL 24 BK B PAC UM E 3 6 Changing a Reference Configuration Using the Software 3 6 1 Effects of Expert Mode If expert mode object 2275 is activated automatic startup of the connected local bus is prevented The user must manually place the bus in RUN state by activating the configuration Activate_Configuration 0711 object or Create_Configuration 0710 object and by starting the local bus Start Data 0701 object In expert mode the bus terminal behaves in the same way as the gateways IBS 5 or IBS 24 ETH DSC I T 3 6 2 Changing a Reference Configuration Deactivate P amp P mode Activate expert mode for access to all firmware commands Place the bus in Active or Stop state e
28. s for buffer DDI_DTI_ data a ReadData format 5691A002 Figure 3 13 Using the macros for programming support 3 64 PHCEN IX 654403 CONTACT Driver Software 3 12 Description of the Macros Table 3 8 Driver software macros Macro Task Page IB_SetCmdCode Enters the command code 16 bit in the specified transmit 3 66 buffer IB_SetParaCnt Enters the parameter count 16 bit in the specified transmit 3 67 buffer IB_SetParaN Enters a parameter 16 bit in the specified transmit buffer 3 67 IB_SetParaNHiByte Enters the high order byte bit 8 to 15 of a parameter in the 3 67 specified transmit buffer IB_SetParaNLoByte Enters the low order byte bit 0 to 7 of a parameter in the 3 67 specified transmit buffer IB_SetBytePtrHiByte Returns the address of a parameter entry starting with the 3 67 high order byte bit 8 to 15 IB_SetBytePtrLoByte Returns the address of a parameter entry starting with the 3 69 low order byte bit to 7 IB_GetMsgCode Reads a message code 16 bit from the specified receive 3 69 buffer IB_GetParaCnt Reads the parameter count 16 bit from the specified receive 3 69 buffer IB_GetParaN Reads a parameter 16 bit from the specified receive buffer 3 69 IB_GetParaNHiByte Reads the high order byte bit 8 to 15 of a parameter from 3 70 the specified receive buffer IB GetParaNLoByte Reads the low orde
29. 0 ERR OK is returned Otherwise the return value is an error code Example Unix Windows NT 2000 IBDDIHND ddiHnd IBDDIRET ddiRet ddiRet ETH ClrNetFailStatus ddiHnd 3 52 PHCENIX 654403 CONTACT Driver Software ETH_SetNetFailMode Task The ETH_SetNetFailMode routine is used to change the behavior of the controller board in the event of a NetFail After startup the controller board is in standard mode ETH_NF_STD_MODE which means that if a NetFail occurs all outputs of the modules connected to the INTERBUS system are set to zero and the bus continues to run This behavior can be changed by calling the routine At present the controller board supports two different modes Standard mode the controller board behavior remains the same i e the outputs are set to zero in the event of an error Alarm stop mode not only are the outputs set to zero but an alarm stop command is also sent to the controller board If the function is executed successfully the routine returns the return value 0 ERR OK In the event of an error the return value is an error code see DDI_ERR H aj Syntax IBDDIRET IBDDIFUNC ETH_SetNetFailMode IBDDIHND nodeHd T ETH NET FAIL MODE netFailModelnfo The routine receives a valid node handle and a pointer to the structure described below as parameters In addition to a component in which the mode to be set is entered the structure contains a pointer to an optio
30. Ox0BO2 E PNM12 STATE CONFLICT 4 49 OxOBB1 E PNM12 DEVICE STATE 4 49 0 0010 E PNM12 MISSING DEVICE 4 49 0 0020 E PNM12 CONFIG MAU FAIL DO 4 50 0 0028 E PNM12 CONFIG MAU FAIL DI 4 50 0 004 E 12 INVALID ID 4 50 0 0080 E PNM12 MULTI ERR OUT 4 51 0 009 E PNM12 CONFIG LB TOO LONG OUT 4 51 OxFFFF CONTROLLER DEVICE NUMBER 4 51 Error Code Description E SM CFG NUM OF DEV TOO BIG 0A1Chex You exceeded the permitted number of specified or connected INTERBUS devices The maximum permissible number of INTERBUS devices is 63 Number of specified or connected INTERBUS devices E_SM_CFG_IND_ADDR_LIST_TOO_BIG OA2Enex The permitted number of internal indirect address list entries was exceeded You have reached the firmware memory limit You have too many modules that occupy only one byte or one nibble of address space in the data ring Reduce the number of modules occupying only one byte or one nibble of address space The maximum number of internal permitted indirect address list entries is 384 Arrange the modules so that the devices that require less than 1 word of address space are next to each other 4 48 PHGNIX 654403 CONTACT Firmware Services Cause Remedy Meaning Remedy Add_Error_Info Meaning Cause Remedy Add_Error_Info E_PNM12_STATE_CONFLICT 0B02 1 Maybe there is an empty configuration fra
31. Table 3 2 Overview of the functions in the DDI Functions page DDI_DevOpenNode 3 20 DDI_DevCloseNode 3 22 DDI DTI ReadData 3 24 DDI DTI WriteData 3 26 DDI DTI ReadWriteData 3 28 DDI SndMessage 3 30 DDI RevMessage 3 32 GetIBSDiagnostic 3 34 ETH_SetHostChecking 3 40 ETH_ClearHostChecking 3 42 ETH_SetDTITimeoutCtrl 3 44 ETH_ClearDTITimeoutCtrl 3 45 ETH_SetNetFail 3 49 ETH_GetNetFailStatus 3 49 ETH_ClrNetFailStatus 3 52 DDI_SetMsgNotification 3 56 DDI_ClrMsgNotification 3 56 ETH_ActivatePDInMonitoring 3 57 ETH_DeactivatePDInMonitoring 3 60 ETH_SetNetFailMode 3 53 ETH_GetFailMode 3 55 3 7 3 Working Method of the Device Driver Interface The entire Device Driver Interface DDI for the bus terminal operates as remote procedure calls It does not use the standard libraries due to time constraints A remote procedure call means that the relevant function is not executed on the local computer or the local user workstation client but on another computer in the network In this case this is the bus terminal for Ethernet The user does not notice anything different about this working method except that it is faster The sequence of a remote procedure call is shown in Figure 3 10 654403 PHCENIX CONTACT 3 17 FL IL 24 Editing data telegrams When a function is called the transfer parameters for the DDI function
32. The local bus connected directly to the controller board consists of more Inline devices than have been entered in the active configuration Check this local bus Error location Segment Position CONTROLLER_DEVICE_NUMBER FFFF 654403 PHCENIX FL IL 24 BK PAC UM E 4 5 2 Get_Version_Info Service Task This service can be used to read the type version manufacturing date etc of the hardware and firmware of your controller board Syntax Get_Version_Info_Request 032Anex Word 1 Word 2 Bit 2 0 Code 032Anex Command code of the service request Parameter_Count Number of subsequent words 0000 No parameter word Syntax Get_Version_Info_Confirmation 832 Ahex Positive message Word 1 Word 2 Word 3 Words 4 5 Words 6 8 Words 9 11 Words 12 14 Words 15 24 Words 25 26 Words 27 29 4 52 PHGNIX 654403 CONTACT Firmware Services Words 30 32 Words 33 35 Words 36 37 Words 38 40 Words 44 43 Words 44 46 Words 47 50 Words 51 65 Words 66 67 Word 68 Words 69 78 Words 79 84 Words 85 87 Bit Host Date byte 1 Host Date byte 6 Host Time byte 1 Host Time byte 6 Start FW Version byte 1 Start FW Version byte 2 Start FW Version byte 3 Start FW Version byte 4 Start FW State byte 1 Start FW State byte 6 Start FW Date byte 1
33. UE 0 Key Code 8309hex Message code of the service confirmation Parameter Count Number of subsequent words with a positive message and if Frame Reference 0000hex XXXXhex 5 Configuration Count with a positive message and if Frame Reference gt 0000hex and Start Entry No 0000 000Dhex 12 parameter words with a positive message and if Frame Reference gt 0000 and Start Entry No gt 0000pex value depends on the number of devices in the configuration frame and the number of enabled attributes with a negative message 0002 2 parameter words Result Result of the service processing 0000 Indicates a positive message The service request has been executed 654403 PHOENIX 4 25 CONTACT FL IL 24 BK PAC UM E Add Error Info More Follows Frame Reference Current Configuration Configuration Count Frame Reference x Frame Device Count Active Device Count Frame IO Bit Count Active IO Bit Count Used Attributes successfully The data is available in the following parameters Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed see also Add Error Info Additional information on the error cause XXXXhex 0000 Indicates that all requested entries contained in the service confirmation 0001 Indicates that the service confirmation
34. Word 2 Word 3 Word 4 Bit p 0 8351hex Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0004 with a negative message 000245 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Variable Count Number of read system parameters 0x0001 Variable ID ID of the read system parameter Value Value of the system parameter Add Error Info Additional information on the error cause 654403 PHOENIX 4 13 CONTACT FL IL 24 BK PAC UM E 4 3 4 Initiate Load Configuration Service Task The Initiate Load Configuration service prepares the controller boards to transmit a configuration with either the Load Configuration 030755 or the Complete Load Configuration 030A16x service onto the INTERBUSmaster To transmit a new configuration frame New Config parameter 0001 specify the Frame Reference and Device Count parameters total number of devices Prerequisite The parameterization phase must have been initiated with the Control Parameterization 030Ehex service before Syntax Initiate Load Configuration Request 0306
35. a module 1 50 PHCENIX 654403 CONTACT FL IL 24 1 14 4 Removal When removing a module proceed as follows Figure 1 30 e If there is a labeling field remove it A1 in Fig Eimer Lift the connector of the module to be removed by pressing on the back connector shaft latching A2 in Figure A e Remove the connector Fig B e Remove the left adjacent and right adjacent connectors of the neighboring modules C This prevents the voltage routing featherkeys and the keyway featherkey connection from being damaged There also is more space available for accessing the module e Press the release mechanism 01 in Fig D and remove the electronics base from the DIN rail by pulling the base straight back D2 in Fig D If you have not removed the connector of the next module on the left remove it now in order to protect the potential routing featherkeys and the keyway featherkey connection 654403 PHGNIX 1 51 CONTACT FL IL 24 BK B UM E 2 LINYITHLT 22 Replacing a module 2 HLT 240 32 65440006 Figure 1 30 Removing a module If you want to replace a module within the Inline station follow the removal procedure described above Do not snap the connector of the module directly to the left back on yet First insert the base of the new module Then reconnect all the connectors NN 1 52 P HCE 654403
36. can be set to a value in the range of 110 ms up to 65000 ms Return value IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code 3 44 ii CONTACT Driver Software Task Syntax Parameters Return value Example ETH_ClearDTITimeoutCtrl ETH_ClearDT ITimeoutCtrl function deactivates the node for monitoring process data activity This function only receives the node handle as a parameter which is also used to activate monitoring After the function has been called successfully monitoring via this channel and for this client is deactivated Other activated monitoring channels are not affected IBDDIRET IBDDIFUNC ETH_ClearDTITimeoutCtrl IBDDIHND nodeHg IBDDIHND nodeHd Node handle DTI for the bus terminal for which monitoring is to be deactivated The same node handle that was used for activating monitoring must also be used here IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code Unix Windows NT 2000 IBDDIHND ddiHnd IBDDIRET ddiRet ddiRet ETH ClearDTITimeoutCtrl ddiHnd 654403 PHCENIX 55 FL IL 24 BK B PAC UM E Table 3 5 3 8 4 Fault Response Mode In case the communication connection is disrupted the user can select the reaction of the FL IL 24 BK beforehand Use the DDI comma
37. infoPtr state Reading and writing only permitted when the bus is running if infoPtr state 0 00 0 printf nIBS not in RUN state gt Abort exit 0 Write zero to the DI8 module roci s 1 printf nWrite read and compare data Set buffer to ZERO dtiAcc length MAX MSG LENGTH dtiAcc address 0 dtiAcc dataCons DTI DATA WORD Specify data consistency word consistency here dtiAcc data locMsgBlk for i 0 i lt MAX MSG LENGTH i locRet DDI DTI WriteData dtiHnd amp dtiAcc locMsgB1k i 0 if locRet ERR OK printf nError resetting buffer Error code 0x 04X locRet Sleep 100 Loop for reading and writing 255 data items 654403 PHCENIX 3 93 CONTACT FL IL 24 Writing data dtiAcc length MAX MSG LENGTH dtiAcc address 0 dtiAcc dataCons DTI_DATA WORD dtiAcc data locMsgBlk DO8 is the first DO module IB PD SetDataN locMsgBlk 0 10ci locRet DDI DTI WriteData dtiHnd amp dtiAcc if locRet ERR printf nError writing data Error code Sleep 500 Read data from module 1 DI8 readAcc length MAX MSG LENGTH readAcc address 0 readAcc data locReadBlk locRet DDI DTI ReadData dtiHnd amp readAcc if locRet 0 printf nError reading data Error code Specify data consistency 0x 04X locRet 0 04
38. 3 Word 4 Bit 0 Code 8711he Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0001hex 1 parameter word with a negative message 0002 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 654403 PHGNIX 4 37 CONTACT FL IL 24 BK PAC UM E 4 3 12 Control Device Function Service Task This service can be used to send control commands to one or more INTERBUS Inline devices for example to acknowledge device status errors or an alarm output Syntax Control_Device_Function_Request 0714 Word 1 Word 2 Word 3 Word 4 List of Word 5 INTERBUS Word 6 devices Word n 2 Bit Ue 0 Key Code 071444 Command code of the service request Parameter Count Number of subsequent words Device Function 00044 Conf Dev All Confirming the peripheral faults PF of all devices devices Set Entry Count 0000 The list of INTERBUS devices is not required Entry Count 0000 If Device Function 00044 4 38 PHCENIX 654403 CONTACT Firmware Services Syntax Key Word 1 Word 2 Word 3 Word 1 Word
39. 384 XXXXXXXX xx Word 385 2 19 Word 575 Analog Input Table Modbus Address XX XXX X X XX X X X X X X x Word 192 Modbus Address Analog Output Table Word 576 XXXXXXXX x x x x x x x x BOOODOGOOOOOGCOC X X Word 193 4 CEFEEEEEFEEFFTTE Word 577 XX X X X XXX XXXXXXXX eX XXX XX KKK XXX XXX Word 194 4 Word 578 X X XXXXXXXXXXXXXX X X X X X X X X X X X X X X x x Word 195 Word 579 K X X X X X XX XXXXXXXX Word 767 61560027 Figure 5 1 Position of the input output data modules 5 8 PHCENIX 654403 CONTACT Modbus TCP Protocol 5 4 Executable Functions The FL IL 24 BK B PAC does not differentiate between Modbus register tables and Modbus input register tables The Modbus register tables and the Modbus input register tables are displayed in all four FL IL 24 BK B E A tables as well as in the error table Table 5 4 Executable Functions Function Func READ Q_TAB AQ_TA Special tion WRITE B Register Code Read 3 READ X X X X X Multiple Registers Read Input 4 READ X X X X X Registers Write 16 WRITE X X X Multiple Registers Read Coils 1 READ X dcs Read Input 2 READ X iis is Discretes Write Coil 5 WRITE X Write 6 WRITE X X X Single Register Read 7 READ ats ES za Exception Code Write 15 WRITE
40. 65440002 Figure 1 18 Main circuit FLIL24 BK B Ethernet bus coupler PWR IN Power terminal SEG F Segment terminal with fuse as an example of a segment terminal 1 32 PHOENIX 654403 CONTACT FL IL 24 Provision of Uy Function Voltage Current carrying In the simplest case the main voltage can be supplied at the bus coupler and in which case it is 24 V DC The power Uy can also be supplied via a power terminal A power terminal must be used if one of the following occurs 1 Different voltage areas e g 120 V AC are to be created 2 Electrical isolation is to be created 3 maximum current carrying capacity of a potential jumper Uy Us or GND total current of Us and Uy is reached 1 11 5 Segment Circuit The segment circuit or auxiliary circuit with segment voltage Us starts at the Ethernet bus coupler or a supply terminal power terminal or segment terminal and is led through all subsequent modules until it reaches the next supply terminal You can use several segment terminals within a main circuit and therefore segment the main circuit It has the same reference ground as the main circuit This means that circuits with different fuses can be created within the station without external cross wiring The voltage in this circuit should not exceed 24 V DC The current carrying capacity is 8 A maximum total current with the main capacity circuit If the limit value of the common p
41. 654403 CONTACT Table of Contents 5 Technical Data 6 3 6 1 Ordering Data d ene eene oet 6 11 654403 PHOENIX vii CONTACT FL IL 24 BK B UME viii PHGNIX 654403 CONTACT Section 1 This section informs you about the basic structure of low level signal modules the arrangement of the diagnostic and status indicators the potential and data routing FEIE24 BE B PAG aria ei pig ia intei dedit tue eee 1 3 1 1 General Functions essen nennen 1 3 1 1 1 Product 1 3 12 Structure of the FL IL 24 BK B PAC Bus Co pler cu ie ced Ie e pere vate 1 5 1 8 Local Status and Diagnostic 1 6 1 4 Connecting the Supply 1 7 1 5 Connector Assignment sssssssssseeeneeeenenennnene 1 8 1 6 Supported Inline 1 9 1 7 Basic Structure of Low Level Signal Modules sssssssseses eene 1 14 1 7 1 Electronics 4 4 1 15 1 7 2 Gonnectors iine eer Rt ee eee 1 16 1 8 X Function Identification and 1 20 1 9 Dimensions of Low Level Signal Modules 1 24 1 10 E
42. 68xxx format if a workstation with Intel format is used to create an application program The Inline local bus numbers words 16 bit according to the conventional counting method of the Programmable Logic Controller PLC Because consecutive words start on even byte addresses 1 byte 8 bits they are also numbered according to the even byte addresses For example the word which contains bytes 6 and 7 is assigned the number 4 The process data is sent to the computer as bytes Because the data on the bus terminal is in Motorola format it is also received in this format on the computer If the processor on the computer is in BigEndian format Motorola the data can also be processed further in a word oriented way without conversion In a processor in LittleEndian format Intel the data must be converted accordingly word oriented Word m Word m 1 High Low High Low INTERBUS byte byte byte byte n n 1 2 v v Computer n n 1 nez n 3 5691A001 Figure 3 12 Assignment of the process data between the local bus and the computer systems 654403 PHCENIX 3 63 CONTACT FL IL 24 Host Coprocessor board Control board Application program Transmit ros for buffer DDI_MXI_ ands vorono SndMessage format buffer DDI_MXI_ a RCVMessage format MOTOROLA Output buffer ALD MOTOROLA WriteData format Input
43. BK B Digital output modules Ethernet Inline local bus 15 0 iX X X X X X X X Word 1 X X X X Word 2 XXXXXXXXXXXXXXXX Word 3 X X Word 4 XXXXXXXXXXXXXXXX Word 5 XXXXXXXXXXXXXXXX Word 6 X Word 7 65440008 Figure 3 5 Position of the process data according to the physical bus configuration 3 8 PHCENIX 654403 CONTACT Driver Software 3 5 Startup Behavior of the Bus Terminal The startup behavior of the bus coupler is specified via two system parameters the Plug amp Play mode and the expert mode In the delivery state the P amp P mode is activated and the export mode is deactivated 3 5 1 Plug amp Play Mode IS P amp P mode activated FL IL 24 BK B PAC supports the socalled Plug amp Play mode P amp P This mode enables Inline modules connected in the field to be started up using the FL IL 24 BK B PAC bus coupler without a higher level computer The P amp P status active or inactive is stored retentively on the bus coupler In P amp P mode the connected Inline terminals are detected and their function is checked If this physical configuration is ready for operation it is stored retentively as reference configuration on the bus coupler The P amp P mode needs to be deactivated again so that the reference configuration will not be overwritten once again during the next startup of the bus coupler At the same time the deactivation of the P amp P mode also is th
44. DC 27 26272 IB IL 24 DO 16 PAC 16 outputs 500 mA 3 wire termination 24 V DC 28 61292 IB IL 24 DO 32 HD 32 outputs 500 mA 1 wire termination 24 V DC 28 60 93 4 IB IL 24 DO 32 HD PAC 32 outputs 500 mA 1 wire termination 24 V DC 28 62 822 IB IL DO 1 AC 1 output 12 V 253 V AC 500 mA 3 termination 28 36 74 8 IB IL DO 1 AC PAC 1 output 12 V 253 V AC 500 mA 3 wire termination 28 61920 IB IL DO 4 AC 1A 1 output 12 V 253 V AC 1 mA 3 wire termination 27 42696 IB IL DO 4 AC 1A PAC 1 output 12 V 253 V AC 1 mA 3 wire termination 28 61658 IB IL 24 230 DOR 1 W 1 PDT relay contact 5 V 253 V AC 3 A 28 36 434 IB IL 24 230 DOR 1 W 1 PDT relay contact 5 V 253 V AC 28 61 88 1 PAC IB IL 24 230 DOR 1 W PC 1 PDT relay contact 5 V 253 V AC 3 A for inductive and 28 60 400 capacitive loads IB IL 24 230 DOR 1 W PC 1 PDT relay contact 5 V 253 V AC 3 A for inductive and 2862178 PAC capacitive loads IB IL 24 230 DOR 4 W 4 PDT relay contacts 5 V 253 V AC 3A 28 36 42 1 IB IL 24 230 DOR 4 W 4 PDT relay contacts 5 V 253 V AC 3A 28 61878 PAC 1 10 PHCENIX 654403 CONTACT FL IL 24 Designation Contd Features Order No IB IL 24 230 DOR 4 W PC 4 PDT relay contacts 5 V 253 V AC for inductive and 28 60 41 3 capacitive loads IB IL 24 230 DOR 4 W PC 4 PDT relay contacts 5 V 253 V AC f
45. FL IL 24 BK PAC UM E 4 6 Error Messages for Firmware Services 4 6 1 Overview Table 4 6 Overview of error messages according to error codes Code Services Page 090554 INCORRECT PARAMETER 4 57 0907 OBJECT 4 57 091844 UNKNOWN CODE 4 57 0922 ACTION HANDLER CONFLICT 4 57 090A INCORRECT PARACOUNT 4 58 091Dhex ACTION HANDLER OVERLAP 4 58 OAO2hex INCORRECT STATE 4 58 0 18 INCORRECT ATTRIB 4 58 0A19 ex FRAME NOT SO BIG 4 58 22 INCORRECT TN NUMBER 4 58 2 DEVICE ZERO 4 59 OA51hex INCORRECT FRAME REF 4 59 0E22hex INTERNAL TIMEOUT 4 59 OE23 FUNCTION REG FREE 4 59 0 24 ACTION ERROR 4 59 4 56 PHOENIX 654403 CONTACT Firmware Services 4 6 2 Positive Messages ERR_OK 0000 Meaning After successful execution of a function the firmware generates this message as a positive acknowledgment Cause No errors occurred during execution of the function 4 6 3 Error Messages If the firmware generates one of the following codes as an acknowledgment this indicates that an error occurred during execution and the called function could not be executed successfully INCORRECT PARAMETER 09054 Cause Incorrect parameters were entered when calling the function Remedy Check the specified parameters NO OBJECT 0907 The object called does not exist Remedy Check the object c
46. LONG Message or command contains too many 3 81 parameters 009 ERR NO MSG No message present 3 81 009Chex ERR NO MORE MAILBOX No further mailboxes of the required size free 3 81 009Dhex ERR SVR USE Send vector register in use 3 82 009 ERR SVR TIMEOUT Invalid node called 3 82 3 76 654403 PHCENIX CONTACT Driver Software Table 3 9 Driver software messages Code Error Message Cause Page 009F rex ERR AVR TIMEOUT Invalid node called 3 82 00A9 ex ERR PLUG PLAY Invalid write access to process data in P amp P 3 83 mode 0100 ERR STATE CONFLICT This service is not permitted in the selected 3 83 operating mode of the controller 010155 ERR INVLD CONN TYPE Service called via an invalid connection 3 84 010255 ERR ACTIVATE PD Process IN data monitoring could not be 3 84 activated 010345 ERR DATA SIZE The data volume is too large 3 84 020054 ERR INVLD Unknown command 3 84 020155 ERR INVLD Invalid parameter 3 84 101044 ERR IBSETH OPEN The IBSETHA file cannot be opened 3 85 101344 ERR IBSETH READ The IBSETHA file cannot be read 3 85 101444 ERR IBSETH NAME The device name cannot be found in the file 3 85 1016 44 ERR IBSETH INTERNET The system cannot read the computer name 3 85 host address 3 14 Positive Messages ERR OK 0000 After successful execution of a function the
47. Line I O configurator is a software package for the easy configuration startup and diagnostics of Factory Line Ethernet bus terminals In particular process data exchange is supported via OPC in an easy to use manner You will find the software on the CD FL IL 24 CD Order No 28 32 06 9 The I O configurator is divided into two parts I O browser and OPC configurator 2 6 1 Factory Line I O Browser The bus structure is created using the I O Browser Out of all supported modules select those that you want to use in your station offline configuration or that you are using at the moment online configuration With regard to the online configuration you have the possibility to read in an existing bus structure and to test it Configuration During system planning the I O configurator offers an integrated online product catalog to help ensure optimal startup You have access to all supported Inline terminals which can be integrated into the Inline local bus by using drag and drop In the following I O browser window the bus structure is displayed on the left and the product catalog on the right Startup After installing the hardware you can start up the stations based on the configured data Diagnostics You can test the operating status of the stations at any time and also receive comprehensive support on correcting any errors with the help of the integrated INTERBUS technology 654403 PHGNIX 2 17 CONTACT FL I
48. NetFail status and the reason for the NetFail if applicable IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code struct USIGN16 status NetFailStatus USIGN16 reason Reason for the NetFail T ETH NET FAIL ETH NET FAIL ACTIVEOxFFFF NetFail signal triggered See also Causes for Fault Response on page 3 36 ETH NET FAIL INACTIVE0x0000 NetFail signal not triggered Unix Windows NT 2000 IBDDIHND ddihnd IBDDIRET ddiRet ETH NET FAIL netFailInfo USIGN16 nfStatus USIGN16 nfReason ddiRet ETH GetNetFailStatus ddiHnd amp netFailInfo if ddiRet ERR OK 3 50 H N IX 654403 CONTACT Driver Software nfStatus netFailInfo status nfReason netFailInfo reason 654403 PHCENIX 3 51 CONTACT FL IL 24 BK B PAC UM E ETH_CirNetFailStatus Task The ETH CirNetFailStatus function resets the NetFail signal This means that process data can be output again and the status of the NetFail signal is set to 0 The function is assigned a valid node handle for a DTI or data channel as a parameter Syntax IBDDIRET IBDDIFUNC ETH_ClrNetFailStatus IBDDIHND Parameters IBDDIHND nodeHd Node handle MXI or DTI for the bus terminal on which the NetFail status is to be reset Return value IBDDIRET If the function is executed successfully the value
49. Process Data 3 56 Notification Mode 2 enn 3 60 Programming Support Macros 3 63 3 11 1 Introduction 3 63 Description of the 2 3 65 3 12 1 Macros for Converting the Data Block of a Command 3 66 3 12 2 Macros for Converting the Data Block of a Message 3 69 3 12 3 Macros for Converting Input Data 3 72 3 12 4 Macros for Converting Output Data 3 73 Diagnostic Options of the Driver Software 3 76 3 13 1 Introd ctlon imei es 3 76 Positive Messages 3 77 Error Messages inne ee e tr eee 3 78 3 15 1 General Error Messages 3 78 3 15 2 Error Messages When Opening a Data Channel 3 80 3 15 3 Error Messages When Transmitting 3 81 3 15 4 Error Messages When Transmitting Process Data 3 83 Example 3 86 3 16 1 Demo Structure Startup 3 86 3 16 2 Example Program Source Code 3 88 M PY 4 3 OVE NISW ar Rete oe a dede 4 3 4 1 14 Services That can be Used in PHCENIX 654403 CONTACT Table of Co
50. Status command has the following format Table 5 26 Read Exception Status Byte No Meaning BYTE 0 Function code 7 The response to the Read Exception Status command has the following format Table 5 27 Answer to Read Exception Status Byte No Meaning BYTE 0 Function code 7 BYTE 1 Exception status 5 5 9 Data Format of the Exception Status Table 5 28 Data Format Exception Status Byte No Meaning BYTEO 5 Free BYTE 6 Exception status BYTE 7 Non occupied error 654403 PHCENIX 5 19 CONTACT FL IL 24 BK B PAC UM E 5 5 10 Exception Responses Table 5 29 Exception Responses N Designation Meaning 0 1 ILLEGAL The transmitted function code is not supported by this device version FUNCTION 2 ILLEGAL DATA The transmitted address is invalid for the device the combination of ADDRESS reference number and transmission length is wrong For a controller with 100 registers an access with an offset of 96 and a length of 4 is successful an access with an offset of 96 and a length of 5 can generate the exception response 2 3 ILLEGAL DATA The value of this request is invalid for this device VALUE DEVICE FAILURE The Plug amp Play mode still is active and thus prevents that data can be written NetFail has occurred n addition a DDI device could be connected that has exclusive write access In this case it is not pos
51. X aas E Multiple Coils Read Write 23 READ X X X X X Registers WRITE ETUR PHCENIX 5 9 CONTACT FL IL 24 BK B PAC UM E 5 5 Supported Function Codes The function codes are defined for Modbus memory mapping For this reason Table 5 3 is practical for the specification of the appropriate areas This table shows the mapping of the designations in the Modbus tables via the appropriate designations in the FL IL 24 BK B PAC tables The FL IL 24 BK B PAC supports the following Modbus function codes Read Multiple Registers function code 3 Write Multiple Registers function code 16 Read Coils function code 1 Read Input Discretes function code 2 Read Input Registers function code 4 Write Coil function code 5 Write Single Register function code 6 Read Exception Status function code 7 Write Multiple Coils function code 15 Read Write Registers function code 23 5 5 1 Read Multiple Registers This command reads 16 bit words from 1 to 125 in the Modbus register table Every part of the Modbus register table can be read using this function When reading the error table however the entire table must be read The Read Multiple Registers command has the following format Table 5 5 Read Multiple Registers Byte No Meaning BYTE 0 Function code 3 BYTE 1 2 Register table offset BYTE 3 4 Word Count 1 125 5 10 PHCENIX 654403 CONTACT Modbu
52. analog module The potential jumpers XXXXX hatched in the figure are not used in the analog module This means that the 24 V supply of the bus coupler or the power terminal is always electrically isolated from the I O circuit measurement amplifier of the analog module The I O circuit of the analog module is supplied by the analog circuit Unna 654403 PHCENIX 1 39 CONTACT FL IL 24 BK B UM E Electrically isolated supply Several electrically isolated segment or main circuits can be created by using power terminals A power terminal interrupts the Us Uy and GND potential jumpers and has terminal points for another power supply unit In this way the I O circuits of the Inline modules are electrically isolated from one another before and after the power terminal During this process the 24 V power supply units on the low voltage side must not be connected to one another One method of electrical isolation using a power terminal is illustrated in Figure 1 25 If a number of grounds are connected 0 to functional earth ground the electrical isolation is lost Because Us and Uy can be supplied separately it is possible to create separate segment circuits using a segment terminal Using a switch it is possible for example to create a switched segment circuit see Figure 1 25 on page 1 41 Us and Uy be protected separately yet still have a common ground potential Please observe the maximum total curr
53. and an ID for the function to be executed are copied into a data telegram network telegram on the client and sent to the host bus terminal via the Ethernet network TCP IP The host decodes the received data telegram accepts the parameters for the function and calls the function using these parameters The DDI_DTI_ReadData nodeHd dtiAcc function is called as an example in Figure 3 10 During function execution by the server bus terminal the thread process is in sleep state on the client until a reply is received from the server Once the function has been executed on the server the read data and the return value for the function are copied into a data telegram on the host and sent back to the client user workstation The workstation decodes this data telegram and makes the return value of the function available to the user This working method is the same for each DDI function which is executed on the server as a remote procedure call 3 18 H N IX 654403 CONTACT Driver Software Remote Procedure Call Process Local computer workstation Ethernet TCP IP IBS ETH controller board DDI_DTI_ReadData nodeHd dtiAcc Data telegram return ret DDI_DTI_ReadData nodeHd dtiAcc ret Data telegram 52254002 Figure 3 10 Execution of a remote procedure call FL IL 24 3 7 4 Description of the Functions of t
54. and unshielded cables are used in a station The cables for the I O devices and supply voltages are connected using the spring cage connection method This means that signals up to 250 V AC DC and 5 A with a conductor cross section of 0 2 mm through 1 5 mm AWG 24 16 can be connected The Ethernet cable is connected via an 8 pos RJ45 connector 1 16 1 Connecting Unshielded Cables 6138A016 Figure 1 35 Connecting unshielded cables 654403 PHCENIX 1 61 CONTACT FL IL 24 BK B UME Wire the connectors as required for your application When wiring proceed as follows e Strip 8 mm 0 31 in off the cable e Push a screwdriver into the slot of the appropriate terminal point Figure 1 35 A so that you can plug the wire into the spring opening Phoenix Contact recommends using a SFZ 1 0 x 3 5 screwdriver Order No 12 04 51 7 see CLIPLINE catalog from Phoenix Contact e Insert the wire Figure 1 35 B Remove the screwdriver from the opening This clamps the wire After installation the wires and the terminal points should be labeled 1 62 P H 654403 FL IL 24 1 16 2 Connecting Shielded Cables Using the Shield Connector 2 8mm 0 315 5981A023 Figure 1 36 Connecting the shield to the shield connector 654403 PHCENIX 1 63 CONTACT FL IL 24 BK B UM E Stripping cables IS Wiring the connectors Co
55. client This process is repeated maximum of three times Connection monitoring then assumes that a serious error has occurred and sets the NetFail signal outputs are set to zero Deactivating Monitoring If connection monitoring is no longer required it can be deactivated using the ETH_ClearHostChecking function Monitoring is only deactivated for the client and the connection which are specified by the node handle If the same client has additional DDI connections to the bus terminal and connection monitoring was also activated for these connections this client is still monitored via the other connections If a DDI connection is closed using DDI_DevCloseNode monitoring for this clientis also deactivated Additional connections are treated as above they are not reset and monitoring for these connections is not deactivated Echo Port on the Client PC Task Syntax Parameters ETH_SetHostChecking After the ETH_SetHostChecking function has been called successfully the client user workstation is addressed by the bus terminal at regular intervals If the client does not respond within the predefined time timeout time three additional attempts are made to address the client If there is still no response the NetFail signal is set and the TCP connection is aborted by the bus terminal IBDDIRET IBDDIFUNC ETH_SetHostChecking IBDDIHND nodeHd USIGN16 time IBDDIHND nodeHd Node handle MXI or DTI for the bus te
56. code Start_Entry_No Position of the first entry 0000 Only reads the header information for the configuration frame XXXXhex Reads the entries from the configuration directory from this number onwards Entry_Count Number of entries to be read The positive message transmits the requested entries from the configuration directory Depending on the Frame_Reference and Start Entry No parameters in the service request it has one of the following three structures Read Configuration Confirmation 8309 Positive message during service request with 0000hex Frame_Reference Start_Entry_No Not relevant 0000 0000hex 654403 FL IL 24 BK PAC UM E 2 structure Positive message during service request with gt 0000 Frame_Reference Start_Entry_No 0000 Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 7 Word 8 Word 9 Word 10 Word 11 Word 12 Word 13 Word 14 Word 15 gt 0000hex Not relevant 0000hex Bit ip 0 3 structure Positive message during service request with gt 0000 Frame Reference Start Entry No gt 0000 hex Word 1 Word 2 Word 3 Word 4 Word 5 4 24 654403 CONTACT Firmware Services Word 6 Word 7 Word 8 ores 1 Device nth device Negative message Word 1 Word 2 Word 3 Word 4 Bit db cc I ULL UIDES
57. coupler Des Color Status Meaning Electronics Module UL Green 24 V supply 7 V communications power interface supply present OFF 24 V supply 7 V communications power interface supply not present UM Green ON 24 V main circuit supply present OFF 24 V main circuit supply not present US Green 24 V segment supply is present OFF 24 V segment supply is not present Ethernet Port PP Green Plug amp Play mode is activated OFF Plug amp Play mode is not activated FAIL Red ON The firmware has detected an error OFF firmware has not detected an error 100 Green ON Operation at 100 Mbps if LNK LED active OFF Operation at 10 Mbps if LNK LED active XMT Green ON Data telegrams are being sent OFF Data telegrams are not being sent RCV Yellow ON Data telegrams are being received OFF Data telegrams are not being received LNK Green ON network connection ready to operate OFF network connection interrupted or not present 654403 PHGNIX 1 43 CONTACT FL IL 24 BK B UM E 1 13 2 Supply Terminal Indicators N i N N N O Ot c Ot 61560022 Figure 1 27 Possible indicators on supply terminals segment terminal with and without fuse and power terminal Diagnost
58. data description lists a default process data reference list and a default communication relationship list CRL according to the currently connected bus configuration In the device descriptions the attributes are initialized as follows Device Number According to the active configuration Length Code According to the active configuration ID Code According to the active configuration Device Level According to the active configuration Group Number For all INTERBUS devices FFFFhex No group numbers are supported Device State All INTERBUS devices are active 654403 PHCENIX 4 33 CONTACT FL IL 24 BK PAC UM E Syntax Create_Configuration_Request 0710 Word 1 Word 2 Word 3 Bit 0 Code 0710 54 Command code of the service request Parameter Count Number of subsequent words 000155 1 parameter word Frame Reference 0001 Syntax Create_Configuration_Confirmation 8710 Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit It 0 Key Code 871044 Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 000155 1 parameter word with a negative message 0002hex 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully 4 34 PHCENIX 654403 CONTACT Firm
59. does not contain all requested entries as the amount of data is larger than the mailbox that is available for the services Call the service again to read the remaining data Number of the read configuration frame The parameter contains the value that was transferred with the service request Number of the currently activated configuration frame Number of configured configuration frames Numbers of all stored configuration frames in ascending order Number of configured INTERBUS devices in the selected configuration frame Number of active INTERBUS devices in the selected configuration frame Number of configured I O bits in the selected configuration frame Number of active I O bits in the selected configuration frame Read attributes The parameter contains the value that was transferred with the service request 4 26 PHCENIX 654403 Firmware Services Start_Entry_No Entry_Count Configuration_Entry Position of the first entry or 0000 if only the header information was read Number of entries that are transmitted by the service confirmation The More_Follows parameter indicates if there are further entries Selected entries in the order of the physical bus configuration The attributes contained in every entry are enabled in the service request by the Used Attributes parameter see the Configuration Entry syntax on page 4 27 In the following the structure of a con
60. driver software generates this message as a positive acknowledgment Cause No errors occurred during execution of the function 654403 PHCENIX CONTACT 3 77 FL IL 24 BK B PAC UM E 3 15 Error Messages If the Device Driver Interface DDI generates one of the following error messages as a negative acknowledgment the function called previously was not processed successfully 3 15 1 General Error Messages These error messages can occur when calling any DDI function ERR_INVLD_NODE_HD 0085 Cause An invalid node handle was used when calling the function Remedy Use the valid node handle of a successfully opened data channel ERR_INVLD_NODE_STATE 0086 Cause An invalid node handle was used when calling the function This is the handle of a data channel that has already been closed Remedy Open the data channel or use one that is already open ERR_NODE_NOT_READY 0087 Cause The node to be used has not yet indicated it is ready i e the node ready bit has not been set in the status register of the coupling memory The cause of this may for example be a hardware fault Remedy Check whether the bus terminal has been started up ERR_WRONG_DEV_TYP 0088 Incorrect node handle An attempt has been made e g to access the mailbox interface with a node handle for the Data Interface 3 78 H N IX 654403 CONTACT Driver Software Cause Remedy Cause Remedy
61. followed could result in damage to hardware and software or personal injury The note symbol informs you of conditions that must strictly be observed to achieve error free operation It also gives you tips and advice on the efficient use of hardware and on software optimization to save you extra work The text symbol refers to detailed sources of information manuals data sheets literature etc on the subject matter product etc This text also provides helpful information for the orientation in the manual We Are Interested in Your Opinion We are constantly attempting to improve the quality of our manuals Should you have any suggestions or recommendations for improvement of the contents and layout of our manuals we would appreciate it if you would send us your comments Please use the universal fax form at the end of the manual for this PHGNIX 654403 CONTACT Statement of Legal Authority This manual including all illustrations contained herein is copyright protected Use of this manual by any third party deviating from the copyright provision is forbidden Reproduction translation or electronic and photographic archiving or alteration requires the express written consent of Phoenix Contact Violators are liable for damages Phoenix Contact reserves the right to make any technical changes that serve the purpose of technical progress Phoenix Contact reserves all rights in the case of patent award or listing of a r
62. g using the Alarm Stop command The reference configuration be downloaded or deleted The connected bus can be read using the Create Configuration command and it can be saved as the reference configuration as long as the bus can be operated The bus is started using the Start Data Transfer command If access to process data is rejected via an error message this means that no reference configuration is present 3 14 PHCENIX 654403 CONTACT Driver Software System parameters for the Set Value service 750 Variable ID System parameters Value Comment 22165 Up to date PD cycle time Read only 2240hex Plug amp play mode 0 Plug amp Play mode inactive 1 Plug amp Play mode active 2275hex Expert mode 0 Expert modus deactivated default 1 Expert mode active 2277 hex Fault response mode 1 Reset fault mode default 2 Hold Last State 0 Standard Fault Mode 2293hex Process data monitoring timeout 0 Process data watchdog deactivated 200 65000 Timeout value oS 654403 PH NIX 3 15 CONTACT FL IL 24 BK B PAC UM E 3 7 Description of the Device Driver Interface DDI 3 7 1 Introduction The Device Driver Interface DDI is provided for using the bus terminal services The functions of the DDI are combined in a library which must be linked 3 16 PHCENIX 654403 CONTACT Driver Software Remote procedure call 3 7 2 Overview
63. labeled individually using Zack markers These markers are covered when a connector is plugged in Using the markers on the connector and on the electronics base you can clearly assign both connector and slot 654403 PHGNIX 1 23 CONTACT FL IL 24 BK B UM E 1 9 Dimensions of Low Level Signal Modules Today small I O stations are frequently installed in 80 mm 3 150 in standard switch boxes Inline modules are designed so that they can be used in this type of control box The housing dimensions of a module are determined by the dimensions of the electronics base and the dimensions of the connector Electronics bases for low level signal modules are available in three widths 12 2 mm 24 4 mm and 48 8 mm 0 480 in 0 961 in and 1 921 in They take one 1 two 2 or four 4 12 2 mm 0 480 in wide connectors When a connector is plugged in each terminal depth is 71 5 mm 2 815 in The height of the module depends on the connector used The connectors are available in three different versions see Figure1 14 2 slot housing 745 2 815 5 2 815 ul 120 mm 4 724 Te be nis S Y la 12 2 mm 0 480 Figure1 11 Dimensions of the electronics bases 2 slot housing 55201023 1 24 PH NIX 654403 CONTACT FL IL 24 BK B PAC 4 slot housing
64. monitoring channels are not affected IBDDIRET IBDDIFUNC ETH ClearHostChecking IBDDIHND IBDDIHND nodeHd Node handle MXI or DTI for the bus terminal for which monitoring is to be deactivated The same node handle that was used for activating monitoring must also be used here IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code 3 8 3 Data Interface DTI Monitoring Error Detection and Response Client monitoring using connection monitoring can only determine whether a client can still be addressed It is not possible to determine whether the process that controls the bus terminal application program is still operating correctly An extremely serious error occurs when the controlling process is no longer operating correctly i e the bus terminal is no longer supplied with up to date process data and as a result incorrect output data is sent to the local bus devices DTI monitoring can detect if a message to the data interface of the bus terminal has failed to arrive and the appropriate safety measures can be implemented In this case the failure of the DTI data telegram sets the NetFail signal and resets the output data for the local bus devices to zero Activating Monitoring Monitoring of the data interface DTI is not activated immediately after the SetDTlTimeoutCtrl has been called but only after data is written to or read f
65. output word 576 577 Command Word 767 The bits are defined as shown in Section Table 5 37 The remaining bits are reserved for later use The activation deactivation of the Plug amp Play mode is executed in the least significant bit of the command word Bit 0 0 gt PP deactivated Bit 0 1 gt PP activated A NetFail occurred in this way the command word can be acknowledged by setting bit 1 If NetFail has been acknowledged successfully bit 1 is reset to zero Table 5 37 Network Interface Command Word 15 14 13 12 11 10 9 8 7 6 5 4131211 Reservierte Bits Clear Peripherial error Clear Net Fail Plug amp Play 1500090 5 24 PHCENIX 634403 CONTACT Modbus TCP Protocol 5 6 2 Status Word Table 5 38 Structure of the Input Discretes Table Input Discretes Table Address The first 16 input bits 0 1 Status word 191 The last word in the Input Discretes table are automatically reserved by the bus terminal as network interface status word The user can extract up to date diagnostic information from this work using the Ethernet host controller e g a PLC without using a configuration software Only two of the least significant bits have a function Bit 0 0 means that an error occured e g a bus error If bit O 1 no error occured Bit 1 indicates wether there is a NetFail one or n
66. side which means that the parameters are transmitted via the network just as they were transferred to the function The nodeHd parameter specifies the bus terminal in the network to which the request is to be sent The node handle must be assigned to a process data channel otherwise an appropriate error message is generated by the bus terminal IBDDIRET IBDDIFUNC DDI DTI ReadWriteData IBDDIHND nodeHd T DDI DTI ACCESS writeDTIAcc T DDI DTI ACCESS IBDDIHND nodeHd Node handle DTI for the connection to which data is to be written The node handle also determines the bus terminal which is to be accessed T DDI DTI ACCESS writeDTIAcc Pointertoa T DDI DTI ACCESS data structure with the parameters for write access T DDI DTI ACCESS readDTIAcc Pointertoa T DDI DTI ACCESS data structure with the parameters for read access IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code 3 28 P HCE 654403 Driver Software Format of the T DDI DTI ACCESS structure Example typedef struct USIGN16 length Amount of data to be read in bytes USIGN16 address Address in the DTI area byte address USIGN16 dataCons Desired data consistency area USIGN8 data Pointer to the data read and write T DDI DTI ACCESS UNIX Windows NT 2000 IBDDIHND dd
67. such as ACTIVATE_CONFIGURATION 0x0711 or START_DATA_TRANSFER 0x0701 3 5 3 Possible Combination of Modes Table 3 1 Possible combination of modes and their effects P amp P Expert Description Effect Diagram Mode Mode Deactive Deactive Standard situation The station sets valid configurations to Figure 3 6 the RUN state since the current configuration is identical on with the memory Process data exchange is possible page 3 11 Deactive Active A valid configuration is set to the READY state A process Figure 3 7 data exchage is only possible if the station has been set to on the RUN state using the firmware command page 3 11 Active Deactive The connected configuration is stored as reference Figure 3 8 configuration and the station is set to the RUN state on Process data exchange is not possible page 3 12 Active Active A physical configuration is stored as reference Figure 3 9 configuration and is set to the Ready state A process on data exchage is only possible if the P amp P mode is page 3 12 deactivated and the station has been set to the RUN state using firmware commands 3 10 PHCENIX 654403 CONTACT Driver Software 3 5 4 Startup Diagrams of the Bus Coupler Standard mode P amp P and expert mode deactivated Figure 3 6 Read connected configuration Operable configuration Ye Save as reference configuration Config
68. the Read Multiple Registers command starting with the beginning of the error table 1024 with a length of 64 registers It is impossible only to read parts of the error table Empty entries contain the 0 value 5 26 PHCENIX 654403 CONTACT Modbus TCP Protocol Deleting the Error Table Data If required the application can write the value into the first register 1024 of the error table using the Write Single Register command You cannot write into any other register using the client Table 5 41 Registers Diagnostic parameter register Diagnostic status register Entries in the Error Table Every error entry is two words long and is positioned as follows If an error occurs one or several bits are set within the diagnostic status register PF BUS or CTRL and a new entry is added to the error table The entry is displayed within the error table as shown below Table 5 42 Error Table Error No Error entry 2 words 1 Diagnostic parameter register Diagnostic status register 2 Diagnostic parameter register Diagnostic status register 3 Diagnostic parameter register Diagnostic status register 32 Diagnostic parameter register Diagnostic status register 654403 PHCENIX 5 27 CONTACT FL IL 24 BK B PAC UM E Table 5 43 Monitoring functions Monitoring The three following monitoring mechanisms are available in the Modbus operating mode
69. the client can successfully restore an interrupted Modbus connection 5 1 2 Modbus Interface The Modbus communication via the FL IL 24 BK B PAC is supported via the Modbus interface in accordance with standard port 502 5 1 3 Modubus Conformity Classes The FL IL 24 BK B PAC supports the Modbus conformity classes 0 and 1 5 4 PHCENIX 654403 CONTACT Modbus TCP Protocol 5 1 4 Modbus Message Format The Modbus TCP protocol has a special message format with the following structure Table 5 1 Modbus Message Format Byte No Meaning 0 1 Transaction identifier unique ID generated by the client BYTE 2 3 Protocol identifer 0 BYTE 4 Length field upper byte 0 all messages lt 256 BYTE 5 Length field lower byte number of the following bytes BYTE 6 Unit identifier BYTE 7 Modbus function code BYTE 8 In data if required 5 1 5 Modbus Byte Sequence Modbus uses the Big Endian format to display addresses and data elements This means that the most significant byte is sent first if a numeric value as individual or double word that is larger than an individual byte is transmitted Example The amount 0x1234 is transmitted in the following order 0x12 0x34 The amount 0x12345678 is transmitted in the following order 0x12 0x34 0x56 0x78 654403 PHCENIX 5 5 CONTACT FL IL 24 BK B PAC UM 5 1 6 Modbus Bit Sequence If a bit sequence is rea
70. to ensure reliable grounding even if the DIN rail is dirty or the metal grounding clip has been damaged Phoenix Contact specifies that the bus coupler must also be grounded via the FE terminal point e g with the USLKG 5 universal ground terminal block Order No 04 41 50 4 see Figure 1 32 0 N SS e ij R 2 5 ST d NER 5 50 an 40 69 NA S 65440007 Figure 1 32 Additional grounding of the FL IL 24 BK B PAC 654403 PHCENIX 1 55 CONTACT FL IL 24 BK B UM E FE potential jumper The FE potential jumper functional earth ground runs from the bus coupler through the entire Inline station Ground the DIN rail FE is grounded when a module is snapped onto the DIN rail correctly If supply terminals are part of the station the FE potential jumper is also connected with the grounded DIN rail rec NN Low level signal The other Inline low level signal modules are automatically grounded via the FE potential jumper when they are mounted adjacent to other modules Power level The FE potential jumper is also connected to the power modules 1 56 PHCENIX 654403 CONTACT FL IL 24 1 15 1 Shielding an Inline Station Shielding is used to reduce the effects of interference on the system In the Inline station the Ethernet cable and the module connecting cables for analog signals are shielded 1 15 2 Shielding Analog Sensors and Actuators IS
71. value 0 ERR is returned Otherwise the return value is an error code Unix Windows NT 2000 IBDDIHnd ddiHnd IBDDIRET ddiRet ddiRet ETH SetNetFail ddiHnd ETH_GetNetFailStatus The ETH_GetNetFailStatus function sends the NetFail status to the user which is determined by the node handle of the bus terminal The function is assigned a node handle for an open DTI or data channel and a pointer to a T_ETH_NET_FAIL structure as parameters After the function has been called successfully the structure components contain the status status of the NetFail signal and an error code reason for triggering the Netfail signal if the NetFail signal has been set If the NetFail signal is not set the status structure component has the value 0 Otherwise status has the value OxFFFF The reason structure component is only valid if the NetFail signal is set The possible values for reason be found in the IOCTRL H file 654403 PHCENIX 529 FL IL 24 Syntax Parameters Return value Format of the T_ETH_NET_FAIL structure Possible values for the status structure component Example IBDDIRET IBDDIFUNC ETH_GetNetFailStatus IBDDIHND nodeHd T ETH NET FAIL netFaillnfo IBDDIHND nodeHd Node handle MXI or DTI for the bus terminal on which the NetFail status is to be read T ETH FAIL netFaillnfo Pointer to a structure which contains the
72. word starting with the high order 3 74 byte bit 8 to 15 IB PD GetBytePtrLoByte Returns the address of a word starting with the low order byte 3 74 bit O to 7 The macros are defined for different operating systems and compilers in the Device Driver Interface so that they can be used universally 3 12 1 IB SetCmdCode n m Macros for Converting the Data Block of a Command Task This macro converts a command code 16 bit into Motorola format and enters it in the specified transmit buffer Parameters n USIGNB8 Pointer to the transmit buffer m USIGN16 Command code to be entered 3 66 PHCENIX 654403 CONTACT Driver Software Task Parameters Task Parameters Task Parameters Task Parameters Task IB SetParaCnt n m This macro converts the parameter count 16 bit into Motorola format and enters it in the specified transmit buffer The call is only necessary when dealing with a command with parameters The parameter count specifies the number of subsequent parameters in words n USIGNS Pointer to the transmit buffer m USIGN16 Parameter count to be entered IB SetParaN n m This macro converts a parameter 16 bit into Motorola format and enters itin the specified transmit buffer The call is only necessary when dealing with a command with parameters n USIGNS Pointer to the transmit buffer m USIGN16 Parameter No counting begins with 1 o USIG
73. 0 ERR is returned Otherwise the return value is an error code typedef struct USIGN16 mode Selects the monitoring moder USIGN16 address Start address of the area to be monitored USIGN16 numOfBytes Size of the area to be monitored USIGN8 maskData Pointer to buffer with the masking data The size of the buffer corresponds to numOfBytes VOID notifyFuncPtr IBDDIHND nodeHd T DDI DTI ACCESS dtiAcc Pointer to a function that is called if there is a change in the PD IN data USIGN32 timeout Timeout time in ms T PD MON define PD IN 0x0000 PD In Check is not activated define ETH PD IN CHK MODE UDP 0x0002 Send data over UDP port ETH_PD_IN_CHK_INACTIVE Not in use at present 3 58 H N IX 654403 CONTACT Driver Software ETH PD IN CHK MODE UDP The controller board sends the process data to the client using UDP The routine automatically determines which port is used i e the user does not normally have any information about the port used For this reason the user is provided with one routine that carries out all necessary tasks thus ensuring that this function is easy to use IBDDIRET IBDDIFUNC WaitForPDInIndication IBDDIHND nodeHd T DDI DTI ACCESS dtiAcc The WaitForPDInIndication function is only assigned the node handle of a valid data channel and a pointer to a DDI
74. 03 PHGNIX 4 15 CONTACT FL IL 24 BK PAC UM E 4 3 5 Load Configuration Service Task The configuration frame describes each of the specified INTERBUS devices in a separate numbered entry The order and the numbering of the entries corresponds to the physical bus configuration This service transfers the configuration data to the controller board in the form of a list Use the Used Attributes parameter to determine which attributes the list should contain Prerequisite Ensure that the controller board has been prepared for transmission with the following services Control Parameterization 030E16x Initiate Load Configuration 0306 6 Syntax Load Configuration Request 0307 Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 or 1 Device nth device Bit 0 Code 0307 44 Command code of the service request Parameter Count Number of subsequent parameter words XXXXhex value depends on the Entry Count parameter and the Used Atrributes parameter 4 16 PHOENIX 654403 CONTACT Firmware Services IS IS Used Attributes Choice of add on attributes The parameter is a 16 bit field in which every bit corresponds to an attribute Set the corresponding bit to 1 on the attribute that you want to transmit see the Configuration Entry syntax on page 4 17 Settings for theUsed Attributes parameter Bit 0 Device number Bit 1 Device code Example If
75. 192 168 36 205 3 20 H 654403 Driver Software Function Syntax Parameters Return value DDI DevOpenNode function opens a data channel to the bus terminal specified by the device name or to a node The function receives the device name the desired access rights and a pointer to a variable for the node handle as arguments If the function was executed successfully a handle is entered in the variable referenced by the pointer and this handle is used for all subsequent accesses to this data channel In the event of an error a valid value is not entered in the variable An appropriate error code is instead returned by the DDI DevOpenNode function which can be used to determine the cause of the error The node handle which is returned to the application program is automatically generated by the DDI or bus terminal This node handle has direct reference to an internal control structure which contains all the corresponding data for addressing the relevant bus terminal The local node handle is used to obtain all the necessary parameters for addressing the bus terminal such as the IP address socket handle node handle on the bus terminal etc from this control structure when it is subsequently accessed A control structure is occupied when the data channel is opened and is not released until the DDI_DevCloseNode function has been executed or the connection has been aborted The maxim
76. 2 Word 3 Word 4 Bit Control_Device_Function_Confirmation 871 4hex Positive message Negative message Code 8714 44 Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0001hex 1 parameter word with a negative message 0002 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 654403 FL IL 24 BK PAC UM E Task Prerequisite 4 3 13 Reset Controller Board Service This service can be used to initiate a controller board reset Before calling this service ensure that the state of your system permits a controller board reset Syntax Reset Controller Board Request 0956nex Word 1 Word 2 Word 3 Bit MEE 0 Key Code 0956hex Command code of the service request Parameter Count Number of subsequent words 000155 1 parameter word Reset Type 0001 cold restart always executes a cold restart Syntax Reset Controller Board Confirmation 8956 Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit A a
77. 218 50 End clamp fixed using screws E UK 12 01 442 50 Screwdriver according to DIN 5264 blade SZF 1 0 6 x 3 5 1204 517 width 3 5 mm 0 138 in 6 12 PHOENIX 654403 CONTACT We Are Interested Your Opinion We would like to hear your comments and suggestions concerning this document We review and consider all comments for inclusion in future documen tation Please fill out the form on the following page and fax it to us or send your comments suggestions for improvement etc to the following address Phoenix Contact GmbH amp Co KG Marketing Services Dokumentation INTERBUS 32823 Blomberg GERMANY Phone 49 0 52 35 3 00 Telefax 49 0 52 35 3 4 18 08 E Mail tecdoc phoenixcontact com 5050df17 PHCENIX CONTACT 449 0 52 35 3 4 18 08 FAX Reply Phoenix Contact GmbH amp Co KG Date Marketing Services Dokumentation INTERBUS Fax No From Company Name Department Address Job function City ZIP Phone code Country Fax Document Designation FL IL 24 BK B UM E Revision 03 My Opinion on the Document Form Is the table of contents clearly arranged Are the figures diagrams easy to understand helpful Are the written explanations of the figures adequate Does the quality of the figures meet your expectations needs Does the layout of the document allow you to find information e
78. 3 F to 185 F Degree of protection IP20 DIN 40050 IEC 60529 Class of protection Class 3 VDE 0106 IEC 60536 Humidity operation EN 60204 1 5 to 90 no condensation Humidity storage EN 60204 1 5 to 95 no condensation Air pressure operation 80 kPa to 108 kPa 2 000 m 6 561 66 ft above sea level Air pressure storage 70 kPa to 108 kPa 3 000 m 9 842 49 ft above sea level Preferred mounting position Perpendicular to a standard DIN rail Connection to protective earth ground The functional earth ground must be connected to the 24 V DC supply functional earth ground connection The contacts are directly connected to the potential jumper and FE springs on the bottom of the housing The terminal is grounded when it is snapped onto a grounded DIN rail Functional earth ground is only used to discharge interference Environmental compatibility Free from substances which would hinder coating with paint or varnish according to VW specification Resistance to solvents Standard solvents Weight 270 g typical 654403 PHCENIX 6 3 CONTACT FL IL 24 BK B UME 24 V Main Supply 24 V Segment Supply Connection method Spring cage terminals Recommended cable lengths 30 98 43 ft maximum do not route cable through outdoor areas Voltage continuation Via potential routing Special demands o
79. 47 IB IL 24 SEG F PAC Segment terminal 24 V DC with fuse 28 61 373 IB IL 24 SEG F D Segment terminal 24 V DC with fuse and diagnostics 28 36 68 3 IB IL 24 SEG F D PAC Segment terminal 24 V DC with fuse and diagnostics 28 61 90 4 IB IL 24 SEG ELF 24 V DC segment terminal with electronic fuse 27 27 789 IB IL 24 SEG ELF PAC 24 V DC segment terminal with electronic fuse 28 61 409 IB IL PD GND Terminal for GND potential distribution 28 63 06 7 IB IL PD GND PAC Terminal for GND potential distribution 28 62 99 0 IB IL PD 24V Terminal for potential distribution main voltage 28 63 054 IB IL PD 24V PAC Terminal for potential distribution main voltage 28 62 98 7 654403 PHGNIX 1 13 CONTACT FL IL 24 BK B UM E 1 7 Basic Structure of Low Level Signal Modules Regardless of the function and the design width an Inline low level signal module consists of the electronics base or base for short and the plug in connector or connector for short ZBFM marker for connectors d Transparent field Attachment for label plate i ZBFM marker for signal 1 2 marker for Back connector shaft latch Diagnostic and status indicators FE or signal terminals 3 4 Function color coding 2 9 ZBFM marker for signal 3 4 ZBFM marker for module identification Electronics base JH Nu w Data routing Slot coding 3 Front snap on mechanism Voltage routing Latch for DIN rail Feather
80. 470 654403 PHCENIX 1 9 CONTACT FL IL 24 BK B UME Designation Contd Features Order No IB IL 24 DO 2 2A 2 outputs 2 A 4 wire termination 24 V DC 27 26 243 IB IL 24 DO 2 2A PAC 2 outputs 2 A 4 wire termination 24 V DC 28 61 263 IB IL 24 DO 2 NPN 2 outputs with negative logic 500 mA 4 wire termination 24 VDC 2740119 IB IL 24 DO 2 NPN PAC 2 outputs with negative logic 500 mA 4 wire termination 24 V 2861496 IB IL 24 EDO 2 2 outputs 500 mA 4 wire termination 24 V DC extensible 27 42 599 diagnostics parameterizable outputs IB IL 24 EDO 2 PAC 2 outputs 500 mA 4 wire termination 24 V DC extensible 28 61 616 diagnostics parameterizable outputs IB IL 24 DO 4 4 outputs 500 mA 3 wire termination 24 V DC 27 26 25 6 IB IL 24 DO 4 PAC 4 outputs 500 mA 3 wire termination 24 V DC 2861276 IB IL 24 DO 8 8 outputs 500 mA 4 wire termination 24 V DC 2726269 IB IL 24 DO 8 PAC 8 outputs 500 mA 4 wire termination 24 V DC 28 61 289 IB IL 24 DO 8 NPN 8 outputs with negative logic 500 mA 28 63 546 4 wire termination 24 V DC IB IL 24 DO 8 NPN PAC 8 outputs with negative logic 500 mA 28 63 533 4 wire termination 24 V DC IB IL 24 DO 8 2A 8 outputs 2 A 4 wire termination 24 V DC 2742117 IB IL 24 DO 8 2A PAC 8 outputs 2 A 4 wire termination 24 V DC 28 61 603 IB IL 24 DO 16 16 outputs 500 mA 3 wire termination 24 V
81. BK PAC UM E 4 3 7 Read Configuration Service Task This service reads various entries of the configuration directory depending on the Frame_Reference and Start_Entry_No parameters Frame_ Start_ Entries Read by the Service Reference Entry_No 0001 nex 000044 Header information of the configuration frame CFG_Header selected with the Frame_Reference parameter 0001 gt 0000 Entries of the configuration frame CFG Entry selected with the Frame_Reference parameter Either the entire configuration frame or only one part e g a single INTERBUS device description can be read Syntax Read_Configuration_Request 0309 Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Bit Dom EE 0 Key Code 030944 Command code of the service request Parameter Count Number of subsequent words 0004 4 parameter words Frame Reference Number of the configuration frame 000154 Reads the reference configuration 0002hexreads in the physical bus structure Only relevant if Used Attributes Attributes to be read Frame Reference The parameter is a 16 bit field in which every bit gt 0000 corresponds an attribute Set the corresponding bit to 1 on the attributes to be read Settings for the Used_Attributes parameter 4 22 PHGNIX 654403 CONTACT Firmware Services Syntax 1 structure Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 7 Word 8 Bit 0 Device number Bit 1 Device
82. BUS The status is indicated in the diagnostic register In order to make sure that only valid data are displayed the diagnostic register also must be requested The same is valid in the event of a faulty configuration In this case the INTERBUS does not run and only internal values can be read in the XML file If an error occurs all data valid except for the data of the faulty terminal 654403 PHCENIX 2 15 CONTACT FL IL 24 BK B PAC UM E c TERMINAL TERMINAL TYPESFL IL 24 BK TERMINAL TYPE lt NAMI L IL 24 BK lt NAME gt 55 gt 172 16 16 207 lt ADDRESS XMODULE NUMBER S c MODULE lt DIAGN C STATUS DIAGNOSTIC PARAMETER REG BUS TERMINA Station Data OSTIC STATUS REGISTER gt JIAGNOSTIC PARAMETER REGISTER Diagnostic Register JULE TYPESDO cPD CHANNELS 16 PD WORDS 2 Data of first Digital Output Modul lt IL MODULE number lt MODULE TYPESDI DULE TYPE HANNELS gt WORDS gt 1 lt PD_WORD 17 gt 18847 PD PD IN worc Data of first Digital Input Modul lt PD_CHANNEL lt PD_WORDS PD IN worde 1 PD IN word PD OUT word PD OUT wordz PD CHANNELS 1 PD WORDS21 2 fie Lokal manet Figure 2 3 Screen for XML data 2 16 PHCENIX 654403 Startup Operation 2 6 Factory Line I O Configurator The Factory
83. Configuring and Installing the INTERBUS Inline IB IL SYS PRO UM E 27 45 554 Product Range User Manual RJ45 gray connector set for linear cable 2 pieces FL PLUG RJ45 GR 2 27 44856 RJ45 connector set green for crossed cable 2 pieces FL PLUG RJ45 GN 2 27 44 57 1 Double sheathed Ethernet cable FL CAT5 HEAVY 27 44814 Flexible Ethernet cable FL CAT5 FLEX 27 44 830 Assembly tool for RJ45 connector FL CRIMPTOOL 27 44 86 9 Media converter 660 nm FL MC 10BASE T FO POF 27 44 51 3 Voltage supplies QUINT PS see INTERFACE catalog Keying profile 100 pcs package CP MSTB see catalog 17 34 63 4 Zack markers for labeling terminals ZB 6 see CLIPLINE catalog Labeling field covering one connector IB IL FIELD 2 27 27 501 Labeling field covering four connectors IB IL FIELD 8 2727515 Insert strips for IB IL FIELD 2 perforated can be ESL 62X10 08 09 492 labeled using a laser printer marker pen or CMS system 72 strips 1 pcs package 654403 PHGNIX 6 11 CONTACT FL IL 24 BK B UME Description Order Designation Order No Insert strips for IB IL FIELD 8 perforated can be ESL 62X46 08 09 502 labeled using a laser printer marker pen or CMS system 15 strips 5 pcs package DIN EN 50022 DIN rail 2 meters 6 56 ft NS 35 7 5 PERFORATED 0801 73 NS 35 7 5 08 01 68 1 UNPERFORATED End clamp snapped on without tools CLIPFIX 35 30 22
84. DOO COW 26 8 OCDE INNOVATION IN INTERFACE User Manual Hardware and Firmware Manual for the Ethernet Inline Bus Coupler FL IL 24 BK B PAC Designation FL IL 24 BK B UME Order 2698766 LINATHLI GEG XIMDFichl LZEZIBE QDVA IHI FZ U 77 232 2245 0 MW gan e FL IL 24 BK B UME PHGNIX 654403 CONTACT Factory Line User Manual Hardware and Firmware Manual for the Factory Line Ethernet Bus Coupler FL IL 24 BK B PAC Designation FL IL 24 BK B UME Revision 03 Order No 26 98 76 6 This user manual is valid for FL IL 24 BK B PAC with Firmware Version 1 10 Phoenix Contact 07 2004 654403 PHCENIX CONTACT FL IL 24 qp Please Observe the Following Notes In order to ensure the safe use of your device we recommend that you read this manual carefully The following notes provide information on how to use this manual Requirements of the User Group The use of products described in this manual is oriented exclusively to qualified electricians or persons instructed by them who are familiar with applicable national standards Phoenix Contact assumes no liability for erroneous handling or damage to products from Phoenix Contact or external products resulting from disregard of information contained in this manual Explanation of Symbols Used The attention symbol refers to an operating procedure which if not carefully
85. DTI ACCESS structure The routine returns as soon as process data is received or the timeout time that was preset in timeout see T ETH PD IN MON has elapsed The components of the T DDI DTI ACCESS structure are used to access the process data The routine returns an integer value which indicates whether process data has been received and is ready to be evaluated or whether a timeout or another error caused the routine to be terminated A return value that is not zero always indicates an error that can be defined more specifically using the value Proceed as follows Activate process data monitoring with ETH ActivatePDInMonitoring Wait for process data input data with WaitForPDInIndication The standard DTI functions can be used to read and write input and output values at any time even if WaitForPDInIndication has been used in another thread to wait for an indication If the controller board transmits data more quickly than the client retrieves it the client saves a certain amount of this data to prevent it from being lost immediately The amount of data saved by the client depends on the system used and the settings in its TCP IP protocol stack The DDI DTI ACCESS structure is not explained here because it has already been described in detail in the standard DTI routines 654403 PHCENIX Sue CONTACT FL IL 24 BK B PAC UM E ETH_DeactivatePDInMonitoring Task The ETH DeactivatePDInMonitoring function deactiva
86. GN16 Parameter No USIGNS Address of the low order byte of the parameter in the transmit buffer 3 12 2 Macros for Converting the Data Block of a Message IB GetMsgCode n This macro reads the message code 16 bit from the specified receive buffer and converts it into Intel format n USIGN8 Pointer to the receive buffer USIGN16 Message code IB GetParaCnt n This macro reads the parameter count 16 bit from the data block of the message and converts it into Intel format The parameter count specifies the number of subsequent parameters in words n USIGN8 Pointer to the receive buffer USIGN16 Parameter count This macro only reads the parameter count for messages that also have parameters IB GetParaN n m This macro reads a parameter value 16 bit from the data block of the message and converts it into Intel format Pointer to the receive buffer Parameter No n USIGN8 m USIGN16 654403 PHCENIX FL IL 24 Return value Remark Task Parameters Return value Remark Task Parameters Return value Remark Task Parameters Return value USIGN 16 Parameter value This macro only reads the parameter value for messages that also have parameters IB GetParaNHiByte n This macro reads the high order byte bit 8 to 15 of a parameter from the specified receive buffer and converts it into Intel fo
87. IL AO 2 U BP 2 outputs 2 wire termination 24 V DC O 10 V x10 V 27 32 732 IB IL AO 2 U BP PAC 2 outputs 2 wire termination 24 V DC 0 10 V x10 V 28 61 46 7 Table 1 6 Special Function Modules Designation Features Order No IB IL SSI 1 absolute encoder input 4 digital inputs 4 digital outputs 500 mA 28 36 340 3 wire termination 24 V DC IB IL SSI PAC 1 absolute encoder input 4 digital inputs 4 digital outputs 500 mA 28 61 86 5 3 wire termination 24 V DC IB IL SSI IN 1 absolute encoder input 24 V DC 28 19 309 IB IL SSI IN PAC 1 absolute encoder input 24 V DC 2819574 IB IL INC 1 incremental encoder input 4 digital inputs 4 digital outputs 500 28 36 324 mA 3 wire termination 24 V DC IB IL INC PAC 1 incremental encoder input 4 digital inputs 4 digital outputs 500 28 61 84 9 mA 3 wire termination 24 V DC IB IL CNT 1 counter input 1 control input 1 digital output 500 mA 3 wire 28 36 33 7 termination 24 V DC IB IL CNT PAC 1 counter input 1 control input 1 digital output 500 mA 3 wire 28 61 852 termination 24 V DC IB IL IMPULSE IN 1 input for magnetostrictive linear measuring scales with impulse 28 19 23 1 interface IB IL IMPULSE IN PAC 1 input for magnetostrictive linear measuring scales with impulse 28 61 85 2 interface Table 1 7 Motor Terminals Designation Features Order No IB IL 24 TC Thermistor terminal 2727417 IB IL 24 TC PAC Thermistor terminal 28 61360 1 12 PHCENIX 654403 CONTACT FL IL 24
88. L 24 BK B PAC UM E Inline station structure with I O configurator Robot Control icf Factory Line 10 Browser iof x File Edit Paste View Help Test Read Import New Station Forward Backward Delete IB IL 24 DO 16 B Ethemet Device IB IL 24 DO 2 24 B IET 008 BER 61 24008 IB IL 24 DO 16 IB IL 24 EDI 2 DESINA DI 8 IB IL 24 EDI 2vxx IB IL 24 DI 16 IL 24 SEG ELF 018 i IB IL 24 SEG F D IB IL AO 1 5 IB IL 24 230 DOR 1 w IB IL AO 2 U BP IB IL Al 2 SF IB IL 1 5 IB IL AO 1 SF i Press F1 for Help INUM 4 Figure 2 4 browser screen 2 6 2 Configurator OPC Data Exchange Process data exchange via OPC is supported in an very easy to use manner Use the OPC Configurator to assign OPC items to the Inline station structure for the respective terminal points With the OPC Configurator you can configure the INTERBUS OPC Server from Phoenix Contact Designation IBS OPC SERVER Order No 27 29 12 7 for this bus terminal type The project file and an OPC server provide the application program or the visualization with direct access to the process data for the bus configuration 2 18 PHGNIX 654403 CONTACT Startup Operation Linking Items and Physical Terminal Points An item can be created for each physical I O terminal in your bus configuration and the entire configuration can be stored in a project file The project file and an OPC serv
89. Load_Configuration service could not be executed number of connected Inline modules is either zero or greater than 63 Remedy Change the number of connected Inline modules INCORRECT_FRAME_REF 0A51 nex Cause The Frame_Reference value is not one 1 Remedy Change the Frame_Reference to 1 INTERNAL_TIMEOUT OE22nex Cause The function start reg was not reset within the timeout Additional info xxxXhex Timeout in hex FUNCTION REG NOT FREE 0 23 Cause The function_start_reg is not empty ACTION_ERROR 0E24hex Cause The service could not be executed successfully Additional info 00054 Bus data could not be detected Additional info 00 5 The configuration could not be activated 654403 PHCENIX 4 59 CONTACT FL IL 24 BK PAC UM E 4 60 PHGNIX 654403 CONTACT Section 5 This section informs you about functions of the Modbus TCP protocols Modbus TCP PFOIDOOL 5 3 5 1 Modbus Protocol edi eee 5 4 5 1 1 Modbus 800 5 4 5 1 2 Modbus 5 4 5 1 3 Modubus Conformity 5 4 5 1 4 Modbus Message 5 5 5 1 5 Modbus Byte 5 5 5 1 6 Modbus Bit 5 6 5 2 Mo
90. N16 Parameter value to be entered IB SetParaNHiByte n m This macro converts the high order byte bit 8 to 15 of a parameter into Motorola format and enters it in the specified transmit buffer n USIGNS Pointer to the transmit buffer m USIGN16 Parameter No o USIGNS Parameter to be entered byte IB SetParaNLoByte n m o This macro converts the low order byte bit O to 7 of a parameter into Motorola format and enters it in the specified transmit buffer n USIGNS Pointer to the transmit buffer m USIGN16 Parameter No o USIGNS Parameter to be entered byte IB SetBytePtrHiByte n m This macro returns the address of a parameter entry starting with the high order byte bit 8 to 15 The address is USIGNE data type 654403 PHCENIX 97 FL IL 24 Parameters n USIGNB8 Pointer to the transmit buffer m USIGN16 Parameter No Return value USIGNB Address of the high order byte of the parameter in the transmit buffer 3 68 PHCENIX 654403 CONTACT Driver Software Task Parameters Return value Task Parameters Return value Task Parameters Return value Remark Task Parameters IB SetBytePtrLoByte n This macro returns the address of a parameter entry starting with the low order byte bit to 7 The address is USIGNE data type n USIGNB8 Pointer to the transmit buffer m USI
91. NIX ae CONTACT FL IL 24 DDI_DTI_WriteData Task The DDI DTI WriteData function is used to write process data to the bus terminal The function is assigned the node handle and a pointer to a T DDI DTI ACCESS data structure The DDI DTI ACCESS structure contains all the parameters that are needed to access the process data area of the bus terminal and corresponds to the general DDI specification A plausibility check is not carried out on the user side which means that the parameters are transmitted via the network just as they were transferred to the function The nodeHd parameter specifies the bus terminal in the network to which the request is to be sent The node handle must also be assigned to a process data channel otherwise an appropriate error message is generated by the bus terminal Syntax IBDDIRET IBDDIFUNC DDI DTI WriteData IBDDIHND nodeHd T DDI DTI ACCESS dtiAcc Parameters IBDDIHND nodeHd Node handle DTI for the connection to which data is to be written The node handle also determines the bus terminal which is to be accessed DDI DTI ACCESS dtiAcc Pointer to a T DDI DTI ACCESS data structure This structure contains all the parameters needed for access Return value IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code UG gne erates amore 3 26 PHCENIX 654403 CONTACT D
92. O 2 After a power up all outputs are set to 0 Module AO DO 16 DO2 Value 0x0000 0x0000 0x0000 3 46 PHGNIX 654403 CONTACT Driver Software Table 3 7 If Ox0200 as first value after the power up is written onto the DO 16 module we get the following output values Module AO DO 16 DO2 Value 0x0000 0x0200 0x0000 Then this is the 0 plus the new values state If values such as 0x0010 for AO 0x0001 for DO 2 and OxACDC for DO 16 have been written onto the respective modules via several write accesses we get the following output values Module AO DO 16 DO2 Value 0x0010 OxACDC 0x0001 Then this is the O plus the sum of all new values state 3 8 4 2 The Connection Monitoring Table This table shows the output values after the connection monitoring or the process data watchdog detected an error such as a disconnection or a communication error while the voltage supply remains the same Connection monitoring table Connection Monitoring Table after Connection Abort a Cable Interrupt or a Communication Error Configuration of Configuration Reset Fault Configuration Last State Fault the FL IL 24 BK Mode Mode Internal memory Actual output Internal memory Actual output Cable or Last values in the All digital Last values in the Values in the communication inter
93. OTIFY_INFO structure and transmitted to the controller board The timeout time is endless if the value FFFF FFFFhex is entered 654403 PHCENIX 3 61 CONTACT FL IL 24 BK B PAC UM E Syntax to be activated Syntax to be deactivated UNIX Parameters Format of the structure Constants Windows NT 2000 Parameters Format of the IBDDIRET IBDDIFUNC DDI_SetMsgNotification IBDDIHND nodeHd T ETH NOTIFY INFO IBPTR notifyInfoPtr IBDDIRET IBDDIFUNC DDI CIrMsgNotification IBDDIHND nodeHd T ETH NOTIFY INFO IBPTR notifyInfoPtr mode Notification mode processld threadid timeout Abort time in milliseconds typedef struct USIGN32 mode Defines the notification mode USIGN32 threadId Thread identifier 0516032 processId Process identifier USIGN32 timeout Timeout time milliseconds T_ETH NOTIFY INFO define NOTIFY MODE 1 processld threadld timeout Abort time in milliseconds typedef struct structure DWORD threadId Thread Identifier DWORD processId Process Identifier USIGN32 timeout Timeout time milliseconds T IBS WIN32 NOTIFY 3 62 PHCENIX 654403 CONTACT Driver Software 3 11 Programming Support Macros 3 11 1 Introduction The macros described in this section make it easier to program the application program These macros also support data transfer commands messages and data between Intel format and Motorola
94. Segment Circuit Supply The segment voltage can be supplied at the power terminal or generated from the main power Install a jumper or create a segment circuit using a switch to tap the voltage Us from the main circuit Uy You can create a new voltage range through the power terminal Power terminals can be used to create substations with different voltage areas Depending on the power terminal you can apply 24 V DC 120 V AC or 230 V AC 654403 PHCENIX FL IL 24 BK B UME 1 17 2 Provision of the Segment Voltage Supply at Power Terminals You cannot provide voltage at the segment terminal A segment terminal can be used to create a new partial circuit segment circuit within the main circuit This segment circuit permits the separate supply of power outputs and digital sensors and actuators You can use a jumper to tap the segment voltage from the main circuit If you use a switch you can control the segment circuit externally You can create a protected segment circuit without additional wiring by means of a segment terminal with a fuse 1 17 3 Requirements Regarding the Voltage Supplies 1 18 Connecting Sensors and Actuators Sensors and actuators are connected using connectors Each module specific data sheet indicates the connector s to be used for that specific module Connect the unshielded cable as described in Section 1 16 1 on page 1 61 and the shielded cable as described in Sec
95. T2 The load is switched directly by the output 1 72 PHGNIX 654403 CONTACT FL IL 24 4 wire technology 55200037 Figure 1 40 4 termination for digital devices Sensor Figure 1 40 A shows the connection of a shielded 4 wire sensor The sensor signal is carried to terminal point IN1 The sensor is supplied with power via terminal points Us and GND The sensor is grounded via the FE terminal point Actuator Figure 1 40 B shows the connection of a shielded actuator The provision of the supply voltage Us means that even actuators that require a separate 24 V supply can be connected directly to the terminal FE SR 654403 PHGNIX 1 73 CONTACT FL IL 24 BK B UME 1 74 PHGNIX 654403 CONTACT Section 2 This section informs you about the startup the IP paramter assignment the management information base MIB Srarup eee ee tie wie stone atta ec Es tate e di 2 3 2 1 Firmware Startup 2 3 2 1 4 Sending BootP 2 3 2 2 Assigning an IP Address Using the Factory 2 3 22 1 BOOP 2 4 2 3 Manual Addition of Devices Using The Factory 2 4 2 4 Selecting IP
96. This function uses only the node handle as a parameter which indicates the data channel that is to be closed If the data channel cannot be closed or the node handle is invalid an appropriate error code is returned by the function IBDDIRET IBDDIFUNC DDI DevCloseNode IBDDIHND IBDDIHND nodeHd Node handle MXI or DTI for the connection that is to be closed IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code 3 22 P HCE 654403 Driver Software Example UNIX Windows NT 2000 IBDDIHND ddiHnd IBDDIRET ddiRet ddiRet DDI DevCloseNode ddiHnd if ddiRet ERR OK Error treatment return 654403 PHCENIX 3 23 CONTACT FL IL 24 Task Syntax Parameters Return value Format of the T DDI DTI ACCESS structure DDI DTI ReadData The DDI DTI ReadData function is used to read process data from the Inline bus terminal The function is assigned the node handle and a pointer to a T DDI DTI ACCESS data structure The 7T DDI DTI ACCESS structure contains all the parameters that are needed to access the process data area of the bus terminal and corresponds to the general DDI specification A plausibility check is not carried out on the user side which means that the parameters are transmitted via the network just as they were transferred to
97. Word 4 Bit R 0 8XXXhex Message code of the service confirmation 4 6 PHCENIX 654403 CONTACT Firmware Services Parameter_Count Result Add Error Info Number of subsequent words with a positive message XXXXhex Number of parameter words that are transferred with a positive message with a negative message XXXXhex Number of parameter words that are transferred with a negative message Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Additional information on the error cause 654403 PHCENIX der CONTACT FL IL 24 BK PAC UM E Task Syntax Word 1 Word 2 Word 3 Bit Key 4 3 Services for Parameterizing the Controller Board 4 3 1 Control Parameterization Service This service initiates or terminates the parameterization phase This is necessary in order to ensure a defined startup behavior for the Inline system During the parameterization phase for example the validity of read objects is not ensured Once the parameterization phase has been terminated the MPM Node Parameterization Ready bit is set in the coupling memory This means that during startup the host system computer PLC can recognize wh
98. actly like the Read Multiple Registers command The Read Input Registers command has the following format Table 5 17 Read Input Discretes Byte No Meaning BYTE 0 Function code 4 BYTE 1 2 Register table offset BYTE 3 4 Word Count 1 125 The response to the Read Input Registers command has the following format Table 5 18 Answer to Read Input Registers Byte No Meaning BYTE 0 Function code 4 BYTE 1 Byte Count of the response B 2x Word Count in the command BYTE 2 B 1 Register values 654403 PHCENIX 5 15 CONTACT FL IL 24 BK B PAC UM E If the command accesses an invalid offset or receives an invalid length an exception response with the following format is output Table 5 19 Exception response to Read Digital Input Registers Byte No Meaning BYTE 0 Function code 0x84 BYTE 1 Exception response 2 5 5 5 1 Example for the Read Input Registers command For examples refer to the Examples for Read Multiple Registers section 5 5 6 Write Coil With this command 1 bit is written into the Modbus coil table The Write Coil command has the following format Table 5 20 Write Coil Byte No Meaning BYTE 0 Function code 5 BYTE 1 2 Coil table offset BYTE 3 OxFF for setting the Coil to ON ON 0 for setting the coil to OFF OFF Byte 4 0 The response to the Write Coil command has the fol
99. all new values state 5 32 PHCENIX CONTACT 6544038 Modbus TCP Protocol Table 5 46 5 9 2 The Connection Monitoring Table This table shows the output values after the connection monitoring or the process data watchdog detected an error such as a disconnection or a communication error while the voltage supply remains the same Connection Monitoring Table Connection Monitoring Table After Connection Abort a Cable Interrupt or a Communication Error Configuration of the FL IL 24 BK Configuration Reset Fault Mode Configuration Last State Fault Mode Output table Actual output Output table Actual output Cable or communication error removal after cable interrupt Last values in the output table All coils are set to 0 Last values in the output table Values of the output table First write access Last values in Output Last values inthe Output table in the output table theoutputtable table output table plus after restoring the plus the newly the newly written connection written values values Operation Last values in Output Last values the Output table the outputtable table output table plus plus all newly all newly written written values values 654403 PHOENIX 5 33 CONTACT FL IL 24 BK B PAC UM E Example The last entries in the output table have the following values Module AO DO 16 DO2 V
100. alled or select another UNKNOWN_CODE 091 8nex Cause This service is not supported by this device Remedy Select another service ACTION_HANDLER_CONFLICT 0922hex Cause An internal firmware error has occurred Additional info 0031 error type and or error location registers cannot be read Additional info FFFFy Incorrect parameters detected during Read Configuration 654403 PHOENIX 4 57 CONTACT FL IL 24 BK PAC UM E INCORRECT_PARACOUNT 090Anex Cause The number of parameters is incorrect Remedy Correct the number of parameters ACTION_HANDLER_OVERLAP 091 Dpex Cause Cannot read from or write to the EEPROM Additional info 0001pex Write error Additional info 00024 Read error INCORRECT STATE 0 02 The called service is not permitted in the current status of the device Remedy Select another service or change the status of the device so that the desired service can be called INCORRECT_ATTRIB 0 18 Cause An invalid bit was activated in the Used_Attributes parameter Remedy Check that the selected attributes are permitted FRAME NOT SO BIG 0 19 Cause When accessing the configuration frame the end of the frame was exceeded Remedy Modify access to the configuration frame INCORRECT_TN_NUMBER 0 22 You specified inconsistent device numbers Remedy Enter the device numbers again 4 58 PHCENIX 654403 CONTACT Firmware Services DEVICE_ZERO 0A2Fhex Cause Initiate_
101. alue 0x0123 0x4321 0x0002 If 1 is written into the output table of the DO 16 as first value after having restored the connection we get the following actual output value Module AO DO 16 DO2 Value 0x0123 0x00A1 0x0002 This is the status Last values in the output table plus the newly written values If values such as 0x0010 for AO 0x0001 for DO 2 and OxACDC for DO 16 have been written into the output table via several write accesses we get the following output values Module AO DO 16 DO2 Value 0x0010 OxACDC 0x0001 This is the status Last values in the output table plus the newly written values 5 34 PHCENIX CONTACT 654403 Section 6 This section informs you about technical data ordering data TheehiniGal A EE 6 3 6 1 6 11 654403 PHGNIX 6 1 CONTACT FL IL 24 BK B PAC UM E 6 2 654403 Technical Data 6 Technical Data General Data Function Ethernet Inline bus coupler Housing dimensions width x height x depth 90 mm x 72 mm x 116 mm 3 543 x 2 835 x 4 567 in Permissible operating temperature EN 60204 1 0 C to 55 C 4 32 F to 131 F Permissible storage temperature EN 60204 1 25 C to 85 C 1
102. arameter 0 or 1 Syntax Set Value Confirmation 8750 Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit p 0 Key Code 875016 Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 654403 PHOENIX 4 11 CONTACT FL IL 24 BK PAC UM E 0001 1 parameter word with a negative message 000244 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 4 3 3 Read_Value Service Task This service can be used to read INTERBUS system parameters variables Syntax Read_Value_Request 0351 hex Word 1 Word 2 Word 3 Word 4 1 Parameter Bit Key Code 0351 Command code of the service request Parameter Count Number of subsequent words 0x002 Variable Count Number of system parameters to be read 0x0001 Variable ID ID of the system parameter to be read 0x2240 0 2275 4 12 PHGNIX 654403 CONTACT Firmware Services Syntax Read_Value_Confirmation 8351 hex Positive message Word 1 Word 2 Word 3 Word 4 Word 5 1 system Word 6 parameter Negative message Word 1
103. arameters ERR_ETH_RCV_TIMEOUT 1001 Cause The time limit for receiving a data telegram was exceeded 3 84 H N IX 654403 CONTACT Driver Software Remedy Cause Remedy Cause Remedy Cause Remedy Cause Remedy The Ethernet connection was interrupted or an incorrect IP address was entered Increase the timeout value ERR_IBSETH_OPEN 1010 IBSETHA cannot be opened The IBSETHA file does not exist or is in the wrong directory ERR_IBSETH_READ 1013 IBSETHA file cannot be read The file exists but cannot be read You may not have read access ERR_IBSETH_NAME 1014 The device name cannot be found in the file The name which was transferred to the DDI DEVOPEN NODE function is not in the IBSETHA file ERR_IBSETH_INTERNET 1016 The system cannot read the computer name host address The IP address entered in the IBSETHA file is incorrect or the symbolic name cannot be found in the host file 654403 PHCENIX o CONTACT FL IL 24 3 16 Example Program The following diagram illustrates the structure of the station to which the example program refers One module with 8 digital outputs IB IL DO 8 Order No 27 26 26 9 and one module with 8 digital inputs IB IL DI 8 Order No 27 26 22 7 are connected to the FL IL 24 BK B PAC The inputs are individually jumpered to the outputs The ground potential is created by the i
104. as the following format Table 5 24 Response to Write Single Register Byte No Meaning BYTE 0 Function code 6 BYTE 1 2 Register table offset as in the command 3 4 Register value as in the command If the command accesses an invalid offset the exception response has the following format Table 5 25 Exception response to Write Single Register Byte No Meaning BYTE 0 Function code 0x86 BYTE 1 Exception response 2 5 5 7 1 Example for Write Single Register With the register table offset 384 the register value is written in Q1 16 With the register table offset 576 the register value is written in AQ1 Register table offset 1024 and register value 0 clears the Fault table With the register table offset 1280 and a register value between 200 and 65 000 a new timeout value for the Modbus TCP connection is written With the register table offset 2 2 000 and a register value between 200 and 65 000 a new timeout value for the process data watchdog is written With the offset 2002 the fault response mode can be set 1 Reset fault mode 0 Standard fault mode 2 Hold last state mode Any Register Table offset 384 or 576 and 1024 or 1024 produces an exception response 5 18 PHCENIX 654403 CONTACT Modbus TCP Protocol 5 5 8 Read Exception Status This command reads a 8 bit status of the FL IL 24 BK B PAC The Read Exception
105. asily Contents Is the phraseology terminology easy to understand Are the index entries easy to understand helpful Are the examples practice oriented Is the document easy to handle Is any important information missing If yes what Other Comments Yes Ooadda da Yes Ooada da Order No 2689766 In Oo In Oo 5050 17
106. ask bits Class B Using this subnet mask the TCP IP protocol software differentiates between the devices that are connected to the local subnetwork and the devices that are located in other subnetworks Example Device 1 wants to establish a connection with device 2 using the above subnet mask Device 2 has IP address 59 EA 55 32 IP address display for device 2 Hexadecimal notation 59 EA 55 32 Binary notation 0101 1001 1110 1010 0101 0101 0011 0010 2 8 PHCENIX 654403 Startup Operation The individual subnet mask and the IP address for device 2 are then ANDed bit by bit by the software to determine whether device 2 is located in the local subnetwork ANDing the subnet mask and IP address for device 2 Subnet mask 1111 1111 1111 1111 1100 0000 0000 0000 AND IP address 0101 1001 1110 1010 0101 0101 0011 0010 Result after ANDing 0101 1001 1110 101000 0000 0000 0000 Subnetwork After ANDing the software determines that the relevant subnetwork 01 does not correspond to the local subnetwork 11 and the data telegram is forwarded to a subnetwork router 2 5 Web Based Management The FL IL 24 BK B PAC has a web server which generates the required pages for web based management and depending on the requirements of the user sends them to the Factory Manager or a standard web browser Web based management can be used to access static information e g technical data MAC address or dynamic infor
107. ata consistency with one of the following constants DTI_DATA_BYTE Byte data consistency 1 byte DTI DATA WORD Word data consistency 2 byte DTI DATA LWORD Double word data consistency 4 byte DTI DATA 64BIT 64 bit data consistency 8 byte ERR PLUG PLAY 00 9 An attempt was made to gain write access to process data Plug amp Play mode This is not permitted for security reasons Deactivate Plug amp Play mode using the Set Value command with the value 0 or switch to read access ERR STATE CONFLICT 0100 A service was called which is not permitted this operating mode 654403 PHCENIX 9 FL IL 24 Remedy Switch to an operating mode in which the desired call can be executed ERR_INVLD_CONN_TYPE 0101 nex Cause A service was called which cannot be executed via the selected connection Remedy Select a connection type via which the service can be executed ERR_ACTIVE_PD_CHK 0102 Cause Process IN data monitoring failed to activate ERR_DATA_SIZE 0103 Cause The data volume to be transmitted exceeds the maximum permissible size Remedy Transmit the data in several cycles ERR_OPT_INVLD_CMD 0200 Cause An attempt was made to execute an unknown invalid command Remedy Select a valid command ERR_OPT_INVLD_PARAM 0201 hex Cause An attempt was made to execute a command with unknown invalid parameters Remedy Enter permitted p
108. ation 24 V DC 0 20 mA 28 61 66 1 4 20 mA 20 mA 0 40 mA 40 mA IB IL TEMP 2 RTD 2 inputs 4 wire termination 16 bits resistance sensors 27 26 308 IB IL TEMP 2 RTD PAC 2 inputs 4 wire termination 16 bits resistance sensors 28 61328 IB IL TEMP 2 RTD 300 2 inputs 4 wire termination 16 bits resistance sensors 27 40 76 6 IB IL TEMP 2 RTD 300 2 inputs 4 wire termination 16 bits resistance sensors 28 61 55 1 PAC IB IL TEMP 2 UTH 2 inputs 2 wire termination 16 bits thermocouples 2727763 IB IL TEMP 2 2 inputs 2 wire termination 16 bits thermocouples 28 61 38 6 IB IL TEMPCON UTH 8 inputs 8 outputs control function 28 19312 IB IL TEMPCON UTH PAC 8 inputs 8 outputs control function 28 61 807 654403 PHGNIX 1 11 CONTACT FL IL 24 BK B UM E Designation Contd Features Order No IB IL AO 1 SF 1 output 2 wire termination 24 V DC 0 20 mA 27 26298 4 20 mA 0 10 V IB IL AO 1 SF PAC 1 output 2 wire termination 24 V DC 0 20 mA 28 61315 4 20 mA 0 10 V IB IL AO 1 U SF 1 output 2 wire termination 24 V DC 0 10 V 27 27 77 6 IB IL AO 1 U SF PAC 1 output 2 wire termination 24 V DC 0 10 V 28 61 399 IB IL AO 2 SF 2 outputs 2 wire termination 24 V DC 0 20 mA 28 62 806 4 20 mA 0 10 V IB IL AO 2 SF PAC 2 outputs 2 wire termination 24 V DC 0 20 mA 28 63 083 4 20 mA 0 10 V IB
109. be used on networked PCs for internal test purposes If a telegram is addressed to a PC with the value 127 in the first byte the receiver immediately sends the telegram back to the transmitter The correct installation and configuration of the TCP IP software for example can be checked in this way As the first and second layers of the ISO OSI reference model are not included in the test they should be tested separately using the ping function Value 255 in the Byte Value 255 is defined as a broadcast address The telegram is sent to all the PCs that are in the same part of the network Examples 004 255 255 255 198 2 7 255 or 255 255 255 255 all the PCs in all the networks If the network is divided into subnetworks the subnet masks must be observed during calculation otherwise some devices may be omitted 0 x x x Addresses Value 0 is the ID of the specific network If the IP address starts with a zero the receiver is in the same network Example 0 2 1 1 refers to device 2 1 1 in this network The zero previously signified the broadcast address If older devices are used unauthorized broadcast and complete overload of the entire network broadcast storm may occur when using the IP address 0 x x x 2 4 2 Subnet Masks Routers and gateways divide large networks into several subnetworks The IP addresses for individual devices are assigned to specific subnetworks by the subnet mask The network part of an IP address is not
110. bus coupler The maximum current carrying capacity of Uana is 0 5 capacity FL IL 24 BK B PAC PWR IN SEG F 0 11 Unna GNDL _ 2 0 J1U 5 Uy 65440001 Figure 1 17 Logic and analog circuit FLIL24 BK B Ethernet bus coupler PWR IN Power terminal SEG F Segment terminal with fuse as an example of a segment terminal 654403 PHOENIX 1 31 CONTACT FL IL 24 BK B UME Function Voltage Current carrying 1 11 4 Main Circuit Uy The main circuit with the main voltage Uy starts at the bus coupler or a power terminal and is led through all subsequent modules until it reaches the next power terminal A new circuit that is electrically isolated from the previous one begins at the next power terminal Several power terminals can be used within one station Several independent segments can be created within the main circuit The main circuit provides the main voltage for these segments For example a separate supply for the actuators can be provided in this way The maximum current carrying capacity is 8 A total current with the capacity segment circuit If the limit value of the common GND potential jumper for and Us is reached total current of Us and Uy a new power terminal must be used FL IL 24 BK B PAC PWR IN SEG F U Uana GNDL H H H Us H Un i L O i Un Un
111. capacity of the power supply unit for communications power and analog supply in Ta C Ambient temperature in C 6 6 PHCENIX 654403 CONTACT Technical Data Power Dissipation Formula to Calculate the Power Dissipation of the Electronics Pg Paus Peer B 2L Pe 2 6 W 1 1 X lin 0 7 X E bum Where PEL Total power dissipation in the terminal PBus Power dissipation for bus operation without I O load permanent Power dissipation with I O connected lin Current consumption of the device n from the communications power n Index of the number of connected devices n 1 to a a Number of connected devices with communications power supply gt Total current consumption of the devices from the 7 5 V communications power nzo 2 A maximum lim Current consumption of the device m from the analog supply m Index of the number of connected analog devices m 1 to b b Number of connected analog devices supplied with analog voltage Y Total current consumption of the devices from the 24 V analog supply m 0 0 5 A maximum 654403 PHCENIX 6 7 CONTACT FL IL 24 BK B UM E Power Dissipation Derating Using the maximum currents 2 A logic current and 0 5 A current for analog terminals in the formula to calculate the power dissipation when the is connected gives the following result 2 2 W 0 35 W 2 55 W 2 55 W corresponds t
112. cation relationship list CRL Syntax Word 1 Word 2 Word 3 Bit Key Code Parameter Count Default Parameter 0308 Command code of the service request Number of subsequent words 000155 1 parameter word Indicates whether a default parameterization of the PD channel is to be carried out for the loaded configuration 0000 No automatic parameterization 0001 Automatic parameterization of the process data channel through the creation of the process data reference list 0003 Automatic parameterization of the processd data channel 4 20 PHCENIX 654403 Firmware Services Syntax Terminate_Load_Configuration_Confirmation 8308 Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit 0 Code 83084 Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0001hex 1 parameter word with a negative message 0002 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 654403 PHGNIX 4 21 CONTACT FL IL 24
113. ce could not be executed Additional information on the error cause 0000 Indicates that all requested entries contained in the service confirmation 0001 Indicates that the service confirmation does not contain all requested entries as the amount of data is larger than the mailbox that is available for the services Call the Read Configuration service 0309hex to read the remaining data Number of the active configuration frame Read attributes The parameter contains the value that was transferred with the service request Number of the first entry 0001hex With this service all entries are read out starting with the first entry Number of entries that are transferred by the service confirmation Entries in the order of the physical bus configuration The attributes contained in every entry are enabled in the service request by the Used Attributes parameter For the description of the Configuration Entry parameters see Read Configuration service 03094 on page 4 22 XXXXhex 654403 PHCENIX vet CONTACT FL IL 24 BK PAC UM E 4 3 9 Delete Configuration Service Task This service deletes an inactive configuration frame from the configuration directory Syntax Delete Configuration Request 030Chex Word 1 Word 2 Word 3 Bit EET 0 Key Code 030Chex Command code of the service request Parameter Count Number of subsequent words 000155 1 parameter word Fram
114. ce name ERR_NO_MORE_HNDL 0092hex Cause Device driver resources used up No further data channels can be opened If you exit a program without closing the data channels in use they will stay open Additional data channels will be opened the next time the program is started After this program has been started a number of times the maximum permitted number of data channels that can be opened simultaneously will be reached and no more will be available Remedy Close a data channel that is not required or reinstall the device driver Always close all data channels used when exiting a program 3 80 P H N IX 654403 CONTACT Driver Software Cause 1 Remedy Cause 2 Remedy Cause Cause 1 Remedy Cause 2 Remedy Cause 3 Remedy 3 15 3 Error Messages When Transmitting Messages Commands ERR MSG TO LONG 009 If an error message occurs when sending a command then the length of the command exceeds the maximum number of permitted parameters Reduce the number of parameters If an error message occurs when receiving a message then the length of the message exceeds the length of the receive buffer specified Increase the length of the receive buffer ERR NO MSG 009 This message occurs if an attempt has been made to retrieve message using the DDI MXI HcvMessage function but no messages are present for the node specified by the node handle ERR NO MORE MAILBOX 009Chex You have requ
115. cess data 8 bit IB PD GetBytePtrHiByte n This macro returns the address of a word starting with the high order byte bit 8 to 15 n USIGN8 Pointer to the input buffer m USIGN16 Word number USIGNS Address of the high order byte of a word in the input buffer IB PD GetBytePtrLoByte n m This macro returns the address of a word starting with the low order byte bit O to 7 n USIGNS Pointer to the input buffer m USIGN16 Word number USIGNB Address of the low order byte of a word in the input buffer 3 12 4 Macros for Converting Output Data The IBS_MACR H file contains macros for converting double words words and bytes from Intel to Motorola format Addressing is always word oriented here IB PD SetLongDataN n m o Task This macro converts a double word 32 bit to Motorola format and writes itto the specified position in the output buffer The word index in the output buffer is used as a position The macro writes the double word starting from the specified word address over two words Parameters n USIGNB8 Pointer to the output buffer m USIGN16 Word number USIGN32 Process data 32 bit 654403 PHCENIX 3 73 CONTACT FL IL 24 BK B PAC UM E Task Parameters Task Parameters Task Parameters Task Parameters Return value Task IB PD SetDataN n m o This macro converts a word 16 bit to Motorola format and writes it to the specifi
116. command has the following format Table 5 14 Read Input Discretes Byte No Meaning BYTE 0 Function code 2 BYTE 1 2 Input Discretes table offset BYTE 3 4 Bit Count 1 2000 The response to the Read Input Discretes command has the following format Table 5 15 Answer to Read Input Discretes Byte No Meaning BYTE 0 Function code 2 BYTE 1 Byte Count of the response B Bit Count of the command 7 8 BYTE 2 B 1 Bit values the least significant bit is the first coil If the command accesses an invalid offset or receives an invalid length an exception response with the following format is output 5 14 PHCENIX 654403 CONTACT Modbus TCP Protocol Table 5 16 Exception response to Read Input Discretes Byte No Meaning BYTE 0 Function code 0x82 BYTE 1 Exception code 5 5 4 1 Examples for Read Digital Coils Input Discrete table offset 0 and Bit Count 1 returns input discrete 11 Input Discrete Table offset 0 and Bit Count 2000 returns input discrete values 11 2000 Input Discrete Table offset 4 and Bit Count 13 returns input discrete values Q5 17 Every combination of the Input Discretes table offset with Bit Count that accesses offset gt 3072 results in an exception response 5 5 5 Read Input Registers This command reads 16 bit words from 1 to 125 in the Modbus register table This command is used ex
117. ction reads message from the bus terminal The function receives a node handle and a pointer to a T DDI MXI ACCESS data structure as parameters The T DDI MXI ACCESS structure contains all the parameters that are needed to read the message These parameters are transmitted to the bus terminals via the network without a plausibility check which means that invalid parameters are first detected at the bus terminal and acknowledged with an error message The nodeHd parameter specifies the bus terminal in the network to which the request is to be sent The node handle must be assigned to a mailbox interface data channel otherwise an appropriate error message is generated by the bus terminal The function does not wait until a message is received in the coupling memory instead it returns immediately If no message is present the error code ERR_NO_MSG is returned IBDDIRET IBDDIFUNC DDI MXI RcvMessage IBDDIHND nodeHd T DDI ACCESS IBDDIHND nodeHd Node handle MXI for the connection via which a message is to be read from the mailbox interface The node handle also determines the bus terminal which is to be accessed T DDI MXI ACCESS dtiAcc Pointer to a T DDI MXI ACCESS data structure This structure contains all the parameters needed for access IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code struct
118. d All Inline modules are mounted on 35 mm 1 378 in standard DIN rails Mount end clamps on both sides of the Inline station The end clamps ensure that the Inline station is correctly assembled End clamps fix the Inline station on both sides and keep it from moving side to side on the DIN rail Phoenix Contact recommends using the CLIPFIX 35 Order No 30 22 21 8 or E UK end clamp Order No 12 01 44 2 a 1 48 H 654403 FL IL 24 End plate An Ethernet Inline station must be terminated with an end plate It has no electrical function It protects the station against ESD pulses and the user against dangerous contact voltage The end plate is supplied with the bus interface module and needs not be ordered separately 1 143 Mounting When mounting a module proceed as follows Figure 1 29 e First attach the electronics base which is required for mounting the station perpendicular to the DIN rail A I M keyway featherkey connection links adjacent modules ensures safe potential routing e Next attach the connectors to the corresponding base First place the front connector shaft latching in the front snap on mechanism C Then press the top of the connector towards the base until it snaps into the back snap on mechanism D 654403 PHCEN IX 1 49 CONTACT FL IL 24 BK B UM E 6138A015 Figure 1 29 Snapping
119. d into a register for example 1 up to 26116 the bit with the highest number 96116 in this example is the least significant bit The bit with the lowest number l1 in this example is the most significant bit 5 2 Modbus Function Codes The following function codes are supported Table 5 2 Supported Function Codes Code No Function Code fc1 Read Coils fc2 Read Input Discretes fc3 Read Multiple Registers fc4 Read Input Registers fc5 Write Coil fc6 Write Single Register fc7 Read Exception Status fc15 Write Multiple Coils fc16 Write Multiple Registers fc23 Read Write Registers 5 3 Modbus Table The definition of the reference tables for the Modbus protocol differs from the internal structure of the FL IL 24 BK B PAC tables Modbus refers to a table of registers input registers discrete inputs as well as coils while the FL IL 24 BK B PAC refers to a table of digital inputs l coils Q analog inputs Al analog outputs and special registers The following table shows that every Modbus table is illustrated in the FL IL 24 BK B PAC tables Please observe that all data in this table refer to the 5 6 PHGNIX 654403 CONTACT Modbus TCP Protocol physical memory in the FL IL 24 BK The FL IL 24 BK memory contains Modbus names For example if you output the Read Input Discretes to read the inputs in the table of the Modbus input discretes the internal FL IL 24 BK tabl
120. dbus Function Codes 0 ccccccccceeeeeeeeeeeeseneeeeeeeeseneeeseneeee 5 6 53 Modbus Table Senni nine ee er e 5 6 5 3 1 Example Position of the Input Output Data 5 8 5 4 Executable 5 9 5 5 Supported Function Codes 5 10 5 5 1 Read Multiple 5 10 5 5 2 Write Multiple 5 12 5 5 9 Read Coils eet tede da inns 5 13 5 5 4 Read Input Discretes 5 14 5 5 5 Read Input 5 15 5 5 6 Wtite COll 5 16 5 5 7 Write Single 4 4 5 17 5 5 8 Read Exception Status 5 19 5 5 9 Data Format of the Exception Status 5 19 5 5 10 Exception 5 20 5 5 11 Write Multiple 8 5 21 5 5 12 Read Write 2 22 442 22 5 22 5 6 Reserved Registers for Command and Status 5 24 5 6 1 Command Word sse 5 24 5 6 2 Status 5 25 654403 PHOENIX 5 1 CONTACT FL IL 24
121. dbus Register table mapped to the and AQ I O tables can be written using this function The Write Multiple Registers command has the following format Table 5 8 Write Multiple Register Byte No Meaning BYTE 0 Function code 0x10 BYTE 1 2 Register table offset BYTE 3 4 Word Count 1 100 BYTE 5 Byte Count of the response Byte Count 22x Word Count BYTE 6 B 5 Register values The response to the Read Multiple Registers command has the following format Table 5 9 Answer to Write Multiple Registers Byte No Meaning BYTE 0 Function code Ox10 BYTE 1 2 Register table offset as in the command 3 4 Word Count as the command If the command accesses an invalid offset or receives an invalid length an exception response with the following format is output Table 5 10 Exception response to Write Multiple Registers Byte No Meaning BYTE 0 Function code 0x90 BYTE 1 Exception response 2 5 5 2 1 Example for Write Multiple Registers Register table offset 384 and Word Count 2 writes the register values into Q1 32 Register table offset 575 and Word Count 2 writes the register values into Q3057 3072 and AQ1 5 12 PHCENIX 654403 CONTACT Modbus TCP Protocol Every combination of the register table offset and Word Count that either accesses Offset lt 384 or gt 767 results in an exception respo
122. dbus TCP Driver software for Sun Solaris Windows NT 2000 Software interface kit for other Unix systems Applications Connection of sensors actuators via Ethernet Exchange of Inline process data via Ethernet using a Unix workstation or a Windows NT 2000 computer Software by Phoenix Contact Required for Process Data Operation Table 1 1 Software for Process Data Operation Operation Software DDI Read and Write DDI driver Modbus TCP Read and Write OPC Read and Write OPC Server gt 2 01 FL IO Browser FL IO Configurator XML Read only 654403 PHCENIX CONTACT 1 3 FL IL 24 BK B UM E Front View of the FL IL 24 BK B PAC PHCENIX CONTACT FL IL 24 BK B PAC Ord No 2862327 00 A0 45 50 A1 77 100 XMT RCV LINK 10 100 61590002 Figure 1 1 Front view of the FL IL 24 BK B PAC 1 4 PHCEN IX 654403 CONTACT FL IL 24 1 2 Structure of the FL IL 24 Bus Coupler LINATHLIF gt 2 XINDH LI LEEZIGZ ON PIO JV PE 7 TA 232 16 AT l e Figure 1 2 Structure of the FL IL 24 BK B PAC Bus Coupler The bus coupler has the following components End plate to protect the last Inline module Inline diagnostic indicators 24 V DC suppl
123. e e PP Q FAIL 100 XMT RCV LINK 10 100 61590004 Figure 1 16 Typical connection of the supply voltage 1 11 2 Logic Circuit U The logic circuit with communications power U starts at the bus coupler is led through all modules of a station and cannot be supplied via another supply terminal Function The logic circuit provides the communications power for all modules in the station Voltage The voltage in this circuit is 7 5 V DC 1 30 PHCENIX 654403 CONTACT FL IL 24 Provision of UL Current carrying capacity Function Voltage Provision of Uana Current carrying The communications power U is generated from the supply voltage of the bus coupler The communications power is not electrically isolated from the 24 V input voltage for the bus coupler The maximum current carrying capacity of U is 2 A 1 11 3 Analog Circuit Uana The analog circuit with the supply for the analog modules here also called analog voltage Uana is supplied at the bus coupler and is led through all the modules in an Inline station Power cannot be supplied by the supply terminals U aya is not electrically isolated from Ugk The module devices for analog signals are supplied from the analog circuit The voltage in this circuit is 24 V The analog voltage Uana is generated from the main voltage Up of the
124. e confirmation Parameter_Count Number of subsequent words with a positive message 0001he Always 1 parameter word with a negative message 0002 Always 2 parameter words 4 18 PHGNIX 654403 CONTACT Firmware Services Result Add_Error_Info Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Additional information on the error cause 654403 PHCENIX asi CONTACT FL IL 24 BK PAC UM E Task Remark 4 3 6 Terminate Load Configuration Service This service terminates the loading of the configuration data in segments The service also checks the loaded configuration data for permissibility and consistency If no error is detected the controller board stores the data in the configuration directory under the Frame Reference given in the Initiate Load Configuration 0306 service If an error is detected the service is acknowledged with a negative confirmation The Default Parameter parameter can also be used to indicate whether the process data channel PD channel is to be parameterized according to the loaded configuration frame In this case the firmware automatically creates the process data reference list physical addressing and or a communi
125. e l that is shown in the table of the Modbus input discretes will actually be read Table 5 3 Modbus Reference Tables Modbus Register Modbus Modbus Internal FL IL 24 BK B Register Tables of Input Output PAC Tables Tables Modbus Discretes Tables Inputs Table 0 191 0 191 0 3071 l1 3072 16 bit words 16 bit words Bit Bit d 192 383 192 383 Al1 192 16 bit words 16 bit words 16 bit words 384 575 384 575 0 3071 Q1 3072 16 bit words 16 bit words Bit Bit Ml 576 767 576 767 S m 1 192 16 bit words 16 bit words 1024 1087 1024 1087 Error table 16 bit words 16 bit words 32 errors x two 16 bit words per error MEM 1280 1280 Timeout table timeout 8 16 bit words 16 bit words value for connection co monitoring a 2000 2000 Process data watchdog 16 bit words 16 bit words timeout 8 2002 2002 Fault response mode 16 bit words 16 bit words 2004 2004 NetFail rReason 16 bit words 16 bit words 654403 PHGNIX 5 7 CONTACT FL IL 24 UM E 5 3 1 Example Position of the Input Output Data DI2 AI2 AM AO1 FL IL 24 BK B PAC DO8 DO2 DI8 Digital Input Table Modbus Address Word 0 Modbus Address Digital Output Table Word
126. e 3 3 Monitoring functions Monitoring Mechanism Monitoring the Client the the the Process Application Individual Ethernet Data Exchange Channels Connection Process data watchdog X X X process data monitoring Host checking DTI Modbus monitoring X X X incre In the event of an error the system reacts with a fault response The user determines the required fault response mode Setting the Required Fault Response Mode The required fault response mode can be set to the object ID 0x2277 using the web based management or by writing to the Modbus register 2002 or using the Set Value 0x0750 service The following fault response modes are available Table 3 4 Available fault response modes Fault Response Mode Value Function Reset fault mode default 1 The digital outputs are set to 0 and the analog outputs are set to the value configured by the user Default 0 Standard fault mode 0 All outputs are set to 0 Hold last state mode 2 All outputs retain their last value 654403 PHCENIX FL IL 24 BK B PAC UM E Causes Causes for Fault Response The web based management the Modbus register 2004 or the ETH_GetNetFailState service allow to request the causes for fault response The following may have been the cause DDI NF TASK CREAT ERR Error when starting a task
127. e EEPROM Power Up Sequence Power Up Sequence Front View of Configuration Reset Fault Mode Configuration Last State Fault the FL IL 24 BK Mode Output table Actual output Output table Actual output Power up 0 0 0 0 First read access 0 plus the new Output table 0 plus the new Output table in output table values values after power up Operation 0 plus the sum Output table 0 plus the sum Output table of all new values of all new values Example A station consists of 3 I O modules an analog output module with a length of 16 bit AO a coil module with a length of 16 bit DO 16 and a coil module with a length of 2bit DO 2 After a power up all outputs are set to 0 Module AO DO 16 DO2 Value 0x0000 0x0000 0x0000 If Ox0200 as first value after the power up is written into the output table of the DO16 module we get the following output values Module AO DO 16 DO2 Value 0x0000 0x0200 0x0000 Then this is the 0 plus the new values state If values such as 0x0010 for AO 0x0001 for DO 2 and OxACDC for DO 16 have been written into the output table via several write accesses we get the following output values 654403 PHCENIX 5 31 CONTACT FL IL 24 BK B PAC UM E Module AO DO 16 DO2 Value 0x0010 OxACDC 0x0001 Then this is the O plus the sum of
128. e Reference 0001 hex Syntax Delete_Configuration_Confirmation 830Chex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit 0 Code 830Chex Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 000155 1 parameter word with a negative message 4 32 PHCENIX 654403 CONTACT Firmware Services 000244 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add Error Info Additional information on the error cause 4 3 10 Create Configuration Service Task This service causes the controller board to automatically generate a configuration frame from the currently connected configuration and to activate it in order to start the bus After the execution of the service the controller board is in the Active state The new configuration frame and the active configuration are stored in the configuration directory under the number specified in the Frame Reference parameter If there is already a configuration frame under this number this frame is overwritten In addition the controller board generates default process
129. e acknowledgment for the reference configuration and the release of the process data exchange P amp P mode When the P amp P mode is deactivated the reference configuration is deactivated compared to the physical configuration If these two configurations are identical the bus coupler can be set to the RUN state If the reference configuration and the physical configuration are not identical the FAIL LED flashes and the process data exchange is not possible for safety reasons In order to operate the bus you have the following two options 1 Restore the original configuration so that the reference configuration and the physical configuration are identical once more or 2 activate the P amp P mode so that the current physical configuration can be accepted as reference configuration 654403 PHCENIX 3 9 CONTACT FL IL 24 3 5 2 Expert Mode IS Expert mode If the expert mode is deactivated default upon delivery so an error free deactivated configuration is automatically set to the RUN state If the configuration has a technical defect or if it is not identical with the reference configuration the FAIL LED flashes and the process data exchange is not possible Expert mode If the expert mode is activated the faulty configuration is set to the activated READY state but not automatically to the RUN state The user must set the station to the RUN state using the appropriate firmware commands
130. e respective Modbus TCP connection is closed 654403 PHCENIX 5 29 CONTACT FL IL 24 BK B PAC UM E 5 9 I O Fault Response Mode In case the communication connection is disrupted the user can select the reaction of the FL IL 24 BK B PAC beforehand Use the DDI command Set Value on the object ID 2277 The following table shows the three possible reactions Table 5 44 Available Fault Response modes Default Fault Response Value Function Mode Reset fault mode 1 The coils are set to 0 and the analog outputs are set to the value configured by the user default 0 Standard fault mode 0 All outputs are set to O Hold last state mode All outputs retain their last value The following tables show the output tables as well as the actual output values for the first two options One table regards the restart after power up and the other table regards the restart after an error occured The output table is part of the internal memory of the bus terminal current output values are the values of the output modules The output table consists of two parts digital and analog outputs 5 30 PHCENIX 654403 CONTACT Modbus TCP Protocol Table 5 45 5 9 1 The Power Up Table The output table of the FL IL 24 BK B PAC is stored in a non volatile memory For this reason all values of the output table are set to 0 after a power up Configuration settings are stored in a non volatil
131. ection The bus terminal is protected by two passwords case sensitive The password for read access is public while the password for read and write access is private All status changes to the bus terminal are only possible after the password for read and write access has been entered The password can be changed at any time Your unique password must be between four and twelve characters long 654403 FL IL 24 BK B PAC UM E IL STATION IL BUS TERMINAL TERMINAL TYPE NAME IP ADDRESS MODULE NUMBER 2 5 5 Process Data Access via XML The integrated web server of the FL IL 24 BK B PAC offers the possibility to access the process data of the connected Inline terminals via a website in XML format You can access the websites via a standard web browser For calling the XML pages with the process data in the address line of the browser enter the address the following format http lt IP Adresse gt processdata xml 2 5 5 1 XML File Structure The XML file contains different data areas Frames for the entire XML file The obligatory elements of this frame are IL BUS TERMINAL and IL BUS This data area contains information on the entire Inline station bus coupler and all connected terminals Belonging to this data area TERMINAL TYPE the module name NAME the IP address ADDRESS the number of connected terminals MODULE NUMBER and the INTERBUS diagnostic r
132. ed position in the output buffer n USIGNS Pointer to the output buffer m USIGN16 Word number o USIGN16 Process data 16 bit IB_PD_SetDataNHiByte n This macro converts the high order byte bit 8 to 15 of a word to Motorola format and writes it to the specified position in the output buffer n USIGNS Pointer to the output buffer m USIGN16 Word number o USIGN8 Process data 8 bit IB PD SetDataNLoByte n m o This macro converts the low order byte bit O to 7 of a word to Motorola format and writes it to the specified position in the output buffer n USIGNS Pointer to the output buffer m USIGN16 Word number o USIGN8 Process data 8 bit IB PD SetBytePtrHiByte n This macro returns the address of a word starting with the high order byte bit 8 to 15 n USIGNS Pointer to the output buffer m USIGN16 Word number USIGNS Address of the high order byte of a word in the output buffer IB PD SetBytePtrLoByte n This macro returns the address of a word starting with the low order byte bit O to 7 3 74 P H N IX 654403 CONTACT Driver Software Parameters n USIGN8 Pointer to the output buffer m USIGN16 Word number Return value USIGNS Address of the low order byte of a word in the output buffer 654403 PHCEN IX 3 75 CONTACT FL IL 24 3 13 Diagnostic Options of the Driver Software 3 13 1 Introduction T
133. egister DIAGNOSTIC STATUS REGISTER and the INTERBUS status register DIAGNOSTIC PARAMETER REGISTER This area contains the module it is always FL IL 24 BK B PAC Contains the user specific station names The station name can be modified via WBM Contains the IP address of the station Contains the number of connected Inline terminals In the case of a bus error the number of the last known operable configuration is indicated 2 12 PHCENIX 654403 CONTACT Startup Operation DIAGNOSTIC_STATUS _REGISTER IL BUS IL MODULE MODULE TYPE PD CHANNELS PD WORDS PD IN Contains the INTERBUS status represented via all bits of the diagnostic status register A detailed description can be found in the diagnostic parameter register Whenever an error bit was set the diagnostic parameter register was rewritten Frame for the connected Inline terminals Frame for the data of an individual Inline terminal The terminals are numbered from one up to 63 Contains the terminal type Possible types are DI DO DIO Al AO and AIO Number of process data channels in an Inline terminal For digital terminals the number of channels is equal to the number of supported bits For other modules the number of process data words is indicated Example An AO 2 has two process data channels and a DO 8 has 8 bits and 8 process data channels Number of process data words in an Inline terminal Observe that analog terminals alwa
134. egister table offset 1024 and Word Count 64 returns an error table Every access onto a combination of register table offset and Word Count between gt 767 and lt 1024 generates an exception response The attempt to read the error table with a register table offset gt 1024 anda Word Count not equal to 64 also generates an exception response The special register 1280 2004 can only be read when the Word Count equals one Register table offset 384 and Word Count 2 writes the register values on the coils Q1 32 Register table offset 575 and Word Count 2 writes register values on the coils Q3057 3072 and the analog output AQ1 Every access onto a combination of Register table offset and Word Count between gt 384 and lt 767 generates an exception response The exception is writing one word into registers 2000 and 2002 654403 PHCENIX 9 53 FL IL 24 BK B PAC UM E 5 6 Reserved Registers for Command and Status Words 5 6 1 Command Word The last word of the table for analog outputs is automatically reserved as network interface command word via the bus terminal and starts using the Modbus address 40767 With this command word and via the Ethernet host controller e g a PLC the user can send commands with basic functions to the module These commands enable startup without configuration software Table 5 36 Structure of the Analog Output Table Analog output table Address First
135. egistered design Third party products are always named without reference to patent rights The existence of such rights shall not be excluded Warning The FL IL 24 BK B PAC module is designed exclusively for SELV operation according to IEC 950 EN 60950 VDE 0805 Shielding The shielding ground of the connected twisted pair cables is electrically connected with the socket When connecting network segments avoid ground loops potential transfers and voltage equalization currents using the braided shield a P ESD The modules are fitted with electrostatically sensitive components Exposure to electric fields or charge imbalance may damage or adversely affect the life of the modules The following safety equipment must be used when using electrostatically sensitive modules Create an electrical equipotential bonding between yourself and your surroundings e g using an ESD wristband which is connected to the grounded DIN rail to which the module will be connected Housing Only authorized Phoenix Contact personnel are permitted to open the housing 654403 PHCENIX CONTACT FL IL 24 Purpose of this manual Who should use this manual Related documentation Latest documentation on the Internet About This Manual This manual illustrates how to configure an Ethernet Inline station to meet application requirements Use this manual if you are responsible for co
136. elding an Inline Station 1 57 1 15 2 Shielding Analog Sensors and Actuators 1 57 1 16 Connecting Cables 1 61 1 16 1 Connecting Unshielded Cables 1 61 1 16 2 Connecting Shielded Cables Using the Shield Connector 1 63 1 17 Connecting the Power 1 66 1 17 1 Power Terminal 2 0 1 67 1 17 2 Provision of the Segment Voltage Supply at Power Terminals 2 eek eerte crecer 1 68 1 17 3 Requirements Regarding the Voltage Supplies 1 68 1 18 Connecting Sensors and 1 68 1 18 1 Connection Methods for Sensors and Actuators 1 68 1 18 2 Examples of Connections for Digital I O Modules 1 70 2 Startup OpeFrati ON ERR 2 3 2 1 Firmware Startup 2 3 2 1 1 Sending BootP Requests 2 3 2 2 Assigning an IP Address Using the Factory Manager 2 3 2 21 4BOOIB x eee opo AT 2 4 2 3 Manual Addition of Devices Using The Factory Manager 2 4 2 4 Selecting IP Addresses 0 2 5 2 4 1 Possible Address Combinations 2 6 2 4 2 Subnet Masks 2 7 2 4 8 Structure of the Subnet Mask
137. em 255 has been output the program is terminated after a 3 second waiting time The following figure is a screenshot of the program 2 DEMO 01 exe Benoetigter Busaufbau IB IL 24 DI 8 i IB IL 24 DO 8 Controllernummer Format xx gt gt Mailboxverbindung OK Haendel 64 Datenkanalverbindung OK Haendel 65 Plug amp Play Modus IBS Status RUNNING Daten schreiben lesen und vergleichen Geschrieben 17 Gelesen 17 Vergleich OK Figure 3 15 Screenshot of the example program 654403 3 87 FL IL 24 3 16 2 Program Source Code INCLUDE FILES AND CONSTANT DEFINITION include lt stdio h gt include lt stdlib h gt include lt time h gt include lt string h gt S EEK K K k k k k RK RR RR RR RRR RR ck ck RR RR RR RR RK KK KK KK KK RR KR KEK Include files for the CLIENT library Windows version K K KK KK KK KK A RR RRR RRR RRR ee include ethwin32 h define MAX MSG LENGTH 100 define MXI_RCV_TIMEOUT 9 kK RK RR RR RK KR KK KR 7 GLOBAL VARIABLES kK KK RR RR RR RR KK RK 7 char OPEN MXI 20 char OPEN DTI 20 IBETH IBDDIHND mxiHnd dtiHnd DDI MXI ACCESS mxiAcc T DDI DTI ACCESS dtiAcc T DDI DTI ACCESS readAcc kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk CreateConnection FUNCTION
138. en set An additional function for the controlled setting of the NetFail signal is provided for test purposes This enables the behavior of the system in the event of a NetFail to be tested especially during program development The ETH SetNetFail function only needs a valid node handle as a parameter so that the corresponding module can be addressed in the network The NetFail signal can only be reset by calling the ETH ClrSysFailStatus function or by executing a reset on the bus terminal 654403 PHCENIX FL IL 24 BK B PAC UM E ETH SetDTlTimeoutCtrl Task The ETH SetDTlITimeoutCtrlfunction activates the node for monitoring the DTI data channel specified by the node handle After this function has been called monitoring checks whether process data is received regularly The function is assigned a valid node handle for a DTI data channel and a pointer time to a variable with the desired timeout time After the function has been called the timeout time calculated by the bus terminal can be found in the USIGN16 time variable Syntax IBDDIRET IBDDIFUNC SetDTITimeoutCtrl IBDDIHND nodeHd USIGN16 time Parameters IBDDIHND nodeHd Node Handle DTI der Busklemme die berwacht werden soll USIGN16 time Pointer to a variable which contains the desired timeout time when called If the function has been called successfully the actual timeout time is then entered in this variable The timeout time
139. en the parameterization sequence that is stored on the memory card has been successfully processed Control_Parameterization_Request 030Enex Code 030Ehex Command code of the service request Parameter_Count Number of subsequent words 000155 1 parameter word Control_Code Function of the service 0001hex Initiate the parameterization phase 0000 Terminate the parameterization phase 4 8 PHCENIX 654403 CONTACT Firmware Services Syntax Control_Parameterization_Confirmation 830Enex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit 0 Code 830 code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001hex 1 parameter word with a negative message 0002 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 654403 PHCENIX 4 9 CONTACT FL IL 24 BK PAC UM E Task Table 4 3 System parameters 4 3 2 Set_Value Service This service assigns new values to INTERBUS system parameters variables A new value is only accepted if no error was d
140. enix Contact ERR AVR TIMEOUT 009Fhex An acknowledge message bit was set when reading a message to indicate to the communication partner that a message has been processed and the mailbox is free again This bit must be reset by the communication partner to indicate that it has recognized that the mailbox is free again If this reset does not take place within a set time an error message is generated Invalid node called e g An attempt was made to address a coprocessor board COP which is faulty or not present Please get in touch with Phoenix Contact 3 82 P H N IX 654403 CONTACT Driver Software Meaning Cause 1 Remedy Cause 2 Remedy Cause Remedy Cause Remedy Cause 3 15 4 Error Messages When Transmitting Process Data These errors only occur when accessing the data interface DTI ERR AREA EXCDED 00964 Access exceeds the upper limit of the selected data area The data record to be read or written is too large The function can read a maximum of 4 Kbyte in one call Only read or write data records with a maximum size of 4 Kbyte The upper area limit 4 Kbyte over the start of the device area has been exceeded Make sure that the total of address offset relative address and data length to be read does not exceed the upper area limit ERR INVLD DATA CONS 0097 An invalid value was entered for data consistency 1 2 4 or 8 bytes Specify a permissible d
141. ent fast module in front of the flashing module has failed or the module itself is faulty Modules following the flashing module are not part of the configuration frame OFF Communications power not present local bus not active Status The status of the input or output can be read on the relevant yellow LED 1 46 PHOENIX 654403 CONTACT FL IL 24 Table 1 18 Status LEDs for the I O terminals LED Color State Description of the LED States 1 2 3 4 Yellow ON Relevant input output set 2 c OFF Relevant input output not set Assignment Between Status LED and I O rini 1 13 4 Indicators on Other Inline Modules 5 ieee 654403 H 1 47 FL IL 24 BK B UM E DIN rail End clamp CLIPFIX 1 14 Mounting Removing Modules and Connecting Cables 1 14 1 Installation Instructions 1 14 2 Mounting and Removing Inline Modules An Inline station can be set up by mounting the individual components side by side No tools are required Mounting side by side automatically creates voltage and bus signal connections potential and data routing between the individual station components The modules are mounted perpendicular to the DIN rail This ensures that they can be easily mounted and removed even within limited space After a station has been set up individual modules can be exchanged by pulling them out or plugging them in Tools are not require
142. ent of 8 A 1 40 PHCENIX 654403 CONTACT FL IL 24 I O supplies electrically isolated from one another FL IL 24 BK B PAC IB IL 24 PWR IN T FLAL 24 BK B PAC Ord No 28623 PP Q FAIL 100 XMT RCV LINK 10 100 r3 1n 65440004 Figure 1 25 Structure of I O supplies that are electrically isolated from one another Potentials within the station 1 Bus logic of the station 2 I O outputs 3 1 0 inputs 654403 PHCENIX 1 41 CONTACT FL IL 24 BK B UM E 1 13 Diagnostic and Status Indicators All modules are provided with LED diagnostic and status indicators for local error diagnostics Diagnostics The diagnostic indicators red green indicate the type and location of the error Once an error has been removed the indicators immediately display the current status Status The status indicators yellow display the status of the relevant inputs outputs or the connected device 1 13 1 LEDs on the Ethernet Bus Coupler mw 22 demus 2227274 p 65440005 Figure 1 26 LEDs on the Ethernet bus coupler 1 42 PHCENIX 654403 CONTACT FL IL 24 BK B PAC Diagnostics The following states can be read on the bus coupler Table 1 13 Diagnostic LEDs on the bus
143. er provide the application program or the visualization with direct access to the process data for the bus configuration Robot Control clr Factory Line OPC Configurator Eigenschaften von Sensor T 2 x Datei Bearbeiten Einf gen Ansicht Hilfe E ae Allgemeines ck X Neu Aufwarts Ausschneiden Kopieren Em Sensor T Lid Unbenannt E g Robot_Control Mn Sensor T Typ DPC Item LJ Data Ort Robot_Control cl Robot_Control IN D ata ItemlD IN Data Sensor_T Physikalische Adresse von Sensor_T x Suchen in DIE 4 Name Datenrichtung Adresse Byte Bit Schreibbar aw IN BYTE 0 Eingang 0 SESS SNS IN 0 0 Eingang 0 0 0 1 Eingang 01 IN 02 Eingang 0 2 Bl 3 Eingang 0 3 IN 0 4 Eingang 0 4 A IN 0 5 Eingang 05 nden amp IN 0 6 Eingang 0 6 81 7 Eingang 07 Abbrechen Ubemehmen Auswahl IN Auswahlen Schliefen Figure 2 5 Linking items and terminal points 3 The entire configuration can be carried out offline 654403 PHCENIX 2 19 CONTACT FL IL 24 BK B PAC UM E Startup After the hardware has been installed the bus configuration can either be configured online or started up using the project file Diagnostics The operating state of the Inline station can be checked at any time The comprehensive diagnostic functions provide support when removing errors from
144. erence potential The reference potential is directly led to the potential for Us and Uy jumper and is at the same time ground reference for the main and segment supply 1 4 2 4 FE Functional earth The functional earth ground must be connected to ground FE the 24 V DC supply functional earth ground connection The contacts are directly connected to the potential jumper and FE springs on the bottom of the housing The terminal is grounded when it is snapped onto a grounded DIN rail Functional earth ground is only used to discharge interference 1 8 PHCEN IX 654403 CONTACT FL IL 24 16 Supported Inline Modules Table 1 4 Digital Modules Designation Features Order No IB IL 24 DI 2 2 inputs 4 wire termination 24 V DC 27 26 20 1 IB IL 24 DI 2 PAC 2 inputs 4 wire termination 24 V DC 28 61 22 1 IB IL 24 DI 2 NPN 2 inputs with negative logic 4 wire termination 24 V DC 27 40112 IB IL 24 DI 2 NPN PAC 2 inputs with negative logic 4 wire termination 24 V DC 28 61483 IB IL 24 EDI 2 2 inputs 4 wire termination with electronic overload protection 27 42 609 and diagnostics IB IL 24 EDI 2 PAC 2 inputs 4 wire termination with electronic overload protection 28 61 629 and diagnostics IB IL 24 EDI 2 DESINA 2 inputs 4 wire termination according to Desina specification with 27 40 326 electronic ove
145. ested too many mailboxes within a short space of time Increase the time interval between individual mailbox requests and start the service DDI_MXI_SndMessage once more No further mailboxes of the required size are available Note the maximum mailbox size that can be used 1020 bytes Select a smaller mailbox or wait until a mailbox of the required size is free again An attempt was made to address the coprocessor board COP but it is faulty Please get in touch with Phoenix Contact 654403 PHCENIX a CONTACT FL IL 24 Cause Remedy Meaning Cause Remedy Meaning Cause Remedy ERR_SVR_IN_USE 009D pex The send vector register for the node is in use Address the register again or wait until the register is available again ERR SVR TIMEOUT 009Enex If a message placed in the MPM by the local bus master is not retrieved by the MPM node addressed this node does not reset the acknowledge message bit set by the local bus master i e the MPM node addressed does not indicate Message detected After a specific time has elapsed timeout the local bus master generates the error message ERR SVR TIMEOUT If this error message occurs repeatedly it must be assumed that the node being addressed is no longer ready to accept the message Invalid node called An attempt was made for example to address the coprocessor board COP which is faulty Please get in touch with Pho
146. etected when the value range was checked The following system parameters are defined Variable ID System parameters Value Comment 2216hex Up to date PD cycle time Read only 2240hex Plug amp play mode 0 Plug amp play mode inactive 1 Plug amp play mode active 2275hex Expert mode 0 Expert mode inactive 1 Expert mode active 2277 hex Fault Response Mode 1 Fault Reset Mode 2 Standard Fault Mode 0 Hold Last State Mode 2293hex Process Data Watchdog Timeout 0 Watchdog deactivated 200 65000 Timeout time in ms Table 4 4 Available fault response modes Mode Fault Response Valu Function Mode e Reset Fault Mode 1 The digital outputs are set to 0 and the analog outputs are set Default to the value configured by the user Default 0 Standard Fault Mode 0 All outputs are set to 0 Hold Last State 2 All outputs retain their last value 4 10 PHGNIX 654403 CONTACT Firmware Services Syntax Set_Value_Request 0750 Word 1 Word 2 Word 3 Word 4 1 Parameter Word 5 Bit 0 Code 0750 Command code of the service request Parameter Count Number of subsequent words 0x0003 Variable Count Number of system parameters to which new values are to be assigned 0x0001 Variable ID ID of the system parameter to which new values are to be assigned see Table 4 3 2240 Value New value of the system p
147. etwork connection interrupted or not present Reset The bus coupler can be reset by switching the supply voltage off and on again 1 6 PHGNIX 654403 CONTACT FL IL 24 BK B PAC 1 4 Connecting the Supply Voltage The module is operated using a 24 V DC SELV Typical Connection of the Supply Voltage Figure 1 3 e PP Q FAIL 100 Q XMT O RCV Q LINK FL IL 24 Ord No 2862327 10 100 Internal jumper in the module 61590004 Typical connection of the supply voltage 654403 1 7 FL IL 24 BK B UM E 1 5 Connector Assignment Table 1 3 Connector assignment Terminal Assignment Wire Color Remark Point Connector Power Connector 1 1 24 V DC 24 V Segment supply The supplied voltage is directly led to the potential Us jumper 1 2 24 V DC 24 V supply The communications power for the bus coupler and the connected local bus devices is generated from this power The 24 V analog power ana for the local bus devices is also generated 2 1 2 2 24 V DC Main power The main power is routed to the local bus devices via the potential jumpers 1 3 LGND Reference potential The potential is the reference ground for the logic ground for Ugg communications power 2 3 SGND Ref
148. evices in the logic area suppresses undesirable compensating currents and increases noise immunity The Ethernet interface is electrically isolated from the bus coupler logic The Ethernet cable shielding is directly connected to functional earth ground The device has two functional earth ground springs which have contact with the DIN rail when they are snapped on The springs are used to discharge interference rather than serve as a protective earth ground To ensure effective interference discharge even for dirty DIN rails functional earth ground is also led to terminals 1 4 and 2 4 Always ground either terminal 1 4 or 2 4 see Figure 1 32 on page 1 55 This also grounds the Inline station of the bus coupler sufficiently up to the first power terminal A 120 V AC or 230 V AC power terminal interrupts the FE potential jumper Therefore a 24 V DC power terminal which is located directly behind such an area must also be grounded using the FE terminal point To avoid the flow of compensating currents connect a suitably sized equipotential bonding cable parallel to the Ethernet cable The bus coupler does not have electrical isolation for the Inline module communications power Up 24 V UL 7 5 V and Uana 24 V are not electrically isolated The logic and I O devices can be supplied by separate power supply units If you wish to use different potentials for the communications power Ugk and the segment main voltage Us Uy do
149. exit 0 Sleep 500 Read Plug amp Play mode mxiAcc msgLength 8 mxiAcc msgBlk locMsgBlk 654403 PHCENIX 3 91 CONTACT FL IL 24 IB SetCmdCode locMsgBlk 0x0351 IB SetParaCnt locMsgBlk 0x0002 IB SetParaN locMsgBlk 0x01 0x0001 IB SetParaN locMsgBlk 0x02 0x2240 locRet DDI MXI SndMessage mxiHnd amp mxiAcc if locRet ERR OK printf FAIL Error code x locRet Get service confirmation mxiAcc msgLength 128 time amp starttime locRet 555 do locRet DDI MXI RcvMessage mxiHnd amp mxiAcc time amp ltime ae ltime starttime lt MXI TIMEOUT amp amp locRet ERR OK if locRet ERR_OK printf n n Incorrect confirmation received Error code 0x 04X locRet else PlugPlayModus IB GetParaN locMsgBlk 0x04 printf nPlug 6 Play mode d PlugPlayModus Plug amp Play mode is active no data can be written gt End of test if PlugPlayModus 0 printf nPlug amp Play mode is active gt End of test n exit 0 Read IBS status locRet GetIBSDiagnostic dtiHnd amp infoPtr if locRet ERR_OK 3 92 PHCENIX 654403 CONTACT Driver Software printf nError reading the INTERBUS status Error code 0x 04X locRet else if infoPtr state 0 00 0 printf nIBS status RUNNING else printf nIBS status 0x 04X
150. f the client The function is assigned a valid node handle DTI or MXI data channel and a pointer time to a variable with the timeout time This mode can be activated for all clients workstations with a DDI connection A connection to a client which only uses Ethernet management cannot be monitored If several connections to a client are activated simultaneously the client is only addressed once during a cycle If the connection no longer exists monitoring is also reset Echo Port Monitoring uses the so called echo port which is provided on all systems that support TCP IP Each data telegram to this port is sent back from the receiver to the sender The port is used for both connection oriented TCP and connectionless UDP In the case of the bus terminal the echo port is used with UDP to keep the resources used to a minimum Detecting an Error Connection monitoring sends a short data telegram to a client every 500 ms This interval is predefined and does not change according to the number of clients that are addressed This means that the frequency with which each client is addressed decreases with the number of connected clients After the data telegram has been sent the Inline bus terminal waits for a user defined time for the reply to be received If the reply is not received within this time the bus terminal sends another data telegram to 654403 PHCENIX on CONTACT FL IL 24 the relevant
151. figuration entry is shown where all attributes are enabled Syntax Configuration Entry Attribute Word x Device Number Word x41 Device Code Bit E 0 Attribute Device Number Bus_Segment_No Number of the bus segment where the INTERBUS device is located Value 0 Position Physical location in the bus segment Value range to 40 for an Inline station 654403 PHOENIX 4 27 CONTACT FL IL 24 BK PAC UM E Attribute Device Code Length_Code Length code The length code refers to the address space required by the INTERBUS device in the host ID_Code ID code The ID code describes the INTERBUS device function It is printed as Module Ident in decimal notation on the modules 4 28 PHGNIX 654403 CONTACT Firmware Services Task Remark Syntax Word 1 Word 2 Word 3 Bit Key 4 3 8 Complete Read Configuration Service This service reads entries in the configuration directory in the form of one or more columns which have been selected with the Used_Attributes parameter It is specially adapted to the PLC programming requirements This service can be understood as a meta service for the Read Configuration service 0309 hex The Start Entry No parameter does not need to be specified since this service reads all entries of the configuration frame Start Entry No 1 Complete Read Configuration Request 030Bhex Code O30Bhex Command code of the
152. gnal OUT OUT X X X Actuator supply Us Us 24 V X Ground GND GND 1 X X X Ground FE shielding FE X x X Used Not used IS 1 70 PHGNIX 654403 CONTACT FL IL 24 2 wire technology Sensor Actuator Different Connection Methods for Sensors and Actuators SO 1 O OUT1 OO Us OO Us OO GND O GND lOO FE OO FE L IN 1 24 V OUT 1 55200027 Figure 1 38 2 termination for digital devices Figure 1 38 A shows the connection of a 2 wire sensor The sensor signal is carried to terminal point IN1 Sensor power is supplied from the voltage Us Figure 1 38 detail B shows the connection of an actuator The actuator power is supplied through output OUT1 The load is switched directly by the output A meet ett scone 654403 PHCENIX pn CONTACT FL IL 24 BK B UME 3 wire technology 55200038 Figure 1 39 3 termination for digital devices Sensor Figure 1 39 A shows the connection of a 3 wire sensor The sensor signal is carried to terminal point IN1 IN2 The sensor is supplied with power via terminal points Us and GND Actuator Figure 1 39 B shows the connection of a shielded actuator The actuator is supplied through output OUT1 OU
153. gnostic IBDDIHND nodeHd T IBS DIAG infoPtr IBDDIHND nodeHd Node handle MXI or DTI of the bus terminal from which the diagnostic bit register and diagnostic parameter register are to be read T IBS DIAG infoPtrPointer to a T IBS DIAG data structure The contents of the register are entered in this structure struct USIGN16 state Status of the local bus USIGN16 diagPara Type of error controller user etc T IBS DIAG IBDDIRET If the function is executed successfully the value 0 ERR is returned Otherwise the return value is an error code UNIX Windows NT 2000 IBDDIHND ddiHnd T IBS DIAG infoPtr IBDDIRET ddiRet USIGN16 stateAB USIGN16 diagAB Sleep 20 Depending on the operating system ddiRet GetIBSDiagnostic ddiHnd amp infoPtr StateAB infoPtr state diagAB infoPtr diagPara while 3 34 P HCE IN IX 654403 CONTACT Driver Software 3 8 Monitoring Function Monitoring functions with different features are available for monitoring the Ethernet communication or the connected devices Process data watchdog process data monitoring Host checking and DTI monitoring There are monitoring functions according to the features functions that need to be monitored According to the application request the appropriate monitoring function can be activated By default upon delivery the process data watchdog is active Tabl
154. he Device Driver Interface DDI_DevOpenNode UNIX Task In order for the Device Driver Interface DDI to be able to find and address the desired bus terminal in the Ethernet network using the device name a file called ibsetha must be created This file contains the assignment between the device name and the IP address or the server name of the bus terminal The structure of the file and its entries is as follows 192 168 5 76 01 1 IBETHO1N1_D 2 02 1 IBETHO2N1 D Several device names be assigned to a single IP address or server name The individual device names are separated by spaces The address of the bus terminal can be entered in dotted notation 192 168 5 76 or as server name etha2 is of no importance If a device name is used several times only the first occurrence in the file is evaluated Windows NT 2000 The following entries should be created in the registry so that the Device Driver Interface DDI can find the selected bus terminal The driver creates the entries for you You will find the driver in the download area of www phoenixcontact com or on the CD FL IL 24 BK CD Order No 28 32 06 9 The following registry entry is created LOCAL MACHINE SOFTWARE Phoenix Contact IBSETH Parameters 1 Connect Timeout 08 00 00 00 DeviceNames IBETHO1N1_M IBETHO1NO 01 IBETHO1N1_D IBETHO1NO D IBETHO1N1 00 01 1 M 05 InUse YES ReceiveTimeout 08 00 00 00 IPAddress
155. he cables connectors and Inline connections for interruptions and repair them if required Error location Segment Position E PNM12 CONFIG MAU FAIL DI 0028 The Medium Attachment Unit MAU diagnosed interruption of the data transmission Cable break on the data return path of the incoming bus interface IN of the indicated Inline device Check the cables connectors and Inline connections for interruptions and repair them if required Error location Segment Position E PNM12 CONFIG INVALID ID 004 The specified Inline device has an invalid ID code Error location Segment Position 4 50 PHCENIX 654403 CONTACT Firmware Services Meaning Cause Remedy Add_Error_Info Meaning Remedy Add_Error_Info E PNM12 CONFIG MULTI ERR OUT 0080 Multiple error at the outgoing bus interface OUT1 of the specified INTERBUS device Fault on the bus cable connected to this bus interface of the following INTERBUS device or of a device of any subsequent local bus Check this part of the system for Missing or incorrect shielding of the bus cables connectors Missing or incorrect grounding equipotential bonding Poor connections in the connector loose contact cold junction Voltage dips on the communications power for remote bus devices Faulty fiber optic assembly Error location Segment Position E PNM12 CONFIG LB TOO LONG OUT oD9Chex
156. he driver software diagnostics uses error messages and error codes for the individual functions These error codes can be used to precisely define the cause of an error An operating system related offset ERR_BASE is added to the the codes listed here This offset has already been taken into consideration when using error message definitions Table 3 9 Driver software messages Code Error Message Cause Page 000044 ERR OK The function was executed successfully 3 77 008545 ERR INVLD NODE HD Invalid node handle specified 3 78 008654 ERR INVLD NODE STATE Node handle of a data channel that is already 3 78 closed specified 0087454 ERR NODE NOT READY Desired node not ready 3 78 008844 ERR WRONG DEV Incorrect node handle 3 78 008944 ERR DEV NOT READY Local bus master not ready yet 3 79 008Anex ERR INVLD PERM Access type not enabled for channel 3 79 008 ERR INVLD Utility function is not supported by driver Version 3 79 0 9 008Dhex ERR INVLD Command contains invalid parameter 3 79 009054 ERR NODE NOT PRES Node not available 3 80 009144 ERR INVLD DEV NAME Unknown device name used 3 80 009245 ERR NO MORE HNDL Device driver resources used up 3 80 009654 ERR AREA EXCDED Access exceeds limit of selected data area 3 83 009745 ERR INVLD DATA CONS Specified data consistency is not permitted 3 83 009Anex ERR MSG TO
157. iHnd IBDDIRET ddiRet DDI DTI ACCESS dtiReadAcc T DDI DTI ACCESS dtiWriteAcc USIGN8 oBuf 512 USIGN8 iBuf 512 dtiWriteAcc length 512 dtiWriteAcc address 0 dtiWriteAcc data oBuf dtiWriteAcc dataCons DTI DATA BYTE dtiReadAcc length 512 dtiReadAcc address 0 dtiReadAcc data iBuf dtiReadAcc dataCons DTI DATA BYTE oBuf 0 0x12 oBuf 1 0x34 ddiRet DDI_DTI_ReadWriteData ddiHnd amp dtiWriteAcc amp dtiReadAcc if ddiRet ERR OK Error treatment 654403 PHCENIX is CONTACT FL IL 24 Task Syntax Parameters Return value Format of the DDI MXI SndMessage The DDI MX SndMessage function is used to send a message to the bus terminal The function receives a node handle and a pointer to a T DDI MXI ACCESS data structure as parameters The T DDI MXI ACCESS structure contains all the parameters that are needed to send the message These parameters are transmitted to the bus terminal via the network without a plausibility check which means that invalid parameters are first detected at the bus terminal and acknowledged with an error message The BDDIHND nodeHd parameter specifies the bus terminal in the network to which the request is to be sent The node handle must be assigned to a mailbox interface data channel otherwise an appropriate error message is generated by the bus terminal IBDDIRET IBDDIFUNC DDI S
158. ics The following states can be read from the supply terminals Table 1 14 Diagnostic LED on the power terminal LED Color State Description of the LED States UM Green ON 24 V main circuit supply present 2 OFF Main circuit supply not present Table 1 15 Diagnostic LED on the segment terminal LED Color State Description of the LED States US Green ON 24 V segment circuit supply present 1 OFF Segment circuit supply not present Table 1 16 Additional LED on supply terminals with fuse LED Color State Description of the LED States E Red ON Fuse not present or blown 3 OFF Fuse OK 1 44 PHGNIX 654403 CONTACT FL IL 24 BK B PAC 654403 PHCEN IX 1 45 CONTACT FL IL 24 BK B UM E 1 13 3 Input Output Module Indicators 55200052 Figure 1 28 module indicators Diagnostics The following states can be read from the I O modules Table 1 17 Diagnostic LED of the I O modules LED Color State Description of the LED States D Green ON Local bus active 1 i Flashing 0 5 Hz Communications power present slow local bus not active 2Hz Communications power present medium I O error 4Hz Communications power pres
159. ide ee 0 Key Code 8956hex Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 4 40 PHCENIX 654403 CONTACT Firmware Services 000155 1 parameter word with a negative message 000244 2 parameter words Result Result of the service processing 0000hex Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add Error Info Additional information on the error cause 654403 PHCENIX 4 41 CONTACT FL IL 24 BK PAC UM E Task Prerequisite 4 4 Services for Direct INTERBUS Access 4 4 1 Start_Data_Transfer Service This service activates the cyclic data traffic on the bus After the execution of the service the controller board is in the Run state Before the service is called the controller board must be in the Active state i e a configuration frame has been activated and ID cycles are already being run at regular intervals Syntax Start Data Transfer Request 0701 hex Word 1 Word 2 Bit P 0 Key Code 0701 44 Command code of the service request Parameter Count Number of subsequent words 0000 No parameter word 4 42 PHOENIX 654403 CONTACT Firmware Services Syntax Start_Data_Transfer_Co
160. ill in progress 0001hex OBDF hex FFFFhex Positive message if error localization has been completed 1 Error Negative message 4 46 PHCENIX 654403 CONTACT Firmware Services Key Code Parameter_Count Result Entry_Count Error_Code Add Error Info 831644 Message code of the service confirmation Number of subsequent words with positive message during error localization 0004ne 4 parameter words with positive message after error localization 00XXhex 2 2 Entry Count 20 words maximum with a negative message 0002hex Always 2 parameter words Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed 0001 hex Information on the error type with positive message Error location Bus segment Position if it could be located with negative message Additional information on the error cause via error codes 654403 PHCENIX 97 FL IL 24 BK PAC UM E Cause Add_Error_Info Meaning Cause Remedy Table 4 5 Supported Error Codes Code Error Type Page 0x0A1C E SM CFG NUM OF DEV TOO BIG 4 48 OxOA2E E SM CFG IND ADDR LIST TOO BIG 4 48
161. ine modules is transferred via memory areas organized in a word oriented way separate memory areas for input and output data The Inline modules use the memory according to their process data width User data is stored in word arrays in the order of the connected modules The assignment of the individual bits is shown in the following diagram Bit 0 2 words 1 word 1 byte 4 bits 2 bits Figure 3 3 word array 61550007 Position of the user data for individual devices in the To achieve cycle consistency between input output data and the station bus cycle the bus terminal uses an exchange buffer mechanism This mechanism ensures that the required I O data is available at the correct time and is protected during writing reading by appropriate measures The following diagram shows the position of the user data for several devices in the word array Byte device Figure 3 4 4 bit device 2 bit device 61550008 Position of the user data for several devices in the word array 654403 3 7 FL IL 24 3 4 1 Position of the Process Data Example The physical assignment of the devices to the bus terminal determines the order of the process data in the memory The following diagram illustrates an example bus configuration and the position of the relevant process data FL IL 24
162. ing mailbox channel Error code d ret fflush stdout return 111 else printf nClose mailbox channel OK Close data channel ret DDI DevCloseNode dtiHnd if ret ERR OK printf nError closing data channel Error code d ret fflush stdout return 111 else printf nClose data channel OK return 0 MAIN int main void 3 90 PHCENIX 654403 CONTACT Driver Software IBDDIRET locRet 0 char Number 2 USIGN8 locMsgBlk MAX MSG LENGTH USIGN8 MAX MSG LENGTH int loci i USIGN16 ReadData 0 USIGN16 anzahl 255 USIGN16 PlugPlayModus 111 IBS DIAG infoPtr time t ltime time t starttime USIGN16 Read1 Read2 Read3 Read4 Display bus configuration printf n n Required bus configuration IB IL 24 DI 8 IB IL 24 DO 8Nn Entry of the controller number printf nController number Format xx gt gt scanf 2s Number strcat OPEN MXI Number strcat OPEN DTI Number strcat MXI N1 M strcat OPEN DTI N1 NnOPEN MXI 58 OPEN DTI 6s OPEN MXI OPEN DTI printf printf Create connections DTI channels to FL IL 24 locRet CreateConnection if locRet 0 printf nNo DTI MXI connection gt Test aborted
163. key for keyway featherkey connection 5520A033 Figure 1 4 Basic structure of an Inline module The most important of the components shown in Figure 1 4 are described in Electronics Base on page 1 15 and Connectors on page 1 16 ZBFM Zack marker strips flat see also Section Function Identification and Labeling on page 1 20 1 14 PH NIX 654403 CONTACT FL IL 24 BK B PAC B rere en nero oo 1 7 1 Electronics Base The electronics base holds the entire electronics for the Inline module and the potential and data routing Design widths The electronics bases for low level signal modules are available in a width of 8 terminal points 8 slot terminal or 2 terminal points 2 slot terminal Exceptions are combinations of these two basic terminal widths see also Section Dimensions of Low Level Signal Modules on page 1 24 654403 PH NIX 1 15 CONTACT FL IL 24 BK B UM E Advantages Connector width 1 7 2 Connectors The I O or supply voltages are connected using a pluggable connector This snap in place connection offers the following advantages Simple exchange of module electronics for servicing There is no need to remove the wiring Different connectors can be used on one electronics base depending on your requirements Regardless of the width of the electronics base the connectors have a width of two terminal points This means that you must plug 1 connector on a 2 slot base 2 c
164. lectrical Potential and Data 1 27 1 11 Circuits Within an Inline Station and Provision of the Supply 20244 1 29 1 11 1 Supply of the Ethernet Bus 1 30 1 11 2 Logic Circuit Up ec o s or toutes 1 11 3 Analog Circuit Uana 1 11 4 Main Circuit Uy sc Le cb DE 1 11 5 Segment 1 12 Voltage 24 000000000 654403 PHGNIX 1 1 CONTACT FL IL 24 BK B PAC UM E 1 13 Diagnostic and Status 1 42 1 13 1 LEDs on the Ethernet Bus Coupler 1 42 1 13 2 Supply Terminal Indicators 1 44 1 13 3 Input Output Module 1 46 1 13 4 Indicators on Other Inline Modules 1 47 1 14 Mounting Removing Modules and Connecting Cables 1 48 1 14 1 Installation Instructions 2422 1 48 1 14 2 Mounting and Removing Inline Modules 1 48 1 14 3 MOUNTING tea e etes 1 49 1214 4 lt teet 1 51 1 14 5 Replacing 1 53 1 15 Grounding an I
165. lid IP parameters are received they are saved as configuration data by the device Further Startups If the device already has valid configuration data it only sends three more BootP requests on a restart If it receives a BootP reply the new parameters are saved If the device does not receive a reply it starts with the previous configuration 2 2 Assigning an IP Address Using the Factory Manager There are two options available when assigning the IP address reading the MAC address via BootP or manually entering the MAC address in the Add New Ethernet Device dialog box in the Factory Manager 654403 PHCENIX 2 3 CONTACT FL IL 24 2 2 1 BootP Ensure that the network scanner 5 and the BootP server have been started Connect the device to the network and the supply voltage The BootP request for the new device triggered by the device restart reset appears in the Factory Manager message window Select the relevant message Click with the right mouse button on the BootP message of the device Enter the relevant data in the Add New Ethernet Device dialog box see Section 2 3 Save the configuration settings and restart the device power up 2 3 Manual Addition of Devices Using The Factory Manager Click on the Add device command or use the key combination CTRL A Enter the desired data under Description and TCP IP Address Activate the BootP Parameter by selecting Repl
166. ll figures tables and abbreviations are listed in the appendices index in the appendix makes it easier to search for specific key terms and descriptions 3 2 The Software Structure Client Controller board Device Driver Interface Firmware Read and write Coupling process data Send and eive messages gnostic pia 61560018 Driver software Figure 3 1 Software structure 654403 PH NIX 3 3 CONTACT FL IL 24 BK B PAC UM E 3 2 1 Ethernet Inline Bus Terminal Firmware The Ethernet Inline bus terminal firmware controls the Inline functions and Ethernet communication shown on the right hand side in Figure 3 1 The bus terminal provides a basic interface for using services via the Ethernet network The software primarily encodes and decodes the data telegrams for addressing the bus terminal services The firmware also ensures the network specific addressing of the bus terminal in the network i e the management of IP parameters 3 2 2 Driver Software The driver software DDI enables the creation of an application program shown on the left hand side in Figure 3 1 A library is available for Sun Solaris 2 4 Due to the large variety of different operating systems the driver software is available as source code in the BS ETH DDI SWD E Order No 27 51 13 7 The driver software can be divided into three groups The Device Driver Interface functions form the first group which cont
167. locRet ReadData IB PD GetDataN locReadB1lk 0x00 if ReadData loci printf rWritten 3d Read 3d Comparison OK loci ReadData else printf rWritten 3d Read 3d Comparison FAILED loci ReadData loci 3 94 PHCENIX 654403 CONTACT Driver Software while loci lt 256 Sleep 500 Close channels to FL IL 24 BK B PAC again locRet DeleteConnection printf nEND n Sleep 3000 return 0 654403 PHCENIX 3 95 CONTACT FL IL 24 BK B PAC UM E 3 96 PHCENIX 654403 CONTACT Section 4 This section informs you about firmware functions Firmware Services ue 4 3 4 1 aa nt 4 3 4 1 1 Services That be Used Every Operating 4 3 4 1 2 Services That are Only Available in Expert Mode 4 4 4 2 Notes on Service 48 4 4 4 2 1 Service Name of the 4 5 4 3 Services for Parameterizing the Controller Board 4 8 4 3 14 Control Parameterization Service 4 8 4 3 2 Set Value Service 4 10 4 3 8 Read Value 4 12 4 3 4 Initiate Load Configuration Service
168. lowing format Table 5 21 Answer to Write Coil Byte No Meaning BYTE 0 Function code 5 BYTE 1 2 Coil table offset as in the command BYTE 3 OxFF for setting the Coil to ON ON 0 for setting the coil to OFF OFF Byte 4 0 If the command accesses an invalid offset the exception response has the following format Table 5 22 Exception response to Write Coil Byte No Meaning 5 16 PHGNIX 654403 CONTACT Modbus TCP Protocol BYTE 0 Function code 0x85 BYTE 1 Exception code 2 5 5 6 1 Example for the Write Coil command With the Coil table offset 0 and the value OxFF the coil Q_1 is set to ON ON With the coil table offset 0 and the value 0 the Q1 is set to OFF OFF Each gt 3072 coil table offset results in an exception response 5 5 7 Write Single Register With this command a 16 bit word is written into the Modbus register table Only that part of the Modbus register table mapped to the Q and AQ I O tables as well as the first word of the error table can be written using this function The Write Single Register command has the following format Table 5 23 Write Single Register Byte No Meaning BYTE 0 Function code 6 BYTE 1 2 Register table offset BYTE 3 4 Register value 654403 PHGNIX 5 17 CONTACT FL IL 24 BK B PAC UM E The response to the Write Single Register command h
169. mation e g IP address status information or to change the configuration password protected 2 5 1 Calling Web Based Management WBM The FL IL 24 BK PAC web server can be addressed using the IP address if configured correspondingly The bus terminal homepage is accessed by entering the URL http ip address Example http 192 168 2 81 654403 PHCENIX 2 9 CONTACT FL IL 24 BK B PAC UM E FL IL 24 BK B PAC last update 8 36 37 FL IL 24 BK B PAC General Instructions Device Information Device Configuration Inline Station Figure 2 2 WBM homepage 2 5 2 Structure of the Web Pages The Ethernet bus terminal pages are divided into two with the selection menu and the relevant submenus on the left hand side and the corresponding information displayed on the right hand side Static and dynamic information about the bus terminal can be found in the following menus 2 10 PHGNIX 654403 CONTACT Startup Operation 2 5 3 Layout of the Web Pages FL IL 24 BK B PAC General Instructions ly Information Device Information General Technical Data Hardware Installation Local Diagnostics Device Configuration IP Configuration SNMP Configuration Change Password Watchdog Hardware Inline Station Services Process Data Monitoring Process Data Watchdog Remote Diagnostics Bus Configuration Event Table H 6155004 2 5 4 Password Prot
170. me or the first device behind the bus coupler is defect or is missing 1 Activate a correct configuration frame Use the first device or aother functioning device E PNM12 DEVICE STATE 1 hex The specified Inline device indicates a peripheral fault Check the specified Inline device Device number Segment Position of the Inline device E PNM12 CONFIG MISSING DEVICE 0D10hex An Inline device is missing A device entered in the active configuration and not marked as switched off is missing from the connected bus configuration The active configuration is the quantity of INTERBUS devices connected to the INTERBUS system whose data is within the summation frame during bus cycles The active configuration may differ from the connected bus configuration only when physically connected bus segments have been switched off Compare the active configuration with the connected bus configuration taking any disabled bus segments into account Error location Segment Position 654403 PHCENIX FL IL 24 BK PAC UM E Meaning Cause Remedy Add_Error_Info Meaning Cause Remedy Add_Error_Info Meaning Add Error Info E PNM12 CONFIG MAU FAIL DO 0D20hex The Medium Attachment Unit MAU firmware component diagnosed an interruption of the data transmission Cable break on the data forward path of the incoming bus interface IN of the indicated Inline device Check t
171. modified by the subnet mask An extended IP address is generated from the user address and subnet mask Because the masked subnetwork is only recognized by the local PC all the other devices display this extended IP address as a standard IP address 654403 PHCENIX 27 CONTACT FL IL 24 BK B PAC UM E 2 4 3 Structure of the Subnet Mask The subnet mask always contains the same number of bits as an IP address The subnet mask has the same number of bits the same position set to one which is reflected in the IP address for the network class Example An IP address from class A contains a 1 byte network address and a 3 byte PC address Therefore the first byte of the subnet mask may only contain ones The remaining bits three bytes then contain the address of the subnetwork and the PC The extended IP address is created when the bits of the IP address and the bits of the subnet mask are ANDed Because the subnetwork is only recognized by local devices the corresponding IP address appears as a normal IP address to all the other devices Application If the ANDing of the address bits gives the local network address and the local subnetwork address the device is located in the local network If the ANDing gives a different result the data telegram is sent to the subnetwork router Example for a class B subnet mask Decimal notation 255 255 192 0 Binary notation 1111 1111 1111 1111 1100 0000 0000 0000 Subnet m
172. n and wiring Common technical data Phoenix Contact reserves the right to make any technical extensions and changes to the system that serve the purpose of technical progress Until a new manual revision is published any updates or changes will be documented on the Internet at http www phoenixcontact com or http www factoryline de 654403 PHCENIX CONTACT FL IL 24 PHGNIX 654403 CONTACT Table of Contents a idee cie 1 3 1 1 General 1 3 1 1 1 Product Description 2 2 1 3 1 2 Structure of the FL IL 24 BUS GCoUuplet i e 1 5 1 3 Local Status and Diagnostic 1 6 1 4 Connecting the Supply 1 7 1 5 Connector Assignment ssssssssssseeneneeneeennnn 1 8 16 Supported Inline 1 9 1 7 Basic Structure of Low Level Signal Modules esserne ennen nr nennen nnne 1 14 1 7 1 Electronics 0 4040 01 1 15 1 27 27 lt 1 16 1 8 Function Identification and 1 20 1 9 Dimensions of Low Le
173. n clamp alignment The shield connection clamp a in Figure 1 37 2 in the shield connector can be used in various ways depending on the cross section of the cable For thicker cables the dip in the clamp must be turned away from the cable Figure 1 37 2 For thinner cables the dip in the clamp is turned towards the cable Figure 1 37 6 If you need to change the direction of the shield connection clamp proceed as shown in Figure 1 37 Open the shield connector housing 1 The shield connection is delivered with the clamp positioned for connecting thicker cables 2 Remove the clamp 3 turn it to suit the cross section of the cable 4 then reinsert the clamp 5 Figure 6 shows the position of the clamp for a thin cable 654403 FL IL 24 BK B UM E 1 17 Connecting the Power Supply To operate a station you must provide the supply voltage for the bus coupler logic of the modules and the sensors and actuators The voltage supplies are connected using unshielded cables Section 1 16 1 E gp 1 66 PHCENIX 654403 CONTACT FL IL 24 Um Us Electrical isolation Voltage ranges 1 17 1 Power Terminal Supply Apart from supplying the I O voltage at the Fieldbus coupler it is also possible to provide the voltage through a power terminal 24 V Main Circuit Supply The main power is reintroduced at the power terminal 24 V
174. n the voltage supply The supplies Uy Usg and the bus coupler supply do not have the same ground potential because they are supplied by two separate power supply units Behavior in the event of voltage fluctuations Voltages main and segment supply that are transferred from the bus coupler to the potential jumpers follow the supply voltages without delay Nominal value 24 V DC Tolerance 15 20 according to EN 61131 2 Ripple 5 96 Permissible range 19 2 V to 30V Current carrying capacity 8 A maximum total current of Us and Uy Safety equipment Surge voltage Polarity reversal Input protective diodes can be destroyed by permanent overload Pulse loads up to 1 500 V are short circuited by the input protective diode Parallel diodes against polarity reversal in the event of an error the high current through the diodes causes the preconnected fuse to blow 6 4 PHCENIX 654403 Technical Data 24 V Bus Coupler Supply Connection method Spring cage terminals Recommended cable lengths 30 98 43 ft maximum do not route cable through outdoor areas Voltage continuation Via potential routing UL Uana Safety equipment Surge voltage Polarity reversal Input protective diodes can be destroyed by permanent overload Pulse loads up to 1 500 V are short circuited by the input protec
175. nal parameter block the size of which is also entered in the structure This parameter block is purely optional and is not used for the modes that exist at present Thus the structure component numOfBytes should be set to Zero 654403 PHCENIX 3 53 CONTACT FL IL 24 Parameters Format of the T_ETH_NET_FAIL_M ODE data structure IBDDIHND nodeHd Node handle of a controller board for which the NetFail mode is to be changed T ETH NET FAIL MODE netFailModelnfo Pointer to a ETH NET FAIL MODE data structure This structure contains the parameters for setting the NetFail mode and if necessary optional parameters typedef struct USIGN16 mode NetFail mode USIGN16 numOfBytes Size of the parameter block in bytes VOID miscParamPtr Parameters for the relevant NetFail mode ETH NET FAIL MODE The function prototypes the type definition of the data structure and the symbolic constants be found in the IOCTRL H file 3 54 H N IX 654403 CONTACT Driver Software Task Syntax Parameters Format of the structure Constants of the different NetFail modes ETH_GetNetFailMode The ETH_GetNetFailMode function can be used to read the set NetFail mode The routine expects a valid node handle and a pointer to a T ETH NET FAIL MODE data structure see above as parameters After the routine has been called successfully the u
176. nal is set by writing a register in the coupling memory of the bus terminal As soon as this signal has been detected by the bus terminal all outputs of the local bus devices are set back Only after the NetFail signal has been set back to zero the process data can be ouput again The NetFail signal is always set if the connection to the client is interrupted the bus terminal does not write data to the DTI within the specified time or a general malfunction has been detected on the bus terminal which prevents safe operation The setting of the NetFail signal is indicated by setting the NetFail bit in the control word of each data telegram which is sent by the bus terminal The NetFail signal can be reset using the appropriate command or if this is no longer possible by executing a power up 3 48 P HCE 654403 Driver Software Task Syntax Parameters Return value Example Task ETH_SetNetFail The ETH_SetNetFail function sets the NetFail signal on the bus terminal and thus prevents the further output of process data to the local bus devices The function is assigned a node handle for a DTI or mailbox data channel of the relevant bus terminal as a parameter IBDDIRET IBDDIFUNC ETH SetNetFail IBDDIHND IBDDIHND nodeHd Node handle MXI or DTI for the bus terminal on which the NetFail signal is to be executed IBDDIRET If the function is executed successfully the
177. nal memory outputs are set internal memory internal memory error removal after to cable interrupt First write access in Last values in the Internal Last values inthe Internal memory the output table internal memory memory output table plus after restoring the plus the newly the newly written connection written values values Operation Last values in the Internal Last values inthe Internal memory internal memory memory internal memory plus all newly plus all newly written values written values 654403 PHCENIX 3 47 CONTACT FL IL 24 BK B PAC UM E Example The last entries in the internal memory have the following values Module AO DO 16 DO 2 Value 0x0123 0x4321 0x0002 If Ox00A1 is written into the internal memory of the DO 16 as first value after having restored the connection we get the following actual output value Module AO DO 16 DO 2 Value 0x0123 0x00A1 0x0002 This is the status Last values in the internal memory plus the newly written values If values such as 0x0010 for AO 0x0001 for DO 2 and OxACDC for DO 16 have been written into the internal memory via several write accesses we get the following output values Module AO DO 16 DO2 Value 0x0010 OxACDC 0x0001 This is the status Last values in the internal memory plus the newly written values 3 8 5 Handling the NetFail Signal Testing With ETH SetNetFail The NetFail sig
178. nal point number in a row It is directly indicated on the terminal point 3 in Figure1 9 The precise designation for a point is thus specified by the slot and terminal point The highlighted terminal point 4 in Figure1 9 would be numbered as follows slot 3 terminal point 2 3 In addition to this module marking you can identify the slots terminal points and connections using marker strips and labeling fields 654403 bel CONTACT FL IL 24 BK B UM E 5520A036 Figure1 10 Labeling of modules 1 22 PHCENIX 654403 CONTACT FL IL 24 Various options are available for labeling the slots and terminal points 1 Each connector can be labeled individually with Zack markers 2 3 Another option is to use a large labeling field This labeling field is available in two widths either as a labeling field covering one connector 2 or as a labeling field covering four connectors 3 You can label each channel individually with free text On the upper connector head there is a keyway for attaching this labeling field The labeling field can be tilted up and down At each end there is a small latch which ensures that the labeling field remains in place 4 5 Each signal can be labeled individually using Zack markers On a double signal connector the upper keyway 4 is designed for labeling signals 1 2 and the lower keyway 5 is for signals 3 4 6 On the electronics base each slot can be
179. nd Set Value on the object ID 2277 The following table shows the three possible reactions Available fault response modes Fault Response Mode Value Function Reset Fault Mode Default 1 The digital outputs are set to 0 and the analog outputs are set to the value configured by the user Default 0 Standard Fault Mode All outputs are set to Hold Last State Mode 2 outputs retain their last value Table 3 6 The FL IL 24 BK B PAC only has one internal volatile memory where the process data are stored during runtime This memory image is displayed cyclically onto the appropriate Inline modules 3 8 4 1 The Power Up Table Power up sequence Power Up Sequence Front View of the Configuration Reset Fault Mode Configuration Last State Fault memory after power up FL IL 24 BK Mode Internal memory Actual output Internal memory Actual output Power up o o o o First write access 0 plus the new Internal memory 0 plus the new Internal memory onto an internal values values Operation 0 plus the sum of all new values Internal memory 0 plus the sum of all new values Internal memory Example A station consists of 3 I O modules an analog output module with a length of 16 bit AO a digital output module with a length of 16 bit DO 16 and a digital output module with a length of 2 bit D
180. ndMessage IBDDIHND nodeHd T DDI MXI ACCESS IBDDIHND nodeHd Node handle for the connection via which a message is to be written to the mailbox interface The node handle also determines the bus terminal which is to be accessed T DDI MXI ACCESS dtiAcc Pointer to a T DDI MXI ACCESS data structure This structure contains all the parameters needed for access IBDDIRET If the function is executed successfully the value 0 ERR is returned Otherwise the return value is an error code struct T DDI MXI USIGN16 msgType ACCESS Message type see DDI description structure USIGN16 msgLength Length of the message in bytes USIGN16 DDIUserID Message ID USIGN8 msgBlk Pointer to the message data T DDI MXI ACCESS 3 30 PHCENIX 654403 CONTACT Driver Software Example UNIX Windows NT 2000 IBDDIHND mxiHnd IBDDIRET ddiRet DDI MXI ACCESS mxiAcc USIGN8 oBuf 256 mxiAcc msgLength 4 mxiAcc DDIUserID 0 mxiAcc msgType 0 mxiAcc msgBlk oBuf O I IB SetCmdCode oBuf S CREATE CFG REQ IB SetParaCnt oBuf 1 IB SetParaN oBuf 1 1 ddiRet DDI MXI SndMessage mxiHnd amp mxiAcc if ddiRet ERR OK Error treatment 654403 PHCENIX e CONTACT FL IL 24 IS Syntax Parameters Return value Format of the DDI RcvMessage The DDI_MXI_RcevMessage fun
181. nfiguring and installing an Ethernet Inline station This manual is written based on the assumption that the reader possesses basic knowledge about Inline systems For specific information on the individual Inline terminals see the corresponding terminal specific data sheets Make sure you always use the latest documentation Changes in or additional information on present documentation can be found on the Internet at http www phoenixcontact com or http www factoryline de The Phoenix Contact homepage is updated daily You can also contact us by sending an e mail to factoryline service phoenixcontact com PHGNIX 654403 CONTACT Orientation in this manual This user manual includes Validity of documentation For easy orientation when looking for specific information the manual offers the following help The manual starts with the main table of contents that gives you an overview of all the topics Each manual section starts with an overview of the section topics On the left side of the pages within the sections you will see the topics that are covered in the section In the appendix you will find a list of figures and a list of tables In the first section you are introduced to Inline basics and general information that applies to all terminals or terminal groups of the Inline range Topics are for example Overview of the Inline Product Groups Terminal Structure Terminal installatio
182. nfirmation 8701 hex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit 0 Code 8701 code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0001hex 1 parameter word with a negative message 0002 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 654403 PHGNIX 4 43 CONTACT FL IL 24 BK PAC UM E 4 4 2 Alarm_Stop Service Task This service triggers a long reset on the bus Data traffic is stopped Modules with process data set their outputs to the value 0 The command is executed directly after the current data cycle has been completed After the execution of the service the controller board is in the Ready state Syntax Alarm_Stop_Request 1303 Word 1 Word 2 Bit 0 Code 1303hex Command code of the service request Parameter_Count Number of subsequent words 0000 No parameter word Syntax Alarm_Stop_Confirmation 9303 hex Positive message Word 1 Word 2 Word 3 Negative message W
183. nline Station 000201 1 55 1 15 1 Shielding an Inline Station 1 57 1 15 2 Shielding Analog Sensors and Actuators 1 57 1 16 Connecting Cables 1 61 1 16 1 Connecting Unshielded Cables 1 61 1 16 2 Connecting Shielded Cables Using the Shield Connector 1 63 1 17 Connecting the Power 1 66 1 17 1 Power Terminal 44000 1 67 1 17 2 Provision of the Segment Voltage Supply at Power 00 4 1 68 1 17 3 Requirements Regarding the Voltage Supplies 1 68 1 18 Connecting Sensors and 1 68 1 18 1 Connection Methods for Sensors and Actuators 1 68 1 18 2 Examples of Connections for Digital I O Modules 1 70 1 2 PHCENIX 654403 CONTACT FL IL 24 1 FL IL 24 1 1 1 General Functions 1 1 Ethernet Inline Bus Coupler Product Description Features Ethernet coupler for the Inline I O system Ethernet TCP IP 10 100 Base T X Up to 63 other Inline modules can be connected process data channel Flexible installation system for Ethernet IP parameter setting via BootP DDI software interface Device Driver Interface and Mo
184. nnecting the shield This section describes the connection of a shielded cable using an analog cable as an example Connection should be carried out as follows e Strip the outer cable sheath to the desired length 1 The desired length a depends on the connection position of the wires and whether there should be a large or a small space between the connection point and the shield connection e Shorten the braided shield to 15 mm 0 59 1 e Fold the braided shield back over the outer sheath 2 Remove the protective foil e Strip 8 mm 0 32 off the wires 2 e Push screwdriver into the slot for the appropriate connection Figure 1 35 on page 1 61 1 so that you can plug the wire into the spring opening recommends using a SFZ 1 0 x 3 5 screwdriver Order No 12 04 51 7 see CLIPLINE catalog from Phoenix Contact e Insert the wire Figure 1 35 on page 1 61 detail 2 Remove the screwdriver from the opening This clamps the wire e Open the shield connector 3 e Check the direction of the shield connection clamp in the shield connector see Figure 1 37 e Place the cable with the folded braided shield in the shield connector 4 e Close the shield connector 5 e Fasten the screws for the shield connector using a screwdriver 6 1 64 H 654403 FL IL 24 Shield connection clamp 5520A068 Figure 1 37 Shield connectio
185. not connect the GND and grounds of the supply voltages 654403 PHCENIX 1599 FL IL 24 BK B UME Option 1 The Fieldbus coupler main voltage and the I O supply Us are provided separately with the same ground potential from two voltage supplies Local bus 0 UL GND uC Ethernet 61560004 Figure 1 20 Potential areas in the bus coupler two voltage supplies Voltage areas 1 Ethernet interface area 2 Functional earth ground PE and shield Ethernet interface area 3 Main voltage Uy and I O voltage Us area 4 Inline communications power 1 36 PHCENIX 654403 CONTACT FL IL 24 Option 2 Common supply of voltages and Us from one voltage supply Local bus UL Unna UL GNDy uC 3 24 V Us Usk Un U 5 24 V Uy GNDysx GND Ethernet 81560005 Figure 1 21 Bus coupler potentials one voltage supply Voltage areas 1 Ethernet interface area 2 Functional earth ground shield Ethernet interface area bus coupler 3 Main voltage Uy and I O voltage Us area Adjacent power connectors can only be used when all the voltages supplied to the bus coupler have the same reference potential Simply insert the external jumper to correctly connect all the supply points see Typical connection of the 2 voc iui 12 m supply voltage on page 1 30 Jumpered in 1 23 the module
186. nse 5 5 3 Read Coils This command reads from 1 to 2000 bits from the Modbus register table The Read Coils command has the following format Table 5 11 Read Coils Byte No Meaning BYTE 0 Function code 1 BYTE 1 2 Coil table offset BYTE 3 4 Bit Count 1 2000 The response to the Read Coils command has the following format Table 5 12 Answer to Read Coils Byte No Meaning BYTE 0 Function code 1 BYTE 1 Byte Count of the response Byte Count Bit Count of the command 7 8 BYTE 2 B 1 Bit values the least significant bit is the first coil 654403 PHCENIX ii CONTACT FL IL 24 BK B PAC UM E If the command accesses an invalid offset or receives an invalid length an exception response with the following format is output Table 5 13 Exception response to Read Coils Byte No Meaning BYTE 0 Function code 0x81 BYTE 1 Exception response 2 5 5 3 1 Example for Read Coils Coil table offset 0 and Bit Count 1 returns coil Q1 Coil table offset 0 and Bit Count 2000 returns the coil values Q1 2000 Coil table offset 4 and Bit Count 13 returns the Coil values Q5 17 Every combination of the Coil table offset and the Bit Count that accesses an offset gt 3072 results in an exception response 5 5 4 Read Input Discretes This command reads from bit 1 to 2000 from the Modbus coil table The Read Input Discretes
187. ntents Every Operating Mode 2 4 3 4 1 2 Services That are Only Available in Expert Mode 4 4 4 2 Notes on Service 4 4 4 2 1 Service Name of the Service 4 5 4 3 Services for Parameterizing the Controller Board 4 8 4 3 14 Control Parameterization Service 4 8 4 3 2 Set Value Service 2 4 10 4 3 8 Read Value Service 4 12 4 3 4 Initiate Load Configuration Service 4 14 4 3 5 Load Configuration Service 4 16 4 3 6 Terminate Load Configuration Service 4 20 4 3 7 Read Configuration Service 4 22 4 3 8 Complete Read Configuration Service 4 29 4 3 9 Delete Configuration Service 4 32 4 3 10 Create Configuration Service 4 33 4 3 11 Activate Configuration Service 4 36 4 3 12 Control Device Function Service 4 38 4 3 13 Reset Controller Board Service 4 40 4 4 Services for Direct INTERBUS 4 42 4 4 1 Start Data Transfer Service 4 42 4 4 8 Alarm St
188. nter to a T ETH PD IN MON structure as parameters The ETH PD IN MON structure contains all the information needed to parameterize the process IN data monitoring mode Mode in which the monitoring is to be executed address Start address in bytes from which the input data is to be monitored numOfBytes Size of the area to be monitored in bytes it must not exceed 1024 bytes maskData Pointer to a vector with the masking data notifyFuncPtr Zero is not supported The masking data is combined bit by bit with the data that has been read and determines whether a change in the associated IN data bit will lead to notification of the client A set bit 1 means that this bit is of significance for the monitoring A bit that is not set 0 means that a change in the associated bit in the process IN data area is insignificant IBDDIRET IBDDIFUNC ETH_ActivatePDInMonitoring IBDDIHND nodeHd T ETH PD IN MON infoPtr 654403 PHCENIX PM CONTACT FL IL 24 Parameters Return value Format of the data structure Constants for the different modes Description of the constants IBDDIHND nodeHd Node handle DTI for the controller board for which process data monitoring is to be activated T ETH PD IN MON infoPtr Pointertoa T ETH PD IN MON data structure This structure contains all the parameters needed to activate monitoring IBDDIRET If the function is executed successfully the value
189. nternal potential jumper FL IL 24 BK B PAC IB IL DO 8 IB IL DI 8 FL IL 24 BK B PAC Ord No 2862327 PP O FAIL e 100 XMT RCV LINK 10 100 22 l Figure 3 14 Structure of the station for the example program 3 16 1 Demo Structure Startup The user is first prompted to specify the bus terminal on which the program is to be executed This is specified using the registry entries position 01 to 99 The entry must always be two digits 3 86 PHCENIX 654403 CONTACT Driver Software Function First the status of Plug amp Play mode is read If P amp P mode is activated value 1 the program is terminated with the error message 00A9hex ERR_PLUG_PLAY because process data cannot be written in P amp P mode for security reasons A check then determines whether the local bus in the station is running If not the program is also terminated If both conditions are met data items 1 to 255 are output from the output module Jumpering between the outputs and inputs enables the output data to be read in again The read data is compared with the output data If they are the same Comparison OK is output and if they are different Comparison FAILED is output After the process data it
190. o 100 current carrying capacity of the power supply unit in the derating curves on page 6 6 Make sure that the indicated nominal current carrying capacity in the derating curves is not exceeded when the ambient temperature is above 40 C 104 F Corresponding with the formula the total current carrying capacity of the connected I O is relevant Ppgg If for example no current is drawn from the analog supply the percentage of current coming from the communications power can be increased Example Ambient temperature 55 C 131 F 1 Nominal current carrying capacity of the communications power and analog supply 50 96 according to the diagram ll Logic 1 I Analog 0 25 1 1 W 0 175 W 1 275 W corresponds to 50 of 2 55 W 2 Possible logic current if the analog supply is not loaded Pperi 1 1 X lii ogic 0 W Peeni 1 1 lii lLLogio 1 275 W 1 1 1 159 A 6 8 PHGNIX 654403 CONTACT Technical Data Safety Equipment Surge voltage segment supply main supply bus coupler supply Input protective diodes can be destroyed by permanent overload Pulse loads up to 1 500 V are short circuited by the input protective diode Polarity reversal segment supply main supply Parallel diodes against polarity reversal in the event of an error the high current through the diodes causes the preconnected fuse to blow
191. o 100 16 bit words into the Modbus register table This command can only write in that part of the table that reflects the coils and AQ The Write Read command has the following format Table 5 33 Read Write Register Byte No Description BYTE 0 Function code 0x17 BYTE 1 2 Read register table offset BYTE 3 4 Number of words to be read 1 to 125 BYTE 5 6 Write register table offset BYTE 7 8 Number of words to be written 1 100 BYTE 9 Number of bytes to be written B 2 x number of words to be written BYTE 10 B Write register values 9 The response to the Read Write Register command has the following format Table 5 34 Answer to Read Write Register Byte No Description BYTE 0 Function code 0x17 BYTE 1 Byte Count B 2 x number of words to be read BYTE 2 1 Read register values If the command accesses an invalid offset the exception response has the following format Table 5 35 Exception response to Read Write Register Byte No Description BYTE 0 Function code 0x97 BYTE 1 Exception code 5 22 PHGNIX 654403 CONTACT Modbus TCP Protocol 5 5 12 1 Examples for the Read Write Register command Register table offset 0 and Word Count 2 returns values of the input discretes 1 32 Register table offset 575 and Word Count 2 returns values of the coils Q3057 3072 and the analog output AQ1 R
192. onnectors on a 4 slot base and 4 connectors on an 8 slot base Connector types The following connector types are available 61560010 Figure 1 5 Connector types of Inline 1 Standard connector The green standard connector is used for the connection of two signals in 4 wire technology e g digital I O signals The black standard connector is used for supply terminals The adjacent contacts are jumpered internally see Figure 1 6 on page 1 18 2 Shield connector 1 16 PHOENIX 654403 CONTACT FL IL 24 BK B PAC Connector identification This green connector is used for signals connected using shielded cables e g analog I O signals FE or shielding is connected by a shield connection clamp rather than by a terminal point 3 Extended double signal connector This green connector is used for the connection of four signals in 3 wire technology e g digital I O signals All connectors are offered with and without color print The connectors with color print marked with CP in the Order Designation have terminal points that are color coded according to their functions The following colors indicate the signals of the terminal points Table 1 9 Terminal point color coding Color Terminal Point Signal Red Blue Green Functional earth ground yellow 654403 PH NIX 1 17 CONTACT FL IL 24 BK B UM E Internal structure of
193. op Service 4 44 4 5 Diagnostic 400 00 4 45 4 5 1 Get Error Info 4 45 4 5 2 Get Version Info Service 4 52 4 6 X Error Messages for Firmware 4 56 4 6 1 x52 auci te E ertet id elt 4 56 4 6 2 Positive Messages 4 57 4 6 3 Error 4 57 5 Modb s TOP PIO lo60l eet eo o tede meta tees 5 3 5 1 Modbus Protocol 2 re aide 5 4 5 1 1 Modbus Connections sse 5 4 5 1 2 Modbus Interface 5 4 654403 PHGNIX v CONTACT FL IL 24 BK B UM E 5 1 3 Modubus Conformity Classes 5 4 5 1 4 Modbus Message Format 5 5 5 1 5 Modbus Byte Sequence 5 5 5 1 6 Modbus Bit Sequence 5 6 5 2 Modbus Function 5 6 5 3 Modbus Table cec eee 5 6 5 3 1 Example Position of the Input Output Data 5 8 5 4 Executable 5 9 5 5 Supported Function Codes 5 10 5 5 1 Read Multiple Registers
194. or inductive and 28 62 18 1 PAC capacitive loads IB IL 24 48 DOR 2W 2 relais PDT contacts 5 V 50 V AC 5 V 120 V DC 2 A 28 62 97 4 IB IL 24 48 DOR 2W PAC 2 relais PDT contacts 5 V 50 V AC 5 V 120 V DC 2 A 28 63 119 Table 1 5 Analog Modules Designation Features Order No IB IL Al 2 4 20 2 inputs 2 wire termination 24 V DC 0 10 V 10 V 28 60 44 2 0 20 mA 4 20 mA x20 mA IB IL Al 2 4 20 PAC 2 inputs 2 wire termination 24 V DC 0 10 V 10 V 2862217 0 20 mA 4 20 mA x20 mA IB IL Al 2 SF 2 inputs 2 wire termination 24 V DC 0 10 V x10 V 27 26 285 0 20 mA 4 20 mA x20 mA 0 40 mA 40 mA IB IL AI 2 SF PAC 2 inputs 2 wire termination 24 V DC 0 10 V 10 V 28 61 302 0 20 mA 4 20 mA x20 mA 0 40 mA 40 mA IB IL AI 2 SF 230 2 inputs 2 wire termination 24 V DC 0 10 V x10 V 27 40818 0 20 mA 4 20 mA 20 mA 0 40 mA 40 mA 230 Hz IB IL AI 2 SF 230 PAC 2 inputs 2 wire termination 24 V DC O 10 V x10 V 2861577 0 20 mA 4 20 mA x20 mA 0 40 mA 40 mA 230 Hz IB IL AI 8 SF 8 inputs 2 wire contact 24 V DC 5V 0 10V 10 0 25 2727831 V 0 20 mA 4 20 mA 20 mA 0 40 mA IB IL Al 8 SF PAC 8 inputs 2 wire contact 24 V 0 5 0 10V 10 0 25 2861412 V 0 20 4 20 mA 20 mA 0 40 mA IB IL AI 8 15 8 inputs 3 wire termination 24 V DC 0 20 mA 27 42748 4 20 mA 20 mA 0 40 mA 40 mA IB IL AI 8 IS PAC 8 inputs 3 wire termin
195. ord 1 Word 2 Word 3 Word 4 Bit UL edie 0 9303hex Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0001hex 1 parameter word with a negative message 0002 2 parameter words 4 44 PHCENIX 654403 CONTACT Firmware Services Task Syntax Word 1 Word 2 Bit Key Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 4 5 Diagnostic Services 4 5 1 Get Error Info Service This service can be used to read out the exact error cause and location after a bus error has been indicated A maximum of ten errors are analyzed Get Error Info Request 0316hex Code 0316hex Command code of the service request Parameter_Count Number of subsequent words 0000 No parameter word 654403 1 45 CONTACT FL IL 24 BK PAC UM E Syntax Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 1 Word 2 Word 3 Word 4 Bit Get_Error_Info_Confirmation 8316 Positive message as long as error localization is st
196. ot zero Thus there are the following values for the status word 0 An error occurred e g bus error 1 No error occurred 2 A NetFail occurred Table 5 39 Status Word 15 14 13 12 11 10 8 7 6 Reserved bits 654403 PHCENIX CONTACT 5 25 FL IL 24 E 5 6 3 Diagnostics Using the Analog Input Table Table 5 40 Structure of the analog input table Analog input table Address First input word 192 193 Diagnostic status register 382 Diagnostic parameter register 383 The diagnostic data are entered into the analog input table The diagnostic status register and the diagnostic parameter register occupy the last two words in the analog input table 5 6 4 Error Table Data Format of the Error Table The Modbus client can access this internal error table that may contain 32 eror codes This internal error table works accoring to the FIFO principle First In First Out This means that the 33rd error entry deletes the oldest error entry An application can request all error entries or it can delete all entries via one command sent to the bus termimal Every error entry is written in two words beginning with the reference 1024 in the register table All error entries serve as information and do not stop the bus terminal Reading the Error Table Data The complete error table can be read out using
197. otential jumper for and or Us is reached total current of Us and a new power terminal must be used 654403 PHCENIX 1 33 CONTACT FL IL 24 BK B UM E Generation of Us There are various ways of providing the segment voltage Us 1 Thesegmentvoltage can be supplied atthe Ethernet Inline bus coupler or a power terminal 2 segment voltage can be tapped from the main voltage at the Ethernet Inline bus coupler or a power terminal using a jumper or a Switch 3 Asegment terminal can be used with a fuse Within this terminal the segment voltage is automatically tapped from the main power 4 Asegment terminal can be used without a fuse and the segment voltage can be tapped from the main voltage using a jumper or a switch FL IL 24 BK B PAC PWR IN SEG F M U Uana GNDL Gc H 65440003 Um Us Um Figure 1 19 Segment circuit FL IL 24 BK B PAC Ethernet Inline bus coupler PWR IN Power Terminal SEG F Segment terminal with fuse as an example of a segment terminal 1 34 PHCENIX 654403 FL IL 24 Electrical isolation Ethernet No electrical isolation of the Inline communications power Isolated supply for logic and I O devices 1 12 Voltage Concept The Ethernet bus coupler and the Inline local bus system have a defined potential and grounding concept This avoids an undesirable effect on I O d
198. r byte bit 0 to 7 of a parameter from the 3 70 specified receive buffer IB GetBytePtrHiByte Returns the address of a parameter entry starting with the 3 70 high order byte bit 8 to 15 IB GetBytePtrLoByte Returns the address of a parameter entry starting with the 3 71 low order byte bit O to 7 IB PD GetLongDataN Reads a double word 32 bit from the specified position in 3 72 the input buffer IB PD GetDataN Reads a word 16 bit from the specified position in the input 3 72 buffer 654403 3 65 PHCENIX CONTACT FL IL 24 Table 3 8 Driver software macros Macro Task Page IB_PD_GetDataNHiByte Reads the high order byte bit 8 to 15 of a word from the 3 72 input buffer IB_PD_GetDataNLoByte Reads the low order byte bit 0 to 7 of a word from the input 3 72 buffer IB PD GetBytePtrHiByte Returns the address of a word starting with the high order 3 73 byte bit 8 to 15 IB PD GetBytePtrLoByte Returns the address of a word starting with the low order byte 3 73 bit O to 7 IB PD SetLongDataN Writes a double word 32 bit to the output buffer 3 73 IB PD SetDataN Writes a word 16 bit to the output buffer 3 74 IB PD GetDataNHiByte Writes the high order byte bit 8 to 15 of a word to the output 3 74 buffer IB PD GetDataNLoByte Writes the low order byte bit O to 7 of a word to the output 3 74 buffer IB PD GetBytePtrHiByte Returns the address of a
199. ration storage transport 5g 150 Hz Criterion A Free fall according to IEC 60068 2 32 1 m 3 28 ft Conformance With EMC Directives Developed according to IEC 61000 6 2 IEC 61000 4 2 ESD Criterion B 6 kV contact discharge 6 kV air discharge without labeling field 8 kV air discharge with labeling field in place IEC 61000 4 3 radiated noise immunity Criterion A IEC 61000 4 4 burst Criterion B IEC 61000 4 5 surge Criterion B 61000 4 6 conducted noise immunity Criterion A IEC 61000 4 8 noise immunity against Criterion A magnetic fields EN 55011 noise emission Class A 6 10 PHCENIX 654403 CONTACT Technical Data 61 Ordering Data Description Order Designation Order No Ethernet Inline bus coupler with connector and labeling FL IL 24 BK B PAC 28 62 327 field Connector with color print IB IL SCN 8 CP 27 27 608 Labelling field IB IL FIELD 8 27 27 50 1 End clamp E UK 1201 442 Zack Quick marker strip ZBFM 6 see CLIPLINE Factory Manager network management software FL SWT 28 31 04 4 FL SNMP OPC gateway software for information FL SNMP OPC SERVER 28 32 16 6 exchange between SNMP and OPC FL OPC SNMP AGENT 28 32 179 OPC server IBS OPC SERVER 27 29 127 CD ROM with user documentation in pdf format driver CD FL IL 24 BK 28 32 06 9 software example program and OPC configurator
200. ress network ID and the user address host ID Network ID Host ID Class A 7 bit 24 bit Class B 14 bit 16 bit Class C 21 bit 8 bit Class D 28 bit multicast identifier Class E 27 bit reserved IP addresses can be represented in decimal octal or hexadecimal notation In decimal notation bytes are separated by dots dotted decimal notation to show the logical grouping of the individual bytes 654403 PHCENIX 2 5 FL IL 24 BK B PAC UM E 2 4 1 Possible Address Combinations 7 bits 24 bits 2 e 0 0 0 0 127 255 255 255 14 bits 16 bits 5 12800 afo 128 0 0 0 191 255 255 255 21 bits 8 bits cr 1920 0 Hosp 192 0 0 0 223 255 255 255 28 bits Class D i 224 0 0 0 239 255 255 255 Identifier for multicast group 27 bits Fee Class E 240 0 0 0 247 255 255 255 Reserved for future applications Figure 2 1 X Structure of IP addresses Special IP Addresses for Special Applications Certain IP addresses are reserved for special functions The following addresses should not be used as standard IP addresses 2 6 PHCENIX 654403 CONTACT Startup Operation 127 x x x Addresses The class A network address 127 is reserved for a loop back function on all PCs regardless of the network class This loop back function may only
201. river Software Format of the T DDI DTI ACCESS ACCESS Example typedef struct USIGN16 length Amount of data to be written in bytes USIGN16 address Address in the DTI area byte address USIGN16 dataCons Desired data consistency area USIGN8 data Pointer to the data read and write T DDI DTI ACCESS UNIX Windows NT 2000 IBDDIHND ddiHnd IBDDIRET ddiRet T DDI DTI ACCESS dtiAcc USIGN8 oBuf 512 dtiAcc length 512 dtiAcc address 0 dtiAcc data oBuf dtiAcc dataCons DTI DATA BYTE oBuf 0 0x12 oBuf 1 0x34 ddiRet DDI DTI WriteData ddiHnd amp dtiAcc if ddiRet ERR_OK Error treatment 654403 PHCENIX mer CONTACT FL IL 24 Task DDI DTI ReadWriteData The DDI DTI ReadWriteData function is used to read and write process data in one call This function increases performance considerably especially when using process data services via the network because process data is read and written in a single sequence Syntax Parameters Return value The function is assigned the node handle and two pointers to T DDI DTI ACCESS data structures One structure contains the parameters for read access and the other structure contains the parameters for write access The T DDI DTI ACCESS structure corresponds to the general DDI specification A plausibility check is not carried out on the user
202. rload protection and diagnostics IB IL 24 2 inputs 4 wire termination according to Desina specification with 28 61 52 2 EDI 2 DESINA PAC electronic overload protection and diagnostics IB IL 24 DI 4 4 inputs 3 wire termination 24 V DC 27 26214 IB IL 24 DI 4 PAC 4 inputs 3 wire termination 24 V DC 28 61234 IB IL 24 DI 8 8 inputs 4 wire termination 24 V DC 27 26 227 IB IL 24 DI 8 PAC 8 inputs 4 wire termination 24 V DC 28 61247 IB IL 24 DI 8 T2 8 inputs 4 wire termination 24 V DC 28 60 439 acc to EN 61131 2 Type 2 IB IL 24 DI 8 T2 PAC 8 inputs 4 wire termination 24 V DC 28 62204 acc to EN 61131 2 Type 2 IB IL 24 DI 16 16 inputs 3 wire termination 24 V DC 27 26 230 IB IL 24 DI 16 PAC 16 inputs 3 wire termination 24 V DC 28 61250 IB IL 24 DI 16 NPN 16 inputs with negative logic 28 63517 3 wire termination 24 V DC IB IL 24 DI 16 NPN PAC 16 inputs with negative logic 3 wire connection 28 63520 24 V DC IB IL 24 DI 32 HD 32 inputs 1 wire termination 24 V DC 28 60 78 5 IB IL 24 DI 32 HD PAC 32 inputs 1 wire termination 24 V DC 28 62 835 IB IL 120 DI 1 1 input 3 wire termination 120 V AC 28 36 70 6 IB IL 120 DI 1 PAC 1 input 3 wire termination 120 V AC 2861917 IB IL 230 DI 1 1 input 3 wire termination 230 V AC 27 40342 IB IL 230 DI 1 PAC 1 input 3 wire termination 230 V AC 28 61 548 IB IL 24 DO 2 2 outputs 500 mA 4 wire termination 24 V DC 27 40 106 IB IL 24 DO 2 PAC 2 outputs 500 mA 4 wire termination 24 V DC 28 61
203. rmat n USIGN8 Pointer to the receive buffer m USIGN16 Parameter No USIGN8 Parameter value byte This macro only reads the parameter value for messages that also have parameters IB GetParaNLoByte n m This macro reads the low order byte bit O to 7 of a parameter from the specified receive buffer and converts it into Intel format n USIGN8 Pointer to the receive buffer m USIGN16 Parameter No USIGN8 Parameter value byte This macro only reads the parameter value for messages that also have parameters IB GetBytePtrHiByte n m This macro returns the address of a parameter entry starting with the high order byte bit 8 to 15 The address is USIGNG data type n USIGN8 Pointer to the receive buffer m USIGN16 Parameter No USIGNS Address of the high order byte of a parameter in the receive buffer 3 70 H N IX 654403 CONTACT Driver Software IB GetBytePtrLoByte n m Task This macro returns the address of a parameter entry starting with the low order byte bit to 7 The address is US IGN8 data type Parameters n USIGNB8 Pointer to the receive buffer m USIGN16 Parameter No Return value USIGNS Address of the low order byte of a parameter in the receive buffer 654403 PHCENIX 3 71 CONTACT FL IL 24 BK B PAC UM E Task Parameters Task Parameters Return value Task Parameters Return value 3 12 3 Mac
204. rminal that is to be monitored 3 40 P HCE 654403 Driver Software USIGN16 time Pointer to a variable which contains the desired timeout time when called If the function has been called successfully the actual timeout time is then entered in this variable The shortest value for the timeout time is 330 ms the longest value for timeout time is 65 000 ms If a shorter value is entered the error code ERR INVLD PARAM is returned and Host Checking is not activated Return value IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code Example Unix Windows NT 2000 IBDDIHND ddiHnd void CAUO0yxDlg OnButtonSetHostCheckingOn IBDDIRET ddiRet USIGN16 hcTime 1000 ddiRet ETH SetHostChecking ddiHnd amp hcTime if ddiRet ERR INVLD PARAM hcSelected time is too short 330 ms minimum UpdateData FALSE uid 3 41 CONTACT FL IL 24 BK B PAC UM E Task Syntax Parameters Return value ETH_ClearHostChecking The ETH_ClearHostChecking function deactivates the node used to monitor the client This function only receives the node handle as a parameter which is also used to activate monitoring with ETH_SetHostChecking After the function has been called successfully monitoring via this channel and for this client is deactivated Other activated
205. rols the bus terminal via the Ethernet network Using these functions firmware services can be called and started and results can be requested on the bus terminal The second group contains functions for monitoring the bus terminal and the workstation with the application program The third group contains macro functions for the conversion of data between Intel and Motorola data format Figure 3 2 illustrates the creation of an application program from the parts of the driver software 3 4 P HCE 654403 Driver Software Workstation Client Application program Library with DDI and ETHA functions Data connection Controller board Server 5225A001 Figure 3 2 Using the driver software the application program 3 3 Support and Driver Update In the event of problems please phone our 24 hour hotline on 49 52 35 34 18 88 Driver updates and additional information are available on the Internet at http www phoenixcontact com 654403 PHCENIX 3 5 CONTACT FL IL 24 Training Courses Our bus terminal training courses enable you to take advantage of the full capabilities of the connected Inline system For details and dates please see our seminar brochure which your local Phoenix Contact representative will be happy to mail to you 3 6 PHCENIX 654403 CONTACT Driver Software 3 4 Transfer of I O Data The I O data of individual Inl
206. rom the DTI for the first time using the node handle which was also used when activating monitoring Writing to or reading from the DTI via a connection or a node handle for which no monitoring is set does not 3 42 P H N IX 654403 CONTACT Driver Software therefore enable monitoring for another connection Once access has been enabled for the first time all subsequent access must be enabled within the set timeout time otherwise the NetFail signal is activated Deactivating Monitoring Monitoring is deactivated by calling the ETH_ClearDT TimeoutCtrl function or by closing the relevant DTI node using the DDI_DevCloseNode function If a connection is interrupted by the bus terminal as a result of DTI monitoring the monitoring mode for this connection is deactivated and the corresponding DDI node is closed see also ETH_SETDTITimeoutCTRL If the bus terminal detects that a connection has been interrupted without the node having been closed the NetFail signal is set This applies especially if the controlling process application program is closed with an uncontrolled action e g pressing Ctrl C and all the open data channels are closed by the operating system Status of the NetFail Signal The user can read the status of the NetFail signal using the ETH_GetNetFailStatus function In addition to the status of the NetFail signal a second parameter is returned which indicates the reason if the NetFail signal has be
207. ros for Converting Input Data The IBS_MACR H file contains macros for converting double words words and bytes from Motorola to Intel format Addressing is always word oriented here IB PD GetLongDataN n m This macro reads a double word 32 bit from the specified position in the input buffer and converts it into Intel format The word index in the input buffer is used as a position The macro reads the double word starting from the specified word address over two words n USIGNB m USIGN16 Pointer to the input buffer Word number IB PD GetDataN n m This macro reads a word 16 bit from the specified position in the input buffer and converts it into Intel format if necessary n USIGNS Pointer to the input buffer m USIGN16 Word number USIGN 16 Process data 16 bit IB PD GetDataNHiByte n m This macro reads the high order byte bit 8 to 15 of a word from the input buffer and converts it into Intel format n USIGNS Pointer to the input buffer m USIGN16 Word number USIGN8 Process data 8 bit IB PD GetDataNLoByte n m Task This macro reads the low order byte bit O to 7 of a word from the input buffer and converts it into Intel format Parameters n USIGNe Pointer to the input buffer 3 72 P H N IX 654403 CONTACT Driver Software Return value Task Parameters Return value Task Parameters Return value m USIGN16 Word number USIGN8 Pro
208. s Data Watchdog The process data watchdog can only be deactivated if the bus terminal is in INIT state For switching off the value of timeout is set to Zero The required fault response mode can also be set to the object ID 0x2277 using the web based management or by writing to the Modbus register 2002 or using the Set Value 0x0750 service Status Diagram of the Process Data Watchdog Status INIT Write OK ETH ClearNetFail Watchdog Timeout 0 Reque gt INTERBUS running RER Write Watchdog Timeout Expires Set Net Fail Fault Response 61560029 Figure 3 11 Status diagram of the process data watchdog 3 38 654403 PHCENIX CONTACT Driver Software 3 8 2 Connection Monitoring Host Checking Application Connection monitoring can be used to determine whether there is still a connection between the bus terminal server and the computer client and whether this computer responds to requests With connection monitoring it is also possible to detect the following error causes Cable broken not connected or short circuited Transceiver faulty Errors or faults in the Ethernet adapter of the bus terminal or in the client System crash of the client workstation Error in the TCP IP protocol stack Activating Monitoring The ETH SetHostChecking function activates the mode for monitoring the connection and the status o
209. s TCP Protocol The response to the Read Multiple Registers command has the following format Table 5 6 Answer to Read Multiple Registers Byte No Meaning BYTE 0 Function code 3 BYTE 1 Byte Count of the response Byte Count 2 x Word Count in the command BYTE 2 1 Register values If the command accesses an invalid offset or receives an invalid length an exception response with the following format is output Table 5 7 Answer to Read Multiple Registers Byte No Meaning BYTE 0 Function code 0x83 BYTE 1 Exception response 2 5 5 1 1 Example for Read Multiple Registers Register table offset 0 and Word Count 2 returns 11 32 Register table offset 575 and Word Count 2 returns Q3057 3072 1 Register table offset 1024 and Word Count 64 returns the error table Every combination of the register table offset and the Word Count that have access onto the offets gt 767 und lt 1024 results in an exception response An exception response is also created when trying to read the erorr table and to enter a register table offset gt 1024 or a Word Count lt gt 64 The special register 1280 2004 can only be read when the Word Count equals one 654403 PHGNIX 5 11 CONTACT FL IL 24 BK B PAC UM E 5 5 2 X Write Multiple Registers This command reads 16 bit words from 1 to 100 in the Modbus Register table Only that part of the Mo
210. ser can read the set NetFail mode from the structure If there are no additional parameters for this mode this is indicated by the structure component numOfBytes which contains the value zero in this case IBDDIRET IBDDIFUNC ETH GetNetFailMode IBDDIHND nodeHd T ETH FAIL MODE netFailModelnfo IBDDIHND nodeHd Node handle of a controller board from which information on the set NetFail mode is to be read T ETH NET FAIL MODE netFailModelnfo Pointer to a T FAIL MODE data structure If the function is called successfully the parameters of the NetFail mode set on the controller board as well as the mode itself are entered in this structure typedef struct USIGN16 mode NetFail mode USIGN16 numOfBytes Size of the parameter block in bytes VOID miscParamPtr Parameters for the relevant NetFail mode ETH NET FAIL MODE define ETH_NF_STD_MODE 0 define ETH_NF_ALARMSTOP_MODE 1 define ETH_NF_HOLD_LAST_STATE_MODE 2 The function prototypes the type definition of the data structure and the symbolic constants be found in the IOCTRL H file 654403 PHCENIX em CONTACT FL IL 24 BK B PAC UM E 3 9 IN Process Data Monitoring Functions that automatically monitor the process IN data area for changes can be used to reduce the load on the Ethernet network In systems in which input signals only change slowly or rarely change the same process data is of
211. service request Parameter_Count Number of subsequent words 000155 Always 1 parameter word Used_Attributes The parameter is a 16 bit field in which every bit corresponds to an attribute Set the corresponding bits to 1 on the attribute that you want to read Settings for the Used_Attributes parameter Bit 0 Device number Bit 1 Device code 654403 FL IL 24 BK PAC UM E Syntax Complete_Read_Configuration_Confirmation 830Bnex Positive message Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 7 0001 hex Word 8 nee 1 device nth device Negative message Word 1 Word 2 Word 3 Word 4 Bit n 0 Key Code 830BhexMessage code of the service confirmation Parameter Count Number of subsequent words with a positive message value depends on the number of entries and the number and type of attributes that you want to read with a negative message 0002hex 2 parameter words Result Result of the service processing 0000 Indicates a positive message The controller board executed the service successfully 4 30 PHCENIX 654403 CONTACT Firmware Services Add_Error_Info More_Follows Frame_Reference Used_Attributes Start_Entry_No Entry_Count Configuration_Entry Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the servi
212. sible to write data via Modbus TCP 5 20 PHCENIX 654403 CONTACT Modbus TCP Protocol 5 5 11 Write Multiple Coils This command writes 1 up to 800 bits into the Modbus Coil table The Write Multiple Coils command has the following format Table 5 30 Write Multiple Coils Byte No Meaning BYTE 0 Function code OxOF BYTE 1 2 Coil table offset BYTE 3 4 Bit Count BYTE 5 Byte Count BYTE 6 B 5 Bit values the least significant bit is the first coil The response to the Write Multiple Coils command has the following format Table 5 31 Response to Write Multiple Coils Byte No Meaning BYTE 0 Function code OxOF BYTE 1 2 Coil table offset as in the command BYTE 3 4 Bit Count as in the command If the command uses an invalid offset the following exception response is generated Table 5 32 Exception response to Write Multiple Coils Byte No Meaning BYTE 0 Function code Ox8F BYTE 1 Exception response 2 5 5 11 1 Example for the Write Multiple Coils command Coil table offset 0 and Bit Count 2 with a value of 3 sets coils Q1 and 02 Coil table offset 0 and Bit Count 2 with a value of 0 sets back coils Q1 and Q2 5 21 PHCENIX CONTACT FL IL 24 BK B PAC UM E 5 5 12 Read Write Register This command reads 1 up to 125 words from a Modbus register table and writes 1 up t
213. te Configuration 4 32 030Enex Control Parameterization 4 8 0701 Start Data Transfer 4 42 0710 Create Configuration 4 33 0711 Activate Configuration 4 36 1303 Alarm Stop 4 44 4 2 Notes on Service Descriptions Use of The use of a service involves sending a service request and evaluating the services service confirmation The codes of a service request and the subsequent service confirmation only differ in binary notation in bit 15 Bit 15 of a service confirmation is always set Thus in hexadecimal notation the code of a service confirmation is always 8000hex higher than the code of the service request which it follows Example Request Start Data Transfer Start Data Transfer Request 0701 4 4 654403 CONTACT Firmware Services Structure of a service description Task Prerequisite Confirmation Start Data Transfer Confirmation 870155 0701 8000hex Parameter Service executed Result 0000 successfully Parameter Error during service execution Result 0000 6 The service confirmation indicates the successful execution of a service via a positive message and provides data if requested The service confirmation indicates an error that occurred during service execution via a negative message The Result parameter of the service confirmation shows if the service was executed successfully Result parameter 0000
214. ten transmitted in successive read cycles Transmission of the same data loads the network and the client user workstation but does not provide any additional information That is why it is possible to only transmit process IN data to the client if this data has changed The user now has the option to define an area to be monitored by the controller board This area is read by the controller board firmware cyclically and compared with a reference image of the process data The comparison of the defined area with the process image of the reference data and the transmission of the data to the relevant client takes place within a period of 222 ms If it is established that the data that has been read differs from the reference image the read data is automatically sent to the relevant client and entered as the new reference image In addition areas in which changes are not taken into account can be specified This provides an easy option for masking out the low order bits of an analog input that change frequently The modified data is sent by an unconfirmed service 3 56 P H N IX 654403 CONTACT Driver Software Task Function Syntax ETH ActivatePDInMonitoring The ETH ActivatePDInMonitoring function activates the mode for monitoring the process IN data for potential changes This mode can only be activated once on each controller board The function is assigned a valid node handle for a DTI data channel and a poi
215. terminal can respond appropriately By default upon delivery the watchdog is activated with 500 ms timeout The first write process activates the process data watchdog the next write process is exptected during timeout default 500 ms During error free operation the write process is realized during timeout and the watchdog is restarted triggered If there is no triggering during timeout an error occured Two responses follow The selected fault response mode is executed and the net fail signal is set The reason for setting the NetFail signal is listed in the reason code see list on page 3 36 For safety reasons the user cannot stop the watchdog once it has been activated In case the user terminates the controlling application there is no watchdog triggering when timeout has expired the NetFail signal is set and the selected fault response mode is executed The NetFail signal can be acknowledged using the web based management or using the ETH ClrNetFailState command and the fault response Mode is reset 654403 PHCENIX idi CONTACT FL IL 24 IS 3 8 1 2 Configuring the Process Data Watchdog and the Fault Response Modes Process data watchdog timeout can be configured from 200 to 65 000 ms Timeout can be set to the object ID 0x2293 using the web based management or by writing to the Modbus register 2000 or using the Set Value 0x0750 service Deactivating the Proces
216. tes process IN data monitoring The function is only assigned the node handle as a parameter which is also used to activate monitoring with ETH ActivatePDInMonitoring Syntax IBDDIRET IBDDIFUNC DeactivatePDInMonitoring IBDDIHND nodeHd Parameters IBDDIHND nodeHd Node handle DTI for the controller board for which process data monitoring is to be deactivated Return value IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code IS 3 10 Notification Mode General The notification mode enables messages received in the MPM e g a message from the INTERBUS controller board to be made available to the application program immediately This reduces the load on the network and the computer because messages do not have to be scanned cyclically Data is only transmitted via the network if there is actually a message in the MPM or a specified timeout time has elapsed 3 60 PHCENIX 654403 CONTACT Driver Software Notification Mode Task A feature of notification mode is that the message is awaited on the controller board DDI RcvMessage call waits on the controller board until there is a message or the preset timeout time has elapsed No other requests can be sent via the channel during this period Thus the data channel is practically blocked When the notification mode is activated the timeout time is entered in the T_ETH_N
217. th sensors and connect the shielding as described above to the shield connector 2 Usea thin cable for the connection of each sensor and connect the shielding of both cables together to the shield connector 3 Usethe standard connector IB IL SCN 8 without shield connector Twist the braided shield of each cable and place it on one of the terminal points to be used for FE connection You should only use this option if the cross section is too large and the first two methods are not possible 1 15 2 2 Connecting an Analog Output Module IB IL AO IS e Connect the shielding via the shield connector see Section 1 16 2 Connecting Shielded Cables Using the Shield Connector e When connecting the shielding with the FE potential ensure a large surface connection Danger of creating ground loops The shielding must only be directly connected with the ground potential at one point 654403 PHCENIX 1 59 CONTACT FL IL 24 BK B UM E For cable lengths exceeding 10 meters 32 81 ft the actuator side should always be isolated by means of an RC element The capacitor C should typically have values of 1 nF to 15 nF The resistor R should be at least 10 MO A B 55200042 Figure 1 34 Connection of actuators signal cables gt 10 m 32 808 ft A Module side B Actuator side 1 60 PHCENIX 654403 CONTACT FL IL 24 BK B PAC 1 16 Connecting Cables Both shielded
218. the entries only consist of the device code enter the value 000246 for the Used Attributes parameter bit 1 is set Start Entry No Number of the first device for which attributes are to be transmitted Entry_Count Number of devices for which attributes are to be transmitted Configuration_Entry Attribute values of the individual devices to be transmitted according to their order in the physical bus configuration see syntax on page 4 17 Syntax Configuration Entry Attribute Word x Word x 1 Device Code Bit poe 0 Attributes Bus_Segment_No Number of the bus segment where the device is located Value range 01 654403 PHGNIX 4 17 CONTACT FL IL 24 BK PAC UM E Position Physical location in the bus segment Value ranges OOhex 3Fhex 63gec for an Inline station The Bus_Segment_No and Position parameters together form the device number Length_Code Length code The length code refers to the address space required by the device in the host ID_Code ID code The ID code indicates the device type It is printed as Module Ident in decimal notation on the modules The Length Code and ID Code parameters together form the device number Syntax Load Configuration Confirmation 8307 Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit E 0 8307hex Message code of the servic
219. the function The nodeHd parameter specifies the bus terminal in the network to which the request is to be sent The node handle must also be assigned to a process data channel otherwise an appropriate error message is generated by the bus terminal IBDDIRET IBDDIFUNC DDI DTI ReadData IBDDIHND nodeHd T DDI DTI ACCESS dtiAcc IBDDIHND nodeHd Node handle DTI for the connection from which data is to be read The node handle also determines the bus terminal which is to be accessed T DDI DTI ACCESS dtiAcc Pointer to a T DDI DTI ACCESS data structure This structure contains all the parameters needed for access IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code typedef struct USIGN16 length Amount of data to be read in bytes USIGN16 address Address in the DTI area byte address USIGN16 dataCons Desired data consistency area USIGN8 data Pointer to the data read and write T DDI DTI ACCESS 3 24 P HCE 654403 Driver Software Example UNIX Windows NT 2000 IBDDIHND ddihnd IBDDIRET ddiRet DDI DTI ACCESS dtiAcc USIGN8 iBuf 512 dtiAcc length 512 dtiAcc address 0 dtiAcc data iBuf dtiAcc dataCons DTI DATA BYTE ddiRet DDI DTI ReadData ddiHnd amp dtiAcc if ddiRet ERR OK Error treatment 654403 PHCE
220. the local bus configuration OPC Communication Configure the OPC server from Phoenix Contact for this type of bus terminal using the project file that was created using this software The project file and an OPC server provide the application program or the visualization with direct access to the process data for the bus configuration 2 20 PHCENIX 654403 CONTACT Section 3 This section informs you about the driver software the example program Driver Sotware cnr eb Rev bt duae dake doe 3 3 3 1 Documentation 3 3 3 1 1 Hardware Software User 3 3 32 Software Structure 3 3 3 2 1 Ethernet Inline Bus Terminal Firmware 3 4 3 2 2 Driver Software Ecserin tiku enuen aai 3 4 3 8 Support and Driver 3 5 34 Transferotl O D ata iecur rete elei itia rns 3 7 3 4 1 Position of the Process Data Example 3 8 3 5 Startup Behavior of the Bus 3 9 3 5 1 Plug amp Play 44222111 3 9 3 5 2 Expert 3 10 3 5 3 Possible Combination of Modes 3 10 3 5 4 Startup Diagrams of the Bus Coupler
221. tial and Data Routing An important feature of the INTERBUS Inline and Ethernet Inline bus coupler product ranges is their internal potential routing system The electrical connection between the individual station devices is created automatically when the station is installed When the individual station devices are connected a power rail is created for the relevant circuit This is created mechanically through the interlocking of knife and featherkey contacts on the adjacent modules A special segment circuit eliminates the need for additional external potential jumpering to neighboring modules Two independent current circuits are realilzed within one station the logic circuit and the I O circuit b 9 8 61560017 Figure 1 15 Potential and data routing 654403 PHCENIX 1 27 CONTACT FL IL 24 BK B UM E Table 1 11 Potential jumper see Figure 1 15 No Function Meaning 1 FE FE Functional earth ground 2 SGND SGND Ground of segment and main supply 3 24V Supply for main circuit if necessary with overload protection 4 24V Us Supply for segment circuit if necessary with overload protection This jumper does not exist in power levels 120 230 V AC 5 LGND UL Ground of communications power and I O supply for analog modules 6 24 V UANA I O supply for analog modules 7 7 5 Ui Supply for module electronics 9 FE spring FE contact to DIN rail
222. tion 1 in Figure1 8 5520A075 Figure1 8 Function identification The following colors indicate the functions Table 1 10 Module color coding Color Function of the Module Light blue Digital input 24 V DC area Pink Digital output 24 V DC area Blue Digital input 120 230 V AC area Red Digital output 120 230 V AC area Green Analog input Yellow Analog output Orange Fieldbus coupler special function modules Black Power terminal segment terminal Connector The color coding of the terminal points is described on page 1 17 identification 1 20 PHOENIX 654403 CONTACT FL IL 24 Labeling terminal point numbering Slot connector Terminal point Additional labeling Terminal point numbering is illustrated using the example of an 8 slot module 1 2 4 0 i 5520A035 Figure1 9 Terminal point numbering The slots connectors on a base are numbered consecutively 1 in Figure1 9 This numbering is not shown on the actual module The terminal points on each connector are marked X Y X is the number of the terminal point row on the connector It is indicated above the terminal point row 2 in Figure1 9 Y is the termi
223. tion 1 16 2 on page 1 63 1 18 1 Connection Methods for Sensors and Actuators Most of the digital I O modules in the Inline product range permit the connection of sensors and actuators in 2 3 and 4 wire technology 1 68 H 654403 FL IL 24 BK B PAC Because of the different types of connectors a single connector can support the following connection methods 2 sensors or actuators 2 3 or 4 wire technology 4 or actuators in 2 or 3 wire technology 2 or actuators in 2 or 3 wire technology with shielding for analog sensors or actuators B EN 654403 PHCENIX 1 69 CONTACT FL IL 24 BK B UM E 1 18 2 Examples of Connections for Digital Modules Various connection options are described below using 24 V DC modules as an example For the 120 V 230 V AC area the data change accordingly A connection example is given in each module specific data sheet Table 1 20 Overview of the connections used for digital input modules Connection Representation 2 wire 3 wire 4 wire in the Figure Sensor signal IN IN X X X Sensor supply Us Us 24 V X Ground GND GND 1 X Ground FE shielding FE A X X Used Not used Table 1 21 Overview of the connections used for digital output modules Connection Representation 2 wire 3 wire 4 wire in the Figure Actuator si
224. tive diode Serial diode in the lead path of the power supply unit in the event of an error only a low current flows In the event of an error the fuse in the external power supply unit does not trip Ensure protection of 2 A by fuses through the external power supply unit Nominal value 24 V DC Tolerance 15 20 according to EN 61131 2 Ripple 5 Permissible range 19 2 V to 30 V Minimum current consumption 92 mA at nominal voltage At no load operation i e Ethernet connected no local bus devices are connected bus inactive Maximum current consumption at nominal voltage 1 5A Loading the 7 5 V communications power with 2 A the 24 V analog voltage with 0 5 A 654403 PHCENIX FL IL 24 BK B UME 24 V Module Supply Communications Power Potential Routing Nominal value 7 5 V DC Tolerance 5 Ripple 1 5 Maximum output current 2 A DC observe derating Safety equipment Electronic short circuit protection Analog Supply Potential Jumper Nominal value 24 VDC Tolerance 15 20 Ripple 5 Maximum output current 0 5 A DC observe derating Safety equipment Electronic short circuit protection Derating of the Communications Power and the Analog Terminal Supply 100 90 80 70 60 50 40 30 P 0 5 10 15 20 25 30 35 40 45 50 55 To 61550009 P Loading
225. um number of control structures is determined when the library is compiled and cannot subsequently be modified In Windows NT 2000 there are 8 control structures per device with a maximum of 256 If all the control structures are occupied another data channel cannot be opened In this case if DD DevOpenNode is called it is rejected locally with the appropriate error message IBDDIRET IBDDIFUNC DDI_DevOpenNode CHAR devName INT16 perm IBDDIHND CHAR devName Pointer to a string with the device name INT16 perm Access rights to the data channel to be opened This includes read write and read write access IBDDIHND nodeHd Pointer to a variable for the node handle MXI or DTI IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code 654403 PHCENIX v CONTACT FL IL 24 Constants for the perm parameter Example Task IS Syntax Parameters Return value DDI READ 0x0001 Read only access DDI WRITE 0 0002 Write only access DDI RW 0x0003 Read and write access Windows NT 2000 UNIX IBDDIHND ddiHnd IBDDIRET ddiRet ddiRet DDI DevOpenNode IBETHOIN1 D DDI RW amp ddiHnd if ddiRet ERR OK Error treatment return DDI DevCloseNode If a data channel is no longer needed it can be closed using the DDI DevCloseNode function
226. uration Reference configuration Set station to RUN state Vv Station in Stop m RUN state Fale ON PESO Fail OFF PP ON 61650025 Standard mode expert and P amp P mode deactivatetd P amp P mode deactivated expert mode activated Figure 3 7 Power Up Read reference configuration Station in READY state Display 61560024 P amp P mode deactivated expert mode activated 654403 9H CONTACT FL IL 24 BK B PAC UM E P amp P mode activated expert mode activated Read connected configuration Operable configuration Configuration Reference configuration Set station to RUN state stop Station in UN state Fail ON PP OFF Fail OFF PP OFF e seoo03 Figure 3 8 P amp P mode activated expert mode deactivated P amp P mode activated expert mode deactivated Read connected configuration Operable configuration Save retentively as reference configuration Station in READY state Fail OFF PP ON Stop Fail ON PP OFF 61560026 Figure 3 9 P amp P mode activated expert mode activated 3 12 H 654403 Driver Software 3 5 5 Changing and Starting a Configuration in P amp P Mode SEES neers The following steps must be carried out when changing an existing configuration Switch the power supply off Change the configuration
227. vel Signal Modules 1 24 1 10 Electrical Potential and Data 1 27 1 11 Circuits Within an Inline Station and Provision of the Supply Voltages 2 444000 1 29 1 11 1 Supply of the Ethernet Bus Coupler 1 30 1 11 2 Logic Circuit UL LL 1 30 1 11 3 Analog Circuit UANA ecce scc LS Ete 1 31 1 11 4 Main Circuit Uy scc eos ccc Dade UE E 1 32 1 11 5 Segment Circuit 1 33 1 12 Voltage Concept ssssssssssssseeeeeeneeeenennnn nnns 1 35 1 13 Diagnostic and Status 1 42 1 13 1 LEDs on the Ethernet Bus Coupler 1 42 1 13 2 Supply Terminal Indicators 1 44 1 13 3 Input Output Module Indicators 1 46 1 13 4 Indicators on Other Inline Modules 1 47 654403 PHOENIX i CONTACT FL IL 24 BK B UME 1 14 Mounting Removing Modules and Connecting Cables 1 48 1 14 1 Installation Instructions 2 2 2 1 1 48 1 14 2 Mounting and Removing Inline Modules 1 48 ETAS MOUNTING ioco trcs a d teo tits 1 49 1 14 4 Remowval sa ar ne i En aiea nennen 1 51 1 14 5 Replacing a Fuse eee 1 53 1 15 Grounding an Inline Station sese 1 55 1 15 1 Shi
228. ware Services XXXXhex Indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed Add_Error_Info Additional information on the error cause 654403 PHCENIX 4 35 CONTACT FL IL 24 BK PAC UM E Task Prerequisite 4 3 11 Activate Configuration Service This service enables the controller board to check the configuration data of the configuration frame for conformance with the currently connected configuration address overlaps need to be checked If no errors are detected the controller board activates this configuration frame and runs ID cycles at regular intervals The number of the configuration frame is indicated to the controller board by the Frame Reference parameter If you want to activate a configuration frame another configuration frame cannot be active at the same time The Deactivate Configuration is not supported Syntax Activate Configuration Request 0711 Word 1 Word 2 Word 3 Bit VO 0 Code 0711 Command code of the service request Parameter_Count Number of subsequent words 0001hex 1 parameter word Frame_Reference 0001 gne 4 36 PHCENIX 654403 CONTACT Firmware Services Syntax Activate_Configuration_Confirmation 871 Thex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word
229. words 2 gt 8 lt PD_IN gt PD OUT word 1 gt 0 lt PD_OUT gt PD OUT word 2 gt 0 lt PD_OUT gt IL MODULE This area is used by all terminals with output data The use of bits is identical with the use of PD IN 2 5 5 2 Validity of Documentation The validity of data is identical with the validity via DDI or OPC access 2 5 5 3 Error in an Inline Station If the FL IL 24 BK B PAC does not configure the connected Inline terminals correctly the process data are listed in the XML file as follows lt xml version 1 0 encoding ISO 8859 1 IDOCTYPE IL STATION SYSTEM processdata dtd gt IL STATION IL BUS TERMINAL TERMINAL gt IL 24 BK B PAC TERMINAL gt 2 14 PHCENIX 654403 CONTACT Startup Operation lt NAME gt EL IL 24 BK B PAC lt NAME gt lt IP_ADDRESS gt 172 16 27 37 lt IP_ADDRESS gt lt MODULE_NUMBER gt 0 lt MODULE_NUMBER gt lt DIAGNOSTIC_STATUS_REGISTER gt 132 lt DIAGNOSTIC_STATUS_REGISTER gt lt DIAGNOSTIC_PARAMETER_REGISTER gt 65535 lt DIAGNOSTIC_PARAMETER_REGISTER gt lt IL_BUS_TERMINAL gt IL BUS IL BUS IL STATION The values of the diagnostic status and the diagnostic parameter register indicate the error cause The number of connected terminals is Zero thus the area IL BUS is empty In the event of a bus error the process data are invalid because only internal values are indicated however not the values on the INTER
230. y and functional earth ground connector MAC address in clear text and as a barcode Ethernet interface twisted pair cables in RJ45 format Two FE contacts for grounding the bus coupler using a DIN rail on the back of the module Ethernet LED status and diagnostic indicators our won 654403 PHCENIX 15 CONTACT FL IL 24 BK B UM E 1 3 Local Status and Diagnostic Indicators Table 1 2 Local Status and Diagnostic Indicators Des Color Status Meaning Electronics module UL Green ON 24 V supply 7 V communications power interface supply present OFF 24 V supply 7 V communications power interface supply not present UM ON 24 V main circuit supply present OFF 24V main circuit supply not present US Green ON 24 V segment supply is present OFF 24 V segment supply is not present Ethernet Port PP Green ON Plug amp play mode is activated OFF Plug amp play mode is not activated FAIL Red ON The firmware has detected an error OFF The firmware has not detected any error 100 Green ON Operation at 100 Mbps if LNK LED active OFF Operation at 10 Mbps if LNK LED active XMT Green ON Data telegrams are being sent OFF Data telegrams are not being sent RCV Yellow ON Data telegrams are being received OFF Data telegrams are not being received LNK Green ON Physical network connection ready to operate OFF Physical n
231. y on BootP Requests Enter the MAC address It can be found on the sticker on the front of the housing Save the configuration settings and restart the device power up The device now sends another BootP request and receives the specified IP parameters from the BootP server 2 4 H 654403 Startup Operation 2 4 Selecting IP Addresses The IP address is a 32 bit address which consists of a network part and a user part The network part consists of the network class and the network address There are currently five defined network classes classes A B and C are used in modern applications while classes D and E are hardly ever used It is therefore usually sufficient if a network device only recognizes classes A B and C With binary representation of the IP address the network class is represented by the first bits The key factor is the number of ones before the first zero The assignment of classes is shown in the following table The empty cells in the table are not relevant to the network class and are already used for the network address Bit 1 Bit 2 Bit 3 Bit4 Bit 5 Class A 0 Class B 1 0 Class C 1 1 0 Class D 1 1 1 0 Class E 1 1 1 1 0 The bits for the network class are followed by those for the network address and user address Depending on the network class a different number of bits are available both for the network add
232. ys have the same number of output and input words An AO 2 also has two input channels and an AI 2 also has tow output channels This area is used by all terminals that occupy input data The number of process data words depends on the terminal type Example Inline terminal with two active inputs IL MODULE number 1 gt MODULE TYPE DI MODULE TYPE PD CHANNELS22 PD CHANNELS PD WORDS 1 PD WORDS PD IN word 1 gt 3 lt PD_IN gt IL MODULE b Inline terminal with two digital inputs and only the second input is active IL MODULE number 3 gt MODULE TYPE DIc MODULE TYPE PD 5 gt 2 lt CHANNELS 654403 PHCENIX 219 CONTACT FL IL 24 BK B PAC UM E PD OUT PD WORDS21 PD WORDS PD IN word 1 gt 2 lt PD_IN gt lt MODULE Inline terminal with 16 digital inputs and the 13th and the 14th input is active IL MODULE number 7 gt MODULE TYPE gt DI lt MODULE TYPE PD 5 gt 16 lt CHANNELS PD WORDS 1 PD WORDS PD IN word 1 gt 12288 lt PD_IN gt IL MODULE The input word returns the value 12288 212 213 d Inline terminal with two analog inputs only the first channel being active 14970 lt IL_MODULE number 10 gt lt MODULE_TYPE gt Al lt MODULE_TYPE gt lt PD_CHANNELS gt 2 lt PD_CHANNELS gt lt PD_WORDS gt 2 lt PD_WORDS gt lt PD_IN word 1 gt 14970 lt PD_IN gt PD IN

User Manual FL IL 24 BK-B UM E - Documentazione Software Marel

Contents

Download Pdf Manuals

Related Search

Related Contents