Thanks for watching! Unfortunately, Proteus doesn't support the TM1638 module directly, but you can still work with it using STM32 by referring to the TM1638 datasheet. The functions are quite similar to those in the TM1637. For example: TM1637Display_setSegments (TM1637) ↔ TM1638_setSegments (TM1638) TM1637Display_showNumberDec (TM1637) ↔ TM1638_showNumberDec (TM1638) TM1637Display_setBrightness (TM1637) ↔ TM1638_setBrightness (TM1638) These should help you get started. Let me know if you need more guidance!
@@theembeddedthings I am having trouble using the TM1638 push button. I have read the datasheet and followed it but it still doesn't work. I hope you can answer me soon. Thanks!
Hey @@lewlew212 ! 😊 It sounds like those push buttons are giving you a bit of a headache . Don’t worry, I’ve got a few tips that might just save the day! Here’s what to check out: 1/SPI Clock Speed : The TM1638 is a bit on the slow side when it comes to SPI communication-keep that clock speed below 500kHz. If you’re using the STM32 HAL library, make sure you’ve got this dialed down in your SPI initialization. It’s crucial for proper communication. 2/Tiny Delays: Even with the right clock speed, timing can be tricky. Sometimes, adding a microsecond delay after sending data can help stabilize things, especially since the STM32 can be too fast for the TM1638 to handle. 3/Voltage Levels : This one’s super important! Make sure your STM32 and TM1638 are on the same page with voltage!!!. If your STM32 is running at 3.3V, the TM1638 should be too. Mixing up voltage levels without a level shifter is a recipe for trouble. 3/SPI Mode 3 : The TM1638 expects SPI mode 3 (CPOL = 1, CPHA = 1)!!. Double-check your STM32 settings to make sure the clock is high when idle and data clocks in on the rising edge. This alignment is key to getting everything working smoothly. These tweaks should help get those buttons responding like they should. If you’re still having issues, there are some resources out there like this stm32python.gitlab.io/en/docs/Stm32duino/exercises/tm1638#usage github.com/MartyMacGyver/TM1638-demos-and-examples?tab=readme-ov-file Keep at it, and don’t hesitate to reach out if you hit another snag. You’ve got this! 💪🚀
Can you guide tm1638 with stm32?
Thanks for watching! Unfortunately, Proteus doesn't support the TM1638 module directly, but you can still work with it using STM32 by referring to the TM1638 datasheet. The functions are quite similar to those in the TM1637. For example:
TM1637Display_setSegments (TM1637) ↔ TM1638_setSegments (TM1638)
TM1637Display_showNumberDec (TM1637) ↔ TM1638_showNumberDec (TM1638)
TM1637Display_setBrightness (TM1637) ↔ TM1638_setBrightness (TM1638)
These should help you get started. Let me know if you need more guidance!
@@theembeddedthings I am having trouble using the TM1638 push button. I have read the datasheet and followed it but it still doesn't work. I hope you can answer me soon. Thanks!
Hey @@lewlew212 ! 😊 It sounds like those push buttons are giving you a bit of a headache . Don’t worry, I’ve got a few tips that might just save the day!
Here’s what to check out:
1/SPI Clock Speed : The TM1638 is a bit on the slow side when it comes to SPI communication-keep that clock speed below 500kHz. If you’re using the STM32 HAL library, make sure you’ve got this dialed down in your SPI initialization. It’s crucial for proper communication.
2/Tiny Delays: Even with the right clock speed, timing can be tricky. Sometimes, adding a microsecond delay after sending data can help stabilize things, especially since the STM32 can be too fast for the TM1638 to handle.
3/Voltage Levels : This one’s super important! Make sure your STM32 and TM1638 are on the same page with voltage!!!. If your STM32 is running at 3.3V, the TM1638 should be too. Mixing up voltage levels without a level shifter is a recipe for trouble.
3/SPI Mode 3 : The TM1638 expects SPI mode 3 (CPOL = 1, CPHA = 1)!!. Double-check your STM32 settings to make sure the clock is high when idle and data clocks in on the rising edge. This alignment is key to getting everything working smoothly.
These tweaks should help get those buttons responding like they should. If you’re still having issues, there are some resources out there like this
stm32python.gitlab.io/en/docs/Stm32duino/exercises/tm1638#usage
github.com/MartyMacGyver/TM1638-demos-and-examples?tab=readme-ov-file
Keep at it, and don’t hesitate to reach out if you hit another snag. You’ve got this! 💪🚀