AS6 : Best way to run AS Debugger and Linkmanager on MacBook

Hello

I am working also with a MacBook Pro (M4Pro) and Parallels VM Windows 11.

Currently I have following issues:

Automation Studio Debugger:
With AR6.5.1 and AS6.5.0.306 the debugger always reports the error as described here: Debugger activation problems in AS6.3.4.31 - #3 by Michal_Malek
Is someone of you able to use the debugger on Mac?

LinkManager:
Until now we did not find a way to run LinkManager on an arm based system. This seems to be a known Issue and there are some post in the internet when searching for Secomea and arm64. Although there is a LinkManager Mobile with very basic functionality that would run on MacOs https://kb.secomea.com/docs/linkmanager-mobile-1, we are currently using a Windows x86 VM in the cloud to connect to our physical machine to have the full functionality. Any one found a better solution?

Any input is appreciated :slight_smile:


Split by moderator from original topic

Question to AI: ”Which is the best way to run B&R link manager on MacBook?”

Answer:
Running B&R LinkManager (Secomea) on a MacBook depends primarily on your processor (Intel vs. Apple Silicon M-series), as the software is natively designed for Windows.

1. For Apple Silicon Macs (M1, M2, M3, M4)

The full LinkManager client does not currently run natively on ARM-based macOS or within standard ARM Windows virtual machines due to driver incompatibilities.

  • LinkManager Mobile: This is the most compatible native option for Mac. It provides basic web-based functionality that allows you to access web services or VNC on the remote PLC directly through a browser without installing drivers.

  • Cloud-Based Windows x86 VM: Some users connect to a physical machine or a full x86 Windows VM hosted in the cloud to gain full LinkManager functionality while working on a Mac.

  • Virtualization Limitations: While Parallels Desktop can run Windows 11 on Apple Silicon, users often report that the specific virtual network drivers required by LinkManager fail to initialize on the ARM architecture.

2. For Intel-Based Macs

If you have an older Intel Mac, you have more robust options:

  • Virtual Machines: Use Parallels Desktop or VMware Fusion to run a standard Windows 10/11 environment. This allows you to install the LinkManager Windows client directly.

  • Boot Camp: For the most stable connection, use the Apple Boot Camp Assistant to boot natively into Windows. This bypasses virtualization layers that can sometimes interfere with industrial VPN drivers.

3. Alternative: Browser-Based Diagnostics

  • B&R System Diagnostics Manager (SDM): If you only need to check hardware status or runtime settings, you can access the System Diagnostics Manager using any standard web browser on macOS, provided you have a TCP/IP connection to the PLC.

Ciao
Valerio

Regarding the debugger, second question to AI:
How can we use the Automation Studio debugger on MacBook?

Answer:
Running B&R LinkManager (Secomea) on a MacBook depends primarily on your processor (Intel vs. Apple Silicon M-series), as the software is natively designed for Windows.

1. For Apple Silicon Macs (M1, M2, M3, M4)

The full LinkManager client does not currently run natively on ARM-based macOS or within standard ARM Windows virtual machines due to driver incompatibilities.

  • LinkManager Mobile: This is the most compatible native option for Mac. It provides basic web-based functionality that allows you to access web services or VNC on the remote PLC directly through a browser without installing drivers.

  • Cloud-Based Windows x86 VM: Some users connect to a physical machine or a full x86 Windows VM hosted in the cloud to gain full LinkManager functionality while working on a Mac.

  • Virtualization Limitations: While Parallels Desktop can run Windows 11 on Apple Silicon, users often report that the specific virtual network drivers required by LinkManager fail to initialize on the ARM architecture.

2. For Intel-Based Macs

If you have an older Intel Mac, you have more robust options:

  • Virtual Machines: Use Parallels Desktop or VMware Fusion to run a standard Windows 10/11 environment. This allows you to install the LinkManager Windows client directly.

  • Boot Camp: For the most stable connection, use the Apple Boot Camp Assistant to boot natively into Windows. This bypasses virtualization layers that can sometimes interfere with industrial VPN drivers.

3. Alternative: Browser-Based Diagnostics

  • B&R System Diagnostics Manager (SDM): If you only need to check hardware status or runtime settings, you can access the System Diagnostics Manager using any standard web browser on macOS, provided you have a TCP/IP connection to the PLC.

so just for curiosity, Have you tried to debug your code with AS code?
Ciao
Valerio

Hello Valerio

Yes I have tried to use AS Code. When I start the debugger I always get following error.

image

Hi @Jonas_Keller ,
I know we have a partner in US where all their engineers use Mac, I’ll ping them with the hope we have some tips.
Ciao
Valerio

2 Likes

question taken by local support.

Hi @Jonas_Keller ,
I’m waiting an answer from them, in the mean time regarding the second point AS Code and Mac I see we have an update at this post:

So for I see it’s possible to run AS Code and Mac
I hope that post helps your case
Ciao
Valerio

Hello @valerio.manenti

Thank you for your inputs.

With AS Code I still have the same connection issues even when I follow the steps from the other post. But I don’t use AS Code that often so it is not a blocker.
Regarding the debugger in AS we are in contact with the local B&R support. So maybe we will find there a solution. I will update the post when I have new findings.

Greetings Jonas

2 Likes

Hello

Did anyone find a solution to run the Automation Studio Debugger under AR 6.5.1?

Until AR6.3.4 debugging was possible on my system in parallels. When I look at the involved ports then its like:

netstat -ano | findstr 2323
TCP 127.0.0.1:2323 127.0.0.1:64035 HERGESTELLT 516 → AR000.exe
TCP 127.0.0.1:64035 127.0.0.1:2323 HERGESTELLT 12688 → gdb.exe

With AR 6.5.1 gdb.exe and gdbserver.exe should run. But it seems that gdbserver.exe crashes immediately and so debugging is not possible.

If someone found a workaround I would love to hear.

Greetings Jonas