I have just worked a bit to make possible read data from SignalK with signalK API and redirect it to OLED screen.
I didnt want to read directly from I2C bus as already openplotter-i2c-read module does and it sends to signalK.
It was tested on my orange pi 5 plus with i2c bus =2 (/dev/i2c-2) and SSD 1306 OLED screen (i2c device address should be 0x3C).
This is customized solution only for 3 sensors as temperature/humidity and pressure (example).
Idea is simple:
- read data from signalK through API (info.sh)
- format / filter data and prepare log file to display (info.log -> info2.log)
- oled128x64 reads info2.log file and it sends to OLED screen , next after 30 s, it turns it off (main program: sensors.sh)
To clear OLED display, please use: ./oled128x64clear /dev/i2c-2 command.
oled128x64 and oled128x64clear were rewritten and based on https://forum.armbian.com/topic/3747-sh1...y-library/
I didnt want to read directly from I2C bus as already openplotter-i2c-read module does and it sends to signalK.
It was tested on my orange pi 5 plus with i2c bus =2 (/dev/i2c-2) and SSD 1306 OLED screen (i2c device address should be 0x3C).
This is customized solution only for 3 sensors as temperature/humidity and pressure (example).
Idea is simple:
- read data from signalK through API (info.sh)
- format / filter data and prepare log file to display (info.log -> info2.log)
- oled128x64 reads info2.log file and it sends to OLED screen , next after 30 s, it turns it off (main program: sensors.sh)
To clear OLED display, please use: ./oled128x64clear /dev/i2c-2 command.
oled128x64 and oled128x64clear were rewritten and based on https://forum.armbian.com/topic/3747-sh1...y-library/