rossanoparis

Thank you @TimvH It is clear that licences are application based and now thanks to your reply I could understand the meaning of RT systems. The RT called "CODESYS Control for Linux ARM SL" can be deployed on a generic debian based ARM system. The RT called "CODESYS Control for Raspberry Pi MC SL" is more specific for Rasberry HW. Did I understand correctly? Regarding the RT called "CODESYS Virtual Control SL" despite its description it is not clear to me when to use it. It seems that a project created...

Hallo all I would appreciate some clarifications regarding the appropriate runtime system to use. I've been using 'KUNBUS CPUs' and 'CODESYS Control for Raspberry Pi MC SL' for the last 4 years. Recently, there have been some changes in the CODESYS licensing policy. [ https://store.codesys.com/en/howto_applicationbasedlicenses ] My questions are mainly two: 1) If I need to start a new project using 'KUNBUS CPUs', which is the correct runtime system to use. 2) Old projects built using 'CODESYS Control...

Hello @rmaas I assume, you've already verified and tuned everything regarding the EtherCAT network. In my case the problem was due to a wrong core assignement. I suggest to not use the core #0 for your EtherCAT task. The OS realtime patch, which is present on RevPi OS, uses the core #0 for its porpouses and it mustn't be used by any other task which requires realtime and deterministic features. regards Rossano

System information - Controller: KUNBUS RevPi CONNECT-S - OS: Linux buster 32bit 5.10.103-rt62-v7l #1 SMP PREEMPT_RT armv7l GNU/Linux - CODESYS v3.5 SP19 Patch 2 I'm facing a problem related to codesys licences using a procedure based on a bash script. Such bash script detect the presence of new .deb files and install them on system. My automation solution don't allow to be maintained by dedicated personal, thus even the CODESYS runtime SW must be installed using an "automatic" procedure instead...

Thank you @eschwellinger Even tough I think the content of the link you provided is a bit messy. To bind OPCUA server to a specific adapter, I should have had insert the following section. [CmpOPCUA] NetworkAdapter=eth0 But it doesn't work, I had to insert the following section instead to get the right configuration. [CmpOPCUAServer] NetworkAdapter=eth0 Regards Rossano

Thank you @eschwellinger Even tough I think the content of the link you provided is a bit messy. To bind OPCUA server to a specific adapter, I should have inserted the following section. [CmpOPCUA] NetworkAdapter=eth0 But it doesn't work, I had to insert the following section to get the right configuration. [CmpOPCUAServer] NetworkAdapter=eth0 Regards Rossano

Thank you @eschwellinger Even tough I think the content of the link you provided is a bit messy. To bind OPCUA server to a specific adapter, I should have inserted teh following section. [CmpOPCUA] NetworkAdapter=eth0 But it doesn't work, I had to insert the following section to get the right configuration. [CmpOPCUAServer] NetworkAdapter=eth0 Regards Rossano

Thank you @eschwellinger Even tough I think the content of the link you provided is a bit messy. To bing OPCUA server to a specific adapter, I should have inserted teh following section. [CmpOPCUA] NetworkAdapter=eth0 But it doesn't work, I had to insert the following section to get the right configuration. [CmpOPCUAServer] NetworkAdapter=eth0 Regards Rossano