About BennyF

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 ... View more

Hi @nickH , seems, we've finally found the issue. However, I think I cannot use the workaround, because I don't have this parameter. And if I try to add this parameter by just typing it, I get the following fault message: I have Ubuntu Core 20 on my ctrlX CORE. Is this a setting of a later version (Core 22)? And will the bug fix be done only for Core 22?   Best regards, Benny ... View more

Hi @nickH , I've read the manual already. That part is clear. Also, there is enough retain memory available, especially as there are no other apps like PLC running. On starting my app, I can even see my memory in "datalayer/retain/chunks". But, it still generates fault messages and doesn't work (in the real CORE). I've done some more testing. I've installed the realtime sample on the CORE. This worked. Then, I've tested my app again, but changed "MemoryType_SharedRetain" to "MemoryType_Shared" for creating the memory. This worked as well! So, it must be something about the "Retain" part! Maybe, it is a license topic? My license looks like this: Or a snapcraft.yaml topic? I've copied the datalayer part from the realtime sample. Is there maybe another plug necessary?   ... View more

Hi @nickH , Yes, it seems that my app starts faster than the data layer. I tested a long delay (30 s) on start of the app. That worked. But in the end, I followed your proposal and implemented retries after 5 seconds, if starting fails. Doing some testing, the retries are not necessary on restart of the app (as the datalayer keeps running). On restart of the CORE or COREvirtual, one retry is necessary. So, that part is fine. But, the SharedRetain memory is only working in the COREvirtual. In the real CORE, it doesn't work. I can start the provider, but on createMemorySync, I always get the result DL_INVALID_HANDLE. The line of code is: result = dataLayer.factory()->createMemorySync(nvram, CtrlXDataLayerRoot + NonVolatileMemoryPath, provider, size, MemoryType_SharedRetain); This line I use after starting the provider, no matter whether the app starts the first time and the shared retain memory has to be created or the app is just restarted and the memory should be there, already. What can be the reason for the DL_INVALID_HANDLE fault in that case? ... View more

Hi @Sgilk , principally, I figured it out. But it doesn't always work. In my application, I: start the data layer create a provider (datalayer.factory()->createProvider(DL_IPC)) start the provider (provider->start()) register the node in the data layer (provider->registerNode(_baseAddress + "**", this)) create/reconnect to the shared retain memory (datalayer.factory()->createMemorySync(owner, ...)) But sometimes, especially on restart of the COREvirtual, I get a DL_CLIENT_NOT_CONNECTED message on starting the provider. As consequence, I have no access to my retain memory. Do I have to wait for something, before I start the provider? ... View more