Home

User Manual FL IL 24 BK-PAC UM E - Configurators

1. 55200052 Figure 1 28 module indicators Diagnostics The following states can be read from the I O modules Table 1 18 Diagnostic LED of the I O modules LED Color State Description of the LED States D Green ON Local bus active 1 Flashing 0 5 Hz Communications power present local bus not slow active 2 Hz Communications power present I O error medium 4 Hz Communications power present 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 615605 PHCENIX FL IL 24 BK PAC UM E Table 1 19 Status LEDs of the I O terminals LED Color State Description of the LED States 1 2 3 4 Yellow ON Relevant input output set 2 OFF Relevant input output not set Assignment Between Status LED and Input Output 1 12 4 teri age hn Indicators on Other Inline Modules 1 46 PHCENIX CONTACT FL IL 24 BK PAC au DIN rail End clamp CLIPFIX 1 43 Mounting Removing Modules and Connecting Cables 1 13 1 Installation Instructions 1 13 2 Mounting and Removing Inline
2. INCLUDE FILES AND CONSTANT DEFINITION Hinclude lt stdio h gt Hinclude lt stdlib h gt Hinclude lt time h gt include lt string h gt BORK KR KKK RR RR RR KR RK RR RR KR RR RR KK RRR RR RR KK RR RR e e ke ke k Include files for the CLIENT library Windows version BR KKK KR KR RK k k k KK k k RR RR RK RR k k k RR k k RR k k k kkk include ethwin32 h define MAX MSG LENGTH 100 define MXI_RCV_TIMEOUT 9 RR KK kkk kkk RR kk kk kk kk k k k k kkk k k kkk KK KK GLOBAL VARIABLES RR KR KR KR kkk kkk kkk kkk kkk kk kkk 7 char OPEN MXI 20 IBETH char OPEN DTI 20 IBETH IBDDIHND mxiHnd dtiHnd T DDI MXI ACCESS mxiAcc T DDI DTI ACCESS dtiAcc T DDI DTI ACCESS readAcc BORK KR RK k k k RR RK RR KK RR RR RR RK KR KR RR KKK k k k k k k k k k k k k k k k ke ke ke CreateConnection FUNCTION Parameters NONE Return value INTEGER 0 for OK 111 for error S EEK k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k k kk k k kk k int CreateConnection void IBDDIRET ret Mailbox connection ret DDI DevOpenNode OPEN MXI DDI RW amp mxiHnd if ret ERR OK printf Yn TEST ABORTED printf nError when creating
3. FL IL 24 BK PAC Configuration Reset Fault Mode Configuration Last State Fault Mode Status Output table Real output Output table Real output Power up 40 404 404 40 First read access 0 plus the new Output table 0 plus the new Output table output table after values values power up Operating 0 plus the sum of Output table 0 plus the sum of Output table all new values all new values Example A station consists of 3 I O modules a 16 bit analog output module AO a 16 bit discrete output module DO 16 and 2 bit discrete output module DO 2 After a power up all outputs are set to 0 Module AO DO 16 DO2 Value 0x0000 0x0000 0x0000 If 0x0200 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 This is the O 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 the following values are output Module AO DO 16 DO2 Value 0x0010 OxACDC 0x0001 This is the O plus the sum of all new values state 615605 PHCENIX 6 27 CONTACT FL IL 24 BK PAC UM E Table 6 47 6 9 2 Connection Monitoring Table This table shows the output values after the connection monitoring or the process data watchdog detected a fault such as a disconnection or
4. Table 3 10 Driver software messages Code Error Message Cause Page 0000 ERR OK The function was executed successfully 3 69 0085454 ERR INVLD NODE HD Invalid node handle specified 3 70 008644 ERR INVLD NODE STATE Node handle of a data channel that is already closed 3 70 specified 0087hex ERR NODE NOT READY Desired node not ready 3 70 008844 ERR WRONG Incorrect node handle 3 70 008944 ERR NOT READY Local bus master not ready yet 3 71 008Ahex ERR INVLD PERM Access type not enabled for channel 3 71 008 ERR INVLD Utility function is not supported by driver Version 0 9 3 71 008Dhex ERR INVLD Command contains invalid parameter 3 71 0090hex ERR NODE NOT PRES Node not available 3 72 0091454 ERR INVLD DEV NAME Unknown device name used 3 72 009244 ERR NO MORE HNDL Device driver resources used up 3 72 0096 ERR AREA EXCDED Access exceeds limit of selected data area 3 75 009745 ERR INVLD DATA CONS Specified data consistency is not permitted 3 75 009Ahex ERR MSG TO LONG Message or command contains too many parameters 3 73 009Bhex ERR NO MSG No message present 3 73 009Chex ERR NO MORE MAILBOX No further mailboxes of the required size free 3 73 009Dhex ERR SVR USE Send vector register in use 3 73 009Ehex ERR SVR TIMEOUT Invalid node called 3 74 009Fhex ERR AVR TIMEOUT Invalid node called 3 74 3 68 615605
5. 4 4 2 Alarm Stop Service hena eero pt 4 5 Diagnostic Services 4 5 1 Get Error Info Service 4 5 2 Get Version Info Service 2 4 47 4 6 Error Messages for Firmware Services 4 50 4 6 1 OT ML Tm 4 50 4 6 2 Positive 4 4 51 4 6 3 Error Messages dienten dh ted pte edet 4 51 615605 PHCENIX 4 1 CONTACT FL IL 24 BK PAC UM E 4 2 PHCENIX 615605 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 Not using the services as specified in the table may cause the firmware to behave as follows service is not permitted in this mode and is rejected with a negative acknowledgment service is executed and terminated with a positive acknowledgment the effect of this service is removed by the firmware 1 4 1 Overview 4 1 1 Services Available in Both Operating Modes Table 4 1 Services available in both operating modes Code Services Page 0309 Read Configuration 4 20 030Bhex Complete_Read_Configuration 4 26 0316 Get Error Info 4 41 032Anex Get Version Info 4 47 0351 hex Read_Value 4 11 0714 Control Device Function 4
6. p dr SO IN1 OUT1 Us OO Us OC GND O GND OO FE OO 2a 5 T 55200027 Figure 1 38 2 wire termination for digital devices Sensor Figure 1 38 detail A shows the connection of a 2 wire sensor The sensor signal is carried to terminal point IN1 The sensor is supplied from the voltage Ug Actuator Figure 1 38 detail B shows the connection of an actuator The actuator is supplied through output OUT1 The load is switched directly by the output 1 68 PHCENIX 615605 CONTACT FL IL 24 BK PAC 3 wire technology Sensor Actuator 55200038 Figure 1 39 3 wire termination for digital devices Figure 1 39 detail A shows the connection of a 3 wire sensor The sensor signal is carried to terminal point IN1 IN2 The sensor is supplied via terminal points Ug and GND Figure 1 39 detail B shows the connection of a shielded actuator The actuator is supplied through output OUT1 OUT2 The load is switched directly by the output 615605 PHCENIX FL IL 24 BK PAC UM E 4 wire technology 55200037 Figure 1 40 4 termination for digital devices Sensor Figure 1 40 detail A shows the connection
7. 3 13 Description of the Device Driver Interface DDI Introduction 3 15 3 7 1 OVeIVIOW tite pedea et dete 3 15 3 7 2 Working Method of the Device Driver Interface 3 16 3 7 3 Description and Functions of the Device Driver Interface 3 18 Monitoring Functions ro ee RO eet ti epus 3 33 3 8 1 Process Data Monitoring Process Data Watchdog sse 3 35 3 8 2 Connection Monitoring Host 3 37 3 8 3 Data Interface DTI Monitoring 3 40 3 8 4 I O Fault Response Mode sse 3 44 3 8 5 Treatment of the NetFail Signal Testing With ETH 2200 3 46 IN Process Data 3 52 615605 PHCENIX e CONTACT FL IL 24 BK PAC UM E 3 10 3 11 3 12 3 13 3 14 3 15 3 16 Notification Mode aati ene a dete lee 3 56 Programming Support Macros 3 58 3 11 31 Introductiom uee HERI eB NP 3 58 Description of the 3 60 3 12 1 Macros for Converting the Data Block of a Command 3 61 3 12 2 Macros for Converting the Data Block of a Message 3 63 3 12 3 Macros for Converting Input
8. 2 10 2 7 2 Structure of the Web 2 11 2 7 3 Layout of the Web Pages 2 11 2 7 4 Password Protection 2 12 2 7 5 Process Data Access Via _ 2 12 2 8 Firmware Update Meee cei e ioi an n dcn ee 2 17 2 8 1 Firmware Update Using The Factory 2 17 2 9 Firmware Update Using Web Based Management WBM Without Factory 2 19 2 9 1 Trap Generation iie RE e Dee eed 2 19 2 9 2 Representation of Traps in the Factory Manager 2 19 2 9 3 FL IL 24 2 20 2 9 4 Defining the Trap 2 20 2 10 Factory Line I O 2 2 21 2 10 1 Factory Line I O 2 21 210 2 nee eR 2 22 2 11 Management Information Base 2 24 2 11 14 Standard MIBS 2 24 615605 2 1 PHCENIX CONTACT FL IL 24 BK PAC UM E 2 12 Interface Group 1 3 6 2 25 21231 Private iem a eats 2 30 2 13 Meaning of the 7 Segment Display 2 44 2 2 PHC
9. 4042244040 0000 6 26 6 9 1 Power Up Table n 6 27 6 9 2 Connection Monitoring Table 6 28 6 10 Modbus TCP PCP Registers 6 30 Zy lechnical 7 3 7 1 Ordering Data ot ted C E eq 7 11 vi PHCEN IX 615605 CONTACT FL IL 24 BK PAC Section 1 This section provides information about the basic structure of low level signal modules the assignment and meaning of the diagnostic and status indicators on the va rious Inline modules potential and data routing housing dimensions and labeling options for the modules general information on the module circuit diagrams M 1 3 1 1 General EUnctions oce D EORR 1 3 1 1 1 Product Description ss ra ae 1 3 1 2 Structure of the FL IL 24 BK PAC Bus 1 5 1 2 1 Local Status and Diagnostic 1 6 1 8 Connecting the Supply 1 7 1 4 Connector Assignment esses 1 8 1 5 Supported Inline 1 9 1 6 Basic Structure of Low Level Signal Modules 1 16 1 6 1 Electronics Base oie it 1 17 1 6
10. 615605 PHCENIX s CONTACT FL IL 24 BK PAC UM E 5 1 1 PCP Configuration in the Web Based Management Z7 NTACE FL IL 24 BK PAC PCP PDU Size Configuration PDU Size CR 2 FL IL 24 BK PAC xcd General Instructions POU Size CR3 Device Information PDU Size CR4 Device Configuration a Inline Station PDU Size CR 5 Services PDU Size CRE jior Pou Ss CR Remote Diaynosti ov size v Bus Configuration PDU Size CRB Event Table PDU Size CR9 Configuration Home Enter Password Send ZE Byte fa Byte fs Byte Byte Byte TN Byte m 5 1 2 Configuration of the PCP PDU Size last update 14 43 22 Receive Byte Byte fa Byte Byte fa Byte fa Byte Byte Byte Reboot The standard PDU size for communication with all Phoenix Contact Inline devices is 64 bytes for the transmit and receive direction Systems couplers like the ILC 200 UNI are provided with PDU sizes that can be configured If a different size is configured and if communication is to be with the ILC 200 UNI via an FL IL 24 BK PAC this size must be configured to the values set on the ILC 200 UNI before 5 4 PHCENIX CONTACT 615605 Communication 5 2 Supported PCP Commands Table 5 1 Supported PCP commands Service Service Code Initiate Request 008B
11. 1 56 PHCENIX 615605 CONTACT FL IL 24 BK PAC 1 14 2 1 Connecting an IB IL 24 Al 2 SF Analog Input Module e Connect the shielding to the shield connector see Section 1 15 2 Connecting Shielded Cables Using the Shield Connector e When connecting 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 Use a multi wire cable for the connection of both sensors and connect the shielding to the shield connector as described above 2 Use a thin cable for the connection of each sensor and connect the shielding of both cables together to the shield connector 3 Use the 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 615605 PHCENIX 1 57 CONTACT FL IL 24 BK PAC UM E Connecting an Analog Output Module IB IL 1 14 2 2 IS 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
12. 55200042 Figure 1 34 Connection of actuators signal cables gt 10 m 32 81 ft A Module side B Actuator side 615605 0598 PHCENIX CONTACT FL IL 24 1 15 Connecting Cables Both shielded 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 25 16 can be connected The Ethernet cable is connected via an 8 pos RJ45 connector 1 15 1 Connecting Unshielded Cables 6138 016 Figure 1 35 Connecting unshielded cables 615605 PHCENIX 1 59 CONTACT FL IL 24 BK PAC UM E Wire the connectors as required for your application E BUE IS 1 60 PHGNIX 615605 CONTACT FL IL 24 BK PAC 1 15 2 Connecting Shielded Cables Using the Shield Connector 5981A023 Figure 1 36 Connecting the shield to the shield connector Hue 1 61 CONTACT FL IL 24 BK PAC UM E Stripping cables IS Wiring the connectors Connecting 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 Strip the outer cable sheath to the desired length a 1 The desired length a depends on the connection position of the wires and whe
13. 6 25 Available fault response 6 26 Power up 6 27 Connection monitoring table 6 28 PGF registers uten gb 6 30 A 8 PHCEN IX 615605 CONTACT
14. 3 60 Table 3 10 Driver software 3 68 Section 4 Table 4 1 Services available in both operating modes 4 3 Table 4 2 Services available only in expert mode 4 4 Table 4 3 System parameters 4 9 Table 4 4 Available fault response 4 9 Table 4 5 Supported error 4 43 Table 4 6 Overview of error messages according to error codes 4 50 A 6 PHCEN IX 615605 CONTACT List of Tables Section 5 Table 5 1 Supported commands 5 5 Section 6 Table 6 1 Modbus message 6 4 Table 6 2 Supported function 6 5 Table 6 3 Modbus reference tables 6 6 Table 6 4 Dynamic process data table 6 6 Table 6 5 Applicable functions seem 6 9 Table 6 6 Read multiple registers sene 6 10 Table 6 7 Response to read multiple 6 10 Table 6 8 Exception response to read multiple registers 6 10 Table 6 9 Write multiple registers 2 1 6 11 Table 6 10 Response
15. EEUU f FL IL 24 BK PAC UM E INNOVATION IN INTERFACE User Manual Hardware and Firmware User Manual for the FL IL 24 BK FL IL 24 BK PAC Ethernet Inline Bus Coupler 90 14 205 Designation Order No jo 16 FL IL 24 BK PAC No au 1717 717 p Factory Line User Manual Hardware and Firmware User Manual FL IL 24 BK FL IL 24 BK PAC Ethernet Inline Bus Coupler Designation FL IL 24 BK PAC UM E Revision 05 Order No 90 14 20 5 This user manual is valid for FL IL 24 BK FL IL 24 BK PAC Phoenix Contact 09 2004 615605 PHCEN IX CONTACT 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 man ual 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 B 615605 PH NIX CONTACT FL IL 24 BK PAC UM E gt XP aj Statement of Legal Authority This manual including all illustrations contained herein is copyri
16. OID 1 3 6 1 4 1 4346 11 11 1 3 Syntax Display string Access Read Description Contains the URL of the device specific web page for WBM flWorkBasicSerialNumber OID 1 3 6 1 4 1 4346 11 11 1 4 Syntax Octet string 12 Access Read Description Contains the serial number of the device flWorkBasicHWRevision OID 1 3 6 1 4 1 4346 11 11 1 5 Syntax Octet string 4 Access Read Description Contains the hardware version of the device flWorkBasicCompMaxCapacity OID 1 3 6 1 4 1 4346 11 11 1 11 Syntax Integer32 1 1024 Access Read Description Contains the maximum possible number of devices that can be connected flWorkBasicCompCapacity OID 1 3 6 1 4 1 4346 11 11 1 12 Syntax Integer32 1 1024 Access Read Description Contains the actual number of connected devices flWorkComponentsTable fl WorkComponentsEntry OID 1 3 6 1 4 1 4346 11 11 2 1 1 Syntax Access Description Generates a table with the description of individual components 2 36 PHCEN IX 615605 CONTACT Startup Operation flWorkComponentsIndex OID 1 3 6 1 4 1 4346 11 1 2 1 1 1 Syntax Integer32 1 1024 Access Read Description Contains the index of the component flWorkComponentsOID OID 1 3 6 1 4 1 4346 11 1 2 1 1 2 Syntax OBJECT IDENTIFIER Access Read Description Contains the designation of OIDs complete path entries flComponentsURL OID 1 3 6 1 4 1 4346 11 1 2 1 1 3 Syntax Display string Access Read Description Contains the URL of the web
17. Tolerance 15 20 according to EN 61131 2 Ripple 5 Permissible range 19 2 V to 30 V Minimum current consumption at nominal voltage 92 mA At no load operation i e Ethernet connected no local bus devices connected bus inactive Maximum current consumption at nominal voltage 15 Loading the 7 5 V communications power with 2 the 24 V analog voltage with 0 5 A 615605 PH NIX 7 5 CONTACT FL IL 24 BK PAC UM E 24 V Module Supply Communications Power Potential Jumper 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 V DC 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 20 10 P 96 0 5 10 15 20 C Ambient temperature in 25 30 35 40 45 TA PC 50 P Loading capacity of the power supply unit for communications power and analog supply in 55 61550009 7 6 PHCENIX CONTACT 615605 Technical Data Power Dissipation Formula to Calculate the Power Dissipation of the Electronics P
18. INVALID ID 4 46 0 0080 PNM12 CONFIG MULTI ERR OUT 4 46 0x0D9C PNM12 CONFIG LB TOO LONG OUT 4 46 OxFFFF CONTROLLER DEVICE NUMBER 4 46 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 Inline devices is 63 Number of specified or connected INTERBUS devices E_SM_CFG_NUM_OF_PCP_DEV_TOO_BIG 0 2 Meaning Too many PCP devices Cause You connected more then the permitted number of PCP devices You configured more then the permitted number of PCP devices Remedy Reduce the number of connected or configured PCP devices The maximum permissible number of PCP devices is 8 E SM CFG IND ADDR LIST TOO BIG OA2Enex Meaning The permitted number of internal indirect address list entries was exceeded You have reached the firmware memory limit Cause You have too many modules that occupy only one byte or one nibble of address space in the data ring Remedy 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 44 PHCEN IX 615605 CONTACT Firmware Services Cause Remedy Meaning Remedy Add Error Info Meaning
19. 3 10 3 5 5 Changing and Starting a Configuration in P amp P Mode 3 12 Changing a Reference Configuration Using the Software 3 13 3 6 1 Effects of Expert Mode 01048 3 13 3 6 2 Changing a Reference Configuration 3 13 Description of the Device Driver Interface DDI Introduction 3 15 3 7 1 Ol E Eum 3 15 3 7 2 Working Method of the Device Driver Interface 3 16 3 7 3 Description and Functions of the Device Driver Interface 22222112 1 3 18 615605 PHCENIX i CONTACT Table of Contents 4 Firmware Services 3 8 3 9 3 10 3 11 3 12 3 13 3 14 3 15 3 16 4 2 4 3 Monitoring 3 33 3 8 1 Process Data Monitoring Process Data Watchdog 3 35 3 8 2 Connection Monitoring Host Checking 3 37 3 8 3 Data Interface DTI Monitoring 3 40 3 8 4 I O Fault Response Mode 3 44 3 8 5 Treatment of the NetFail Signal Testing With ETH SetNeltFail nude di 3 46 IN Process Data 3 52 Notification Mode eee a cete dcn 3 56 Programming Support Macros seem 3 58 3 11 41 Introduction ehe 3 58 Description of the
20. End plate to protect the last Inline module Inline diagnostic indicators 24 V DC supply and functional earth ground connector not supplied as standard order as an accessory 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 status and diagnostic indicators Reset button 7 segment display for the device status Ethernet communication unit 615605 PHCENIX CONTACT FL IL 24 BK PAC UM E 1 2 1 Local Status and Diagnostic Indicators Table 1 1 Local status and diagnostic indicators Des Color Status Meaning Module Electronics 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 Green ON 24 V main circuit supply present OFF 24 V main circuit supply not present US Green ON 24 V segment supply present OFF 24 V segment supply not present Ethernet Port 100 Green ON Operation at 100 Mbps OFF Operation at 10 Mbps if LNK LED active FD Green ON Data transmission in full duplex mode OFF Data transmission in half duplex mode if LNK LED active COL Red ON Collision of data telegrams OFF Transmission of telegrams without a collision if LNK LED active XMT Green ON Data telegrams are being sen
21. 4 5 Services for Parameterizing the Controller Board 4 7 4 3 1 Control Parameterization Service 4 7 PHCENIX 615605 CONTACT FL IL 24 BK PAC UM E 5 PCP Communication 6 Modbus TCP Protocol 4 4 4 5 4 6 5 2 6 1 6 2 4 3 2 Set Value Service unde ete er ei heo cive ers 4 9 4 3 3 Read Value Service te tice ted 4 11 4 3 4 Initiate Load Configuration Service 4 13 4 3 5 Load Configuration Service 20 4 15 4 3 6 Terminate Load Configuration Service 4 18 4 3 7 Read Configuration Service 4 20 4 3 8 Complete Read Configuration Service 4 26 4 3 9 Delete Configuration Service 4 29 4 3 10 Create Configuration Service 4 30 4 3 11 Activate Configuration Service 4 32 4 3 12 Control Device Function Service 4 34 4 3 13 Reset Controller Board Service 4 36 Services for Direct INTERBUS Access 4 38 4 4 1 Start Data Transfer Service 4 38 4 4 2 Alarm Stop ServiGe e a NE eds 4 40 Dia
22. Syntax Display string Access Read Description Contains a brief description of the component flComponentsURL OID 1 3 6 1 4 1 4346 11 1 2 1 1 4 Syntax Display string Access Read Description Contains the URL of a web page with additional information www factoryline de flComponentsOrderNumber OID 1 3 6 1 4 1 4346 11 1 2 1 1 5 Syntax Display string Access Read Description Contains the order number of the component 615605 PHCENIX ER CONTACT FL IL 24 BK PAC UM E 2121 3 FL Device MIB The FL Device MIB contains general information about components from the Factory Line product group This private FL Device MIB OID 1 3 6 1 4 1 4346 describes one part of the pxcFactoryLine OID 1 3 6 1 4 1 4346 11 group MIB structure 1 pxcModules 3 flDeviceModule 11 pxcFactoryLine 11 flWorkDevice 1 flWorkBasic 1 flWorkBasicName 2 flWorkBasicDescr 3 flWorkBasicUrl 4 flWorkBasicSerialNumber 5 flWorkBasicHWhevision 11 flWorkBasicCompMaxCapacity 12 flWorkBasicCompCapacity 2 flWorkComponents 1 flWorkComponentsTable 1 flWorkComponentsEntry 1 fl WorkComponentsIndex 2 flWorkComponentsOID 3 flWorkComponentsURL 4 flWorkComponentsDevSign 5 flWorkComponentsPowersStat 11 flWorkComponentsStrongReset 3 flWorkTraps 0 flWorksTrapsDelemeter 1 flWorkFWPasswdAccess 2 flWorkFWHealth 3 flWorkFWConf 11 flWorkFirmware 1 flWork
23. Word 3 Word 4 1 parameter Word 5 Bit BE EET 0 Key Code 0750 44 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 parameter 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 16 0 Code 875044 Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001 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 has executed the service successfully XXXXhex indicates a negative message The controller board could not execute the 4 10 PHCEN IX 615605 CONTACT Firmware Services 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 Word 1 Word 2 Word 3 Word 4 1 parameter Bit Key Code 0351
24. se e 2 4 Assigning an IP Address Using the Factory Manager 2 4 2 4 1 BootP iron au tdt ade c ruo aH 2 4 Manual Addition of Devices Using The Factory Manager 2 5 Selecting IP Addresses 8 888 2 5 2 6 1 Possible Address Combinations 2 7 2 6 2 SUBNET MASKS hono H rea RE 2 8 2 6 3 Structure of the Subnet Mask 2 8 Web Based 2 10 2 7 1 Calling Web Based Management WBM 2 10 2 7 2 Structure of the Web Pages 2 11 2 7 3 Layout of the Web Pages 2 11 2 7 4 Password Protection sse 2 12 2 7 5 Process Data Access Via _ 2 12 Firmware 2 17 2 8 1 Firmware Update Using The Factory Manager 2 17 PHCEN IX 615605 CONTACT FL IL 24 BK PAC UM E 3 Driver Software 2 9 2 10 2 12 2 13 3 3 3 4 3 5 3 6 3 7 Firmware Update Using Web Based Management WBM Without Factory Manager es emen 2 19 2 9 1 Trap Generation ooa ete attendees 2 19 2 9 2 Representation of Traps in the Factory Manager 2 19 2 9 3
25. 1 1 0 Class 1 1 1 1 0 The bits for the network class followed by those for the network address and user address Depending on the network class a different number of bits is available both for the network address network ID and the user address host ID Network ID Host ID Class A 7 bits 24 bits Class B 14 bits 16 bits Class C 21 bits 8 bits Class D 28 bit multicast identifier Class E 27 bits 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 2 6 PHCENIX 615605 CONTACT Startup Operation Class A 0 0 0 0 127 255 255 255 Class B 2 6 1 Possible Address Combinations 7 bits 24 bits 14 bits 16 bits Class C 21 bits 8 bits 4 1200o 223255285255 1 1 0 Class D 28 bits 224 0 0 0 239 255 255 255 Identifier for multicast group Class E 27 bits o 240 0 0 0 247 255 255 255 Reserved for future applications Figure 2 1 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
26. 32 Host_Date byte 1 Et m Host Date byte 6 Words 33 35 Host Time byte 1 EN Host Time byte 6 615605 PHCENIX 4 47 CONTACT FL IL 24 BK PAC UM E Words 36 37 Start FW Version byte 1 Start FW Version byte 2 Start FW Version byte 3 Start FW Version byte 4 Words 38 40 Start FW State byte 1 ae Start_FW_State byte 6 Words 41 43 Start_FW_Date byte 1 m Start FW Date byte 6 Words 44 46 Start FW Time byte 1 TE Start FW Time byte 6 Words 47 50 HW Art No byte 1 m E HW Art No byte 8 Words 51 65 HW Art Name byte 1 a HW Art Name byte 30 Words 66 67 HW Motherboard ID byte 1 HW Motherboard ID byte 2 HW Motherboard ID byte 2 HW Motherboard ID byte 4 Word 68 HW Version byte 1 HW Version byte 2 Words 69 78 HW Vendor Name byte 1 HW Vendor Name byte 20 Words 79 84 HW Serial No byte 1 ER gt HW Serial No byte 12 Words 85 87 HW Date byte 1 M HW Date byte 6 Bit 0 Negative message Word 1 Code Word 2 Parameter Count Word 3 Result Word 4 Add Error Info Bit jo 0 Key Code 832A Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 00554 55 parameter words with a negative message 4 48 615605 PHCEN
27. FL IL 24 BK PAC UM E 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 16 Settings for the Used Attributes parameter Start Entry No Entry Count Configuration Entry Bit 0 Device number Bit 1 Device code Example If the entries are only to consist of the device code enter the value 0002 for the Used Attributes parameter bit 1 is set Number of the first device for which attributes are to be transmitted Number of devices for which attributes are to be transmitted Attribute values of the individual devices to be transmitted according to their order in the physical bus configuration see syntax on page 4 16 Syntax Configuration Entry Attribute Word x Device number Word x 1 Device code Bit Jc Attributes Bus Segment No Number of the bus segment where the device is located Value range 01 Position Physical location in the bus segment Value range OOhex 6 for an Inline station The Bus Segment No and Position parameters together form the device number 4 16 PHCENIX 615605 CONTACT Firmware Services Length Code The length code refers to the address space required by the device in the host ID Code The ID code indicates the device type It is prin
28. Figure 2 4 Software Update on Next Reboot C Enable Disable TFTP Update Status Firmware Update was successfully executed the FL IL 24 BK If the software update status is set to enable the FL IL 24 BK will try to load new software within the next reboot Press the apply button to change the software update status The settings will take effect after the next reboot of Enter password Apply Apply and Reboot WBM firmware update 2 18 PHCENIX 615605 CONTACT Startup Operation 2 9 Firmware Update Using Web Based Management WBM Without Factory Manager The following steps must be carried out when executing a firmware update using WBM 1 Open the web page for the bus coupler by entering the IP address for the bus coupler in the address line of a standard web browser After the web page has been loaded click on Device Configuration and then Software Update Enter the IP address of the tftp server in the TFTP Server IP Address field Then enter the file name of the firmware and the path name if necessary in the Downloadable File Name field In the Software Update on Next Reboot field click on Enable 2 Enter your password and click Apply to execute a reboot at a later time click on Apply and Reboot for the update to take effect immediately 2 9 1 Trap Generation When important events occur e g a configuration change the bus coupler sends
29. PHCENIX CONTACT Driver Software Table 3 10 Driver software messages Code Error Message Cause Page 00A9 ex ERR PLUG PLAY Invalid write access to process data in P amp P mode 3 75 0100hex ERR STATE CONFLICT This service is not permitted in the selected operating 3 75 mode of the controller 010155 ERR INVLD CONN TYPE Service called via an invalid connection 3 76 010245 ERR ACTIVATE PD CHK IN process data monitoring could not be activated 3 76 0103454 ERR DATA SIZE The data volume is too large 3 76 0200 ERR INVLD Unknown command 3 76 020144 ERR INVLD Invalid parameter 3 76 1010 ERR OPEN The IBSETHA file cannot be opened 3 76 101344 ERR IBSETH READ The IBSETHA file cannot be read 3 77 101444 ERR IBSETH The device name cannot be found in the file 3 77 101644 ERR IBSETH INTERNET The system cannot read the computer name host 3 77 address 3 14 Positive Messages ERR_OK 0000hex Meaning After successful execution of a function the driver software generates this message as a positive acknowledgment Cause No errors occurred during execution of the function 615605 3 69 PHCENIX CONTACT FL IL 24 BK 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 process
30. PHCENIX 615605 CONTACT Driver Software 3 8 Monitoring Functions Monitoring functions with different features are available for monitoring Ethernet communication and the connected devices Process data watchdog process data monitoring Host checking DTI monitoring There are monitoring functions according to the features functions that need to be monitored According to the application requirements the appropriate monitoring function can be activated By default upon delivery process data watchdog is activated Table 3 4 Monitoring functions Monitoring Mechanism Monitoring the client the the Ethernet process data application individual connection exchange channels Process data watchdog process X X X data monitoring Host checking X DTI Modbus monitoring X X X In the event of error the system reacts with 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 5 Available fault response modes Fault Response Mode Value Function Reset fault mode default 1 The digital outputs are set to 0 The analog outputs
31. SEG F Segment terminal with fuse as an example of a segment terminal sien CONTACT FL IL 24 BK PAC Electrical isolation Ethernet No electrical isolation of the Inline communications power Isolated supply for logic and I O devices 1 11 Voltage Concept The Ethernet bus coupler and the Inline local bus system have a defined voltage and grounding concept This avoids an undesirable effect on I O devices 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 shield is directly connected to functional earth ground The device has two functional earth ground springs which have contact to the DIN rail when they are snapped on The springs are used to discharge interference rather than serve as 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 54 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 co
32. Te Lokal Invanet Figure 2 3 Screenshot of the XML data 2 16 PHCENIX CONTACT 615605 Startup Operation 2 8 Firmware Update 2 8 1 Firmware Update Using The Factory Manager The following steps must be carried out when executing a firmware update using the Factory Manager 1 In the Device View window right click on the device whose firmware you want to update Select Properties from the context menu and then the BootP Parameter tab Activate BootP and fill in the appropriate fields For further information please refer to the Factory Manager help Ensure that the BootP and tftp server for the Factory Manager are activated Open the web page for the bus coupler context menu or Ctrl W Click on Device Configuration and then Software Update In the Software Update on Next Reboot field click on Enable Enter your password and click Apply to execute a reboot at a later time click on Apply and Reboot for the update to take effect immediately 615605 PHCENIX EM CONTACT FL IL 24 BK PAC UM E eaux FL IL 24 BK PAC FLIL 24 BK PAC last update 10 32 28 Software Update TFTP Server IP Address fi 49 208 18 40 Downloadable File Name General Instructions Device Information Device Configuration IP Configuration SNMP Configuration Software Update Change Password Watchdog Inline Station Home IS
33. The electronics bases of the low level signal modules are available in three design widths 12 2 mm 0 480 in 24 4 mm 0 961 in and 48 8 mm 1 921 in It accepts either one two or four 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 Figure 1 14 71 5 mm 2 815 04807 55201023 Figure 1 11 Dimensions of the electronics bases 2 slot housing 1 24 PHCEN IX 615605 CONTACT FL IL 24 BK PAC 4 slot housing 120 mm 4 724 5 191127 peel ce 119129 De Y 24 4 mm i 0 961 71 5 mm 2 815 55201022 Figure 1 12 Dimensions of the electronics bases 4 slot housing 8 slot housing Es Ee Ee Le s Sle Eene A N 120 mm 4 724 71 5 mm 2 815 48 8 mm 1 921 55201024 Figure 1 13 Dimensions of the electronics bases 8 slot housing 615605 PHCENIX 1 25 CONTACT FL IL 24 BK PAC UM E
34. min 330ms UpdateData FALSE 615605 PHCENIX oor CONTACT FL IL 24 BK PAC UM E Task Syntax Parameter 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 monitoring channels are not affected IBDDIRET IBDDIFUNC ETH ClearHostChecking IBDDIHND nodeHd IBDDIHND nodeHd Node handle MXI or DTI of the bus coupler 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 coupler application program is still operating correctly An extremely serious error occurs when the controlling process is no longer operating correctly i e the bus coupler is no longer supplied with up to date process data and as a result incorrect output data is sent t
35. reference configuration Yes Set station to RUN state 61650025 Figure 3 8 P amp P mode active expert mode inactive P amp P mode active and expert mode active Read connected configuration Operable configuration Save retentively as reference configuration Station in READY state Display Stop Display 82 61560026 Figure 3 9 P amp P mode active and expert mode active 615605 PHCENIX mH CONTACT FL IL 24 BK PAC UM E IS 3 5 5 Changing and Starting a Configuration in P amp P Mode The following steps must be carried out when changing an existing configuration Switch the power supply off Change the configuration Switch the power supply on A configuration is started as shown in the flowchart see Figure 3 6 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 known configuration is saved in the EEPROM as the reference configuration connected Inline devices are integrated in the known configuration if the DIAG LEDs are continuously lit on all modules Topreventthe accidental use of the wrong configuration process data can only be accessed when P amp P mode has been deactivated 3 12 PHCNIX 615605 CONTACT Driver Software 3 6 Ch
36. 230 Hz IB IL AI 8 SF 8 inputs 2 wire termination 24 V 0 5 0 10V 10 0 2727831 25 V 0 20 mA 4 20 mA 20 mA 0 40 mA IB IL AI 8 SF PAC 8 inputs 2 wire termination 24 V 0 5 0 10V 10 0 2861412 25 V 0 20 mA 4 20 mA 20 mA 0 40 mA IB IL AI 8 IS 8 inputs 3 wire termination 24 V DC 0 20 mA 27 42 74 8 4 20 mA 20 mA 0 40 mA 40 mA IB IL AI 8 IS PAC 8 inputs 3 wire termination 24 V DC 0 20 mA 28 61 66 1 4 20 mA 20 mA 0 40 mA 40 mA IB IL Al 2 HART 2 inputs 2 wire termination 24 V DC 0 25 4 20 mA HART 28 60 26 4 functionality HART protocol transmission IB IL Al 2 HART PAC 2 inputs 2 wire termination 24 V DC 0 25 mA 4 20 mA HART 2862149 functionality HART protocol transmission 615605 1 11 PHCENIX CONTACT FL IL 24 BK PAC UM E Table 1 4 Analog input output modules Designation Contd Properties Order No 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 2861328 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 27 27 763
37. 3 65 3 12 4 Macros for Converting Output 3 66 Diagnostic Options for Driver Software 3 68 31315 dntrod ctiom uiae crecer ert erri eret 3 68 Positive Messages eiie xe e ER ER EP ERES 3 69 Error Messages ei nce dcus 3 70 3 15 1 General Error 3 70 3 15 2 Error Messages When Opening a Data Channel 3 72 3 15 3 Error Messages When Transmitting Messages Commands 3 73 3 15 4 Error Messages When Transmitting Process Data 3 75 Example Program iate hain quieta lecce 3 78 3 16 1 Demo Structure 3 78 3 16 2 Example Program Source 3 80 3 2 PHCNIX 615605 CONTACT Driver Software 3 Driver Software 3 1 Documentation This Hardware and Firmware User Manual for FL IL 24 BK FL IL 24 BK PAC Ethernet Inline Bus Coupler Order No 90 14 20 5 describes the hardware and software functions in association with an Ethernet network and the functions of the Device Driver Interface DDI software 3 2 Software Structure Client Controller board Device Driver Interface Firmware Read and write Process data Send and receive Ethernet adapter ostic IBS pi ag master 61560018 Driver software Figure 3 1 Software stru
38. Connector D N x pem tele a 00 BB 88 08 Ba 00 0 480 Inn 12 2 mm 99 0 480 12 2 mm 0 480 55200058 Figure 1 14 Connector dimensions Key A Standard connector B Shield connector C Extended double signal connector The depth of the connector does not influence the overall depth of the module 1 26 PHCENIX 615605 CONTACT FL IL 24 BK PAC 1 9 Electrical Potential 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 It 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 circuits are created in one station the logic circuit and the I O circuit 1 2 3 4 5 6 7 1 A a b 9 8 61560017 Figure 1 15 Potential and data routing 615605 PHCENIX 1 27 CONTACT FL IL 24 BK PAC UM E Table 1 12 Potential jumper see Fig
39. Description A new password can be entered here with a maximum of 12 characters Example Your new password should be factory3 The password must be entered a second time for confirmation Your entry factory3factory3 Your password for write access now is factory3 fIWorkFWCtrlPasswdSuccess OID 1 3 6 1 4 1 4346 11 11 11 2 3 2 Syntax Integer Access Read Description A message is displayed which informs you whether the last change of password was successful Unknown 1 Failed Successful 3 615605 PHCENIX 2 41 CONTACT FL IL 24 BK PAC UM E fIWorkFWCtrlUpdateEnable OID 1 3 6 1 4 1 4346 11 11 11 2 4 1 Syntax Integer Access Read write Description A firmware update can be executed here on the next manual restart reset of the device Start with existing firmware 1 Update firmware 2 fIWorkFWCtrITftplPAddr OID 1 3 6 1 4 1 4346 11 11 11 2 4 2 Syntax IP address Access Read write Description Enter the IP address of the tftp server where the new firmware can be found fIWorkFWCtrITftpFile OID 1 3 6 1 4 1 4346 11 11 11 2 4 3 Syntax Octet String 0 64 Access Read write Description Enter the file name of the new firmware here fIWorkFWCtrlConfStatus OID 1 3 6 1 4 1 4346 11 11 11 2 5 1 Syntax INTEGER Access Read Description Contains a status message about the current hardware configuration Configuration OK 1 Configuration faulty 2 Configuration saved 3 flWorkFWParamSaveConfig OID 1 3 6 1 4 1 434
40. 1 9 Table 1 4 Analog input output 1 11 Table 1 5 Special function 1 12 Table 1 6 Motor terminal 8 1 13 Table 1 7 Power and segment terminals eee 1 14 Table 1 8 Safety E QE 1 15 Table 1 9 Controller CPU eei eene de e t decani s 1 15 Table 1 10 Terminal point 2 1 18 Table 1 11 Module 1 21 Table 1 12 Potential jumper see Figure 1 15 1 28 Table 1 13 Data jumper see Figure 1 15 1 28 Table 1 14 Diagnostic LEDs of the bus 1 43 Table 1 15 Diagnostic LED on the power terminal 1 44 Table 1 16 Diagnostic LED on the segment terminal 1 44 Table 1 17 Additional LED on supply terminals with fuse 1 44 Table 1 18 Diagnostic LED of the I O 1 45 Table 1 19 Status LEDs of the I O terminals 1 46 Table 1 20 Overview shield connection of analog Sensotrs actuatots uo etr Cb id tee d e Pis 1 56 Table 1 21 Overview of the connections used for digital inputimodules 2 2 b rtt 1 67 Table 1 22 Overview of the connections used fo
41. 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 has 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 615605 PHCENIX TM CONTACT FL IL 24 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 hex 000044 Header information of the configuration frame Header selected with the Frame Reference parameter 0001 hex 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 Word 4 Word 5 Word 6 Bit Qo 0 Key Code 0309 Command code of the service request Parameter Count Number of subsequent words 0004nex 4 parameter words Frame Reference Number of the configuration frame 0001 reads the reference configuration 00024 reads
42. 11 Input discretes table offset 0 and bit count 2000 returns input discrete values 11 2000 Input discretes table offset 4 and bit count 13 returns input discrete values Q5 17 Any combination of the input discretes table offset with bit count that accesses offset gt 3072 produces an exception response 6 5 5 Read Input Registers This command reads from 1 to 125 16 bit words from the Modbus register table This command is used exactly like the read multiple registers command The read input registers command has the following format Table 6 18 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 6 19 Response to read input registers Byte No Meaning BYTE 0 Function code 4 BYTE 1 Byte count of response B 2 x word count in the command BYTE 2 1 Register values If the command accesses an invalid offset or contains an invalid length an exception response in the following format is output 6 14 615605 PHCENIX CONTACT Modbus TCP Protocol Table 6 20 Exception response to read input registers Byte No Meaning BYTE 0 Function code 0x84 BYTE 1 Exception response 2 6 5 5 1 Example for the Read Input Registers For examples please refer to the E
43. 6 3 1 Dynamic Modbus TCP Process Data Table 6 6 6 3 2 Example Location of the Input Output Data 6 7 6 3 3 Location of the Process Data in Dynamic Tables 6 8 6 4 Applicable Functions iet e itte teens 6 9 6 5 Supported Function 6 9 6 5 1 Read Multiple Registers 2102112 6 10 6 5 2 Write Multiple Registers 22 002112 6 11 6 5 3 ene E ode cett 6 12 6 5 4 Read Input Discretes e 6 13 6 5 5 Read Input Registers 4 2211 6 14 0 5 6 Wiite COllS anco de ERE EBERT 6 15 6 5 7 X Write Single Register 6 16 6 5 8 Read Exception Status 2 6 17 6 5 9 Exception Status Data Format 6 17 6 5 10 Exception Responses 8 4 4 6 18 6 5 11 Write Multiple Coils 6 19 6 5 12 Read Write Register 6 20 6 6 Reserved Registers for Command and Status 6 22 6 6 1 Command Word ide en 6 22 6 6 2 Status ett eet educ to eet ate e e qe eee ET 6 23 6 6 3 Diagnostics Using the Analog Input Table 6 23 6 6 4 Fault Table eie PIERDE 6 24 6 7 cT 6 25 6 8 Modbus 0 6 26 6 9 I O Fault Response
44. 615605 PHGNIX 2 25 CONTACT FL IL 24 BK PAC UM E Internet Protocol Group IP 1 3 6 1 2 1 4 The Internet protocol group is mandatory for all systems It contains information concerning IP switching 4 ip 1 ipForwarding 2 ipDefaultTTL 3 4 ipInHdrErrors 5 ipInAddrErrors 6 ipForwDatagrams 7 ipInUnknownProtos 8 ipInDiscards 9 ipInDelivers 0 ipOutRequests 1 ipOutDiscards 2 ipOutNoRoutes 3 ipReasmTimeout 4 ipReasmReqds 5 ipReasmOKs 6 ipReasmFails 7 ipFragOKs 8 ipFragFails 9 ipFragCreates 20 ipAddrTable 1 ipAddrEntry 1 ipAdEntAddr 2 ipAdEntlfindex 3 ipAdEntNetMask 4 ipAdEntBcastAddr 5 ipAdEntReasmMaxSize 21 ipRouteTable 1 ipRouteEntry 1 ipRouteDest 2 ipRoutelflndex 3 ipRouteMetric1 4 ipRouteMetric2 5b ipRouteMetric3 6 ipRouteMetric4 7 ipRouteNextHop 8 9 10 1 4 4 1 1 4 1 er st ud sex af set sl s T 1 1 1 S 8 ipRouteType 9 ipRouteProto 10 ipRouteAge 2 26 PHCENIX 615605 CONTACT Startup Operation 11 ipRouteMask 12 ipRouteMetric5 13 ipRoutelnfo 22 ipNetToMediaTable 1 ipNetToMediaEntry 1 ipNetToMedialflndex 2 ipNetToMediaPhysAddress 3 ipNetToMediaNetAddress 4 ipNetToMediaType 23 ipRoutingDiscards ICMP Group 1 3 6 1 2 1 5 The Internet c
45. 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 0x2275 615605 PHCENIX 7 CONTACT FL IL 24 BK PAC UM E Syntax Read Value Confirmation 8351 Positive message Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 1 system parameter Negative message Word 1 Word 2 Word 3 Word 4 Bit 0 8351hex Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 0004 with a negative message 0002 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 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 4 12 PHCENIX 615605 CONTACT Firmware Services Task Prerequisite 4 3 4 Initiate Load Configuration Service The Initiate Load Configuration service prepares the controller board to transmit a configuration to the INTERBUSmaster usi
46. ETH_ActivatePDInMonitoring 3 53 ETH_DeactivatePDInMonitoring 3 55 ETH_SetNetFailMode 3 50 ETH_GetFailMode 3 51 615605 PHCENIX 3 15 CONTACT FL IL 24 BK PAC UM E Remote procedure call Editing data telegrams 3 7 2 Working Method of the Device Driver Interface The entire Device Driver Interface DDI for the bus coupler 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 coupler 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 When a function is called the transfer parameters for the DDI function 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 coupler 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 ReaaData nodeHd dtiAcc function is called as an example in Figure 3 10 During function execution by the server bus coupler the thread process is in sleep state on the client until a reply is received from the server Once the function has be
47. FL IL 24 BK 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 pointerto a 7 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 GetlBSDiagnostic IBDDIHND nodeHd T IBS DIAG infoPtr IBDDIHND nodeHd Node handle MXI or DTI of the bus coupler from which the diagnostic bit register and diagnostic parameter register are to be read IBS DIAG infoPtr Pointerto a T IBS DIAG data structure The contents of the register are entered in this structure typedef 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 OK 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 Dependent on operating system ddiRet GetIBSDiagnostic ddiHnd amp infoPtr StateAB infoPtr state diagAB infoPtr diagPara while 3 32
48. Q2 Coil table offset 0 and bit count 2 with the value 0 resets the coils Q1 and Q2 615605 PHGNIX 6 19 CONTACT FL IL 24 BK PAC UM E 6 5 12 Read Write Register This command reads 1 up to 125 words from the Modbus register table and writes 1 up to 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 The write read command has the following format Table 6 34 Read write register Byte No Description BYTE 0 Function code 0x17 BYTE 1 2 Read register table offset BYTE 3 4 Read word count 1 to 125 BYTE 5 6 Write register table offset BYTE 7 8 Write word count 1 100 BYTE 9 Write byte count B 2 x write word count BYTE 10 9 Write register values The response to the read write register command has the following format Table 6 35 Answer to read write register Byte No Description BYTE 0 Function code 0x17 BYTE 1 Byte count B 2 x read word count BYTE 2 1 Read register values If the command accesses an invalid offset the exception response has the following format Table 6 36 Exception response to read write register Byte No Description BYTE 0 Function code 0x97 BYTE 1 Exception code 6 5 12 1 Examples for the read write register command Register table offset 0 and word count 2 returns
49. atraptoatrap manager defined by the user This enables the network administrator to react quickly to these events and to ensure network availability Traps are usually only transmitted once 2 9 2 Representation of Traps in the Factory Manager EN 2000 31 1 2001 08 28 32 Trap Receiver gt 5 LinkUp an Slice 1 Port 4 received from Inline I 0 Robot 192 168 2 80 2000 31 1 2001 08 28 32 Trap Receiver gt 5 LinkUp an Slice 1 Port 3 received from Inline I 0 Robot 192 168 2 80 A 2000 31 1 2001 08 28 32 Trap Receiver SNMP Trap LinkUp an Slice 1 Port 1 received from Inline 1 0 Robot 192 168 2 80 2000 31 1 2001 08 28 31 Trap Receiver gt 5 ColdStart received from Inline 1 0 Robot 192 168 2 80 2000 31 1 2001 08 28 31 TrapReceiver gt 5 ColdStart received from Inline 1 O Robot 192 168 2 80 Figure 2 5 Trap representation in the Factory Manager using a few example traps 615605 219 FL IL 24 BK PAC UM E 2 9 3 FL IL 24 BK PAC Traps The FL IL 24 BK PAC supports five traps ColdStart sent twice each time the device is restarted PasswordChange sent after the password is changed successfully FWHealth sent after any changes to the firmware operating status Configuration sent after any changes to the hardware configuration Authentification wrong password for SNMP acce
50. cc H 61560006 Ethernet Ug Uw Us Figure 1 24 Electrical isolation between Ethernet bus coupler and analog module The potential jumpers hatched XXXXX 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 from the analog circuit U aya 615605 PHCENIX 1 39 CONTACT FL IL 24 BK PAC UM E supply electrically isolated from one another Several electrically isolated segment or main circuits can be created by using power terminals A power terminal interrupts the 5 0 and GND potential jumpers 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 e g to functional earth ground electrical isolation is lost Because Ug 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
51. ous Figure 3 3 Position of the user data for individual devices in the word array LT bou 61550007 To achieve cycle consistency between input output data and the station bus cycle the bus coupler 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 15 4 0 15 4 0 15 4 0 4 bit device 2 bit device Figure 3 4 Position of the user data for several devices in the word array 3 6 PHCENIX 615605 CONTACT Driver Software 3 4 1 Position of the Process Data Example The physical assignment of the devices to the bus coupler 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 BK PAC Digital output modules Ethernet Inline local bus 15 0 iX X X X X X X X Word 1 XX X X Word 2 XXXXXXXXXXXXXXXX Word 3 X X Word 4 XXXXXXXXXXXXXXXX Word 5 XXXXXXXXXXXXXXXX Word 6 X Word 7 61560020 Figure 3 5 Position of the process data according to the physical bus config
52. perpendicular to the DIN rail detail A aj The keyway featherkey connection links adjacent modules and ensures safe potential routing Next attach the connectors to the corresponding base First place the front connector shaft latching in the front snap on mechanism detail C Then press the top of the connector towards the base until it snaps into the back snap on mechanism detail D 1 48 PHCENIX 615605 CONTACT FL IL 24 BK PAC 6138A015 Figure 1 29 Snapping on a module 615605 1 49 CONTACT FL IL 24 BK PAC UM E 1 13 4 Removing When removing a module proceed as follows Figure 1 30 e f there is a labeling field remove it A1 in detail A Lift the connector of the module be removed pressing the back connector shaft latching A2 in detail A Remove the connector detail B Remove the left adjacent and right adjacent connectors of the neighboring modules detail C This prevents the potential routing featherkeys and the keyway featherkey connection from being damaged You also have more space available for accessing the module e Press the release mechanism D1 in detail D and remove the electronics base from the DIN rail by pulling the base straight back D2 in detail 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 co
53. return 0 int main void IBDDIRET locRet 0 char Number 2 USIGN8 locMsgBlk MAX MSG LENGTH USIGN8 locReadBlk MAX MSG LENGTH int loci i USIGN16 ReadData 0 USIGN16 anzahl 255 USIGN16 PlugPlayModus 111 T IBS DIAG infoPtr time t ltime time t starttime USIGN16 Readl Read2 Read3 Read4 Display bus configuration printf n n Required bus configuration IB IL 24 DI 8 IB IL 24 DO 8 n Entry of the controller number printf NnController number Format xx gt gt 3 82 PHCENIX 615605 CONTACT Driver Software scanf 2s Number strcat OPEN MXI Number strcat OPEN DTI Number strcat OPEN MXI N1 M strcat OPEN DTI N1 D printf nOPEN MXI SS OPEN DTI s OPEN MXI OPEN DTI printf ss An Create connections DTI and MXI channels to FL IL 24 BK PAC locRet CreateConnection if locRet 0 printf NnNo DTI MXI connection gt Test aborted exit 0 Sleep 500 Read plug amp play mode mxiAcc msgLength 8 mxiAcc msgBlk locMsgBlk 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 Get service confirmation mxiAcc msgLength 128 time amp starttime locRet 555 printf FAIL Error code x locRet
54. shield Ethernet interface area bus coupler 3 Main voltage Uy and I O voltage Us area IB IL SCN PWR IN CP Order No 27 27 637 27 External jumper 12 m Jumpered in the s 23 module e gt Jumpered in the connector 61560021 Figure 1 22 Power connector for supply from a single power supply unit 615605 PHCENIX 1 37 CONTACT FL IL 24 BK PAC UM E Potentials The isolation of the I O circuit of a digital module to the communications power is Digital module only ensured if Ug and Uy Us are provided from separate voltage 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 U Us Us EP JL Figure 1 23 Example Interruption creation of the potential jumpers using the power terminal The areas hatched in the figure show the points at which the potential jumpers are interrupted 1 38 PHCENIX 615605 CONTACT FL IL 24 BK PAC Potentials The I O circuit measurement amplifier of an analog module receives floating Analog module power from the 24 V supply voltage Uana The power supply unit with electrical isolation is a component of an analog module The voltage U ana is looped through in each module and in this way is also available to the next module FL IL 24 BK PAC IB IL AI 2 SF uC Local bus U ANA 0 GNDy Electronics IB IL Al 2 SF
55. 0 1 means that no fault occurred Bit 1 indicates whether there is a Net Fail one or not zero This results in the following values for the status word 0 A fault occurred e g bus fault 1 No fault occurred 2 A NetFail occurred Table 6 40 Status word 15 14 13 12 11 10 9 8 765432 1 0 Reserved bits XIX 6 6 3 Diagnostics Using the Analog Input Table Table 6 41 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 is entered into the analog input table The diagnostic status register and the diagnostic parameter register use the last two words in the analog input table 615605 PH NIX 6 23 CONTACT FL IL 24 BK PAC UM E 6 6 4 Fault Table Data Format of the Fault Table The internal fault table which may contain up to 35 fault codes can be accessed by a Modbus client This internal fault table works according to the FIFO principle First In First Out This means that the 33rd fault entry deletes the oldest fault entry An application can request all fault entries or it can delete all entries via one command sent to the bus coupler Every fault entry is written in two words beginning with the reference 1024 in the register table All fault entries serve as information and do not stop the bus c
56. 0x0001 on the DO 2 and OxACDC on the DO 16 results in the following output values Module AO DO 16 DO2 Value 0x0010 OxACDC 0 0001 The state is Last values internal memory plus all newly written values 3 8 5 Treatment of the NetFail Signal Testing With ETH_SetNetFail The NetFail signal is set by writing a register in the coupling memory of the bus coupler As soon as this signal is detected by the bus coupler all local bus device outputs are reset and the PCP connections to the devices are interrupted The NetFail signal must be set to zero before process data can be output again The NetFail signal is always set if the connection to the client is interrupted the bus coupler does not write data to the DTI within the specified time or a general malfunction has been detected on the bus coupler which prevents safe operation Setting the NetFail signal is indicated by setting the NetFail bit in the control word of each data telegram which is sent by the bus coupler The NetFail signal can be reset using the appropriate command or if this is no longer possible by pressing the reset key on the front plate of the bus coupler 3 46 PHGNIX 615605 CONTACT Driver Software Task Syntax Parameter Return value ETH_SetNetFail The ETH_SetNetFail function sets the NetFail signal on the bus coupler and thus prevents further output of process data to the local bus devices The function is
57. 1 1 1 User Datagram Protocol Group UDP 1 3 6 1 2 1 7 The user datagram protocol group is mandatory for all systems that implement UDP 7 udp 1 udplnDatagrams 2 udpNoPorts 3 udpInErrors 4 udpOutDatagrams 5 udpTable 1 udpEntry 1 udpLocalAddress 2 udpLocalPort 2 28 PHCEN IX 615605 CONTACT Startup Operation EGP 1 3 6 1 2 1 8 The EGP group is mandatory for all systems that implement EGP 8 egp 1 egplnMsgs 2 egpinErrors egpOutMsgs 4 egpOutErrors 5 egpNeighTable 1 egpNeighEntry T egpNeighState uS 3 al Simple Network Management Protocol Group 1 3 6 1 2 1 11 The simple network management protocol group is mandatory for all systems In SNMP devices which are optimized to support either a single agent or a single management station some of the listed objects will be overwritten with the value 0 11 snmp 1 snmpinPkts 2 snmpOutPkts 3 snmpInBadVersions 4 snmpInBadCommunityNames B snmplnBadCommunityUses 6 snmpInASNParseErrs 7 not used 8 snmpInTooBigs 9 snmplnNoSuchNames 10 snmpInBadValues 615605 PHCENIX 549 FL IL 24 BK PAC UM E 11 snmplnReadOnlys 12 snmplnGenErrs 13 snmpinTotalReqVars 14 snmpinTotalSetVars 15 snmpInGetRequests Po snmplnGetNexts 1 1 1 2 12 1 Private MIBs 2 12 1 1 PhoenixContact MIB The
58. 15 PHCENIX CONTACT FL IL 24 BK PAC UM E 1 6 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 labeling field for connector Back T Transparent field connector shaft latch Attachment for labeling field m 1 2 labeling field for signal 1 2 i Signal terminals 1 2 Diagnostic and status Voltage terminals indicators FE or signal terminals 3 4 Function color uu ZBFM labeling field for signal 3 4 Back i Connector snap on mechanism ZBFM labeling field for module identification Front connector shaft latch Electronics base Data routing Slot coding Front Potential routing snap on mechanism Latch for DIN rail N Featherkey for key featherkey connection 5520A033 Figure 1 4 Basic structure of an Inline module The most important components shown in Figure 1 4 are described in sections Electronics Base on page 1 17 and Connectors on page 1 17 ZBFM Zack marker strips flat see also Section Function Identification and Labeling on page 1 21 20 1 16 PHCENIX 615605 CONTACT FL IL 24 BK PAC Design widths Advantages Connector width 1 6 1 Electronics Base The electronics base holds the entire electronics for the Inline module and the potent
59. 2 wire termination for digital devices 1 68 Figure 1 39 3 wire termination for digital devices 1 69 Figure 1 40 4 wire termination for digital devices 1 70 Section 2 Figure 2 1 Structure of IP addresses sse 2 7 Figure 2 2 WBM homepage nennen 2 10 Figure 2 3 Screenshot of the XML data 2 16 Figure 2 4 WBM firmware update 8 88 1 2 18 Figure 2 5 Trap representation in the Factory Manager using a few example traps 2 19 Figure 2 6 Defining the trap manager 2 2 20 Figure 2 7 browser screen 2 22 Figure 2 8 Linking items and terminal points 2 23 A 2 PHCENIX 615605 CONTACT Table of Figures Section 3 Figure 3 1 Software structure sinais i 3 3 Figure 3 2 Using the driver software in the application program 3 5 Figure 3 3 Position of the user data for individual devices in the word 3 6 Figure 3 4 Position of the user data for several devices inthe WOId array ise e e ede co o nee 3 6 Figure 3 5 Position of the process data according to the physical bus configuration coit ee cite acceded 3 7
60. 34 0750 Set Value 4 9 0956 Reset Controller Board 4 36 615605 PHCENIX 4 3 CONTACT FL IL 24 BK PAC UM E 4 1 2 Services Available Only in Expert Mode Table 4 2 Services available only in expert mode Code Services Page 0306 Initiate Load Configuration 4 13 0307 Load Configuration 4 15 0308 Terminate Load Configuration 4 18 030Chex Delete_Configuration 4 29 O30Epex Control_Parameterization 4 7 0701 hex Start_Data_Transfer 4 38 0710hex Create_Configuration 4 30 071 1hex Activate_Configuration 4 32 1303 Alarm Stop 4 40 4 2 Notes on Service Descriptions Using the The use of a service involves sending a service request and evaluating the service services 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 8000 higher than the code of the service request which it follows Example Request Start Data Transfer E F Start Data Transfer Request 0701 Confirmation Start Data Transfer Confirmation 870145 070156 8000 6 Parameter Result 0000pex gt Service executed successfully Parameter Result 0000 gt Error during service execution The service confirmation indicates the successful execution of a service via
61. 36 706 IB IL 120 DI 1 PAC 1 input 3 wire termination 120 V AC 28 61917 IB IL 230 DI 1 1 input 3 wire termination 230 V AC 27 40 342 IB IL 230 DI 1 PAC 1 input 3 wire termination 230 V AC 28 61548 IB IL 24 DO2 2 outputs 500 mA 4 wire termination 24 V DC 27 40 106 615605 1 9 PHCENIX CONTACT FL IL 24 BK PAC UM E Table 1 3 Digital Input Output Modules Designation Contd Properties Order No IB IL 24 DO 2 PAC 2 outputs 500 mA 4 wire termination 24 V DC 28 61470 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 61263 IB IL 24 DO 2 NPN 2 outputs with negative logic 500 mA 4 wire termination 24 V DC 27 40119 IB IL 24 DO 2 NPN PAC 2 outputs with negative logic 500 mA 4 wire termination 24 V DC 28 61 496 IB IL 24 EDO 2 2 outputs 500 mA 4 wire termination 24 V DC extended 27 42 599 diagnostics configurable outputs IB IL 24 EDO 2 PAC 2 outputs 500 mA 4 wire termination 24 V DC extended 28 61616 diagnostics configurable outputs IB IL 24 DO 4 4 outputs 500 mA 3 wire termination 24 V DC 27 26256 IB IL 24 DO 4 PAC 4 outputs 500 mA 3 wire termination 24 V DC 28 61 276 IB IL 24 DO 8 8 outputs 500 mA 4 wire termination 24 V DC 27 26 269 IB IL 24 DO 8 PAC 8 outputs 500 mA 4 wire termination 24 V DC 28 61289 IB IL 24 DO 8 NPN
62. 615605 CONTACT Driver Software Example UNIX Windows NT 2000 IBDDIHND mxiHnd IBDDIRET ddiRet T DDI MXI ACCESS mxiAcc USIGN8 oBuf 256 mxiAcc msgLength 4 mxiAcc DDIUserID 0 mxiAcc msgType 0 mxiAcc msgBlk oBuf O ll 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 615605 PHCENIX SER CONTACT FL IL 24 BK PAC UM E DDI MXI RcvMessage The DDI MXI RcvMessage function reads a message from the bus coupler The function receives a node handle and a pointer to a T DDI MXI ACCESS data structure as parameters The DDI MXI ACCESS structure contains all the parameters that are needed to read the message These parameters are transmitted to the bus couplers via the network without a plausibility check which means that invalid parameters are first detected at the bus coupler and acknowledged with an error message The nodeHd parameter specifies the bus coupler 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 coupler 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 Syntax Parameters
63. Add Error Info 83164 Message code of the service confirmation Number of subsequent words with positive message during error localization 0004nex 4 parameter words with positive message after error localization O0xXqg 2 2 Entry Count 20 words maximum with a negative message 000244 Always 2 parameter words Result of the service processing 0000hex indicates a positive message The controller board has executed the service successfully indicates a negative message The controller board could not execute the service successfully The Result parameter indicates why the service could not be executed XXXXhex 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 using error codes Table 4 5 Supported error codes Code Error Type Page Ox0A1C E SM CFG NUM OF DEV TOO BIG 4 44 Ox0A2D SM CFG NUM OF PCP DEV TOO BIG 4 44 OxOA2E E SM CFG IND ADDR LIST TOO BIG 4 44 Ox0BO2 E PNM12 STATE CONFLICT 4 45 615605 4 43 PHCENIX CONTACT FL IL 24 BK PAC UM E Cause Add Error Info Code Error Type Page 1 E PNM12 DEVICE STATE 4 45 0 0010 E 12 CONFIG MISSING DEVICE 4 45 0 0020 12 CONFIG MAU FAIL DO 4 45 0 0028 PNM12 CONFIG MAU FAIL DI 4 46 0x0D4C 12
64. Edit Paste View E t IN x Test Read Import New Station Forward Backward paete IB IL 24 DO 16 Ethernet Device IL 24 DO 2 24 8 IB IL 24 DO 4 8 IB IL 24 D0 8 L24D0 16 IB IL 24 EDI 2 DESINA 8 IB IL 24 EDI 2vxx L 24 DI 16 IB IL 24 SEG ELF 8 IB IL 24 SEG F D LAO 1 SF IB IL 24 230 DOR 15 LAO 2 U BP IB IL Al 2 SF L AO 1 SF IB IL AO 1 SF __ i Press F1 For Help 2 Figure 2 7 browser screen 2 10 2 Configurator OPC Data Exchange Process data exchange via OPC is supported in an very easy to use manner OPC items are assigned to the Inline station structure for the relevant terminal points using 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 coupler type using the OPC configurator 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 22 PHCENIX 615605 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 server provide the application program or the visualization with direct access to the process data for the bus configuration Robot C
65. Inactive Active A valid configuration is set to the READY state Process data Figure 3 7 can only be exchanged if the station was set to the RUN state page 3 10 by means of firmware commands Active Inactive The connected configuration is stored as the reference Figure 3 8on configuration The station is set to the RUN state Process data page 3 11 exchange is not possible Active Active A physical configuration is stored as the reference configuration Figure 3 9 and set to the READY state Process data can only be page 3 11 exchanged if P amp P mode is inactive and the station was set to the RUN state by means of firmware commands 615605 PHCENIX 952 FL IL 24 BK PAC UM E 3 5 4 Startup Diagrams of the Bus Coupler Normal mode P amp P mode and expert mode inactive Read connected configuration Operable configuration Configuration reference configuration 61560023 Figure 3 6 Normal mode expert mode and P amp P mode inactive P amp P mode inactive expert mode active Read reference configuration Station in READY state Display 61560024 Figure 3 7 P amp P mode inactive expert mode active PHCEN IX 615605 CONTACT Driver Software P amp P mode active expert mode inactive Read connected configuration Operable configuration Ye Save as refernce configuration Configuration
66. Inline Modules 1 47 1133 Mounting inhaerere 1 48 1 43 4 Removing uie eri eh eed eels 1 50 1 135 Replacing a Fuse ue 1 52 615605 PHCENIX Table of Contents 2 Startup Operation 2 5 2 6 2 7 2 8 Grounding an Inline Station senes 1 54 1 14 1 Shielding an Inline Station 1 56 1 14 2 Shielding Analog Sensors and Actuators 1 56 Connecting Cables ote et ed aha eoe oU Per ut 1 59 1 15 1 Connecting Unshielded Cables 1 59 1 15 2 Connecting Shielded Cables Using the Shield Connector 1 61 Connecting the Voltage Supply seen 1 64 1 16 1 Power Terminal Supply 1 64 1 16 2 Provision of the Segment Voltage Supply at Power Terminals esses 1 65 1 16 3 Demands on the Power Supply Units 1 65 Connecting Sensors and Actuators 1 66 1 17 1 Connection Methods for Sensors and Actuators 1 66 1 17 2 Connection Examples for Digital I O Modules 1 67 nS 2 3 Default Upon Delivery Default Settings 2 3 Firmware Start uie isi d usb eie tuere eoe Due v 2 3 Transmitting BootP Requests
67. Macros 3 60 3 12 1 Macros for Converting the Data Block of a Command 3 61 3 12 2 Macros for Converting the Data Block of a Message 3 63 3 12 3 Macros for Converting Input Data 3 65 3 12 4 Macros for Converting Output Data 3 66 Diagnostic Options for Driver Software 3 68 3193 Introduction eene Re 3 68 Positive Messages nennen nennen 3 69 Error Messages ie r tee 3 70 3 15 1 General Error Messages 3 70 3 15 2 Error Messages When Opening a Data Channel 3 72 3 15 3 Error Messages When Transmitting Messages Commands sse 3 73 3 15 4 Error Messages When Transmitting Process Data 3 75 Example Prograr uci s estet ee e ee eL 3 78 3 16 4 Demo Structure Startup 3 78 3 16 2 Example Program Source Code 3 80 PER E 4 3 OVEWIOW ies iii eel E ig t ee LE as 4 3 4 1 1 Services Available in Both Operating Modes 4 3 4 1 2 Services Available Only in Expert Mode 4 4 Notes on Service Descriptions 4 4 4 2 1 Name of the Service Service
68. 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 required 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 clamps Order No 12 01 44 2 EUM 615605 PHCENIX c CONTACT FL IL 24 BK PAC UM E 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 coupler and must not be ordered separately 1 13 3 Mounting When mounting a module proceed as follows Figure 1 29 e First snap on the electronics base which is required for mounting the station
69. Node handle MXI or DTI for the bus coupler on which the NetFail status is to be reset 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 IBDDIRET ddiRet ddiRet ETH ClrNetFailStatus ddiHnd 615605 PHCENIX 3 49 CONTACT FL IL 24 BK PAC UM E Task ETH SetNetFailMode 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 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 Syntax Parameters Format of the T ETH NET FAIL MODE IBDDIRET IBDDIFUNC ETH SetNetFailMode IBDDIHND nodeHd T ETH NET FAIL MODE netFa
70. PHCENIX CONTACT 3 25 FL IL 24 BK PAC UM E Task Syntax Parameters Return value 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 The function is assigned the node handle and two pointers to 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 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 coupler 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 coupler IBDDIRET IBDDIFUNC DDI DTI ReadWriteData IBDDIHND nodeHd T DDI DTI ACCESS writeDTIAcc DDI DTI ACCESS readDTIAcc IBDDIHND nodeHd Node handle DTI for the connection to which data is to be written The node handle also determines the bus coupler which is to be accessed DDI DTI ACCESS writeDTIAcc Pointer to a T DDI DTI ACCESS data structure with the parameters f
71. PhoenixContact MIB contains manufacturer information The pxcModules OID 1 3 6 1 4 1 4346 1 and pxcGlobal OID 1 3 6 1 4 1 4346 2 groups are described in this private Phoenix Contact MIB OID 1 3 6 1 4 1 4346 MIB structure 1 pxcModules 1 pxcRootModule 2 pxcGlobal 1 pxcBasic 1 pxcBasicName 2 pxcBasicDescr 3 pxcBasicURL 2 30 PHCENIX 615605 CONTACT Startup Operation pxcBasicName OID 1 3 6 1 4 1 4346 2 1 1 Syntax Display string Access Read Description Contains the manufacturer name Phoenix Contact GmbH amp Co KG pxcBasicDescr OID 1 3 6 1 4 1 4346 2 1 2 Syntax Display string Access Read Description Contains the manufacturer name and address Phoenix Contact GmbH amp Co KG P O Box 1341 D 32819 Blomberg pxcBasicURL OID 1 3 6 1 4 1 4346 2 1 3 Syntax Display string Access Read Description Contains the URL of the manufacturer http Awww phoenixcontact com 2 12 1 2 FL MIB The FL MIB contains information about the Factory Line product group This private FL MIB OID 1 3 6 1 4 1 4346 describes the pxcFactoryLine OID 1 3 6 1 4 1 4346 11 group MIB structure 1 pxcModules 2 pxcFLModule 11 pxcFactoryLine 1 flGlobal 1 flBasic 1 flBasicName 2 flBasicDescr 3 flBasicURL 4 flBasicCompCapacity 615605 PHGNIX 2 31 CONTACT FL IL 24 BK PAC UM E 2 flComponents 1 flComponentsTable 1 flComponentsEntry 1 flCo
72. Store a new reference configuration the same Create Configuration 8A Process data watchdog Safe operation of the station e g due to triggered excessive network load can no longer be guaranteed A station reset must be carried out bF Bus error the bus was stopped Check the INTERBUS devices Get Diag Info due to an error nF Network error Check the Ethernet connection Process data watchdog activated nC No MODBUS client connected Check the Ethernet connection to bus coupler no process data The application program was stopped watchdog active PF I O error The I O error must be removed and acknowledged via DDI or web page Display in Modbus TCP Operation On the 7 segment display a connected Modbus TCP device is indicated by a decimal point If the connection to a Modbus TCP device fails and no other error is present nC not connected is displayed In addition the bus coupler activates the fault response mode specified by the user If no Modbus TCP connections was activated neither a decimal point nor nC are displayed 2 46 615605 PHCENIX CONTACT Startup Operation If several errors occur at the same time the error with the highest priority is displayed For the priority of the individual errors please refer to the following table Table 2 7 Priority of the error messages Priority Display Meaning 1 8x Firmware error 2 bF Bus
73. Syntax Octet string 6 Access Read Description Contains the creation time of the firmware version as a string Example for 14 10 20 0x31 0x34 0x31 0x30 0x32 0x30 2 38 PHCEN IX 615605 CONTACT Startup Operation fIWorkFWInfoCopyright OID 1 3 6 1 4 1 4346 11 11 11 1 5 Syntax Display string 6 Access Read Description Contains the owner of the firmware copyright Copyright by Phoenix Contact GmbH amp Co KG 2000 fIWorkFWiInfoBootVersion OID 1 3 6 1 4 1 4346 11 11 11 1 6 Syntax Octet string 4 Access Read Description Contains the version of the Boot loader as a string Example for version 2 65 0x32 0 2 0x36 0x35 flWorkFWInfoBootState OID 1 3 6 1 4 1 4346 11 11 11 1 7 Syntax Octet string 6 Access Read Description Contains the Boot loader release as a string Example for beta 0x62 0x65 0x64 0x61 flWorkFWInfoBootDate OID 1 3 6 1 4 1 4346 11 11 11 1 8 Syntax Octet string 6 Access Read Description Contains the creation date of the Boot loader version as a string Example for 09 03 2001 0x30 0x39 0x30 0x33 0x30 0x31 flWorkFWInfoBootTime OID 1 3 6 1 4 1 4346 11 11 11 1 7 Syntax Octet string 6 Access Read Description Contains the creation time of the Boot loader version as a string Example for 14 10 20 0x31 0x34 0x31 0x30 0x32 0x30 615605 PHCENIX 2 39 CONTACT FL IL 24 BK PAC UM E fIWorkFWiInfoBootStatus OID 1 3 6 1 4 1 4346 11 11 11 1 11 Syntax Integer Access R
74. The node handle must also be assigned to a process data channel otherwise an appropriate error message is generated by the bus coupler Syntax IBDDIRET IBDDIFUNC DDI DTI WriteData IBDDIHND nodeHd T DDI DTI ACCESS dtiAcc Parameter IBDDIHND nodeHd Node handle DTI for the connection to which data is to be written The node handle also determines the bus coupler which is to be accessed T DDI DTI ACCESS dtiAcc Pointertoa 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 Format of the typedef struct T DDI DTI USIGN16 length ACCESS structure Amount of data to be written in bytes USIGN16 address Address in the DTI area byte address USIGN16 dataCons Desired data consistency area 3 24 PHCENIX 615605 CONTACT Driver Software Example 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 20x34 ddiRet DDI DTI WriteData ddiHnd amp dtiAcc if ddiRet ERR OK Error treatment 615605
75. Word 10 Frame IO Bit Count Word 11 Active IO Bit Count Word 12 Frame PCP Device Count Word 13 Active PCP Device Count Word 14 Frame PCP Word Count Word 15 Active PCP Word Count Bit uu nep iU M 0 3 structure Positive message during service request with Frame Reference gt 0000hex Start Entry No gt 0000 Word 1 Code Word 2 Parameter Count Word 3 Result Word 4 More Follows Word 5 Frame Reference Word 6 Used Attributes Word 7 Start Entry No Word 8 Entry Count Configuration Entry Negative message Word 1 Code Word 2 Parameter Count Word 3 Result Word 4 Add Error Info Bit poem A 0 Key Code 8309 44 Message code of the service confirmation Parameter Count Number of subsequent words with a positive message and if Frame Reference 0000pex XXXXhex 5 Configuration Count 4 22 PHCENIX 615605 CONTACT Firmware Services Result Add Error Info More Follows Frame Reference Current Configuration Configuration Count Frame Reference x Frame Device Count Active Device Count Frame IO Bit Count with a positive message and if Frame Reference gt 000044 and Start Entry No 0000 000Dhex 12 parameter words with a positive message and if Frame Reference gt 0000 and Start Entry No gt 0000 XXXXhex The value depends on the number of devices in the configuration frame an
76. address Digital output table Word 384 X X Word 1 VEG Word 191 Word 575 Analog input table Modbus address XXXXXXXXXXXXXXX 192 Modbus address Analog output table 4 Word 576 K X XX XXX XXX HX K KX X X XX X X X X X X X X X X X X Word 193 4 9 4 Word 577 XX XXX XX XK XXXKXXY X X X X X X X X X X X X XK X X X Word 194 4 4 Word 578 X X X X X X X X XX XXXXXX Word 767 61560027 Word 383 Figure 6 1 Location of the data in input output modules 615605 PHCENIX 6 7 CONTACT FL IL 24 BK PAC UM E 6 3 3 Location of the Process Data in Dynamic Tables DI2 Al2 2 FL IL 24 BK PAC DO8 DO2 DI8 1 Ere reser CONTACT 100 88 ORCV 88 101100 aul py 5 Dynamic process data table Modbus address XXX XX Word 0 Word 1 XX KKK Word 2 x Word XXX XXX X r Word 4 CX Wore 5 Xx xxx xXx Word 6 XX Wore 7 XX XXX XX Word 8 x Word 9 61560028 Figure 6 2 Location of the process data in dynamic tables 6 8 PHGNIX 615605 CONTACT Modbus TCP Protocol 6 4 Applicable Functions The FL IL 24 BK PAC makes no distinction between Modbus register tables and Modbus input register tables they are identically mapped to all four FL IL 24 BK PAC 1 0 tables as we
77. 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 coupler 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 O Word 1 High Low High Low INTERBUS Byte Byte Byte Byte n n 1 n 2 n 3 Y Y Computer n n 1 n 2 n 3 5691A001 Figure 3 12 Assignment of the process data between the local bus and the computer systems 3 58 PHCENIX 615605 CONTACT Driver Software Host coprocessor board Application program Transmit buffer MOTOROLA format Receive buffer MOTOROLA format Output buffer MOTOROLA format buffer MOTOROLA Format Figure 3 13 Controller board IBS master board DDI MXI SndMessage DDI_MXI_ RCVMessage DDI DTI WriteData MPM MOTOROLA format ReadData 5691A00
78. as parameters After the routine has been called successfully the user can read the set NetFail mode from the structure If there are no additional parameters for this mode this is indicated by the numOfBytes structure component which contains the value zero in this case IBDDIRET IBDDIFUNC ETH GetNetFailMode IBDDIHND nodeHd T ETH NET FAIL MODE netFailModelnfo IBDDIHND nodeHd Node handle of a controller board from which information on the set NetFail mode is to be read T NET FAIL MODE netFailModelnfo Pointer to a T ETH NET 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 T 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 can be found in the IOCTRL H file 615605 PHCENIX eM CONTACT FL IL 24 BK PAC UM E 3 9 IN Process Data Monitoring Functions that automatically monitor the IN process data area for changes can be used to reduce the load on the Ethernet network In systems in which input signals only change slo
79. board The function is assigned a valid node handle for a DTI data channel and a pointer toa T ETH PD MON structure as parameters The T ETH PD IN MON structure contains all the information needed to parameterize the IN process 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 monitoring A bit that is not set 0 means that a change in the associated bit in the IN process data area is insignificant IBDDIRET IBDDIFUNC ETH ActivatePDInMonitoring IBDDIHND nodeHd T ETH PD IN MON infoPtr IBDDIHND nodeHd Node handle DTI for the controller board for which process data monitoring is to be activated T ETH PD IN MON infoPtr Pointer to a 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 0 ERR OK is returned Otherwise the return value is an error code 615605 PHCENIX id CONTACT FL IL 24 BK P
80. code 15 Read write register function code 23 6 5 1 Read Multiple Registers This command reads from 1 to 125 16 bit words from the Modbus register table Any part of the Modbus register table can be read using this function When reading the fault table however the entire table must be read The read multiple registers command has the following format Table 6 6 Read multiple registers Byte No Meaning BYTE 0 Function code 3 BYTE 1 2 Register table offset BYTE3 4 Word count 1 125 The response to the read multiple registers command has the following format Table 6 7 Response to read multiple registers Byte No Meaning BYTE 0 Function code 3 BYTE 1 Byte count of 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 6 8 Exception response to read multiple registers Byte No Meaning BYTEO Function code 0x83 BYTE 1 Exception response 2 6 10 PHCENIX 615605 CONTACT Modbus TCP Protocol 6 5 1 1 Examples 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 and AQ1 Register table offset 1024 and word count 64 returns the fault table Any c
81. error the bus was stopped due to an error 3 nF Network error the monitoring function detected an error Modbus TCP connection interrupted No process data control watchdog active PF error of the Inline modules PP Plug amp play mode activated nC No MODBUS client connected to bus coupler no process data watchdog active The differences on the display for DDI mode and Modbus TCP mode are shown in the following table The remedy in Modbus TCP mode corresponds to the remedy in DDI mode Table 2 8 Differences on the display in DDI mode and Modbus TCP mode DDI Mode Modbus TCP Mode Display Meaning Display Meaning Normal operation without errors Normal operation without errors Modbus TCP device connected bF Bus error bF Bus error one Modbus TCP device connected bF Bus error connection to Modbus TCP device interrupted nF Network error the monitoring function nC All Modbus TCP connections interrupted detected an error or the process data the connection was closed the cable has watchdog became active been removed or a communication error occurred No process data watchdog active PF I O error of the Inline modules nF Network error the monitoring function detected an error or the process data watchdog became active PP Plug amp play mode activated PF I O error of the Inline modules one Modbus TCP device connected PP Plug amp play mode activated one Modbus TCP device connected 615605 PHCENIX 2 47 CONT
82. 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 09055 Cause Incorrect parameters were entered when calling the function Remedy Check the specified parameters NO OBJECT 0907 Cause The object called does not exist Remedy Check the object called or select another UNKNOWN CODE 0918 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 0031pex error type and or error location registers cannot be read Additional info FFFF lncorrect parameters detected during Read Configuration INCORRECT PARACOUNT 090Anex Cause The number of parameters is incorrect Remedy Correct the number of parameters 615605 PHCENIX 4 51 CONTACT FL IL 24 BK PAC UM E ACTION HANDLER OVERLAP 091Dhex Cause Cannot read from or write to the EEPROM Additional info 0001 Write error Additional info 0002 Read error INCORRECT STATE 0A02nex Cause The called service is not permitted in the current status of the device Remedy Select another service or change the status of the devic
83. firmware interface 6 bytes Version of the start firmware 4 bytes Status of the start firmware 6 bytes Creation date of the start firmware 6 bytes Creation time of the start firmware 6 bytes Order No of the controller board 8 bytes Order designation of controller board 30 bytes Motherboard identification e g 32 43 for 2C 4 bytes Version of the hardware 2 bytes Manufacturer of the controller board 20 bytes 615605 PHCENIX Las CONTACT FL IL 24 BK PAC UM E HW Serial No Serial number of the controller board 12 bytes HW Date Creation date of the controller board 6 bytes 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 0905 INCORRECT PARAMETER 4 51 090744 NO OBJECT 4 51 0918454 UNKNOWN CODE 4 51 092244 ACTION HANDLER CONFLICT 4 51 090Anex INCORRECT PARACOUNT 4 51 091Dhex ACTION HANDLER OVERLAP 4 52 OA02nex INCORRECT STATE 4 52 OA18hex INCORRECT ATTRIB 4 52 0A19 ex FRAME NOT SO BIG 4 52 OA22hex INCORRECT TN NUMBER 4 52 OA2Frex DEVICE ZERO 4 52 OA51hex INCORRECT FRAME REF 4 52 0 22 INTERNAL TIMEOUT 4 53 2 FUNCTION REG NOT FREE 4 53 0 24 ACTION ERROR 4 53 4 50 PHGNIX 615605 CONTACT Firmware Services 4 6 2 Positive Messages ERR OK 0000 Meaning After successful
84. get in touch with Phoenix Contact 3 74 PHCENIX 615605 CONTACT Driver Software 3 15 4 Error Messages When Transmitting Process Data These errors only occur when accessing the data interface DTI ERR AREA EXCDED 00965 Meaning Access exceeds the upper limit of the selected data area Cause 1 The data record to be read or written is too large The function can read a maximum of 4 kbytes in one call Remedy Only read or write data records with a maximum size of 4 kbytes Cause 2 The upper area limit 4 kbytes over the start of the device area has been exceeded Remedy 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 Cause An invalid value was entered for data consistency 1 2 4 or 8 bytes Remedy Specify a permissible data consistency with one of the following constants DTI DATA BYTE Byte data consistency 1 byte DTI DATA WORD Word data consistency 2 bytes DTI DATA LWORD Double word data consistency 4 bytes DTI DATA 64BIT 64 bit data consistency 8 bytes ERR PLUG PLAY 00 9 Cause An attempt was made to gain write access to process data in plug amp play mode This is not permitted for security reasons Remedy Deactivate plug amp play mode using the Set Value command with the value 0 or switch to read access ERR STATE CONFLICT 0100 Cause A service was called which is not p
85. mailbox connection Error code d ret SER PHCENIX CONTACT 615605 Driver Software 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 when creating data channel connection Error code d ret printf n TEST ABORTED fflush stdout return 111 else printf NnData channel connection OK Handle d dtiHnd return 0 kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkki DeleteConnection FUNCTION PE Parameters NONE Return value INTEGER 0 for OK 111 for error E S EEK k k k k k k k k k k k k k KR RK k k k RR RK RR k k k k k k RR RR RR RR k f int DeleteConnection void IBDDIRET ret Close mailbox channel ret DDI DevCloseNode mxiHnd if ret ERR OK printf nError when closing mailbox channel Error code d ret fflush stdout return 111 else printf nClose mailbox channel OK 615605 PHCENIX 3 81 CONTACT FL IL 24 BK PAC UM E Close data channel ret DDI_DevCloseNode dtiHnd if ret ERR OK printf nError when closing data channel Error code d ret fflush stdout return 111 else printf nClose data channel OK
86. multiple registers Byte No Meaning BYTE 0 Function code 0x90 BYTE 1 Exception word 2 6 5 2 1 Examples for Write Multiple Registers Register table offset 384 and word count 2 writes the register values into 96Q1 32 Register table offset 2 575 and word count 2 writes the register values into Q3057 3072 and AQ1 Any combination of the register table offset and the word count that accesses an offset 384 or gt 767 produces an exception response 6 5 3 Read Coils This command reads bits 1 to 2000 from the Modbus register table The read coils command has the following format Table 6 12 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 6 13 Response to read coils Byte No Meaning BYTE 0 Function code 1 BYTE 1 Byte count of response byte count B bit count of command 7 8 BYTE 2 B 1 Bit values the least significant bit is the first coil 6 12 PHGNIX 615605 CONTACT Modbus TCP Protocol If the command accesses an invalid offset or contains an invalid length an exception response in the following format is output Table 6 14 Exception response to read coils Byte No Meaning BYTE 0 Function code 0x81 BYTE 1 Exception word 2 6 5 3 1 Examples for Read
87. of a word starting with the low order byte 3 67 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 Macros for Converting the Data Block of a Command IB SetCmdCode n m Task This macro converts a command code 16 bit into Motorola format and enters it in the specified transmit buffer Parameters n USIGNB Pointer to the transmit buffer m USIGN16 Command code to be entered IB SetParaCnt n m Task 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 Parameters n USIGNSB Pointer to the transmit buffer m USIGN16 Parameter count to be entered 615605 PHCENIX vel CONTACT FL IL 24 BK PAC UM E Task Parameters Task Parameters Task Parameters Task Parameters Return value IB SetParaN This macro converts parameter 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 n USIGNB Pointer to the transmit buffer m USIGN16 Parameter number counting starts with 1 0 USIGN16 Parameter value to be entered IB SetParaNHiByte n m o This m
88. of the supply voltage 1 7 Figure 1 4 Basic structure of an Inline module 1 16 Figure 1 5 Inline connector types 1 17 Figure 1 6 Internal structure of the connectors 1 19 Figure 1 7 Connector 1 20 Figure 1 8 Function identification 8 1 21 Figure 1 9 Terminal point numbering 1 22 Figure 1 10 Labeling 1 23 Figure 1 11 Dimensions of the electronics bases 2 slot housing 1 24 Figure 1 12 Dimensions of the electronics bases 4 slot housing 1 25 Figure 1 13 Dimensions of the electronics bases 8 slot housing 1 25 Figure 1 14 Connector dimensions see 1 26 Figure 1 15 Potential and data routing sees 1 27 Figure 1 16 Typical connection of the supply voltage 1 30 Figure 1 17 Logic and analog circuit 2 1 31 Figure 1 18 Main CIF CUIL icc Eu e eei e utes 1 32 Figure 1 19 Segrrient clrcuil cde aee 1 34 Figure 1 20 Potential areas in the bus coupler two voltage supplies 1 36 Figure 1 21 Bus coupler potentials one voltage supply 1 37 Figure 1 22 Power connector for supply from a single power supply unit sner nerne nennen 1 37 Figure 1 23 E
89. on s by selecting Add Device from the Device View context menu or by using the Ctrl A key combination Enter the desired data under Description and TCP IP Address Activate the BootP Parameter by selecting Reply on BootP Requests Enter the MAC address It can be found the sticker on the front of the housing Savethe configuration settings and restart the device reset key or power up The device now transmits another BootP request and receives the specified IP parameters from the BootP server 2 6 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 615605 PHCENIX 2 5 FL IL 24 BK PAC UM E 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 Bit1 Bit2 Bit3 Bit4 Bit 5 Class A 0 Class 1 0 5 1 1 0 Class
90. page of this component with additional information flWorkComponentsDevSign OID 1 3 6 1 4 1 4346 11 11 2 1 1 4 Syntax INTEGER 0 255 Access Read Description Contains the index entry of the component flWorkComponentsPowerStat OID 1 3 6 1 4 1 4346 11 11 2 1 1 5 Syntax INTEGER Access Read Description Contains status information about the connected supply voltages Unknown 1 No voltage present 2 Supply voltage 1 OK 3 Supply voltage 2 OK 4 Supply voltages 1 and 2 OK 5 615605 PHCENIX 2 37 CONTACT FL IL 24 BK PAC UM E flWorkComponentsStrongReset OID 1 3 6 1 4 1 4346 11 11 2 1 1 11 Syntax INTEGER Access Read write Description With write access a reset can be executed with 2 With read access the value is always 1 no reset fIWorkFWiInfoVersion OID 1 3 6 1 4 1 4346 11 11 11 1 1 Syntax Octet string 4 Access Read Description Contains the firmware version as a string Example for version 3 97 0x33 0 2 0x39 0x37 fIWorkFWiInfoState OID 1 3 6 1 4 1 4346 11 11 11 1 2 Syntax Octet string 6 Access Read Description Contains the firmware release as a string Example for beta 0x62 0x65 0x64 0x61 flWorkFWInfoDate OID 1 3 6 1 4 1 4346 11 11 11 1 3 Syntax Octet string 6 Access Read Description Contains the creation date of the firmware version as a string Example for 21 05 2001 0x32 0x31 0x30 0x35 0x30 0x31 fIWorkFWiInfoTime OID 1 3 6 1 4 1 4346 11 11 11 1 4
91. structure Possible values for the status structure component Example IBDDIHND nodeHd Node handle MXI or DTI for the bus coupler on which the NetFail status is to be read NET FAIL netFaillnfo Pointer to a structure which contains the 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 typedef struct USIGN16 status NetFail status USIGN16 reason Reason for the NetFail T ETH NET FAIL ETH NET FAIL ACTIVE OxFFFF NetFail triggered See also Reasons for Fault Response on page 3 34 ETH NET FAIL INACTIVE 0x0000 NetFail signal not triggered Unix Windows NT 2000 IBDDIHND ddihnd IBDDIRET ddiRet T ETH NET FAIL netFailInfo USIGN16 nfStatus USIGN16 nfReason ddiRet ETH GetNetFailStatus ddiHnd amp netFailInfo if ddiRet ERR OK nfStatus netFailInfo status nfReason netFailInfo reason 3 48 PHCEN IX 615605 CONTACT Driver Software 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 MXI data channel as a parameter Syntax IBDDIRET IBDDIFUNC ETH CirNetFailStatus IBDDIHND nodeHd Parameter IBDDIHND nodeHd
92. terminal 24 V DC with fuse and diagnostics 28 61904 IB IL 24 SEG ELF Segment terminal 24 V DC with electronic fuse 27 27 789 1 14 615605 PHCENIX CONTACT FL IL 24 BK PAC Table 1 7 Power and segment terminals Designation Properties Order No IB IL 24 SEG ELF PAC Segment terminal 24 V DC with electronic fuse 28 61409 IB IL PD GND Terminal for GND potential distribution 28 63 06 7 IB IL PD GND PAC Terminal for potential distribution GND 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 Table 1 8 Safety Designation Properties Order No IB IL 24 SAFE 1 Safety terminal with 2 N O contacts 27 40 782 IB IL 24 SAFE 1 PAC Safety terminal with 2 N O contacts 28 61564 IB IL 400 SAFE 2 Safety terminal with 3 N O contacts and 1 contact 200 V AC 2740795 to 600 V AC Table 1 9 Controller CPU Designation Properties Order No ILC 200 UNI Inline Controller with INTERBUS local bus interface 27 30 90 9 ILC 200 UNI PAC Inline Controller with INTERBUS local bus interface 28 62 29 1 IB IL 332 128 Inline CPU 28 19 134 IB IL 332 128 PAC Inline CPU 28 61 739 IB IL 332 256 Inline CPU with 256 kbytes RAM 1 MB flash serial interface 28 19 325 IB IL 332 256 PAC Inline CPU with 256 kbytes RAM 1 MB flash serial interface 28 61810 615605 1
93. 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 USIGN8 Pointer to the input buffer m USIGN16 Word number USIGNS 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 This macro converts a double word 32 bit to Motorola format and writes it to the specified position in the output buffer The word index in the output buffer is used as the position The macro writes the double word starting from the specified word address over two words n USIGNS m USIGN16 USIGN32 Pointer to the output buffer Word number Process data 32 bit IB_PD_SetDataN n This macro converts a word 16 bit to Motorola format and writes it to the specified position in the output buffer n USIGN8 m USIGN 16 o USIGN16 Pointer to the output buffer Word number Process data 16 bit 3 66 615605 PHCENIX CONTACT Driver Software Task Parameters Task Parameters Task Parameters Return value IB PD SetDataNHiByte n m o 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 ou
94. the physical bus configuration Only relevant if Used Attributes Attributes to be read Frame Reference The parameter is a 16 bit field in which every bit gt 0000hex corresponds to attribute Set the corresponding bit to 1 on the attributes to be read Settings for the Used Attributes parameter Bit 0 Device number Bit 1 Device code 4 20 PHCENIX 615605 CONTACT Firmware Services Syntax 1 structure Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 7 Word 8 2 structure Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 7 Word 8 Word 9 Start Entry No Position of the first entry 0000hex 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 Frame Reference 0000 Start Entry No Not relevant 0000hex 00005 Positive message during service request with Frame Reference gt 0000 Start Entry No 0000hex gt 0000 ex Not relevant 0000hex 615605 PHCENIX T CONTACT FL IL 24 BK PAC UM E
95. to write multiple registers 6 11 Table 6 11 Exception response to write multiple registers 6 12 Table 6 12 Fiead colls iiie e Hte e Ohba detente 6 12 Table 6 13 Response to read coils 6 12 Table 6 14 Exception response to read 6 13 Table 6 15 Read input 6 13 Table 6 16 Response to read input 6 13 Table 6 17 Exception response to read input 6 14 Table 6 18 Read input 6 14 Table 6 19 Response to read input 6 14 Table 6 20 Exception response to read input registers 6 15 Table 6 21 Whrite COllS secret t 6 15 Table 6 22 Response to write coils 6 15 Table 6 23 Exception response to write 6 15 Table 6 24 Write single register 2 22222221 6 16 Table 6 25 Response to write single 6 16 Table 6 26 Exception response to write single register 6 16 Table 6 27 Read exception 2 6 17 Table 6 2
96. to 40hex for an Inline station Attribute Device Code Length Code The length code refers to the address space required by the INTERBUS device in the host ID Code The ID code describes the INTERBUS device function It is printed as Module Ident in decimal notation on the modules 615605 PHCENIX 4 25 CONTACT FL IL 24 BK PAC UM E 4 3 8 Complete Read Configuration Service Task 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 Remark This service can be understood as a meta service for the Read Configuration service 0309 The Start Entry No parameter does not need to be specified since this service reads all entries of the configuration frame Start Entry 1 Syntax Complete Read Configuration Request 030Bhex Word 1 Word 2 Word 3 Bit oper 0 Key Code 030Bhex Command code of the service request Parameter Count Number of subsequent words 0001 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 attributes to be read Settings for the Used Attributes parameter Bit 0 Device number Bit 1 Device code 4 26 PHCEN IX 615605 CONTACT Firmware Services Syntax Complete Read Configuration Confirmation 830B Positive m
97. 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 62 9 and diagnostics IB IL 24 EDI 2 DESINA 2 inputs 4 wire termination according to Desina specification with 27 40 32 6 electronic overload protection and diagnostics IB IL 24 2 inputs 4 wire termination according to Desina specification with 28 61522 EDI 2 DESINA PAC electronic overload protection and diagnostics IB IL 24 DI 4 4 inputs 3 wire termination 24 V DC 27 26 214 IB IL 24 DI 4 PAC 4 inputs 3 wire termination 24 V DC 28 61 23 4 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 43 9 according to EN 61131 2 Type 2 IB IL 24 DI 8 T2 PAC 8 inputs 4 wire termination 24 V DC 28 62 204 according 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 termination 28 63 520 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 83 5 IB IL 120 DI 1 1 input 3 wire termination 120 V AC 28
98. with 24 V DC 120 V AC or 230 V AC 1 64 PHGNIX 615605 CONTACT FL IL 24 BK PAC If these instructions are not followed there is a danger of damage to health or even of a life threatening injury 1 16 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 16 3 Demands on the Power Supply Units En MI 615605 PHCENIX 1 65 CONTACT FL IL 24 BK PAC UM E 1 47 Connecting Sensors 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 15 1 on page 1 59 and the shielded cable as described in Section 1 15 2 on page 1 61 1 17 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 Because of the dif
99. 09 492 a laser printer marker pen or CMS system 72 strips 1 pcs package Insert strips for IB IL FIELD 8 perforated can be labeled using ESL 62X46 08 09 502 a laser printer marker pen or CMS system 15 strips 5 pcs package 615605 PHCENIX 7 11 CONTACT FL IL 24 BK PAC UM E Description Order Designation Order No DIN EN 50022 DIN rail 2 meters 6 56 ft NS 35 7 5 gelocht 0801733 NS 35 7 5 ungelocht 0801681 End clamp snapped on without tools CLIPFIX 35 3022218 50 pcs package End clamp fixed using screws E UK 1201442 50 pcs package Screwdriver according to DIN 5264 blade SZF 1 0 6 x 3 5 1204517 width 3 5 mm 0 138 in Phoenix Contact amp Co Flachsmarktstr 8 32825 Blomberg Germany 49 0 52 35 3 00 2 49 0 52 35 3 4 12 00 www phoenixcontact com e Worldwide Locations www phoenixcontact com salesnetwork HOTLINE If problems occur which cannot be solved with the help of this documentation please contact our hotline 49 0 52 35 3 4 18 88 factoryline service phoenixcontact com ef 7 12 PHCENIX CONTACT 615605 Reference Data Appendix A A1 Table of Figures Section 1 Figure 1 1 Front view of the FL IL 24 BK PAC 1 4 Figure 1 2 Structure of the FL IL 24 BK PAC bus coupler 1 5 Figure 1 3 Typical connection
100. 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 be used on networked POs 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 complete testing should be carried out separately using the ping function 615605 PHCENIX er CONTACT FL IL 24 BK PAC UM E 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
101. 2 Using the macros for programming support 615605 PHCENIX CONTACT 3 59 FL IL 24 BK PAC UM E 3 12 Description of the Macros Table 3 9 Driver software macros Macro Task Page IB SetCmdCode Enters the command code 16 bit in the specified transmit buffer 3 61 IB SetParaCnt Enters the parameter count 16 bit in the specified transmit buffer 3 61 IB SetParaN Enters a parameter 16 bit in the specified transmit buffer 3 62 IB SetParaNHiByte Enters the high order byte bit 8 to 15 of a parameter in the specified 3 62 transmit buffer IB SetParaNLoByte Enters the low order byte bit O to 7 of a parameter in the specified 3 62 transmit buffer IB SetBytePtrHiByte Returns the address of a parameter entry starting with the high order 3 62 byte bit 8 to 15 IB SetBytePtrLoByte Returns the address of a parameter entry starting with the low order 3 63 byte bit O to 7 IB GetMsgCode Reads a message code 16 bit from the specified receive buffer 3 63 IB GetParaCnt Reads the parameter count 16 bit from the specified receive buffer 3 63 IB GetParaN Reads a parameter 16 bit from the specified receive buffer 3 63 IB GetParaNHiByte Reads the high order byte bit 8 to 15 of a parameter from the 3 64 specified receive buffer IB GetParaNLoByte Reads the low order byte bit O to 7 of a parameter from the 3 64 specified receive buffer IB Get
102. 2 CONNECTS an 2 cie ie Ecke ae 1 17 1 7 Function Identification and Labeling 1 21 1 8 Dimensions of Low Level Signal 1 24 1 9 Electrical Potential and Data 1 27 1 10 Circuits Within an Inline Station and Provision of the Supply Voltages i tope RR eR CRINE 1 29 1 10 1 Supply of the Ethernet Bus 1 30 1 10 2 Logic Circuit UL cc osa tecto dd 1 30 1 10 3 Analog Circuit 3 1 31 1 10 4 Main Circuit Uy 1 10 5 Segment Circuit 1 11 Voltage Goncept cede i Pee eit reed des 1 12 Diagnostic and status 1 42 1 12 1 LEDs on the Ethernet Bus 1 42 1 12 2 Indicators on the Supply 1 44 1 12 3 Indicators on the Input Output Modules 1 45 1 12 4 Indicators on Other Inline 1 46 615605 PHCENIX i CONTACT FL IL 24 BK PAC UM E Mounting Removing Modules and Connecting Cables 1 47 1 13 1 Installation Instructions ee 1 47 1 13 2 Mount
103. 3 CONTACT FL IL 24 BK PAC UM E Table 3 2 System parameters for the Set Value service 75054 Variable ID System Parameter Value Comment 2240hex Plug amp play mode 0 Plug amp play mode inactive 1 Plug amp play mode active takes effect after reboot 2275hex Expert mode 0 Expert mode inactive default Expert mode active 2277 Fault response mode 1 Fault reset mode default 2 Hold last state 0 Standard fault mode 2293hex Process data monitoring timeout 0 Process data watchdog inactive 200 65000 Timeout value 3 14 PHCENIX 615605 CONTACT Driver Software 3 7 Description of the Device Driver Interface DDI Introduction The Device Driver Interface DDI is provided for using the bus coupler services The functions of the DDI are combined in a library which must be linked 3 7 1 Overview Table 3 3 Overview of the functions in the DDI Functions Page DDI DevOpenNode 3 18 DDI DevCloseNode 3 20 DDI DTI ReadData 3 22 DDI DTI WriteData 3 24 DDI_DTI_ReadWriteData 3 26 DDI_MXI_SndMessage 3 28 DDI_MXI_RcevMessage 3 30 GetlBSDiagnostic 3 32 ETH SetHostChecking 3 38 ETH ClearHostChecking 3 40 SetDTITimeoutCtrl 3 42 ETH ClearDTITimeoutCtrl 3 43 ETH SetNetFail 3 47 ETH GetNetFailStatus 3 47 ETH_ClrNetFailStatus 3 49 DDI_SetMsgNotification 3 52 DDI_ClrMsgNotification 3 52
104. 3 is displayed and process data cannot be exchanged for safety reasons However to operate the bus there are two possibilities 1 Restore the original configuration again in order for the reference configuration to match the physical configuration 2 Activate P amp P mode in order for the known physical configuration to be stored as the reference configuration 3 8 PHCEN IX 615605 CONTACT Driver Software IS Expert mode inactve Expert mode active 3 5 2 Expert Mode If expert mode is inactive default upon delivery an error free configuration is automatically set to the RUN state If the configuration has a technical fault or if it does not match the reference configuration 83 is displayed and process data cannot be exchanged If expert mode is active an error free configuration is set to the READY state but not automatically to the RUN state The station must be set to the RUN state using appropriate firmware commands such as ACTIVATE CONFIGURATION 0 0711 or START DATA TRANSFER 0 0701 3 5 3 Possible Combinations of the Modes Table 3 1 Possible combination of the modes and their effect P amp P Mode Expert Description Effect Diagram Mode Inactive Inactive Normal status If the connected configuration matches the Figure 3 6 on configuration in the memory the station sets the valid page 3 10 configuration to the RUN state Process data exchange is possible
105. 31 Replacing a fuse 615605 PHCENIX 1 53 CONTACT FL IL 24 BK PAC UM E 1 14 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 Ethernet bus coupler The bus coupler power terminals and segment terminals have FE springs metal and supply terminals clips on the bottom 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 to ensure reliable grounding even if the DIN rail is dirty or the metal clip has grounding 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 61560008 Figure 1 32 Additional grounding of the FL IL 24 BK PAC 1 54 PHCENIX 615605 CONTACT FL IL 24 BK PAC 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 gr
106. 6 11 11 11 11 1 2 42 PHCEN IX 615605 CONTACT Startup Operation Syntax INTEGER Access Read write Description The current configuration can be saved in the EEPROM Do not save configuration 1 has no effect Save configuration 2 With read access the value is always 1 615605 PHCENIX 2 43 CONTACT FL IL 24 BK PAC UM E 2 13 Meaning of the 7 Segment Display Table 2 2 During startup operation Display Meaning 01 Boot loader is started BootP requests are sent bo Firmware is extracted 02 Firmware is started Operating Table 2 3 Additional information Display Meaning PP P amp P mode is activated Table 2 4 During firmware update Display Meaning 03 The firmware is downloaded from the tftp server 04 The firmware is downloaded to the memory 05 The firmware transfer to the memory is complete 2 44 PHCENIX 615605 CONTACT Startup Operation Table 2 5 Boot loader error messages Display Meaning Remedy 17 The transfer of the firmware failed Check the physical connection during tftp download display Establish a point to point connection changes from 03 to 17 Make sure that the file with the specified file name exists and is in the correct directory Check the IP address of the tftp server Activate the tftp server Repeat the download Boot loader 1 80 Restart the bus c
107. 6 767 576 767 96AQ1 192 16 bit words 1024 1087 16 bit words 1024 1087 16 bit words Fault table 82 error x two 16 bit words per error 16 bit words 16 bit words 1280 1280 Timeout table timeout value 16 bit words 16 bit words for connection monitoring 1400 1463 1400 1463 1400 INTERBUS devices From 1401 ID code of the corresponding device 2000 16 bit word 7 m D o o 9 2000 16 bit word Process data watchdog timeout 2002 16 bit word 2002 16 bit word Fault response mode 2004 16 bit word 2004 16 bit word NetFail reason 6020 6093 16 bit words 6020 6093 16 bit words 6 3 1 Dynamic Modbus TCP Process Data Table Table 6 4 Dynamic process data table Modbus Modbus Input Modbus Input Modbus Coil Internal FL IL 24 BK PAC Register Table Register Table Discrete Table Table Tables 8000 8192 8000 8192 Dynamic process data table 16 bit words 16 bit words 6 6 PHCENIX 615605 CONTACT Modbus TCP Protocol 6 3 2 Example Location of the Input Output Data DI2 AI2 AO2 FL IL 24 BK PAC DO8 DO2 DI8 AM AO1 Queer SE ero oca 8 onn orev oun bol YYAA Digital input table Modbus address Word 0 Modbus
108. 8 Answer to read exception 6 17 615605 PHCENIX 7 FL IL 24 BK UME Table 6 29 Table 6 30 Table 6 31 Table 6 32 Table 6 33 Table 6 34 Table 6 35 Table 6 36 Table 6 37 Table 6 38 Table 6 39 Table 6 40 Table 6 41 Table 6 42 Table 6 43 Table 6 44 Table 6 45 Table 6 46 Table 6 47 Table 6 48 Exception status data 6 17 Exception responses 6 18 Write multiple 8 6 19 Response to write multiple 6 19 Exception response to write multiple coils 6 19 Read Write register sssseeeeeeeennenne 6 20 Answer to read write register 22 6 20 Exception response to read write register 6 20 Structure of the analog output 6 22 Network interface command word 6 22 Structure of the input discretes table 6 23 Status Word usi pide hada ene tedio ties 6 23 Structure of the analog input 6 23 1 bet Uie e 6 24 eet tedio dies 6 25 Monitoring
109. 8 outputs with negative logic 500 mA 28 63546 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 27 42117 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 DC 27 26272 IB IL 24 DO 16 PAC 16 outputs 500 mA 3 wire termination 24 V DC 28 61 292 IB IL 24 DO 32 HD 32 outputs 500 mA 1 wire termination 24 V DC 28 60 934 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 wire termination 28 36 748 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 A 3 wire termination 27 42 69 6 IB IL DO 4 AC 1A PAC 1 output 12 V 253 V AC 1 A 3 wire termination 28 61658 IB IL 24 230 DOR 1 W 1 SPDT relay contact 5 V 253 V AC 3A 28 36 434 IB IL 24 230 DOR 1 W 1 SPDT relay contact 5 V 253 V AC 3A 28 61 88 1 PAC IB IL 24 230 DOR 1 W PC 1 SPDT relay contact 5 V 253 V AC 3 A for inductive and 28 60 400 capacitive loads IB IL 24 230 DOR 1 W 1 SPDT relay contact 5 V 253 V AC 3 A for inductive and 28 62 178 PC PAC capacitive loads 1 10 615605 PHCENIX CONTACT FL IL 24 BK PAC Tab
110. 862314 Ethernet Inline bus coupler FL IL 24 BK 28 31057 Connector with color print IB IL SCN 8 CP 27 27 608 Labeling field IB IL FIELD 8 2727501 End E UK 12 01 442 Zack Quick marker strip ZBFM 6 see CLIPLINE Factory Manager network management software FL SWT 28 31 044 FL SNMP OPC gateway software for information exchange FL SNMP OPC SERVER 28 32 166 between SNMP and OPC FL SNMP AGENT 28 32 179 OPC server IBS OPC SERVER 27 29127 CD ROM with user documentation in pdf format driver CD FL IL 24 BK 28 32 06 9 software example program and OPC configurator Configuring and Installing the INTERBUS Inline Product IB IL SYS PRO UM E 27 43048 Range user manual RJ45 gray connector set for linear cable 2 pieces FL PLUG RJ45 GR 2 27 44 856 RJ45 green connector set for crossed cable 2 pieces FL PLUG RJ45 GN 2 27 44 57 1 Double sheathed Ethernet cable FL CAT5 HEAVY 2744814 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 44513 Voltage supplies QUINT PS see INTERFACE catalog Keying profile 100 pcs package CP MSTB see COMBICON 17 34 634 catalog 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 labeled using ESL 62X10 08
111. 9 Basic Structure of Low Level Signal Modules 1 16 1 6 1 Electronics Base ned he pee ee 1 17 1 6 2 CODLGeCIOIS 3 nonet eee Gn 1 17 Function Identification and 48 11 1 21 Dimensions of Low Level Signal 1 24 Electrical Potential and Data 1 27 Circuits Within an Inline Station and Provision of the 1 29 1 10 1 Supply of the Ethernet Bus Coupler 1 30 1102 Logic Circuit UL e e 1 30 1 10 3 Analog Circuit UANA s 1 31 1 10 4 Main Circuit Up E 1 32 1 10 5 Segment Circuit 2 2 00 1 33 Voltage Concept eode einai 1 35 Diagnostic and status 1 42 1 12 1 LEDs on the Ethernet Bus Coupler 1 42 1 12 2 Indicators on the Supply Terminal 1 44 1 12 3 Indicators on the Input Output Modules 1 45 1 12 4 Indicators on Other Inline Modules 1 46 Mounting Removing Modules and Connecting Cables 1 47 1 13 1 Installation Instructions see 1 47 1 13 2 Mounting and Removing
112. A 1 10 3 Analog Circuit Uana The analog circuit with the supply for the analog modules also referred to as 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 Ugy The module I O 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 Upgy of the bus coupler The maximum current carrying capacity of Uana is 0 5 capacity FL IL 24 BK PAC PWR IN SEG F U Unna GNDL Us eee ee 4 Un 61560001 Figure 1 17 Logic and analog circuit FL IL 24 BK PAC Ethernet bus coupler PWR IN Power terminal SEG F Segment terminal with fuse as an example of a segment terminal 615605 PHCENIX 1 31 CONTACT FL IL 24 BK PAC UM E Function Voltage Current carrying capacity Provision of 1 10 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 circ
113. AC UM E Format of the data typedef struct structure 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 IN PD data USIGN32 timeout Timeout time in ms M T ETH PD IN MON Constants for the define ETH PD IN CHK INACTIVE 0x0000 PD In Check is not activated different modes define ETH PD IN CHK MODE UDP 0x0002 Send data over UDP port Description of the ETH PD IN CHK INACTIVE constants Not in use at present 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 WaitForPDiInIndication 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 T DDI DTI ACCESS structure The routine returns as soon as pro
114. ACT FL IL 24 BK PAC UM E 2 48 PHCENIX 615605 CONTACT Driver Software Section 3 This section provides information about 3 3 3 4 3 5 3 6 3 7 3 8 3 9 the driver software an example program rU pu tes se c E ENERO EE a eat ee cinta E E ER 3 3 Documentation eoe HER ue e ee le act alee 3 3 3 1 1 Hardware and Firmware User 3 3 Software Structure wwii ania di eet 3 3 3 2 1 Ethernet Inline Bus Coupler Firmware 3 4 3 2 2 Driver SoftWare sis dee taco d Ecc 3 4 Support and Driver 3 5 Transt rot VO Data dnd een o e ete eet 3 6 3 4 1 Position of the Process Data Example 3 7 Startup Behavior of the Bus 3 8 3 5 1 amp 3 8 3 5 2 Expert Gat te ae 3 9 3 5 3 Possible Combinations of the Modes 3 9 3 5 4 Startup Diagrams of the Bus 3 10 3 5 5 Changing and Starting a Configuration in P amp P Mode 3 12 Changing a Reference Configuration Using the Software 3 13 3 6 1 Effects of Expert Mode 3 13 3 6 2 Changing a Reference Configuration
115. BytePtrHiByte Returns the address of a parameter entry starting with the high order 3 64 byte bit 8 to 15 IB GetBytePtrL oByte Returns the address of a parameter entry starting with the low order 3 64 byte bit O to 7 IB PD GetLongDataN Reads a double word 32 bit from the specified position in the input 3 65 buffer IB PD GetDataN Reads a word 16 bit from the specified position in the input buffer 3 65 IB PD GetDataNHiByte Reads the high order byte bit 8 to 15 of a word from the input buffer 3 65 3 60 615605 PHCENIX CONTACT Driver Software Table 3 9 Driver software macros Macro Task Page IB PD GetDataNLoByte Reads the low order byte bit to 7 of a word from the input buffer 3 65 IB PD GetBytePtrHiByte Returns the address of a word starting with the high order byte 3 66 bit 8 to 15 IB PD GetBytePtrLoByte Returns the address of a word starting with the low order byte 3 66 bit O to 7 IB PD SetLongDataN Writes a double word 32 bit to the output buffer 3 66 IB PD SetDataN Writes a word 16 bit to the output buffer 3 66 IB PD GetDataNHiByte Writes the high order byte bit 8 to 15 of a word to the output buffer 3 67 IB PD GetDataNLoByte Writes the low order byte bit to 7 of a word to the output buffer 3 67 IB PD GetBytePtrHiByte Returns the address of a word starting with the high order byte 3 67 bit 8 to 15 IB PD GetBytePtrLoByte Returns the address
116. Cause Remedy Add Error Info Meaning Cause Remedy Add Error Info E PNM12 STATE CONFLICT 0B02 t may be that there is an empty configuration frame the first device after the bus coupler is faulty or missing Activate a correct configuration frame or Use the first device or an operational device E PNM12 DEVICE STATE OBB1 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 E PNM12 CONFIG MAU FAIL DO 0 20 Medium Attachment Unit MAU firmware component interruption of the data transmission Cable break on the data forward path of the incoming bus interface IN of the indicated Inline device Check the cables
117. 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 Any combination of the coil table offset and the bit count that accesses an offset gt 3072 produces an exception response 6 5 4 Read Input Discretes This command reads bits 1 to 2000 from the Modbus input discrete table The read input discretes command has the following format Table 6 15 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 6 16 Response to read input discretes Byte No Meaning BYTE 0 Function code 2 BYTE 1 Byte count of response B bit count of command 7 8 BYTE 2 1 Bit values the least significant bit is the first coil If the command accesses an invalid offset or contains an invalid length an exception response in the following format is output 615605 PHCENIX 6 13 CONTACT FL IL 24 BK PAC UM E Table 6 17 Exception response to read input discretes Byte No Meaning BYTE 0 Function code 0x82 BYTE 1 Exception code Examples for read digital inputs Input discrete table offset 0 and bit count 1 returns input discrete
118. D ue 7 3 7 1 Ordering Data eve ice 7 11 615605 PHCENIX 7 1 CONTACT FL IL 24 BK PAC UM E 7 2 PHCENIX 615605 CONTACT Technical Data 7 Technical Data General Data Function Ethernet Inline bus coupler Housing dimensions width x height x depth 90 mm x 116 mm x 72 mm 3 543 x 4 567 x 2 835 in Permissible operating temperature EN 60204 1 0 C to 55 4 32 F to 131 F Permissible storage temperature EN 60204 1 25 to 85 13 to 185 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 2000 m 6562 ft above sea level Air pressure storage 70 kPa to 108 kPa 3000 m 9843 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 compatibili
119. DS PD IN word 1 gt 14970 lt PD_IN gt PD IN word 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 lt IL MODULE PD OUT This area is used by all terminals with output data The use of bits is identical to the use of PD IN 2 7 5 2 Validity of Data The validity of data is identical to the validity via DDI or OPC access 2 7 5 3 Error in the Inline Station If the FL IL 24 BK PAC is not able to configure the connected Inline terminals correctly error code 82 is displayed The process data is then listed in the XML file as follows lt xml version 1 0 encoding SO 8859 1 gt IDOCTYPE IL STATION SYSTEM processdata dtd gt lt IL_STATION gt lt IL_BUS_TERMINAL gt TERMINAL gt IL 24 BK PAC lt TERMINAL_TYPE gt lt NAMES gt FL IL 24 BK PAC lt NAME gt IP ADDRESS 172 16 27 37 IP ADDRESS MODULE NUMBER20 MODULE NUMBER gt DIAGNOSTIC STATUS REGISTER 132 DIAGNOSTIC STATUS REGISTER DIAGNOSTIC PARAMETER REGISTER 65535 DIAGNOSTIC PARAMETER REGISTER IL BUS TERMINAL IL BUS IL BUS lt IL STATION 2 14 PHCENIX 615605 CONTACT Startup Operation The values of the diagnostic status register and the diagnostic parameter register indicate the error cause The number of the connected terminals is zero which means that the IL BUS area is empty In the event of a bus error is displayed
120. ENIX 615605 CONTACT Startup Operation 2 Startup Operation 2 1 Default Upon Delivery Default Settings By default upon delivery the following functions and properties are available The password is private The bus coupler has no valid IP parameters IP address 0 0 0 0 Subnet mask 0 0 0 0 Gateway 0 0 0 0 Plug amp play mode activated Expert mode inactive System description Ethernet bus coupler System contact unknown System name FL IL 24 BK System location unknown HW watchdog activated default parameter 0x00000001 No INTERBUS configuration stored All entries set to 0x0000 Fault response mode 1 Protocol switch 0 Watchdog timeout 500 ms 2 2 Firmware Start The firmware is started after the device has been connected to the power supply or the reset key has been pressed The following sequence is displayed see also Startup Behavior of the Bus Coupler on page 3 8 Table 2 1 Sequence displayed after the device is switched on Display Meaning 01 Boot loader is started BootP requests are transmitted bo Firmware is extracted 02 Firmware is started PP Plug amp play mode activated or operation 615605 PHCENIX 23 FL IL 24 BK PAC UM E 2 3 Transmitting BootP Requests Initial Startup During initial startup the device transmits BootP requests without interruption until it receives a valid IP address The requests are transmitted at v
121. FL IL 24 BK PAC 2 20 2 9 4 Defining the Trap Manager 2 20 Factory Line I O Configurator seen 2 21 2 10 1 Factory Line I O Browser seen 2 21 2 10 2 Configurator 2 2 22 Management Information Base 2 24 2414 Standard MIBs ee eee ete guit 2 24 Interface Group 1 3 6 1 2 25 2 12 4 Private MIBS itc ee Cete 2 30 Meaning of the 7 Segment Display 2 44 3 3 Documentations sissa des DERE 3 3 3 1 1 Hardware and Firmware User Manual 3 3 Software Structure uude eto a eee 3 3 3 2 1 Ethernet Inline Bus Coupler Firmware 3 4 3 2 2 Driver Software essent 3 4 Support and Driver Update 2 3 5 Transfer of I O D ta necat cede nina 3 6 3 4 1 Position of the Process Data Example 3 7 Startup Behavior of the Bus 3 8 3 5 1 Plug amp Play Mode 3 8 3 5 2 Expert Mode ERROR DERE UE 3 9 3 5 3 Possible Combinations of the Modes 3 9 3 5 4 Startup Diagrams of the Bus Coupler
122. FWInfo 1 fl WorkFWiInfoVersion 2 flWorkFWinfoState 3 flWorkFWInfoDate 4 flWorkFWInfoTime 5 flWorkFWInfoCopyright 6 flWorkFWInfoBootVersion 7 8 zt t a El 7 flWworkFWInfoBootState 8 flWorkFWInfoBootDate 2 34 PHCEN IX 615605 CONTACT Startup Operation 9 flWorkFWInfoBootTime 11 flWorkFWInfoOperStatus 12 flWorkFWInfoHealthText 2 flWorkFWCtrl 1 flWorkFWCtrlBasic 1 flWorkFWCtrlReset 2 flWorkFWCtrlTrapDestCapacity 2 flWorkFWCtrlTrapDest 1 flWorkFWCtrlTrapDestTable 1 flWorkFWCtrITrapDestEntry 1 flWorkFWCtrlTrapDestIndex 2 flWorkFWCtrlTrapDestIPAddr 3 flWorkFWCtrlPasswd 1 flWorkFWCtrlPasswdSet 2 flWorkFWCtrlPasswdSuccess 4 flWorkFWCtrlUpdate 1 flWorkFWCtrlUpdateEnable 2 flWorkFWCtrITftpIPAddr 3 flWorkFWCtrITftpFile 5 flWorkFWCtrlConf 1 flWorkFWCtrlConfStatus 11 flWorkFWInfo 1 flWorkFWParamSaveConfig 12 flWorkRptr flWorkBasicName OID 1 3 6 1 4 1 4346 11 11 1 1 Syntax Display string Access Read write Description Contains the device name corresponds to sysName from MIB2 flWorkBasicDescr OID 1 3 6 1 4 1 4346 11 11 1 2 Syntax Display string Access Read write Description Contains a brief description corresponds to sysDescr from MIB2 615605 PHCENIX 2 35 CONTACT FL IL 24 BK PAC UM E flWorkBasicName
123. Figure 3 6 Normal mode expert mode and P amp P mode inactive 3 10 Figure 3 7 P amp P mode inactive expert mode active 3 10 Figure 3 8 P amp P mode active expert mode inactive 3 11 Figure 3 9 P amp P mode active and expert mode active 3 11 Figure 3 10 Execution of a remote procedure call 3 17 Figure 3 11 Status diagram of the process data watchdog 3 36 Figure 3 12 Assignment of the process data between the local bus and the computer systems 3 58 Figure 3 13 Using the macros for programming support 3 59 Figure 3 14 Structure of the station for the example program 3 78 Figure 3 15 Screenshot of the example program 3 79 Section 6 Figure 6 1 Location of the data in input output modules 6 7 Figure 6 2 Location of the process data in dynamic tables 6 8 615605 PHCENIX ido CONTACT FL IL 24 BK PAC UM E A 4 PHCENIX 615605 CONTACT Appendix 2 List of Tables Section 1 Table 1 1 Local status and diagnostic indicators 1 6 Table 1 2 Connector 1 8 Table 1 3 Digital Input Output Modules
124. HostChecking Task After the ETH SetHostChecking function has been called successfully the client user workstation is addressed by the bus coupler at regular intervals If the client does not respond within the predefined time timeout 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 coupler Syntax IBDDIRET IBDDIFUNC ETH SetHostChecking IBDDIHND nodeHd USIGN16 time Parameters IBDDIHND nodeHd Node handle MXI or DTI for the bus coupler that is to be monitored 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 is 65000 ms If a shorter value is entered the error code ERR INVLD PARAM is returned and Host Checking is not activated 3 38 PHCEN IX 615605 CONTACT Driver Software 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 CAU00yxDlg OnButtonSetHostCheckingon IBDDIRET ddiRet USIGN16 hcTime 1000 ddiRet SetHostChecking ddiHnd amp 1 if ddiRet ERR INVLD PARAM hcTime selected too short
125. IB IL TEMP 2 UTH PAC 2 inputs 2 wire termination 16 bits thermocouples 28 61 38 6 IB IL TEMPCON RTD Multi channel temperature controller 6 inputs 6 outputs 28 19244 IB IL TEMPCON RTD Multi channel temperature controller 6 inputs 6 outputs 28 61 77 1 PAC IB IL TEMPCON UTH 8 inputs 8 outputs controller functions 28 19312 IB IL TEMPCON UTH 8 inputs 8 outputs controller functions 28 61807 PAC IB IL AO 1 SF 1 output 2 wire termination 24 V DC 0 20 mA 27 26 298 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 08 3 4 20 mA 0 10 V IB IL AO 2 U BP 2 outputs 2 wire termination 24 V DC 0 10 V 10 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 467 Table 1 5 Special function modules Designation Properties Order No IB IL SSI 1 absolute encoder input 4 digital inputs 4 digital outputs 500 28 36 34 0 mA 3 wire termination 24 V DC IB IL SSI PAC 1 absolute encoder input 4 digital inputs 4 digital outputs 500 28 61 86 5 mA 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 abso
126. INFO structure and transmitted to the controller board The timeout time is endless if the value FFFF FFFFpe is entered IBDDIRET IBDDIFUNC DDI SetMsgNotification IBDDIHND nodeHd T ETH NOTIFY INFO IBPTR notifyInfoPtr IBDDIRET IBDDIFUNC DDI CIrMsgNotification IBDDIHND nodeHd T ETH NOTIFY INFO IBPTR notifyInfoPtr UNIX Parameters mode Notification mode processld threadld timeout Abort time in milliseconds 3 56 PHGNIX 615605 CONTACT Driver Software Format of the structure Constants Windows NT 2000 Parameters Format of the typedef struct USIGN32 mode Defines the notification mode USIGN32 threadId Thread identifier USIGN32 processId Process identifier USIGN32 timeout Timeout time in milliseconds T ETH NOTIFY INFO define ETH 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 in milliseconds T IBS WIN32 NOTIFY 615605 3 57 FL IL 24 BK PAC UM E 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 68xxx format if a workstation with Intel format is used to create
127. IP address 2 6 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 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 PCs this extended IP address appears as a standard IP address to all the other devices 2 6 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 in 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 2 8 PHCENIX 615605 CONTACT Startup Operation Application If ANDing of the address bits gives the local network address and the local subnetwork address the device is located in the
128. IX CONTACT Firmware Services Result Add Error Info 000244 2 parameter words Result of the service processing 0000hex indicates a positive message The controller board has 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 Version information for the hardware and firmware Every byte indicates the ASCII code for a character FW Version FW State FW Date FW Time Host Type Host Version Host State Host Date Host Time Start FW Version Start FW State Start FW Date Start FW Time HW Art No HW Art Name HW Motherboard ID HW Version HW Vendor Name Version of the firmware core 4 bytes e g 33 2E 39 37hex for Version 3 97 Firmware status 6 bytes e g 62 65 64 61 00 00nex for beta with preliminary versions Creation date of the firmware 6 bytes e g 31 37 30 33 30 315 for 17 03 01 Creation time of the firmware 6 bytes e g 31 34 31 30 32 30hpex for 14 10 20 Type of the host specific firmware interface e g FL IL 24 BK PAC 20 bytes Version of the host specific firmware interface 4 bytes Status of the host specific firmware interface 6 bytes Creation date of the host specific firmware interface 6 bytes Creation time of the host specific
129. LoByte 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 USIGNB Pointer to the receive buffer m USIGN16 Parameter number USIGN8 Parameter value byte Only read parameters 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 a USIGNG data type n USIGNB Pointer to the receive buffer m USIGN16 Parameter number USIGNB8 Address of the high order byte of a parameter in the receive buffer IB_GetBytePtrLoByte n m This macro returns the address of a parameter entry starting with the low order byte bit 0 to 7 The address is a USIGN8 data type n USIGNB Pointer to the receive buffer m USIGN16 Parameter number USIGNS Address of the low order byte of a parameter in the receive buffer 3 64 615605 PHCENIX CONTACT Driver Software Task Parameters Task Parameters Return value Task Parameters Return value Task Parameters Return value 3 12 3 Macros 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 t
130. MIB The FL IL 24 BK PAC supports the following MIBs Standard MIB 1213 MIB II Private MIBs PhoenixContact MIB FL MIB Factory Line MIB and FL DEVICE MIB 2 11 1 Standard MIBs 2 11 1 1 RFC 1213 MIB II System Group 1 3 6 1 2 1 1 The system group contains information about device management 1 interfaces 1 sysDescr 2 sysObjektID 3 sysUpTime 4 sysContact 5 sysName 6 sysLocation 7 sysServices 2 24 615605 PHCENIX CONTACT Startup Operation 2 12 Interface Group 1 3 6 1 2 1 2 The interface group contains information about device interfaces 2 interfaces 1 ifNumber 2 ifTable 1 if Entry 1 iflndex 2 ifDescr ifType 4 ifMtu 5 ifSpeed 6 ifPhysAddress 7 ifAdminStatus 8 ifOperStatus 9 ifLastChange 0 iflnOctets 1 iflnUcastPkts 2 iflnNUcastPkts 3 iflnDiscards 4 iflnErrors 5 iflnUnknownProtos 6 ifOutOctets 7 ifOutUcastPkts 8 ifOutNUcastPkts 9 ifOutDiscards 20 ifOutErrors 21 ifOutQLen 22 ifSpecific A 3 eu x EA ui 1 1 1 1 1 1 1 1 1 1 N Address Translation Group AT 1 3 6 1 2 1 3 The address translation group is mandatory for all systems It contains information about the address assignment 3 at 1 atTable 1 atEntry 1 atlflndex 2 atPhysAddress 3 atNetAddress
131. O 8 has eight bits and eight process data channels Number of process data words of an Inline terminal Note that analog terminals always have the same number of output and input data words An AO 2 also has two input channels and an Al 2 also has two output channels This area is used by all terminals that use 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 gt DI lt MODULE TYPE PD CHANNELS 2 PD CHANNELS PD WORDS 1 PD WORDS PD IN word 1 gt 3 lt PD_IN gt lt IL MODULE b Inline terminal with two digital inputs only the second input is active IL MODULE number 3 gt MODULE TYPE DIc MODULE TYPE PD CHANNELS 2 PD CHANNELS PD WORDS 1 PD WORDS PD IN word 1 gt 2 lt PD_IN gt lt IL MODULE Inline terminal with 16 digital inputs inputs 13 and 14 are active 615605 PHCENIX is CONTACT FL IL 24 BK PAC UM E lt IL MODULE number 7 gt MODULE TYPE gt DI lt MODULE TYPE PD CHANNELS 16 PD CHANNELS PD WORDS 1 PD WORDS PD IN word 1 gt 12288 lt PD_IN gt IL MODULE The inputs data word returns the value 12288 212 213 d Inline terminal with two analog inputs only the first channel 14970 is active IL MODULE number 10 gt MODULE TYPE AI MODULE TYPE PD CHANNELS 2 PD CHANNELS PD WORDS 2 PD WOR
132. ONTACT Technical Data Bus Interface of the Lower Level System Bus Interface Inline local bus Electrical isolation No Number of Inline terminals that can be connected Limited by software Limited by power supply unit 63 maximum Maximum logic current consumption of the connected local bus modules Imax lt 2 A DC Observe the logic current consumption of each device when configuring an Inline station This information is given in every module specific data sheet The current consumption can differ depending on the individual module The permissible number of devices that can be connected therefore depends on the specific station structure Observe the current consumption of the modules Interfaces Ethernet Interface Number One Connection format 8 pos RJ45 socket 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 25 AWG Cable impedance 100 Q Transmission speed 10 100 Mbps Maximum network segment expansion 100 m 328 ft Protocols MIBs Supported protocols TCP UDP SNMP BootP Modbus TCP Supported standard MIB 1213 MIB II Supported private MIBs PhoenixContact MIB FL MIB FL Device MIB 615605 PHCENIX 7 9 CONTACT FL IL 24 BK PAC UM E Mechanical Tests Shock test accordi
133. Registers essssseseeneeen 6 30 6 2 PHCENIX 615605 CONTACT Modbus TCP Protocol 6 Modbus TCP Protocol This section describes the implementation of Modbus TCP communications on the FL IL 24 BK PAC Modbus Protocol Modbus connections Modbus port Modbus conformance 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 coils Write single register Read exception status Write multiple coils Read write registers 6 1 Modbus Protocol The bus coupler supports a Modbus TCP server with the following features 6 1 1 Modbus Connections The FL IL 24 BK PAC supports up to eight simultaneous connections This allows for the fast reestablishment of a connection i e a client is able to re establish a Modbus connection successfully after it has been aborted 615605 PHCENIX ie CONTACT FL IL 24 BK PAC UM E 6 1 2 Modbus Port Modbus communication on the FL IL 24 BK PAC is supported on the Modbus standard port 502 6 1 3 Modbus Conformance Classes The FL IL 24 BK PAC supports Modbus conformance classes 0 and 1 6 1 4 Modbus Message Format The Modbus TCP protocol has a special message format as follows Table 6 1 Modbus me
134. Return value Format of the T DDI MXI ACCESS structure IBDDIRET IBDDIFUNC DDI MXI RcvMessage IBDDIHND nodeHd T DDI MXI ACCESS mxiAcc 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 coupler which is to be accessed DDI 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 typedef struct USIGN16 msgType Message type 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 615605 CONTACT Driver Software Example 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 256 mxiAcc DDIUserID 0 mxiAcc msgType 0 mxiAcc msgBlk iBuf ddiRet DDI MXI 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 i 615605 PHCENIX vM CONTACT
135. T ddiRet ddiRet DDI DevCloseNode ddiHnd if ddiRet ERR OK Error treatment return 615605 PHCENIX 3 21 CONTACT FL IL 24 BK PAC UM E Task Syntax Parameters Return value Format of the T DDI DTI ACCESS structure DDI DTI ReadData The DDI DTI ReaabData function is used to read process data from the Inline bus coupler The function is assigned the node handle and a pointer to a T DDI DTI ACCESS data structure The T DDI DTI ACCESS structure contains all the parameters that are needed to access the process data area of the bus coupler 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 coupler 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 coupler 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 coupler which is to be accessed T DDI DTI ACCESS dtiAcc Pointertoa T DDI DTI ACCESS data structure This structure contains all the parameters needed for access IBDDIRET If the function is execu
136. The process data is invalid because only internal values but no values on INTERBUS are indicated The status is shown in the diagnostic register To ensure that valid data is shown the diagnostic register must also always be scanned The same behavior will occur if a wrong configuration is connected In this case INTERBUS is not running and only internal values can be read in the XML file In the event of an I O error all data is valid except for the data of the faulty terminal 615605 PHCENIX 2 15 CONTACT FL IL 24 BK PAC UM E lt IL STATION View lt IL ST encoding TION TERMINA lt TERMINAL TYPE AME gt FL IL 24 BK lt 224 PARAMETER REGISTER IL BUS TERMINAL MoD cPD CHANNEL LE_TYPE gt DO lt TYPE 6 c PDO CHANNELS JOULE TY O_CHANNE lt PD_CHANNEL lt PD_WORDS gt 1 PD IN word 1 gt 18847 lt PD_ CAILLA T D CHANNEL PD WORD PD IN words PD IN word ULE numbe gt LE TYPESAQc MODULE TYPE ANNELS gt 1 lt PD ANNELS gt lt PD_WORDS gt 1 lt PD_WOR PD OUT word 1 gt 16521 lt PD CHANNEL PD PD WORDS 1 PD WORD DIAGNOSTIC IAGNOSTIC PARAMETER REGISTER gt Data of first Digital Output Modul Data of first Digital Input Modul Station Data STATUS REGISTER gt Diagnostic Register
137. a positive message and provides data if requested The service confirmation indicates the error that occurred during service execution via a negative message 4 4 PHGNIX 615605 CONTACT Firmware Services Structure of a service description Task Prerequisite The Result parameter of the service confirmation shows if the service was executed successfully Result parameter 0000 or if an error occurred Result parameter 0000 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 hex or binary pin notation The structure of all service descriptions is as follows 4 2 1 Name of the Service Service Describes the functions of the service All conditions which must be met before a service is called to enable successful processing Syntax Name of the Service Request Word 1 Word 2 Word 3 Word 4 Word 5 Bit 0 Key Code Command code of the service request hexadecimal notation Parameter Count Number of subsequent words 0000hex 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 ind
138. a 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 USIGNB Pointer to the receive buffer USIGN16 Message code IB GetParaCnt 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 USIGNB Pointer to the receive buffer USIGN16 Parameter count Only read 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 n USIGNB Pointer to the receive buffer m USIGN16 Parameter number USIGN16 Parameter value Only read parameters for messages that also have parameters 615605 PHCENIX is CONTACT FL IL 24 BK PAC UM E Task Parameters Return value Remark Task Parameters Return value Remark Task Parameters Return value Task Parameters Return value IB GetParaNHiByte n m This macro reads the high order byte bit 8 to 15 of a parameter from the specified receive buffer and converts it into Intel format n USIGNB Pointer to the receive buffer m USIGN16 Parameter number USIGNS Parameter value byte Only read parameters for messages that also have parameters IB GetParaN
139. 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 Configuration Reset Fault Mode Configuration Last State Fault Mode FL IL 24 BK PAC Output table Real output Output table Real output Cable removal or Last values in the All discrete outputs Last values in the Values of the output communication error output table are set to 0 output table table after cable interrupt First write access inthe Last values in the Output table Last values in the Output table output table after output table plus output table plus the restoring the the newly written newly written values connection values Operating Last values in the Output table Last values in the Output table output table plus all output table plus all newly written newly written values values 6 28 PHGNIX 615605 CONTACT Modbus TCP Protocol Example The last entries in the output table have the following values Module AO DO 16 DO 2 Value 0x0123 0x4321 0x0002 Writing 0 00 1 into the output table of the DO 16 as the first value after having restored the connection gives the following actual output value Module AO DO 16 DO2 Value 0x0123 0x00A1 0x0002 This is the Last va
140. a transmission via RS 232 28 61357 IB IL RS 485 422 Terminal for serial data transmission via RS 485 422 28 36 79 3 IB IL RS 485 422 PAC Terminal for serial data transmission via RS 485 422 28 61 933 ASI MA IB IL AS i master 27 41288 Table 1 6 Motor terminal blocks Designation Properties Order No IB IL 24 TC Thermistor terminal 2727417 IB IL 24 TC PAC Thermistor terminal 28 61360 IB IL 400 ELR 1 3A Electronic direct starter 1 5 KW 2 01 hp 400 V AC 27 27 352 IB IL 400 ELR R 3A Electronic reversing load starter 1 5 kW 2 01 hp 400 V AC 2727378 IB IL 400 MLR 1 8A Electromechanical direct starter 3 7 kW 4 96 hp 400 V AC 27 27 36 5 IB IL DC AR 48 10A Servo amplifier for DC motors with brushgears 28 19 28 6 IB IL EC AR 48 10A Servo amplifier for DC motor without brushgears EC motor 28 19257 615605 1 13 PHCENIX CONTACT FL IL 24 BK PAC UM E Table 1 6 Motor terminal blocks Designation Properties Order No IB IL EC AR 48 10 Servo amplifier for DC motor without brushgears EC motor 28 19 587 IB IL PWM 2 Terminal for pulse width modulation and frequency modulation or 27 42612 stepper motor control 2 outputs for 5 V or 24 V IB IL PWM 2 PAC Terminal for pulse width modulation and frequency modulation or 28 61 63 2 stepper motor control 2 outputs for 5 V or 24 V Table 1 7 Power and segment terminals Design
141. acro converts the high order byte bit 8 to 15 of a parameter into Motorola format and enters it in the specified transmit buffer n USIGNB Pointer to the transmit buffer m USIGN16 Parameter number o USIGN8 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 USIGNB Pointer to the transmit buffer m USIGN16 Parameter number o USIGN8 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 a USIGNG data type n USIGNB Pointer to the transmit buffer m USIGN16 Parameter number USIGNS Address of the high order byte of the parameter in the transmit buffer 3 62 PHCEN IX 615605 CONTACT Driver Software Task Parameters Return value Task Parameter Return value Task Parameter Return value Remark Task Parameters Return value Remark IB SetBytePtrLoByte n m This macro returns the address of a parameter entry starting with the low order byte bit to 7 The address is a USIGN8 data type n USIGNB Pointer to the transmit buffer m USIGN16 Parameter number USIGN8 Address of the low order byte of the parameter in the transmit buffer 3 12 2 Macros for Converting the Dat
142. alog power Uana for the local bus devices is also generated 2 1 2 2 24V DC Main voltage The main voltage is routed to the local bus devices via the Um potential jumpers 1 3 LGND Reference potential The potential is the reference ground for the communications logic ground for Ugk power 2 3 SGND Reference potential The reference potential is directly led to the potential jumper for Us and Uy 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 the 24 V ground FE 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 itis snapped onto a grounded DIN rail Functional earth ground is only used to discharge interference 1 8 PHCENIX 615605 CONTACT FL IL 24 BK PAC 1 5 Supported Inline Modules Table 1 3 Digital Input Output Modules Designation Properties 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 61 483 IB IL 24 EDI 2 2 inputs 4
143. and a pointer to a DDI ACCESS data structure as parameters The DD MXI ACCESS structure contains all the parameters that are needed to send the message These parameters are transmitted to the bus coupler via the network without a plausibility check which means that invalid parameters are first detected on the bus coupler and acknowledged with an error message The BDDIHND nodeHd parameter specifies the bus coupler 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 coupler IBDDIRET IBDDIFUNC DDI MXI SndMessage IBDDIHND nodeHd T DDI MXI ACCESS mxiAcc IBDDIHND nodeHd Node handle MXI for the connection via which a message is to be written to the mailbox interface The node handle also determines the bus coupler which is to be accessed T DDI 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 typedef struct T DDI MXI USIGN16 msgType ACCESS structure Message type see DDI description USIGN16 msgLength Length of the message in bytes USIGN16 DDIUserID Message ID USIGN8 msgBlk Pointer to the message data T DDI MXI ACCESS 3 28 PHCEN IX
144. anging a Reference Configuration Using the Software 3 6 1 Effects of Expert Mode If expert mode object 2275 is active automatic startup of the connected local bus is prevented The user must manually place the bus to the RUN state by activating the configuration Activate 0711 object or Create Configuration 0710 object and by starting the local bus Start Data Transfer 0701 pex object In expert mode the bus coupler behaves in the same way as the gateways IBS SC I T or IBS 24 ETH DSC 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 to the Active or Stop state e g using the Alarm Stop command The reference configuration can be downloaded or deleted The connected bus can be read using the Create Configuration command and 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 with an error message this means that no reference configuration is present Table 3 2 System parameters for the Set Value service 75054 Variable ID System Parameter Value Comment 0104hex Diagnostic status register Read only 0105hex Diagnostic parameter register Read only 2216hex Current PD cycle time Read only 615605 PH NIX 3 1
145. are set to a value default 0 programmed by the user Standard fault mode All outputs are set to 0 Hold last state mode All outputs hold the last value 615605 PHCENIX FL IL 24 BK PAC UM E Reasons for Fault Response The web based management the Modbus register 2004 or the ETH GetNetFailState service allow to request the causes for fault response mode and for setting the NetFail signal Causes The following reasons are possible DDI NF TASK CREAT ERR 0x0001 Error when starting a task 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 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 Acknowledgement of the NetFail Signal The NetFail signal can be acknowledged using the web based management by setting bit 1 in the command word of the Modbus register 4076 or using the ETH_Cl
146. area includes TERMINAL TYPE module NAME ADDRESS the number of connected terminals MODULE NUMBER the INTERBUS diagnostic register DIAGNOSTIC STATUS REGISTER and the INTERBUS status register DIAGNOSTIC PARAMETER REGISTER This area contains the module designation i e always FL IL 24 BK PAC Contains user specific station names The station name can be modified via SNMP or WBM Contains the station IP address Contains the number of connected Inline terminals In the event of a bus error the number of the last known operable configuration is specified 2 12 PHCENIX 615605 CONTACT Startup Operation DIAGNOSTIC STATUS REGISTER IL BUS IL MODULE MODULE TYPE PD CHANNELS PD WORDS PD IN Contains the INTERBUS status indicated by all the bits in the diagnostic status register A detailed description can be found in the diagnostic parameter register The diagnostic parameter register is always re written if an error bit is set Frame for the connected Inline terminals Frame for the data of individual Inline terminals The terminals are numbered from one to 63 maximum Contains the module type e g DI DO DIO Al AO AIO and PCP Number of process data channels of an Inline terminal With digital terminals the number of channels is equal to the number of supported bits With other modules the number of process data words is indicated Example An AO 2 has two process data channels and a D
147. arying intervals 2 s 4 5 8 s 2 s 4 s etc so that the network is not loaded unnecessarily If valid IP parameters are received they are saved as configuration data by the device Restart If the device already has valid configuration data it only transmits three more BootP requests upon 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 4 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 2 4 1 BootP P Ensure that the network scanner amp the BootP server have been started Connect the device to the network and the supply voltage 2 4 PHCENIX 615605 CONTACT Startup Operation 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 for the device or on Enterthe relevant data in the Add New Ethernet Device dialog box see 2 5 Savethe configuration settings and restart the device reset key or power up 2 5 Manual Addition of Devices Using The Factory Manager Open the Add New Ethernet Device dialog box by clicking
148. assigned a node handle for a DTI or mailbox data channel of the relevant bus coupler as a parameter IBDDIRET IBDDIFUNC ETH SetNetFail IBDDIHND nodeHd IBDDIHND nodeHd Node handle MXI or DTI forthe bus coupler on which the NetFail signal is to be executed 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 IBDDIRET ddiRet ddiRet ETH SetNetFail ddiHnd ETH_GetNetFailStatus Task The ETH_GetNetFailStatus function sends the NetFail status to the user which is determined by the node handle of the bus coupler The function is assigned a node handle for an open DTI or MXI 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 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 can be found in the IOCTRL H file Syntax IBDDIRET IBDDIFUNC ETH GetNetFailStatus IBDDIHND nodeHd T ETH NET FAIL netFaillnfo 615605 PHCENIX S R CONTACT FL IL 24 BK PAC UM E Parameters Return value Format of the T ETH NET FAIL
149. ation Properties Order No IB IL 24 PRW IN Power terminal 24 V DC 27 26 31 1 IB IL 24 PRW 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 894 IB IL 24 PRW IN 2 F Power terminal 24 V DC with fuse 28 60 015 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 28 0 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 61 027 IB IL 24 PWR IN R Power terminal 24 V DC 27 42 764 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 31704 IB IL 120 PRW IN PAC Power terminal 120 V AC with fuse 28 61454 IB IL 230 PRW IN Power terminal 230 V AC with fuse 27 40 339 IB IL 230 PRW 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 IB IL 24 SEG PAC Segment terminal 24 V DC 28 61344 IB IL 24 SEG F Segment terminal 24 V DC with fuse 2727747 IB IL 24 SEG F PAC Segment terminal 24 V DC with fuse 28 61373 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
150. bindex 6073 Invoke ID 60724 6079 Reserved 6 30 PHCENIX 615605 CONTACT Modbus TCP Protocol Table 6 48 PCP registers CR 8 6080 6081 Index 6082 Subindex 6083 Invoke ID 6084 6089 Reserved CR 9 6090 6091 Index 6092 Subindex 6093 Invoke ID 6094 6099 Reserved Example To read object Ox5FEO of an IB IL RS232 using communication reference 4 the configuration registers 6041 6043 must be set to the desired values e g 6041 index 0x5FE0 6042 subindex 0x0 6043 Invoke ID 0x0 first using the FC 16 command Then use the FC 3 command to read 29 words via the communication register 6040 A Modbus function can only be used to read or write in one single PCP index You cannot use the FC 3 command to read 20 words from the registers 6020 to 6039 The communication register contains a different value range which depends on the selected register values and the module used The IB IL RS 232 module for example has three different PCP objects Two of them consist of one word and the third of 29 words The three configuration registers can be read written using a single Modbus command Access to a reserved register produces an exception response 615605 PHCENIX ed CONTACT FL IL 24 BK PAC UM E 6 32 PHGNIX 615605 CONTACT Section 7 This section provides information about technical data ordering data Technical Data i eee MI
151. cess 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 3 54 PHCENIX 615605 CONTACT Driver Software Task Syntax Parameter Return value IS 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 T DDI DTI ACCESS structure is not explained here because it has already been described in detail in the standard DTI routines ETH DeactivatePDInMonitoring The ETH DeactivatePDInMonitoring function deactivates IN process
152. 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 been 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 coupler 615605 PHCENIX TH CONTACT FL IL 24 BK PAC UM E ETH SetDTITimeoutCtrl Task The SetDTlITimeoutCtrl function 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 ca
153. connection is disabled 6 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 PAC beforehand Use the DDI Set Value command on the object ID 2277 The following table shows the three possible reactions Table 6 45 Available fault response modes Fault Response Mode Value Function Reset fault mode default 1 The discrete 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 The following tables show the output tables and real output values for the first two configuration choices One table is for restart after power up and the other table for restart after a fault occurred The output table is part of the bus coupler s internal memory real output values are the values of the output modules The output table consists of two parts discrete and analog outputs 6 26 PHCEN IX 615605 CONTACT Modbus TCP Protocol Table 6 46 6 9 1 Power Up Table The FL IL 24 BK PAC output table of the is stored in a 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 volatile EEPROM Power up sequence Power Up Sequence
154. connectors and Inline connections for interruptions and repair them if required Error location Segment Position 615605 PHCENIX T CONTACT FL IL 24 BK PAC UM E Meaning Cause Remedy Add Error Info Meaning Add Error Info Meaning Cause Remedy Add Error Info Meaning Remedy Add Error Info E PNM12 CONFIG MAU FAIL DI 0D28hex The Medium Attachment Unit MAU diagnosed an 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 OD4Chex The specified Inline device has an invalid ID code Error location Segment Position E PNM12 CONFIG MULTI ERR OUT OD80hex 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 Seg
155. 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 615605 PHCENIX Tes 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 set an alarm output Syntax Control Device Function Request 0714 Word 1 Word 2 Word Word 4 List Word 5 INTERBUS Word 6 devices Word n 2 Bit je 0 Code 0714 Command code of the service request Parameter Count Number of subsequent words Device Function 000445 Conf Dev Err All Confirming the peripheral faults PF of all devices Set Entry Count 0000 The list of INTERBUS devices is not required Entry Count 0000hex If Device Function 0004 4 34 Sines CONTACT Firmware Services Syntax Control Device Function Confirmation 8714 Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit jp 0 Key Code 87144 Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001 1 parameter word with a negative message 000244 2 parameter words Result Result of the service processing 0000hex indicates a positi
156. cture A L T 615605 PHCENIX FL IL 24 BK PAC UM E 3 2 1 Ethernet Inline Bus Coupler Firmware The Ethernet Inline bus coupler firmware controls the Inline functions and Ethernet communication shown on the right hand side in Figure 3 1 The bus coupler provides a basic interface for using services via the Ethernet network The software primarily encodes and decodes the data telegrams for addressing the bus coupler services The firmware also ensures the network specific addressing of the bus coupler 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 BS ETH DDI SWD E Order No 27 24 19 3 The driver software can be divided into three groups The Device Driver Interface functions form the first group which controls the bus coupler via the Ethernet network Using these functions firmware services can be called and started and results can be requested on the bus coupler The second group contains functions for monitoring the bus coupler and the workstation with the application program The third group contains macro functions for the conversion of data between Intel and Motorola
157. d the number of enabled attributes with a negative message 00024 2 parameter words Result of the service processing 0000hex indicates a positive message The service request has been executed successfully The data is available in the following parameters 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 see also Add Error Info Additional information on the error cause 0000hex indicates that all requested entries are contained in the service confirmation 000145 indicates that the service confirmation does not contain all requested entries as the amount of data is larger than the mailbox MXI 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 which was transmitted by 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 the selected configuration frame 615605 PHCENIX 4 23 CONTACT FL IL 24 BK PAC UM E Active IO Bit Count Number of active I O bits in the selected config
158. data monitoring The function is only assigned the node handle as a parameter which is also used to activate monitoring with ETH ActivatePDInMonitoring IBDDIRET IBDDIFUNC ETH DeactivatePDInMonitoring IBDDIHND nodeHd IBDDIHND nodeHd Node handle DTI for the controller board for which process data monitoring is to be deactivated IBDDIRET If the function is executed successfully the value 0 ERR OK is returned Otherwise the return value is an error code 615605 PHCENIX 98 CONTACT FL IL 24 BK PAC UM E General Task IS Syntax to activate Syntax to deactivate 3 10 Notification Mode Notification mode enable 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 Notification Mode A feature of notification mode is that the message is awaited on the controller board DDI MXI 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 notification mode is activated the timeout time is entered in the T ETH NOTIFY
159. data format Figure 3 2 illustrates the creation of an application program from the parts of the driver software 3 4 PHCEN IX 615605 CONTACT 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 in 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 www phoenixcontact com Training Courses Our bus coupler 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 615605 PHCENIX FL IL 24 BK PAC UM E 3 4 Transfer of I O Data The I O data of individual Inline 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 15 4 Bit 0 2 words 1 word EN
160. do locRet DDI MXI RcvMessage mxiHnd amp mxiAcc time amp ltime Le ltime starttime lt MXI RCV TIMEOUT amp amp locRet ERR OK if locRet ERR OK printf n n Incorrect confirmation received Error code 0x 04X locRet 615605 PHGNIX 3 83 CONTACT FL IL 24 BK PAC UM E else PlugPlayModus IB GetParaN locMsgBlk 0x04 printf nPlug amp 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 printf nError when reading INTERBUS status Error code 0x 04X locRet else if infoPtr state 0x00E0 printf nIBS status RUNNING else printf nIBS status 0x 04X infoPtr state Reading and writing only permitted when the bus is running if infoPtr state OxOOEO printf NnIBS not in RUN state Abort exit 0 Write zero to the DI8 module loci 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 MAX MSG LENGTH i 3 84 PHCENIX 615605 CONTACT Drive
161. dule will be connected Housing Only authorized Phoenix Contact personnel are permitted to open the housing PHCEN IX 615605 CONTACT 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 applica tion requirements Use this manual if you are responsible for configuring and installing an Ethernet In line station This manual is written based on the assumption that the reader pos sesses basic knowledge about Inline systems For specific information on the individual Inline terminals see the corresponding ter minal specific data sheets Make sure you always use the latest documentation Changes in or additional infor mation on present documentation can be found on the Internet at www phoenixcontact com or www factoryline de The homepages are updated daily You can also contact us by sending an e mail to factoryline service 9 phoenixcontact com 615605 PHCENIX CONTACT FL IL 24 BK PAC UM E Orientation in this manual This user manual includes Validity of documentation For easy orientation when looking for specific information the manual offers the fol lowing help The manual starts with the main table of contents that gives you an overview of all manual topics Each manual section starts with an overview of the secti
162. e so that the desired service can be called INCORRECT ATTRIB 0A18nex 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 0A22nex Cause You specified inconsistent device numbers Remedy Enter the device numbers again DEVICE ZERO 2 The Initiate Load Configuration service could be executed The number of connected Inline modules is either zero or greater than 63 Remedy Change the number of connected Inline modules INCORRECT FRAME REF 0 51 Cause The Frame Reference value is not one 1 Remedy Change the Frame Reference to 1 4 52 PHCEN IX 615605 CONTACT Firmware Services Cause Cause Cause INTERNAL TIMEOUT The function start reg was not reset within the timeout Additional info xxXXpex Timeout in hex FUNCTION REG NOT FREE The function start reg is not empty ACTION ERROR The service could not be executed correctly Additional info 0005 Bus data could not be detected Additional info 00 5 The configuration could not be activated 22 pex 0E23hex 0E24hex 615605 PHCENIX CONTACT 4 53 FL IL 24 BK PAC UM E 4 54 PHCENIX 615605 CONTACT Communication Section 5 This section p
163. ead Description Contains the operating state of the firmware Problem 1 No problem 2 flWorkFWInfoHealthText OID 1 3 6 1 4 1 4346 11 11 11 1 12 Syntax Display string Access Read Description Contains additional information error states of the firmware fIWorkFWCtrlReset OID 1 3 6 1 4 1 4346 11 11 11 2 1 1 Syntax Integer Access Read write Description With write access a reset can be executed with 2 With read access the value is always 1 fIWorkFWCtrlTrapDestCapacity OID 1 3 6 1 4 1 4346 11 11 11 2 1 2 Syntax Integer32 1 1024 Access Read Description Contains the number of devices to which the traps are sent fIWorkFWCtrlTrapDestTable fl WorkFWCtrlTrapDestEntry OID 1 3 6 1 4 1 4346 11 11 11 2 2 1 1 Syntax Access Description Generates a table with the IP addresses of the trap managers 2 40 PHCEN IX 615605 CONTACT Startup Operation flWorkFWCtrlTrapDestIndex OID Syntax Access Description 1 3 6 1 4 1 4346 11 11 11 2 2 1 1 1 Integer32 1 1024 Read Contains the index of the target component which is to receive the traps flWorkFWCtrlTrapDestIPAddr OID 1 3 6 1 4 1 4346 11 1 2 1 1 2 Syntax IP address Access Read write Description Contains the IP address of the target component which is to receive the traps fIWorkFWCtrlPasswdSet OID 1 3 6 1 4 1 4346 11 11 11 2 3 1 Syntax Octet String 2 24 Access Read write 3 For security reasons the response is always with read access
164. eb 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 information e g IP address status information or to change the configuration password protected 2 7 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 coupler homepage is accessed by entering the URL http jp address Example http 192 168 2 81 FL 24 BK PAC last update 8 36 37 CONTACT FL IL 24 BK PAC General Instructions Device Information Device Configuration Inline Station Home Figure 2 2 WBM homepage 2 10 PHCENIX 615605 CONTACT Startup Operation 2 7 2 Structure of the Web Pages The Ethernet bus coupler pages are divided into two parts 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 coupler can be found in the following menus 2 7 3 Layout of the Web Pages FL IL 24 BK PAC General Instructions ly Information Device Information General Technical Data Hardware Installation Local Diagnostics Device Configuration IP Configuration SNMP Configuration Software Update Change Pa
165. ed 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 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 coupler has been started up ERR WRONG DEV TYP 0088hex Cause Incorrect node handle An attempt has been made e g to access the mailbox interface with a node handle for the data interface 3 70 PHCEN IX 615605 CONTACT Driver Software ERR DEV NOT READY 00894 Cause The local bus master was addressed even though it was not ready Remedy After a reset request the local bus master using the Get BSDiagnostic function the ready bit in the diagnostic bit register Once this bit is set the local bus master can be addressed ERR INVLD PERM 008Ahex Cause An attempt has been made to execute a function on a channel for which the relevant access rights we
166. en 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 16 PHCEN IX 615605 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 return ret Data telegram 5225A002 Figure 3 10 Execution of a remote procedure call 615605 PHCENIX 3 17 CONTACT FL IL 24 BK PAC UM E Task Function 3 7 3 Description and Functions of the Device Driver Interface DDI DevOpenNode UNIX In order for the Device Driver Interface DDI to be able to find and address the desired bus coupler 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 coupler The structure of the file and its entries is as follows 192 168 5 76 01 1 IBETHO1N1 D etha2 IBETHO2N1 M IBETHO2N1 D Several device names can be assigned to a single IP address or server name The individ
167. er command has the following format Table 6 24 Write single register Byte No Meaning BYTE 0 Function code 6 BYTE 1 2 Register table offset BYTES3 4 Register value The response to the write single register command has the following format Table 6 25 Response to write single register Byte No Meaning BYTE 0 Function code 6 BYTE 1 2 Register table offset same as command BYTE3 4 Register value same as command If the command accesses an invalid offset the exception response has the following format Table 6 26 Byte No Exception response to write single register Meaning BYTE 0 Function code 0x86 BYTE 1 Exception response 2 6 5 7 1 Register table offset 384 writes the register value into Q1 16 Examples for Write Single Registers Register table offset 576 writes the register value into AQ1 Register table offset 1024 and register value 0 clears the fault table 6 16 615605 PHCENIX CONTACT Modbus TCP Protocol Register table offset 1280 and a register value between 200 and 65000 sets a new timeout value for the Modbus TCP connection Register table offset 2000 and a register value between 200 and 65000 sets a new timeout value for the process data watchdog Offset 2002 can be used to set the fault response mode 1 Reset fault mode 2 Standard fault mode 0 Hold last state mode Any regist
168. er table offset lt 384 or gt 576 and lt 1024 or gt 1024 produces an exception response 6 5 8 Read Exception Status This command reads an 8 bit status of the FL IL 24 BK B PAC The read exception status command has the following format Table 6 27 Read exception status Byte No Meaning BYTE 0 Function code 7 The response to the read exception status command has the following format Table 6 28 Answer to read exception status Byte No Meaning BYTE 0 Function code 7 BYTE 1 Exception status 6 5 9 Exception Status Data Format Table 6 29 Exception status data format Byte No Meaning BYTE 0 5 Not used BYTE 6 Exception status BYTE 7 Unused fault 615605 PHGNIX 6 17 CONTACT FL IL 24 BK PAC UM E 6 5 10 Exception Responses Table 6 30 Exception responses No Designation Meaning 1 ILLEGAL FUNCTION The transmitted function code is not supported by this device version 2 ILLEGAL DATA The transmitted address is invalid for the device the combination of reference ADDRESS 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 will generate exception response 2 3 ILLEGAL DATA The value of this request is invalid for this device VALUE 4 DEVICE FAILURE Plug amp play mode is
169. ermitted in this operating mode Remedy Switch to an operating mode in which the desired call can be executed 615605 PHCENIX ot CONTACT FL IL 24 BK PAC UM E ERR INVLD CONN TYPE 0101 Cause 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 IN process data monitoring failed to activate ERR DATA SIZE 0103hex Cause The data volume to be transmitted exceeds the maximum permissible size Remedy Transmit the data in several cycles ERR_OPT_INVLD_CMD 0200hex 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 parameters ERR ETH RCV TIMEOUT 1001 The time limit for receiving a data telegram was exceeded Remedy The Ethernet connection was interrupted or an incorrect IP address was entered Increase the timeout time ERR IBSETH OPEN 1010hex Cause The IBSETHA file cannot be opened Remedy The IBSETHA file does not exist or is in the wrong directory 3 76 PHGNIX 615605 CONTACT Driver Software ERR IBSETH READ 1013hex Cause The IBSETHA file cannot be read Remedy The file exists but cannot be read You may not have read access ERR_IBSETH_NAME 1014hex Cause The device name can
170. 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 coupler This node handle has direct reference to an internal control structure which contains all the corresponding data for addressing the relevant bus coupler The local node handle is used to obtain all the necessary parameters for addressing the bus coupler such as the IP address socket handle node handle on the bus coupler 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 maximum number of control structures is determined when the library is compiled and cannot subsequently be modified In Windows NT 2000 there are eight 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 DDI 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
171. es why the service could not be executed Add Error Info Additional information on the error cause 4 8 PHCENIX 615605 CONTACT Firmware Services 4 3 2 Set Value Service Task This service assigns new values to INTERBUS system parameters variables A new value is only accepted if no error was detected when the value range was checked The following system parameters are defined Table 4 3 System parameters Variable ID System Parameter Value Comment 0104hex Diagnostic status register Read only 0105hex Diagnostic parameter register Read only 2216hex Current PD cycle time Read only 2240hex Plug amp play mode 0 Plug amp play mode inactive 1 Plug amp play mode active 227 5hex 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 inactive 200 65000 Timeout time in ms Table 4 4 Available fault response modes Fault Response Mode Value Function Reset fault mode 1 The digital outputs are set to 0 The analog outputs are set to a value default default 0 programmed by the user Standard fault mode 0 All outputs are set to 0 Hold last state mode 2 All outputs hold the last value Syntax Set_Value_Request 0750hex Word 1 Word 2 615605 PH NIX 4 9 CONTACT FL IL 24 BK PAC UM E
172. essage Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 Word 7 0001 nex Word 8 Word 9 1 device nth device Negative message Word 1 Word 2 Word 3 Word 4 Bit WE ove E E EEE A 0 830 code of the service confirmation Parameter Count Number of subsequent words with a positive message XXXXhex The value depends on the number of entries and the number and type of attributes that were read with a negative message 0002 2 parameter words Result Result of the service processing 0000hex indicates a positive message The controller board has 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 615605 PHCENIX Tar CONTACT FL IL 24 BK PAC UM E Add Error Info More Follows Frame Reference Used Attributes Start Entry No Entry Count Configuration Entry Additional information on the error cause 0000hex indicates that all requested entries are contained in the service confirmation 000155 indicates that the service confirmation does not contain all requested entries as the amount of data is larger than the mailbox MXI that is available for the services Call the Read Configuration service 03095 to read the remaining data Number of the active configuration frame Read att
173. eus Woe Pr 2 6 1 1 X lin 0 7 Xx X lim A n 0 A 0 Where PEL Total power dissipation in the terminal PBus Power dissipation for bus operation without I O load permanent PPERI 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 nap 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 2 Total current consumption of the devices from the 24 V analog supply map 0 5 A maximum 615605 7 7 PHCENIX CONTACT FL IL 24 BK PAC 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 I O is connected gives the following result 2 2 W 0 35 W 2 55 W 2 55 W corresponds to 100 current carrying capacity of the power supply unit in the derating curves on page 7 6 Make sure that the indicated nominal current carrying capacity in the derating curves is not exceeded when the ambient temperature is above 40 104 F Corresponding with the fo
174. ext supply terminal You can use several segment terminals within a main circuit and in this way 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 circuit If the limit value of the common potential jumper for Uy and or Us is reached total current of Us and Uy a new power terminal must be used 615605 PHCENIX 198 FL IL 24 BK PAC UM E Generation of Ug There are various ways of providing the segment voltage Us 1 You can supply the segment voltage at the Ethernet Inline bus coupler or a power terminal 2 Youcan tap the segment voltage from the main voltage at the Ethernet Inline bus coupler or a power terminal using a jumper or a switch 3 You can use a segment terminal with a fuse Within this terminal the segment voltage is automatically tapped from the main power 4 Youcan use a segment terminal without a fuse and tap the segment voltage from the main voltage using a jumper or a switch EMI rn uns M FL IL 24 BK PAC PWR IN SEG F UL H Uana GNDL t Us 61560003 Figure 1 19 Segment circuit FL IL 24 BK PAC Ethernet Inline bus coupler PWR IN Power terminal
175. ferent types of connectors a single connector can support the following connection methods 2 sensors or actuators in 2 3 or 4 wire technology 4 sensors or actuators in 2 or 3 wire technology 2 sensors or actuators in 2 or 3 wire technology with shield for analog sensors or actuators 1 66 PHCEN IX 615605 CONTACT FL IL 24 BK PAC 1 17 2 Connection Examples for Digital I O 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 changes accordingly A connection example is given in each module specific data sheet Table 1 21 Overview of the connections used for digital input modules Connection Representation in 2 wire 3 wire 4 wire the Figure Sensor signal IN IN X X X Sensor supply Us Uy Us 24 V X X X Ground GND GND 1 X X Ground FE shielding X FE A X Used Not used Table 1 22 Overview of the connections used for digital output modules Connection Representation in 2 wire 3 wire 4 wire the Figure Actuator signal OUT OUT X X X Actuator supply Us Us 24 V X Ground GND GND 1 X X X Ground FE shielding FE A x X X Used Not used 615605 PHCENIX pet CONTACT FL IL 24 BK PAC UM E Different Connection Methods for Sensors and Actuators 2 wire technology
176. figuration software Table 6 37 Structure of the analog output table Analog Output Table Address First output word 576 577 Command word 767 The bits are defined as shown in Table 6 38 The remaining bits are reserved for future use Activation deactivation of plug amp play mode is executed by means of the least significant bit of the command word Bit 0 0 gt PP inactive bit 0 1 gt PP active If a NetFail occurred it can be acknowledged by setting bit 1 in the command word If NetFail has been acknowledged successfully bit 1 is reset to zero Table 6 38 Network interface command word 15 14 13 12 11 10 9 8 7 6 5 4131211 Reserved bits Clear peripherial fault mm Clear NetFail Plug amp play 61560030 6 22 PHCENIX 615605 CONTACT Modbus TCP Protocol 6 6 2 Status Word Table 6 39 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 is automatically reserved by the bus coupler as network interface status word This word allows the Ethernet host controller e g PLC to receive up to date diagnostic information without using a configuration software Only the two least significant bits have a function Bit 0 0 means that a fault occurred e g bus error Bit
177. g mode see Section 3 8 on page 3 33 Table 6 44 Monitoring functions Monitoring Mechanism Monitoring the client the the Ethernet process data application individual connection exchange channels Process data watchdog process X X X data monitoring Host checking X DTI Modbus monitoring X X X 615605 6 25 PHCENIX CONTACT FL IL 24 BK PAC UM E 6 8 Modbus Monitoring A monitoring mechanism can be activated for every Modbus TCP connection in order for the FL IL 24 BK PAC to detect a fault in the network e g defective cable or in the client operating system crash or error in the TCP IP protocol stack and react correspondingly The monitoring mechanism is activated via the relevant TCP connection upon the first read or write procedure To change the timeout value for the relevant TCP connection write the new timeout value to the timeout table to the special address 1280 using the functions fc 6 or fc 16 The value of this entry is the value of the timeout table The time is indicated in milliseconds and ranges from 200 ms to 65000 ms A timeout value of 0 deactivates the monitoring function Values between 1 and 199 as well as values bigger than 65000 ms generate exception response 3 ILLEGAL DATA VALUE After the first access by a Modbus TCP function all other access must be carried out using the entered timeout value Otherwise fault response mode is activated and the Modbus TCP
178. ge 0002 2 parameter words Result Result of the service processing 0000hex indicates a positive message The controller board has executed the service successfully 4 40 PHCEN IX 615605 CONTACT Firmware 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 4 5 Diagnostic Services 4 5 1 Get Error Info Service Task 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 Syntax Get Error Info Request 031 6pex Word 1 Word 2 Bit T Key Code 031644 Command code of the service request Parameter Count Number of subsequent words 0000 No parameter word 615605 PHCENIX m CONTACT FL IL 24 BK PAC UM E Syntax Get Error Info Confirmation 8316 Positive message as long as error localization is still progress Word 1 Word 2 Word 3 Word 4 Word 5 Word 6 0001 hex OBDF hex FFFF hex Positive message if error localization has been completed Word 1 Word 2 Word 3 Word 4 Word 5 1 error Word 6 Negative message Word 1 Word 2 Word 3 Word 4 Bit 0 4 42 PHCENIX 615605 CONTACT Firmware Services Key Code Parameter Count Result Entry Count Error Code
179. ght protected Use of this manual by any third party deviating from the copyright provision is forbidden Reproduction translation or electronic or photographic archiving or alteration re quires 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 regis tered 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 PAC module is designed exclusively for SELV operation ac cording to IEC 60950 EN 60950 VDE 0805 Shielding The shielding ground of the twisted pair cables that can be connected is electri cally connected with the socket When connecting network segments avoid ground loops potential transfers and voltage equalization currents using the braided shield 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 surround ings e g using an ESD wristband which is connected to the grounded DIN rail to which the mo
180. gnostic Services 4 41 4 5 1 Get Error Info Service noni anann n 4 41 4 5 2 Get Version Info Service 4 47 Error Messages for Firmware Services 4 50 4 6 1 GUT TM REM 4 50 4 6 2 Positive Messages esee 4 51 4 6 3 Error Messages ieee 4 51 vexit tr erit ve i SER RENEE 5 3 Transmission of Parameter 5 3 5 1 1 PCP Configuration in the Web Based Management 5 4 5 1 2 Configuration of the PDU Size 5 4 Supported Commands essen 5 5 6 3 Modbus 6 3 6 1 1 Modbus Connections nnne 6 3 6 1 2 Modbus Port ccccccccccccceaseeseseececececceeceeeseessceceeeeeeeeeeseeneasses 6 4 6 1 3 Modbus Conformance Classes 6 4 6 1 4 Modbus Message Format 6 4 6 1 5 Modbus Byte Order 2 0 4 0 6 4 6 1 6 Modbus Bit 2 6 5 Modbus Function Codes eene nnne 6 5 615605 PHCENIX Table of Contents 6 3 Modbus Table sch woth mec Rae den ae ee 6 5
181. guration frame for conformance with the currently connected configuration address overlaps If no errors are detected the controller board activates this configuration frame display PP for plug amp play mode for expert mode 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 Bit 0 0711 Command code of the service request Parameter Count Number of subsequent words 0001 1 parameter word Frame Reference 0001 4 32 PHCEN IX 615605 CONTACT Firmware Services Syntax Activate Configuration Confirmation 8711 hex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit jp 0 Key Code 8711 Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001 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 has executed the service successfully XXXXhex indicates a negative message The
182. he Inline I O system Ethernet TCP IP 10 100 Base T X Management via SNMP Integrated web server Modbus TCP protocol DDI Device Driver Interface protocol software interface Up to 63 additional Inline modules can be connected process data channel up to eight PCP modules can be connected Flexible installation system for Ethernet IP parameter setting via BootP web based management WBM or SNMP 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 615605 PHCENIX c CONTACT FL IL 24 BK PAC UM E Front view of the FL IL 24 BK PAC PH NIX CONTACT FL IL 24 BK PAC Ord No 2862314 FD 00 0 45 50 1 77 COL RCV LINK 10 100 Figure 1 1 Front view of the FL IL 24 BK PAC 61550002 ER PHCENIX CONTACT 615605 FL IL 24 BK PAC 1 2 Figure 1 2 Structure of the FL IL 24 BK PAC Bus Coupler 2 A N at ASKER RR org MA AS AN OM 155 DA SONA ER Structure of the FL IL 24 bus coupler The bus coupler has the following components 1 2 3
183. he input buffer and converts it into Intel format The word index in the input buffer is used as the position The macro reads the double word starting from the specified word address over two words n USIGNB Pointer to the input buffer m USIGN16 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 USIGNB Pointer to the input buffer m USIGN16 Word number USIGN16 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 USIGNSB Pointer to the input buffer m USIGN16 Word number USIGN8 Process data 8 bit IB PD GetDataNLoByte This macro reads the low order byte bit 0 to 7 of a word from the input buffer and converts it into Intel format n USIGNSB Pointer to the input buffer m USIGN16 Word number USIGNS Process data 8 bit 615605 PHCENIX FL IL 24 BK PAC UM E Task Parameters Return value Task Parameters Return value Task Parameters Task Parameters IB PD GetBytePtrHiByte n m 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
184. hex Abort_Request 088Dhex Get_OD_Request 0088hex Read_Request 0081hex Write Request 0082 6 Information Report Request 0885hex Status_Request 0083hex Identify Request 0087hex 7 Initiate Request 00A0nex PNM7 Abort Request 08A11nex Load Kbl Par Loc Request 0264 Service Execution Remote Request 00 1 Read Kbl Loc Request 0203 615605 PHCENIX 5 5 CONTACT FL IL 24 BK PAC UM E 5 6 PHGNIX 615605 CONTACT Modbus TCP Protocol Section 6 This section provides information about 6 2 6 3 6 4 6 5 6 6 the Modbus TCP protocol supported commands 6 3 Modb s Protocol 2 intente aid 6 3 6 1 1 Modbus Connections seeeeeeneeeennene 6 3 6 1 2 Modbus Port cee noe Mina ique 6 4 6 1 3 Modbus Conformance 6 4 6 1 4 Modbus Message 6 4 6 1 5 Modbus Byte Order sese 6 4 6 1 6 Modbus Bit Order cats deena ie 6 5 Modbus Function Codes essen 6 5 Modbus Table iter ete Rer eit ge estu 6 5 6 3 1 Dynamic Modbus TCP Process Data Table 6 6 6 3 2 Example Location of the Input Output Data 6 7 6 3 3 Location of the Process Data in Dynamic Tables 6 8 Applicable Functions ite terit etre tac inb rn
185. ial and data routing 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 1 6 2 Connectors The I O or supply voltages are connected using a pluggable connector This pluggable 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 connectors 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 Inline connector types 615605 PHCENIX 1 17 CONTACT FL IL 24 BK PAC UM E Connector identification 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 19 2 Shield connector This green connector is used for signals connected using shielded cables e g a
186. icated by a line with three dots Parameter blocks Parameter blocks are marked in bold outline The individual parameters are described in the following section 615605 PHCENIX FL IL 24 BK PAC UM E Syntax Name of the Service Confirmation Codenex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit patie en 0 Key Code 8XXXhex Message code of the service confirmation Parameter Count 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 Result of the service processing 0000hex indicates a positive message The controller board has 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 6 PHCENIX 615605 CONTACT Firmware Services Task Syntax Key Word 1 Word 2 Word 3 Bit 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 I
187. ication 615605 PHCENIX 1 21 CONTACT FL IL 24 BK PAC UM E Labeling terminal numbering Slot connector Terminal point Additional labeling Terminal point numbering is illustrated using the example of an 8 slot module D 5520A035 Figure 1 9 Terminal point numbering The slots connectors on a base are numbered consecutively 1 in Figure 1 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 Figure 1 9 Y is the terminal point number in a row It is directly indicated on the terminal point 3 in Figure 1 9 The precise designation for a connection point is thus specified by the slot and terminal point The highlighted terminal point 4 in Figure 1 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 1 22 PHCEN IX 615605 CONTACT FL IL 24 BK PAC 5520A036 Figure 1 10 Labeling of modules Various options are available for labeling the slots and terminal
188. iguration Device Level According to the known configuration Group Number For all INTERBUS devices FFFFhex i e no group numbers are supported Device State All INTERBUS devices are active Create Configuration Request 0710 0710hex Command code of the service request 4 30 PHCENIX 615605 CONTACT Firmware Services Parameter Count Number of subsequent words 0001 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 ee cee eee eee tee eee eee eet ee ee A eer 0 Key Code 8710 Message code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0001 1 parameter word with a negative message 0002 2 parameter words Result Result of the service processing 0000hex indicates a positive message The controller board has 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 615605 PHCENIX 2 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 confi
189. ilModelnfo 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 optional 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 IBDDIHND nodeHd Node handle of a controller board for which the NetFail mode is to be changed ETH NET FAIL MODE netFailModelnfo Pointer to a 7 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 Parameter for the relevant NetFail mode NET FAIL MODE The function prototypes the type definition of the data structure and the symbolic constants can be found in the IOCTRL H file 3 50 PHCENIX 615605 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 7 ETH NET FAIL MODE data structure see above
190. ill 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 72 PHCENIX 615605 CONTACT Driver Software 3 15 3 Error Messages When Transmitting Messages Commands ERR MSG TO LONG 009Ahex Cause 1 If an error message occurs when sending a command then the length of the command exceeds the maximum number of permitted parameters Remedy Reduce the number of parameters Cause 2 If an error message occurs when receiving a message then the length of the message exceeds the length of the receive buffer specified Remedy Increase the length of the receive buffer ERR_NO_MSG 009Bhex Cause This message occurs if an attempt has been made to retrieve a message using the DDI MXI RcvMessage function but no message is present for the node specified by the node handle ERR NO MORE MAILBOX 009Chex Cause 1 You have requested too many mailboxes within a short time Remedy Increase the time interval between individual mailbox requests and restart the DDI_MXI_SndMessage service Cause 2 No further mailbox of the required size is available Observe the maximum mailbox size that can be used 1020 bytes Remedy Select a smaller mailbox or wait until a mailbox of the required size is free again Cause 3 An attempt was made to address the coprocessor board COP but it is faulty Remedy Please get in touch with Phoenix Contact ERR_SVR_IN_USE 009D
191. ing and Removing Inline 1 47 148533 Mounting eingegeben 1 48 1 19 4 Removing rn te ce ERE 1 50 1 13 5 Replacing a FUSE Sepre insana naea 1 52 Grounding an Inline 1 54 1 14 1 Shielding an Inline 1 56 1 14 2 Shielding Analog Sensors and Actuators 1 56 1 59 1 15 1 Connecting Unshielded Cables 1 59 1 15 2 Connecting Shielded Cables Using the Shield Connector 1 61 Connecting the Voltage Supply sene 1 64 1 16 1 Power Terminal Supply seen 1 64 1 16 2 Provision of the Segment Voltage Supply at Power Terminals iit nte erede 1 65 1 16 3 Demands on the Power Supply 1 65 Connecting Sensors and 1 66 1 17 1 Connection Methods for Sensors and Actuators 1 66 1 17 2 Connection Examples for Digital I O Modules 1 67 1 2 PHCNIX 615605 CONTACT FL IL 24 BK PAC 1 24 BK PAC 1 1 General Functions 1 1 1 Product Description Ethernet Inline bus coupler Features Ethernet coupler for t
192. 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 IBDDIRET ddiRet ddiRet ETH ClearDTITimeoutCtrl ddiHnd 615605 PHCENIX R CONTACT FL IL 24 BK PAC UM E Table 3 6 3 8 4 I O Fault Response Mode In case the communication connection is disrupted the user can select the reaction of the FL IL 24 BK PAC beforehand Use the DDI command 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 The analog outputs are set to a value default 0 programmed by the user Standard fault mode All outputs are set to O Hold last state mode All outputs hold the last value Table 3 7 The FL IL 24 BK PAC only has one internal volatile memory where the process data is stored during runtime This memory image is cyclically mapped to the appropriate Inline modules 3 8 4 1 Power up Table Power up sequence Power up Sequence Status of the FL IL 24 BK PAC Configuration Reset Fault Mode Configuration Last State Fault Mode Internal memory Actual output Internal memory Actual output all new values all new values Power up 04 04 04 oe Fi
193. le Figure 1 37 detail 6 If you need to change the direction of the shield connection clamp proceed as shown in Figure 1 37 e Open the shield connector housing 1 e The shield connection is delivered with the clamp positioned for connecting thicker cables 2 e Remove the clamp 3 turn it to suit the cross section of the cable 4 then reinsert the clamp 5 e Figure 6 shows the position of the clamp for a thin cable 615605 PHCENIX 1 63 CONTACT FL IL 24 BK PAC UM E 1 16 Connecting the Voltage 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 see Section 1 15 1 Electrical isolation Voltage areas 1 16 1 Power Terminal Supply Apart from supplying the I O voltage at the Fieldbus coupler it is also possible to provide the voltage using a power terminal 24 V Main Circuit Supply The main power is reintroduced at the power terminal 24 V 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 potential area through the power terminal Power terminals can be used to create substations with different voltage areas Depending on the power terminal it is possible to work
194. le 1 3 Digital Input Output Modules Designation Contd Properties Order No IB IL 24 230 DOR 4 W 4 SPDT relay contacts 5 V 253 V AC 28 36 42 1 IB IL 24 230 DOR 4 W 4 SPDT relay contacts 5 V 253 V AC 3A 28 61 87 8 PAC IB IL 24 230 DOR 4 W PC 4 SPDT relay contacts 5 V 253 V AC 3 A for inductive and 28 60 41 3 capacitive loads IB IL 24 230 DOR 4 W 4 SPDT relay contacts 5 V 253 V AC for inductive and 28 62 18 1 PC PAC capacitive loads IB IL 24 48 DOR 2W 2 SPDT relay contacts 5 V 50 V AC 5 V 120 V DC 2A 28 62 97 4 IB IL 24 48 DOR 2W PAC 2 SPDT relay contacts 5 V 50 V AC V 120 V DC 2A 28 63 11 9 Table 1 4 Analog input output modules Designation Properties Order No IB IL AI 2 4 20 2 inputs 2 wire termination 24 V DC 0 10 V 10 V 28 60 442 0 20 mA 4 20 mA 20 mA IB IL AI 2 4 20 PAC 2 inputs 2 wire termination 24 V DC 0 10 V 10 V 28 62 217 0 20 mA 4 20 mA 20 mA IB IL Al 2 SF 2 inputs 2 wire termination 24 V DC 0 10 V 10 V 27 26 28 5 0 20 mA 4 20 mA 20 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 30 2 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 10 V 27 40818 0 20 mA 4 20 mA 20 mA 0 40 mA 40 230 Hz IB IL AI 2 SF 230 PAC 2 inputs 2 wire termination 24 V DC 0 10 V 10 V 2861577 0 20 mA 4 20 mA 20 mA 0 40 mA 40
195. ll as to the fault table Table 6 5 Applicable functions Function Functio READ TAB Al TAB TAB TAB Special Dynam n Code WRITE Register Tables Read coils 1 READ X Read input 2 READ X discretes Read multiple 3 READ X X X X X X register Read input 4 READ X X X X X X register Write coils 5 WRITE X Write single 6 WRITE X X X Read 7 READ exception code Write multiple 15 WRITE X coils Write multiple 16 WRITE X X X X register Read write 23 READ X X X X X registers WRITE 6 5 Supported Function Codes The function codes are defined for the Modbus memory mapping so to determine what area of the memory is affected refer to table Table 6 8 which maps the Modbus table names to their corresponding FL IL 24 BK PAC table names The FL IL 24 BK PAC supports the following Modbus function codes Read multiple register function code 3 Write multiple register function code 16 Read coils function code 1 Readinput discretes function code 2 Readinput register function code 4 Write coils function code 5 615605 PHCENIX 6 9 CONTACT FL IL 24 BK PAC UM E Write single register function code 6 Read exception status function code 7 Write multiple coils function
196. lled the timeout time calculated by the bus coupler can be found in the USIGN16 time variable Syntax IBDDIRET IBDDIFUNC ETH_SetDTITimeoutCtrl IBDDIHND nodeHd USIGN16 time Parameters IBDDIHND nodeHd Node handle DTI for the bus coupler that is to be monitored 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 can be set to a value in the range from 110 ms 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 42 PHCENIX 615605 CONTACT Driver Software Task Syntax Parameter Return value ETH_ClearDTITimeoutCtrl The ClearDTITimeoutCtrl 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 nodeHd IBDDIHND nodeHd Node handle DTI for the bus coupler 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
197. local network If 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 mask 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 to device 2 using the above subnet mask Device 2 has IP address 59 EA 55 32 IP address representation for device 2 Hexadecimal notation 59 EA 55 32 Binary notation 0101 1001 1110 1010 0101 0101 0011 0010 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 615605 PH NIX 2 9 CONTACT FL IL 24 BK PAC UM E 2 7 Web Based Management The FL IL 24 BK PAC has a web server which generates the required pages for w
198. lues in the output table plus the newly written 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 the following values are output Module AO DO 16 DO2 Value 0x0010 OxACDC 0 0001 This is the Last values the output table plus the newly written values state 615605 PHCENIX CONTACT 6 29 FL IL 24 BK PAC UM E 6 10 Modbus TCP PCP Registers There are two classes of PCP registers Communication register for data exchange with the desired PCP device Configuration register for selecting the Invoke ID index and subindex of a PCP device The FL IL 24 BK PAC supports eight PCP devices which means that eight communication registers and 24 configuration registers are supported Table 6 48 PCP registers PCP BK Communication Configuration Remark Communication Register Register Reference CR2 6020 6021 Index 6022 Subindex 6023 Invoke ID 6024 6029 Reserved CR3 6030 6031 Index 6032 Subindex 6033 Invoke ID 6034 6039 Reserved CR4 6040 6041 Index 6042 Subindex 6043 Invoke ID 6044 6049 Reserved CR5 6050 6051 Index 6052 Subindex 6053 Invoke ID 6054 6059 Reserved CR6 6060 6061 Index 6062 Subindex 6063 Invoke ID 6064 6069 Reserved CR 7 6070 6071 Index 6072 Su
199. lute encoder input 24 V DC 28 19 57 4 1 12 615605 PHCENIX CONTACT FL IL 24 BK PAC Table 1 5 Special function modules Designation Properties Order No IB IL INC 1 incremental encoder input 4 digital inputs 4 digital outputs 500 2836 324 mA 3 wire termination 24 V DC IB IL INC PAC 1 incremental encoder input 4 digital inputs 4 digital outputs 500 2861849 mA 3 wire termination 24 V DC IB IL INC IN 1 incremental encoder input with square wave signal 1 digital 28 19228 signal for reference signal 2 digital inputs 24 V DC IB IL INC IN PAC 1 incremental encoder input with square wave signal 1 digital 28 61 755 signal for reference signal 2 digital inputs 24 V DC IB IL CNT 1 counter input 1 control input 1 digital output 500 mA 3 wire 28 36 337 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 length measuring systems with pulse 28 19 23 1 interface IB IL IMPULSE IN PAC 1 input for magnetostrictive length measuring systems with pulse 28 61 852 interface IB IL POS 200 Inline positioning control 28 19 338 IB IL POS 200 PAC Inline positioning control including accessories 28 61 823 IB IL RS 232 Terminal for serial data transmission via RS 232 27 27 349 IB IL RS 232 PAC Terminal for serial dat
200. mation about firmware functions Firmware Semvices e ri ar tem ivid arie fad Ba Cun canale 4 3 4 1 OVelVIOW Qa MORE dte mene 4 3 4 1 1 Services Available in Both Operating 4 3 4 1 2 Services Available Only in Expert 4 4 4 2 Notes on Service Descriptions 4 2 1 Name of the Service Service 4 3 Services for Parameterizing the Controller Board 4 7 4 3 1 Control Parameterization 4 3 2 Set Value Service ane b ee 4 3 3 Read Value Service 4 3 4 Initiate Load Configuration Service 4 3 5 Load Configuration Service esses 4 3 6 Terminate Load Configuration Service 4 3 7 Read Configuration Service 4 3 8 Complete Read Configuration Service 4 3 9 Delete Configuration 4 3 10 Create Configuration Service 2 4 3 11 Activate Configuration Service 4 3 12 Control Device Function 4 3 13 Reset Controller Board 4 4 Services for Direct INTERBUS Access 4 4 1 Start Data Transfer
201. ment Position E PNM12 CONFIG LB TOO LONG OUT OD9Chex 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 4 46 615605 PHCENIX CONTACT Firmware Services 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 Code Word 2 Parameter Count Bit WD eine pee teed 0 Key Code 032Ahex Command code of the service request Parameter Count Number of subsequent words 000044 No parameter word Syntax Get Version Info Confirmation 832 Positive message Word 1 Code Word 2 Parameter Count Word 3 Result Words 4 5 FW Version byte 1 FW Version byte 2 FW Version byte 3 FW Version byte 4 Words 6 8 FW State byte 1 E ER FW State byte 6 Words 9 11 FW Date byte 1 ES m FW Date byte 6 Words 12 14 FW Time byte 1 E ze FW Time byte 6 Words 15 24 Host Type byte 1 m Host Type byte 20 Words 25 26 Host Version byte 1 Host Version byte 2 Host Version byte 3 Host Version byte 4 Words 27 29 Host State byte 1 m Host_State byte 6 Words 30
202. mponentsIndex 2 flComponentsName 3 flComponentsDescr 1 flComponentsURL 1 flComponentsOrderNumber flBasicName OID 1 3 6 1 4 1 4346 11 1 1 1 Syntax Display string Access Read Description Contains the name of the product group Factory Line flBasicDescr OID 1 3 6 1 4 1 4346 11 1 1 2 Syntax Display string Access Read Description Contains a brief description of the product group Ethernet installation system flBasicURL OID 1 3 6 1 4 1 4346 11 1 1 3 Syntax Display string Access Read Description Contains a URL for the product group http www factoryline de flBasicCompCapacity OID 1 3 6 1 4 1 4346 11 1 1 4 Syntax Integer32 1 1024 Access Read Description Contains the number of different components that can be controlled by this device 2 32 PHCEN IX 615605 CONTACT Startup Operation flComponentsTable flComponentsEntry OID 1 3 6 1 4 1 4346 11 1 2 1 1 Syntax Access Description Generates a table with descriptions for components in the Factory Line product group which can be controlled by this management device flComponentsIndex OID Syntax Access Description 1 3 6 1 4 1 4346 11 1 2 1 1 1 Integer32 1 1024 Read Contains the component product index flComponentsName OID Syntax Access Description 1 3 6 1 4 1 4346 11 1 2 1 1 2 Display string Read Contains the designation of the component flComponentsDescr OID 1 3 6 1 4 1 4346 11 1 2 1 1 3
203. nalog I O signals FE or shielding is connected via a shield connection clamp rather than via 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 10 Terminal point color coding Color Terminal Point Signal Red Blue Green yellow Functional earth ground 1 18 PHCEN IX 615605 CONTACT FL IL 24 BK PAC Internal structure of the connectors H I I E il pum pem pem pem 1 2 32 1 2 88 68 68 ie 5 cA 4 5 5 DI ide 88 B8 pm Og NN 61560011 Figure 1 6 Internal structure of the connectors 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 already integrated in the connectors are shown in Fig
204. negative message 000244 2 parameter words Result Result of the service processing 0000hex indicates a positive message The controller board has 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 615605 PHCENIX 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 display PP for plug amp play mode for expert mode Syntax Alarm Stop Request 1303 Word 1 Word 2 Bit NE SSD BESS 180344 Command code of the service request Parameter Count Number of subsequent words 0000 No parameter word Syntax Alarm Stop Confirmation 9303 Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit jo 0 9303hex Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001 1 parameter word with a negative messa
205. network connection ready to operate OFF Physical network connection interrupted or not present 615605 PHCENIX FL IL 24 BK PAC UM E 1 42 2 Indicators on the Supply Terminal UN 2 3 1 1 mI 4 m 4 OO QO QO aa ant dne 61560022 Figure 1 27 Possible indicators on supply terminals segment terminal with and without fuse and power terminal Diagnostics The following states can be read from the supply terminals Table 1 15 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 16 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 17 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 niga CONTACT FL IL 24 BK PAC 1 42 3 Indicators on the Input Output Modules
206. nex Cause The send vector register for the node is in use Remedy Address the register again or wait until the register is available again 615605 PHCENIX vm CONTACT FL IL 24 BK PAC UM E Meaning Cause Remedy Meaning Cause Remedy ERR SVR TIMEOUT 009 If a message placed 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 Phoenix Contact ERR AVR TIMEOUT 009F hex 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
207. nfirmation Remark The Default Parameter parameter can also be used to indicate whether the process data channel PD channel and or the PCP channel are 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 communication relationship list CRL Syntax Terminate Load Configuration Request 0308hex Word 1 Word 2 Word 3 Bit Key Code 0308hex Command code of the service request Parameter Count Number of subsequent words 0001hex 1 parameter word Default Parameter Indicates whether a default parameterization of the PCP and or PD channel is to be carried out for the loaded configuration 0000 No automatic parameterization 0001hex Automatic parameterization of the process data channel through the creation of the process data reference list 0002 Automatic parameterization of the PCP channel through the creation of the communication relationship list 0003hex Automatic parameterization of the process data and PCP channel 4 18 PHCENIX 615605 CONTACT 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 SEE ee AE A A AAE E 0 Key Code 8308hexMessage code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001
208. ng the following services Load Configuration 0307 or Complete Load Configuration 030A16x To transmit a new configuration frame New Config parameter 0001 specify the Frame Reference and Device Count parameters total number of devices The parameterization phase must have been initiated with the Control Parameterization 030 service before Syntax Initiate Load Configuration Request 0306 Word 1 Word 2 Word Word 4 Word 5 Word 6 Bit Key Code 030644 Command code of the service request Parameter Count Number of subsequent words XXXXhex 3 Extension Length 1 2 New Config 0001454 configuration frame is created again An existing configuration frame is overwritten 000 updates the existing configuration frame Frame Reference 0x0001 nex 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 615605 PHCENIX Tis CONTACT FL IL 24 BK PAC UM E Syntax Initiate Load Configuration Confirmation 8306 Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit 0 8306 44 Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001 1 parameter word with a nega
209. ng to IEC 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 Operation 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 A in the vicinity IEC 61000 4 4 burst Criterion B IEC 61000 4 5 surge Criterion B IEC 61000 4 6 conducted noise immunity Criterion A IEC 61000 4 8 noise immunity against magnetic Criterion A fields EN 55011 noise emission Class A Warning Portable radiotelephone equipment P gt 2 W must not be operated any closer than 2 m 6 56 ft There should be no strong radio transmitters or ISM industrial scientific and medical devices Approvals Approvals CUL 508 cUL 2279 cUL 1604 Class 1 Div 2 7 10 PHCENIX 615605 CONTACT Technical Data 7 1 Ordering Data Description Order Designation Order No Ethernet Inline bus coupler with connector and labeling field FL IL 24 BK PAC 2
210. nline 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 when 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 0001 1 parameter word Control Code Function of the service 0001 initiates the parameterization phase 000 terminates the parameterization phase 615605 PHCENIX TI CONTACT FL IL 24 BK PAC UM E 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 830EhexMessage code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001 1 parameter word with a negative message 00024 2 parameter words Result Result of the service processing 0000hex indicates a positive message The controller board has executed the service successfully XXXXhex indicates a negative message The controller board could not execute the service successfully The Result parameter indicat
211. nnect 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 Ugk 24 V U 7 5 V and U ayna 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 and the segment main voltage Us Uy do not connect the GND and GNDypx grounds of the supply voltages 615605 PHCENIX Tap CONTACT FL IL 24 BK PAC UM E Option 1 The Fieldbus coupler main voltage Uy and the I O supply Us are provided separately with the same ground potential from two voltage supplies Local bus U ANA UL uC Ethernet 61560004 Figure 1 20 Potential areas in the bus coupler two voltage supplies Potential areas Ethernet interface area Functional earth ground PE and shield Ethernet interface area Main voltage Uy and I O voltage Us area Inline communications power 1 36 PHCENIX 615605 CONTACT FL IL 24 BK PAC Option 2 Common supply of voltages Uy and Us from one voltage supply Local bus UL Unna 0 GNDy uc 3 24 V Us Usk Um Us 24 V Uy GNDys GND Ethernet 61560005 Figure 1 21 Bus coupler potentials one voltage supply Potential areas 1 Ethernet interface area 2 Functional earth ground
212. nnection gt 1 50 PHCENIX 615605 CONTACT FL IL 24 BK PAC 61560007 Removing a module Figure 1 30 follow the removal If you want to replace a module within the Inline station Replacing a module procedure described above Do not snap the connector of the module directly to the left back on yet First connectors insert the base of the new module Then reconnect all the 1 51 PEE MIX CONTACT 615605 FL IL 24 BK PAC UM E 1 13 5 Replacing a 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 Use the screwdriver carefully to avoid injury Lift the fuse out at the metal contact Do not lift the fuse out at the glass part as you may break it Carefully lift the fuse out at one side and remove it by hand Make sure the fuse does not fall into your system 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 1 52 PHCEN IX 615605 CONTACT FL IL 24 BK PAC 5520C011 Figure 1
213. not be found in the file Remedy The name which was transferred to the DDI DEVOPEN NODE function is not in the IBSETHA file ERR IBSETH INTERNET 1016 Cause The system cannot read the computer name host address Remedy The IP address entered in the IBSETHA file is incorrect or the symbolic name cannot be found in the host file 615605 PHCENIX 3 77 CONTACT FL IL 24 BK PAC UM E 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 PAC The inputs are individually jumpered to the outputs The ground potential is created by the internal potential jumper FL IL 24 BK PAC IB IL DO 8 IB IL DI 8 FL IL 24 BK PAC RESET Ord No 2862314 QQ 100 EATEN NANA FD COL O XMT RCV LINK OO 10 100 ea M 4 Q8 61560019 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 coupler on which the program is to be executed This is specified using the registry entries p
214. nt MODEN Lo datas 6 9 Supported Function Codes sse 6 9 6 5 1 Read Multiple 22222121 6 10 6 5 2 Write Multiple Registers esee 6 11 6 5 3 Read Goils el 6 12 6 5 4 Read Input Discretes 21042222111 6 13 6 5 5 Read Input Registers 222222112 2 6 14 6 5 6 aoe alee 6 15 6 5 7 Write Single 0 6 16 6 5 8 Read Exception 6 17 6 5 9 Exception Status Data 6 17 6 5 10 Exception 6 18 6 5 11 Write Multiple 6 19 6 5 12 Read Write Register 6 20 Reserved Registers for Command and Status 6 22 6 6 1 Gomimird WOtgd eoe iter vie eed aan 6 22 6 6 2 Status Word aara 6 23 6 6 3 Diagnostics Using the Analog Input Table 6 23 6 6 4 Fault Table te RD oH RUNE 6 24 615605 PHCENIX x CONTACT FL IL 24 BK PAC UM E 6 7 Monitoring 6 25 6 8 Modbus Monitoring eee 6 26 6 9 I O Fault Response Mode essen 6 26 6 9 1 Power Up Table cedere 6 27 6 9 2 Connection Monitoring 6 28 6 10 Modbus TCP PCP
215. o the local bus devices DTI monitoring can detect if a message to the data interface of the bus coupler 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 from 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 therefore not enable monitoring for another connection Once access has been enabled for the first time all subsequent access must be enabled within the set timeout otherwise the NetFail signal is activated 3 40 PHCEN IX 615605 CONTACT Driver Software Deactivating Monitoring Monitoring is deactivated by calling the ETH ClearDTITimeoutCtrl function or by closing the relevant DTI node using the DDI DevCloseNode function If a connection is interrupted by the bus coupler as a result of DTI monitoring the monitoring mode for this connection is deactivated and the corresponding DDI node is closed see also SETDTITimeoutCTRL If the bus coupler detects that a connection has been interrupted without the node having been
216. oard has 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 615605 PHCENIX 4 37 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 display PP for plug amp play mode for expert mode 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 Na T 0701hex Command code of the service request Parameter Count Number of subsequent words 0000hex No parameter word 4 38 PHCEN IX 615605 CONTACT Firmware Services Syntax Start Data Transfer Confirmation 8701 hex Positive message Word 1 Word 2 Word 3 Negative message Word 1 Word 2 Word 3 Word 4 Bit eee ee eee epee eee EIE 0 Key Code 8701hexMessage code of the service confirmation Parameter_Count Number of subsequent words with a positive message 0001 1 parameter word with a
217. of a shielded 4 wire sensor The sensor signal is carried to terminal point IN1 The sensor is supplied via terminal points Ug and GND The sensor is grounded via the FE terminal point Actuator Figure 1 40 detail B shows the connection of a shielded actuator The provision of the supply voltage Ug means that even actuators that require a separate 24 V supply can be connected directly to the terminal 1 70 PHCENIX 615605 CONTACT Section 2 This section provides information about startup assigning IP parameters the Management Information Base MIB iirzigiuje Qe Iriiojq me PE 2 3 2 1 Default Upon Delivery Default Settings 2 3 2 2 Firmware Start neo eese OR RUNE TE 2 3 2 3 Transmitting BootP 8 2 4 2 4 Assigning an IP Address Using the Factory Manager 2 4 2 4 1 BOOtP RO RSBUDU DE IH BEBE 2 4 2 5 Manual Addition of Devices Using The Factory Manager 2 5 2 6 Selecting IP Addresses 0 0 2 5 2 6 1 Possible Address 5 2 7 2 6 2 S bhet MaskS rne eee e ere cdi quus 2 8 2 6 3 Structure of the Subnet 2 8 2 7 Web Based 2 10 2 7 1 Calling Web Based Management WBWM
218. ombination of the register table offset and the word count which accesses an offset gt 767 and lt 1024 produces an exception response An exception response is also generated when trying to read the fault table while giving a register table offset gt 1024 or a word count lt gt 64 The special registers 1280 2004 can only be read when the word count equals one 6 5 2 Write Multiple Registers This command writes from 1 to 100 16 bit words in the Modbus register table Only the part of the Modbus register table mapped to the Q and AQ I O tables may be written using this function The write multiple registers command has the following format Table 6 9 Write multiple registers 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 response byte count 2 x word count 6 5 Register values The response to the write multiple registers command has the following format Table 6 10 Response to write multiple registers Byte No Meaning BYTE 0 Function code 0x10 BYTE 1 2 Register table offset same as command BYTE 3 4 Word count same as command If the command accesses an invalid offset or contains an invalid length an exception response in the following format is output 615605 PHCENIX 6 11 CONTACT FL IL 24 BK PAC UM E Table 6 11 Exception response to write
219. on 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 product range Topics are for example Overview of the Inline product groups Terminal structure Terminal installation 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 Up to the time that a new manual revision is published any updates or changes will be documented on the Internet at www phoenixcontact com or www factoryline de PHCEN IX 615605 CONTACT 1 FLIL 24 BK PAC Table of Contents 1 2 1 8 1 4 1 5 1 6 1 7 1 8 1 9 1 10 1 12 ES 1 3 General FUNCIONS 2 merece de 1 3 1 1 1 Prod ct DescriptiOr 1 3 Structure of the FL IL 24 BK PAC Bus 1 5 1 2 1 Local Status and Diagnostic Indicators 1 6 Connecting the Supply Voltage seen 1 7 Connector Assignment nnne neni 1 8 Supported Inline 0 44 4 00 en 1
220. ontrol clr Factory Line OPC Configurator Sensor T 2 x File Edit Paste View Help M General ck gt X New Up Cut Copy Einl Sensor T Robot 1 E g Robot_Control L IN Data Sensor T Type Item 2 1 OUT Data Location Robot_Control cl Robot_Control IN Data OPC ItemID IN Data SensorT Search in ms 4 Name Address Byte Bit IN BYTE 0 Input 0 lt IN Input 0 0 1 writeable 91 BIT 01 Input 01 Input 0 2 Input 0 3 Input 0 4 Input 0 5 Input 0 6 Input 0 7 Cancel Selection Select Close Figure 2 8 Linking items and terminal points IS The entire configuration can be carried out offline 615605 PHCENIX 2 23 CONTACT FL IL 24 BK 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 the local bus configuration OPC Communication Configure the OPC server from Phoenix Contact for this type of bus coupler 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 11 Management Information Base
221. ontrol message protocol group is mandatory for all systems It contains information about error treatment and control in Internet data traffic 5 icmp 1 iempInMsgs 2 iempInErrors 3 icmpinDestUnreachs 4 icmpInTimeExcds 5 iempInParmProbs 6 icmpinSrcQuenchs 8 FL gt IL a 7 icmplInRedirects 9 icmpInEchoReps 10 icmpInTimestamps 0 1 icmpInTimestampReps icmplnAddrMasks icmpInAddrMaskReps iempOutMsgs iempOutErrors iempOutDestUnreachs iempOutTimeExcds iempOutParmProbs iempOutSrcQuenchs 20 icmpOutRedirects i i i i i i 615605 PHCENIX ud CONTACT FL IL 24 BK PAC UM E Transfer Control Protocol Group TCP 1 3 6 1 2 1 6 The transfer control protocol group is mandatory for all systems that implement TCP Instances for objects which provide information about a specific TCP connection apply as long as the connection is established 6 tcp 1 tepRtoAlgorithm 2 tcpRtoMin 3 tcpRtoMax 4 tcpMaxConn 5 tcpActiveOpens 4 ipRouteMetric2 6 tcpPassiveOpens 7 tcpAttemptFails 8 tcpEstabResets 9 tcpCurrEstab 0 05 1 tcpOutSegs 2 tcpRetransSegs 13 tcpConnTable 1 tepConnEntry 1 tepConnState 2 tcpConnLocalAddress 3 tepConnLocalPort 4 tcpConnRemAddress 5 tepConnRemPort 14 tcpInErrs 15 tcpOutRsts
222. 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 DDI READ 0x0001 Read only access DDI WRITE 0x0002 Write only access DDI RW 0x0003 Read and write access 615605 PHCENIX is CONTACT FL IL 24 BK PAC UM E Example Task IS Syntax Parameter Return value Windows NT 2000 UNIX IBDDIHND ddiHnd IBDDIRET ddiRet ddiRet DDI DevOpenNode IBETHO1N1_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 This function uses only the node handle as a parameter which determines 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 nodeHd 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 20 PHCENIX 615605 CONTACT Driver Software Example UNIX Windows NT 2000 IBDDIHND ddiHnd IBDDIRE
223. or write access DDI DTI ACCESS readDTIAcc Pointer to a 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 26 PHCEN IX 615605 CONTACT Driver Software Format of the typedef struct T DDI DTI USIGN16 length ACCESS structure Amount of data to be read in bytes USIGN16 address Address in the DTI area byte address USIGN16 dataCons Desired data consistency area USIGNS8 data Pointer to the data read and write T DDI DTI ACCESS Example UNIX Windows NT 2000 IBDDIHND 1 IBDDIRET ddiRet T 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 615605 PHCENIX FL IL 24 BK PAC UM E Task Syntax Parameters Return value Format of the DDI MXI SndMessage The DDI MXI SndMessage function is used to send a message to the bus coupler The function receives a node handle
224. oring sends a short data telegram to a client every 500 ms This interval is predefined and does not even change with 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 coupler waits for a user defined time for the reply to be received If the reply is not received within this time the bus coupler sends another data telegram to the relevant client This process is repeated a maximum of three times Connection monitoring then assumes that a serious error has occurred and sets the NetFail signal outputs are set to zero 615605 PHCENIX 97 FL IL 24 BK PAC UM E Deactivating Monitoring If connection monitoring is no longer required it 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 coupler 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 client is 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 Computer ETH Set
225. osition 01 to 99 The entry must always be two digits 3 78 PHCENIX 615605 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 00 9 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 is output and if they are different Comparison FAILED is output After the process data item 255 has been output the program is terminated after a 3 second waiting time The following figure is a screenshot of the program E DEMO_O1 exe 1506 Benoetigter Busauf bau IB IL 24 DI 8 ii IB IL 24 DO 8 Controllernummer Format xx gt gt IBETHO3N1 D Mailboxverbindung OK Haendel 64 Datenkanalverbindung OK Haendel 65 Plug amp Play Modus IBS Status RUNNING Daten schreiben lesen und vergleichen Geschrieben 17 Gelesen 17 Uergleich OK Figure 3 15 Screenshot of the example program 615605 PHCENIX 3 79 CONTACT FL IL 24 BK PAC UM E 3 16 2 Example Program Source Code
226. ounded DIN rail IS 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 615605 PHCENIX 1 55 CONTACT FL IL 24 BK PAC UM E 1 44 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 Fasten the shielding so that as much of the braided shield as possible is held underneath the clamp of the shield connection Make sure there is good contact between the connector and module Do not damage or squeeze the wires Do not strip off the wires too far a clean wire connection 1 44 2 Shielding Analog Sensors and Actuators Table 1 20 Overview shield connection of analog sensors actuators Module Type Connection to the Module Cable Length Connection to the Sensor Actuator Analog input module Within the module ground is 10m IB IL AI 2 SF connected to FE via an RC 32 81 ft element gt 10m Connect the sensor directly to PE 32 81 ft Analog output module Via shield connection clamp lt 10m IB IL directly to FE 32 81 ft 10m Isolate the actuator with an RC 32 81 ft element and connect it to PE
227. oupler Reading the Fault Table Data The entire fault table can be read using the read multiple registers command starting at the beginning of the fault table 1024 with a length of 64 registers It is impossible to only read parts of the fault table Empty entries contain the value 0 IS Deleting the Fault Table Data If required the application may write the value 0 into the first register 1024 of the fault table using the write single register command A client cannot write to any other register Table 6 42 Registers Diagnostic parameter register Diagnostic status register 6 24 PHCENIX 615605 CONTACT Modbus TCP Protocol Fault Table Entries Each fault entry is two words in length and is formatted as follows If a fault occurs one or more bits are set in the diagnostic status register PF BUS or CTRL and a new entry is added to the fault table The representation of the fault table entry is shown in the following table Table 6 43 Fault table Fault Table Fault No Fault 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 6 7 Monitoring The three following monitoring mechanisms are available in the Modbus operatin
228. oupler and repeat the update using a valid firmware Boot loader 21 80 The bus coupler starts with the firmware already available Check the firmware version on the Device Information web page and repeat the update if necessary 19 The tftp download was completed Provide a valid firmware version with the successfully but the file is not a previously specified file name valid firmware version for the bus Repeat the download coupler Boot loader lt 1 80 Restart the bus coupler and repeat the update using a valid firmware Boot loader gt 1 80 By a reset the bus coupler starts with the firmware already available Check the firmware version on the Device Information web page and repeat the update if necessary Table 2 6 Firmware error messages Display Meaning Remedy 80 An error occurred in the Restart the device firmware Power up or reset 81 An error occurred when Restart the device accessing the EEPROM Power up or reset 82 The known configuration could Use Get Error Info to check whether any faulty not be activated modules are present 615605 PHCENIX 2 45 CONTACT FL IL 24 BK PAC UM E Table 2 6 Firmware error messages Contd Display Meaning Remedy 83 The known configuration could Create a configuration which corresponds to the not be activated because the reference configuration known configuration and the Activate P amp P mode reference configuration are not
229. ouplers In particular process data exchange is supported via OPC in an easy to use manner You can find the software on the CD FL IL 24 BK CD Order No 28 32 06 9 The I O configurator is divided into two parts I O browser OPC configurator 2 10 1 Factory Line I O Browser The I O browser is used to create the bus configuration From all supported modules select those you want to use in your station later offline configuration or those you are using currently online configuration During online configuration you have the possibility to read and test an existing bus configuration Configuration During system planning the I O configurator offers an integrated online product catalog using XML technology to help ensure optimum 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 using the integrated INTERBUS technology 615605 PHGNIX 2 21 CONTACT FL IL 24 BK PAC UM E Configuring an Inline station using the I O configurator Robot Control icf Factory Line 10 Browser B x File
230. points 1 2 3 4 5 Each connector be labeled individually with Zack marker strips 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 oras 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 In each end position there is a small latch which ensures that the labeling field remains in place 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 On the electronics base each slot can be labeled individually using Zack markers These markers are covered when a connector is plugged in 615605 PHCENIX FL IL 24 BK PAC UM E 2 slot housing Using the markers on the connector and on the electronics base you can clearly assign both connector and slot 1 8 Dimensions of Low Level Signal Modules Today small I O stations are frequently installed in 80 mm 3 150 in standard control 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
231. r Configuration of the FL IL 24 BK PAC Configuration Reset Fault Mode Configuration Last State Fault Mode Internal memory Actual output Internal memory Actual output After connection abort cable interrupt or communication error Last value in internal memory The digital outputs are set to 0 Last value internal memory Values in internal memory First write access in the output table after the connection has been re established Last values in internal memory plus newly written values Internal memory Last values in the output table plus newly written values Internal memory Operating Last values in internal memory plus all newly written values Internal memory Last values in internal memory plus all newly written values Internal memory 615605 PHCENIX CONTACT 3 45 FL IL 24 BK 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 Writing the value 0x00A1 to the internal memory of the DO 16 after the connection has been re established results in the following actual output value Module AO DO 16 DO2 Value 0x0123 0x00A1 0x0002 The state is Last values in internal memory plus newly written values Writing the following values to the internal memory e g 0x0010 on the AO
232. r Software locRet DDI DTI WriteData dtiHnd amp dtiAcc locMsgB1k i 0 if locRet ERR printf nError when resetting buffer Error code 0x 04X locRet Sleep 100 Loop for reading and writing 255 data items do Write data dtiAcc length MAX MSG LENGTH dtiAcc address 0 dtiAcc dataCons DTI_DATA WORD Specify data consistency dtiAcc data locMsgBlk DO8 is the first DO module IB PD SetDataN locMsgBlk 0 1oci locRet DDI DTI WriteData dtiHnd amp dtiAcc if locRet ERR printf NnError when writing data Error code 0x 04X locRet 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 when reading data Error code 0x 04X ReadData IB PD GetDataN locReadBlk 0x00 if ReadData loci printf rWritten 3d Read 3d Comparison OK ReadData locRet loci 615605 PHCEN IX CONTACT 3 85 FL IL 24 BK PAC UM E else printf rWritten 3d Read 3d Comparison FAILED loci ReadData loci while loci lt 256 Sleep 500 Close channels to FL IL 24 BK PAC again locRet DeleteConnection printf nEND n Sleep 3000 return 0 3 86 PHGNIX 615605 CONTACT Section 4 This section provides infor
233. r digital output modules ras cete Sa 1 67 615605 PHGNIX A 5 CONTACT FL IL 24 BK UME Section 2 Table 2 1 Sequence displayed after the device is switched on 2 3 Table 2 2 During startup operation esee 2 44 Table 2 3 Additional 2 44 Table 2 4 During firmware update 2 2 44 Table 2 5 Boot loader error messages 2 45 Table 2 6 Firmware error 41021 2 45 Table 2 7 Priority of the error 2 47 Table 2 8 Differences on the display in DDI mode and Modbus TCP mode misinis a 2 47 Section 3 Table 3 1 Possible combination of the modes and their effect 3 9 Table 3 2 System parameters for the Set Value service 750 3 13 Table 3 3 Overview of the functions in the DDI 3 15 Table 3 4 Monitoring 3 33 Table 3 5 Available fault response 3 33 Table 3 6 Available fault response 244 22 2 1 3 44 Table 3 7 Power up 4 3 44 Table 3 8 Connection monitoring table 3 45 Table 3 9 Driver software
234. r there is still a connection between the bus coupler server and the computer client and whether this computer responds to requests With this monitoring function it is also possible to detect the following error causes Cable broken not connected or short circuited Transceiver faulty Errors or defects in the Ethernet adapter of the bus coupler 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 of 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 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 coupler the echo port is used with UDP to keep the resources used to a minimum Detecting an Error Connection monit
235. rNetFailState service 3 34 PHGNIX 615605 CONTACT Driver Software 3 8 1 Process Data Monitoring Process Data Watchdog 3 8 1 1 Process Data Watchdog Function C A process data watchdog is integrated into the bus coupler to avoid uncontrolled setting resetting of the Inline station outputs in the event of an error If outputs of the stations are set ensure access of the controlling process to the station In the event of an error e g network line interrupted or function error in the controlling process the bus coupler can react appropriately via the process data watchdog 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 expected during timeout default 500 ms During error free operation the write process is performed during timeout and the watchdog is restarted triggered nz eee If there is no triggering during timeout an error occurred Two reactions follow The selected fault response mode is executed The NetFail signal is set The reason for setting the NetFail signal is listed in the reason code see page 3 34 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 e
236. re 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 Remedy Close the channel and open it again with modified access rights ERR_INVLD_CMD 008Chex Cause This error message is displayed if you are using an older driver library or an older DLL Remedy Use the latest driver ERR_INVLD_PARAM 008Dhex Cause This error message is displayed if invalid parameters are used in the command Remedy Check the validity of the parameters used 615605 PH NIX 3 71 CONTACT FL IL 24 BK PAC UM E 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 that does not exist 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 device name ERR_NO_MORE_HNDL 0092 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 w
237. rent status Status The status indicators yellow display the status of the relevant inputs outputs or the connected device 1 42 1 LEDs on the Ethernet Bus Coupler 30 SHAT 61560015 Figure 1 26 LEDs on the Ethernet bus coupler 1 42 FL IL 24 BK PAC Diagnostics The following states can be read on the bus coupler Table 1 14 Diagnostic LEDs of the bus coupler Des Color Status Meaning Module Electronics 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 Green ON 24 V main circuit supply present OFF 24 V main circuit supply not present US Green ON 24 segment supply present OFF 24 V segment supply not present Ethernet Port 100 Green ON Operation at 100 Mbps OFF Operation at 10 Mbps if LNK LED active FD Green ON Data transmission in full duplex mode OFF Data transmission in half duplex mode if LNK LED active COL Red ON Collision of data telegrams OFF Transmission of telegrams without a collision 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
238. ributes This parameter contains the value which was transmitted by 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 030955 on page 4 20 4 28 PHCENIX 615605 CONTACT Firmware Services 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 BE 0 030Chex Command code of the service request Parameter Count Number of subsequent words 0001 1 parameter word Frame Reference 0001 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 0001 1 parameter word with a negative message 0002 2 parameter words 615605 PHCENIX Ted CONTACT FL IL 24 BK PAC UM E Task Syn
239. rmula 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 131 F 1 Nominal current carrying capacity of the communications power and analog supply 50 according to the diagram lL Logic 1A 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 loaded 1 1 X ILLogic 0 W Ppeni 1 1 lij ogic lLLogic 1 275 W 1 1 ILLogic 1 159 A Safety Equipment Surge voltage Input protective diodes can be destroyed by segment supply main supply bus coupler supply permanent overload Pulse loads up to 1500 V are short circuited by the input protective diode Polarity reversal Parallel diodes against polarity reversal in the event of segment supply main supply an error the high current through the diodes causes the preconnected fuse to blow Polarity reversal Serial diode in the lead path of the power supply unit bus coupler supply 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 7 8 PHCENIX 615605 C
240. rovides information about 5 2 supported PCP commands RM 5 3 Transmission of Parameter 5 3 5 1 1 PCP Configuration in the Web Based Management 5 4 5 1 2 Configuration of the PDU Size 5 4 Supported 000 0 0 eene 5 5 615605 PHCENIX zi CONTACT FL IL 24 BK PAC UM E 5 2 PH NIX 615605 CONTACT Communication 5 PCP Communication Peripherals Communication Protocol PCP 5 1 Transmission of Parameter Data Besides exchanging process data there are intelligent devices like frequency inverters or controllers that exchange process data with each other and also large data amounts with the control system Such data can for example be needed for the startup phase of a machine This kind of parameter data seldom changes and must therefore only be transmitted when required The INTERBUS protocol can transmit process data and complex data records parameter data at the same time For this the complex parameter data is divided into small units transmitted and put together again In the INTERBUS system the Peripherals Communication Protocol PCP divides the parameter data into single segments After the transmission it recombines the data PCP refers to the protocol software which makes connection establishment and connection abort possible etc nz
241. rst write access to the 0 plus the new Internal memory 0 plus the new Internal memory internal memory after values values power up Operating 0 plus the sum of Internal memory plus the sum of Internal memory Example A station consists of a total of three I O modules one 16 bit analog output module AO one 16 bit digital output module DO16 and one 2 bit digital output module DO 2 After power up all outputs are set to 0 Module AO DO 16 DO2 Value 0x0000 0x0000 0x0000 Writing Ox0200 to the DO 16 module as the first value results in the following output values 3 44 PHCENIX CONTACT 615605 Driver Software Table 3 8 Module AO DO 16 DO 2 Value 0x0000 0x0200 0x0000 The state is O plus the new values Writing the following values to the relevant modules e g 0x0010 on the AO 0x0001 on the DO 2 and OxACDC on the DO 16 results in the following output values Module AO DO 16 DO2 Value 0x0010 OxACDC 0x0001 The state is O plus the sum of all new values 3 8 4 2 Connection Monitoring Table This table shows the output values after connection monitoring or the process data watchdog detected an error e g connection interrupted or communication error while the power supply was kept Connection monitoring table Connection monitoring table after connection abort cable interrupt or communication erro
242. see Figure 1 25 on page 1 41 Us and Uy can be protected separately yet still have a common ground potential Please observe the maximum total current of 8 A 1 40 PHCEN IX 615605 CONTACT FL IL 24 BK PAC I O supplies electrically isolated from one another FL IL 24 BK PAC IB IL 24 PWR IN DO DI 1 E MAT 24 BK PAC ESET Ord No 28623 100 LE a pe 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 1 2 FD o E EE COL 3 e xuT ih CLIE RCV mj mA B LINK Cae 5 58 1 10 100 T 61560014 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 outputs 3 1 0 inputs ass 1 41 CONTACT FL IL 24 BK PAC UM E 1 12 Diagnostic and status indicators 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 The module is functioning correctly if all of the green LEDs are on Once an error has been removed the indicators immediately display the cur
243. ss 2 9 4 Defining the Trap Manager Traps must be sent to a trap manager to be evaluated Two appropriate network devices can be defined as trap managers Open the SNMP Configuration dialog box in the Device Configuration menu and enter the IP addresses of the trap managers in the First Second Trap Manager IP Address fields Enter the password for write access and save with Apply Eta FL IL 24 BK PAC last update 12 48 29 CONTACT SNMP Configuration System Information Name of Device FL IL24 BK FL IL 24 BK PAC General Instructions Description Ethernet bus terminal Device Information Physical Location 0 2 4 Device Configuration IP Configuration Contact Manager SNMP Configuration Writing new configuration can take several seconds Software Update Enter Password Apply Change Password Trap Configuration Watchdog First Trap Manager IP 19218817243 Inline Station Address 13215517 57 Home Boone Manager IP 19216823378 Sending traps Enable Disable Please enter IP addresses in dotted decimal notation e g 172 16 16 230 Enter Password Apply Figure 2 6 Defining the trap manager 2 20 PHCEN IX 615605 CONTACT Startup Operation 2 10 Factory Line I O Configurator The Factory Line I O configurator is a software package for the easy configuration startup and diagnostics of Factory Line Ethernet bus c
244. ssage format Byte No Meaning BYTE 0 1 Transaction identifier unique ID generated by the client BYTE 2 3 Protocol identifier 0 4 Length field upper byte 0 all messages lt 256 BYTE 5 Length field Iower byte number of subsequent bytes BYTE 6 Unit identifier BYTE 7 Modbus function code BYTE 8 Data as needed 6 1 5 Modbus Byte Order Modbus uses the big endian representation for addresses and data items This means that if a numerical quantity larger than a single byte is transmitted as single or double word the most significant byte is sent first Example The quantity 0x1234 would be transmitted in the order 0x12 0x34 The quantity 0x12345678 would be transmitted in the order 0x12 0x34 0x56 0x78 6 4 PHCENIX 615605 CONTACT Modbus TCP Protocol 6 1 6 Modbus Bit Order If a series of bits is read as a register e g 11 to 116 the highest numbered bit 26116 in this example is the least significant and the lowest numbered bit 11 in this example is the most significant 6 2 Modbus Function Codes The following function codes are supported Table 6 2 Supported function codes Code No Function Code fci 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 regi
245. ssword Watchdog Hardware Inline Station Services Process Data Monitoring Process Data Watchdog Remote Diagnostics Bus Configuration Event Table 6155004 PCP Configuration 615605 PHCENIX SH CONTACT FL IL 24 BK PAC UM E 2 7 4 Password Protection The bus coupler 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 coupler 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 IL STATION IL BUS TERMINAL TERMINAL TYPE NAME IP ADDRESS MODULE NUMBER 2 7 5 Process Data Access Via XML The integrated FL IL 24 BK PAC web server can be used to access the process data of the connected Inline terminals using a web page in XML format Use a standard web browser to access the web pages Enter the address in the following format in the address line of the browser to call the XML pages containing the process data http lt IP Adresse gt processdata xml 2 7 5 1 Structure of the XML Files The XML file comprises different data areas Frame 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 This
246. sters fc23 Read write registers 6 3 Modbus Table The Modbus protocol s reference table is different from the internal structure of the FL IL 24 BK PAC tables Modbus refers to a register input register discrete input and coil table the FL IL 24 BK PAC refers to a discrete input l discrete output Q analog inputs Al analog outputs AQ and special register table The following table shows how each Modbus table is mapped to the FL IL 24 BK PAC tables Note that all specifications in this table refer to the physical memory inside theFL IL 24 BK PAC In effect the FL IL 24 BK PAC memory has been given Modbus names If for example we issue a read input discretes command to read the inputs in the read inputs discretes table we are actually reading from the internal FL IL 24 BK PAC table l which is mapped to the Modbus input discrete table 615605 PHCENIX 6 5 CONTACT FL IL 24 BK PAC UM E 16 bit words 16 bit words Table 6 3 Modbus reference tables Modbus Modbus Input Modbus Input Modbus Coil Internal FL IL 24 BK PAC Register Table Register Table Discrete Table Table Tables 0 191 0 191 0 3071 911 3072 p 16 bit words 16 bit words bits bits LH 192 383 192 383 192 2 16 bit words 16 bit words 16 bit words 384 575 384 575 0 3071 Q1 3072 8 16 bit words 16 bit words bits bits 57
247. still active and thus prevents data from being written NetFail occurred n addition a DDI device could be closed that has exclusive write access In this case it is not possible to write data via Modbus TCP 16 DOUBLE PCP Another client already has a PCP connection to this bus coupler CONNECTION 6 18 PHGNIX 615605 CONTACT Modbus TCP Protocol 6 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 6 31 Write multiple coils Byte No Meaning BYTE 0 Function code 0x0F BYTE 1 2 Coil table offset BYTE 3 4 Bit count BYTE 5 Byte count BYTE 6 5 Bit values the least significant bit is the first coil The response to the write multiple coils command has the following format Table 6 32 Response to write multiple coils Byte No Meaning BYTEO Function code OxOF BYTE 1 2 Coil table offset same as command BYTE3 4 Bit count same as command If the command uses an invalid offset the following exception response is generated Table 6 33 Exception response to write multiple coils Byte No Meaning BYTE 0 Function code Ox8F BYTE 1 Exception response 2 6 5 11 1 Example for the Write Multiple Coils Command Coil table offset 0 and bit count 2 with the value 3 sets the coils Q1 and
248. t 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 network connection interrupted or not present Reset button The reset button is on the front plate When the reset button is pressed the bus coupler is completely initialized and booted Inline system outputs are reset and inputs are not read 1 6 PHCEN IX 615605 CONTACT FL IL 24 BK PAC 1 3 Connecting the Supply Voltage The module is operated using a 24 V DC SELV Typical Connection of the Supply Voltage CONTACT FL IL 24 BK PAC RESET Ord No 2862314 Internal jumper in the module 100 e FD COL XMT RCV Q LINK 10 100 61551011 Figure 1 3 Typical connection of the supply voltage 615605 PHCENIX 1 7 CONTACT FL IL 24 BK PAC UM E 1 4 Connector Assignment Table 1 2 Connector assignment Terminal Assignment Power Connector Wire Color Remark Point Connector 1 1 24 VDC 24 segment supply The supplied voltage is directly led to the potential jumper Us 1 2 24V 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 an
249. tax Word 1 Word 2 Word 3 Bit Key Result Result of the service processing 0000hex indicates a positive message The controller board has 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 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 display PP for plug amp play mode for expert mode The new configuration frame and the known 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 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 known configuration Length Code According to the known configuration ID Code According to the known conf
250. ted 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 15 VUE DES ERE 0 8307hex Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 0001 Always 1 parameter word with a negative message 0002 Always 2 parameter words Result Result of the service processing 0000hex indicates a positive message The controller board has 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 615605 PHCENIX mE CONTACT FL IL 24 BK PAC UM E 4 3 6 Terminate Load Configuration Service Task This service terminates the loading of the configuration data in segments The service also checks the loaded configuration data for permissibility and consistency If error is detected the controller board stores the data in the configuration directory under the Frame Reference given in the Initiate Load Configuration 030646x service If an error is detected the service is acknowledged with a negative co
251. ted 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 USIGNS8 data Pointer to the data read and write T DDI DTI ACCESS 3 22 PHCENIX 615605 CONTACT Driver Software Example UNIX Windows NT 2000 IBDDIHND ddihnd IBDDIRET ddiRet T 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 615605 PHGNIX 3 23 CONTACT FL IL 24 BK PAC UM E DDI DTI WriteData Task The DDI DTI WriteData function is used to write process data to the bus coupler The function is assigned the node handle and a pointer to a DDI ACCESS data structure The T DDI DTI ACCESS structure contains all the parameters that are needed to access the process data area of the bus coupler 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 coupler in the network to which the request is to be sent
252. the diodes causes the preconnected fuse to blow This 24 V area must be fused externally The power supply unit must be able to supply 4 times 400 the nominal current of the external fuse to ensure that the fuse blows safely in the event 24 V Bus Coupler Supply Connection method Spring cage terminals Recommended cable lengths 30 m 98 43 ft maximum do not route cable through outdoor areas Voltage continuation Via potential routing UANA Safety equipment Surge voltage Polarity reversal Input protective diodes can be destroyed by permanent overload Pulse loads up to 1500 V are short circuited by the input protective 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 Observe the current consumption of the modules A Observe the logic current consumption of each device when configuring an Inline station This information is given in every module specific data sheet The current consumption can differ depending on the individual module The permissible number of devices that can be connected therefore depends on the specific station structure Nominal value 24V DC 7 4 PHCEN IX 615605 CONTACT Technical Data 24 V Bus Coupler Supply
253. the input discrete values 261 32 Register table offset 2575 and word count 2 returns the value of the coils Q3057 3072 and the analog output AQ1 Register table offset 1024 and word count 64 returns a fault table Any combination of the register table offset and a word count gt 767 and 1024 produces an exception response The attempt to read the fault table with a register table offset gt 1024 and a word count not equal to 64 also generates an exception response 6 20 PHCEN IX 615605 CONTACT Modbus TCP Protocol The special register 1280 2004 can only be read if the word count equals one Register table offset 384 and word count 2 writes the register values into coils 96Q1 32 Register table offset 575 and word count 2 writes the register values into coils Q3057 3072 and the analog output AQ1 Any combination of register table offset and word count between gt 384 and 767 generates an exception response except writing one word into registers 2000 and 2002 615605 PHCENIX 6 21 CONTACT FL IL 24 BK PAC UM E 6 6 Reserved Registers for Command and Status Words 6 6 1 Command Word The last word of the analog output table is automatically reserved by the bus coupler as network interface command word and starts at Modbus address 40767 This command word allows the Ethernet host controller e g PLC to send commands with basic functions to the module These commands enable startup without con
254. ther there should be a large or a small space between the connection point and the shield connection Shorten the braided shield to 15 mm 0 591 in 1 Fold the braided shield back over the outer sheath 2 Remove the protective foil Strip 8 mm 0 315 in off the wires 2 Push a screwdriver into the slot of the appropriate terminal point Figure 1 35 on page 1 59 detail 1 so that you can insert the wire into the spring opening Phoenix Contact recommends using a SFZ 1 0 6 x 3 5 screwdriver Order No 12 04 51 7 see Phoenix Contact CLIPLINE catalog Insert the wire Figure 1 35 on page 1 59 detail 2 Remove the screwdriver from the opening This clamps the wire Open the shield connector 3 Check the direction of the shield connection clamp in the shield connector see Figure 1 37 Place the cable with the folded braided shield in the shield connector 4 Close the shield connector 5 Fasten the screws on the shield connector using a screwdriver 6 1 62 PHCEN IX 615605 CONTACT FL IL 24 BK PAC 5520A068 Figure 1 37 Shield connection clamp alignment Shield connection The shield connection clamp a in Figure 1 37 detail 2 in the shield connector can clamp 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 detail 2 For thinner cables the dip in the clamp is turned towards the cab
255. tive message 000244 2 parameter words Result Result of the service processing 0000hex indicates a positive message The controller board has 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 14 PHCENIX 615605 CONTACT Firmware Services Task IS Prerequisite 4 3 5 Load Configuration Service 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 Ensure that the controller board has been prepared for transmission with the following services Control Parameterization 030Ehex nitiate Load Configuration 0306554 Syntax Load Configuration Request 0307 Word 1 Word 2 Word Word 4 Word 5 Word 6 1 device nth device Bit pe 0 Key Code 030744 Command code of the service request Parameter Count Number of subsequent parameter words XXXXhex The value depends on the Entry Count parameter and Used Atrributes parameter 615605 PHCENIX GER CONTACT
256. tput buffer n USIGNE8 Pointer to the output buffer m USIGN16 Word number o USIGNB 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 USIGNB Pointer to the output buffer m USIGN16 Word number o USIGN8 Process data 8 bit IB PD SetBytePtrHiByte n m This macro returns the address of a word starting with the high order byte bit 8 to 15 n USIGNB Pointer to the output buffer m USIGN16 Word number USIGNB8 Address of the high order byte of a word in the output buffer IB_PD_SetBytePtrLoByte n m Task This macro returns the address of a word starting with the low order byte bit 0 to 7 Parameters n USIGNB Pointer to the output buffer m USIGN16 Word number Return value USIGNB8 Address of the low order byte of a word in the output buffer 615605 PHGNIX 3 67 CONTACT FL IL 24 BK PAC UM E 3 13 Diagnostic Options for Driver Software 3 13 1 Introduction The 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 offset ERR BASE depending on the operating system is added to each code listed here This offset is already taken into account when using the error message definitions
257. ty Free from substances which would hinder coating with paint or varnish according to VW specification Resistance to solvents Standard solvents Weight 270 g typical 24 V Main Supply 24 V Segment Supply Connection method Spring cage terminals Recommended cable lengths 30 m 98 43 ft maximum do not route cable through outdoor areas Voltage continuation Through potential routing Special demands on the voltage supply The supplies Uy Ug and the bus coupler supply Ugx 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 615605 PHCENIX Fa CONTACT FL IL 24 BK PAC UM E 24 V Main Supply 24 V Segment Supply Tolerance 15 20 according to EN 61131 2 Ripple 5 Permissible range 19 2 V to 30 V Current carrying capacity maximum total current of Us and Uy Safety equipment Surge voltage Polarity reversal of an error Input protective diodes can be destroyed by permanent overload Pulse loads up to 1500 V are short circuited by the input protective diode Parallel diodes against polarity reversal in the event of an error the high current through
258. ual device names are separated by spaces The address of the bus coupler can be entered in dotted notation 192 168 5 76 or as server name etha2 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 coupler Entry creation is done by the driver You can find the driver in the download area on the Internet at www phoenixcontact com or the CD FL IL 24 BK CD Order No 28 32 06 9 The following registry entry is created HKEY LOCAL MACHINENSOFTWARENPhoenix Contact IBSETH Parameters 1 ConnectTimeout 08 00 00 00 DeviceNames IBETHO1N1 01 0 01 01 1 D 01 0 D 01 1 M 00 01 1 05 InUse YES ReceiveTimeout 08 00 00 00 IPAddress 192 168 36 205 The DDI DevOpenNode function opens a data channel to the bus coupler specified by the device name or to a node 3 18 PHCENIX 615605 CONTACT Driver Software Syntax Parameters Return value Constants for the perm parameter 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 access to this data channel In the event of an
259. uit 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 segment circuit If the limit value of the common GND potential jumper for Uy and Us is reached total current of Us and Uy a new power terminal must be used FL IL 24 BK PAC PWR IN SEG F H U Uana GNDL I H H Us Un 0 61560002 Figure 1 18 Main circuit FL IL 24 BK PAC Ethernet bus coupler PWR IN Power terminal SEG F Segment terminal with fuse as an example of a segment terminal In the simplest case the main voltage Uy can be supplied at the bus coupler In this case it is 24 V DC 1 32 PHCENIX 615605 CONTACT FL IL 24 BK PAC Function Voltage Current carrying capacity The main voltage Uy can also be supplied via a power terminal A power terminal must be used if 1 Different voltage areas e g 120 V AC are to be created 2 Electrical isolation is to be created 3 The maximum current carrying capacity of a potential jumper Uy Us or GND total current of Us and Uy is reached 1 40 5 Segment Circuit The segment circuit or auxiliary circuit with the segment voltage Ug 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 n
260. upply of the Ethernet Bus Coupler The supply voltage Ugk and the segment voltage Us must be connected to the Ethernet bus coupler From the supply voltage Ugk the voltages for the logic circuit UL 7 5 V and the supply of the modules for analog signals Uana 24 V internally generated The segment voltage is used to supply the sensors and actuators CONTACT FL IL 24 BK PAC RESET Ord No 2862314 Internal jumper in the module 100 FD COL XMT RCV LINK 10 100 61551011 Figure 1 16 Typical connection of the supply voltage 1 10 2 Logic Circuit The logic circuit with communications power 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 615605 CONTACT FL IL 24 BK PAC Provision of UL Current carrying capacity Function Voltage Provision of UANA Current carrying The communications power U is generated from the supply voltage Up 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 is 2
261. uration 615605 PHCENIX 3 7 CONTACT FL IL 24 BK PAC UM E IS P amp P mode active P amp P mode inactive 3 5 Startup Behavior of the Bus Coupler Startup behavior of the bus coupler is determined via two system parameters plug amp play mode and expert mode By default upon delivery P amp P mode is activated and expert mode deactivated 3 5 1 Plug amp Play Mode The FL IL 24 BK PAC supports 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 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 recognized and checked for their function If this physical configuration is ready to operate it is stored retentively on the bus coupler If the connected configuration could be stored as the reference configuration PP is displayed on the bus coupler In order not to overwrite the reference configuration again on the next bus coupler start P amp P mode must be deactivated again Deactivation of P amp P mode also acknowledges the reference configuration and enables process data exchange With inactive P amp P mode the reference configuration is compared with the physical configuration If both are the same the bus coupler can be set to the RUN state If the reference configuration does not match the physical configuration 8
262. uration frame Frame PCP Device Count Number of configured PCP devices in the selected configuration frame Active PCP Device Count Number of active PCP devices in the selected configuration frame Frame PCP Word Count Number of configured PCP words in the selected configuration frame Active PCP Word Count Number of active PCP words in the selected configuration frame Used Attributes Read attributes This parameter contains the value which was transmitted by the service request Start Entry No Position of the first entry or 0000 if only the header information was read Entry Count Number of entries that are transmitted by this service confirmation The More Follows parameter indicates if there are other entries Configuration Entry 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 25 In the following the structure of a configuration entry is shown where all attributes are enabled 4 24 PHCENIX 615605 CONTACT Firmware Services Syntax Configuration Entry Attribute Word x Device number Word x 1 Device code Bit p e BE o A 0 Key Attribute Device Number Bus Segment No Number of the bus segment where the INTERBUS device is located Value 00 Position Physical location in the bus segment Value range OOhex
263. ure 1 15 No Function Meaning 1 FE FE Functional earth ground 2 SGND SGND Ground of segment supply and main supply 3 24 Supply for main circuit with overload protection if necessary 4 24V Us Supply for segment circuit with overload protection if necessary This jumper does not exist in the120 230 V AC power levels 5 LGND UL Ground of communications power and I O supply for analog modules 24 UANA supply for analog modules 7 7 5V Ui Supply for module electronics 9 FE spring FE contact to DIN rail Table 1 13 Data jumper see Figure 1 15 No Function Meaning 8a Local bus signal Data IN 8b DO1 Local bus signal Data OUT 8c DCLK Clock signal local bus 1 28 PHCENIX 615605 CONTACT FL IL 24 BK PAC 1 10 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 LINZ eee Load capacity of the Observe the maximum current carrying capacity of the jumper contacts on the side jumper contacts for each circuit The load capacities for all potential jumpers are given in the following sections ld 615605 PHCENIX 1 29 CONTACT FL IL 24 BK PAC UM E 1 10 1 S
264. ure 1 6 The shield connector is jumpered through the shield connection All other connectors are jumpered through terminal point connection imm 149 CONTACT FL IL 24 BK PAC UM E Connector keying You can prevent mismatching of connectors by keying 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 detail A e Use a diagonal cutter to cut off the keying tab from the connector Figure 1 7 detail B Now only the base and connector with the same keying will fit together Figure 1 7 detail C 1 20 PHCENIX 615605 CONTACT FL IL 24 BK PAC 1 7 Function Identification and Labeling Function identification The modules are color coded to enable visual identification of the functions 1 in Figure 1 8 5520A075 Figure 1 8 Function identification The following colors indicate the functions Table 1 11 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 18 identif
265. ve message The controller board has 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 615605 PHCENIX me CONTACT 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 0956 Word 1 Word 2 Word 3 Bit 0 Key Code 095644 Command code of the service request Parameter Count Number of subsequent words 000145 1 parameter word Reset Type 0001 hex Cold restart A cold restart is always carried out 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 Uc 0 Key Code 8956 44 Message code of the service confirmation Parameter Count Number of subsequent words with a positive message 000155 1 parameter word with a negative message 00024 2 parameter words Result Result of the service processing 4 36 PHCEN IX 615605 CONTACT Firmware Services 0000hex indicates a positive message The controller b
266. wly or rarely change the same process data is often 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 the IN process 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 gt 22 ms If itis 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 52 PHCEN IX 615605 CONTACT Driver Software Task Function Syntax Parameters Return value IS ETH ActivatePDInMonitoring The ETH ActivatePDInMonitoring function activates the mode for monitoring the IN process data for potential changes This mode can only be activated once on each controller
267. xample Interruption creation of the potential jumpers using the power terminal 1 38 Figure 1 24 Electrical isolation between Ethernet bus coupler and analog module esee 1 39 615605 1 PHCENIX CONTACT FL IL 24 BK PAC UM E Figure 1 25 Structure of I O supplies that are electrically isolated from one another 1 41 Figure 1 26 LEDs on the Ethernet bus coupler 1 42 Figure 1 27 Possible indicators on supply terminals segment terminal with and without fuse and power terminal 1 44 Figure 1 28 module indicators 22222 1 45 Figure 1 29 Snapping on a 1 49 Figure 1 30 Removing a module rtt 1 51 Figure 1 31 Replacing a fuse 1 53 Figure 1 32 Additional grounding of the FL IL 24 BK PAC 1 54 Figure 1 33 Connection of analog sensors signal cables gt 10 32 81 ft 1 57 Figure 1 34 Connection of actuators signal cables gt 10 m 32 81 ft 1 58 Figure 1 35 Connecting unshielded cables 1 59 Figure 1 36 Connecting the shield to the shield connector 1 61 Figure 1 37 Shield connection clamp alignment 1 63 Figure 1 38
268. xamples for Read Multiple Registers section 6 5 6 Write Coils With this command 1 bit is written into the Modbus coil table The write coil command has the following format Table 6 21 Write coils Byte No Meaning BYTE 0 Function code 5 BYTE 1 2 Coil table offset BYTE 3 OxFF to turn coil ON O to turn coil OFF Byte 4 0 The response to the write coils command has the following format Table 6 22 Response to write coils Byte No Meaning BYTE 0 Function code 5 BYTE 1 2 Coil table offset same as command BYTE 3 OxFF to turn coil ON 0 to turn coil OFF Byte 4 0 If the command accesses an invalid offset the exception response has the following format Table 6 23 Exception response to write coils Byte No Meaning BYTE 0 Function code 0x85 BYTE 1 Exception code 2 615605 PHCENIX 6 15 CONTACT FL IL 24 BK PAC UM E 6 5 6 1 Examples for Write Coils Coil table offset 0 and the value 0xFF turns coil Q1 ON Coil table offset 0 and the value 0 turns coil 1 OFF Each coil table offset gt 3072 produces an exception response 6 5 7 Write Single Register This command writes a 16 bit word to the Modbus register table Only the part of the Modbus register table mapped to the Q and AQ I O tables as well as the first word of the fault table may be written using this function The write single regist
269. xecuted The NetFail signal is acknowledged using the web based management or the ETH ClrNetFailState command and the fault response mode is reset uere que qc il 615605 PHCENIX 3 35 CONTACT FL IL 24 BK PAC UM E IS 3 8 1 2 Configuring the Process Data Watchdog and the Fault Response Modes Process data watchdog timeout can be configured from 200 ms to 65000 ms Timeout can be set to the object ID 0x2293 using the web based management by writing to the Modbus register 2000 or using the Set Value 0x0750 service Deactivating the Process Data Watchdog The process data watchdog can only be deactivated if the bus coupler is in INIT state For deactivation the timeout time is set to zero The required fault response mode can also be set to the object ID 0x2277 using the web based management by writing to the Modbus register 2002 or using the Set Value 0x0750 service Status Diagram of the Process Data Watchdog INIT status Write OK ETH ClearNetFail Watchdog timeout 0 es Q Request M No INTERBUS running es Yes Write OK No Watchdog timeout expires Set Net Fail Fault Response 61560029 Figure 3 11 Status diagram of the process data watchdog 3 36 615605 PHCENIX CONTACT Driver Software 3 8 2 Connection Monitoring Host Checking Application Connection monitoring be used to determine whethe

User Manual FL IL 24 BK-PAC UM E - Configurators

Contents

Download Pdf Manuals

Related Search

Related Contents