AStudio 6.5.2 Warm Restart Issue

Ask Questions B&R Software & Runtime
1

Currently running AStudio 6.5.2 with a project downloading to an X20CP1684 (CP1684 firmware v1.8.1 and v1.9.0 tried). When the download completes and the ‘Force Reboot’ option is selected, the CP1684 does start a warm restart, but it never fully boots back up. The R/E light on the processor is solid red, DC is yellow, and IF2/ETH is blinking. All other indicators are OFF. After waiting up to 10 minutes minutes, cycling the power on the unit, the unit does boot successfully. Also tried a ‘Consistent Installation’ method on the download and the forced a ‘Warm Restart’ from the menus and still the CP1684 starts the restart, and never fully boots back up. A ‘Warm Restart’ without a download results in a similar response.

Reviewing the logger files/SDM dump, no entries are made in the logger after the warning for the ‘PLC Reset: Warm Restart via communication’ message. Normal messaging shows after the power cycle. During the ‘down’ time, the unit cannot be seen by AStudio and also does not respond to a network ‘ping’ though the IF2/ETH indicator is flashing.

When the system is up and running and a Sys_Resest() call is executed from within the code it does work as expected, the system reboots and recovers correctly.

The download/reboot issue is not seen on our other systems (C30’s).

The problem seemed to start after the upgrade to AStudio 6.5?

Any ideas?

2

Hello,

i would test different Automation Runtime Versions. If you have two PLCs i would check if both behave the same.

Try to reduce you Project Hardware as much as you can to reproduce the issue and get then in contact with local B&R Support, so they can reproduce the issue.

Greetings
Michael

3

Hi @Fritz_Kuehnel ,
You already know our system and it’s clear the behavior of X20CP1684 you have is not normal,
please as Michael said, call our Support in Atlanta or send an email to support.br@us.abb.com for reporting the issue.

Ciao
Valerio

4

Valerio please update us with your findings. Thanks

5

Hi all, I wanted to update that a CASE has been created to troubleshoot this issue with Fritz. I will follow up once we have found a solution.