Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DietPi Buster + Raspberry Pi 4 works well! #991

Open
raspberry-pi-maker opened this issue Feb 22, 2020 · 6 comments
Open

DietPi Buster + Raspberry Pi 4 works well! #991

raspberry-pi-maker opened this issue Feb 22, 2020 · 6 comments

Comments

@raspberry-pi-maker
Copy link

When I used Rasbian Buster with Rpi4 issue #483 occcurs. I have to use an old Rasbian Jessie. But the Rpi 4 doesn't support Jessie. As a result, I have to use Rpi 3 instead of 4.
Yesterday, I tested DietPi Buster with Rpi 4. The RGB LED matrices display is good. No flickering.
I've write the test process in my blog (https://iot-for-maker.blogspot.com/2020/02/led-5-raspberry-pi-4-dietpi-buster.html). I hope this can help you who want to use Rpi 4.

@mikecann
Copy link

mikecann commented Feb 26, 2020

This is good to know. Im about to embark on a project involving 6 x 64x64 panels using a pi 4 and the Electrodragon HAT.

I calculated here (#989) that I would need a max of 200w. I noticed that you got a 10a supply for yours, was that enough?

@raspberry-pi-maker
Copy link
Author

When all the RGB LED pixels are on, max power might be needed.
However, this rarely happens.
Of course, it's a good idea to have a power supply that can handle the maximum power.
In my case, considering the cost, there was no big problem using 5V10A to handle P3 64X32 4EA.

@marcmerlin
Copy link
Contributor

Thanks @raspberry-pi-maker I was about to ask @hzeller if there was any benefit to using an rPi4 over a 3?
From what I understand the rPi3 is already able to output faster than the panels are able to absorb the input and that while 256x256 is possible with an electrodragon active-3 board, it's pushing the limits of what can be done with 3 channels/1 Pi (refresh rate and color depth are not great).
My assumption so far is that an rPi4 doesn't change this and 256x256 is still more or less the limit.
I opened
#971 5703107 to write this to the best of my understanding.

@mikecann
Copy link

@marcmerlin I actually found that the pi4 was cheaper than the pi3 thats why I chose it. Plus the extra power lets me run more complex code or run in a higher level language or something.

@hzeller
Copy link
Owner

hzeller commented Feb 27, 2020

Yes, the faster internal processing makes a Pi4 more desirable than a Pi3 even if the clock to the matrix is at their limit.

@raspberry-pi-maker
Copy link
Author

I agree with @hzeller .
Even though the rPi3 has enough processing power to GPIO handling, making the contents to display is also important.
I like to use OpenCV to create the contents. The greater the processing power, the faster the OpenCV's processing speed. Therefore, rPi4 is more advantageous than rPi3 when working with OpenCV such as video display.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants