Any way to fix it?
sudo pironman5 -v
1.2.19
You have to go into Dashboard ( IP address : 34001) go in settings and you’ll find oled settings.
Yes, that’s correct. You need to access the dashboard settings page, set the OLED disk, and choose the disk you are using for display.
If you are currently booting from an SD card, please set it to /dev/mmcblk0 and then check if the disk displayed on the OLED screen is correct.
I want show GB not TB and when i swith to my nvme it show still 0/0.2TB
Our software currently has this issue. We will fix it in the next version.
We have determined that when the memory exceeds 100GB, it is converted to 0.1TB.
1 Like
I have one more question what branch i need to edit to build custom 1.2.19 version?
The source code you provided is incorrect. The code you shared is for Pironman4, which is for the Raspberry Pi 4 case, not the Raspberry Pi 5 case.
The correct source code for Pironman5 can be found here:
If you would like to download version 1.2.19 of the Pironman5 software, you can execute the following command:
git clone -b 1.2.19 GitHub - sunfounder/pironman5: Code for Raspberry Pi 5 case (Pironman5) --depth 1
I dont see here any code like disk_info = get_disk_info() xDD
It is a required dependency library.pm_auto/pm_auto/oled_page/disk.py at main · sunfounder/pm_auto · GitHub
I have just got my Pironman5 case , and I am running 1.2.26 and this issue is still here , showing 0.0/0.2TB for my 250GB drive
We have not yet released an update to fix this disk size display issue.
This situation might be a bit complicated. It seems the Raspberry Pi was already connected to WiFi, and then it sent its IP address to EZBlock Studio via Bluetooth. EZBlock Studio uses this IP to connect, but if the connection fails, it reports that the WiFi is not on the same network.
If both your Android device and the robot are indeed connected to the same network, it’s possible that the Raspberry Pi is connected to two networks and sent the wrong IP address, causing Ezblock to fail to connect. Since you already have a screen, mouse, and keyboard connected, you can check the device’s IP address by running the command:
ifconfig
Check the Raspberry Pi’s IP address.
You could also try rebooting the Raspberry Pi. There’s a concern that the IP might have changed, but the data transmitted via Bluetooth hasn’t, leading to connection issues. After the Raspberry Pi reboots, it should automatically reconnect to WiFi. Then you can try connecting with Ezblock again.
You might also check your router, or simply switch to a different WiFi network. Remember to switch the WiFi on both devices if you change networks. It’s recommended to try modifying the WiFi using the WiFi settings within Ezblock, as this change will force an update of the Bluetooth IP information.
In a multi-WiFi environment, you need to be especially careful to prevent the Raspberry Pi from connecting to the wrong WiFi, which would cause connection failure.
Please feel free to provide more screenshots for us to review.