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 ...

Hi Francois,
There is traditional touch panel based HMI soulution from CODESYS ecosystem
https://www.codesys.com/products/codesys-visualization/hmi.html
https://store.codesys.com/en/codesys-hmi-sl-bundle.html

More economical option is using a browser based HMI option usaing CODESYS WebVisu which ...

Analog Input channel should be configured to 0-10V in CODESYS Compact Parameters as in your test case.

Codesys Configuration overwrites pictory configuration.Pictory configuration is independent and not used together with codesys.
The combination with pictory and piTest was an alternate option ...

Hi Vaggelis,
It works at my side as shown in screenshots below:
Compact Test.png

Compact Test 2.png

Test Project: CompactTestAI.zip


Attached project is tested with:
revolutionpibridge-V1.4.1.0
CODESYS Control for Raspberry PI 4.10.0.0


You can try other Analog inputs.

Test if Analog ...

The previous picture shows wiring to Analog input CH 6.
Also, the input variable declared in CODESYS should be called in program in order to be updated cyclically.This can be done as shown in screenshots below.
Regards, Amar

Hello Sigmund,
Thank you for bringing the issue to notice.The strange behaviour for controlling RevPiLED for Connect 4 is due to missing parameter RevPiOutput in I/O mapping of Connect4 which was adapted in PiCtory.
This resulted in writing the RevPiLED at incorrect offset in process image.This will ...

Try creating a new Connect 4 project with CODESYS Control for Raspberry Pi MC SL V4.8.0.0 and CODESYS Development System V3.5.19.0

In libarry manager remove any previous references to libarry KunbusIoDrvRevPiBridge, 1.3.0.0 (Kunbus GmbH)

Regards, Amar

Perhaps you have not configured the PlaceholderFilePath for pictory in /etc/CODESYSControl_User.cfg.
A config.rsc is not being created in that case.

Refer release notes RevolutionPiBridgeV1.4.0.0
In the Revolution Pi Library for Codesys, file write access under the following folder, /etc/revpi/, is ...

You can refer to RevPi CODESYS Node-RED example which exchanges CODESYS application data running on RevPi device with Node red application

Revolution Pi Library Beta for CODESYS V1.4.0.0
https://revolutionpi.com/tutorials/downloads
Regards
Amar

Hi,
Have you manually configured PlaceholderFilePath in /etc/CODESYSControl_User.cfg?

Details explained in following Post
Using Revolution Pi Library for CODESYS V1.3.0.0 with CODESYS V3.5 SP19,CODESYS Control for Raspberry Pi MC SL V4.8.0.0
https://revolutionpi.com/forum/viewtopic.php?t=4007 ...