About FooFighter

FooFighter · ‎04-26-2024

Hello akrosis, can you send me the "C:\ProgramData\Rexroth\ctrlX WORKS\virtual-controls\virtual-controls.json" file and also the subsequent batch file of the started control ("C:\ProgramData\Rexroth\ctrlX WORKS\virtual-controls\images\1.20.????\???.user.qcow2.tap.start.bat" ot the "???.user.qcow2port.start.bat". So I can check the start parameters. It seems like a param like the memory is not passed correctly. When starting an emulation without configured memory it reboots endless. As a workaround you can check to edit the name of the control, save, change the name back and save to rewrite the parameters correctly. Regards, Oliver

FooFighter · ‎04-15-2024

Hello gyoussef, Maybe your WMI is corrupt, then this may be helpful: Run in an elevated cmd the command window: winmgmt /salvagerepository Then execute the command: winmgmt /verifyrepository to see if it now comes back as consistent. Regards Oliver

FooFighter · ‎03-20-2024

Hello Johanna, The second screenshot displays that the intel haxm service is running and the hypervisor platform is enabled. This is only the case when the platform was enabled without a reboot. There can be only one kind of hypervisor active on a machine. So when you reboot, the haxm service will no more running and your virtual control shall be accelerated by WHPX. Regards, Oliver

FooFighter · ‎02-05-2024

Hello, can you please create a systemreport in ctrlX WORKS and send it to me? Meanwhile you can start the engineering by command line arg --disablewebserver, this means you are not able to automate plc engineering but you should be able to work interactively. Regards, Oliver

FooFighter · ‎11-24-2023

Hello, we recommend using the "Windows Hypervisor Platform" for Hardware Acceleration, because Intel does not support the HAXM Feature any more. To turn on the "Windows Hypervisor Platform" run the command "optionalfeatures" in a cmd window and select the option "Windows Hypervisor Platform". Restart of the PC is needed. The above mentioned error about the socket binding may be caused by a still running qemu process. To be shure not process is still running, try to stop all "qemu-system-x86_64.exe" (task manager /details). Then try to restart the virtual control. Regards, Oliver

About FooFighter

Re: Problem creating a virtual core

Re: invalid class

Re: CORE Virtual hardware acceleration error

Re: API webserver prrblem

Re: Virtual Core could not start correctly.