Taking the non-working DI module home to test on bench... will update then. Tested DI module with my bench Core 3+ Bullseye, same result. Reverted image to Stretch, which then was able to detect the DI module... conclusion, DI module with v1.4 firmware will not communicate with Bullseye image. pi@Re...

I have confirmed the first-to-the-left DI module is functioning correctly with LED indications and piTest -d command. I have removed the functioning DI module from the chain/bridge and have placed the second DI module (that is flashing red power LED) in the first-to-the-left position. Clean PiCtory ...

Update: after reviewing the module firmware update procedure here https://revolutionpi.com/en/tutorials/images/firmware-update I started a clean PiCtory config and added a single DI module. piTest reports success pi@RevPi43743:~ $ piTest -d Found 2 devices: Address: 0 module type: 105 (0x69) RevPi C...

RevPi DI modules
product number SKU 100195
serial numbers: 46688, 49297
revisions 1.3

Contents of /var/log/kern.log Mar 12 20:13:47 RevPi43743 kernel: [ 0.000000] Booting Linux on physical CPU 0x0 Mar 12 20:13:47 RevPi43743 kernel: [ 0.000000] Linux version 6.1.46-rt13-v7 (support@kunbus.com) (arm-linux-gnueabihf-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian)...

Image installed/downloaded: 2024-02-15-revpi-bullseye-armhf.img Kernel version: pi@RevPi43743:~ $ uname -a Linux RevPi43743 6.1.46-rt13-v7 #1 SMP PREEMPT_RT Mon, 5 Feb 2024 15:02:39 +0100 armv7l GNU/Linux pi@RevPi43743:~ $ dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version...

Hello RevPi community, I have recently updated a RevPi Connect+ from Stretch to Bullseye. Before the update, I saved the Pictory project and transferred to fresh install. All went well, saved to Start-Config, Reset Driver, rebooted etc. I am unable to connect to two RevPi DI modules that are connect...

+1 for single-time modbus write function

I am developing some PHP web pages that run directly on my RevPi Connect 4 4GB/32GB. I noticed this morning that the apache logs had filled up the /var/log mount. I realize this is more of a general linux sysadmin question. I am looking for suggestions on how best to resolve this. Expand /var/log vo...

Upon further investigation I noticed also that the device did not have the correct ethernet address. I followed the image write procedure again, and it is now functioning. I believe the first time I may have physically rebooted the device rather than issued a 'sudo reboot', and this may have left ce...