You have a RevPi Module and you want to put CODESYS and the involved examples we deliver into operation? Then you are in the right place.
To get the Revolution Pi CODESYS examples up and running, the versions must be compatible.
...
| Info |
|---|
In unlicensed demo mode, the |
...
Regarding the release notes of the Revolution Pi Library for CODESYS the following versions are necessary:
runtime is stopped after approx. 1 hour. |
Prerequisites
- RevPi Bullseye 64-bit (04/2024)
- CODESYS Development System V3.5.20.0
- Revolution Pi Library for CODESYS
...
...
...
...
...
...
...
Apply the steps in the release notes regarding CODESYS bug fix CDS-81506 https://revolutionpi.com/forum/viewtopic.php?t=4007
Edit the file
/etc/CODESYSControl_User.cfg
On the device itself via terminal session and that command
...
Implementation
You can watch Dirk’s helpful video tutorial here to view how easy it is to put everything in the right place:
...
FAQ
Don't I still have to adapt a configuration file?
No, since PiCtory version 2.4.0.0 or higher there is no need to manually configure the config.rsc PlaceholderFilePath in
/etc/CODESYSControl_User.cfg
...
Via copying it to your local machine, edit it and copy it back afterwards
Apply those lines
For CODESYS Control for Raspberry Pi - 4.10.0.0
| Code Block | ||
|---|---|---|
| ||
[SysFile]
PlaceholderFilePath.2=/etc/revpi, $configrsc$ |
For CODESYS Control for Raspberry Pi - 4.8.0.0
| Code Block | ||
|---|---|---|
| ||
[SysFile]
PlaceholderFilePath.1=/etc/revpi, $configrsc$ |
Note: Background information when using CODESYS Control for Raspberry Pi 4.10.0.0
...
.
Which license is the right one?
...
Which CODESYS license can I use for my Revolution Pi device?
Where did the Raspberry Pi MC SL license go, or is there an alternative?