Hello, I recommend you this: - CODESYS Controller for Raspberry Pi MC SL - 4.6.0.0 - CODESYS Runtime 3.5.18 -Revolution Pi Library for CODESYS V1.3.0.0 (ID: 9721) CODESYS Runtime 3.5.17 is incompatible with CODESYS Controller for Raspberry Pi MC SL - 4.6.0.0 Best Regards Ulrich Kouatang Biakoup | Te...
Hello beusterh, I want to let you know that CODESYS override the configuration of PiCtory. CODESYS writes all 32 bytes of Virtual outputs cyclically. Two applications cannot have write access to those virtual bytes address space, and they would be overwritten by CODESYS application. Could you please...
Hello tomazbracic, Yes, of course. The RevolutionPi project is built on the idea of sharing and discussing knowledge across the community. You can create a custom Image and run it in your RevolutionPi. In our GitHub repository, we have a Imagebakery , which is used to build custom image. Also, take ...
Hello aki-ks, The device does not boot when the USB cable is connected (disable eMMC). Therefore, the USB plug has to be disconnected, and the device has to be de-energized for a short time. A workaround must be to disable the computer's USB slot via the Windows Device Manager and then find a way to...
Hi yongchaow, Please use Revolution Pi Library for CODESYS V1.3.0.0 (ID: 4712) not RevolutionPiBridgeV1.2.1.0. CODESYS Runtime V3.5.18 is only compatible with CODESYS Control for Raspberry Pi MC SL - 4.6.0.0 and Revolution Pi Library for CODESYS V1.3.0.0 (ID: 4712). Please, make sure that you have t...
Hello Johan.vdw, The error you have on UaExpert is due to the configuration on your server side. You are running OPCUA Server in codesys. Please have a look at this OPCUA&CODESYS webinar . you can also post your problem on Codesys forum . Best Regards Ulrich Kouatang Biakoup | Technical Support