Operating system

The PLCnext Technology control platform is based on a Linux® operating system with the OSADL real-time patch. Linux® is a highly reliable, open source operating system suitable for applications that require a high stability. A wide range of open source software is available for the Linux® operating system, which is supported by a large community of users and developers.

You can also use this open software, software blocks, and technologies for your PLC applications (e.g., SQL server). PLCnext Technology uses the Linux operating system and extends it by the functions of a PLC such as the cyclic processing of tasks and cycle-consistent data exchange. Core changes or extensions are not possible. To add functions to the system, the user must compile and, if necessary, execute installations with root rights.

The operating system features the following components and services:

• Firewall (can be configured via the Web-based Management)
• OpenVPN
• IPsec strongSwan
• SSH/SFTP
• NTP (Network Time Protocol)
• DNS

Text editors

Nano and Vim are installed on the controller as text editors. When you are connected to the controller via the SSH console, you can call the desired editor via the command line. To open a file with the desired editor, enter nano <file name> or vim <file name>.

Nano

The Nano text editor is easy to use and is therefore recommended for less experienced users.

Find an introduction and documentation of features at the GNU nano website. 

Vim

The Vim text editor has an extended range of functions and is a popular editor in the Linux® environment.

Find an introduction and documentation of features at the Vim website.

Linux scripts of the PLCnext Technology firmware

Firmware update

Beginning with firmware version 2019.0 LTS, you can update the firmware conveniently via the Web-based Management of your controller.

For older firmware versions, you can start the firmware update via the sudo update-plcnext shell script, which you will find in the file system of the controller.

• Download and unzip the firmware *.zip file from the download area of your controller (see Tool downloads).
• For older firmware, run the *.exe setup file to extract the *.raucb update file. Newer firmware contains already the *.raucb update file.
• Open an SFTP client software (e.g., WinSCP).
• Log in to the PLCnext Control as an administrator
  (default access data is User name: admin; Password: printed on the controllers' housing).
• Copy the *.raucb update file to the /opt/plcnext directory (this is the home directory of the Linux user “admin”).
• Open the shell using a command line tool (e.g., PuTTY or Tera Term).
• Log in to the PLCnext Control as administrator.
• Issue the update command; the name of the update script is the same for every controller:sudo update-plcnext.
  • The script is available in the directory under /usr/sbin/.
  • Under /usr/sbin/, you will also find symbolic links with the respective product designation in the name, e.g., sudo update-axcf2152.

The script executes the following operations:

1. Stopping the PLCnext Technology process.
2. Performing the firmware update.
3. Rebooting the system and deleting the firmware container.

The same goes for downgrading to a former firmware version.

Known issue: 

Reset to default setting type 1 and type 2

A distinction is made between two types of default settings:

• Type 1: 
  All user-specific data is deleted (settings, programs, users, etc.). The current PLCnext Technology firmware remains unchanged.
  The following directories are cleared:
  • /media/rfs/rw/upperdir
  • /media/rfs/rw/work 
  The directories that are used for containers are also cleared from firmware version 2023.0 LTS:  
  • /media/rfs/rw/var
  • /media/rfs/rw/data
• Type 2:
  In addition to deleting the user-specific data (type 1), the firmware of the controller is reset to delivery state.

You can reset your controller to default settings via the device-specific operating elements (e.g., reset button or operating display). For additional information, please refer to the corresponding user manual.

Another option is to reset the controller using a shell script. The script is available in the controller's file system. The name of the factory reset script is the same for every controller:  sudo recover-plcnext 

You will find the script under /usr/sbin/. When calling the script, specify the desired reset type, e.g.,  sudo recover-plcnext 1 for type 1 default settings.
Under /usr/sbin/, you will also find symbolic links with the respective product designation in the name, e.g., 
recover-axcf2152 1 for type 1 default settings of a PLCnext Control AXC F 2152.

The type 1 default settings can also be restored via the Cockpit editor in PLCnext Engineer and from firmware version 2023.0 LTS via the WBM cockpit.

So in this case not necessarily all user files are deleted and a reset to default setting type 2 does not necessarily restore the controller to factory default state. 

All licenses, and especially licenses that are bound to the device, are retained.

Controlling the firmware

The plcnext script in the /etc/init.d directory controls the firmware.

You can control the firmware with the following commands: