Update the CODESYS runtime to 4.11.0.0.
https://revolutionpi.com/forum/viewtopic.php?p=15576#p15576No, there is a demo mode that runs about 1 hour until the runtime is stopped - take a look at this FAQ:
Q: Why will the Raspberry Pi MC SL licenses be discontinued next year, but not Raspberry Pi SL
Take a look here at: Why will the Raspberry Pi MC SL licenses be discontinued next year, but not Raspberry Pi SL?
https://store.codesys.com/en/faq-applicationbased-licensesCODESYS changed the license model for the start of 2024. The new application-based licenses apply to all CODESYS Control SL products. They are based on the software function used and no longer on the performance of the device. This means that the licenses can be used equally on all CODESYS Control SL-capable devices.
Division into performance classes
The function of a control system is largely determined by the software, whereas the hardware is responsible for providing the required resources. For this very reason, the application-based licenses no longer refer to the hardware, but to the software used in the IEC application.
For this purpose, all applications are divided into different performance classes based on suitable characteristics. Behind this are use cases that are covered. The limits of a class are derived from the use cases:
You can see more information here:
https://store.codesys.com/en/howto_applicationbasedlicensesPlease change the access in the project to WORD access. Alternatively, use the supplied example projects from the Revolution Pi Library for CODESYS.
Original discussion
https://revolutionpi.com/forum/viewtopic.php?t=4358The actual error is shown on the right in the picture, it is because the PiCtory configuration could not be written:
Please follow the steps of the
Alternatively, you can switch to the 64-bit compatible version of the Revolution Pi Library for CODESYS V1.4.1.99 or higher.
Original discussion
You should select RevPi Core 3.
Create an /wiki/spaces/SUP/pages/2809364531 and check whether there are any entries in the codesyscontrol.log file:
AR consumer DHT expired
If this is the case, please contact the manufacturer of the bus device you are using and CODESYS Support
The firmware of a bus device may need to be updated
Here is a discussion
No
The module is shipped with the 64 Bit image but currently, CODESYS does not deliver a 64 bit runtime.
Please use a 32 bit image.
https://revolutionpi.com/forum/viewtopic.php?t=4076Disable CODESYS, connect an output to an input pin, and run the commands on the shell. See here: https://revolutionpi.com/forum/viewtopic.php?t=3920#p13994
Yes, this is technically possible, see here:https://de.codesys.com/produkte/codesys-fieldbus/profibus.html
Another variable can be used for converting to the required type instead of direct mapping. This can then be called in Main task cyclically to update required RevPi I/O variables accordingly.
https://help.codesys.com/api-content/2/codesys/3.5.16.0/en/_cds_operator_convert_integer/
There are discussions about this in the Revolution Pi forum
The Multi Core version uses all cores of the processor.
https://store.codesys.com/en/codesys-control-for-raspberry-pi-mc-sl.html
suggest?ently there is no RevPi Core S as an option in the hardware selection of Codesys, but you can select RevPi Core 3. The Core S is 100% compatible with the Core 3, so it is sufficient if you select the Core 3 in CODESYS.
Retain Persistent variable is not supported with RevPi since it requires a separate EEPROM interface to store the variables.
As a workaround, the variable status could be saved to a file and read again on startup.
Write and Read File using Codesys
https://forge.codesys.com/forge/talk/Engineering/thread/d5550f2e37/
CODESYS runtime for raspberry MC supports webvisu on RevPi devices. The default browser on RevPi device could be used with webvisu with an HDMI connection; however, you will have to look out if somfunctionalitieses are not curtailed in that browser. CODESYS Target visu works well with remote browser, but may have limitations with inbuilt browser. I suggest you also to install the Chrome browser on RevPi if you have issues with the inbuilt browser.
You can perhaps check on CODESYS webvisu forum for possible solution or post a query on the CODESYS forum.
Yes, that's right. If you use Codesys, this is the leading system.
Yes, look here at the example Blinking Light
https://revolutionpi.com/tutorials/beispiel-blinking-light-2-2/
Currently, there is no RevPi Core S as an option in the hardware selection of Codesys, but you can select RevPi Core 3. The Core S is 100% compatible with the Core 3, so it is sufficient if you select the Core 3 in CODESYS.
In the following video, you can see how the devices are to be arranged in codesys.
Sort device arrangement
Please verify the execution sequence.
https://revolutionpi.de/forum/viewtopic.php?f=6&t=2711#p10016
The simulation mode in CODESYS for the RevolutionPi is not supported.
Edit the file “/etc/codesyscontrol.cfg” to set the value “/dev/ttyRS48” (without 5!). Then in CODESYS set the RS485 to port 6.
https://revolutionpi.com/tutorials/beispiel-modbustcp-rtu-master-2-2/?noredirect=en_US
Problem: When I use the Tools → Update Raspberry Pi option in CODESYS, I get the following msg:”The target CPU architecture is not supported: ARMV6l”
Solution: ARMV6l is for single core support in Codesys. If the multicore version is installed, then the architecture is automatically set to ARMV7l and the error can be avoided.
Please follow the instructions in the Forum: Verbindungsprobleme RevPi Connect + mit CODESYS - Revolution Pi Forum
There is an example in Forum: unable to install device configuration in CODESYS for RevPiDIO Module - Revolution Pi Forum
Always place the RevPi device at the root of the CODESYS device tree.
For example:
The RevPi device should be placed at the root of the device (CODESYS Control for Raspberry Pi MC SL) in the CODESYS device tree. Other devices such as Ethernet (see image below) should be placed after the basic RevPi device (Core/Connect/Compact/Flat) in the CODESYS device tree.
To configure the Analog outputs, you must log into PiCtory and make the changes there.
https://revolutionpi.de/forum/viewtopic.php?t=3377
The default PROFINET IO task cycle in the CODESYS control for the Raspberry Pi MC runtime is 1 ms.
This is the recommended task cycle. Faster task cycles below 1 ms may cause PROFINET communication errors.
This error message appears:
There may be a problem with the user management:
Reinstall the CODESYS runtime environment on RevolutionPi Connect.
Check the configured gateway in the Devices→Communication Settings tab.
Click Scan Network and select the RevPi CODESYS device found and click the OK button.
The first time you log in, you will be asked again to configure username and password,
then try to go online again.
Please install a suitable version of https://store.codesys.com/codesys-control-for-raspberry-pi-mc-sl.html the CODESYS Runtime
Please look at your PC under your administrator profile for this file:
C:\Users\[USERNAME]\Revolution Pi\Help\RevPi CodesysLibHelp.chm
No, the licence is bound to the device.
You can buy the Licence on the CODESYS Website. https://store.codesys.com/codesys-control-for-raspberry-pi-mc-sl.html
Yes, the RevPi S / SE will be compatible with the upcoming CODESYS Release.
You have to buy a new licence for the target device.
No, it is not possible
https://revolutionpi.de/forum/viewtopic.php?f=49&t=3016
Run your application as administrator
https://revolutionpi.de/forum/viewtopic.php?f=49&t=3138#p11167
https://forge.codesys.com/forge/talk/Engineering/thread/cef51eb0d0/
There is a module from Codesys, see here:
https://de.codesys.com/produkte/codesys-safety/safety-sil2.html
Please contact the support and the community of Codesys. Original discussion:
https://revolutionpi.de/forum/viewtopic.php?f=4&t=3068
This issue has been reported here https://revolutionpi.de/forum/viewtopic.php?f=6&t=3023#p10839
Please disable the GPIO’s in the CODESYS device tree like so:
There may be several reasons for this. Please have a look at the following article:
Codesys Resolving Version Conflicts
Please send us the following information to support@kunbus.com
Your invoice copy
Serial number of the device. You can find this information here.
We will restore your CODESYS licence. Have a look here about the licence import handling:
https://www.codesys.com/the-system/licensing.html
After a random time, the EtherCAT stops working and the log shows this error “Field bus lost synchronicity”.
Please have a look at the following post on our forum:
https://revolutionpi.de/forum/viewtopic.php?f=6&t=3007#p10748
Here is a typical error message:
The problem occurs with older CODESYS project when trying to use this project in a new CODESYS Runtime version. For Example, load project from CODESYS 3.5.16.0 to 3.5.17.0. The solution to this is to rebuild the project with 3.5.17.0 and reconfigure the CODESYS device tree as in the previous project.
In the next version of the CODESYS Revolution Pi Package, the examples will default to CODESYS Runtime V3.5.17.0.
Here already in advance the modified examples for download:
There might be some Application code in Codesys, breaking the SSH connection.
The CODESYS control runtime might be getting stopped when the application is downloaded.
Try initially by downloading an empty CODESYS application to see if the problem exists
CODESYS menu entry "Update Raspberry Pi" missing
Yes, this works – check out the included tutorials, e.g. the traffic light. These are installed in the form of a Windows help file together with the RevPi CODESYS Library. Also, have a look at these helpful links:
There is a message with green: licence available, yellow licence available but invalid and red no licence. Does not show any of the three icons for the product.
https://revolutionpi.de/forum/viewtopic.php?f=8&t=2983#p10851
Yes, you just have to download the Revolution Pi Library for CODESYS.
Together with the instructions on the page, you can make a configuration for your expansion modules.
This way you can also access the X2 input. Have a look at the help file in CODESYS after you have installed everything. There you will find more interesting code examples that can support you during commissioning.
Please update the Revolution Pi Library. You can find it in the Downloads section, see here:
https://revolution.kunbus.com/tutorials/downloads/?noredirect=en_US#driver
Verify which CODESYS control for Raspberry Pi is installed on RevPi Connect
GoTo Tools → update Raspberry Pi
enter username password, IP address and click System info
This version should be the same as the one configured in CODESYS application project in IDE.
For first login, CODESYS user management asks for configuring user/password. If that was not asked, uninstall CODESYS runtime on RevPi Connect and install it again.
(Same version as the one configured in CODESYS project)
Installing CODESYS Runtime
https://revolutionpi.com/codesys-runtime-installieren-3/
If login does not work, try disabling user management.
Edit /etc/CODESYSControl_User.cfg and add the following:
[CmpSecureChannel] CertificateHash=5ab21d81c63a48b3410f1f3e95bd463645986590 SECURITY.CommunicationMode=PLAIN_AND_ENCRYPTED |
[CmpUserMgr] AsymmetricAuthKey=c6c2a088595c3fe17cf23ff5705a134b3e9cff9f SECURITY.UserMgmtEnforce=NO |
Save and exit. Restart CODESYS control or do a system reboot
sudo systemctl codesyscontrol restart
Install new Image
https://revolutionpi.de/forum/viewtopic.php?f=3&t=2655#p9747
You can use a" RevPi Con Can” for your project to read and process sensor values with CODESYS via the this CON extension module.
Information on the “Con Can” can be found under the following links:
https://revolutionpi.de/shop/de/canbus-module
https://revolutionpi.com/tutorials/uebe ... i-con-can/
Forum Entry:https://revolutionpi.de/forum/viewtopic.php?f=4&t=3339
Docker image on Docker Hub that might be interesting. You can find it at the following link: https://hub.docker.com/r/hilschernetpi/netpi-codesys-basis.
The content by label feature displays related articles automatically, based on labels you choose. To edit options for this feature, select the placeholder below and tap the pencil icon.
|