Posts made by bertf

@cleve
The repair form is completed and the unit is on it's way to you.

@cleve
No problem. The serial number is 725.
Kind regards,
Bert

Hi @cleve
I'm not sure. I use the images from the Unipi-website and the standard repo's that come with them. I have local backups from 'patron-base-os_12.20240701.0' and 'patron-node-red_12.20240701.0'. I will have used one of these images to initially migrate from Debian 10 to 12. The reinstall as mentioned above is done with image 'patron-node-red_12.20240917.1'.
Kind regards,
Bert

@cleve
Sorry for my very late respons. As suggested I did a complete reinstall of the most recent Unipi Patron OS - Debian 12, but also a reinstall of the earlier Debian 10. I tried several times but both OS-versions didn't reconnect the device to the DI/DO/RO's. Same message in the kernel log each time: "spi channel looks empty". Can it be a hardware problem?

@cleve
Hello Krystof,
yes, run1 and run2 are blinking (1 sec on, 1 sec off and so on).

Hi,
All the DI/DO's on my M207 have stopped working. I cannot connect to them anymore using the Evok or modbus API. The problem seems to have occurred after updating from evok/bookworm 3.0.5.1~bookworm to evok/bookworm 3.0.6.1~bookworm, but downgrading evok doesn't solve the problem.

The kernel log shows that the device isn't able to connect to spi2.0 en spi2.1:
Sep 28 13:02:19 unipi kernel: unipi-id unipi-id: Found PLC M207 (family Patron)
Sep 28 13:02:19 unipi kernel: imx-sdma 302c0000.dma-controller: firmware found.
Sep 28 13:02:19 unipi kernel: imx-sdma 302c0000.dma-controller: loaded firmware 4.5
Sep 28 13:02:19 unipi kernel: imx-sdma 302b0000.dma-controller: firmware found.
Sep 28 13:02:19 unipi kernel: w1_master_driver w1_bus_master1: Attaching one wire slave 28.3c94e38178aa crc 4e
Sep 28 13:02:19 unipi kernel: imx-sdma 30bd0000.dma-controller: firmware found.
Sep 28 13:02:19 unipi kernel: spi_master spi2: will run message pump with realtime priority
Sep 28 13:02:19 unipi kernel: unipi-spi spi2.1: spi channel looks empty
Sep 28 13:02:19 unipi kernel: unipi-spi spi2.0: spi channel looks empty
Sep 28 13:02:19 unipi kernel: unipi-spi: Driver registered. Major Version: 2.52:2024:04:26
Sep 28 13:02:19 unipi kernel: w1_master_driver w1_bus_master1: Attaching one wire slave 28.3cffb55644a1 crc 47
Sep 28 13:02:20 unipi kernel: w1_master_driver w1_bus_master1: Attaching one wire slave 28.3cbbe381d791 crc de
Sep 28 13:02:20 unipi kernel: w1_master_driver w1_bus_master1: Attaching one wire slave 28.3cbae381c1a3 crc 79
Sep 28 13:02:20 unipi kernel: w1_master_driver w1_bus_master1: Attaching one wire slave 28.3c41e3815f93 crc 3b
Sep 28 13:02:20 M207-sn725 kernel: w1_master_driver w1_bus_master1: Attaching one wire slave 28.3c4ee3814c1b crc 5a
Sep 28 13:02:22 M207-sn725 kernel: fec 30be0000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
Sep 28 13:02:22 M207-sn725 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Any ideas what is the problem? Thanks in advance!

Best regards,
Bert