Pipower 5 on Pro Max case

I have the Pro Max case and the Pipower 5.

If I use mkdir pipower5 → cd pipower5 → curl -sSL https://raw.githubusercontent.com/sunfounder/sunfounder-installer-scripts/main/pironman5/install.sh -o install.sh followed by sudo bash install.sh --pipower5 I then chose 4 for the Pro Max, I chose to show the dashboard on the 4.3" screen, and reboot.

After rebooting, the dashboard is only partially shown on the 4.3" screen, and none of the data related to the Pipower5 is populated, just the blocks.

Since the Pipower5 is compatible with the Pro Max, what is the secret to actually getting “compatible” Sunfounder products to work together? This has become incredibly tiresome, and frankly, I have literally lost all trust and respect for Sunfounder.

UPDATE: Sunfounder is aware of the issue, and is working on a resolution.

We are currently working on this issue. We will notify you as soon as we have an update or a solution.Thank you for your patience and understanding.

1 Like

First of all, we sincerely apologize for the delay. We underestimated the amount of work required to address these compatibility issues, and the release took a few days longer than we originally expected.

Over the past several days, our engineering and testing teams have been working intensively to resolve the problems. Although the schedule slipped, we’re happy to report that the latest Raspberry Pi OS 64-bit Desktop version has now successfully passed our testing.

The new installation script has been moved to the Pironman 5 repository. Please use the following commands:

For Pironman 5 with PiPower 5 support:
curl -sSL "``https://raw.githubusercontent.com/sunfounder/pironman5/1.3.x/install.sh``" | sudo bash -s -- --pipower5

For Pironman 5 only (without PiPower 5):
curl -sSL "``https://raw.githubusercontent.com/sunfounder/pironman5/1.3.x/install.sh``" | sudo bash

We strongly recommend starting with a fresh Raspberry Pi OS installation before running the installer. This helps avoid conflicts with older installations or previously installed packages.

One reason for the additional complexity is that we have been upgrading PiPower 5 to the new V2 architecture, which uses native Linux drivers. Most PiPower 5 functionality is now implemented directly through Linux drivers rather than user-space services, resulting in better performance, improved reliability, and a more seamless user experience.

Thank you for your patience and understanding while we worked through these issues. We appreciate your feedback and the time you’ve spent helping us identify and resolve these compatibility challenges.

██████╗ ██╗██████╗ ██████╗ ███╗ ██╗███╗ ███╗ █████╗ ███╗ ██╗ ███████╗
██╔══██╗██║██╔══██╗██╔═══██╗████╗ ██║████╗ ████║██╔══██╗████╗ ██║ ██╔════╝
██████╔╝██║██████╔╝██║ ██║██╔██╗ ██║██╔████╔██║███████║██╔██╗ ██║ ███████╗
██╔═══╝ ██║██╔══██╗██║ ██║██║╚██╗██║██║╚██╔╝██║██╔══██║██║╚██╗██║ ╚════██║
██║ ██║██║ ██║╚██████╔╝██║ ╚████║██║ ╚═╝ ██║██║ ██║██║ ╚████║ ███████║
╚═╝ ╚═╝╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═══╝╚═╝ ╚═╝╚═╝ ╚═╝╚═╝ ╚═══╝ ╚══════╝
✓ Install argcomplete
✓ Register bash completion
Setup auto-start
✓ Install service file
✓ Enable pironman5 service
✓ Reload systemd
Configure kernel modules
✓ Add module i2c-dev
Copy device tree overlays
✓ Copy sunfounder-pironman5promax.dtbo
✓ Copy PiPower5 device tree overlay
Run post-install scripts
✓ Migrate RPi.GPIO to rpi.lgpio
Finalize permissions
✓ Set execution permission on work dir
✓ Set final ownership
Write product variant
✓ Ensure work directory exists
✓ Write variant identifier
✓ Write custom module
Configure device tree overlays
✓ Add dtoverlay=sunfounder-pironman5promax to config.txt
✓ Add dtoverlay=sunfounder-pipower5 to config.txt

Error happened:
Cleaning build files…
make[1]: Entering directory ‘/usr/src/linux-headers-6.18.35+rpt-rpi-2712’
make[2]: Entering directory ‘/home/kc5jim/pipower5/driver’
make[2]: Leaving directory ‘/home/kc5jim/pipower5/driver’
make[1]: Leaving directory ‘/usr/src/linux-headers-6.18.35+rpt-rpi-2712’
rm -f sunfounder-pipower5.dtbo
rm -f Module.symvers modules.order
Clean completed.
Building PiPower5 driver v2.1.0…
make -C /lib/modules/6.18.35+rpt-rpi-2712/build M=/home/kc5jim/pipower5/driver EXTRA_CFLAGS=“-I/home/kc5jim/pipower5/driver/include” modules
make[1]: Entering directory ‘/usr/src/linux-headers-6.18.35+rpt-rpi-2712’
make[2]: Entering directory ‘/home/kc5jim/pipower5/driver’
CC [M] src/pipower5_main.o
src/pipower5_main.c:29:10: fatal error: pipower5.h: No such file or directory
29 | #include “pipower5.h”
| ^~~~~~~~~~~~
compilation terminated.
make[4]: *** [/usr/src/linux-headers-6.18.35+rpt-common-rpi/scripts/Makefile.build:292: src/pipower5_main.o] Error 1
make[3]: *** [/usr/src/linux-headers-6.18.35+rpt-common-rpi/Makefile:2050: .] Error 2
make[2]: *** [/usr/src/linux-headers-6.18.35+rpt-common-rpi/Makefile:260: __sub-make] Error 2
make[2]: Leaving directory ‘/home/kc5jim/pipower5/driver’
make[1]: *** [/usr/src/linux-headers-6.18.35+rpt-common-rpi/Makefile:260: __sub-make] Error 2
make[1]: Leaving directory ‘/usr/src/linux-headers-6.18.35+rpt-rpi-2712’
make: *** [Makefile:67: module] Error 2

Please check /tmp/install.log for more details.

(Install log is too large to post. I have included it in my response to Mike in email.)

kc5jim@Pi5-16gb-Pro-Max:~ $ hostnamectl
Static hostname: Pi5-16gb-Pro-Max
Icon name: computer
Machine ID: 8fcd5b9a791048f1961032a3e7280d9b
Boot ID: e5951fca4b324387a1df747d239e2b45
Operating System: Debian GNU/Linux 13 (trixie)
Kernel: Linux 6.18.35+rpt-rpi-2712

Architecture: arm64

Web UI Version
1.2.18

pipower5 doctor
Traceback (most recent call last):
File “/usr/local/bin/pipower5”, line 6, in
sys.exit(main())
~~~~^^
File “/opt/pironman5/venv/lib/python3.13/site-packages/pipower5/_init_.py”, line 87, in main
pipower5 = PiPower5()
File “/opt/pironman5/venv/lib/python3.13/site-packages/pipower5/pipower5.py”, line 45, in _init_
check_pipower5_connected()
~~~~~~~~~~~~~~~~~~~~~~~~^^
File “/opt/pironman5/venv/lib/python3.13/site-packages/pipower5/device.py”, line 39, in check_pipower5_connected
raise IOError(“PiPower 5 driver not loaded. Run ‘pipower5 doctor’ to diagnose.”)
OSError: PiPower 5 driver not loaded. Run ‘pipower5 doctor’ to diagnose.

kc5jim@Pi5-16gb-Pro-Max:~ $ hostnamectl
Static hostname: Pi5-16gb-Pro-Max
Icon name: computer
Machine ID: 8fcd5b9a791048f1961032a3e7280d9b
Boot ID: e5951fca4b324387a1df747d239e2b45
Operating System: Debian GNU/Linux 13 (trixie)
Kernel: Linux 6.18.35+rpt-rpi-2712
Architecture: arm64

Web UI Version
1.2.18

We sincerely apologize for the inconvenience.

Previously, our testing was conducted only on the 64-bit Raspberry Pi OS image available at that time, which was using the 6.12.75 kernel. We had not yet tested the newer 6.18 kernel.

Yesterday, while validating other operating systems, we encountered a similar issue and discovered that the newer system no longer supports the configuration method used by our older installer. After updating our Raspberry Pi system and testing with the newer kernel ourselves, we implemented a fix that resolves this problem.

Could you please run the installation command again? The installer will automatically download the latest version.

Please make sure the installed version is v1.3.16. After the installation is complete, let us know whether the issue has been resolved.

The previous post IS the result of reinstalling as requested.

Le sigh, is this merry-go-round of false promises and false reassurance that everything was tested and worked, the incredible amount of time and money I’ve invested in Sunfounder products, the incredible amount of research and testing that I’ve done for Sunfounder, across several products, only to be let down again and again and again and again, ever going to end?

To be honest, I think the best course of action for me is to divest myself of all the Sunfounder products that I’ve purchased, and that is over a dozen products, and chalk the entire sad affair up to a series of bad purchasing decisions on my part.

The last promise that was made to me was " After updating our Raspberry Pi system and testing with the newer kernel ourselves, we implemented a fix that resolves this problem."

My Pi OS before I began the installation was a clean install, the only thing that was done after the OS install was to run “sudo apt update && sudo apt full-upgrade && sudo rpi-eeprom-update -a”

This is the result of hostnamectl immediately prior to the reinstallation of the Pipower 5 software:

kc5jim@Pi5-16gb-Pro-Max:~ $ hostnamectl
Static hostname: Pi5-16gb-Pro-Max
Icon name: computer
Machine ID: 8fcd5b9a791048f1961032a3e7280d9b
Boot ID: e5951fca4b324387a1df747d239e2b45
Operating System: Debian GNU/Linux 13 (trixie)
Kernel: Linux 6.18.35+rpt-rpi-2712
Architecture: arm64

Besides Pironman 5 Pro Max and PiPower 5, do you have anything else installed on this Raspberry Pi? → NO
Is PiPower 5 connected to the Pro Max through the GPIO header, or are you powering the Pro Max through USB only? → GPIO HEADER
PiPower 5 reads its telemetry data through I2C communication with the Raspberry Pi. If only the USB power connection is being used, the power data cannot be read correctly. This time, you did not send us any installation error messages. Does that mean the installation completed successfully without any errors? → NO ERRORS

kc5jim@Pi5-16gb-Pro-Max:~ $ i2cdetect -y 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: – – – – – – – –
10: – – – – – – – – – – – – – – – –
20: – – – – – – – – – – – – – – – –
30: – – – – – – – – – – – – 3c – – –
40: – – – – – – – – – – – – – – – –
50: – – – – – – – – – – – – 5c – – –
60: – – – – – – – – – – – – – – – –
70: – – – – – – – –
kc5jim@Pi5-16gb-Pro-Max:~ $ pipower5 doctor

=======================================================
PiPower 5 Doctor

Hardware & Driver
✓ I2C device (0x5C)
✗ sysfs interface → Driver not loaded or device not present. Reboot or run ‘sudo modprobe pipower5’.
✗ kernel module loaded → pipower5 module not loaded. Run ‘sudo modprobe pipower5’.
✗ power_supply registered → Power supply not registered. Driver may need reload.
✓ dtoverlay in config.txt
✓ device tree blob (.dtbo)

Module not loaded
→ Run: pipower5 doctor --fix

kc5jim@Pi5-16gb-Pro-Max:~ $ pipower5 doctor --fix

=======================================================
PiPower 5 Doctor

Hardware & Driver
✓ I2C device (0x5C)
✗ sysfs interface → Driver not loaded or device not present. Reboot or run ‘sudo modprobe pipower5’.
✗ kernel module loaded → pipower5 module not loaded. Run ‘sudo modprobe pipower5’.
✗ power_supply registered → Power supply not registered. Driver may need reload.
✓ dtoverlay in config.txt
✓ device tree blob (.dtbo)

Module not loaded
→ Running modprobe pipower5…

=======================================================
kc5jim@Pi5-16gb-Pro-Max:~ $ sudo modprobe pipower5
modprobe: FATAL: Module pipower5 not found in directory /lib/modules/6.18.34+rpt-rpi-2712
kc5jim@Pi5-16gb-Pro-Max:~ $

kc5jim@Pi5-16gb-Pro-Max:~ $ hostnamectl
Static hostname: Pi5-16gb-Pro-Max
Icon name: computer
Machine ID: 20f5bb76b24d4bd9a7811d26cccec8f7
Boot ID: 751681fba34047499831e37dc7189f9a
Operating System: Debian GNU/Linux 13 (trixie)
Kernel: Linux 6.18.34+rpt-rpi-2712
Architecture: arm64
kc5jim@Pi5-16gb-Pro-Max:~ $

No fan control in the dashboard.

We’re sorry for the frustrating experience you’ve had.Our team has been in contact with you via email, and our General Manager will continue to follow up with you directly to discuss the matter in detail.

1 Like