Technical issues with Revolution Pi Core 1 and Buster
The Buster image does not work well on Revolution Pi Core (CM1) modules, you can try an older image.
You can find older Buster versions at the following link.
http://packages.revolutionpi.de/buster/
I would like to bring data from a PROFINET application to the cloud. According to my research, the S7 PUT/GET protocol can be used with Revolution Pi7, can you confirm this?
We have no stock in Revolution Pi7, here is a quick guide, however, Support this is not active.https://revolution.kunbus.de/forum/viewtopic.php?t=854
However, yes exactly that was the goal of Revolution Pi7, namely to read and process data from the data stream of the PROFINET network.
I want to use the serial gateway and for that, I need a software, is that correct?
Yes, that's right. The GATEWAY Module for serial network you may need the KUNBUS-Scripter.
Here are the FAQs about the software:KUNBUS-Scripter FAQ
Are you planning to put CODESYS on the Revolution Pi Core device?
No, unfortunately we are not planning to do so.
https://revolutionpi.de/forum/viewtopic.php?f=49&t=3016
I get an old outdated version in Web Status, although I have updated the system, how is this possible?
You are probably using an outdated distribution, for example, Jessie. Please update your system to the latest distribution. Original discussion:
https://revolutionpi.de/forum/viewtopic.php?f=6&t=3131
I use Modbus-RTU and after a restart of the Revolution Pi there is an error in the register. What can I do?
Unfortunately, this is a known problem that has been reported here:
https://revolutionpi.de/forum/viewtopic.php?f=14&t=3156
After the reboot, the value 0x11 is in the register "Modbus_Master_Status".
Even if I write the value 1 into the register "Master_Status_Reset", the error remains.
If I reset the driver via PiCtory or use the command "piTest -x", the "Modbus_Master_Status" register shows the hex value 0x00.
I have a network problem. When I try to connect directly to the Revolution Pi via Ethernet, I have problems with the connection. This can be avoided by connecting a switch in between, what can I do?
We can confirm that direct Ethernet connections without an intermediate switch do not work reliably with the recently released 5.10 kernel. The 4.19 kernel we’ve used before does not exhibit the issue. A fix is underway here. We’ll release a kernel update shortly.
How can I disable the error "Failed to start Network Time Synchronization" when using Revolution Pi Core 100102?
The older Buster images with kernel 4.19 (2022-01-19-Revolution Pi-buster.zip) work with the kernel. A list of all Buster images can be found at http://packages.revolutionpi.de/buster/.
The current image uses kernel 5.10 with the dwc2 USB driver, which leads to severe performance problems on the old hardware of the core with CM1. To prevent this, the customer has 2 options:
(a) pin kernel to version 4.19, as also described in the release notes,
https://kunbus-gmbh.atlassian.net/servicedesk/customer/kb/view/2606891078https://kunbus-gmbh.atlassian.net/servicedesk/customer/kb/view/2588082208b) Change the USB driver to dwc_otg. Instructions, which can be provided on request, can be found here: Run Buster Image on Revolution Pi Core (CM1)
Can I install a backup image from a RevPi Core on a RevPi Core3+?
The image created for the RevPi Core is incompatible with the RevPi Core 3+ due to differences in hardware or firmware. To resolve this issue, you may need to modify the image or create a new image specifically for the RevPi Core 3+.
I have a USB-Serial interface and get transmission errors, what can I do?
After about a week uptime, Ethernet communication seems to stop. What can I do?
Please update your image. You may use this guide Revolution Pi Checklist
See original discussion: https://revolutionpi.de/forum/viewtopic.php?f=3&t=3088
I don’t enough space to upgrade my Revolution Pi Core 3. What can I do?
Please take a look here: (40) Can't upgrade - Revolution Pi Forum
How can I avoid the problem?
The Ethernet port on the front of the Revolution Pi Core uses Auto-MDIX for automatic detection, which does not always work reliably. Disable Auto-MDIX and configure the connection speed and duplex mode manually.
sudo ethtool -s eth0 duplex full speed 100
Would it be possible to install LabVIEW on a Revolution Pi device?
No, see the original discussion here: