Operational configuration of the robot's energy saving function and network wake-up

PROFIenergy can be used to control energy consumption via PROFINET. This is done using commands that allow the load to react to planned and unplanned interruptions.

ROFIenergy is a PROFINET-based data interface for the centralized shutdown of electrical consumers and fully coordinated shutdowns during pauses, regardless of manufacturer or device type. This ensures that only the devices in the process are supplied with the power they actually need. The process saves the majority of the energy, while the PROFINET devices themselves only have a small potential for energy savings.

PROFIenergy commands for the IO controller:

Two instructions are required to control and monitor the PROFIenergy functions.

The PE_START_END instruction allows you to easily activate and deactivate the idle state of a PROFINET device. This can be done via an incoming or outgoing edge. The PE_START_END instruction provides a simple interface for implementing the PROFIenergy commands Start_Pause and End_Pause. With the PE_CMD instruction, you can transmit all PROFIenergy commands, including Start_Pause and End_Pause. Other commands can be used to query the current state or behavior of a PROFINET device during a pause. With the PE_CMD instruction, all PROFIenergy functions can be processed quickly and easily.

FB PE_WOL (FB820)

Since FB PE_WOL is not multi-instance capable, it is called including the instance data block DB 820 IDB_PE_WOL.

This is also used in S7-5.5 version

Using PE_WOL it is possible to address up to 256 PROFINET devices using PROFIenergy. After the block is initialized, the complete I&M data of all devices connected on the PROFINET line are read. These data are then saved in an instance of the data type PE_PLUS "PENERGY" and made available to the user (here FB PE_CTRL).

In addition, check the PROFIenergy functionality of each device. In the following procedure, only address devices that support PROFIenergy standby management (i.e. can be shut down via PROFIenergy during pauses).

This also includes PROFIenergy devices that support the Wake-on-LAN (WOL) mode. For the end-of-suspend command, a so-called "magic packet" is sent to them to stop the suspend.

While the device is in PROFIenergy conversion, i.e. immediately after the start or end of the pause command, the PROFIenergy status of the device is polled cyclically and its data area is updated until the device terminates the conversion.

PE_WOL: Start and stop power saving mode via WakeOnLan:

The "PE_WOL" instruction sends the PROFIenergy commands "Start_Pause" and "End_Pause" to multiple PROFIenergy-capable devices in a PROFINET I/O system.

If the PE device supports the "Wake on LAN" function through a UDP connection, multiple PE devices can be coordinated through commands.

The "PE_WOL" instruction can only be executed on CPUs with an integrated interface. This CPU can load blocks with a size of approximately 400 KB. If this CPU is connected via an Ethernet CP, the block cannot be used in a PROFINET I/O system.

The "PE_WOL" instruction is executed asynchronously.

The "PE_WOL" command only supports devices with numbers less than 256, and devices with numbers greater than this will be ignored.

Definition: Wake on LAN

When using the Wake on LAN function, a disabled device can be reactivated by receiving a special Ethernet packet. To be able to perform this operation, the data processing device must have a network controller that can receive such a packet. This packet (Magic Packet) has a special format. It contains the 15 MAC addresses of the network adapter.

Select device

The device selection is made using a user data block (type: "PE_PLUS") at the PENERGY parameter.

The user data block is a database for handling multiple devices.

Before initializing "PE_WOL", at least the following information must be stored in the user data block:

● PROFINET I/O system ID

● Connection data for "Wake on LAN".

● The port number used for Wake on LAN.

● For each device

– Pause Time

– Switch the device to PE_SLEEP_MODE (EnableSleep)

The "PE_WOL" instruction is initialized using the parameter COM_T. After initialization, the jobs stored in the user data block are processed one after the other.

The following figure illustrates how the PE command "Start_Pause" is transmitted to multiple devices:

(1) Step 1: The “CmdStartPause” bit of the device to be powered off is set to “1” by the user.

(2) Step 2: The diagnostic address of the device to be shut down (CmdStartPause = “1”) is linked to the array.

(3) Step 3: After the job is linked, the bit “CmdStartPause” will be automatically reset.

(4) Step 4: After the jobs are linked, the instruction "PE_WOL" will immediately start processing these jobs.

The PROFIenergy command "CmdStartPause" or "CmdEndPause" can be sent to all devices in the PROFINET IO system that are identified via the START and END parameters.

The status of job processing and any errors that may have occurred during processing are output via the STATUS parameter.

Instructions for using user data blocks

The "PE_WOL" instruction can only be executed via a user data block. The basic procedure is used in this case:

1. Select the command you want to execute on the device:

– START_PAUSE ("CmdStartPause" in the user data block)

– ENDE_PAUSE ("CmdEndPause" in the user data block)

– UPDATE_STATUS ("CmdUpdateStatus" in the user data block)

2. When the update bit ("Update" in the user data block header) is set "Update" = False, at least one CPU cycle should elapse between two updates; otherwise, the edge is no longer guaranteed.

PE command priority:

The commands are processed sequentially without regard to whether the previous command invocations succeeded or completed successfully.

If two commands are set at the same time (such as "CmdEndPause" and "CmdUpdateStatus"), only one of them will be executed.

There are various priorities within a block:

● The command "CmdStartPause" has the highest priority and will always be executed if it is selected.

● The command "CmdEndPause" has the next highest priority.

● The command "CmdUpdateStatus" has the lowest priority.

If these three commands are set at the same time, the unexecuted command will remain in the preselected state. At this time, the next command will be supported at the next rising edge.

FB PE_CTRL (FB 821)

PE_CTRL integrates PE_WOL and enhances it with additional features:

Simplified block parameterization

Can be controlled by process

Suspension of storage plan

Automatic device wake-up

 Unified visualization

Features of this block:

KUKA's PROFINET Device supports PROFIenergy. When using PROFIenergy, it communicates with the higher-level control system via the PROFIenergy protocol.

KUKA uses WorkVisual to configure PROFINET Device

Option card PROFIenergy

The robot controller supports the following PROFIenergy states:

l Rey_To_Opera: The controller is ready.

l Drive bus off: The drive is switched off.

l Hibernate: The control system is in hibernation state and only responds to WakeOnLan packets.

l Brake applied: The brake is applied and will only respond to the next travel command.

If production breaks are short, the Brake braked status can be used to save energy in order to use the status to drive the bus shutdown. However, the Brake braked status can only be activated when the robot controller is in the stopped state.

PROFIenergy can only be implemented in the AUT EXT operating mode, not in the T1 and T2 operating modes. It is not possible to combine PROFIenergy with .

1 Status Ready_To_Operate

2-state drive bus off, hibernate or brake applied

The PROFIenergy states have the following characteristics:

me_to_Pause (toff): Time interval until the control system reaches the state Drive Bus Off, Hibernate or Brake Applied from the state Ready_To_Operate.

Time_min_length_of_stay (toff_min): The time interval when the control system remains in the drive bus off, hibernation or brake applied state. In the drive bus off and hibernation state, all connected devices should

A complete shutdown can be performed before restarting the control system.

Time_to_operate (ton): Time interval until the control system reaches the state Ready_To_Operate from the state Drive Bus Off, Hibernate or Brake Applied.

The default values ​​for the downtime correspond to the minimum values. These values ​​cannot be exceeded.

The downtime can be increased by installing additional application packages. It is recommended to test the required downtime during commissioning.

Activate PROFIenergy  Selected: Use PROFIenergy. Unselected: Do not use PROFIenergy.

Sleep control:

Pause Time: Enter the time the control system is allowed to wait until it reaches the hibernation state. Default value: 50000 ms

Dwell Time Length (Minutes): Enter the minimum time the control system should remain in hibernation mode. Default value: 10000 ms

Operation Time: Enter the time the control system is allowed to wait until it reaches the Ready_To_Operate state. Default value: 60000 m

To shut down the drive bus:

Dwell Time: Enter the time the control system is allowed to wait until the drive bus has reached the off state. Default value: 5000 ms

Dwell Time Length (Minutes): Enter the minimum time the control system should remain in the Drive Bus Off state. Default value: 0 ms

Operation Time: Enter the time the control system is allowed to wait until it reaches the Ready_To_Operate state. Default value: 20000 ms

Brake Brakes:

Dwell Time: Enter the time the control system is allowed to wait until the brake is engaged. Default value: 1000 ms

Dwell Time Length (Minutes): Enter the minimum time the control system will remain in the brake applied state. Default value: 0 ms

Operation Time: Enter the time the control system is allowed to wait until it reaches the Ready_To_Operate state. Default value: 1000 ms