Activity for ajadhav
-
ajadhav modified a comment on discussion Runtime 🇬🇧
The issue of crashing of CODESYS Control on CM4s is resolved in CODESYS Control for Raspberry Pi MC SL v4.8.0.0.
-
The issue of crashing of CODESYS Control for Raspberry Pi on CM4s is resolved in CODESYS Control for Raspberry Pi MC SL v4.8.0.0.
-
Hi Edwin, Thank you for the initial suggestion.I am currently testing with CODESYS Control for Raspberry Pi MC SL v4.8.0.0 and it would take couple of days to check if the issue exists with latest runtime. I have an question with SP19 In SP19, there is a bug fix CDS-81506 - CODESYS Control SysFile system file access vulnerability In the Revolution Pi Library for Codesys, a file r/w access under following folder /etc/revpi/ is required. The IO driver basically writes a configuration specific to Revolution...
-
Hello Codesys Support Team, Does the CODESYS Control for Raspberry Pi MC SL v4.6.0.0 or higher support Compute Module 4s (CM4s)? The datasheet of CODESYS Control for Raspberry Pi MC SL mentions support for Compute module 3 and Compute module 4 but not Compute Module CM4s. We have Revolution Pi devices (Connect S / with CM4s) running CODESYS Control for Raspberry Pi MC SL where the Control Runtime crashes after some days.The issue has been raised my multiple users on this forum.The same application...
-
I also had noticed the same problem.Infact the file access with SysFileOpen was working till CODESYS Control for Raspberry Pi MC SL V 4.6.0.0 Manual editing of user.cfg file wouldnt be a desirable method especially for Codesys IO libary packages which need some specific file access in some working directory in linux.
-
Codesys fails to Restore a license from the explicitly created license update file CMLicenseNew.WibuCmRaU The license update file connect_57869_C83EA7021F8F.WibuCmRaU could not be restored on RevPi Connect Feat Codesys device (100337 57869 1.0). https://revolutionpi.com/revpi-connect-codesys/ License restore with following combinations were tried out: CODESYS Control for Raspberry Pi MC SL 4.0.1.0 with CODESYS Runtime Toolkit V3.5.16.40 CODESYS Control for Raspberry Pi MC SL 4.2.0.0 with CODESYS...
-
Codesys fails to Restore a license from the explicitly created license update file CMLicenseNew.WibuCmRaU The license update file connect_57869_C83EA7021F8F.WibuCmRaU could not be restored on RevPi Connect Feat Codesys device (100337 57869 1.0). https://revolutionpi.com/revpi-connect-codesys/ License restore with following combinations were tried out: CODESYS Control for Raspberry Pi MC SL 4.0.1.0 with CODESYS Runtime Toolkit V3.5.16.40 CODESYS Control for Raspberry Pi MC SL 4.2.0.0 with CODESYS...
-
Codesys fails to Restore a license from the explicitly created license update file CMLicenseNew.WibuCmRaU The license update file connect_57869_C83EA7021F8F.WibuCmRaU could not be restored on RevPi Connect Feat Codesys device (100337 57869 1.0). https://revolutionpi.com/revpi-connect-codesys/ License restore with following combinations were tried out: CODESYS Control for Raspberry Pi MC SL 4.0.1.0 with CODESYS Runtime Toolkit V3.5.16.40 CODESYS Control for Raspberry Pi MC SL 4.2.0.0 with CODESYS...
-
Codesys fails to Restore a license from the explicitly created license update file CMLicenseNew.WibuCmRaU The license update file connect_57869_C83EA7021F8F.WibuCmRaU could not be restored on RevPi Connect Feat Codesys device (100337 57869 1.0). https://revolutionpi.com/revpi-connect-codesys/ License restore with following combinations were tried out: CODESYS Control for Raspberry Pi MC SL 4.0.1.0 with CODESYS Runtime Toolkit V3.5.16.40 CODESYS Control for Raspberry Pi MC SL 4.2.0.0 with CODESYS...
-
Thanks for the hint.Turning User management was desired only for licensing bulk of the devices and then restoring the default User Configuration from the installed codesys runtime. Following setting works in disabling user management in "CODESYSControl_User.cfg" [CmpSecureChannel] CertificateHash=5ab21d81c63a48b3410f1f3e95bd463645986590 SECURITY.CommunicationMode=PLAIN_AND_ENCRYPTED [CmpUserMgr] AsymmetricAuthKey=c6c2a088595c3fe17cf23ff5705a134b3e9cff9f SECURITY.UserMgmtEnforce=NO
-
Hello everyone, For first time activating Codesys Control for Raspberry Pi v 4.1.0.0 using Online activation with Ticket ID, is it mandatory to activate user management on the device? If User management is not setup, no container found error is thrown. The container is found only after setting user management and login to the device. Is there any workaround for activating the devices using Online Ticket ID with simplicity. This was not the case with older codesys control for Raspverry Pi versions....
-
Hello everyone, For first time activating Codesys Control for Raspberry Pi v 4.1.0.0 using Online activation with Ticket ID, is it mandatory to activate user management on the device? If User management is not setup, no container found error is thrown. The container is found only after setting user management and login to the device. Is there any workaround for activating the devices using Online Ticket ID with simplicity. This was not the case with older codesys control for Raspverry Pi versions....
-
Hello everyone, For first time activating Codesys Control for Raspberry Pi v 4.1.0.0 using Online activation with Ticket ID, is it mandatory to activate user management on the device? If User management is not setup, no container found error is thrown. [-img src=codesys error.png width=50%: missing =-] The container is found only after setting user management and login to the device. [-img src=2021-08-26 11_43_36-License Manager.png width=50%: missing =-] Is there any workaround for activating the...
-
Hello everyone, For first time activating Codesys Control for Raspberry Pi v 4.1.0.0 using Online activation with Ticket ID, is it mandatory to activate user management on the device? [-img src=2021-08-26 10_44_32-CODESYS.png width=50%: missing =-] [-img src=2021-08-26 10_22_02-CODESYS.png width=50%: missing =-] If User management is not setup, no container found error is thrown. [-img src=codesys error.png width=50%: missing =-] The container is found only after setting user management and login...