About Sgilk

Sgilk · ‎07-10-2024

If you are simulating the values, you need to disable the code where the value is written. This is difficult for hardware as it requires excluding the IO from the project. My suggestion would be to add seperate logic and variables for simulation.

nickH · ‎07-08-2024

Hi @EchoHarm0ny I found a issue in the clone-install-sdk.sh. The paths in this script are wrong, there is no "release" folder. Could you try to execute these comands again without "/release" in the path? Wrong path in clone-install-sdk.sh

CodeShepherd · ‎07-05-2024

Consider connecting the ctrlX CORE X7 to a DHCP server at a port that is still active. It should get an IP automatically and be found again in the ctrlX WORKS or the Windows network folder.

BennyF · ‎07-04-2024

Hi @nickH , in that case, it is clear that I have to upgrade to Version 2.6. As this is the prototype for a later series product, this is possible for me. Maybe with the LTS release end of July, the bug is fixed. Thanks for your support! Best regards, Benny

leonberger-m · ‎07-04-2024

Hello @CodeShepherd it really seems that version 1.9.6 fixes the node-red subscpription issue since the memory doesn't increase any more even if the default values for the subscription node timings are used. That's great! But this morning the memory issue is still present since the KVD allocates the whole memory. So only a restart helps to avoid running into the memory issue (yellow led, no response from core). Could you please take a look into the system report we generated yesterday to verify what is going wrong with the key value database? Therefore I opened up another forum topic. Key Value Database (KVD) full memory allocation - Bosch Shared (boschrexroth.com) Thanks and regards.

About Sgilk

Re: Forced Data do not react to Logic

Re: Developing a ctrlX App without App Build Environment

Re: Engineering Port Disabled how to recover

Re: How to use persistent data in c++

Re: DL_INVALID_ADDRESS causes Core Memory Issue (yellow led)