Phoenix Contact ILC 330 Series User Manual
  1. Manuals
  2. Brands
  3. Phoenix Contact Manuals
  4. Controller
  5. ILC 330 Series
  6. User manual

Phoenix Contact ILC 330 Series User Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Installing and operating the
ILC 330... and ILC 350...
Inline controllers
User manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ILC 330 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Phoenix Contact ILC 330 Series

Summary of Contents for Phoenix Contact ILC 330 Series

  • Page 1 Installing and operating the ILC 330... and ILC 350... Inline controllers User manual...
  • Page 2 This user manual is valid for: Designation As of version (HW) As of version (FW) Order No. ILC 330 ETH 4.6F/1.41 2737193 ILC 330 PN 4.6F/3.11 2988191 ILC 350 ETH 4.6F/1.11 2737203 ILC 350 ETH/M 4.6F/1.20 2985819 ILC 350 PN 4.6F/1.3F 2876928 PHOENIX CONTACT 6959_en_07...
  • Page 3 How to contact us Internet Up-to-date information on Phoenix Contact products and our Terms and Conditions can be found on the Internet at: phoenixcontact.com Make sure you always use the latest documentation.
  • Page 4 The receipt of technical documentation (in particular user documentation) does not constitute any further duty on the part of Phoenix Contact to furnish information on modifications to products and/or technical documentation. You are responsible to verify the suitability and intended use of the products in your specific application, in particular with regard to observing the applicable standards and regulations.

  • Page 5: Table Of Contents

    24 V segment supply ................38 2.14.5 24 V main voltage ................38 2.14.6 24 V ILC supply ..................38 2.14.7 Jumpers ....................38 2.15 Digital inputs and outputs ..................39 The Inline controller under PC Worx ..................43 Software version....................43 IP address ......................43 6959_en_07 PHOENIX CONTACT...
  • Page 6 Status information of each PROFINET device (ILC 330 PN / ILC 350 PN) ..79 Technical data and ordering data .....................81 Technical data .....................81 Ordering data.......................88 5.2.1 Products ....................88 5.2.2 Accessories ..................88 5.2.3 Software ....................88 5.2.4 Documentation ..................88 PHOENIX CONTACT 6959_en_07...
  • Page 7 Table of contents Technical appendix: service and maintenance .................89 Error causes and remedies..................89 Updating the Inline controller firmware..............89 Connecting unshielded cables................90 Appendix for document lists......................91 List of figures .......................91 List of tables ......................93 Index........................95 6959_en_07 PHOENIX CONTACT...
  • Page 8 ILC 330.../350... PHOENIX CONTACT 6959_en_07...

  • Page 9: Foreword

    ILC 350 PN PC Worx Version 5.00 or later (part of the AUTOMATIONWORX Software Suite 2006 1.20) For the ordering data for hardware, software, and additional documentation, please refer to “Technical data and ordering data” on page 81. 6959_en_07 PHOENIX CONTACT...
  • Page 10 ILC 330.../350... PHOENIX CONTACT 6959_en_07...

  • Page 11: Description Of The Inline Controller

    The Inline controller can also be used as the head of an INTERBUS Inline station. An Inline local bus as well as a remote bus can be connected. In this way you can create a complete INTERBUS system using the Inline controller as a distributed controller. 6959_en_07 PHOENIX CONTACT...

  • Page 12: Examples Of Topologies With Interbus

    Figure 2-1 Connected Inline local bus MRESET FAIL RUN / PROG 10/100 RB-T INLINE CONTROL ILC 350 ETH Ord.No.: 27 37 203 RESET RDY / RUN FAIL Ethernet INTERBUS remote bus 6959B002 Figure 2-2 Connected remote bus PHOENIX CONTACT 6959_en_07...

  • Page 13: Examples Of Topologies With Profinet

    00A0451B8D M12 DI8 M12 RESET 2RTD INTERBUS 10/100 IN3 IN4 IN5 IN6 IN7 IN8 IB BK DIO 4/4 DIO 4/4 FLM DIO 4/4 M12-2A 6959C030 Figure 2-3 ILC 350 PN in a system comprising PROFINET and INTERBUS 6959_en_07 PHOENIX CONTACT...

  • Page 14: Unpacking The Inline Controller

    ESD regulations. NOTE: Electrostatic discharge The device contains components that can be damaged or destroyed by electrostatic discharge. When handling the device, observe the necessary safety precautions against electrostatic discharge (ESD) according to EN 61340-5-1 and IEC 61340-5-1. PHOENIX CONTACT 6959_en_07...

  • Page 15: Connection And Operating Elements

    Ethernet connection Reset button RS-232 interface Connectors 1 to 3: input terminal points Connector 4: output terminal points Connector 5: terminal points for voltage supply Mode selector switch Card holder for the parameterization memory 10 End plate 6959_en_07 PHOENIX CONTACT...

  • Page 16: Diagnostics And Status Indicators

    IEC 61131 runtime system not ready to operate. IEC 61131 runtime system successfully initialized. Flashing Green Control function is in the READY/STOP state, program not processed. IEC 61131 runtime system successfully initialized and a program is running. Control function is in the RUN state. PHOENIX CONTACT 6959_en_07...
  • Page 17 (see also “Power supply” on page 35) 24 V supply for segment circuit Green Supply voltage is present. Supply voltage is not present. 24 V supply for main circuit Green Supply voltage is present. Supply voltage is not present. 6959_en_07 PHOENIX CONTACT...
  • Page 18 ILC 330.../350... Des. Color Status Meaning 24 V supply U for generating voltages U and U Supply voltage is present Green (indication if 24 V supply voltage U is present). Supply voltage is not present. PHOENIX CONTACT 6959_en_07...

  • Page 19: Mode Selector Switch

    . : 2 . : 2 I L C I L C ie nn ie nn (S er (S er x x x x x x x x x x x x 6959B014 Figure 2-6 Mode selector switch 6959_en_07 PHOENIX CONTACT...

  • Page 20: Reset Button (Concealed)

    . : 2 . : 2 I L C I L C ie nn ie nn (S er (S er x x x x x x x x x x x x RESET 6959B015 Figure 2-7 Reset button PHOENIX CONTACT 6959_en_07...

  • Page 21: Parameterization Memory

    A parameterization memory (CompactFlash card) is absolutely necessary in order to operate the Inline controller. The parameterization memory is available with 256 MB and 2 GB. NOTE: Only use a parameterization memory provided by Phoenix Contact: – 256 MB parameterization memory CF FLASH 256MB (Order No. 2988780) –...

  • Page 22: Inserting The Parameterization Memory

    6959B007 Figure 2-8 Inserting the parameterization memory One side of the parameterization memory has a marking field. You can enter the file name for your project in the marking field, for example. PHOENIX CONTACT 6959_en_07...

  • Page 23: Parameterization Memory And Internet Explorer

    • Select the “Extended Settings” tab in the “Device Details” window. • Open Internet Explorer from this window by clicking on the “Open FTP folder on device” button. Figure 2-9 Extended Settings: Open FTP folder on device 6959_en_07 PHOENIX CONTACT...

  • Page 24: Internet Explorer Ftp Functionality

    For the current state to be displayed, update the display after every action by means of the “View, Update” command. 2.9.4 Internet Explorer FTP functionality • Activate this setting in Internet Explorer under “Options... Internet Properties... Advanced”. Figure 2-10 Internet Properties: Enable folder view for FTP sites PHOENIX CONTACT 6959_en_07...

  • Page 25: Activating/Deactivating The Ftp Server

    ETH_SRV_HTTP_ACTIVE system variable. This setting is restored the next time the Inline controller is rebooted. Value range for the CPU_Set_Value_Request service: Var ID 0173 Value 0000 Deactivate HTTP server 0001 Activate HTTP server 6959_en_07 PHOENIX CONTACT...

  • Page 26: Internal Basic Circuit Diagram

    Clock generator for local bus clock FPGA Ethernet Converter SDRAM Synchronous dynamic RAM Optocoupler Digital output Transistor Resistor Digital input Protective circuit Other symbols used are explained in the IB IL SYS PRO UM E user manual. PHOENIX CONTACT 6959_en_07...

  • Page 27: Mounting And Removing The Inline Controller

    Mount end brackets on both sides of the Inline station. The end brackets ensure that the Inline station is correctly mounted. End brackets secure the station on both sides and keep it from moving from side to side on the DIN rail. Phoenix Contact recommends using CLIPFIX 35-5 end brackets (Order No. 3022276).

  • Page 28: Snapping On The Inline Controller

    First, place the front connector shaft latching in the front snap-on mechanism (detail C1). Then press the top of the connector towards the base until it snaps into the back snap- on mechanism (detail C2). 6959B009 Figure 2-13 Snapping on the Inline controller PHOENIX CONTACT 6959_en_07...

  • Page 29: Connectors To Be Removed If Terminals Are Installed Next To The Inline Controller

    Connectors to be removed if terminals are installed next to the Inline controller • Insert a tool in the base latches of the Inline controller and pull gently upwards (Figure 2-15, detail B). Pull out the Inline controller from the DIN rail (Detail C1, C2). 6959_en_07 PHOENIX CONTACT...

  • Page 30: Removing The Inline Controller

    If you want to use the parameterization settings and projects of the Inline controller to be replaced, insert its parameterization memory into the new Inline controller. • Enter the new MAC address when using the BootP server. PHOENIX CONTACT 6959_en_07...

  • Page 31: Communication Paths

    (S er (S er x x x x x x x x x x x x x x x x x x x x x x x x 6959B004 Figure 2-16 Communication paths: (A) Ethernet, (B) PRG 6959_en_07 PHOENIX CONTACT...

  • Page 32: Ethernet

    6959B005 Figure 2-18 Connecting the Ethernet cable to the Inline controller A crossover twisted-pair cable is required to connect the Inline controller directly to another Inline controller or to a PC. PHOENIX CONTACT 6959_en_07...

  • Page 33: Serial Prg Interface (Mini-Din Socket)

    Figure 2-19 Connecting cable between PC and Inline controller Ordering data: Connecting cable for connecting the Inline controller to a PC (RS-232) for PC Worx, length: 3 m (order designation: COM CAB MINI DIN, Order No. 2400127). 6959_en_07 PHOENIX CONTACT...

  • Page 34: Interbus

    MRESET FAIL RUN / PROG 10/100 RB-T INLINE CONTROL ILC 350 ETH Ord.No.: 27 37 203 RESET RDY / RUN FAIL Local bus Ethernet Remote bus 6959B011 Figure 2-20 Bus configuration with remote bus and local bus PHOENIX CONTACT 6959_en_07...

  • Page 35: Power Supply

    Some electronically controlled power supplies have a fall-back characteristic curve (see Figure 2-21). They are not suitable for operation with capacitive loads. A primary-switched power supply (without fall-back characteristic curve) from the QUINT POWER range (see INTERFACE catalog from Phoenix Contact) is recommended for Inline controller operation. Overload range...

  • Page 36: Connecting The Power Supplies

    The Inline controller is now fully initialized. If the LEDs do not light up or start flashing, there is a serious fault on the Inline controller. In this case, please contact Phoenix Contact. Q 3 Q 4 I 1 0...
  • Page 37 The Inline controller is grounded when it is snapped onto a grounded DIN rail. Functional earth ground is only used to discharge interference. NOTE: The maximum total current flowing through the potential jumpers is 8 A. 6959_en_07 PHOENIX CONTACT...

  • Page 38: Segment Supply/24 V Main Supply

    The rating of the fuse connected upstream must be such that the maximum permissible load current of 2 A is not exceeded. 2.14.7 Jumpers Terminals 1.3 and 2.3 on connector 5 can be jumpered if the communications power and the segment voltage are not to be electrically isolated. PHOENIX CONTACT 6959_en_07...

  • Page 39: Digital Inputs And Outputs

    1 - 4 r. ) r. ) ri e ri e (S e (S e x x x x x x x x x x x x 6959B013 Figure 2-24 Terminal point assignment of connectors 1 to 4 6959_en_07 PHOENIX CONTACT...
  • Page 40 Ground contact for 3-conductor connection Input 11 Input 12 1.5, 2.5 24 V Supply voltage U for 2 and 3-conductor connection 1.6, 2.6 Ground contact for 3-conductor connection The inputs are supplied with 24 V DC from the main supply (U PHOENIX CONTACT 6959_en_07...

  • Page 41: Basic Wiring Of An Output With A Load (L)

    The outputs are supplied with 24 V DC from the segment supply (U The outputs have protection against ground connection interrupt and must be wired accordingly. ILC 350 ... ILC 350 ... 6959C016 Figure 2-25 Basic wiring of an output with a load (L) 6959_en_07 PHOENIX CONTACT...
  • Page 42 ILC 330.../350... PHOENIX CONTACT 6959_en_07...

  • Page 43: The Inline Controller Under Pc Worx

    The time and date for the internal system clock of the Inline controller can be set in the “Device Details” window for the controller in PC Worx. To set the realtime clock, proceed as described in the quick start guide for the PC Worx version used. 6959_en_07 PHOENIX CONTACT...

  • Page 44: Download Changes (Ilc 330 Eth / Ilc 350 Eth / Ilc 350 Eth/M)

    Please note that each realtime violation may result in unexpected consequences in the automation system, as under certain circumstances user tasks are not processed for a short time. Therefore, check the level of risk before disabling this option. PHOENIX CONTACT 6959_en_07...

  • Page 45: Function Blocks For Handling Files On The Parameterization Memory

    80 characters in length. – Up to 64 files can be monitored for modifications. – Maximum number of instances for function blocks: FILE_NOTIFY: 1 instance Others: 8 instances – Minimum scan time for FILE_NOTIFY: 1 second 6959_en_07 PHOENIX CONTACT...

  • Page 46: File_Open

    The variable in which the file name is entered must be a STRING data type. – The file name must not exceed 80 characters in length. – The status of the “Done”, “Error”, and “ErrorID” outputs is maintained until a falling edge is detected at the “Execute” input. PHOENIX CONTACT 6959_en_07...
  • Page 47 Error number of the error that occurred when opening/creating the file: No error information available. The maximum number of files is already open. The file is already open. The file is write-protected or access was denied. File name not specified. 6959_en_07 PHOENIX CONTACT...

  • Page 48: File_Close

    No errors occurred when closing the file. TRUE: An error occurred when closing the file. ErrorID UINT Output Error number of the error that occurred when closing the file: No error information available. Invalid file handle. File could not be closed. PHOENIX CONTACT 6959_en_07...

  • Page 49: File_Read

    Following successful execution, the data is copied to the buffer and the number of characters read is entered at the “LengthRead” output. The number of characters read may be less than “MaxLength” if the end of the file was reached before the number of characters entered was processed. 6959_en_07 PHOENIX CONTACT...
  • Page 50 Error number of the error that occurred when reading the file: No error information available. Invalid file handle. End of file reached. Number of characters to be read is greater than data buffer. No data could be read. PHOENIX CONTACT 6959_en_07...

  • Page 51: File_Write

    If an error occurred during execution, the value at the “Error” output = 1. “ErrorID” indicates the number of the cause of the error. The status of the “Done”, “LengthWritten”, “Error”, and “ErrorID” outputs is maintained until a falling edge is detected at the “Execute” input. 6959_en_07 PHOENIX CONTACT...
  • Page 52 Error number of the error that occurred when writing the file: No error information available. Invalid file handle. No memory is available for writing the data. Number of characters to be written is greater than data buffer. No data could be written. PHOENIX CONTACT 6959_en_07...

  • Page 53: File_Remove

    If an error occurred during execution, the value at the “Error” output = 1. “ErrorID” indicates the number of the cause of the error. The status of the “Done”, “Error”, and “ErrorID” outputs is maintained until a falling edge is detected at the “Execute” input. 6959_en_07 PHOENIX CONTACT...
  • Page 54 Error number of the error that occurred when deleting the file: No error information available. The maximum number of files is already open. File could not be found. The file is open or write-protected or access was denied. File name not specified. File could not be deleted. PHOENIX CONTACT 6959_en_07...

  • Page 55: File_Tell

    FALSE: No errors occurred when determining the position. TRUE: An error occurred when determining the position. ErrorID UINT Output Error number of the error that occurred when determining the position: No error information available. Invalid file handle. 6959_en_07 PHOENIX CONTACT...

  • Page 56: File_Seek

    If an error occurred during execution, the value at the “Error” output = 1. “ErrorID” indicates the number of the cause of the error. The status of the “Done”, “Error”, and “ErrorID” outputs is maintained until a falling edge is detected at the “Execute” input. PHOENIX CONTACT 6959_en_07...
  • Page 57 An error occurred when setting the position. ErrorID UINT Output Error number of the error that occurred when setting the position: No error information available. Invalid file handle. Invalid positioning mode. The position could not be set. 6959_en_07 PHOENIX CONTACT...

  • Page 58: File_Notify

    “Execute” input. If the monitoring condition set is true for a number of files, the block is reset as soon as “Done” changes to 1 following a rising edge at “Execute”. The next file name can then be read from “Name”. PHOENIX CONTACT 6959_en_07...
  • Page 59 Incorrect length of FILENAME (0 or > 80). Incorrect or missing entry for MAXFILES (< 1 or > 64). Incorrect entry for SCANTIME (< 1000 or > 1000000). Too many files in directory (> MAXFILES). Block resources conflict (e.g., insufficient memory) 6959_en_07 PHOENIX CONTACT...
  • Page 60 Because the file is still being written, the size indicated does not match the actual size of the file. PHOENIX CONTACT 6959_en_07...

  • Page 61: Function Blocks For Tcp/Ip Communication

    Communication between two Phoenix Contact controllers (e.g., ILC - RFC, ILC - FC, ILC - ILC) – Communication between a Phoenix Contact controller and any other TCP/IP-capable device (e.g., ILC - PC, ILC - PLC) • Implement all time and connection monitoring in the application program.

  • Page 62: Ip_Connect

    Error codes of the error that occurred. Output Unique ID of the communication connection. If several communication connections are established, the ID parameter can be used to distinguish between them. ID is only valid if the VALID output = TRUE. PHOENIX CONTACT 6959_en_07...
  • Page 63 (reconnect; close socket/open socket) is automatically made. The time can be changed using this parameter. RCVTO=xxxx Receive timeout (in ms) The default value is 5000 ms. If no telegram is received within this time, the IP_URCV block indicates an error. 6959_en_07 PHOENIX CONTACT...

  • Page 64: Ip_Usend

    1460 bytes can be sent using the IP_USEND block. Before data can be sent, a communication connection must be established with the IP_CONNECT block. IP_USEND DONE ERROR R_ID STATUS SD_1 SD_1 7062B022 Figure 3-11 IP_USEND block PHOENIX CONTACT 6959_en_07...
  • Page 65 The number of bytes to be transmitted is entered in the first word of the SD_1 transmit buffer (observe Intel format). This data word is not transmitted. The data is transmitted in the other words. The data is transmitted as a byte stream. There is no Intel/Motorola conversion. 6959_en_07 PHOENIX CONTACT...

  • Page 66: Ip_Urcv

    The data is received in the other words. As long as the EN_R input = TRUE, data can be received. If a data block has been received, the NDR output is set for one data cycle. PHOENIX CONTACT 6959_en_07...

  • Page 67: Error Codes

    The specified IP address is invalid or could not be interpreted correctly. ERR_INVALID_PORT 0042 Port number is not permitted. ERR_NO_FREE_ 0053 All available connections are being used. CONNECTION ERR_FB_EXISTS 0065 Another block instance is already using this connection. 6959_en_07 PHOENIX CONTACT...
  • Page 68 ILC 330.../350... PHOENIX CONTACT 6959_en_07...

  • Page 69: System Variables And Status Information

    INTERBUS Diagnostics Guide (IBS SYS DIAG DSC UM E), Order No. 2747293 Not all system variables that are listed in this user manual are available in firmware versions < 3.95. At least firmware Version 3.95 is required in order to use all system variables. 6959_en_07 PHOENIX CONTACT...

  • Page 70: Status Register For Local Digital Inputs And Outputs

    State of local output OUT1 ONBOARD_OUTPUT_BIT1 BOOL State of local output OUT2 ONBOARD_OUTPUT_BIT2 BOOL State of local output OUT3 ONBOARD_OUTPUT_BIT3 BOOL State of local output OUT4 ONBOARD_OUTPUT_OVERLOAD_0_3 BOOL Overload at at least one of the local outputs PHOENIX CONTACT 6959_en_07...

  • Page 71: Status Register Of A Profinet Controller (Ilc 330 Pn / Ilc 350 Pn)

    RALRM diagnostic block. PNIO_CONFIG_STATUS WORD Configuration status of the PROFINET controller PNIO_CONFIG_STATUS_READY BOOL The variable is set if the PROFINET controller has been initialized correctly. No desired configuration has been loaded by PC Worx yet. 6959_en_07 PHOENIX CONTACT...

  • Page 72: Interbus Registers For The Ilc 350 Pn

    There may be several INTERBUS masters in each PROFINET system. This is why the registers of an INTERBUS master are available directly as process data. The naming conventions for the system variables of local INTERBUS masters (as with the ILC 350 ETH, for example) are also directly applied. PHOENIX CONTACT 6959_en_07...

  • Page 73: Diagnostic Status Register

    Faulty data cycles MASTER_DIAG_STATUS_REG_WARN BOOL Defined warning time exceeded MASTER_DIAG_STATUS_REG_QUAL BOOL Defined error density exceeded MASTER_DIAG_STATUS_REG_SSINFO BOOL A message is present MASTER_DIAG_STATUS_REG_HI BYTE Master diagnostic status register, high byte MASTER_DIAG_STATUS_REG_LOW BYTE Master diagnostic status register, low byte 6959_en_07 PHOENIX CONTACT...

  • Page 74: Diagnostic Parameter Register

    Error location (for a bus error) or error code MASTER_DIAG_PARAM_REG_HI BYTE Diagnostic parameter register, high byte MASTER_DIAG_PARAM_REG_LOW BYTE Diagnostic parameter register, low byte MASTER_DIAG_PARAM_2_REG_HI BYTE Extended diagnostic parameter register, high byte MASTER_DIAG_PARAM_2_REG_LOW BYTE Extended diagnostic parameter register, low byte PHOENIX CONTACT 6959_en_07...

  • Page 75: Iec 61131 Runtime System

    PLC_TASK_AVAILABLE Number of available PLC tasks PLC_TASK_DEFINED Number of tasks used PLC_TASK_1 Record, Information regarding task 1 elements = 17 PLC_TASK_16 Record, Information regarding task 16 elements = 17 6959_en_07 PHOENIX CONTACT...

  • Page 76: Control Processor

    System variables of the battery, realtime clock, and memory card System variable Type Meaning RTC_BATTERY_LOW BOOL The realtime clock battery is low. RTC_DATA_INVALID BOOL The realtime clock data is invalid. FLASHCARD_PRESENT BOOL The CompactFlash card from Phoenix Contact is present. PHOENIX CONTACT 6959_en_07...

  • Page 77: Power Supplies

    The mode selector switch is in the STOP position. KEY_SWITCH_RUN BOOL The mode selector switch is in the RUN position (not supported by the first version of the ILC 350 ETH). KEY_SWITCH_RUN_PROG BOOL The mode selector switch is in the RUN_PROG position. 6959_en_07 PHOENIX CONTACT...

  • Page 78: System Time

    System time Table 4-13 System variables of the system time System variable Type Meaning RTC_HOURS System time (hours) RTC_MINUTES System time (minutes) RTC_SECONDS System time (seconds) RTC_DAY System time (day) RTC_MONTH System time (month) RTC_YEAR System time (year) PHOENIX CONTACT 6959_en_07...

  • Page 79: Status Information Of Each Profinet Device (Ilc 330 Pn / Ilc 350 Pn)

    If this bit is set, the device diagnostics can be read from the PROFINET device using a special function block in an additional implementation step of the basic system if additional information on the error that occurred is required in the control program. 6959_en_07 PHOENIX CONTACT...
  • Page 80 ILC 330.../350... PHOENIX CONTACT 6959_en_07...

  • Page 81: Technical Data And Ordering Data

    Provide external protection for the 24 V area. The power supply unit must be able to supply four times (400%) the nominal current of the external fuse, to ensure that the fuse blows safely in the event of an error. 6959_en_07 PHOENIX CONTACT...
  • Page 82 The current consumption can differ depending on the individual terminal. The permissible number of devices that can be connected therefore depends on the specific station structure. Protection by the external power supply unit Ensure protection of 2 A by means of the external power supply unit. PHOENIX CONTACT 6959_en_07...
  • Page 83 CR check (Hamming distance: 4) Protocol EN 50254 Number of devices in the INTERBUS system Total number of bus devices 512, maximum Number of remote bus devices 254, maximum Number of PCP devices Number of remote bus levels 16, maximum 6959_en_07 PHOENIX CONTACT...

  • Page 84: Inline Local Bus

    PROFINET functions (ILC 330 PN / ILC 350 PN) Device function PROFINET controller Conformance class Performance class Number of PROFINET devices 100, maximum, depending on the update time for inputs and outputs Update time for inputs and outputs 1 ms, minimum PHOENIX CONTACT 6959_en_07...

  • Page 85: Digital Inputs

    Program memory 750 kB, 1 MB, typically 63 K instructions in IL typically 85 K instructions in IL Mass storage 1.5 MB 2 MB Memory for retentive data 64 kB NVRAM 64 kB NVRAM Number of control tasks 6959_en_07 PHOENIX CONTACT...

  • Page 86: Realtime Clock

    This is a Class A item of equipment. When using the equipment in residential areas, it may cause radio interference. In this case, the operator may be required to implement appropriate measures and to pay the resulting costs. PHOENIX CONTACT 6959_en_07...
  • Page 87 Technical data and ordering data Approvals For the latest approvals, please visit phoenixcontact.net/products. 6959_en_07 PHOENIX CONTACT...

  • Page 88: Ordering Data

    Parameterization memory (CompactFlash card) 2 GB CF FLASH 2GB 2701185 Connecting cable for connecting the Inline controller to a PC (RS-232 cable) COM CAB MINI DIN 2400127 QUINT POWER power supplies See current catalog from Phoenix Contact at phoenixcontact.net/products 5.2.3 Software Description Type Order No.

  • Page 89: A Technical Appendix: Service And Maintenance

    Ethernet interface. Such firmware updates are exclusively used for adding new functions that are implemented within the scope of continuous product improvement. No firmware update is required for normal system operation. If required, please contact your Phoenix Contact representative. 6959_en_07 PHOENIX CONTACT...

  • Page 90: Connecting Unshielded Cables

    Push a screwdriver into the actuation shaft of the appropriate terminal point (Figure A-1, A) so that you can insert the wire into the spring opening. Phoenix Contact recommends the SFZ 1-0,6x3,5 screwdriver (Order No. 1204517). • Insert the wire (Figure A-1, B). Remove the screwdriver from the opening. This clamps the wire.

  • Page 91: B Appendix For Document Lists

    Terminal point assignment of connectors 1 to 4 ........39 Figure 2-25: Basic wiring of an output with a load (L) ..........41 Section 3 Figure 3-1: Ensuring realtime ................44 Figure 3-2: FILE_OPEN block ................46 Figure 3-3: FILE_CLOSE block ................48 6959_en_07 PHOENIX CONTACT...
  • Page 92 Figure 3-12: IP_URCV block ...................66 Section 4 Figure 4-1: Error location in the master diagnostic parameter register ....74 Figure 4-2: Error code in the master diagnostic parameter register .......74 Appendix A Figure A-1: Connecting unshielded cables ............90 PHOENIX CONTACT 6959_en_07...

  • Page 93: B 2 List Of Tables

    System variables of the control processor ...........76 Table 4-8: System variable of the control processor (firmware Version 1.1 or later)..............76 Table 4-9: System variables of the battery, realtime clock, and memory card ..76 Table 4-10: System variables of the power supplies ..........77 6959_en_07 PHOENIX CONTACT...
  • Page 94 Table 4-12: System variables of the mode selector switch ........77 Table 4-13: System variables of the system time............78 Table 4-14: Status information variables of a PROFINET device......79 Appendix A Table A-1: Installation error causes and remedies ..........89 PHOENIX CONTACT 6959_en_07...

  • Page 95: B 3 Index

    Fall-back characteristic curve........35 Serial PRG interface............ 33 FTP functionality ............23 Sizing of the power supply .......... 35 Sizing the power supply ..........35 Software requirements ..........9 Hardware requirements..........9 Status indicators ............16 System variables............69 6959_en_07 PHOENIX CONTACT...
  • Page 96 ILC 330.../350... Terminal box ............... 27 Update ..............9, 43 Updating the firmware ..........89 PHOENIX CONTACT 6959_en_07...

This manual is also suitable for:

Ilc 350 series

Table of Contents