Hi,

We are currently interested in getting coprocessor board statuses to check that the underlying hardware is still working as expected. For instance, we would like to know if all the coprocessor boards are up and running and/or all their I/Os are also functioning.

Currently, we are relying on:

/sys/devices/platform/unipi_plc/io_group[1-3]

What we successfully checked so far is that unplugging a coprocessor board made its corresponding /sys/devices/platform/unipi_plc/io_group[1-3] vanish from the sysfs tree. However, if we only unplug the relay board from its coprocessor board, the relays still appear in the sysfs tree and can still be read from/written into.

1. Are there any ways to check that relays (or any other kinds of I/Os) are actually plugged in and physically up and running?
2. I saw there are logs in dmesg that tell when a given board is not plugged in e.g. "[ 8.312951] UNIPISPI: Probe did not detect a valid UniPi device at CS3". Can we get this information elsewhere (e.g. through sysfs) or do we have to parse dmesg?
3. What is the meaning of the status we get in /sys/devices/platform/unipi_plc/io_group2/driver/spi0.2/of_node/status? What would "okay" mean exactly?
4. sysfs-platform-unipi.txt tells us that accessing some files from sysfs "Returns an error if no valid combination corresponding to a UniPi device can be found" in some cases. What kind of error would that be?

In advance, thank you.

Hi,

We would also be interested in a bullseye upgrade for Unipi Neuron Series as we are currently facing issues with the systemd version that comes with buster.

Any updates on this matter?

Best regards,

Romain

Hi all,

Are there any ways to programmatically retrieve PLC's serial number (e.g. on Neuron PLCs)?
Also, is the serial number we get from reading the QR code unique across all unipi products (Neuron, Patron, Axon, ...)?

In advance, thank you.

Best regards,

Romain

Hi Martin,

Just for the record, we successfully menderized neuron-opensource-os_image-20210806.0 and the PLC now boots up. There seems to be an issue with u-boot 2020.01 that mender uses by default. Using version 2019.01 works just fine.

Best regards,

Romain

Hello,

We are currently studying your Neuron M203 PLC and as part of our study we want to ensure we can update that device remotely. We are planning on using Mender (mender.io) to do so but we are currently stuck at boot time after converting your latest image.

We followed Mender's debian image conversion guide on neuron-opensource-os_image-20210401.0's image file. Flashing your original image gives us a bootable device that we can ssh to. However when using mender-convert the converted image does not boot completely and the network interface does not get turned on and we cannot ssh at all.

Did you ever work with Mender? If so, would you have some ideas on what could have gone wrong?

Do not hesitate if you need further details from us.

In advance, thank you.