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 #299] Hanshow Nebular tags (TLSR firmware) with S/N beginning 7 do not refresh display #1830

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

Originally created by @dslatford on GitHub (Apr 16, 2024).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/299

Using a handful of these Hanshow tags and the alpha TLSR firmware, I've discovered the firmware works perfectly on tags with serials beginning with 3.

However while I can flash tags with serials beginning 7 and they appear in the AP, the screen never refreshes. All tags are model Nebular-350R-N

Examining the serial output, on the working (S/N beginning 3) tags, we see the firmware report 1 second sleeps during the screen refresh, finally ending with the 40 second sleep on completion:

...
Eeprom read 4E295 Len: 256
Eeprom read 4E395 Len: 256
Eeprom read 4E495 Len: 256
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 1000 ms
Sleeping for: 40212 m

However this doesn't happen on the (newer?) tags with serials beginning with 7, the tag enters 40s sleep without the screen refreshing first:

...
Eeprom read 47295 Len: 256
Eeprom read 47395 Len: 256
Eeprom read 47495 Len: 256
Sleeping for: 40015 ms

Internally the tags appear identical. The only other visible differentiator is the working 3xxx tags all feature "D3HG" on the back while the non-working 7xxx tags all have "E3HG".

If there's any debugging I can do with the non-working tags I'm happy to assist.

Originally created by @dslatford on GitHub (Apr 16, 2024). Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/299 Using a handful of these Hanshow tags and the alpha TLSR firmware, I've discovered the firmware works perfectly on tags with serials beginning with 3. However while I can flash tags with serials beginning 7 and they appear in the AP, the screen never refreshes. All tags are model Nebular-350R-N Examining the serial output, on the working (S/N beginning 3) tags, we see the firmware report 1 second sleeps during the screen refresh, finally ending with the 40 second sleep on completion: ... Eeprom read 4E295 Len: 256 Eeprom read 4E395 Len: 256 Eeprom read 4E495 Len: 256 Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 1000 ms Sleeping for: 40212 m However this doesn't happen on the (newer?) tags with serials beginning with 7, the tag enters 40s sleep without the screen refreshing first: ... Eeprom read 47295 Len: 256 Eeprom read 47395 Len: 256 Eeprom read 47495 Len: 256 Sleeping for: 40015 ms Internally the tags appear identical. The only other visible differentiator is the working 3xxx tags all feature "D3HG" on the back while the non-working 7xxx tags all have "E3HG". If there's any debugging I can do with the non-working tags I'm happy to assist.
sascha_hemi added the bug label 2026-03-20 20:06:29 +01:00
sascha_hemi commented 2026-03-20 20:06:30 +01:00
Author
Owner
Copy Link

@Reletiv commented on GitHub (Apr 19, 2024):

At this moment for the 2 or 3 color displays there are 2 known driver groups, you could try the other

Send me a message on discord I'll send you a different firmware to try

<!-- gh-comment-id:2066277300 --> @Reletiv commented on GitHub (Apr 19, 2024): At this moment for the 2 or 3 color displays there are 2 known driver groups, you could try the other Send me a message on discord I'll send you a different firmware to try
sascha_hemi commented 2026-03-20 20:06:30 +01:00
Author
Owner
Copy Link

@nethomas1968 commented on GitHub (Jun 10, 2024):

I've got a few of the Nebular-350R-N units. Although I can flash the firmware in this repo, I didn't get much luck in making the actual display work. I can get serial from it, and I've made a simple command line interpreter to send commands to it. And, I can make the LED flash. But, the screen itself needs a lot more work.

<!-- gh-comment-id:2158801164 --> @nethomas1968 commented on GitHub (Jun 10, 2024): I've got a few of the Nebular-350R-N units. Although I can flash the firmware in this repo, I didn't get much luck in making the actual display work. I can get serial from it, and I've made a simple command line interpreter to send commands to it. And, I can make the LED flash. But, the screen itself needs a lot more work.
sascha_hemi commented 2026-03-20 20:06:30 +01:00
Author
Owner
Copy Link

@dontrajik commented on GitHub (Jun 14, 2024):

Use the SSD sending that usually works

<!-- gh-comment-id:2168385945 --> @dontrajik commented on GitHub (Jun 14, 2024): Use the SSD sending that usually works
sascha_hemi commented 2026-03-20 20:06:30 +01:00
Author
Owner
Copy Link

@bonsai308 commented on GitHub (Aug 5, 2024):

Unfortunately, I have the same problem. After flashing (blue LED flashes), there is no reaction from the display. It is a Nebular-350Y-N (with a 7 at the beginning of the serial number). I have tried TLSR_HS_BWY_35_ALPHA, TLSR_HS_BWY_35_SSD, TLSR_HS_BWY_35_INVERSE and TLSR_HS_BW_35_ALPHA. All without success.

<!-- gh-comment-id:2268287143 --> @bonsai308 commented on GitHub (Aug 5, 2024): Unfortunately, I have the same problem. After flashing (blue LED flashes), there is no reaction from the display. It is a Nebular-350Y-N (with a 7 at the beginning of the serial number). I have tried TLSR_HS_BWY_35_ALPHA, TLSR_HS_BWY_35_SSD, TLSR_HS_BWY_35_INVERSE and TLSR_HS_BW_35_ALPHA. All without success.
sascha_hemi commented 2026-03-20 20:06:30 +01:00
Author
Owner
Copy Link

@dontrajik commented on GitHub (Aug 5, 2024):

I made a repo for this:

https://github.com/dontrajik/Nebular

<!-- gh-comment-id:2268299034 --> @dontrajik commented on GitHub (Aug 5, 2024): I made a repo for this: https://github.com/dontrajik/Nebular
sascha_hemi commented 2026-03-20 20:06:30 +01:00
Author
Owner
Copy Link

@bonsai308 commented on GitHub (Aug 5, 2024):

I made a repo for this:

https://github.com/dontrajik/Nebular

Thank you! Now it run

<!-- gh-comment-id:2268485328 --> @bonsai308 commented on GitHub (Aug 5, 2024): > I made a repo for this: > > https://github.com/dontrajik/Nebular Thank you! Now it run
sascha_hemi commented 2026-03-20 20:06:30 +01:00
Author
Owner
Copy Link

@bonsai308 commented on GitHub (Aug 8, 2024):

Hello, it's me again. So flashing the display worked. According to the display, it is looking for the AP.
I have the Spaghetti as the AP. However, the Nebular display does not appear in the web interface. Can the Nebular even communicate with the Spaghetti AP?
The AP itself should work, since I am shown an unflashed M3 2.9 ESL.
One more off-topic question: can the ESL display also be flashed via an FTDI converter or do I have to use a "middleware" like an ESP? Thank you

<!-- gh-comment-id:2275552591 --> @bonsai308 commented on GitHub (Aug 8, 2024): Hello, it's me again. So flashing the display worked. According to the display, it is looking for the AP. I have the Spaghetti as the AP. However, the Nebular display does not appear in the web interface. Can the Nebular even communicate with the Spaghetti AP? The AP itself should work, since I am shown an unflashed M3 2.9 ESL. One more off-topic question: can the ESL display also be flashed via an FTDI converter or do I have to use a "middleware" like an ESP? Thank you
sascha_hemi commented 2026-03-20 20:06:31 +01:00
Author
Owner
Copy Link

@nethomas1968 commented on GitHub (Aug 8, 2024):

I use a CH340. Probably much the same as an FTDI converter, right?

<!-- gh-comment-id:2275887071 --> @nethomas1968 commented on GitHub (Aug 8, 2024): I use a CH340. Probably much the same as an FTDI converter, right?
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#1830
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?