Brief Analysis of PN Power Management of KUKA C4-8.3 System + Case Study

Publisher:DazzlingSmileLatest update time:2024-05-06 Source: elecfansKeywords:KUKA Reading articles on mobile phones Scan QR code
Read articles on your mobile phone anytime, anywhere

Power management via Industrial Ethernet, Power management via PROFINET

The configuration of the Industrial Ethernet interface with the help of CapCtrl.xml is not a function of PROFIenergy and must be considered separately. Only PROFIenergy or CapCtrl.xml must always be configured. If both are configured at the same time, unexpected effects and malfunctions will occur!


The following signals are available for activating or deactivating various energy-saving modes and for identifying the state of the robot controller.

These functions can only be performed in EXT operating mode, not in T1 or T2.

It is not possible to combine PROFIenergy with power management.

Power management does not refer to PROFIenergy.

Input byte 0

0 AB Drive bus
0 = Turn on the drive bus, condition: HIB = 0 and KS = 0
1 = Turn off the drive bus, condition: HIB = 0 and KS = 0
1 HIB Sleep
0 = No function
1 = Put ​​the controller to sleep, condition: AB = 0 and KS = 0
2 KS Cold Start
0 = No function
1 = Cold start the controller, condition: AB = 0 and HIB =
0

Output Byte 0

0 AB Drive bus
0 = Drive bus is connected
1 = Drive bus is disconnected
1 BBS Ready operating state of the robot controller
0 = robot controller is not yet ready for operation
1 = robot controller is ready for operation

Power management with CabCtrl.xml.

A higher-level PLC can switch the drive bus of the KR C4 on and off via Industrial Ethernet or start the controller from cold restart or in sleep mode. For power management via CabCtrl.xml, an input bit is provided for the control function and an output bit is provided for feedback to the higher-level PLC.

Both bits must be transmitted together via the Industrial Ethernet telegram in the non-safe area (02xxxx).

3e0eaf04-4d86-11ee-a25d-92fbcf53809c.png

The vector address (bit offset) is determined via CabCtr.xml. It must be ensured that the reserved range cannot be used for other purposes.

PROFIsafe protocol structure:

3e2c2cbe-4d86-11ee-a25d-92fbcf53809c.png

1. In the PLC project, up to 2032 safety inputs/outputs are available

2.PROFIsafe is a component of the standard PROFINET telegram.

3. Telegram Structure

a. Bytes 0 to 15 are safety inputs

b. Bytes 16 to 269 are standard input

c. Bytes 270 to 285 are safe output

d. From the 286th byte onwards it is standard output

4. For power management via Industrial Ethernet, the specified input bytes and output bytes are transmitted via the normal input/output range.

Steps:

1. Open the following file on Windows platform:

C:KRCRoboterConfiguserCommonCabCtrl.xml

2. Adjustment

"On" activates power management

3.

(input driver="PNIODriver" bus="PNIO-DEV" bitOffset="376")

(Output driver = "PNIODriver" Bus = "PNIO-DEV" bitOffset = "2536")

As shown, accept the values ​​of PNIODriver and PNIO-DEV

4. Calculate bitOffset (Example)

Bit offsets must always be multiples of eight.

3e515160-4d86-11ee-a25d-92fbcf53809c.png

3e7abcb2-4d86-11ee-a25d-92fbcf53809c.png

5. On the KR C4 controller, inputs 02248 to 02256 should be used.

a. 02248 matches byte offset 31.

b. The first 16 bytes of safety input must be taken into account

c. That is, 16 bytes + 31 bytes = 47 bytes

d. 47 bytes is equivalent to 376 bits

e. In the position offset, enter the value

6. On the KR C4 controller, outputs 02248 to 02256 should be used.

7. 02248 matches byte offset 31

8. 286 bytes are occupied by safety inputs, standard inputs and safety outputs

9. That is, 286 bytes + 31 bytes = 317 bytes

10. 317 Byte corresponds to 2536 Bit.

11. In the position offset, enter the value

3eadb5ea-4d86-11ee-a25d-92fbcf53809c.png

E249-E256ENERGYMM is a robot power control

Because it is a PN network card, it can be awakened!

3ec6c558-4d86-11ee-a25d-92fbcf53809c.png

Special Notes:

The CabCtrl.xml file of the Profinet software version used on the KUKA8.2 system is automatically written to the power management control, but when using the Profinet software 3.3 version CabCtrl.xml on the KUKA8.3 system, you need to activate the power management yourself.

8.3 The original CabCtrl.xml file of the system à

3ee5091e-4d86-11ee-a25d-92fbcf53809c.png

Rewritten 8.3 system CabCtrl.xml fileà

3f052474-4d86-11ee-a25d-92fbcf53809c.png

After changing the CabCtrl.xml file, the power management function can be activated.

Connection via the wiring editor is no longer necessary. The control signals are already intercepted at the protocol level and further processed internally. However, the reserved bit areas should not be used elsewhere. The inputs can be mapped in the KR C4 input range (as a diagnostic monitor, e.g. as a shutdown command for the PLC drive bus), dual configuration of the outputs is not permitted!


Keywords:KUKA Reference address:Brief Analysis of PN Power Management of KUKA C4-8.3 System + Case Study

Previous article:Introduction to Open User Communications TCP, ISO- on- TCP, UDP
Next article:How to draw a SIMATIC S7-1500 PLC function diagram (1)

Recommended ReadingLatest update time:2024-11-16 09:49

KUKA KRC4 robot started up for the first time
1. When starting the machine for the first time, the battery cable (X305) is not connected and needs to be plugged in. X305. Check the wiring of the main unit. After the wiring check is completed, turn on the switch in clockwise direction. The first startup time is relatively long, so wait patientl
[robot]
Latest Embedded Articles
Change More Related Popular Components

EEWorld
subscription
account

EEWorld
service
account

Automotive
development
circle

About Us Customer Service Contact Information Datasheet Sitemap LatestNews


Room 1530, 15th Floor, Building B, No.18 Zhongguancun Street, Haidian District, Beijing, Postal Code: 100190 China Telephone: 008610 8235 0740

Copyright © 2005-2024 EEWORLD.com.cn, Inc. All rights reserved 京ICP证060456号 京ICP备10001474号-1 电信业务审批[2006]字第258号函 京公网安备 11010802033920号