Debugger activation problems in AS6.3.4.31

Ask Questions B&R Software & Runtime
1

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:

obrázok
obrázok486×208 6.46 KB

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.

2

Hi Michal,

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

  1. Go back to AR 6.3.4
  2. Use the workaround

Workaround:

  1. Open Powershell as Administrator
  2. Start Debugger with AS6 AR 6.4.2
  3. Check connection
1..50 | % {

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

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

Start-Sleep -Milliseconds 200

}
  1. 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
  1. Set-up the forwarding
netsh interface portproxy add v4tov6 `
listenaddress=127.0.0.1 listenport=2323 `
connectaddress=::1 connectport=2323
  1. 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
2 Likes
3

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:

obrázok
obrázok552×319 11.9 KB

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

4

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

5

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

6

This should be released in the first week of December.

1 Like