Duet Wifi heats Bed and Hotend from start

sixfeetunder

thanks for your response. this sounds Not that good. is it possible to teplace this Chip? it would be a shame to throw that nice piece of Hardware into trash because of one 1-Dollar Chip right?

T3P3Tony

@sixfeetunder where are you located? User @W3DRK is in the US and does repairs. Does the board work other than the MOSFETs? VIN to 5V circuit might have caused some.other damage.

sixfeetunder

i am located in germany, at the Moment i dont see any other Problems. Motors and Sensors are working so far

T3P3Tony

@sixfeetunder Do you have the capability to replace a SMT component or know of someone.local who does. It may just be U11 that needs replacing

Jacotheron

Looking at my DuetWifi v1.03 board, U11 is a small chip close to the 2 extruder mosfets^ (near the USB port; on your photo slightly hidden behind the blue and black wire's connector [looks like temperature input connector]). I have soldered this size chip before (I have limited soldering experience, I would say novice level), and here is my recommendation:

If you have access to a hot-air station, that will help you a lot.
Use a small tipped solder iron.
Use a good amount of flux while desoldering and soldering (the flux can help to keep the pins separate).
Be careful for making it too hot (especially the new chip).
Before you start ensure you make a note or mark of the chip's orientation (there may be a mark in the silkscreen, always better to be safe than sorry).
The C54 capacitor is in very close proximity to the chip, be careful around it.

If you don't feel confident doing this, rather get a friend to help, or maybe ask a repair center to help you with this.

^ On mine, this chip in U11 is marked as "HT02 78KG4 A7H8"; U12 (in the corner near the wifi module) is marked as "HC74 73KG4 ..." (bottom line is not very clear);

sixfeetunder

theae are my Chips. i guess i should get a and try to replace it or find someone who can help me with this?
should i buy exactly the Model which is written on the Chip? HT0278KG4 A7H9

dc42

You need a 74HCT02 chip in a TSSOP package. A typical part number is 74HCT02PW or SN74HCT02PW. The PW suffix is the package type.

sixfeetunder

ok i get some of these. Thanks a lot for you help

sixfeetunder

So now i switched the chip and i think i did a quite bad job, but it should work. at least from my point of view. The board is still working (can connect to it with yat and the heat LEDs are not flashing from start). so far so good. but now i have another problem: when i start the board and want connect to wifi, the wifi module is blinking blue and then switches off. in yat i get following message:

M552 S1
ok<LF>Error retrieving WiFi status message: SPI timeout<LF>WiFi module is idle<LF>Error retrieving WiFi status message: SPI timeout<LF>Error retrieving WiFi status message: SPI timeout<LF>Error retrieving WiFi status message: SPI timeout<LF>Error retrieving WiFi status message: SPI timeout<LF>Error retrieving WiFi status message: SPI timeout<LF>WiFi module is idle<LF>

Do anyone have an idea what i could have damaged or what is wrong? maybe i forgot something?

SupraGuy

No expert here, but does your board remember your network?

Is the M587 command still in your config.g?

M587 S"WiFiForSupraGuy" P"SupraGuysSuperSecurePassword"

You can enter just

M587

using your terminal, and it should tell you what networks it remembers. I generally start wifi troubleshooting with purging all of those, and adding them again.

You could purge all networks with:

M588 S"*"

Or just specify the networks you want to forget.

dc42

@sixfeetunder said in Duet Wifi heats Bed and Hotend from start:

So now i switched the chip and i think i did a quite bad job, but it should work. at least from my point of view. The board is still working (can connect to it with yat and the heat LEDs are not flashing from start). so far so good. but now i have another problem: when i start the board and want connect to wifi, the wifi module is blinking blue and then switches off. in yat i get following message:

M552 S1
ok<LF>Error retrieving WiFi status message: SPI timeout<LF>WiFi module is idle<LF>Error retrieving WiFi status message: SPI timeout<LF>Error retrieving WiFi status message: SPI timeout<LF>Error retrieving WiFi status message: SPI timeout<LF>Error retrieving WiFi status message: SPI timeout<LF>Error retrieving WiFi status message: SPI timeout<LF>WiFi module is idle<LF>

Do anyone have an idea what i could have damaged or what is wrong? maybe i forgot something?

Try re-installing DuetWiFiServer.bin. If it is already on the SD card, you can do this by sending M997 S1.

sixfeetunder

@SupraGuy
i tried that already, but thanks for your help

@dc42 said in Duet Wifi heats Bed and Hotend from start:

M997 S1

i placed DuetWiFiServer-1.21.bin on the sd card and tried your command. But i guess it doesnt work as expected. This is what i get back:

M997 S1
Trying to connect at 230400 baud: failed<LF>Trying to connect at 115200 baud: failed<LF>Trying to connect at 74880 baud: failed<LF>Trying to connect at 9600 baud: failed<LF>Error: Installation failed due to comm write error<LF>ok<LF>

thanks for the fast reply

edit: i tried it in root and in sys directory

Phaedrux

@sixfeetunder I think the file has to be named exactly DuetWiFiServer.bin

sixfeetunder

Thanks for the hint. i renamed it and recognized that there was already a file like this in the sys folder. i replaced it anyways with the new one but i get the same result "installation failed..."

Jacotheron

The Baud Rate is the data rate at which the main processor communicates with the Wifi chip, using the UART / Serial protocol.

The fact that it fails to get any response, tells me there is an issue where a trace between the 2 may have an issue.

The UART communication uses 2 data lines: TX (transmit) and RX (receive); the TX of one goes to the RX of the other. If a data line is damaged, the communication will fail.

One of the other guys might be able to tell you where to look for these traces.

sixfeetunder

okay, thanks. i guess you are right. i can do a firmware upgrade and everything works fine, but it looks like the processort cant communicate with the wifi chip properly. I can set the wifi to active and inactive but connecting to my wifi will result in an error every time. Additionally, as already pointed out, the update of the wifi firmware itself wont work...

dc42

My guess is that you had a transient or short to the 5V or the 3.3V power rail, which damaged both U11 and the WiFi module. So I think you need to replace the WiFi module. The good news is that it's easier to solder than U11 because the pads are larger.

The correct replacement part is ESP-12S, or ESP-07S (the S is important) if you want the version with external antenna. These are are readily available on eBay.

Please note, the other component that is easily damaged by over-voltage on the 3.3V rail is the main processor. So I suggest you check first that the processor is not getting hot (slightly warm is normal) and the other functions of the Duet are working properly.

From the photo, it looks like your Duet was revision 1.04, in which case it might still be under warranty.

sixfeetunder

@dc42 thanks for your informative answer. the WiFi Was working before i tried my soldering skills on the U11, thats why i wanted to figure out what i might have damaged
the Board is only 6 Weeks old thats why i asked the Internet Shop where i bought It if warranty is an option, but they refused. Do you think i should ask at the headquarters in uk?

dc42

If the internet shop was one of our official distributors (see the list at the bottom of https://www.duet3d.com/DuetWifi) then they would typically refer warranty enquiries to us, unless they had reason to believe that the Duet had been abused.

sixfeetunder

they asked me to open this forum Post and After the First few posts they thought i damaged it myself, because the most likely reason was that i created a short.
it would be really nice if i could get warranty because i didnt Do anything harmful to the Board (at least i dont know about something). Do you think i should try to contact your Support Directly?