Hope you read the previous part of the departure board.
Else check the pictures. ;)
--
So I think that the departure board was OKAY, and I kept there. But the reality was that it also needed to be improved a lot.
Energy consumption, component quality stress, fragility, versatility, UTILITY.
I must highlight again that I have "recovered" this screen from a laptop, then I bought a frame kit from Aliexpress. I remember that the frame was really expensive but was precise. It offered a very tiny room for the Raspberry, which I thought it could actually burn the display, but that didn't happened. The display can support a lot of heat apparently.
The deployment started to be really important, since every iteration you could emulate sure, but then eventually it must be added to the device like several times per minute. I have created few scripts for versatility.
I have found problems with the browser. At the begging I was using chromium, which opened with an alert of low ram, that was easy to disable; the issue was the time for starting was a lot, so I have replaced it by a solution that doesn't use X to load the OS.
Qt/EGLFS-based browser
I have discovered that I could use as little as 64-75mb of ram to render my Angular app with this type of browser (kiosk_fb), which is a Frame Buffer browser.
We don't have window manager.
Originally the project was around 300-400mb to be loaded just because the browser, so this is a perfect fit.
My choice uses Qt's GPU acceleration, not linuxfb. Practical and minor tradeoffs.
Home Assistant
Because I also needed to know the temperature at home, I have made some services to get the information from specific sensors.
Keep it up for a next part and check out the repo!
https://github.com/kevinch3/rpiz

Comments
Post a Comment