-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR2 max7219 dot matrix, less memory #14091
PR2 max7219 dot matrix, less memory #14091
Conversation
Have you set "DisplayWidth 64"? (64 pixels in a row). Are you shure that the orientation of the first display isn't upside down? |
The display is powered by the ESP so how to bring power to the diplay before ESP starts. |
I compared your driver with this one. There is no initialisation issue, as my tests figured out. Is there a way to provide modes in your driver? |
Hi Rushmed, there is no initialisation issue with this driver when wowering the ESP and the display at the same time.
Yes, chaniging the module type causes a restart of the module which resends the initalisation to the display.
Yes: Restarting the ESP. E.g. use the web console command "restart"
The driver is written memory optimized and contains only a minimum of necessary functionality. Which display modes do you miss for your project? Regards, |
Hallo Michael, do you connect the LEDs to the power source directly? I am powering the LEDs with the ESP output. |
Hi Rushmed,
No, I use the same USB power supply as for the ESP. So be sure to use a 5 V source with enough power. |
OK thanks. |
FYI. I was able to solve the initialisation issue by the help of another user. |
Thank you very much. :-) :-) I already use 16 moduls in row. Still using another code, which is still buggy. My standard view is a clock <weekday, month, day, hh:mm:ss>. I find it really cool. Every minute i generate a mqtt post from openhab with sensor values from my smart home. After that it returns to the clock. Is this clock already possible with tasmota? Could it be added too? |
Using this display with Tasmota it can display any string via MQTT. The tasmota display driver also supports a clock display. To switch back from clock to text send: Regards, |
Dear Michael, i also use openhab with this current code to post a mqtt payload. But i already send all my values from my weatherstation every minute. So it is not possible to post a second one with my time notification withous having trouble with synchronisation. And i would loos the seconds, that are displayed now. Just see the video i added. The max 7219 are really cool and it is really easy to use more than one or two of them. The current clock with "HH:MM" or "HH:MM:SS" could be too small if you use 4 elements ore more of max7219. Just try to put the english notification. It would be enough if this option could be set in the xdsp_19_max7219_matrix.ino itself. Could be very cool. :-) Thank you very much. Regards Patrick. VID_20220131_100758.mp4 |
Is this driver included in the new Tasmota V11 display.bin or do I still need to implement and compile? |
Changelog of v11 says yes: Support for MAX7219 Dot Matrix displays #14091 |
I know but its not working. |
Yes, as described you still need to compile with: Resaon:
See also file tasmota_template.h line 558 on v11.0.0 |
ok, thanks! |
Dear frend, |
Hi, |
i am a beginner i only knows how to use tasmotizer with nodemcu, can any body give me a bin file, regards |
share the firmware for esp32 |
Description:
This driver enables the display of ascii text on MAX7219 based 8x8 LED dot matrix modules (1088AS).
#define USE_DISPLAY_MAX7219_MATRIX
See also usage description in file tasmota/xdsp_19_max7219_matrix.ino
Same functionality as PR #13917, but less memory usage.
(character table only for standard ascii, no usage of lib time.h)
tasmota_display witout USE_DISPLAY_MAX7219_MATRIX
uses 609556 bytes
tasmota_display #define USE_DISPLAY_MAX7219_MATRIX
uses 603736 bytes
(-5820 bytes, cause impicit #undef USE_DISPLAY_MAX7219 and #undef USE_DISPLAY_TM1637)
tasmota_display #define USE_DISPLAY_MAX7219_MATRIX #define USE_UTF8_LATIN1
uses 604584 bytes
(+848 bytes for additional character tables)
Checklist:
NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass