-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V2 board starts burning when attempting dfu mode #26
Comments
you can copy the mks_monster8.bin file to the TF card, and you can update it with the card, or update the .bin file through dfu |
I confirm this "V2 board burning" issue - When you put the Monster8 board into DFU mode the bed heater MOSFET Q7 is enabled (the red LED turns on), and the printer bed heats up. It does this because the HOTBED signal comes from PB10, which happens to be UART3 TX which can be used for DFU communications by the bootloader. When idle UART3 TX sits at a HIGH state (3.3v). I was using a 12 VDC silicone heater which took 14 Amps, so approx 169 Watts. According to the MOSFET datasheet it should have been fine with this amount of load. I am waiting for a response from MKS technical support regarding this issue. |
In the end I think Q7 MOSFET was a faulty component from manufacturer. Not good ;O( Anyway the repair is working and entering DFU mode doesn't cause problems any more. |
+1 here. |
Well, I do not think this is a faulty Q7 device. Too much coincidence for this many cases. All after using DFU with 24V connected. For Q7 the situation in DFU is the same as in normal bed heating (if 3.3V is applied from the TX3). Just my guess after 50 years of experience in electronics. |
Just encountered the same issue on the v1 board but in a different scenario. When I was heating the bed up to do my first print I smelled something burning then to my surprise the mosfet was hot enough to desolder itself. I also did notice in dfu that mosfet is powered for some odd reason |
My monster8 v2 starts burning on the marked piece after holding the boot button while the board is off and turning it on with the button pressed. I'm trying to add marlin binary file transfer via octoprint. Marlin 2.1-bugfix. My ras-pi and my computer see my board as a com port but the .bat files don't run and dfu-utils isn't recognizing my device.
The text was updated successfully, but these errors were encountered: