RELEASE NOTES

These release notes are for the current development version of RevolutionPiBridge CODESYS Package.
A codesys package library to support Revolution Pi Family from KUNBUS GmbH

Online help documentation - Revolution Pi Library for CODESYS:

English: https://revolutionpi.com/documentation/codesys

German: https://revolutionpi.com/documentation/de/codesys

-----------------------------------------------------------------------------------------------------------------------------

2.1.0.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 11-02-2025

Features
- Added support for Connect 5 variants
- Counter reset feature added for DIO/DI modules

Bug Fixes
- Corrected Ethenet IP gateway I/O address space size to 480 bytes instead of 512 bytes
- Add RO module detectition in scan device list
- Fixed Module state parameter update for RevPi Gateways with CODESYS Control Linux ARM 64
- Input Mode channel description visible in the Module parameters tab for DI and DIO modules
- Corrected DI Module InputMode channel 16 configuration options

Release Note

System Requirements
CODESYS Development System V3.5.20.0 or higher.

CODESYS control runtime support on RevPi Bookworm and Bullseye Image (64 bit)

  • CODESYS Control Linux ARM 64 bit V4.11.0.0 or higher

CODESYS control runtime support on RevPi Bullseye Image (32 bit)

  • CODESYS Control Linux ARM 32 bit V4.11.0.0 or higher

PiCtory version 2.4.0.0 or higher
This removes earlier necessity of manually configuring  config.rsc PlaceholderFilePath in /etc/CODESYSControl_User.cfg.

Check current installed pictory package
dpkg-query -l | grep pictory

Install latest pictory debian packet
sudo apt update && sudo apt install pictory

If CODESYS Control Linux ARM 32/64 bit is installed on RevPi Device, restart it in order to load the changes after updating pictory packet.
sudo service codesyscontrol restart
Alternatively, you could reboot the device

For installing CODESYS Control Linux ARM 64 bit on RevPi devices with Bullseye 64-bit Image use following menu from CODESYS Development System
Tools->Update Linux ARM 64

For installing CODESYS Control Linux ARM 32 bit on RevPi devices with Bullseye Image (32-bit) use following menu from CODESYS Development System
Tools->Update Linux ARM
Do I have an ARM or ARM64 device?

Currently, only the RevPi Connect 4 is delivered with a 64-bit operating system. Here the "CODESYS Control Linux ARM 64" must be used. All other RevPi devices have a 32-bit operating system on which the "CODESYS Control Linux ARM" must be installed upon delivery.

You can install other operating system versions, which are available on our download pages.

To check which version is the right one, execute following on the command line of the RevPi device over SSH.

cat /etc/revpi/image-release

If "armhf" is specified in the name, it is an "CODESYS Control Linux ARM" device, if "arm64" is specified there, it is an "CODESYS Control Linux ARM 64" device.
Known issues
  • If you use "Scan for devices" dialog and use the "Copy All Devices to Project" button, it will remove preconfigured virtual Devices and reset all configured module parameters and mapped variables. For an existing project, we recommend adding only individual devices from the list.

-----------------------------------------------------------------------------------------------------------------------------

1.4.1.99 beta
-----------------------------------------------------------------------------------------------------------------------------
Date: 27-2-2024

Features
- Support for CODESYS Control Linux ARM 64 bit with Connect 4 on RevPi Bullseye 64-bit Image.
- Support for CODESYS Control Linux ARM 32 bit on RevPi family devices with
  RevPi Bullseye Image (alternative for CODESYS Control for Raspberry Pi MC)

Changes
- CODESYS library compiler version used  - V3.15.19.40

Release Note

System Requirements
CODESYS Development System V3.5.19.40 or higher.

CODESYS control runtime support on RevPi Bullseye Image (64 bit)

  • CODESYS Control Linux ARM 64 bit V4.10.0.0 or higher

CODESYS control runtime support on RevPi Bullseye Image (32 bit)

  • CODESYS Control for Raspberry Pi MC V4.10.0.0 or higher
  • CODESYS Control Linux ARM 32 bit V4.10.0.0 or higher

For installing CODESYS Control Linux ARM 64 bit on RevPi devices with Bullseye 64-bit Image use following menu from CODESYS Development System
Tools->Update Linux ARM 64

For installing CODESYS Control Linux ARM 32 bit on RevPi devices with Bullseye Image (32-bit) use following menu from CODESYS Development System
Tools->Update Linux ARM

For installing CODESYS Control for Raspberry Pi MC on RevPi devices with Bullseye Image (32-bit) use following menu from CODESYS Development System
Tools->Update Raspberry Pi

CODESYS V3.5 SP19 includes a bug fix. CDS-81506: CODESYS Control SysFile
system file access vulnerability.ForceIecFilePath is activated by default, due to which file access from IEC is now restricted to the configured paths only (file sandbox).

For more details see Advisory 2023-01, which is available on the CODESYS website:

https://customers.codesys.com/index.php?eID=dumpFile&t=f&f=17553&token=cf49757d232ea8021f0c0dd6c65e71ea5942b12d&download=

Release notes for CODESYS V3.5 SP19
https://www.codesys.com/fileadmin/data/Images/System/Releaseinformation/Release-Notes-CODESYS-35190.html

In the Revolution Pi Library for Codesys, file write access under the following folder, /etc/revpi/, is required in order to create a config.rsc file based on devices configured in the CODESYS application project. The CODESYS project using the KUNBUS RevolutionPiBridge IO library creates a configuration file /etc/revpi/config.rsc, which is basically the PiCtory file /var/www/revpi/pictory/projects/_config.rsc.

Customers using Revolution Pi CODESYS devices will therefore have to manually configure appropriate PlaceholderFilePath in /etc/CODESYSControl_User.cfg as mentioned below:

For CODESYS Control for Linux ARM (32 bit and 64 bit) V4.10.0.0 or higher

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

For CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 or higher

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

Note: When using CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 you may be required
to increase the PlaceholderFilePath from default 1 to 2.This may be due to the CODESYS Control occupying this path internally.

https://forge.codesys.com/forge/talk/Engineering/thread/3b90bda4a1/

Restart CODESYS Control in order to load the new changes from /etc/CODESYSControl_User.cfg.
Alternatively, you could reboot the device, and the changes will be automatically loaded from the user configuration file at the start of CODESYS Control.

sudo service codesyscontrol restart

 

-----------------------------------------------------------------------------------------------------------------------------

1.4.1.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 1-12-2023

Features
- Added support for Relay Output module for Core/Connect/Connect4 series

Bug Fixes
- Fixed incorrect Connect 4 config.rsc offset generation for RevPiOutput and 
  RevPiLED, which resulted in incorrect RevPiLED access for Connect 4.

Changes
- Examples added for CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 using 
  CODESYS V3.5 SP19 Patch 4

Release Note

CODESYS V3.5 SP19 includes a bug fix. CDS-81506: CODESYS Control SysFile
system file access vulnerability.ForceIecFilePath is activated by default, due to which file access from IEC is now restricted to the configured paths only (file sandbox).

For more details see Advisory 2023-01, which is available on the CODESYS website:

https://customers.codesys.com/index.php?eID=dumpFile&t=f&f=17553&token=cf49757d232ea8021f0c0dd6c65e71ea5942b12d&download=

Release notes for CODESYS V3.5 SP19
https://www.codesys.com/fileadmin/data/Images/System/Releaseinformation/Release-Notes-CODESYS-35190.html

In the Revolution Pi Library for Codesys, file write access under the following folder, /etc/revpi/, is required in order to create a config.rsc file based on devices configured in the CODESYS application project. The CODESYS project using the KUNBUS RevolutionPiBridge IO library creates a configuration file /etc/revpi/config.rsc, which is basically the PiCtory file /var/www/revpi/pictory/projects/_config.rsc.

Customers using Revolution Pi CODESYS devices will therefore have to manually configure appropriate PlaceholderFilePath in /etc/CODESYSControl_User.cfg as mentioned below:

For CODESYS Control for Raspberry Pi MC SL - 4.8.0.0

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

For CODESYS Control for Raspberry Pi MC SL - 4.10.0.0

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

Note: When using CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 you may be required
to increase the PlaceholderFilePath from default 1 to 2.This may be due to the CODESYS Control occupying this path internally.

https://forge.codesys.com/forge/talk/Engineering/thread/3b90bda4a1/

Restart CODESYS Control in order to load the new changes from /etc/CODESYSControl_User.cfg.
Alternatively, you could reboot the device, and the changes will be automatically loaded from the user configuration file at the start of CODESYS Control.

sudo service codesyscontrol restart

 

-----------------------------------------------------------------------------------------------------------------------------

1.4.0.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 5-06-2023

Features
- Added support for Connect 4 variants
- Added RevPi CODESYS Node-RED Example

Changes
- Library targeted to CODESYS Runtime V3.5.19.0
- Examples targeted as default for CODESYS Control for Raspberry Pi MC SL - 4.8.0.0

Release Note

CODESYS V3.5 SP19 includes a bug fix. CDS-81506: CODESYS Control SysFile
system file access vulnerability.ForceIecFilePath is activated by default, due to which file access from IEC is now restricted to the configured paths only (file sandbox).

For more details see Advisory 2023-01, which is available on the CODESYS website:

https://customers.codesys.com/index.php?eID=dumpFile&t=f&f=17553&token=cf49757d232ea8021f0c0dd6c65e71ea5942b12d&download=

Release notes for CODESYS V3.5 SP19
https://www.codesys.com/fileadmin/data/Images/System/Releaseinformation/Release-Notes-CODESYS-35190.html

In the Revolution Pi Library for Codesys, file write access under the following folder, /etc/revpi/, is required in order to create a config.rsc file based on devices configured in the CODESYS application project. The CODESYS project using the KUNBUS RevolutionPiBridge IO library creates a configuration file /etc/revpi/config.rsc, which is basically the PiCtory file /var/www/revpi/pictory/projects/_config.rsc.

Customers using Revolution Pi CODESYS devices will therefore have to manually configure PlaceholderFilePath in /etc/CODESYSControl_User.cfg as mentioned below.

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

Restart CODESYS Control in order to load the new changes from /etc/CODESYSControl_User.cfg.
Alternatively, you could reboot the device, and the changes will be automatically loaded from the user configuration file at the start of CODESYS Control.

sudo service codesyscontrol restart

-----------------------------------------------------------------------------------------------------------------------------

2.0.0.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 26-06-2024

Features
- Support for CODESYS Control Linux ARM 64 bit with Connect 4 on RevPi Bullseye 64-bit Image.
- Support for CODESYS Control Linux ARM 32 bit on RevPi family devices with
  RevPi Bullseye Image (alternative for CODESYS Control for Raspberry Pi MC)
- Discontinued support for CODESYS Control for Raspberry Pi MC runtime

Changes
- CODESYS library compiler version used  - V3.15.20.0
- Examples targeted to CODESYS Runtime V3.5.20.0
- Discontinued CHM based offline documentation
- Improve Connector error messaging in device tree

Release Note

System Requirements
CODESYS Development System V3.5.20.0 or higher.

CODESYS control runtime support on RevPi Bullseye Image (64 bit)

  • CODESYS Control Linux ARM 64 bit V4.10.0.0 or higher

CODESYS control runtime support on RevPi Bullseye Image (32 bit)

  • CODESYS Control Linux ARM 32 bit V4.10.0.0 or higher

PiCtory version 2.4.0.0 or higher
This removes earlier necessity of manually configuring  config.rsc PlaceholderFilePath in /etc/CODESYSControl_User.cfg.

Check current installed pictory package
dpkg-query -l | grep pictory

Install latest pictory debian packet
sudo apt update && sudo apt install pictory

If CODESYS Control Linux ARM 32/64 bit is installed on RevPi Device, restart it in order to load the changes after updating pictory packet.
sudo service codesyscontrol restart
Alternatively, you could reboot the device

For installing CODESYS Control Linux ARM 64 bit on RevPi devices with Bullseye 64-bit Image use following menu from CODESYS Development System
Tools->Update Linux ARM 64

For installing CODESYS Control Linux ARM 32 bit on RevPi devices with Bullseye Image (32-bit) use following menu from CODESYS Development System
Tools->Update Linux ARM
Do I have an ARM or ARM64 device?

Currently, only the RevPi Connect 4 is delivered with a 64-bit operating system. Here the "CODESYS Control Linux ARM 64" must be used. All other RevPi devices have a 32-bit operating system on which the "CODESYS Control Linux ARM" must be installed upon delivery.

You can install other operating system versions, which are available on our download pages.

To check which version is the right one, execute following on the command line of the RevPi device over SSH.

cat /etc/revpi/image-release

If "armhf" is specified in the name, it is an "CODESYS Control Linux ARM" device, if "arm64" is specified there, it is an "CODESYS Control Linux ARM 64" device.
Known issues
  • If you use "Scan for devices" dialog and use the "Copy All Devices to Project" button, it will remove preconfigured virtual Devices and reset all configured module parameters and mapped variables. For an existing project, we recommend adding only individual devices from the list.

-----------------------------------------------------------------------------------------------------------------------------

1.4.1.99 beta
-----------------------------------------------------------------------------------------------------------------------------
Date: 27-2-2024

Features
- Support for CODESYS Control Linux ARM 64 bit with Connect 4 on RevPi Bullseye 64-bit Image.
- Support for CODESYS Control Linux ARM 32 bit on RevPi family devices with
  RevPi Bullseye Image (alternative for CODESYS Control for Raspberry Pi MC)

Changes
- CODESYS library compiler version used  - V3.15.19.40

Release Note

System Requirements
CODESYS Development System V3.5.19.40 or higher.

CODESYS control runtime support on RevPi Bullseye Image (64 bit)

  • CODESYS Control Linux ARM 64 bit V4.10.0.0 or higher

CODESYS control runtime support on RevPi Bullseye Image (32 bit)

  • CODESYS Control for Raspberry Pi MC V4.10.0.0 or higher
  • CODESYS Control Linux ARM 32 bit V4.10.0.0 or higher

For installing CODESYS Control Linux ARM 64 bit on RevPi devices with Bullseye 64-bit Image use following menu from CODESYS Development System
Tools->Update Linux ARM 64

For installing CODESYS Control Linux ARM 32 bit on RevPi devices with Bullseye Image (32-bit) use following menu from CODESYS Development System
Tools->Update Linux ARM

For installing CODESYS Control for Raspberry Pi MC on RevPi devices with Bullseye Image (32-bit) use following menu from CODESYS Development System
Tools->Update Raspberry Pi

CODESYS V3.5 SP19 includes a bug fix. CDS-81506: CODESYS Control SysFile
system file access vulnerability.ForceIecFilePath is activated by default, due to which file access from IEC is now restricted to the configured paths only (file sandbox).

For more details see Advisory 2023-01, which is available on the CODESYS website:

https://customers.codesys.com/index.php?eID=dumpFile&t=f&f=17553&token=cf49757d232ea8021f0c0dd6c65e71ea5942b12d&download=

Release notes for CODESYS V3.5 SP19
https://www.codesys.com/fileadmin/data/Images/System/Releaseinformation/Release-Notes-CODESYS-35190.html

In the Revolution Pi Library for Codesys, file write access under the following folder, /etc/revpi/, is required in order to create a config.rsc file based on devices configured in the CODESYS application project. The CODESYS project using the KUNBUS RevolutionPiBridge IO library creates a configuration file /etc/revpi/config.rsc, which is basically the PiCtory file /var/www/revpi/pictory/projects/_config.rsc.

Customers using Revolution Pi CODESYS devices will therefore have to manually configure appropriate PlaceholderFilePath in /etc/CODESYSControl_User.cfg as mentioned below:

For CODESYS Control for Linux ARM (32 bit and 64 bit) V4.10.0.0 or higher

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

For CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 or higher

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

Note: When using CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 you may be required
to increase the PlaceholderFilePath from default 1 to 2.This may be due to the CODESYS Control occupying this path internally.

https://forge.codesys.com/forge/talk/Engineering/thread/3b90bda4a1/

Restart CODESYS Control in order to load the new changes from /etc/CODESYSControl_User.cfg.
Alternatively, you could reboot the device, and the changes will be automatically loaded from the user configuration file at the start of CODESYS Control.

sudo service codesyscontrol restart

 

-----------------------------------------------------------------------------------------------------------------------------

1.4.1.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 1-12-2023

Features
- Added support for Relay Output module for Core/Connect/Connect4 series

Bug Fixes
- Fixed incorrect Connect 4 config.rsc offset generation for RevPiOutput and 
  RevPiLED, which resulted in incorrect RevPiLED access for Connect 4.

Changes
- Examples added for CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 using 
  CODESYS V3.5 SP19 Patch 4

Release Note

CODESYS V3.5 SP19 includes a bug fix. CDS-81506: CODESYS Control SysFile
system file access vulnerability.ForceIecFilePath is activated by default, due to which file access from IEC is now restricted to the configured paths only (file sandbox).

For more details see Advisory 2023-01, which is available on the CODESYS website:

https://customers.codesys.com/index.php?eID=dumpFile&t=f&f=17553&token=cf49757d232ea8021f0c0dd6c65e71ea5942b12d&download=

Release notes for CODESYS V3.5 SP19
https://www.codesys.com/fileadmin/data/Images/System/Releaseinformation/Release-Notes-CODESYS-35190.html

In the Revolution Pi Library for Codesys, file write access under the following folder, /etc/revpi/, is required in order to create a config.rsc file based on devices configured in the CODESYS application project. The CODESYS project using the KUNBUS RevolutionPiBridge IO library creates a configuration file /etc/revpi/config.rsc, which is basically the PiCtory file /var/www/revpi/pictory/projects/_config.rsc.

Customers using Revolution Pi CODESYS devices will therefore have to manually configure appropriate PlaceholderFilePath in /etc/CODESYSControl_User.cfg as mentioned below:

For CODESYS Control for Raspberry Pi MC SL - 4.8.0.0

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

For CODESYS Control for Raspberry Pi MC SL - 4.10.0.0

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

Note: When using CODESYS Control for Raspberry Pi MC SL - 4.10.0.0 you may be required
to increase the PlaceholderFilePath from default 1 to 2.This may be due to the CODESYS Control occupying this path internally.

https://forge.codesys.com/forge/talk/Engineering/thread/3b90bda4a1/

Restart CODESYS Control in order to load the new changes from /etc/CODESYSControl_User.cfg.
Alternatively, you could reboot the device, and the changes will be automatically loaded from the user configuration file at the start of CODESYS Control.

sudo service codesyscontrol restart

 

-----------------------------------------------------------------------------------------------------------------------------

1.4.0.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 5-06-2023

Features
- Added support for Connect 4 variants
- Added RevPi CODESYS Node-RED Example

Changes
- Library targeted to CODESYS Runtime V3.5.19.0
- Examples targeted as default for CODESYS Control for Raspberry Pi MC SL - 4.8.0.0

Release Note

CODESYS V3.5 SP19 includes a bug fix. CDS-81506: CODESYS Control SysFile
system file access vulnerability.ForceIecFilePath is activated by default, due to which file access from IEC is now restricted to the configured paths only (file sandbox).

For more details see Advisory 2023-01, which is available on the CODESYS website:

https://customers.codesys.com/index.php?eID=dumpFile&t=f&f=17553&token=cf49757d232ea8021f0c0dd6c65e71ea5942b12d&download=

Release notes for CODESYS V3.5 SP19
https://www.codesys.com/fileadmin/data/Images/System/Releaseinformation/Release-Notes-CODESYS-35190.html

In the Revolution Pi Library for Codesys, file write access under the following folder, /etc/revpi/, is required in order to create a config.rsc file based on devices configured in the CODESYS application project. The CODESYS project using the KUNBUS RevolutionPiBridge IO library creates a configuration file /etc/revpi/config.rsc, which is basically the PiCtory file /var/www/revpi/pictory/projects/_config.rsc.

Customers using Revolution Pi CODESYS devices will therefore have to manually configure PlaceholderFilePath in /etc/CODESYSControl_User.cfg as mentioned below.

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

Restart CODESYS Control in order to load the new changes from /etc/CODESYSControl_User.cfg.
Alternatively, you could reboot the device, and the changes will be automatically loaded from the user configuration file at the start of CODESYS Control.

sudo service codesyscontrol restart

-----------------------------------------------------------------------------------------------------------------------------

1.3.0.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 15-12-2022

Features
- Added support for Core SE and Connect SE variants

Changes
- Library targeted to CODESYS Runtime V3.5.18.0
- RevPiCodesysLibHelp document updated
- Examples targeted as default for CODESYS Control for Raspberry Pi MC SL - 4.6.0.0
- Core/Connect/Compact devices and submodules DI/DO/DIO/MIO shall use word/byte access
  for Digital IO's instead of bit access
- KUNBUS Gateway device description files available for installation in
  Device Repository located to "%USERPROFILE%\Revolution Pi\Devices" folder
- Codesys Development System examples under the Examples folder have been moved
   to a version-specific subfolder.

Bug Fixes
- Fix error in identifying modules in codesys device tree occuring due to
  change in connector listing in SP18
-----------------------------------------------------------------------------------------------------------------------------

1.2.1.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 7-09-2022

Bug Fixes
- Fix error in setting parameter Input1Range for Analogue Input CH1 in AIO module

-----------------------------------------------------------------------------------------------------------------------------

1.2.0.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 12-05-2022

Features
- Provide Codesys access to RevPi Virtual devices

Changes
- Library targeted to CODESYS Runtime V3.5.17.0
- Library uptaded to use CmpCharDevicelib API 3.5.17.0
- RevPiCodesysLibHelp document updated
- Examples targeted as default for CODESYS Control for Raspberry Pi MC SL - 4.4.0.0

Bug Fixes
- Include PWM outputs in I/O Mapping for DO Module
- Skip RevPi Serial Gate update connector status
- Fix mem object Key-value pair for MIO in generated _config.rsc
-----------------------------------------------------------------------------------------------------------------------------

1.1.0.0
-----------------------------------------------------------------------------------------------------------------------------
Date: 9-04-2021

Features
- Added Codesys support for Buster image
- Added MIO device support
- Added Example projects 'RevPiConCAN' and 'Profinet IO-Controller and Profinet IRT Gateway'
- Flat Top Button support added.The button status can be read in Codesys Application

Changes
- piBridgeLeft and piBridgeRight device name used instead of Left and Right
- RevPiCodesysLibHelp document updated
- Examples targeted as default for CODESYS Control for Raspberry Pi MC SL - 4.0.0.0


1.0.1.99 beta
-----------------------------------------------------------------------------------------------------------------------------
Date: 4-12-2020

Features
- Added RevPi Flat device support
- Codesys document update for PR100337 Conntct+ 16GB Codesys
- Added Compact help documentation - English version


1.0.0.99 beta
-----------------------------------------------------------------------------------------------------------------------------
Date: 1-09-2020

Initial beta version for RevPi Codesys Library