The Industrial Raspberry Pi Forum

Software:

CODESYS Version: 3.5 SP20 Patch 3 (64-bit)
Revolution Pi Library for CODESYS: 2.0.0.0
CODESYS Control for Linux ARM64SL: 4.13.0.0
Operating System: Debian 11.7
Kernel Version: 1:9.20230720+1-5.10.152-1+revpi11+1 (arm64)
Development Environment: Windows 10

Hardware:

Controller: RevPi Connect 4 (Firmware 2.0.0.0)
I/O Module: RevPi_DIO (Firmware 2.0.0.0)

PiCtory Configuration:

Added Connect 4 and DIO to the configuration (left side in PiCtory UI).
Saved the configuration as "Start-Config."
Verified functionality via the piTest terminal tool:
Successfully changed LED colors on Connect 4.
Set output values on DIO, which operated a Fischertechnik conveyor belt.


I attempted to follow the tutorial "CODESYS Commissioning with RevPi Connect 4" (https://youtu.be/EF-Jtd6mPLE?si=y5q91QT9dllj12YQ). But with downloading the latest packages.

After logging into the device in CODESYS, the expected green refresh icon beside the Connect 4 is replaced by a warning icon.
Error Message: "The bus is not running."
Status Details: The Connect 4 status displays a message indicating a configuration error.

Could you help identify the cause of the configuration error and guide me on resolving the "bus is not running" issue?

Thanks!

Hi Matistikoff, thanks for your detailed report and the details and photos on this, this is wonderful. CODESYS becomes the leading system and overrides the PiCtory configuration. Please try updating the RevPi DIO module firmware: https://revolutionpi.com/en/tutorials/i ... are-update If this does not succeed, then run a test with CODESYS example project Blinking LED without the DIO module.

Edit: PiCtory seems to be of version 2.1.0 due to which config.rsc is not being generated by CODESYS, leading to a configuration error.
That can be checked in CODESYS log too.

The procedure to update PiCtory is mentioned in release notes for the RevPi CODESYS library.

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

Check current installed PiCtory package Install the latest PiCtory Debian packet If CODESYS Control Linux ARM 32/64 bit is installed on RevPi Device, restart it to load the changes after updating PiCtory packet. Alternatively, you could reboot the device

I updated firmware and debian packet and it worked, thanks dirk, you are a little legend for this!

Hey thank you very much that's wonderful, I'm not completely alone even if it seems that way Amar is very helpful here in the background!