ctrlX Virtual log

[Eden]

The virtual ctrlX sometimes switches to No response mode.
How can I access the Virtual ctrlX log to find out why the ctrlX goes to no response?

(using V2.4.1)

[CodeShepherd]

Could you more specify what "no response mode" means?

Please beware the a ctrlX COREvirtual will completely shut down after 4h for license reasons.

What is your architecture? Where is the emulation running? In a virtualization (e.g. virtual box) the emulator of ther ctrlX COREvirtual is not hardware accelerated and so can get quite slow or unresponsive. In that state you cannot access it as it would be the same then a real hardware not longer connected.

[Eden]

No response is the state of the ctrlX. This is not happening after 4 hours. It seems to be happening after installing Flowfuse and trying to use it. When launching the flowfuse app, the state of ctrlX goes to "no response". 
So, do you know why this is happening ? 
In order to understand what goes wrong, I would like to access the logs, but I don't know how. Could you help me with this ? 
Thanks 🙂
 

[CodeShepherd]

Like mentioned above, an unresposive control cannot be accessed. Like a disconnected real hardware would also not be.

I could not reproduce your problem. Could you please answer some of my questions above about your software architecture?

Please keep in mind, that there is no official supported version of the FlowFuse - Node-RED app for ctrlX OS 2.x.

[CodeShepherd]

@Eden Are there any news? Could the issue been solved on your side?