About nickH

nickH · ‎01-13-2022

Hello Elleshar, the standard way to communicate with the EtherCAT-Master is over the Data Layer interface of the EtherCAT Master App. This can be found at “fieldbuses/ethercat/master/instances/ethercatmaster” in the Data Layer of the ctrlX CORE. You can access the current state of the fieldbus and the Realtime Data there. What would be your specific requirements, so that a connection via a ServiceDependency and thereby the Celix framework would be necessary? Best regards, Nick

nickH · ‎01-12-2022

Hello Elleshar, I'm sorry, I don't understand the issue correctly. Why can't you have the .bfbs file inside of the snap where you want to execute the registerType methode? And which data is used by the rexroth-automationcore snap? Best regards, Nick

nickH · ‎01-10-2022

Ok. Let's check some further points. Did you try your flatbuffer schema and your compile mechanism via shellscript in a Non-Real-Time context first? For example just modify the provider.all-data or the register.node example. If your flatbuffer schema and your compile mechanism works in the Non-Real-Time context, we can rule out some issues. And focus on the special requirements, which come with RT-Bundles. Best regards, Nick

nickH · ‎01-10-2022

Hello mauricej, I tried to reproduce your problem. I build the SDK-Python-Samples (V 1.12.0) with the QEMU-ARM-VM and installed them on my ctrlX CORE and they work like expected. So I don't get the logbook message you mentioned. Did you already update your ctrlX CORE to the new release V1.12? Please check the versions of your system apps: Hint, if you haven't performed the update: Because the partition layout of Ubuntu Core 20 has changed, the version update to V1.12 has to be conducted using the image update mechanism of the ctrlX CORE via micro SD card. In the Collaboration Room (path: ctrlX_CORE_APPS/All-Apps-In-One-File/RM21.11 - V 1.12) you can find the SystemImage and a Guideline on how to perform the update in the Release Notes. Best regards, Nick

nickH · ‎01-10-2022

Hello Elleshar, maybe your bfbsPath is not correct. Try to use getenv("SNAP") to get the correct Path (like you can see in the example and in the post you mentioned): bfbsPath = getenv("SNAP") != nullptr ? getenv("SNAP") : "bfbs"; bfbsPath += "/sampleSchema.bfbs"; I tried out the example sdk-cpp-registernode and it works fine for me. I additionally printed out the bfbsPath which looks like this: /snap/sdk-cpp-registernode/x1/sampleSchema.bfbs Furthermore you should check if you can find your bfbs file at the Path you expect it to be: If not, check your snapcraft.yaml and see if you've got this parts: parts: registernode: plugin: dump source: ./generated/build flatbuffers: plugin: dump source: ./bfbs .... Let me know if this was helpful for you. Best regards, Nick

About nickH

Re: How to add Ethercatclient as a service dependency to a bundle?

Re: registerType return DL_INVALID_VALUE

Re: registerType return DL_INVALID_VALUE

Re: Problem with building ARM-python-snaps

Re: registerType return DL_INVALID_VALUE