Debugger activation problems in AS6.3.4.31

Michal_Malek · November 11, 2025, 9:19am

Hello,
I have a problem with the debugger in AS 6.3.4.31.
Previous issues with the simulation were resolved by properly installing AS (as an administrator) and the security software suite FortiClient (by our IT department).
This setup also helps occasionally run the debugger on the PLC.

However, most of the time, activating the PLC debugger ends with the following dialog:

An even worse situation occurs with the simulation debugger, which cannot be activated at all — it always ends with a timeout:
obrázok

Has anyone experienced similar issues?
According to the security software status, it does not block any processes or ports, and the same applies to the Windows 11 firewall.

Thank you.

simon.buschor · November 11, 2025, 10:13am

Hi Michal,

This is a known issue of AR 6.4.2. You have to options:

Go back to AR 6.3.4
Use the workaround

Workaround:

Open Powershell as Administrator
Start Debugger with AS6 AR 6.4.2
Check connection

1..50 | % {

$c = Get-NetTCPConnection -LocalPort 2323 -ErrorAction SilentlyContinue

if ($c) { $c | ft State,LocalAddress,LocalPort,OwningProcess; break }

Start-Sleep -Milliseconds 200

}

Execute the follow command to start service for Portproxy (copy/paste the two lines in powershell and press enter)

Set-Service iphlpsvc -StartupType Automatic
Start-Service iphlpsvc

Set-up the forwarding

netsh interface portproxy add v4tov6 `
listenaddress=127.0.0.1 listenport=2323 `
connectaddress=::1 connectport=2323

Check if creating the portproxy was successful

netsh interface portproxy show all

From the ticket:

Issue was introduced with AR 6.4
It depends on Windows IPv6 prefix policies, which is the reason why it does not happen on all PCs, Customers, …
GDB Client in Automation Studio does not support IPv6
Issue will be fixed with AR 6.5
Fix: IPv4 mode will be enforced when starting GDB

Michal_Malek · November 11, 2025, 12:23pm

Hi Simon,
I’ve marked the issue as solved, but that’s only true for the PLC. When downgrading to version 6.3.4, the simulation enters a strange state — it appears to be in run mode (both in ARsim and AS), and all programs on the target match those in the project, but it doesn’t actually run. The debugger shows this dialog:

I’ve tried all the usual tricks (rebuild, restart PC, offline commissioning, clear configuration, delete Temp and binary files, etc.), but none of them work.
Do you have any idea how to deal with this?
Thank you
Regards
Michal Malek

Lukas_Kimme · November 20, 2025, 12:45pm

Hi,

just for the record, I ran into the same issue today.

Thanks @Michal_Malek for reporting this here so I know it’s not related to my specific installation. The “strange state” that you observed after downgrading resulted for me without downgrade but with modifications in the PVI Manager properties, cf. B&R Online Help . (specifically after enabling “Use TCP/IP Communication” with port 2323). So the text might just be a common symptom of some invalid configuration.

Since AR6.5 is supposed to fix this: For when is this scheduled?

Best regards

Lukas

Michal_Malek · November 21, 2025, 9:05am

Hi Lukas,
I’m happy too — at least there are two of us experiencing these problems :-). Unfortunately, these aren’t the only ones, and with every step I take in AS6, I’m solving a new issue. Hopefully AR6.5 will fix most of them :-).
Regards
Michal Malek

job.franken · November 21, 2025, 9:19am

This should be released in the first week of December.

Rickard_Odgren · December 17, 2025, 8:04am

I have installed Automation Studio 6.5.0.306, but the same problem persists:

First attempt:

(gdb) target remote 127.0.0.1:2323
127.0.0.1:2323: Connection timed out.
(gdb) set print raw-frame-arguments on
(gdb) set python print-stack full

Then, when I try again, the simulator (ARSim) becomes unresponsive and needs to be restarted.

simon.buschor · December 17, 2025, 9:52am

Hi,
The problem has been fixed with the new Automation Runtime version.
AR = Automation Runtime
AS = Automation Studio
Do you also have the new AR version?

Michal_Malek · December 17, 2025, 12:30pm

Hi Rickard and Simon,

It seems that Rickard is right. I have installed all the 6.5 upgrades, but simulation debugging is still not working and shows the same dialog as it did with version 6.3.4.

Regards
Michal Malek

Rickard_Odgren · December 17, 2025, 12:55pm

Hi again!
It’s working for me now, but I’ve only tested it in the simulator.
I installed Automation Runtime 6.5.1 and, just to be safe, deleted the Temp folder. Then I performed a rebuild (initial install).
Thanks for the advice!
Best regards,
Rickard

Marek_Hluchnik · February 4, 2026, 1:07pm

Hello,
unfortunately we have the same problem(or it at least looks the same) also with recently installed Automation Runtime 6.5.1 and Automation Studio V 6.5.0.306.
Now we are not able to activate Debugger with PLC(X20CP0484_1) at all.
It ended always with this error:

Here are our current versions:

We have also deleted Temp subfolder with the same result.

Debugger works fine with Simulator(ArSim) after removing Temp subfolder.

Some background info: I have reinstalled AS 6.5.0.306 from the official zip file from BR web, before reinstallation we used AS 6.3.something and runtime on X20CP0484_1 ‘6.1.1’. My colleague installed AS 6.5.0.306 on completely new reinstalled W11 (so no previous version of AS was installed on his PC), also with the same result - Debugger ended with error during connection with PLC. Also we don’t have admin rights for developers in our company (installation has been made by our IT team) but we also tried to run AS 6.5.0.306 with admin rights with the same result. We have also tried Powershell’s commands from this thread(though I assume they are useless in Runtime 6.5.1) with the same result.

Any suggestions on how to get it to work?

Thank you in advance.

valerio.manenti · February 4, 2026, 5:38pm

Hi @Marek_Hluchnik ,
Welcome to the community!
It seems R&D has fixed debugger issues on the new Automation Runtime, but unfortunately you still are facing new debugger issue.
In Czech republic we have strong B&R team, I recommend to report new issue to them so they can create a CASE and International Support can link your issue to the one already reported.
In the mean time on our side we will update you if we find possible work around.
I know it’s not the answer you need but I see your case required deep investigation.
Ciao
Valerio

Michal_Malek · February 5, 2026, 12:30pm

Hello,
Finally, together with our B&R support team, I found a solution to the original simulation debugging problem, and the debugger in simulation mode is now working as expected.

In my case, the issue was related to the TCP port 2323 being occupied by the iphlpsvc service. I stopped this service and released the port for simulation purposes.

Hopefully, this can help someone else.

Regards
Michal Malek

valerio.manenti · February 5, 2026, 1:46pm

@Michal_Malek I told you we have strong team In Czech republic.
Thaks
Ciao
Valerio

Marek_Hluchnik · February 5, 2026, 1:53pm

I suppose this is only related to debugger connection with simulator(ArSim) and it is not related to debugger running on PLC.

Topic		Replies	Views
Debug startup of PLC B&R Software & Runtime automation-runtime , plc , sdm	5	185	March 20, 2025
Can't activate Simulation/Watch B&R Software & Runtime arsim	3	65	January 5, 2026
A question about an error related to the runtime B&R Software & Runtime automation-studio , automation-runtime	2	63	November 17, 2025
Description AR-RTK: EXCEPTION Unknown in simulation mode B&R Software & Runtime arsim , automation-studio-6	5	141	September 26, 2025
Error in AS, Automation Runtime is not supported B&R Software & Runtime automation-studio	3	198	May 6, 2025

Debugger activation problems in AS6.3.4.31

From the ticket:

Related topics