I started to design a programming rig for the MDBT50Q-1MV2 module. I paused to see if anyone made a programming jig, but I did not see anything. I plan to continue the design and determine which components I need to support the module.
I tested an ESP32 module with wireless power, and I could ping it via Bluetooth, but the power receiver became dangerously hot. I had the same problem with three other units, so I need to run further hardware tests. I found and modified a Universal Asynchronous Receiver-Transmitter (UART) sketch and recognized a designated character, enabling two-way communication, which should be enough for rudimentary functions.
The overheating wireless power receivers were problematic, and I wanted to test if the 20V transmitting coil was part of the problem. I soldered a 5V transmitter, and when I powered it, the chip overheated, melted the solder, and fell off the board. The second try worked fine, but I could not power the ESP32 board without finicky coil alignment, which also caused overheating. I will have to find a reliable receiver.
I discarded the ESP32 as a viable microcontroller since I could not get one to power up without overheating. The MDBT50Q-1MV2 modules worked, so I started making a programming harness for one. Doing this much work would be excessive for a hobbyist, but they should not have to make a harness; they should just print the one I was making. I drafted the layout from the datasheet and compared the two to ensure they matched.
I wrote the quiz for Thrash (2026), and my justification for the questions is "garbage in, garbage out." The movie was too high-budget to be a cult classic, and too poorly executed to be campy. I have not spoken to anyone who enjoyed it.
This was Critical Affection's first episode with a surprise guest! Fish Lee jumped into the show to defend Fred, who argued that Thrash (2026) was not an atrocious movie, but rather a fun B-movie. The debate was hot, and everyone got their say, but it was madness and so much fun.
The rest of the summary posts have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Completed projects from year 12
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
![]() |
| Adafruit Feather with an nRF52840 |
I tested an ESP32 module with wireless power, and I could ping it via Bluetooth, but the power receiver became dangerously hot. I had the same problem with three other units, so I need to run further hardware tests. I found and modified a Universal Asynchronous Receiver-Transmitter (UART) sketch and recognized a designated character, enabling two-way communication, which should be enough for rudimentary functions.
![]() |
| ESP32 with no reliable source |
The overheating wireless power receivers were problematic, and I wanted to test if the 20V transmitting coil was part of the problem. I soldered a 5V transmitter, and when I powered it, the chip overheated, melted the solder, and fell off the board. The second try worked fine, but I could not power the ESP32 board without finicky coil alignment, which also caused overheating. I will have to find a reliable receiver.
![]() |
| Power light, but no connection |
I discarded the ESP32 as a viable microcontroller since I could not get one to power up without overheating. The MDBT50Q-1MV2 modules worked, so I started making a programming harness for one. Doing this much work would be excessive for a hobbyist, but they should not have to make a harness; they should just print the one I was making. I drafted the layout from the datasheet and compared the two to ensure they matched.
![]() |
| MDBT50Q-1MV2 footprint in QCAD |
I wrote the quiz for Thrash (2026), and my justification for the questions is "garbage in, garbage out." The movie was too high-budget to be a cult classic, and too poorly executed to be campy. I have not spoken to anyone who enjoyed it.
![]() |
| The quiz for Thrash (2026) |
This was Critical Affection's first episode with a surprise guest! Fish Lee jumped into the show to defend Fred, who argued that Thrash (2026) was not an atrocious movie, but rather a fun B-movie. The debate was hot, and everyone got their say, but it was madness and so much fun.
Critical Affection: Thrash (1:54)
The rest of the summary posts have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8
Completed projects from year 9
Completed projects from year 10
Completed projects from year 11
Completed projects from year 12
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.





Comments
Post a Comment