Add support for 6 digits and keypad#48
Conversation
Extend to 6 digits and add keypad scan
Extend to 6 digits and add keypad scan
Add Keypad Scan
Extended to 6 digits and Keypad scan added
Add SEG_DP
Minor change at stop sequence to avoid extra peak in DIO.
Adapt counter to around 1/100 sec per cycle
|
Hello, Do you know any workaround ? |
|
Well, the library is writing the digits in a sequence. Your module seems to me ordering the digits in a special way. You may have three choices: Changing the TM1637Display.cpp to work with this messed pin wiring would mean, that we do not use the sequence writing any more. Which I would not place here. The failure is definitively at the hardware wiring. BR |
|
Hey, ok I thougt so. |
|
I was just about to do this. Glad I checked the open PRs first. |
|
I have the same robotdyn issue. `void TM1637Display::setSegmentsOrg(const uint8_t segments[], uint8_t length, uint8_t pos) // Write COMM2 + first digit address // Write the data bytes // Write COMM3 + brightness // Write COMM4 void TM1637Display::setSegments(const uint8_t segments[], uint8_t length, uint8_t pos) if (length==0) length = m_noDigits; |
|
3 years ago it was relased here: |
|
I can confirm this actually works when downloading |
|
I just fixed this in my copy of the code. I changed the constructor of the class so that you can set the number of characters and a digit order remapping array. gonna get it checked in shortly. |
|
I have a project with four displays, ten individual LEDs and ten pushbuttons, all controlled through a TM1637. This fork allows me to handle everything with great versatility. I thought I would have to create my own library and this has been a pleasant surprise. |

I optimized the timing for writing a command, so it is able to be followed by a read of keypad scan!