AS 6.7: Debugger

[valerio.manenti]

Hi all,

I tried to debug with AS 6.7 a prj developed with AS 6.5.
First during build I saw new messages “Security Risks”…interesting I never saw them in the past:

I have started my Monitor:

but when I tried to enable the debugger, I got the error below:

interesting what’s that?
Then I checked on the rev history:

so I opened the CPU configuration and I saw new settings:

For default the debugger is disabled, so I enabled that, I got an additional “Security Risk” message:

after transfer, now my debugger works:

I hope with this post we have less panic calls and emails to our Support.

Ciao
Valerio

[kovarj (Jaroslav Kovar)]

Good to know, thanks for sharing

[cesma2000 (M_z_C)]

I don’t want to be off topic but I’ll think about the debugger.
In the past, I have developed with an automation development platform that included a specific type of function (part of the IEC code norm) to allow you to download and run new code line by line. Obviously the source code had been downloaded to the CPU (hw and sw were a proprietary project of the machine tool developer), furthermore the machine type allowed you to break the cycle with a breakpoint and run to test the new code (typically a line structured into stations that works 1 piece at a time).
I have been able to use this way of working little with Autoamtion Studio due to the lack of convenience of downloading the sources into the cpu (biblical compilation times, and other known and non-circumventable situations) and the type of machinery implemented (process plants or mix of process plant and machine tool).
From this perspective, I consider the functionality that interlocks the debugger to be very far-sighted.
The problem with this platform remains its lack of expertise in machine structuring, too often defined with logic that is not adequate to the specifications and functionality that characterize Automation Studio.

Ciao, C.