FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
- About leonberger-m
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About leonberger-m
since
01-23-2023
07-19-2024
leonberger-m
Established Member
34
Posts
1
Likes
2
Solutions
07-19-2024
08:50 AM
Hello, it seems that there was a bug in reading explicit defined nodes within the KVD nodes.json file. It will be fixed with the next release. BR Markus
... View more
07-04-2024
08:04 AM
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.
... View more
07-03-2024
02:20 PM
Hello, we have updated the node-red-contrib-ctrlx-automation to the current available version 1.9.6. After that we have reset the parameters back to "default" to verify what happens. In case the data layer node is not available (e.g. machine is powered off) the DL_INVALID_ADDRESS messages are created quite often. But it seems that the logfile is not flooded completely even if we are using the "default values". So we are going to monitor this issue to verfiy after some hours of runtime that the memory does not increase more and more for the node-red app. The current memory usage is shown in the picture: Regards, Markus
... View more
07-02-2024
08:49 AM
Hello, we have updated two CtrlX Core 3 to the latest version 2.6. After nearly one day the whole memory RAM has been allocated by the Core. For us it seems to be strange since one CtrlX Core only runs in a testbed without much traffic. The memory is not released until the Core is getting restarted. Also a system report has been generated right before restarting the device. BR Markus
... View more
07-01-2024
04:25 PM
Hi @Sgilk , thanks for your quick response. Regarding 1. Within Node-Red we are using some quite simple parameter mapping flows. The data is received from OPC-UA source (by subscription) and forwarded to a KVD node. In all cases the DL_INVALID_ADDRESS appears since the whole data node of the OPC UA source is currently not available (SPS switched off). I also attached the example to the reply. Regarding 2. Yes that's right. The source nodes are currently not available since the OPC-UA server (source) is sometimes not available. Since the IOT CtrlX device runs separately this situation could happen. If I refer to a existing node or the configured OPC-UA server resource is running the error disappears and everything runs fine.
... View more
OK
OK