Enhanced TM1650 with 7-Segment commands like TM1637

[gablau]

Description:

Improved TM1650 with 7-segment commands like TM1637
I ported all 7-segment commands into this driver with a bit of refactoring, simplified operation and future extensions by display type, currently only supports:
DisplayType 0 for XY-Clock
DisplayTypo 2 for 303WifiLC01

Bonus:

• the colon in DisplayMode 1 to 3 now flashes every second.
• in DisplayMode 3 (time/date), it is possible to increase the time display time using the DisplayRefresh [1..7] command

I tested everything with XY-Clock hardware, I don't have the 303WiFiLC01 clock

If this PR is merged, I intend to update the documentation, as at the moment the "20/TM1650" display driver is not documented

Unfortunately I can't test it against ESP32 but compiling via platform.io works fine

Related issue (if applicable): See discussion #15788

Checklist:

• The pull request is done against the latest development branch
• Only relevant files were touched
• Only one feature/fix was added per PR and the code change compiles without warnings
• The code change is tested and works with Tasmota core ESP8266 V.2.7.4.9
• The code change is tested and works with Tasmota core ESP32 V.2.0.7
• I accept the CLA.

NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass

[Jason2866]

@gablau Digit colon is wrong for 303WifiLC01

[gablau]

Hi @Jason2866 ,
I don't have a 303WiFiLC01 to experiment with, but I traced this type of segment wiring from the source code.
In the byte that is sent to the display these are the bits that turn on the segments.
XY-Clock: PGFEDCBA
303 Wifi: BFAEDCGP

/*        A
 *       ---
 *   F |     | B
 *     |  G  |
 *       ---
 *   E |     | C
 *     |  D  |
 *       ---    ° P
 */     

I apply the position swap before sending it to the display, in the "swapbits" function.
If you could do a few more tests and get me the results, I could fix that.
Are you sure you used the DisplayType 2 command before sending commands to the display?

The only command that doesn't use the swapbits function is DisplayRaw, To be used after putting the display in DisplayMode 0
Could you send these two commands and show me what display shows for each one?

DisplayRaw 0, 4, 1, 2, 4, 8
DisplayRaw 0, 4, 16, 32, 64, 128

Each of these commands should light one segment of each digit on the display.

Best Regards
Gabriele

[Jason2866]

Yes, DisplayType 2 the pictures of the raw command

The first pictures should show 11:15 So following your drawing "G" should be Double Point.
@gablau

[gablau]

If the 11:15 time was correct, I think it's just a problem of dots.

Without sending me the pictures, could you try to see if the numbers are displayed correctly with:

DisplayText 0000
DisplayText 1111
DisplayText 2222
DisplayText 3333
DisplayText 4444
DisplayText 5555
DisplayText 6666
DisplayText 7777
DisplayText 8888
DisplayText 9999

or

DisplayScrollDelay 10
DisplayScrollText 0123456789

Then if possible show me displaytext _._._._., this is mine:

Thank you

[Jason2866]

Hi, the issue is just with the dots. All numbers are shown correct
displaytext _._._._.

[gablau]

Fixed, it should work now. I had moved segment P wrong, which became G.

[Jason2866]

@gablau Verified working now for the 303WiFiLC01 module. Thx for the PR!