ARwin startup stuck

Ask Questions B&R Software & Runtime
1

One APC910 suddenly refuses to start the ARwin runtime.

It is stuck at the following state:

grafik
grafik372×386 51.6 KB

The console tab is empty.

The log file from C:\BRAutomation\AR010\LOGS contains the following:

Fri Nov 07 12:32:32 2025

Installed AR-Version: 4.34
parseNodeMultiCoreCPU 1
IP is corrected to 192.168.137.1
Windows 10 - 64Bit
Number of processors :1 active core(s):0x1

Bernecker & Rainer
local IP Windows: 192.168.137.1
local IP AR: 192.168.137.2

Internet Connection Sharing is activ.
Use following settings to connect a remote device:
Adapter : Intel(R) Ethernet Connection (2) I219-LM
Connection : Ethernet
DHCP is activ. IP Address may change!
IP Address : 10.43.x.x

Subnet Mask : 255.255.255.0

!!!
Secure Filesystem is not activ. Use this setting only for test enviroment!
!!!

Timeout = 0[sec]
Retrycount = 30

Fri Nov 07 12:33:09 2025
COMMAND_COLDSTART
Socket Create-Error : 10049

Product: VxWin V6.1.00 (6.1.0.10)
Base: V6.1.0.10
RtosWin version: 6.1
Hosting OS: Windows 8 - 64 bit

RtosLib64.dll version: 7.21.6.0 (6.1.0.10)

RtosDrv - Realtime OS Driver (IRQ)
Driver version 9.5.8.0
Inf file version 1.4.2.0
Installer version 0.0.0.1
Required VMF version 1.30.5.0

RtosVnet - Realtime OS Virtual Network Adapter
Driver version 7.10.4.0
Inf file version 1.3.2.0
Installer version 0.0.0.1
Required VMF version 1.30.0.0

RteDevice (= RtosPnp or RtosVnet or RtosDrv) - B&R Interface Card for ARwin #3
Driver version 5.6.3.0
Inf file version 1.6.1.0
Installer version 1.4.4.0
Required VMF version 1.30.0.0

RteDevice (= RtosPnp or RtosVnet or RtosDrv) - Realtime OS Virtual Network Adapter
Driver version ignored
Inf file version ignored
Installer version ignored
Required VMF version 1.30.0.0

RteDevice (= RtosPnp or RtosVnet or RtosDrv) - B&R Interface Card for ARwin
Driver version 5.6.3.0
Inf file version 1.6.1.0
Installer version 1.4.4.0
Required VMF version 1.30.0.0

RteDevice (= RtosPnp or RtosVnet or RtosDrv) - B&R Interface Card for ARwin #2
Driver version 5.6.3.0
Inf file version 1.6.1.0
Installer version 1.4.4.0
Required VMF version 1.30.0.0

RteDevice (= RtosPnp or RtosVnet or RtosDrv) - Realtime OS Driver (IRQ)
Driver version ignored
Inf file version ignored
Installer version ignored
Required VMF version 1.30.5.0

RtosService version: 3.9.3.0 (6.1.0.10)

RtosControl version: 7.9.1.0 (6.1.0.10)

Virtual machine framework version: 1.30.5.0
Virtual machine framework version required by Uploader: 1.30.2.0

Loading VMF… Ok
Start OS - Id:0… Ok
Waiting for Windows ↔ Realtime OS communication subsystems…
MTCX-Version : 1.27
ok

What’s the Socket Create-Error : 10049 ?

2

Hi,

the socket create error 10049 is a Windows error meaning that there’s some trouble with the network address a socket should be bound to.
I’m pretty sure that this is also the reason why the ArWin status window does not show anything, because as I remember there’s also a TCP connection used via the virtual interface to communicate between the realtime service and the ArWin loader / window.

I can’t say what happenend exactly, but it seems that something has changed in the WIndows network and/or firewall settings, especially about the virtual interface?
Please see here some additional information about error 10049 out of the ArWin FAQ in the online help:

Best regards!

3

Thank you for your answer. I tried a few different things, e.g. disable/enable ICS, enable/disable firewall, change the IP adress of the virtual adapter, … but it still is stuck at starting.

However, the socket create error is no longer in the log file and no other error is there. :frowning:

4

We’ve decided to reinstall the Automation Runtime. After that, the runtime started to work again :slight_smile: