Hi Ketchup ;) Technically, you are creating a library, which is loaded by Linux. So there is technically no such limitation. But practically you have to have a deep understanding of C and C++ to master the binding between them. The starting point is: Create one object, which implements the C interface, that is used by CODESYS. Then you create an interface header, which contains C interfaces, sourounded by eytern "C" statements. This interface can then be used, and called from the C wrapper, and builds...
I don't know your driver. But the GPIO open error sounds suspicious. Otherwise I can say, that there is no real difference between a BBB and another runtime. When you registered your driver handle (IBase) in UpdateConfiguration correctly, and you used the channels in your project (check device->Task Deployment to be sure), your ReadInput/WriteOutput functions should be called.
Hi Paula! That should be as easy, as changing the URL in install2.sh. The variable is called CDS_LINK, and it contains the SP16 version number. I didn't test it with SP11, but guess it should simply work...
Searching Forge
Searching Forge
Hi @mondinmr, thanks again for this nice summary about realtime optimizations! And also thanks for the outlook regarding the Rasperry Pi 4. Looking forward to hear from that. Hint: If you post the Raspberry Pi results in CODESYS Talk, maybe use a different topic for RPI. Then it will be easier found. Don't know if you found this already, but from CODESYS there is an FAQ, giving some optimization hints: https://faq.codesys.com/pages/viewpage.action?pageId=122748972 And soon, there will be a new chapter...
The only problem is the new installer. I didn't find a stable way, yet to install it. When installed, everything runs fine. But you might have noticed, the automation of the setup of wine and CODESYS in Docker is quite tricky. π
Error while building project