About schoeffler

Marc_Smaak · ‎10-26-2022

Sorry by bad, I still had a fixed IP configured in my network range for the Virtula core. After removing the inside out does work so I can connct for the virtual core shell to a local server on my network. Also the Node-Red flow does connect to the public MQTT server so indeed Internet connectivity is in place

CodeShepherd · ‎10-10-2022

In my post above I mentioned the paths where the settings.js file is expected. After installation it is only in the installation path available and can be put to the active configuration to be "replaced". Also as mentioned above: You should copy out an original Settings.js already prepared by us for normal usage (otherwise the snap will/could stop working) from the third path, then add your extensions and load it to e.g. the first path to be persistent.

schoeffler · ‎03-01-2022

Thanks for checking! We were able to solve the problem: We noticed that the problem occurs only with snaps that were build by one specific machine (Development qemu). After a full reinstall of the dotnet SDK 6.0, also snaps from this machine did work. We are almost 100% sure it had something to do with a wrong/incompatible dotnet version. // Unfortunately, I can't tell how we installed the previous "incompatible" dotnet SDK (it was dotnet v5), since we did the reinstall at the very beginning.

schoeffler · ‎08-13-2020

I've got an update on this (I work together with benediktB): We updated everything to RM20.7.1 (ctrlX Works 1.4.1, SDK 1.4.2,....) --> all problems are gone! Thank you.

schoeffler · ‎06-08-2020

Thanks, this explains why it suddenly stopped working on my Firefox browser (always used for ctrlX) but still worked on Chrome (never used before for ctrlX).

About schoeffler

Re: Communication between ctrlX CORE Virtual and external device in same network

Re: Option to replace the Settings.js file from the NodeRed snap

Re: C# SDK Apps return error/exit code 127

Re: C++ datalayer.register.node example at a Virtual Control - node sometimes not availabl...

Re: Error when starting virtual cntrol