-
Notifications
You must be signed in to change notification settings - Fork 201
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
where the problems is ? #20
Comments
Hardware issue. Check your wiring and grounding.
OE pin especially.
Not a software matter.
…On Thu, 21 Nov 2019, 14:15 cxandy, ***@***.***> wrote:
[image: 1085405609]
<https://user-images.githubusercontent.com/1715155/69345304-e2121c00-0cab-11ea-9757-926c98523dfa.jpg>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#20>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC3TMKJGEGYWG6JCT22MWZ3QU2JTJANCNFSM4JQC6AOQ>
.
|
this firmware is work fine. |
@Galaxy-Man thank you for your kind words. I also discovered the WiFiConnectLite issue last night as well, and have implemented a fix to this. Please download a new .zip of the library. As for these new 'FM6126' - I do not have one of these so cannot test. What is it you needed to connect the RESET pin to? Other than that, just to confirm my understanding, you only needed to change the following pin mappings:
|
Thank you for the fix, I will try it and let you know how I get on. I was goign to hack the code and use EEPROM or Preferences to store the settings. I did not get that far as I got distracted making a Lemmings clock for a friend. I changed all the pins, it started out I wanted to use a TTGO oled ESP32 with battery, Wemos ESP32 and DoIT ESP32 so tried to get the pins to work on all boards with having to change layout between them. I had more issues with the TTGO board so rather than waste time I opted for the DoIT board and the pin layout is what I end up with which worked for me and frees the SDA and SDL pins, I should of stuck with your layout. Your libray for the matrix is impressive, is there anything else you are thinking of adding or improving? The reset is Bob's code which you need ot run before initializing your library, it initialise the FM6126 chipset correctly. It should be on my github page, if not I'll upload it. I Will try 2x FM6126 boards together this week, I have them with me but forgot the cable from work, doh! I have not had so much fun with these matrix boards since my Atari days lol |
Tested new code works well, thanks. |
Thanks again. I can thank the original guy who came up with a working DMA implementation for this. I just wanted to make something that was straightforward and that worked. I can't think of anything further that needs to be done. Perhaps share a link to Bob's code so I can understand it more.
To be honest, I haven't touched my panel since I wrote the original library out of my own curiosity. However, you've got me interested again. So last night found an old Gyro laying around. You can connect it to the two I2C pins (22 and 21) that this library keeps free, and have a lot of fun. |
This is not good news, these panels are taking up loads of my time! I like it :-) Bob's code to follow... |
#include <Arduino.h> RGB64x32MatrixPanel_I2S_DMA matrix; //////////////////////////////////////////////////////////////////// // R1 | G1 #define R1 25 void resetPanel() int C12[16] = {0, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1, 1}; pinMode(R1, OUTPUT); // Send Data to control register 11 void setup(){ resetPanel(); // do this before matrix.begin // If you experience ghosting, you will need to reduce the brightness level, not all RGB Matrix matrix.setPanelBrightness(10); // SETS THE BRIGHTNESS HERE. 60 OR LOWER IDEAL. matrix.begin(R1, G1, BL1, R2, G2, BL2, CH_A, CH_B, CH_C, CH_D, CH_E, LAT, OE, CLK); // setup the LED matrix } void loop(){ } |
Let me know how you get on with this...or need a hand! I'm sure you can work it out :-) |
I'm not going to code anything I can't test directly, so if I get a FM6126 based panel one day I might implement a routine. However, your code seems straight forward enough to re-purpose. |
Understood, I was going to make it as a standalone file for neatness but never got round to it. Got the Morphing Clock working with your library, works well and is neat. If you need inspiration (well not much of a challenge) for a project then an alarm addin would be good. Q. Does your DailTimer library work ok on ESP32, reason for question is when I build it reports TimeLib errors! In file included from lib\DailyTimer\DailyTimer.h:21:0, |
Not sure what library you're using, but this is the TimeLib library. |
the build was referencing a very old TimeLib, sorted now thanks. |
@cxandy - Can you do me a favour and try the development branch and see if that improves anything? |
The text was updated successfully, but these errors were encountered: