Version 3.0.0.-51-x86-64 (latest) - Manual - Industrial Edge - Industrial Edge - Industrial Edge - Documentation of the Industrial Edge Platform - IEM - Hub - Industrial - Device - IED - Edge - IEH

Title	Description
Firmware name	simatic-ipc-ied-os-3.0.0-51-x86-64
Industrial Edge Device Kit version	1.22.3-1
Docker version	20.10.24
Operating system	Bookworm v12
Release date	March 21, 2025
What's new?	The SIMATIC IPC Industrial Edge Device Operating System (SIMATIC IPC IED-OS) V3.0 includes the following features: Support the following device types: SIMATIC IPC127E, IPC227E, IPC427E, IPC847E, IPC227G, IPC BX-39A, IPC BX-59A SIMATIC IPC AI IED-OS v1.0 (for SIMATIC IPC BX-59A device type), which used to be separate, is merging with this release. IEDK v1.22.3 features with Resource Manager features CPU/NIC allocation & Shared memory RM features for SIMATIC IPC127E, IPC227E, IPC427E, IPC847E, IPC227G, IPC BX-39A, IPC BX-59A device types GPU allocation for SIMATIC IPC BX-59A device type Update Industrial Linux version to v4.1.0 (Debian "bookworm") The transition from binary-based logging to text-based logging has been made.
Known Issues	The following are the known issues: Issue Troubleshooting Connecting an Edge Device to the IEM fails and the "Nginx configuration test failed" error message is displayed during activating the Edge Device phase. Check the DNS server configuration since the error message is DNS server related. The DNS server must be configured properly and reachable for the IEM. In case user data of edge device is corrupted due to unexpected power-outage or forcibly shutdown of edge device. IED-OS filesystem recovery process is going to take place. The process might take 2-3 hours depending on hardware specification of the running device. - Sporadically, the Edge Device might stuck during the boot phase when you perform a firmware update. Switch off the Edge Device and switch the Edge Device on again manually. After switching on the Edge Device, the Edge Device will boot from the previous firmware version. After that, you can again trigger the firmware update process. In case several apps are being installed at the same time, it takes a while to reach the Edge Device UI. Wait for a while to reach the Edge Device UI. During firmware update IED might fail to activate device due to a failure in IE Device Catalog service and might get stucked in Activating state. The device should be rebooted. It is expected that the device would boot from the previous firmware. Firmware update should be triggered again. Depending on the restart policies of the apps, the apps might not restart automatically after the reboot (includes also firmware update since it reboots the device). These apps should be manually started. IED can have two selected Gateway Interfaces when one network interface configured as Gateway Interface from IED UI before onboard and another network interface configured as Gateway Interface during the creation of Edge Device configuration file in IEM. While connecting the IPC Edge Device, Pre-Onboard Network Configurations made from IED UI should be checked in order to perform a flawless connection with New IPC Edge Device Onboarding Network Configurations generated from IEM. After network settings change from static IP to DHCP via Device UI, it takes a while to finalize the setting of new IP. Wait for a while to see the new IP settings. If you set the IPs on the same subnet for network interfaces, one of the connections may be broken. Do not set more than one IP on the same subnet.
Fixed issues	The following bugs have been fixed with SIMATIC IPC IED-OS V3.0: Bug fixes for the IE Runtime.
Other information	You can find more information from Release Notes & Operational Manual