Hello Codesys Support Team,
Does the CODESYS Control for Raspberry Pi MC SL v4.6.0.0 or higher support Compute Module 4s (CM4s)?
The datasheet of CODESYS Control for Raspberry Pi MC SL mentions support for Compute module 3 and Compute module 4 but not Compute Module CM4s.

We have Revolution Pi devices (Connect S / with CM4s) running CODESYS Control for Raspberry Pi MC SL where the Control Runtime crashes after some days.The issue has been raised my multiple users on this forum.The same application runs well on Connect3 (with CM3) devices.

A sample Codesys Connect S project is attached which also contains Core Dump, codesyscontrol log for which the application crashes after couple of days as seen in codesyscontrol log snippet.

2023-04-27T14:15:52Z, 0x00000018, 1, 0, 4, Network interface <interface>ether 1</interface> at router <instance>2</instance> registered
2023-04-27T14:15:52Z, 0x00000018, 1, 0, 1, Setting router <instance>2</instance> address to <address>(003d)</address>
2023-05-05T09:42:34Z, 0x00000001, 1, 0, 35, CODESYS Control shutdown...
2023-05-05T09:42:35Z, 0x00000114, 2, 1, 0, !!!! Warning: SysTaskJoin [CMCommCycleTask]: error Connection timed out
2023-05-05T09:42:36Z, 0x00000124, 1, 0, 0, Provider 'AlarmManager' (version 0x305121e) unregisterd at the OPC UA server.

Best Regards,
Amar Jadhav
KUNBUS GmbH,
Heerweg 15C, 73770 Denkendorf

Hi,
could you please give 4.8.0.0 version a try? (Current version)
Regards
Edwin

Hi Edwin,
Thank you for the initial suggestion.I am currently testing with CODESYS Control for Raspberry Pi MC SL v4.8.0.0 and it would take couple of days to check if the issue exists with latest runtime.

I have an question with SP19

In SP19, there is a bug fix CDS-81506 - CODESYS Control SysFile system file access vulnerability

In the Revolution Pi Library for Codesys, a file r/w access under following folder /etc/revpi/ is required.
The IO driver basically writes a configuration specific to Revolution Pi in file /etc/revpi/config.rsc

From SP19 onwards the customers using Revolution Pi CODESYS devices will have to manually add a path in /etc/CODESYSControl_User.cfg
eg:
[SysFile]
PlcLogicPrefix=1
PlaceholderFilePath.1=/etc/revpi, $configrsc$

Since ForceIecFilePath=1 (new default), is there any other alternative with which the settings can be embedded in IO driver library instead of manually having the users to configure the file access settings on each of the field devices by editing CODESYSControl_User.cfg?

Regards,
Amar

The issue of crashing of CODESYS Control on CM4s is resolved in CODESYS Control for Raspberry Pi MC SL v4.8.0.0.