In small and medium-sized automation systems, compact controllers often need to simultaneously undertake logical operations, fieldbus management, and remote communication tasks. The ILC 1X1 series Inline controllers from Phoenix Contact (including ILC 131 ETH, ILC 151 ETH, ILC 171 ETH 2TX, ILC 191 ETH 2TX, and their XC wide temperature models) are designed specifically for this purpose. They integrate Ethernet, INTERBUS local bus, digital I/O, and optional PROFINET device functions, enabling flexible construction of distributed control solutions. However, facing the complex electromagnetic environment, power fluctuations, and network configuration on site, engineers often encounter problems such as inability to start, communication interruption, or parameter loss. This article is based on the official technical manual, systematically reviewing the hardware characteristics, installation specifications, common fault phenomena, and troubleshooting methods of this series of controllers, and providing practical suggestions for SD card usage, IP allocation, and firmware upgrades.
Model Differences and Selection Points
The ILC 1X1 series includes multiple models, with the main differences being memory capacity, number of Ethernet ports, and environmental adaptability.
Model Program Memory Data Memory Ethernet Port Supports INTERBUS Remote Bus Environment Temperature
ILC 131 ETH 192 kbyte 192 kbyte 1 No -25...+55 ℃
ILC 151 ETH 256 kbyte 256 kbyte 1 is (up to 4 levels) -25...+55 ℃
ILC 171 ETH 2TX 512 kbyte 512 kbyte 2 (internal exchange) is -25...+55 ℃
ILC 191 ETH 2TX 1 Mbyte 1 Mbyte 2 (internal exchange) is -25...+55 ℃
ILC 131 ETH/XC 192 kbyte 192 kbyte 1 No -40...+60 ℃ (derating)
ILC 151 ETH/XC 256 kbyte 256 kbyte 1 is -40...+60 ℃ (derating)
Key selection points:
When dual port redundancy or ring network (MRP) is required, ILC 171/191 ETH 2TX must be selected.
When involving the INTERBUS remote bus (beyond the local station), the ILC 131 series is not available.
Select XC model for extremely cold or high temperature environments (such as outdoor cabinets and desert areas), and note that it needs to be downgraded for use above 24.5V.
Core points of installation and wiring
2.1 DIN rail and grounding
The controller adopts IP20 protection and must be installed in a closed control cabinet (recommended IP54 or above). Using 35mm standard DIN rails, end clamps (such as CLIPFIX 35-5) must be installed at both ends. The guide rail must be grounded, and the FE spring at the bottom of the controller must be in reliable contact with the guide rail. The manual emphasizes that when installing and disassembling the controller, the power must be turned off, and the adjacent right side Inline terminal must be removed first, otherwise it will damage the hook and jumper contacts.
2.2 Power selection and wiring
ILC 1X1 requires three 24V power supplies:
ULLC: Provides power for controller logic and local bus communication, with a typical current of 210 mA and a maximum of 870 mA. It is necessary to use a power supply without a return characteristic curve (such as the QUINT POWER series) because the controller is a capacitive load when powered on, and a return type power supply may mistakenly trigger overload protection.
UM (Main Power Supply): Provides power to local inputs and some bus devices, with a maximum of 8 A.
US (segment power supply): Provides local output power, with a maximum of 8 A.
Common on-site error: Using a regular switch power supply causes the controller to fail to start after power on, and the FR and RDY LEDs do not flash. The solution is to replace it with a power supply without folding characteristics, or connect a larger capacitor in parallel (not recommended in the manual, it is best to directly replace the power supply).
Fuse configuration: Each power supply must be equipped with an external fuse (8 A recommended for UM/US and 2 A recommended for UICC), as the controller only has polarity reversal and surge protection internally, without short circuit protection.
2.3 Digital I/O wiring
The controller comes with 8 inputs (I1~I8) and 4 outputs (Q1~Q4). The input is 24V DC, in compliance with EN 61131-2 type 1, with a switch threshold low level<5V and high level>15V. The output is 0.5 A per channel, with a total current of 2 A. Please note that the output has ground interruption protection, but inductive loads (relays, solenoid valves) must be connected in parallel with freewheeling diodes to avoid damaging the output stage. The manual states that the switching frequency under nominal inductive load should not exceed 0.5 Hz, otherwise the output may be damaged.

Startup and IP address allocation
3.1 Factory state and first power on
The controller does not have a preset IP address when it leaves the factory, and the internal parameter memory is empty. After the first power on, the PWR LED (UL/UM/US) should light up, and after about 10 seconds, the FR (green) and RDY (green) LEDs start flashing, indicating that the IEC 61131 system has been initialized but no program is running.
3.2 IP Address Allocation Method
There are three ways:
BootP server (default mode): After the controller is powered on, it sends a BootP request broadcast. Activate the BootP server in PC Worx Express, enter the MAC address of the controller (printed on the side of the device, format 00.A0.45. xx. xx. xx) and assign an IP address. Once successful, the IP address will be permanently stored in the internal parameter memory.
DCP protocol (firmware ≥ 4.20 required): Set the IP and PROFINET device name directly in the device details window of PC Worx.
Serial port (only for IP allocation, non programmable): Use a COM CAB MINI DIN cable to connect the PC serial port to the controller PRG port (mini DIN), and set the IP through Diag+software.
Common malfunction: BootP allocation failure, message window shows no response. Check if the PC network card and controller are in the same physical network segment (not necessarily the same IP segment, but BootP is broadcasting and requires the switch to allow broadcasting), and also confirm that the MAC address input is correct.
3.3 Reset the controller through the mode switch
If you forget your IP or need to completely clear the program and retain data, you can use the MRESET function: turn the mode switch from STOP to MRESET position for 3 seconds, then release it (<3 seconds), and then turn it to MRESET position for 3 seconds. After completion, the controller returns to its factory state, the IP address is cleared, and the program is lost.
Hide reset button: Press and hold the reset button with a pointed object while turning off the power and then turning it back on. Wait for the FF (yellow) LED to flash before releasing it. After about 1 minute, FR and RDY will flash, indicating that it has been restored to the factory.
LED indicator light fault diagnosis
The ILC 1X1 provides rich status LEDs for quick identification of fault sources.
Common reasons and countermeasures for the meaning of LED color status
UL green out 24V UILC missing check power terminals 1.1/1.3, whether the voltage is 19.2~30V
UM green out 24V main power supply missing inspection terminal 2.1/2.2
Check for missing terminals 1.1/2.3 or external fuses in the 24V segment of the US green out power supply
FR green flashing system ready when running, stopped state with no program running or program stopped
FR green constant light program is running normally
FF yellow constant bright runtime error program includes zero division, array out of bounds, etc., PLC error variables need to be checked
RDY green flashing INTERBUS master station ready but not running waiting to start
FAIL Red Always On INTERBUS Bus Fault Remote bus disconnection, missing terminal module or hardware failure
The BSA yellow constant bright bus segment has been closed, and a remote bus branch has been disconnected
PF yellow constant bright peripheral device failure, a certain I/O module failure or parameterization error
E yellow constant light output short circuit/overload check Q1~Q4 load, eliminate short circuit
BF (PROFINET) is always red and there is no PROFINET connection. The controller has not established communication with the PROFINET controller
BF is flashing red and establishing a connection is normal
SF (PROFINET) is always red and on. PROFINET diagnostic information exists. View controller diagnostic data
On site case: A user reported that the controller RUN light is not on, FR is flashing, and FF is constantly on. Through PC Worx online reading of errors, it was found that the runtime overflow was caused by a short cycle time in the task configuration. Restore after modifying the task cycle.
SD card (parametric memory) usage and troubleshooting
All ILC 1X1 supports inserting SD cards (Phoenix Contact specific, pre formatted). SD cards can be used as main storage or additional storage.
5.1 Main Memory Mode
When the SD card is inserted before the controller is powered on and the PC Worx is set to "Preferable use external SD card as main memory" (default), all project data and IP configurations are stored on the SD card, and the internal flash memory is erased. When running in this mode, the SD card cannot be unplugged, otherwise it will cause the program to stop and report an error (FAIL LED on).
Attention: In the explosion-proof area (Zone 2), SD cards can only be used as main storage and are strictly prohibited from being plugged in or unplugged with power on.
5.2 Additional Memory Mode
If the SD card is inserted after the controller is started, or if it is set to "Use external SD card as additional memory" in PC Worx, the SD card is only used to store user files (such as logs and recipes), and the program still runs in internal flash memory. At this time, it is possible to insert/unplug during operation, but it is necessary to avoid unplugging during read and write operations.
Common error: After formatting the SD card to FAT32 on the PC and reinserting it, the controller cannot recognize it. Phoenix Contact's original pre formatted SD card (order number 2988146 or 2988162) must be used and cannot be formatted by oneself.
5.3 SD card as log storage
By accessing the controller through FTP (with FTP server enabled), folders (such as Logfile) can be created in the/sddisk directory. Then use the function blocks such as FILE. OPEN and FILE. WRITE in PC Worx to write runtime data to the SD card. Pay attention to the lifespan of write cycles (typically 100000 per sector) and avoid frequent writing of small data.
5.4 FTP Access Issues
Phenomenon: Unable to view SD card contents through FTP. Reason: The FTP server is not activated or access is restricted. Solution:
Enable FTP Folder View in Internet Explorer.
Control the FTP server through the CPU_Set_ValueRequest service in PC Worx (Var ID 0172hex, value 0001hex activated, 0000hex disabled).
The default username is anonymous, and the password is empty. To restrict access, you can use CPU_Set_ValueRequest() (Var ID 019Ahex) to set the username and password (in ASCII hexadecimal format).

Troubleshooting of PROFINET device functionality
ILC 1X1 can be used as a PROFINET device (slave) to access higher-level controllers (such as RFC 470 PN 3TX). The configuration steps are as follows:
Assign an IP address (such as 192.168.161.155) to ILC.
In PC Worx, open the controller "Extended Settings" ->select "PROFINET device activated" ->send and restart the controller.
Use the "Read PROFINET" function in the main station project to scan the network and read the device names and process data of ILC.
Common faults:
BF LED constantly on: No connection established with PROFINET controller. Check the switch and network cable to ensure that the device names configured in the main station are consistent with the names set in ILC (which can be modified through DCP).
SF LED constantly on: There is a diagnostic event (such as a fault in an input module). Read diagnostic data of ILC (via PND_S1 system variable).
Process data not updated: Confirm that the length of the process data configured by the main station matches the actual length of the ILC. When ILC is used as a PROFINET device, its IN/OUT process data length can be viewed in the "Process Data" tab.
Special cases of power and ground faults
7.1 All LEDs do not light up after power on
Reason: The external fuse is blown, the power supply is not connected, or the polarity is reversed. There is a polarity reversal protection diode inside the controller, but reversing it can cause a large current to flow through the diode and burn out the external fuse. Correct method: Measure the voltage at terminals 1.1 (+) and 1.3 (-), which should be between 19.2 and 30V.
7.2 FR and RDY do not flicker
Possible reasons: insufficient voltage of the UICC, damage to the internal firmware of the controller, or hardware malfunction. After attempting to power off, press and hold the reset button before powering on. If there is still no improvement, it is necessary to return to the factory for repair.
7.3 Output no voltage but E LED does not light up
Check if the US segment power supply is connected (terminals 1.1 and 2.3). If the US is normal, measure the voltage at the output point to SGND. If the load is inductive, confirm that the freewheeling diode has been installed.
Maintenance and firmware upgrade
8.1 Firmware Update
Firmware updates are only used to add new features and are not necessary. Update method: Use the dedicated tool provided by Phoenix Contact via Ethernet (see application instructions "Firmware update ILC 1.../3..."). Be sure to back up the project before updating.
Attention: After updating the firmware, all parameters and programs will be lost (unless stored in the main memory of the SD card). Save the project file before updating.
8.2 Real time clock battery
The standard model (non XC) has a built-in real-time clock, which is held by a capacitor for about 10 days after power failure (it takes 24 hours to fully charge). If time is lost after a long-term power outage, it needs to be resynchronized (which can be done through the SNTP function block). The XC model has no clock holding capacitor and must be synchronized through SNTP or PLC every time it is powered on.
8.3 Environment and Rating Reduction
When the ambient temperature exceeds 55 ℃, ILC 131/151/171/191 needs to be downgraded for use (see manual downgrade curve). The XC model is available within the temperature range of -40 ℃ to+60 ℃, but requires an additional derating (multiplied by a factor of 1.25) when the voltage exceeds 24.5V.
Typical troubleshooting process (pocket steps)
Visual inspection of LED: PWR LED (UL/UM/US) must be fully illuminated; FR should flash or stay on constantly; If FF is constantly on, there is an error when connecting PC Worx to read the runtime.
Check the power supply: Use a multimeter to measure the voltage and ripple (not exceeding ± 5%) of the UICC, UM, and US terminals.
Verify IP communication: Use the ping command to test the controller IP. If there is no response, reassign the IP through the serial port or DCP.
View diagnostic system variables: Read MASTER-DIAGVNet REG and MASTER-DIAG-PARM-REG in the application to obtain the location of the INTERBUS bus error.
Check SD card: If the program is lost, confirm whether the SD card is loose or damaged. Remove the SD card and restart to see if it has been restored to the internal flash program.
Restore factory settings: Use MRRESET or hide reset button to clear incorrect configurations.
Upgrade replacement and spare parts suggestions
When replacing the old ILC 1X1 controller (if the hardware version is lower than 004.00) with a new one, please note:
The firmware version of the new controller is higher, and the project may need to be recompiled (execute 'Rebuild all' in PC Worx).
If using an SD card as the main memory, simply insert the new controller (provided that the model is compatible, ILC 131 cannot be replaced with the 171 project).
After replacement, the MAC address changes, and the MAC address mapping needs to be updated in the BootP server.
Recommended spare parts: SD card (SD FLASH 2GB, 2988162), serial cable (COM CAB MINI DIN, 2400127), end clamp (CLIPFIX 35-53022276).
