Hello Rossano,
Thank you for the confirmation. We have released the same version that you tested.

https://revolutionpi.com/en/support/downloads

Archive CODESYS Drivers
Revolution Pi Library for CODESYS V1.4.2.0

The Revolution Pi Library for CODESYS V2.2.0.0 (CODESYS Development System V 3.5 SP21 ...

Hello Rossano,
Please test the revolutionpibridge-V1.4.2.0-beta library package.
The library is compiled for CODESYS 3.5 SP19 and can be used with SP21.

https://packages.revolutionpi.com/buster/download/revolutionpibridge-V1.4.2.0-beta.zip

It can be used with the discontinued CODESYS Control for ...

Hi PAHO,
Can you please test with the attached sample example?
Connect4_DIO_Test.zip

The program sets the first 8 outputs of the first DIO module and the first 4 outputs of the second DIO module starting from the left of piBridge.

CODESYS_FE65mDjfPX.png

The following pictory configuration ...

/dev/ttyRS485 in pictory is symbolic link to /dev/ttyUSB0


The port number 0 should not be mentioned in /etc/CODESYSControl_User.cfg . Actual entry therefore is
Now /dev/ttyUSB0 corresponds to COM port 1 in CODESYS for Connect /S

Hello Wolfgang and PVCS,
Modbus RTU with Connect 4 on 64 bit image shall work with following settings :

Configure COM port default interface for Connect4 in /etc/CODESYSControl_User.cfg
running CODESYS Control for Linux ARM64 SL


[SysFile]
PlaceholderFilePath.1=/etc/revpi, $configrsc$

[SysCom ...

Hello Wolfgang,
Please follow the similar topic posted on the english forum.

viewtopic.php?t=4345

Viele Grüße, Amar

Hello PVCS,

Under General->Serial Port Configuration tab of MODBUS_COM device in codesys tree
COM Port selected will be as follows

/dev/ttyUSB0 -> COM Port 1
/dev/ttyUSB1 -> COM Port 2 ...
/dev/ttyUSBn -> COM Port n

In /etc/CODESYSControl_User.cfg you can try configuring following:

[SysCom ...

Hi,
Are you using 1.4.1.99 beta version of Revolution Pi Library for CODESYS?

For Connect 4 with RevPi Bullseye Image (64 bit) you need to use
CODESYS Control Linux ARM 64 bit.

There may be some incorrect device tree combination in your configured project.

I would recommend to first create a new ...

Hallo,
Möglicherweise liegt es an einem fehlerhaften Bitzugriff im konfigurierten Projekt.
Verwend die neueste Version der RevPi Codesys-Bibliothek.
Überprüf mal, ob das richtige DIO-Modul im Codesys-Gerätebaum konfiguriert ist.
(Verwendest du die Blinklicht-Demo, um einzelne Bits des ...

It is recommended to use latest Codesys control runtime.(CODESYS Control for Raspberry Pi MC V 4.10.0)

https://store.codesys.com/en/softplcs-for-applicationbased-licenses

Some other configuration (probably 1-Wire Busmaster) occupied the placeholder path on your configured device.
When you install ...