OLED screen, fans and fan LEDs stopped working properly - pironman 5

My Pironman 5 case is behaving strangely.

After booting up, I see the green light in the lightpipe, and LEDs working on the fans, then the OLED screen displays as normal but for less than 2 seconds, then it says “POWEROFF” the fan LEDs turn off, the fans stop rotating and the lightpipe light goes off.

BUT the pi5 responds as usual to the CLI and WinSCP. It is running. I have a web server on it and this operates as normal.

I see a similar case mention with a pironman 4 and power supply issues, so I will say that I am using the official RPi5 power supply, plugged into the pironman PCB via the USBC power socket. As I have a spare official RPi5 power supply I tried that, and the result is the same.

I did a full update and next I did this:
roy @ pi5: ~/pironman$
sudo python3 install.py --no-dep

result:

pironman 2.2.9 install process starts for roy:

Kernel Version:
Linux pi5 6.6.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.47-1+rpt1 (2024-09-02) aarch64 GNU/Linux

OS Version:
Description: Debian GNU/Linux 12 (bookworm)

PCB info::
Revision : d04170
Model : Raspberry Pi 5 Model B Rev 1.0

Config gpio

  • enable i2c … Done
  • enable spi … Done
  • enable i2c in config… Done
  • enable spi in config… Done
  • set core_freq to 500… Done
  • set core_freq_min to 500… Done
  • config gpio-poweroff… Done
  • config gpio-ir… Done
    create WorkingDirectory
  • create dir… Done
  • copy service file… Done
  • add excutable mode for service file… Done
  • copy bin file… Done
  • add excutable mode for bin file… Done
  • copy config file… Done
  • enable the service to auto-start at boot… Done
  • run the service… Done
    Finished.
    Whether to restart for the changes to take effect(Y/N):
    Y

After reboot, it responded as above. I powered off, waited for all the lights to go out, then powered back up. Same result.

/opt/pironman/log shows (the last entry, various repeats of this above this entry)
------------------------24/09/24 18:36:35------------------------
pironman version: 2.2.9
username: root
config_file: /opt/pironman/config.txt

Kernel Version:
Linux pi5 6.6.47+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.47-1+rpt1 (2024-09-02) aarch64 GNU/Linux

OS Version:
Description: Debian GNU/Linux 12 (bookworm)

PCB info:
Revision : d04170
Model : Raspberry Pi 5 Model B Rev 1.0

24/09/24 18:36:35,129 [DEBUG] power_key_pin : 16
24/09/24 18:36:35,129 [DEBUG] fan_pin : 6
24/09/24 18:36:35,129 [DEBUG] update_frequency : 0.5
24/09/24 18:36:35,129 [DEBUG] temp_unit : C
24/09/24 18:36:35,129 [DEBUG] fan_temp : 50.0
24/09/24 18:36:35,129 [DEBUG] screen_always_on : False
24/09/24 18:36:35,129 [DEBUG] screen_off_time : 60
24/09/24 18:36:35,129 [DEBUG] rgb_enable : True
24/09/24 18:36:35,129 [DEBUG] rgb_style : breath
24/09/24 18:36:35,129 [DEBUG] rgb_color : 0a1aff
24/09/24 18:36:35,129 [DEBUG] rgb_blink_speed : 50
24/09/24 18:36:35,129 [DEBUG] rgb_pwm_freq : 1000
24/09/24 18:36:35,129 [DEBUG] rgb_pin : 10

24/09/24 18:36:35,139 [DEBUG] rgb_strip init failed:
ws2811_init failed with code -3 (Hardware revision is not supported)
24/09/24 18:36:35,156 [DEBUG] oled init success
24/09/24 18:36:35,162 [DEBUG] fan init success
24/09/24 18:36:35,162 [DEBUG] power_key init success
24/09/24 18:36:35,170 [DEBUG] Get IP: 192.168.0.105


/opt/pironman/config.txt (omitting comment lines)
[all]

temp_unit = C
fan_temp = 50
screen_always_on = False
screen_off_time = 60
rgb_enable = True
rgb_style = breath
rgb_color = 0a1aff
rgb_blink_speed = 50
rgb_pwm_freq = 1000
rgb_pin = 10

This has worked for months - it first failed a few days ago.

I also did a full RPi OS update a few days ago, and this was a major update affecting many libraries. Has that introduced an incompatibity with the pironman 5 software? The comment “ws2811_init failed with code -3 (Hardware revision is not supported)” may be significant.

It appears that the software you installed is incorrect.
You have installed the Pironman V2 software, but you should be using the Pironman5 software, as your system is based on the Pironman5.

Please ensure that you are following the correct tutorial for the Pironman5 installation. The Pironman software is designed for the PI4, while Pironman5 is specifically for the PI5.

I recommend that you carefully check the tutorial you are following and consider reinstalling the system before installing the Pironman5 software according to the appropriate instructions.Set Up on Raspberry Pi/Ubuntu/Kali/Homebridge OS — SunFounder Pironman 5 documentation

Thanks for your help.

As I mentioned, this has been running pironman5 successfully for months - since June in fact and it first failed a few days ago.

Only when it first went wrong, did I copy from an answer to someone with the same symptoms but with a pi 4, so that is how I ended up with the wrong software installed (in addition to pirnoman5).

This explains present problems - I should have been more careful with what I copied.

But it doesn’t explain why I had the problem in the first place after making no changes apart from the big system update I mentioned (that I had done on all my Pi’s).

Anyway, I renamed all existing pironman5 folders, and the pironman folder that I should not have installed.

I followed the installation instructions, and the OLED screen and fan LEDs are now working.

I have one remaining query:
my EEPROM configuration file showed:
[all]
BOOT_UART=1
BOOT_ORDER=0xf146
POWER_OFF_ON_HALT=1

after sudo rpi-eeprom-config -e
I changed to
BOOT_ORDER=0xf41
as instructed. It then says

[all]
BOOT_UART=1
BOOT_ORDER=0xf41
POWER_OFF_ON_HALT=1
etc., etc. and
UPDATE SUCCESSFUL

But if I examine it with sudo rpi-eeprom-config -e again, I can see it has reverted to 0xf146
Is this significant?

Thanks.

It will not affect the setup. The configuration is mainly based on your needs.

POWER_OFF_ON_HALT=1: This configures the shutdown to disable the GPIO power. To prevent devices powered by the Raspberry Pi GPIO, such as OLED screens and RGB fans, from remaining active after shutdown, the GPIO power must be disabled.
BOOT_ORDER=0xf416: This configures the boot order.
If you have both an SD card and an SSD connected and want to boot the system from the SSD, you should modify the configuration file with sudo rpi-eeprom-config --edit to:

BOOT_ORDER=0xf416

This means:
6: First try NVMe SSD
1: Then try SD card
4: Then try USB

If you want to boot from the SD card while both an SD card and an SSD are connected, modify the configuration file to:

BOOT_ORDER=0xf41 (or BOOT_ORDER=0xf461)

Please refer to the link:Copy OS from Micro SD to NVMe SSD — SunFounder Pironman 5 documentation

1 Like