About Sgilk

@rlilla , Might the issue just be a typo? You have unix:/// in your proxy mapping instead of unix:// ... View more

@Tasty_Tech , No. This is a very long time to boot the virtual CORE. The image above still indicates a problem with your hardware acceleration, but also with memory. Can you check your RAM usage when booting the CORE? Also, make sure you have Windows Hypervisor Platform selected for the hardware acceleration of this virtual CORE. ... View more

@stefanAT_ctrlX , I do not know of a great solution within the PLC. One option would be to browse the file structure in another application, like Node-RED, and write the result to a datalayer node which you can reference in the PLC logic. ... View more

Hello @rlilla , I just build the appdata Python sample and also saw that the app configuration directory is not visible upon installation. Once I saved the active configuration to an archive, the directory became visible. You can see the logs from this process below. You should be able to access files using the path structure you specified above, so long as they are read accessible and the client is authorized. As an example, here I read a file from the PLC app data from Node-RED. It seems the active-solution plug is not connecting with the sample app by default. A connect-plug hook that creates a directory in the activeConfiguration fixed this, but I do not have a good answer as to why. I thought these only execute when the plug is connected.   rexroot@VirtualControl-2-6-8:/var/snap/sdk-py-appdata/common/solutions/activeConfiguration/demo$ snap connections sdk-py-appdata Interface Plug Slot Notes content[package-assets] rexroth-deviceadmin:package-assets sdk-py-appdata:package-assets manual content[package-run] rexroth-deviceadmin:package-run sdk-py-appdata:package-run manual content sdk-py-appdata:active-solution - - network-bind sdk-py-appdata:network-bind :network-bind -     ... View more