mirror of
https://github.com/OpenEPaperLink/OpenEPaperLink.git
synced 2026-03-21 16:06:54 +01:00
[GH-ISSUE #558] Feature request: Support Hanshow Nebular 350-N (old Version) and Nebular pro 350Q-n #7541
Reference in New Issue
Block a user
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?
Originally created by @AccsoKollinFreise on GitHub (Mar 8, 2026).
Original GitHub issue: https://github.com/OpenEPaperLink/OpenEPaperLink/issues/558
I have a several Hanshow Displays. Three of them already working without problems.
Two other arent working:
I can flash them (led is blinking). After Flashing the Devices are registered at my Open EPaper Link Access Point. Sadly the display never updates (not after flashing and also not after sending some content to it).
I tryed all 350 and 346 versions...
I would be realy happy about a workaround, a new Service Type or any information how to start.
@DimitrieDinu commented on GitHub (Mar 11, 2026):
I have the same issue (the led blinks during flashing, it blinks at startup, but the display doesnt update at all). with a hanshow nebular pro 420Q-M. I tried to use all the modes that support BWRY, but no luck. What should i do (except get another tag) ?
edit:If needed, i can upload some images of the PCB and/or some FCC docs (especially the internal view and the user manual)
@MacCrutzen commented on GitHub (Mar 11, 2026):
Hi @AccsoKollinFreise,
Great to see that you got three of your Hanshow displays working! I am currently working on a similar project with some Hanshow Nebular shelf labels as well and I'm looking for a bit of guidance.
Since I am trying to get my setup running, I was wondering if you could share some details about your successful units:
Which specific Hanshow Nebular models are the three that are currently working for you?
Could you share a photo or a description of the UART pinout connection you used for flashing?
Which firmware version or specific bin file did you use for the ones that are working?
Any information would be greatly appreciated! Good luck with the Nebular 350-N's.
@nethomas1968 commented on GitHub (Mar 12, 2026):
I have some Hanshow 350R-N devices. I'm not interested in connecting to access points.
I just want to use them as simple displays connected to my Raspberry Pi projects.
Although I can program them, and run my code, and even communicate with them over simple serial port - I can't reliably update the screen. Seems that something in the firmware isn't up to the job.
Until that's sorted out then the units will remain in a box while I play with other things.
@AccsoKollinFreise commented on GitHub (Mar 19, 2026):
Hey :-)
For me worked following setup:
UART Flasher ----> Epaper
GND ----> GND
VCC (3,3v) ----> VCC
DTR ----> NRST
RX ----> SWS
Flashing Tool: https://atc1441.github.io/ATC_BLE_OEPL_Image_Upload.html
Flasher: https://www.amazon.de/dp/B0DGFYQTGH?ref=ppx_yo2ov_dt_b_fed_asin_title
I tried out all images with 350/346. For me worked 350 HS BWR not sure if US or SSD (I used the default values). The same setup does not work for this type of board (bigger controller):
These type of controller worked for me (smaller controller):