Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
Hi,
I'm actually out of ideas how I can activate the serial port in Codesys (pic below).
If I use the "Pictory"-System of Kunbus, I can ask regulary all registers from all attached units on the serial port of the Revolution PI. But when the Codesys Runtime is installed it overwrites the Kunbus Config. Modbus Master RTU isn´t installed on the RevPI. (pic below)
Modbus TCP is working correctly when used.
ttyAMA0 is set as Linux.Devicefile=/dev/ttyAMA0 in CODESYSControl_User.cfg, I also tried /dev/serial and /dev/ttyS
The new released driver from codesys installed over the runtime also doesn't work.
The flashing red triangle before each installed Modbus Slave is there because Kunbus (Maker of RevPI) didn't programmed status of the slaves (controlled over codesys) yet
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The Problem isn´t solved yet, our project is cancelled (since Sep 22) caused of massive personal fluctuation.
I personally found a solution using Phyton (in combination with RevPiModIO) while implementing the Pictory System by Kunbus for adress resolving. But as long the ModbusRTU-Hardware isn´t implemented by Kunbus in Codesys it probaply won´t work. Also, Kunbus is going to finish the support of any ModbusRTU caused by problemacity of hardware procurement.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm actually out of ideas how I can activate the serial port in Codesys (pic below).
If I use the "Pictory"-System of Kunbus, I can ask regulary all registers from all attached units on the serial port of the Revolution PI. But when the Codesys Runtime is installed it overwrites the Kunbus Config. Modbus Master RTU isn´t installed on the RevPI. (pic below)
Modbus TCP is working correctly when used.
ttyAMA0 is set as Linux.Devicefile=/dev/ttyAMA0 in CODESYSControl_User.cfg, I also tried /dev/serial and /dev/ttyS
Thanks!
It seems there isn't the modbus serial driver available for the RevPI. (pic below) How can I add Modbus to the Device Repository?
Last edit: draygoon 2022-08-04
The new released driver from codesys installed over the runtime also doesn't work.
The flashing red triangle before each installed Modbus Slave is there because Kunbus (Maker of RevPI) didn't programmed status of the slaves (controlled over codesys) yet
Hello I have the same problem do you already fixed the issue
Hello I have the same problem do you already fixed the issue
The Problem isn´t solved yet, our project is cancelled (since Sep 22) caused of massive personal fluctuation.
I personally found a solution using Phyton (in combination with RevPiModIO) while implementing the Pictory System by Kunbus for adress resolving. But as long the ModbusRTU-Hardware isn´t implemented by Kunbus in Codesys it probaply won´t work. Also, Kunbus is going to finish the support of any ModbusRTU caused by problemacity of hardware procurement.