ToniG

ok, Thanks I saw them in the file list & assumed...

pic16F182x chips not showing in the select list of devices. The 'pic16f182x_description.xml' files are present in folder 'devices' & in manifest file so something is not set. Looking in the 'user.config' file they are not listed when app close. I have the latest app download.

Haroen - I've decided to manually copy a backup file every time I think some part of code should be saved. That's just what I do as well, by appending a copy file code.gcb.bak1, code.gcb.bak2... in the working folder & at session end I copy changed files to external drive in chronological backup folders. Has saved my sanity on many occasions. Slightly relevant... When I compile a .gcb with SimulIDE it puts output files into a sub folder in the working folder.

"Unfortunately installing GC Studio Code is the only way to update the compiler, that I know of," Chris, GCstudio is not for me either, I like to do things manually. After installing GCs a while back it modified many file associations that are used for other apps. For me I get just the updated folders (or files) from the install using eg. 7zip into a new app folder then copy (or edit) the Synwrite/lexer settings files from the previous install. I only update if I need to. (I am still on 2022-12-21...

"Unfortunately installing GC Studio Code is the only way to update the compiler, that I know of," Chris, GCstudio is not for me either, I like to do things manually. After installing GCs a while back it modified many file associations that are used for other apps. For me I get just the updated folders (or files) from the install using eg. 7zip into a new app folder then copy (or edit) the Synwrite/lexer settings files from the previous install. I only update if I need to. (I am still on 2022-12-21...

There is a good explanation of BAM here.... https://christian-marty.ch/ElectricThings/BitAngleModulation.html

Good to see you got it working. The TM1651 lib code I attached to this post is identical to the TM1637, I just cut down the demo to simplify testing, & .h include text. The 'TM1651_HW_Driver.h' file can be deleted (It's unused)

Looking at the sch for the board, dp is connected to seg 5. This shouldn't be causing your issues but set #Define TM_DispLen 3 Try slowing down your program with a wait 1000ms to see each digit being written en it should. Do all segments come on at power up ? & then clear. (if you are running the supplied test program.) Sending a 0 byte with tmSndDig should clear the digit. (this is what tmCLRdisp uses) Have you got a delay after the display clear(if you have an endless loop it could be writing again...