Updating Web Interface and Server
-
I am just completing my CoreXY printer build and DC’s new software seems like good timing.
I can measure the bed and see if the slab of aluminum and the Borosilicate glass were a good investment.
The firmware updates to 1.17RC3 no problem.
The Web Interface however refuses to update. It appears to go through the motions, loads fine, asks me if I want to update, displays the progress bar asks me if I want to reload the page. I then get an error “Could not establish a connection”. I cannot connect until I reset the Duet. It works after the reset but still running 1.12. Tried renaming the file to its generic name, run M997 S2, no success.
I can see DuetWebControl.bin on the settings/System Editor page (3.0MB).
I noted that the WiFi Server version was 1.02, I tried to update this to 1.03. It failed in exactly the same way as the Web Interface. Still running 1.02
I’m clearly missing something here. Any suggestions would be appreciated -
Was your board only powered by USB when you update it?
-
No its running from 24v
-
If you connect to the Duet via USB and run the M997 S1 or S2 from Pronterface or similar, you will get more information about what is going on.
-
Thanks for your reply David.
This is what I am seeing on pronterfaceConnecting…
Printer is now online.M997 S2
SENDING:M997 S2
Trying to connect at 460800 baud:
failed
Trying to connect at 230400 baud:
failed
Trying to connect at 115200 baud:
failed
Trying to connect at 74880 baud:
failed
Error: Installation failed due to comm write error
[ERROR] Error: Installation failed due to comm write error -
So the WiFi module isn't responding when the Duet main processor tries to use the programming interface. Looks like you have a hardware fault. Do all the pads of the WiFi module look adequately soldered to the main board? You can ignore the pads at the back of the module because those connections are not used.
-
There looks to be a crack in the joint of the bottom left hand pin, the pin nearest the board mounting hole. If you think this pin would cause the fault then I am happy to attempt a repair.
-
There looks to be a crack in the joint of the bottom left hand pin, the pin nearest the board mounting hole. If you think this pin would cause the fault then I am happy to attempt a repair.
Yes, that could explain the problem.
-
Strange thing.
I removed the board remade the the connection on the wifi module and I was able to update both the wifi server and Interface.
Just once. It has failed every time since. So mission completed, I have the latest firmware installed and working but will have the same problem again next update.
Have we reached the point where I need to return the board -
Strange thing.
I removed the board remade the the connection on the wifi module and I was able to update both the wifi server and Interface.
Just once. It has failed every time since. So mission completed, I have the latest firmware installed and working but will have the same problem again next update.
Have we reached the point where I need to return the boardProbably, unless you can spot another bad joint either on the WiFi module or on R102 or R103. Is it a blue production board or a white pre-production board? If it's a pre-production board, can you read the value of R103?
-
Its a blue production board.
It is almost certainly an intermittent connection. I am just little concerned about warranty if I go around the WiFi module redoing all the joints. -
I've emailed T3P3 about replacing or repairing your board. As you currently have a working board loaded with latest firmware, I presume the repair or exchange can wait until after New Year.
-
No problem David, I'm happy to wait until the new year
-
David
Replacement board received from T3P3 with their normal efficiency.
Fitted in printer, firmware updated and all working fine once more.
Thanks for your help -
I too am having this exact same problem, but with the duetwebcontrol.bin installation. I followed the same steps as johneato for the web interface and pronterface and had the same results. Any progress on finding out why this is happening?
-
Yes, it seems that a small proportion of WiFi modules need the value of R103 reduced for them to connect reliably for programming. We've reduced the value in the latest production batch.
if you have one of the WiFi modules that is marginal in this respect, it may connect more easily at higher or lower temperatures. I've also found in the past that extra capacitance at that part of the circuit helps connection, so putting your finger on R103 while it is trying to connect may help.
-
Thank you for the fast response. No luck with heating up the board to ~55C with a hair dryer or putting my finger on R103 while trying to update. I have a blue duet wifi which I purchased through Filastruder. What steps should I take next? Any other ideas?
-
The other thing that may make a difference is trying it both with and without Vin power applied. If that doesn't work, then assuming you are not equipped for and experienced in SMD rework, I suggest you ask Filastruder to replace the board.
-
Ok, thank you for your help David. I did try with and without Vin power, no luck. As I do not have the experience needed to rework this myself, I will contact Filastruder.
-
Hi all, i'm happy to find the thread about my ardwrare problem. My printer are under construction and i just begin wiring and connection. Wifi network only run when i put my finger on R103. I bought my T3P3 board at the end of january, a blue production one. Should i've it replaced? Is there another solution without soldering for fix it alone?
Sorry for my english, i'm new french user who use google translate.
