NEW feature. E-ink #48

Open
opened 2026-10-05 05:31:25 +02:00 by adam · 2 comments
Owner
First test. 😉 https://youtu.be/5zWcB2fp9pM?si=NeCK4KrWzQeXxW-O <!-- github-sync-id:2216948269 -->
Author
Owner

Ok but why, for what purpose? My IGate/Digi stations are automatic stations and I don't look at them, this feature is better for tracker. I can see the statistics etc. via website or other way on my TV screen.

If you are connected to grid you don't need to save power and if you want to save power, go low power mode etc. then you don't want to use any screen.

This is just my opinion about this feature.

Ok but why, for what purpose? My IGate/Digi stations are automatic stations and I don't look at them, this feature is better for tracker. I can see the statistics etc. via website or other way on my TV screen. If you are connected to grid you don't need to save power and if you want to save power, go low power mode etc. then you don't want to use any screen. This is just my opinion about this feature. <!-- github-comment-id:2029677551 -->
Author
Owner

Well. For what purpose?
Maybe just experiment, curiosity, interest, to explore the possibilities.
Not an option for Tracker because it is slow due to frequent screen refreshes.
But for Igate it is suitable and especially because I only update the information on the display when there is a change. This also speeds up the time to run the code once.
I am aware that you don't watch this all the time and there are other options (web, etc).
But then I could ask the question, why is the oled display implemented in the code? ;)
Maybe as you saw it is not an accidental choice of HWSL since it has no display. Precisely because I find the display unnecessary for igate. And here I go back to my first sentence: curiosity, experiment...
(You know that this is not my first attempt. Just a few: tracker T-deck, Helteck wireless tracker, lilygo T-QT pro, dualscreen oled.)
IMG_20240312_170005
IMG_20240307_175422
IMG_20240305_163929

Well. For what purpose? Maybe just experiment, curiosity, interest, to explore the possibilities. Not an option for Tracker because it is slow due to frequent screen refreshes. But for Igate it is suitable and especially because I only update the information on the display when there is a change. This also speeds up the time to run the code once. I am aware that you don't watch this all the time and there are other options (web, etc). But then I could ask the question, why is the oled display implemented in the code? ;) Maybe as you saw it is not an accidental choice of HWSL since it has no display. Precisely because I find the display unnecessary for igate. And here I go back to my first sentence: curiosity, experiment... (You know that this is not my first attempt. Just a few: tracker T-deck, Helteck wireless tracker, lilygo T-QT pro, dualscreen oled.) ![IMG_20240312_170005](https://github.com/richonguzman/LoRa_APRS_iGate/assets/22783982/d21fa28d-7363-4e02-b32a-b0ff85c4135f) ![IMG_20240307_175422](https://github.com/richonguzman/LoRa_APRS_iGate/assets/22783982/6c222d79-30a5-4963-8093-e2ccaf0c4750) ![IMG_20240305_163929](https://github.com/richonguzman/LoRa_APRS_iGate/assets/22783982/a238ed75-6ae6-4ea9-a4e6-012faee89538) <!-- github-comment-id:2030044785 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/LoRa_APRS_iGate#48