The Industrial Raspberry Pi Forum

Having successfully got my DIO test code working yesterday, I was disappointed it failed today.

I noticed that the DIO module had a RED power LED and the IN and OUT LEDs were off.
I opened PiCtory via Cockpit where the configuration displayed correctly, then I clicked Tools > Reset Driver and all the LEDs on the DIO module turned green and the DIO test code sprang back into life.

Any idea why the start-config. failed to load on startup?

Hi KristinH,I understand that sometimes the modules show a red PWR LED after a restart. Then a reset driver or “piTest -x” makes it work again, right?There may be a newer version of the kernel and the PiControl driver. Update the system:
https://revolutionpi.com/documentation/ ... ng-updates

Everything is up-to-date but every time I reboot or power cycle I have to reconnect to the piControl process.

When I get 2 red power LEDS, "piTest -x" doesn't work: And neither does reset driver from PiCtory. I have to reload start-config., save as start-config. and reboot.

When I get a red LED on the DIO and green on the RevPi, "piTest -x" does work.

How can I check that start-config. is configured correctly, or is there a work around to ensure this starts without manual intervention?

Thanks

Hello KristinH,
okay, sounds strange to me in case "piTest -x" returns permission issues.

Can you install the latest image using the steps from this helpful checklist:
https://kunbus-gmbh.atlassian.net/servi ... /836468748

Then the erroneous "operation not permitted" behavior should stop.
Furthermore, your system will receive all the improvements for communication and stabilization via PiControl with the update.

If these problems persist, please send us an SOS report using these instructions:
https://kunbus-gmbh.atlassian.net/servi ... CONFLUENCE

Good morning,

Both RevPis have the latest 250124 bookworm lite image installed, both are up-to-date.
Both RevPis are configured in PiCtory with one DIO and one Con CAN.
Both failed to connect to the DIO this morning using PiTest -x or PiCtory Reset Drivers
After a soft reboot one came up with two red lights, the other with only one red light and that one responded to a PiCtory reload start-config. and Reset Drivers.
After a power cycle both came up with one red LED but this time both responded to PiTest -x
SOS reports are attached

I noticed the following lines in your /boot/firmware/config.txt:

dtparam=spi=on
dtparam=i2c_arm=on
enable_uart=1

Please remove them as they result in malfunction of the device. Did you eg. change things within raspi-config? These lines are not present with the default image.

Nicolai

Thank you, I have removed those lines from the RevPi that had these lines, but the other one didn't. I've compared both and they're the same now.

On power cycle they both came up with one red LED on the DIO and recovered with piTest -x

Any idea why they're still failing to initialise correctly?

The other sos report also contains

enable_uart=1

in /boot/firmware/config.txt?

Sorry missed mentioning that. They're both without any of those lines and always fail to start on reboot or power cycle. At best I can start them with piTest -x, at worse I have to completely reload everything and power cycle.
(yes, I've updated and upgraded them today)

What does

dmesg | grep -E '(serial|piControl|pibridge)'

print in case of failure and after a successful reset?