Hello,
another option, to connect a status display like OLED SSD1306 to connect to raspberry.
Show information like ip, cpu, ... 🤩Â
Â
Thanks
PIO
Some series of the eBlocker 2 had a custom LED build in (based on GPIO) that is supported by eBlockerOS already. This shows the status with different color coding & blinking. I.e LED blinks white while updating, blue when booting, orange when active & protecting etc.
Maybe we can leverage this code and/or publish the electronic layout (made by an eBlocker partner).
As I mentioned, this LED kit was made by a partner and we are all software guys. Unfortunately we have no clue about electronic details - but you‘ll see the code for driving the LED shortly 😉
If you are into hardware, I‘happy to send you a LED kit to check it out and share your insights with the community. I have one(!) left to share.
I just startet kind of socialmedia-thing on building a cool and sexy PIeBlocker at another thread here (you'll find the link after this post. It's called PieBlocker-Workshop). It would be serious fun to get the story more populatet and maybe fix that thing with the thumb-up-votes. I'd love to have thumb-down ones...;-)
referring to my last comment:
@ngnb
I read your post, for the status led you need a led with WS2812 Controller (SPI)
the next days i will post the pinout.
PIO
@ngnb
Â
Hi, it is not working with raspberry pi ...
In eblocker there is eblocker-led service on the SPI Pin.
I think it works only on Banana PI (kommercial eBlocker white case)
:o(
The status values for the eblocker-led service are defined here:
https://github.com/eblocker/eblocker-led/blob/develop/lib/eblocker/led/status.rb
To activate a status you send the string "status=..." to localhost at port 9000 as described in the readme:
https://github.com/eblocker/eblocker-led
Unfortunately, I could not get the RGB LED to work on a Raspberry Pi. Maybe the timing of the SPI device is somehow different than on a Banana Pi M2+.
The low-level code for sending the bits via SPI to the LED is here:
https://github.com/eblocker/eblocker-led/blob/develop/lib/eblocker/led/spi.rb
Basically, a short pulse means 0 and a long pulse means 1. The timing specification is at:
@bpr, @all
I looked at the led modul on github, here the result.
This is to do:
At:
/boot/config.txt
change:
dtparam=spi=on
At:
/etc/eblocker-device.properties
change:
device.led.rgb.available = true
Â
Plug in Led (WS2812)
Reboot eBlocker
And now its working ... tested eBlocker 2.5.3 on Raspberry PI 3B
Â
Pin-Out LED (WS2812)
       ________
      /               \
    /                   \
   I                     I
   I                     I
##############
   I      I     I     I
 Din Vdd Gnd Dout
   I      I     I    Â
 19    1    6
Pin on GPIO Port Raspberry PI
Â
is it possible to set these two settings for default?
Â
nice evening 🍺Â
PIO78