Page 1 User Manual Hardware and Firmware User Manual for the FL IL 24 BK / FL IL 24 BK-PAC Ethernet/Inline Bus Coupler Designation: FL IL 24 BK-PAC UM E Order No.: 90 14 20 5...
Page 3 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: Order No.: 90 14 20 5 This user manual is valid for:...
Page 5 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.
Page 6 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.
Page 7: About This Manual
About This Manual Purpose of this manual This manual illustrates how to configure an Ethernet/Inline station to meet applica- tion requirements. Who should use this Use this manual if you are responsible for configuring and installing an Ethernet/In- manual line station. This manual is written based on the assumption that the reader pos- sesses basic knowledge about Inline systems.
Page 8 – Common technical data Validity of Phoenix Contact reserves the right to make any technical extensions and changes documentation 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...
Page 9: Table Of Contents
1 FL IL 24 BK(-PAC)......................1-3 General Functions .................. 1-3 1.1.1 Product Description ..............1-3 Structure of the FL IL 24 BK(-PAC) Bus Coupler ........1-5 1.2.1 Local Status and Diagnostic Indicators ........1-6 Connecting the Supply Voltage .............. 1-7 Connector Assignment ................
Page 10 Table of Contents 1.14 Grounding an Inline Station ..............1-54 1.14.1 Shielding an Inline Station ............ 1-56 1.14.2 Shielding Analog Sensors and Actuators ......1-56 1.15 Connecting Cables ................1-59 1.15.1 Connecting Unshielded Cables ..........1-59 1.15.2 Connecting Shielded Cables Using the Shield Connector ... 1-61 1.16 Connecting the Voltage Supply ............
Page 11 Without Factory Manager ..............2-19 2.9.1 Trap Generation ..............2-19 2.9.2 Representation of Traps in the Factory Manager ....2-19 2.9.3 FL IL 24 BK(-PAC) Traps ............2-20 2.9.4 Defining the Trap Manager ........... 2-20 2.10 Factory Line I/O Configurator ............... 2-21 2.10.1 Factory Line I/O Browser ............
Page 12 Table of Contents Monitoring Functions ................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_SetNetFail ..............
Page 13 FL IL 24 BK-PAC UM E 4.3.2 "Set_Value" Service ..............4-9 4.3.3 "Read_Value" Service ............4-11 4.3.4 "Initiate_Load_Configuration" Service ........4-13 4.3.5 "Load_Configuration" Service ..........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...
Page 14 Table of Contents Modbus Table..................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 ................6-9 Supported Function Codes..............6-9 6.5.1 Read Multiple Registers ............
Page 15 FL IL 24 BK(-PAC)......................1-3 General Functions .................. 1-3 1.1.1 Product Description ..............1-3 Structure of the FL IL 24 BK(-PAC) Bus Coupler ........1-5 1.2.1 Local Status and Diagnostic Indicators........1-6 Connecting the Supply Voltage .............. 1-7 Connector Assignment ................1-8 Supported Inline Modules...............
Page 16 FL IL 24 BK-PAC UM E 1.13 Mounting/Removing Modules and Connecting Cables......1-47 1.13.1 Installation Instructions ............1-47 1.13.2 Mounting and Removing Inline Modules........ 1-47 1.13.3 Mounting ................1-48 1.13.4 Removing................1-50 1.13.5 Replacing a Fuse ..............1-52 1.14 Grounding an Inline Station ..............1-54 1.14.1...
Page 17: Fl Il 24 Bk(-Pac)
FL IL 24 BK(-PAC) FL IL 24 BK(-PAC) General Functions 1.1.1 Product Description Ethernet/Inline bus coupler Features – Ethernet coupler for the Inline I/O system – Ethernet TCP/IP - 10/100 Base-T(X) - Management via SNMP - Integrated web server –...
Page 18 FL IL 24 BK-PAC UM E Front view of the FL IL 24 BK(-PAC) Figure 1-1 Front view of the FL IL 24 BK(-PAC) 615605...
Page 19: Structure Of The Fl Il 24 Bk(-Pac) Bus Coupler
FL IL 24 BK(-PAC) Structure of the FL IL 24 BK(-PAC) Bus Coupler Figure 1-2 Structure of the FL IL 24 BK(-PAC) bus coupler The bus coupler has the following components: End plate to protect the last Inline module Inline diagnostic indicators...
Page 20: Local Status And Diagnostic Indicators
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 Green 24 V supply, 7 V communications power/interface supply present 24 V supply, 7 V communications power/interface supply not present...
Page 21: Connecting The Supply Voltage
FL IL 24 BK(-PAC) Connecting the Supply Voltage The module is operated using a +24 V DC SELV. Typical Connection of the Supply Voltage Figure 1-3 Typical connection of the supply voltage 615605...
Page 22: Connector Assignment
FL IL 24 BK-PAC UM E Connector Assignment Table 1-2 Connector assignment Terminal Assignment/Power Connector Wire Color/Remark Point/ Connector 24 V DC 24 V segment supply The supplied voltage is directly led to the potential jumper. 24 V DC 24 V supply The communications power for the bus coupler and the connected local bus devices is generated from this power.
Page 23: Supported Inline Modules
FL IL 24 BK(-PAC) 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...
Page 24 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 61 47 0 IB IL 24 DO 2-2A 2 outputs, 2 A, 4-wire termination, 24 V DC...
Page 25 FL IL 24 BK(-PAC) Table 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, 3 A 28 36 42 1 IB IL 24/230 DOR 4/W-...
Page 26 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 30 8 IB IL TEMP 2 RTD-PAC 2 inputs, 4-wire termination, 16 bits, resistance sensors...
Page 27 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 28 36 32 4 mA, 3-wire termination, 24 V DC IB IL INC-PAC...
Page 28 FL IL 24 BK-PAC UM E Table 1-6 Motor terminal blocks Designation Properties Order No. IB IL EC AR 48/10A-PAC Servo amplifier for DC motor without brushgears (EC motor) 28 19 58 7 IB IL PWM/2 Terminal for pulse width modulation and frequency modulation or...
Page 29 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 61 40 9 IB IL PD GND Terminal for GND potential distribution 28 63 06 7...
Page 30: Basic Structure Of Low-Level Signal Modules
"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) The components required for labeling are listed in the Phoenix Contact "CLIPLINE" catalog. 1-16 615605...
Page 31: Electronics Base
FL IL 24 BK(-PAC) 1.6.1 Electronics Base The electronics base holds the entire electronics for the Inline module and the potential and data routing. Design widths The electronics bases for low-level signal modules are available in a width of 8 terminal points (8-slot terminal) or 2 terminal points (2-slot terminal).
Page 32 FL IL 24 BK-PAC UM E 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).
Page 33 FL IL 24 BK(-PAC) Internal structure of the connectors Figure 1-6 Internal structure of the connectors Green connector for I/O connection Black connector for supply terminals Shield connector for analog terminals Double signal connector for I/O connection Jumpered terminal points already integrated in the connectors are shown in Figure 1-6.
Page 34 FL IL 24 BK-PAC UM E Connector keying You can prevent mismatching of connectors by keying the base and the connector. Figure 1-7 Connector keying • 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).
Page 35: Function Identification And Labeling
FL IL 24 BK(-PAC) Function Identification and Labeling Function identification The modules are color-coded to enable visual identification of the functions (1 in Figure 1-8). Figure 1-8 Function identification The following colors indicate the functions: Table 1-11 Module color-coding Color...
Page 36 FL IL 24 BK-PAC UM E Labeling/ Terminal point numbering is illustrated using the example of an 8-slot module. terminal numbering Figure 1-9 Terminal point numbering Slot/connector The slots (connectors) on a base are numbered consecutively (1 in Figure 1-9).
Page 37 FL IL 24 BK(-PAC) Figure 1-10 Labeling of modules Various options are available for labeling the slots and terminal points: Each connector can be labeled individually with Zack marker strips. 2 / 3 Another option is to use a large labeling field. This labeling field is available in two widths, either as a labeling field covering one connector (2) or as a labeling field covering four connectors (3).
Page 38: Dimensions Of Low-Level Signal Modules
FL IL 24 BK-PAC UM E Using the markers on the connector and on the electronics base, you can clearly assign both connector and slot. The components required for labeling are listed in the Phoenix Contact "CLIPLINE" catalog. Dimensions of Low-Level Signal Modules Today, small I/O stations are frequently installed in 80 mm (3.150 in.) standard...
Page 39 FL IL 24 BK(-PAC) 4-slot housing Figure 1-12 Dimensions of the electronics bases (4-slot housing) 8-slot housing Figure 1-13 Dimensions of the electronics bases (8-slot housing) 1-25 615605...
Page 40 FL IL 24 BK-PAC UM E Connector Figure 1-14 Connector dimensions Key: Standard connector Shield connector Extended double signal connector The depth of the connector does not influence the overall depth of the module. 1-26 615605...
Page 41: Electrical Potential And Data Routing
FL IL 24 BK(-PAC) 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.
Page 42 FL IL 24 BK-PAC UM E Table 1-12 Potential jumper (see Figure 1-15) Function Meaning Functional earth ground SGND SGND Ground of segment supply and main supply 24 V Supply for main circuit (with overload protection, if necessary) 24 V Supply for segment circuit (with overload protection, if necessary) This jumper does not exist in the120/230 V AC power levels.
Page 43: Circuits Within An Inline Station And Provision Of The Supply Voltages
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.
Page 44: Supply Of The Ethernet Bus Coupler
FL IL 24 BK-PAC UM E 1.10.1 Supply of the Ethernet Bus Coupler The supply voltage U and the segment voltage U must be connected to the Ethernet bus coupler. From the supply voltage U , the voltages for the logic circuit (7.5 V) and the supply of the modules for analog signals U...
Page 45: Analog Circuit Uana
FL IL 24 BK(-PAC) Provision of U The communications power U is generated from the supply voltage U of the bus coupler. The communications power is not electrically isolated from the 24 V input voltage for the bus coupler. Current carrying The maximum current carrying capacity of U is 2 A.
Page 46: Main Circuit U M
FL IL 24 BK-PAC UM E 1.10.4 Main Circuit U The main circuit with the main voltage U starts at the bus coupler or a power terminal and is led through all subsequent modules until it reaches the next power terminal.
Page 47: Segment Circuit
FL IL 24 BK(-PAC) The main voltage U can also be supplied via a power terminal. A power terminal must be used if: Different voltage areas (e.g., 120 V AC) are to be created. Electrical isolation is to be created.
Page 48 FL IL 24 BK-PAC UM E Generation of U There are various ways of providing the segment voltage U You can supply the segment voltage at the Ethernet/Inline bus coupler or a power terminal. You can tap the segment voltage from the main voltage at the Ethernet/Inline bus coupler or a power terminal using a jumper or a switch.
Page 49: Voltage Concept
FL IL 24 BK(-PAC) 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.
Page 50 FL IL 24 BK-PAC UM E Option 1 The Fieldbus coupler main voltage U and the I/O supply U are provided separately with the same ground potential from two voltage supplies: Figure 1-20 Potential areas in the bus coupler (two voltage supplies)
Page 51 FL IL 24 BK(-PAC) Option 2 Common supply of voltages U , and U from one voltage supply: Figure 1-21 Bus coupler potentials (one voltage supply) Potential areas: 1 Ethernet interface area 2 Functional earth ground / (shield) Ethernet interface area, bus coupler...
Page 52 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 U and U are provided from separate voltage supplies. An example of this principle is shown in Figure 1-23 on a section of an Inline station.
Page 53 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 U . The power supply unit with electrical isolation is a component of an analog module. The voltage U is looped through in each module and, in this way, is also available to the next module.
Page 54 FL IL 24 BK-PAC UM E I/O supply electrically Several electrically isolated segment or main circuits can be created by using power isolated from one terminals. A power terminal interrupts the U and GND potential jumpers and another 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.
Page 55 FL IL 24 BK(-PAC) I/O supplies electrically isolated from one another Figure 1-25 Structure of I/O supplies that are electrically isolated from one another Potentials within the station: Bus logic of the station I/O (outputs) I/O (inputs) 1-41 615605...
Page 56: Diagnostic And Status Indicators
FL IL 24 BK-PAC UM E 1.12 Diagnostic and status indicators All modules are provided with LED diagnostic and status indicators for local error diagnostics. Diagnostics The diagnostic indicators (red/green) indicate the type and location of the error. The module is functioning correctly if all of the green LEDs are on.
Page 57 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 Green 24 V supply, 7 V communications power/interface supply present 24 V supply, 7 V communications power/interface supply not present...
Page 58: Indicators On The Supply Terminal
FL IL 24 BK-PAC UM E 1.12.2 Indicators on the Supply Terminal 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...
Page 59: Indicators On The Input/Output Modules
FL IL 24 BK(-PAC) 1.12.3 Indicators on the Input/Output Modules Figure 1-28 I/O module indicators Diagnostics The following states can be read from the I/O modules: Table 1-18 Diagnostic LED of the I/O modules Color State Description of the LED States...
Page 60: Indicators On Other Inline Modules
FL IL 24 BK-PAC UM E Table 1-19 Status LEDs of the I/O terminals Color State Description of the LED States 1, 2, 3, 4 Yellow Relevant input/output set Relevant input/output not set Assignment Between Status LED and Input/Output For the assignment of a status LED and the corresponding input/output, please refer to the module-specific data sheet.
Page 61: Mounting/Removing Modules And Connecting Cables
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.
Page 62: Mounting
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.
Page 63 FL IL 24 BK(-PAC) 6138A015 Figure 1-29 Snapping on a module 1-49 615605...
Page 64: Removing
FL IL 24 BK-PAC UM E 1.13.4 Removing When removing a module, proceed as follows (Figure 1-30): • If there is a labeling field, remove it (A1 in detail A). If a module has more than one connector, all of these must be removed. Below is a description of how to remove a 2-slot module.
Page 65 FL IL 24 BK(-PAC) Figure 1-30 Removing a module Replacing a module If you want to replace a module within the Inline station, follow the removal procedure described above. Do not snap the connector of the module directly to the left back on yet.
Page 66: Replacing A Fuse
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.
Page 67 FL IL 24 BK(-PAC) Figure 1-31 Replacing a fuse 1-53 615605...
Page 68: Grounding An Inline Station
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.
Page 69 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 grounded DIN rail.
Page 70: Shielding An Inline Station
FL IL 24 BK-PAC UM E 1.14.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.
Page 71 FL IL 24 BK(-PAC) 1.14.2.1 Connecting an IB IL 24 AI 2/SF Analog Input Module • Connect the shielding to the shield connector (see Section 1.15.2, "Connecting Shielded Cables Using the Shield Connector"). • When connecting the sensor shielding with FE potential, ensure a large surface connection.
Page 72 FL IL 24 BK-PAC UM E 1.14.2.2 Connecting an Analog Output Module IB IL AO ... – Connect the shielding via the shield connector (see Section 1.15.2, "Connecting Shielded Cables Using the Shield Connector"). – When connecting the shielding with the FE potential, ensure a large surface connection.
Page 73: Connecting Cables
FL IL 24 BK(-PAC) 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...
Page 74 Push a screwdriver into the slot of the appropriate terminal point (Figure 1-35, 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).
Page 75: Connecting Shielded Cables Using The Shield Connector
FL IL 24 BK(-PAC) 1.15.2 Connecting Shielded Cables Using the Shield Connector Figure 1-36 Connecting the shield to the shield connector 1-61 615605...
Page 76 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).
Page 77 FL IL 24 BK(-PAC) 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).
Page 78: Connecting The Voltage Supply
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).
Page 79: Provision Of The Segment Voltage Supply At Power Terminals
FL IL 24 BK(-PAC) Use appropriate power terminals for different voltage areas To use different voltage areas within a station, a new power terminal must be used for each area. Dangerous voltage When the power terminal is removed, the metal contacts are freely accessible.
Page 80: Connecting Sensors And Actuators
FL IL 24 BK-PAC UM E 1.17 Connecting Sensors and Actuators Sensors and actuators are connected using connectors. Each module-specific data sheet indicates the connector(s) to be used for that specific module. Connect the unshielded cable as described in Section 1.15.1 on page 1-59 and the shielded cable as described in Section 1.15.2 on page 1-61.
Page 81: Connection Examples For Digital I/O Modules
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.
Page 82 FL IL 24 BK-PAC UM E Different Connection Methods for Sensors and Actuators 2-wire technology 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 U Actuator Figure 1-38, detail B, shows the connection of an actuator.
Page 83 FL IL 24 BK(-PAC) 3-wire technology Figure 1-39 3-wire termination for digital devices Sensor 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 U and GND.
Page 84 FL IL 24 BK-PAC UM E 4-wire technology Figure 1-40 4-wire termination for digital devices Sensor Figure 1-40, detail A, shows the connection of a shielded 4-wire sensor. The sensor signal is carried to terminal point IN1. The sensor is supplied via terminal points U and GND.
Page 85 Without Factory Manager ..............2-19 2.9.1 Trap Generation..............2-19 2.9.2 Representation of Traps in the Factory Manager ....2-19 2.9.3 FL IL 24 BK(-PAC)Traps............2-20 2.9.4 Defining the Trap Manager ............ 2-20 2.10 Factory Line I/O Configurator ............... 2-21 2.10.1 Factory Line I/O Browser ............
Page 86 FL IL 24 BK-PAC UM E 2.12 Interface Group (1.3.6.1.2.1.2) ............. 2-25 2.12.1 Private MIBs ................2-30 2.13 Meaning of the 7-Segment Display ............2-44 615605...
Page 87: Startup/Operation
Plug & 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.
Page 88: Transmitting Bootp Requests
FL IL 24 BK-PAC UM E 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 varying intervals (2 s, 4 s, 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.
Page 89: Manual Addition Of Devices Using The Factory Manager
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 –...
Page 90 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.
Page 91: Possible Address Combinations
Startup/Operation 2.6.1 Possible Address Combinations 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. 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.
Page 92: Subnet Masks
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.
Page 93 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 local network. If ANDing gives a different result, the data telegram is sent to the subnetwork router. Example for a class B subnet mask: 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...
Page 94: Web-Based Management
FL IL 24 BK-PAC UM E Web-Based Management The FL IL 24 BK(-PAC) has a web server, which generates the required pages for web-based management and, depending on the requirements of the user, sends them to the "Factory Manager" or a standard web browser.
Page 95: Structure Of The Web
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.
Page 96: Password Protection
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:// <IP-Adresse>/processdata.xml".
Page 97 Startup/Operation DIAGNOSTIC_STATUS Contains the INTERBUS status, indicated by all the bits in the diagnostic status _REGISTER 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. IL_BUS Frame for the connected Inline terminals.
Page 98 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: <?xml version="1.0"...
Page 99 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 "bF" is displayed. The process data is invalid because only internal values but no values on INTERBUS are indicated.
Page 100 FL IL 24 BK-PAC UM E Figure 2-3 Screenshot of the XML data 2-16 615605...
Page 101: Firmware Update
Startup/Operation Firmware Update Boot loader <1.80 (see WBM: Device Information/General): When activating a firmware update, ensure that a valid firmware version is available. Otherwise the management part of the device attempts to update repeatedly and is unavailable for management and diagnostic functions. 2.8.1 Firmware Update Using The Factory Manager The following steps must be carried out when executing a firmware update using...
Page 102 FL IL 24 BK-PAC UM E Figure 2-4 WBM firmware update The display indicates "03" (requesting firmware download at tftp server), then "04" (downloading firmware to memory) and finally "05" (firmware transfer to memory complete). The bus coupler is then automatically restarted.
Page 103: Firmware Update Using Web-Based Management (Wbm) Without Factory Manager
Startup/Operation Firmware Update Using Web-Based Management (WBM) Without Factory Manager The following steps must be carried out when executing a firmware update using WBM: 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.
Page 104: Fl Il 24 Bk(-Pac)Traps
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.
Page 105: Factory Line I/O Configurator
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 and OPC configurator.
Page 106: Opc Configurator
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.
Page 107 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.
Page 108: Management Information Base - Mib
(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.
Page 109: Interface Group (1.3.6.1.2.1.2)
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) ifIndex -- (2) ifDescr -- (3) ifType -- (4) ifMtu -- (5) ifSpeed -- (6) ifPhysAddress -- (7) ifAdminStatus -- (8) ifOperStatus...
Page 110 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) ipInReceives -- (4) ipInHdrErrors...
Page 111 Startup/Operation -- (11) ipRouteMask -- (12) ipRouteMetric5 -- (13) ipRouteInfo -- (22) ipNetToMediaTable -- (1) ipNetToMediaEntry -- (1) ipNetToMediaIfIndex -- (2) ipNetToMediaPhysAddress -- (3) ipNetToMediaNetAddress -- (4) ipNetToMediaType -- (23) ipRoutingDiscards ICMP Group (1.3.6.1.2.1.5) The Internet control message protocol group is mandatory for all systems. It contains information about error treatment and control in Internet data traffic.
Page 112 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.
Page 113 Startup/Operation EGP (1.3.6.1.2.1.8) The EGP group is mandatory for all systems that implement EGP. (8) egp -- (1) egpInMsgs -- (2) egpInErrors -- (3) egpOutMsgs -- (4) egpOutErrors -- (5) egpNeighTable -- (1) egpNeighEntry -- (1) egpNeighState -- (2) egpNeighAddr -- (3) egpNeighAs -- (4) egpNeighInMsgs -- (5) egpNeighInErrs...
Page 114: Private Mibs
Private MIBs 2.12.1.1 PhoenixContact MIB The 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...
Page 115 Startup/Operation pxcBasicName 1.3.6.1.4.1.4346.2.1.1 Syntax Display string Access Read Description Contains the manufacturer name, Phoenix Contact GmbH & Co. KG pxcBasicDescr 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 & Co. KG P.O. Box 1341...
Page 116 FL IL 24 BK-PAC UM E -- (2) flComponents -- (1) flComponentsTable -- (1) flComponentsEntry -- (1) flComponentsIndex -- (2) flComponentsName -- (3) flComponentsDescr -- (1) flComponentsURL -- (1) flComponentsOrderNumber flBasicName 1.3.6.1.4.1.4346.11.1.1.1 Syntax Display string Access Read Description Contains the name of the product group,...
Page 117 Startup/Operation flComponentsTable - flComponentsEntry 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 1.3.6.1.4.1.4346.11.1.2.1.1.1 Syntax Integer32 (1 ... 1024) Access Read Description Contains the component product index flComponentsName 1.3.6.1.4.1.4346.11.1.2.1.1.2 Syntax...
Page 118 FL IL 24 BK-PAC UM E 2.12.1.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.
Page 119 Startup/Operation -- (9) flWorkFWInfoBootTime -- (11) flWorkFWInfoOperStatus -- (12) flWorkFWInfoHealthText -- (2) flWorkFWCtrl -- (1) flWorkFWCtrlBasic -- (1) flWorkFWCtrlReset -- (2) flWorkFWCtrlTrapDestCapacity -- (2) flWorkFWCtrlTrapDest -- (1) flWorkFWCtrlTrapDestTable -- (1) flWorkFWCtrlTrapDestEntry -- (1) flWorkFWCtrlTrapDestIndex -- (2) flWorkFWCtrlTrapDestIPAddr -- (3) flWorkFWCtrlPasswd -- (1) flWorkFWCtrlPasswdSet -- (2) flWorkFWCtrlPasswdSuccess -- (4) flWorkFWCtrlUpdate...
Page 120 FL IL 24 BK-PAC UM E flWorkBasicName 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 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 1.3.6.1.4.1.4346.11.11.1.5...
Page 121 Startup/Operation flWorkComponentsIndex 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 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 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 page of this component with additional information flWorkComponentsDevSign...
Page 122 FL IL 24 BK-PAC UM E flWorkComponentsStrongReset 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. flWorkFWInfoVersion 1.3.6.1.4.1.4346.11.11.11.1.1 Syntax Octet string (4)
Page 123 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 & Co. KG, 2000 flWorkFWInfoBootVersion 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":...
Page 124 FL IL 24 BK-PAC UM E flWorkFWInfoBootStatus 1.3.6.1.4.1.4346.11.11.11.1.11 Syntax Integer Access Read Description Contains the operating state of the firmware. - Problem - No problem flWorkFWInfoHealthText 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.
Page 125 Startup/Operation flWorkFWCtrlTrapDestIndex 1.3.6.1.4.1.4346.11.11.11.2.2.1.1.1 Syntax Integer32 (1 ... 1024) Access Read Description Contains the index of the target component, which is to receive the traps flWorkFWCtrlTrapDestIPAddr 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 flWorkFWCtrlPasswdSet 1.3.6.1.4.1.4346.11.11.11.2.3.1...
Page 126 FL IL 24 BK-PAC UM E flWorkFWCtrlUpdateEnable 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 - Update firmware flWorkFWCtrlTftpIPAddr 1.3.6.1.4.1.4346.11.11.11.2.4.2 Syntax IP address...
Page 127 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 With read access, the value is always "1". 2-43 615605...
Page 128: Meaning Of The 7-Segment Display
FL IL 24 BK-PAC UM E 2.13 Meaning of the 7-Segment Display Table 2-2 During startup/operation: Display Meaning Boot loader is started, BootP requests are sent Firmware is extracted Firmware is started Operating Table 2-3 Additional information: Display Meaning P&P mode is activated...
Page 129 Startup/Operation Table 2-5 Boot loader error messages: Display Meaning Remedy 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...
Page 130 DDI or web page The points under "Remedy" are recommendations; they do not all have to be carried out for every error. For all other error codes displayed, please contact Phoenix Contact (see final page). Display in Modbus/TCP Operation On the 7-segment display a connected Modbus/TCP device is indicated by a decimal point.
Page 131 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 Firmware error Bus error, the bus was stopped due to an error Network error;...
Page 132 FL IL 24 BK-PAC UM E 2-48 615605...
Page 133 Section This section provides information about – the driver software – an example program Driver Software......................... 3-3 Documentation ..................3-3 3.1.1 Hardware and Firmware User Manual ........3-3 Software Structure.................. 3-3 3.2.1 Ethernet/Inline Bus Coupler Firmware ........3-4 3.2.2 Driver Software ................ 3-4 Support and Driver Update..............
Page 134 FL IL 24 BK-PAC UM E 3.10 Notification Mode.................. 3-56 3.11 Programming Support Macros.............. 3-58 3.11.1 Introduction ................3-58 3.12 Description of the 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...
Page 135: Driver Software
Driver Software 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.
Page 136: Ethernet/Inline Bus Coupler Firmware
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.
Page 137: Support And Driver Update
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.
Page 138: Transfer Of I/O Data
FL IL 24 BK-PAC UM E 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.
Page 139: Position Of The Process Data (Example)
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. Figure 3-5 Position of the process data according to the physical bus configuration...
Page 140: Startup Behavior Of The Bus Coupler
The FL IL 24 BK(-PAC) supports plug & play mode (P&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&P status (active or inactive) is stored retentively on the bus coupler.
Page 141: Expert Mode
Driver Software 3.5.2 Expert Mode Observe that the following description applies with inactive P&P mode. Possible combinations of both modes and their behavior are described on page 3-9. Expert mode inactive If expert mode is inactive (default upon delivery) an error-free configuration is automatically set to the "RUN"...
Page 142: Startup Diagrams Of The Bus Coupler
FL IL 24 BK-PAC UM E 3.5.4 Startup Diagrams of the Bus Coupler "Normal" mode / P&P mode and expert mode inactive Figure 3-6 "Normal" mode / expert mode and P&P mode inactive P&P mode inactive - expert mode active Figure 3-7 P&P mode inactive - expert mode active...
Page 143: Figure 3-8 P&P Mode Active - Expert Mode Inactive
Driver Software P&P mode active - expert mode inactive Figure 3-8 P&P mode active - expert mode inactive P&P mode active and expert mode active Figure 3-9 P&P mode active and expert mode active 3-11 615605...
Page 144: Changing And Starting A Configuration In P&P Mode
FL IL 24 BK-PAC UM E 3.5.5 Changing and Starting a Configuration in P&P Mode The following steps must be carried out when changing an existing configuration: Ensure that plug & play mode is active and expert mode is inactive.
Page 145: Changing A Reference Configuration Using The Software
Driver Software Changing a Reference Configuration Using the Software 3.6.1 Effects of Expert Mode Only switch to expert mode if you want to deactivate automatic configuration and activate manual configuration using the firmware commands. If expert mode (object 2275 ) is active, automatic startup of the connected local bus is prevented.
Page 146 FL IL 24 BK-PAC UM E Table 3-2 System parameters for the "Set_Value" service (750 Variable ID System Parameter Value/Comment 2240 Plug & play mode 0: Plug & play mode inactive 1: Plug & play mode active (takes effect after reboot)
Page 147: Description Of The Device Driver Interface (Ddi) Introduction
Driver Software 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...
Page 148: Working Method Of The Device Driver Interface
FL IL 24 BK-PAC UM E 3.7.2 Working Method of the Device Driver Interface Remote procedure call 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...
Page 149: Figure 3-10 Execution Of A Remote Procedure Call
Driver Software Remote Procedure Call Process Figure 3-10 Execution of a remote procedure call 3-17 615605...
Page 150: Description And Functions Of The Device Driver Interface
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:...
Page 151 Driver Software 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.
Page 152 FL IL 24 BK-PAC UM E Example Windows NT/2000 / UNIX: IBDDIHND ddiHnd; IBDDIRET ddiRet; ddiRet=DDI_DevOpenNode ("IBETH01N1_D", DDI_RW, &ddiHnd); if (ddiRet !=ERR_OK) /* Error treatment */ return: DDI_DevCloseNode Task: If a data channel is no longer needed, it can be closed using the DDI_DevCloseNode function.
Page 153 Driver Software Example UNIX / Windows NT/2000 IBDDIHND ddiHnd; IBDDIRET ddiRet; ddiRet=DDI_DevCloseNode (ddiHnd); if (ddiRet !=ERR_OK) /* Error treatment */ return; 3-21 615605...
Page 154 FL IL 24 BK-PAC UM E DDI_DTI_ReadData Task The DDI_DTI_ReadData 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.
Page 155 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, &dtiAcc); if (ddiRet != ERR_OK) /* Error treatment */ 3-23 615605...
Page 156 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. 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).
Page 157 Driver Software USIGN8 *data; /* Pointer to the data (read and write) */ } T_DDI_DTI_ACCESS; Example 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;...
Page 158 FL IL 24 BK-PAC UM E DDI_DTI_ReadWriteData Task: 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.
Page 159 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 */ USIGN8 *data;...
Page 160 FL IL 24 BK-PAC UM E DDI_MXI_SndMessage Task: The DDI_MXI_SndMessage function is used to send a message to the bus coupler. The function receives a node handle and a pointer to a T_DDI_MXI_ACCESS data structure as parameters. The T_DDI_MXI_ACCESS structure contains all the parameters that are needed to send the message.
Page 161 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; IB_SetCmdCode (oBuf, S_CREATE_CFG_REQ); IB_SetParaCnt (oBuf, 1); IB_SetParaN (oBuf, 1, 1); ddiRet = DDI_MXI_SndMessage (mxiHnd, &mxiAcc); if (ddiRet!=ERR_OK) /* Error treatment */ 3-29...
Page 162 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 T_DDI_MXI_ACCESS structure contains all the parameters that are needed to read the message.
Page 163 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, &mxiAcc); if (ddiRet != ERR_OK) /* Evaluation of the message */ msgCode = IB_GetMsgCode (iBuf);...
Page 164 FL IL 24 BK-PAC UM E GetIBSDiagnostic Task: The DDI_GetIBSDiagnostic function reads the diagnostic bit register and the diagnostic parameter register. The function receives a valid node handle and a pointer to a T_IBS_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.
Page 165: Monitoring Functions
Driver Software 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.
Page 166 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:...
Page 167: Process Data Monitoring Process Data Watchdog
Driver Software 3.8.1 Process Data Monitoring/ Process Data Watchdog 3.8.1.1 Process Data Watchdog Function By default upon delivery, process data watchdog is activated with 500 ms timeout. 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.
Page 168: Figure 3-11 Status Diagram Of The Process Data Watchdog
FL IL 24 BK-PAC UM E 3.8.1.2 Configuring the Process Data Watchdog and the Fault Response Modes Timeout can only be changed if the watchdog is in "INIT" state. The "INIT“ state occurs after a power up as long as no process data exchange has taken place or in the event of a timeout when fault response was activated and no acknowledgment of the NetFail has yet taken place.
Page 169: Connection Monitoring (Host Checking)
Driver Software 3.8.2 Connection Monitoring (Host Checking) Application Connection monitoring can be used to determine whether there is still a connection between the bus 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: –...
Page 170 FL IL 24 BK-PAC UM E Deactivating Monitoring If connection monitoring is no longer required, it can be deactivated using the ETH_ClearHostChecking function. Monitoring is only deactivated for the client and the connection, which are specified by the node handle. If the same client has...
Page 171 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 = ETH_SetHostChecking (ddiHnd, &hcTime);...
Page 172: Data Interface (Dti) Monitoring
FL IL 24 BK-PAC UM E ETH_ClearHostChecking Task: 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.
Page 173 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 "ETH_SETDTITimeoutCTRL").
Page 174 FL IL 24 BK-PAC UM E ETH_SetDTITimeoutCtrl Task: The ETH_SetDTITimeoutCtrl 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.
Page 175 Driver Software ETH_ClearDTITimeoutCtrl Task: The ETH_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.
Page 176: I/O Fault Response Mode
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:...
Page 177 Connection monitoring table Connection monitoring table after connection abort, cable interrupt or communication error Configuration of the Configuration: "Reset Fault Mode " Configuration: "Last State Fault Mode" FL IL 24 BK-PAC Internal memory Actual output Internal memory Actual output After connection...
Page 178: Treatment Of The Netfail Signal/Testing With Eth_Setnetfail
FL IL 24 BK-PAC UM E Example: The last entries in the internal memory have the following values: Module DO 16 DO 2 Value 0x0123 0x4321 0x0002 Writing the value 0x00A1 to the internal memory of the DO 16 after the connection...
Page 179 Driver Software ETH_SetNetFail Task: 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 assigned a node handle for a DTI or mailbox data channel of the relevant bus coupler as a parameter.
Page 180 FL IL 24 BK-PAC UM E Parameters: IBDDIHND nodeHd Node handle (MXI or DTI) for the bus coupler on which the NetFail status is to be read. T_ETH_NET_FAIL *netFailInfo Pointer to a structure, which contains the NetFail status and the reason for the NetFail, if applicable.
Page 181 Driver Software ETH_ClrNetFailStatus Task: The ETH_ClrNetFailStatus 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.
Page 182 FL IL 24 BK-PAC UM E ETH_SetNetFailMode Task: The ETH_SetNetFailMode routine is used to change the behavior of the controller board in the event of a NetFail. After startup, the controller board is in standard mode (ETH_NF_STD_MODE), which means that if a NetFail occurs, all outputs of the modules connected to the INTERBUS system are set to zero and the bus continues to run.
Page 183 Driver Software ETH_GetNetFailMode Task: The ETH_GetNetFailMode function can be used to read the set NetFail mode. The routine expects a valid node handle and a pointer to a T_ETH_NET_FAIL_MODE data structure (see above) as parameters. After the routine has been called successfully, the user can read the set NetFail mode from the structure.
Page 184: In Process Data Monitoring
FL IL 24 BK-PAC UM E 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 slowly or rarely change, the same process data is often transmitted in successive read cycles.
Page 185 Driver Software ETH_ActivatePDInMonitoring Task: 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 board. The function is assigned a valid node handle for a DTI data channel and a pointer to a T_ETH_PD_IN_MON structure as parameters.
Page 186 FL IL 24 BK-PAC UM E Format of the data typedef struct { structure: USIGN16 mode; /* Selects the monitoring mode*/ USIGN16 address; /* Start address of the area to be monitored*/ USIGN16 numOfBytes; /* Size of the area to be monitored*/ USIGN8 *maskData;...
Page 187 Driver Software 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.
Page 188: Notification Mode
FL IL 24 BK-PAC UM E 3.10 Notification Mode General: 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.
Page 189 Driver Software Format of the typedef struct { structure: USIGN32 mode; /* Defines the notification mode */ USIGN32 threadId; /*Thread identifier USIGN32 processId;/*Process identifier USIGN32 timeout; /*Timeout time in milliseconds }T_ETH_NOTIFY_INFO; Constants: #define ETH_NOTIFY_MODE_1 Windows NT/2000 Parameters: processId threadId timeout Abort time in milliseconds Format of the typedef struct {...
Page 190: Figure 3-12 Assignment Of The Process Data Between The Local Bus And The Computer Systems
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 an application program.
Page 191: Figure 3-13 Using The Macros For Programming Support
Driver Software Figure 3-13 Using the macros for programming support The macros are available for both processor types. However, for processors in Motorola format, the macros have no function. 3-59 615605...
Page 192: Description Of The Macros
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...
Page 193: Macros For Converting The Data Block Of A Command
Driver Software Table 3-9 Driver software macros Macro Task Page IB_PD_GetDataNLoByte Reads the low-order byte (bit 0 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...
Page 194 FL IL 24 BK-PAC UM E IB_SetParaN (n, m, o) Task: This macro converts a 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.
Page 195: Macros For Converting The Data Block Of A Message
Driver Software IB_SetBytePtrLoByte (n, m) Task: 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. Parameters: n(USIGN8 *): Pointer to the transmit buffer m(USIGN16): Parameter number Return value:...
Page 196 FL IL 24 BK-PAC UM E IB_GetParaNHiByte (n, m) Task: 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. Parameters: n(USIGN8 *): Pointer to the receive buffer...
Page 197: Macros For Converting Input Data
Driver Software 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) Task: This macro reads a double word (32-bit) from the specified position in the input buffer and converts it into Intel format.
Page 198: Macros For Converting Output Data
FL IL 24 BK-PAC UM E IB_PD_GetBytePtrHiByte (n, m) Task: This macro returns the address of a word starting with the high-order byte (bit 8 to 15). Parameters: n(USIGN8 *): Pointer to the input buffer m(USIGN16): Word number Return value:...
Page 199 Driver Software IB_PD_SetDataNHiByte(n, m, o) Task: This macro converts the high-order byte (bit 8 to 15) of a word to Motorola format and writes it to the specified position in the output buffer. Parameters: n(USIGN8 *): Pointer to the output buffer m(USIGN16): Word number o(USIGN8):...
Page 200: Diagnostic Options For Driver Software
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.
Page 201: Positive Messages
Driver Software Table 3-10 Driver software messages Code Error Message Cause Page 00A9 ERR_PLUG_PLAY Invalid write access to process data in P&P mode 3-75 0100 ERR_STATE_CONFLICT This service is not permitted in the selected operating 3-75 mode of the controller 0101 ERR_INVLD_CONN_TYPE Service called via an invalid connection...
Page 202: General Error Messages
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 processed successfully. 3.15.1 General Error Messages These error messages can occur when calling any DDI function.
Page 203 Driver Software ERR_DEV_NOT_READY 0089 Cause: The local bus master was addressed, even though it was not ready. Remedy: After a reset, request the local bus master using the GetIBSDiagnostic() function on the ready bit in the diagnostic bit register. Once this bit is set, the local bus master can be addressed.
Page 204: Error Messages When Opening A Data Channel
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:...
Page 205: Error Messages When Transmitting Messages/Commands
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 Cause: The send vector register for the node is in use.
Page 206 FL IL 24 BK-PAC UM E ERR_SVR_TIMEOUT 009E Meaning: If a message placed in the MPM by the local bus master is not retrieved by the MPM node addressed, this node does not reset the acknowledge message bit set by the local bus master, i.e., the MPM node addressed does not indicate Message...
Page 207: Error Messages When Transmitting Process Data
Driver Software 3.15.4 Error Messages When Transmitting Process Data These errors only occur when accessing the data interface (DTI). ERR_AREA_EXCDED 0096 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.
Page 208 FL IL 24 BK-PAC UM E ERR_INVLD_CONN_TYPE 0101 Cause: A service was called, which cannot be executed via the selected connection. Remedy: Select a connection type via which the service can be executed. ERR_ACTIVE_PD_CHK 0102 Cause: IN process data monitoring failed to activate.
Page 209 Driver Software ERR_IBSETH_READ 1013 Cause: The IBSETHA file cannot be read. Remedy: The file exists but cannot be read. You may not have read access. ERR_IBSETH_NAME 1014 Cause: The device name cannot be found in the file. Remedy: The name, which was transferred to the DDI_DEVOPEN_NODE () function, is not in the IBSETHA file.
Page 210: Figure 3-14 Structure Of The Station For The Example Program
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.
Page 211: Figure 3-15 Screenshot Of The Example Program
Driver Software Function: First, the status of plug & play mode is read. If P&P mode is activated (value = 1) the program is terminated with the error message 00A9 (ERR_PLUG_PLAY), because process data cannot be written in P&P mode for security reasons. A check then determines whether the local bus in the station is running.
Page 212: Example Program Source Code
FL IL 24 BK-PAC UM E 3.16.2 Example Program Source Code /*======================================================================*/ /* INCLUDE FILES AND CONSTANT DEFINITION */ /*======================================================================*/ #include <stdio.h> #include <stdlib.h> #include <time.h> #include <string.h> /*********************************************************** * Include files for the CLIENT library Windows version ************************************************************/ #include "ethwin32.h"...
Page 213 Driver Software fflush(stdout); return 111; else printf("\nMailbox connection...OK Handle: %d",mxiHnd); /*Data channel connection*/ ret = DDI_DevOpenNode(OPEN_DTI,DDI_RW,&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("\nData channel connection...OK Handle: %d",dtiHnd); return 0;...
Page 214 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"); return 0; *======================================================================*/ /*======================================================================*/ /* M A I N */...
Page 215 %s OPEN_DTI: %s",OPEN_MXI,OPEN_DTI); printf("\n ========================================= \n"); // Create connections (DTI and MXI channels) to FL IL 24 BK-PAC locRet = CreateConnection(); if(locRet != 0){ printf("\nNo DTI/MXI connection -> Test aborted"); exit(0); Sleep(500); // Read plug & play mode mxiAcc.msgLength = 8;...
Page 216 FL IL 24 BK-PAC UM E else PlugPlayModus = IB_GetParaN(locMsgBlk, 0x04); printf("\nPlug & Play mode: %d",PlugPlayModus); // If plug & play mode is active, no data can be written // -> End of test if(PlugPlayModus != 0) { printf("\nPlug & play mode is active -> End of test\n");...
Page 217 Driver Software locMsgBlk[i]=0; locRet = DDI_DTI_WriteData(dtiHnd,&dtiAcc); if(locRet != ERR_OK){ printf("\nError when resetting buffer. Error code: 0x%04X",locRet); Sleep(100); //Loop for reading and writing 255 data items //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,loci);...
Page 218 FL IL 24 BK-PAC UM E else { printf("\rWritten: %3d Read: %3d Comparison: FAILED",loci, ReadData); loci++; while(loci < 256); Sleep(500); // Close channels to FL IL 24 BK-PAC again locRet = DeleteConnection(); printf("\nEND\n"); Sleep(3000); return 0; 3-86 615605...
Page 219 Section This section provides information about – firmware functions Firmware Services......................4-3 Overview....................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..........4-5 Services for Parameterizing the Controller Board ........
Page 220 FL IL 24 BK-PAC UM E 615605...
Page 221: Overview
Firmware Services 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: –...
Page 222: Services Available Only In Expert Mode
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 030C Delete_Configuration 4-29 030E Control_Parameterization 0701 Start_Data_Transfer...
Page 223: Name_Of_The_Service" Service
Firmware Services 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). Structure of a service A service request/confirmation consists of a block of data words. The parameters description that are contained in this block are given in hexadecimal ( ) or binary (...
Page 224 FL IL 24 BK-PAC UM E Syntax: Name_of_the_Service_Confirmation Code Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Negative message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Add_Error_Info 15 ................. 0 Key: Code: 8xxx...
Page 225: Services For Parameterizing The Controller Board
Firmware Services Services for Parameterizing the Controller Board 4.3.1 "Control_Parameterization" Service Task: This service initiates or terminates the parameterization phase. This is necessary in order to ensure a defined startup behavior for the Inline system. During the parameterization phase, for example, the validity of read objects is not ensured. Once the parameterization phase has been terminated, the MPM_Node_Parameterization_Ready bit is set in the coupling memory.
Page 226 FL IL 24 BK-PAC UM E Syntax: Control_Parameterization_Confirmation 830E Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Negative message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Add_Error_Info 15 ................. 0 Key: Code: 830E...
Page 227: Set_Value" Service
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...
Page 228 FL IL 24 BK-PAC UM E Word 3 Variable_Count Word 4 Variable_ID 1. parameter Word 5 Value 15 ................. 0 Key: Code: 0750 Command code of the service request Parameter_Count: Number of subsequent words, 0x0003 Variable_Count: Number of system parameters to which new values...
Page 229: Read_Value" Service
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). For a list of defined system parameters (variables), please refer to the description of the "Set_Value"...
Page 230 FL IL 24 BK-PAC UM E Syntax: Read_Value_Confirmation 8351 Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Variable_Count Word 5 Variable_ID 1. system parameter Word 6 Value Negative message Word 1 Code Word 2 Parameter_Count...
Page 231: Initiate_Load_Configuration" Service
Firmware Services 4.3.4 "Initiate_Load_Configuration" Service Task: The "Initiate_Load_Configuration" service prepares the controller board to transmit a configuration to the INTERBUSmaster using the following services: - "Load_Configuration" (0307 ) or - "Complete_Load_Configuration" (030A To transmit a new configuration frame (New_Config parameter = 0001 ), specify the Frame_Reference and Device_Count parameters (total number of devices).
Page 232 FL IL 24 BK-PAC UM E Syntax: Initiate_Load_Configuration_Confirmation 8306 Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Negative message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Add_Error_Info 15 ................. 0 Key: Code: 8306...
Page 233: Load_Configuration" Service
Firmware Services 4.3.5 "Load_Configuration" Service Task: The configuration frame describes each of the specified INTERBUS devices in a separate numbered entry. The order and the numbering of the entries corresponds to the physical bus configuration. This service transfers the configuration data to the controller board in the form of a list.
Page 234 FL IL 24 BK-PAC UM E 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"...
Page 235 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 printed as Module Ident in decimal notation on the modules. The Length_Code and ID_Code parameters together form the device number.
Page 236: Terminate_Load_Configuration" Service
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 no error is detected, the controller board stores the data in the configuration directory under the Frame_Reference given in the "Initiate_Load_Configuration"...
Page 237 Firmware Services Syntax: Terminate_Load_Configuration_Confirmation 8308 Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Negative message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Add_Error_Info 15 ................. 0 Key: Code: 8308 Message code of the service confirmation Parameter_Count: Number of subsequent words with a positive message:...
Page 238: Read_Configuration" Service
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 0000 Header information of the configuration frame (CFG_Header) selected with the Frame_Reference parameter.
Page 239 Firmware Services Start_Entry_No: Position of the first entry 0000 only reads the header information for the configuration frame. xxxx 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.
Page 240 FL IL 24 BK-PAC UM E 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 15 ................. 0 3. structure Positive message during service request with: – Frame_Reference > 0000 – Start_Entry_No >...
Page 241 Firmware Services with a positive message and if Frame_Reference > 0000 and Start_Entry_No = 0000 000D 12 parameter words with a positive message and if Frame_Reference > 0000 and Start_Entry_No > 0000 xxxx The value depends on the number of devices in the configuration frame and the number of enabled attributes.
Page 242 FL IL 24 BK-PAC UM E Active_IO_Bit_Count: Number of active I/O bits in the selected configuration 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:...
Page 243 Firmware Services Syntax "Configuration_Entry" Attribute: Word x Bus_Segment_No Position Device number Word x+1 Length_Code ID_Code Device code 15 ........8 7 ........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:...
Page 244: Complete_Read_Configuration" Service
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.
Page 245 Firmware Services Syntax: Complete_Read_Configuration_Confirmation 830B Positive message 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 0001 Word 8 Entry_Count Word 9 Configuration_Entry 1. device Configuration_Entry nth device Negative message Word 1 Code...
Page 246 FL IL 24 BK-PAC UM E Add_Error_Info: Additional information on the error cause More_Follows: 0000 indicates that all requested entries are contained in the service confirmation. 0001 indicates that the service confirmation does not contain all requested entries as the amount of data is larger than the mailbox (MXI) that is available for the services.
Page 247: Delete_Configuration" Service
Firmware Services 4.3.9 "Delete_Configuration" Service Task: This service deletes an inactive configuration frame from the configuration directory. Syntax: Delete_Configuration_Request 030C Word 1 Code Word 2 Parameter_Count Word 3 Frame_Reference 15 ................. 0 Key: Code: 030C Command code of the service request Parameter_Count: Number of subsequent words 0001...
Page 248: Create_Configuration" Service
FL IL 24 BK-PAC UM E Result: Result of the service processing 0000 indicates a positive message. The controller board has executed the service successfully. xxxx indicates a negative message. The controller board could not execute the service successfully. The Result parameter indicates why the service could not be executed.
Page 249 Firmware Services Parameter_Count: Number of subsequent words 0001 1 parameter word Frame_Reference: 0001 Syntax: Create_Configuration_Confirmation 8710 Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Negative message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Add_Error_Info 15 .................
Page 250: Activate_Configuration" Service
FL IL 24 BK-PAC UM E 4.3.11 "Activate_Configuration" Service Task: This service enables the controller board to check the configuration data of the configuration frame for – conformance with the currently connected configuration – address overlaps If no errors are detected, the controller board activates this configuration frame (display: "PP"...
Page 251 Firmware Services Syntax: Activate_Configuration_Confirmation 8711 Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Negative message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Add_Error_Info 15 ................. 0 Key: Code: 8711 Message code of the service confirmation Parameter_Count: Number of subsequent words with a positive message:...
Page 252: Control_Device_Function" Service
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...
Page 253 Firmware Services Syntax: Control_Device_Function_Confirmation 8714 Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Negative message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Add_Error_Info 15 ................. 0 Key: Code: 8714 Message code of the service confirmation Parameter_Count: Number of subsequent words with a positive message:...
Page 254: Reset_Controller_Board" Service
FL IL 24 BK-PAC UM E 4.3.13 "Reset_Controller_Board" Service Task: This service can be used to initiate a controller board reset. Prerequisite: Before calling this service, ensure that the state of your system permits a controller board reset. Syntax: Reset_Controller_Board_Request...
Page 255 Firmware Services 0000 indicates a positive message. The controller board has executed the service successfully. xxxx 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-37...
Page 256: Services For Direct Interbus Access
FL IL 24 BK-PAC UM E Services for Direct INTERBUS Access 4.4.1 "Start_Data_Transfer" Service Task: 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 & play mode, "--"...
Page 257 Firmware Services Syntax: Start_Data_Transfer_Confirmation 8701 Positive message Word 1 Code Word 2 Parameter_Count Word 3 Result Negative message Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Add_Error_Info 15 ................. 0 Key: Code: 8701 Message code of the service confirmation Parameter_Count: Number of subsequent words with a positive message:...
Page 258: Alarm_Stop" Service
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"...
Page 259: Diagnostic Services
Firmware Services xxxx 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 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.
Page 260 FL IL 24 BK-PAC UM E Syntax: Get_Error_Info_Confirmation 8316 Positive message, as long as error localization is still in progress Word 1 Code Word 2 Parameter_Count Word 3 Result Word 4 Entry_Count = 0001 Word 5 Error_Code = 0BDF = FFFF...
Page 261 Firmware Services Key: Code: 8316 Message code of the service confirmation Parameter_Count: Number of subsequent words with positive message (during error localization): 0004 4 parameter words with positive message (after error localization): = 2 + 2 × Entry_Count 00xx (20 words, maximum) with a negative message: 0002 Always 2 parameter words...
Page 262 FL IL 24 BK-PAC UM E Code Error Type Page 0x0BB1 E_PNM12_DEVICE_STATE 4-45 0x0D10 E_PNM12_CONFIG_MISSING_DEVICE 4-45 0x0D20 E_PNM12_CONFIG_MAU_FAIL_DO 4-45 0x0D28 E_PNM12_CONFIG_MAU_FAIL DI 4-46 0x0D4C E_PNM12_CONFIG_INVALID_ID 4-46 0x0D80 E_PNM12_CONFIG_MULTI_ERR_OUT 4-46 0x0D9C E_PNM12_CONFIG_LB_TOO_LONG_OUT 4-46 0xFFFF CONTROLLER_DEVICE_NUMBER 4-46 Error Code Description E_SM_CFG_NUM_OF_DEV_TOO_BIG 0A1C Cause: You exceeded the permitted number of specified or connected INTERBUS devices.
Page 263 Firmware Services E_PNM12_STATE_CONFLICT 0B02 Cause: – It may be that - there is an empty configuration frame - the first device after the bus coupler is faulty or missing Remedy: – - Activate a correct configuration frame or - Use the first device or an operational device. E_PNM12_DEVICE_STATE 0BB1 Meaning:...
Page 264 FL IL 24 BK-PAC UM E E_PNM12_CONFIG_MAU_FAIL DI 0D28hex Meaning: The Medium Attachment Unit (MAU) diagnosed an interruption of the data transmission. Cause: Cable break on the data return path of the incoming bus interface (IN) of the indicated Inline device.
Page 265: Get_Version_Info" Service
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 032A Word 1 Code Word 2 Parameter_Count 15 ................. 0 Key: Code: 032A...
Page 266 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) Start_FW_State (byte 6) Words 41 ... 43 Start_FW_Date (byte 1) Start_FW_Date (byte 6) Words 44 ...
Page 267 Creation time of the firmware (6 bytes) (e.g., 31 34 31 30 32 30 for 14:10:20) Host_Type: Type of the host-specific firmware interface (e.g., FL IL 24 BK-PAC) (20 bytes) Host_Version: Version of the host-specific firmware interface bytes) Host_State: Status of the host-specific firmware...
Page 268: Error Messages For Firmware Services
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) Error Messages for Firmware Services 4.6.1 Overview Table 4-6 Overview of error messages (according to error codes)
Page 269: Positive Messages
Firmware Services 4.6.2 Positive Messages ERR_OK 0000 Meaning After successful execution of a function, the firmware generates this message as a positive acknowledgment. Cause No errors occurred during execution of the function. 4.6.3 Error Messages If the firmware generates one of the following codes as an acknowledgment, this indicates that an error occurred during execution, and the called function could not be executed successfully.
Page 270 FL IL 24 BK-PAC UM E ACTION_HANDLER_OVERLAP 091D Cause Cannot read from or write to the EEPROM. Additional info 0001 : Write error Additional info 0002 : Read error INCORRECT_STATE 0A02 Cause The called service is not permitted in the current status of the device.
Page 271 Firmware Services INTERNAL_TIMEOUT 0E22 Cause The function_start_reg was not reset within the timeout. Additional info xxxx Timeout in hex FUNCTION_REG_NOT_FREE 0E23 Cause The function_start_reg is not empty. ACTION_ERROR 0E24 Cause The service could not be executed correctly. Additional info 0005 : Bus data could not be detected Additional info 00A5 : The configuration could not be activated.
Page 272 FL IL 24 BK-PAC UM E 4-54 615605...
Page 273 Section This section provides information about – supported PCP commands PCP Communication ......................5-3 Transmission of Parameter Data............5-3 5.1.1 PCP Configuration in the Web-Based Management....5-4 5.1.2 Configuration of the PCP PDU Size ........5-4 Supported PCP Commands ..............5-5 615605...
Page 274 FL IL 24 BK-PAC UM E 615605...
Page 275: Pcp Communication
PCP Communication PCP Communication 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.
Page 276: Pcp Configuration In The Web-Based Management
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.
Page 277: Supported Pcp Commands
PCP Communication Supported PCP Commands Table 5-1 Supported PCP commands Service Service Code Initiate_Request 008B Abort_Request 088D Get_OD_Request 0088 Read_Request 0081 Write_Request 0082 Information_Report_Request 0885 Status_Request 0083 Identify_Request 0087 PNM7_Initiate_Request 00A0 PNM7_Abort_Request 08A1 Load_Kbl_Par_Loc_Request 0264 Service_Execution_Remote_Request 00C1 Read_Kbl_Loc_Request 0203 615605...
Page 278 FL IL 24 BK-PAC UM E 615605...
Page 279 Section This section provides information about – the Modbus/TCP protocol – supported commands Modbus/TCP Protocol ...................... 6-3 Modbus Protocol..................6-3 6.1.1 Modbus Connections ............... 6-3 6.1.2 Modbus Port ................6-4 6.1.3 Modbus Conformance Classes..........6-4 6.1.4 Modbus Message Format ............6-4 6.1.5 Modbus Byte Order..............
Page 280 FL IL 24 BK-PAC UM E Monitoring..................... 6-25 Modbus Monitoring ................6-26 I/O Fault Response Mode..............6-26 6.9.1 Power Up Table ..............6-27 6.9.2 Connection Monitoring Table ..........6-28 6.10 Modbus/TCP PCP Registers ..............6-30 615605...
Page 281: Modbus/Tcp 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.
Page 282: Modbus Port
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.
Page 283: Modbus Bit Order
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 (%I), discrete output (%Q), analog inputs (%AI), 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.
Page 284: Dynamic Modbus/Tcp Process Data Table
FL IL 24 BK-PAC UM E 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 %I1 –...
Page 285: Example: Location Of The Input/Output Data
Modbus/TCP Protocol 6.3.2 Example: Location of the Input/Output Data Figure 6-1 Location of the data in input/output modules 615605...
Page 286: Location Of The Process Data In Dynamic Tables
FL IL 24 BK-PAC UM E 6.3.3 Location of the Process Data in Dynamic Tables Figure 6-2 Location of the process data in dynamic tables 615605...
Page 287: Supported Function Codes
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 I/O tables as well as to the fault table.
Page 288: Read Multiple Registers
FL IL 24 BK-PAC UM E – Write single register (function code 6) – Read exception status (function code 7) – Write multiple coils (function code 15) – Read/write register (function code 23) The following function command and response message descriptions start with the Modbus function code (byte 0 is actually byte 7 of the Modbus message format).
Page 289: Write Multiple Registers
Modbus/TCP Protocol 6.5.1.1 Examples for "Read Multiple Registers": Register table offset = 0 and word count = 2 returns %I1-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 combination of the register table offset and the word count which accesses an offset >...
Page 290: Read Coils
FL IL 24 BK-PAC UM E Table 6-11 Exception response to "write 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 %Q1-32.
Page 291: Read Input Discretes
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 Coils":...
Page 292: Read Input Registers
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 %I1.
Page 293: Write Coils
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 "Examples for ’Read Multiple Registers’" section. 6.5.6 Write Coils With this command, 1 bit is written into the Modbus coil table.
Page 294: Write Single Register
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 %Q1 OFF. Each coil table offset > 3072 produces an exception response.
Page 295: Read Exception Status
Any register table offset < 384 or (> 576 and < 1024) or > 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.
Page 296: Exception Responses
FL IL 24 BK-PAC UM E 6.5.10 Exception Responses Table 6-30 Exception responses No. Designation Meaning ILLEGAL FUNCTION The transmitted function code is not supported by this device version. ILLEGAL DATA The transmitted address is invalid for the device, the combination of reference ADDRESS number and transmission length is wrong.
Page 297: Write Multiple Coils
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...
Page 298: Read/Write Register
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 (%Q and %AQ).
Page 299 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 %Q1-32. Register table offset = 575 and word count = 2 writes the register values into coils %Q3057-3072 and the analog output %AQ1.
Page 300: Reserved Registers For
FL IL 24 BK-PAC UM E 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.
Page 301: Status Word
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 ..Status word 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.
Page 302: Fault Table
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).
Page 303: Monitoring
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...
Page 304: 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.
Page 305: Power Up Table
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.
Page 306: Connection Monitoring Table
FL IL 24 BK-PAC UM E 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 a communication error while the voltage supply remains the same.
Page 307 Modbus/TCP Protocol Example: The last entries in the output table have the following values: Module DO 16 DO 2 Value 0x0123 0x4321 0x0002 Writing 0x00A1 into the output table of the DO 16 as the first value after having restored the connection gives the following actual output value: Module DO 16 DO 2...
Page 308: Modbus/Tcp Pcp Registers
– 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...
Page 309 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 0x5FE0 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.
Page 310 FL IL 24 BK-PAC UM E 6-32 615605...
Page 311 Section This section provides information about – technical data – ordering data Technical Data........................7-3 Ordering Data ..................7-11 615605...
Page 312 FL IL 24 BK-PAC UM E 615605...
Page 313: Technical Data
Technical Data 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°C (+32°F to +131°F) Permissible storage temperature (EN 60204-1) -25°C to 85°C (-13°F to +185°F) Degree of protection...
Page 314 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 8 A, maximum (total current of U and U...
Page 315 Technical Data 24 V Bus Coupler Supply 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 1.5 A (Loading the 7.5 V communications power with 2 A,...
Page 316 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)
Page 317 Technical Data Power Dissipation Formula to Calculate the Power Dissipation of the Electronics PERI Where Total power dissipation in the terminal Power dissipation for bus operation without I/O load (permanent) Power dissipation with I/O connected PERI Current consumption of the device n from the communications power Index of the number of connected devices (n = 1 to a) Number of connected devices (with communications power supply) Total current consumption of the devices from the 7.5 V communications power...
Page 318 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...
Page 319 Technical Data Bus Interface of the Lower-Level System Bus Interface Inline local bus Electrical isolation Number of Inline terminals that can be connected Limited by software 63, maximum Limited by power supply unit Maximum logic current consumption of the connected ≤...
Page 320 FL IL 24 BK-PAC UM E Mechanical Tests Shock test according 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.)
Page 321: Ordering Data
OPC server IBS OPC SERVER 27 29 12 7 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 43 04 8 Range"...
Page 322 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 08 01 73 3 NS 35/7,5 ungelocht 08 01 68 1 End clamp snapped on without tools...
Page 323: Reference Data
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 of the supply voltage ....... 1-7 Figure 1-4: Basic structure of an Inline module ........1-16 Figure 1-5: Inline connector types ............
Page 324 Removing a module ............. 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 > 10 m (32.81 ft.) ........... 1-57 Figure 1-34: Connection of actuators, signal cables >...
Page 325 Table of Figures Section 3 Figure 3-1: Software structure ..............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 array ..............3-6 Figure 3-4: Position of the user data for several devices in the word array ..............
Page 326 FL IL 24 BK-PAC UM E 615605...
Page 327 Appendix A List of Tables Section 1 Table 1-1: Local status and diagnostic indicators ........1-6 Table 1-2: Connector assignment............1-8 Table 1-3: Digital Input/Output Modules ..........1-9 Table 1-4: Analog input/output modules ..........1-11 Table 1-5: Special function modules............1-12 Table 1-6: Motor terminal blocks............
Page 328 FL IL 24 BK UM E Section 2 Table 2-1: Sequence displayed after the device is switched on ....2-3 Table 2-2: During startup/operation: ............2-44 Table 2-3: Additional information: ............2-44 Table 2-4: During firmware update: ............2-44 Table 2-5: Boot loader error messages: ..........
Page 329 List of Tables Section 5 Table 5-1: Supported PCP commands ............ 5-5 Section 6 Table 6-1: Modbus message format ............6-4 Table 6-2: Supported function codes ............6-5 Table 6-3: Modbus reference tables ............6-6 Table 6-4: Dynamic process data table ........... 6-6 Table 6-5: Applicable functions..............
Page 330 FL IL 24 BK UM E Table 6-29: Exception status data format ..........6-17 Table 6-30: Exception responses ............6-18 Table 6-31: Write multiple coils..............6-19 Table 6-32: Response to "write multiple coils"......... 6-19 Table 6-33: Exception response to "write multiple coils" ......6-19 Table 6-34: Read/write register..............

This manual is also suitable for:

Fl il 24 bk-pac

Phoenix Contact FL IL 24 BK User Manual

Table of Contents

2 Section

3 Section

5 Section

6 Section

Section 3

Quick Links

Chapters

Need help?

Questions and answers

Related Manuals for Phoenix Contact FL IL 24 BK

Summary of Contents for Phoenix Contact FL IL 24 BK