starred/OpenEPaperLink
1
0
Fork 0
mirror of https://github.com/OpenEPaperLink/OpenEPaperLink.git synced 2026-03-21 00:04:28 +01:00
Code Issues 472 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #383] Gicisky 2.13 inch BLE Tag Incorrect Size #1883

New Issue
Closed
opened 2026-03-20 20:07:03 +01:00 by sascha_hemi · 9 comments
sascha_hemi commented 2026-03-20 20:07:03 +01:00
Owner
Copy Link

Originally created by @Jestinator on GitHub (Oct 25, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/383

I have a Gicisky 2.13 inch TFT BLE Tag which is found by the AP fine but the images are distorted.

I've found that the image being sent is 250x132 however the display is 250x122.

I've tried editing the tagtype file BA.json on the AP and it shows 250x122 on the tag info screen but I can see in the log on the device that the image is encoded to 250x132 regardless. This results in an unreadable display.

Originally created by @Jestinator on GitHub (Oct 25, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/383 I have a Gicisky 2.13 inch TFT BLE Tag which is found by the AP fine but the images are distorted. I've found that the image being sent is 250x132 however the display is 250x122. I've tried editing the tagtype file BA.json on the AP and it shows 250x122 on the tag info screen but I can see in the log on the device that the image is encoded to 250x132 regardless. This results in an unreadable display.
sascha_hemi added the bug label 2026-03-20 20:07:03 +01:00
sascha_hemi commented 2026-03-20 20:07:04 +01:00
Author
Owner
Copy Link

@atc1441 commented on GitHub (Oct 25, 2024):

Hey, this display is not fully supported right now.
This is the expected outcome

<!-- gh-comment-id:2437432755 --> @atc1441 commented on GitHub (Oct 25, 2024): Hey, this display is not fully supported right now. This is the expected outcome
sascha_hemi commented 2026-03-20 20:07:05 +01:00
Author
Owner
Copy Link

@jonasniesner commented on GitHub (Oct 26, 2024):

I updated the wiki to avoid confusion in the future

<!-- gh-comment-id:2439547876 --> @jonasniesner commented on GitHub (Oct 26, 2024): I updated the wiki to avoid confusion in the future
sascha_hemi commented 2026-03-20 20:07:05 +01:00
Author
Owner
Copy Link

@atc1441 commented on GitHub (Oct 26, 2024):

Thank you @jonasniesner

<!-- gh-comment-id:2439549023 --> @atc1441 commented on GitHub (Oct 26, 2024): Thank you @jonasniesner
sascha_hemi commented 2026-03-20 20:07:05 +01:00
Author
Owner
Copy Link

@azdlowry commented on GitHub (Dec 10, 2024):

Is there a specific issue making the 2.13 inch difficult to support or is it just that no one has looked at it yet? I bought the wrong ones accidently and have some time to look at fixing them at the moment.

<!-- gh-comment-id:2531820555 --> @azdlowry commented on GitHub (Dec 10, 2024): Is there a specific issue making the 2.13 inch difficult to support or is it just that no one has looked at it yet? I bought the wrong ones accidently and have some time to look at fixing them at the moment.
sascha_hemi commented 2026-03-20 20:07:05 +01:00
Author
Owner
Copy Link

@atc1441 commented on GitHub (Dec 10, 2024):

Hey @azdlowry you can flash this OEPL Firmware onto it https://github.com/OpenEPaperLink/OpenEPaperLink/blob/master/binaries/Tag/TLSR_Gicisky_TFT_213.bin
via this flasher: https://atc1441.github.io/BLE_EPaper_OTA.html
It will then work on the OEPL 802.15.2 Protocol and is working fine.

<!-- gh-comment-id:2531827911 --> @atc1441 commented on GitHub (Dec 10, 2024): Hey @azdlowry you can flash this OEPL Firmware onto it https://github.com/OpenEPaperLink/OpenEPaperLink/blob/master/binaries/Tag/TLSR_Gicisky_TFT_213.bin via this flasher: https://atc1441.github.io/BLE_EPaper_OTA.html It will then work on the OEPL 802.15.2 Protocol and is working fine.
sascha_hemi commented 2026-03-20 20:07:05 +01:00
Author
Owner
Copy Link

@azdlowry commented on GitHub (Dec 11, 2024):

Thanks @atc1441 .
I'm running a BLE only AP at the moment. I'll have a poke around while I'm looking at some other issues.

<!-- gh-comment-id:2536216688 --> @azdlowry commented on GitHub (Dec 11, 2024): Thanks @atc1441 . I'm running a BLE only AP at the moment. I'll have a poke around while I'm looking at some other issues.
sascha_hemi commented 2026-03-20 20:07:05 +01:00
Author
Owner
Copy Link

@connoreaton3 commented on GitHub (Feb 11, 2025):

I am currently running BLE only AP on a esp32-s3 and have flashed the firmware on my tag but now it just shows No AP Found. Which AP should I be using for this?

<!-- gh-comment-id:2651126241 --> @connoreaton3 commented on GitHub (Feb 11, 2025): I am currently running BLE only AP on a esp32-s3 and have flashed the firmware on my tag but now it just shows No AP Found. Which AP should I be using for this?
sascha_hemi commented 2026-03-20 20:07:05 +01:00
Author
Owner
Copy Link

@Obamium69 commented on GitHub (Aug 3, 2025):

Hi @connoreaton3.

I also having the same setup and the same issue. Did found a fix for that?

<!-- gh-comment-id:3148690816 --> @Obamium69 commented on GitHub (Aug 3, 2025): Hi @connoreaton3. I also having the same setup and the same issue. Did found a fix for that?
sascha_hemi commented 2026-03-20 20:07:06 +01:00
Author
Owner
Copy Link

@connoreaton3 commented on GitHub (Aug 10, 2025):

Hi @connoreaton3.

I also having the same setup and the same issue. Did found a fix for that?

Hi @Obamium69,

Yes, I managed to get it all working. It was a bit of a pain and had a few issues whilst doing so, but please see below where I posted my full fix and steps taken to get it all working.

https://github.com/OpenEPaperLink/OpenEPaperLink/issues/437#issuecomment-2866210027

<!-- gh-comment-id:3172601786 --> @connoreaton3 commented on GitHub (Aug 10, 2025): > Hi [@connoreaton3](https://github.com/connoreaton3). > > I also having the same setup and the same issue. Did found a fix for that? Hi @Obamium69, Yes, I managed to get it all working. It was a bit of a pain and had a few issues whilst doing so, but please see below where I posted my full fix and steps taken to get it all working. https://github.com/OpenEPaperLink/OpenEPaperLink/issues/437#issuecomment-2866210027
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
88MZ100 FW
ARM Tag FW
ap fw
bug
documentation
enhancement
good first issue
nRF FW
pull-request
Mirrored from GitHub Pull Request
 question
tag fw
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
sascha_hemi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/OpenEPaperLink#1883
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?