Cant connect to machine over web - trying causes card failure.
-
What is the power supply voltage? It shows 13v which is odd.
Reason I ask about trying with the USB connected is that it's supplying 5v separate to the PSU.
Firmware update would just be an attempt to fix with a new flash and replacing the DWC files in case they were corrupted.
A new SD card will likely already be in the correct format. Copying the files across is all that's needed. But further detail on the exact format can be found here: https://duet3d.dozuki.com/Wiki/SD_Card#Section_Formatting
-
@phaedrux Oh I see. How would I find out the PSU voltage?
-
It would likely be printed on the unit itself. Otherwise you can test it with a multimeter. But testing it would likely tell you 13v which the Duet already shows. It would be good to know what it's supposed to be. Typically it would be either 12v or 24v. If it's supposed to be 12v then it's likely that the adjustment potentiometer on the PSU is just turned a bit too high. If it's supposed to be 24v, then something is potentially failing in the PSU.
-
@phaedrux I will at least look up the specs from the manufacturer and email them if that doesn't yield anything. If I have to disassemble the head of the machine then so be it, I guess (I don't build these things, I just use them).
EDIT I looked it up and it's apparently a Meanwell 350W 12V supply. I assume I should ask the company if it should be adjusted, just in case. I don't know if they overvolt something on purpose in there.
But, that said, for a machine that has given me no issues for 2 years or so, outside of 2 network/wifi based problems (this being the second one), is there a reason to suspect a voltage misadjustment now?
-
@ddxdesign said in Cant connect to machine over web - trying causes card failure.:
is there a reason to suspect a voltage misadjustment now?
I can't say for sure. But if the PSU were having an issue it might come into play. I would think a problem with the SD card may be more likely. It's just something I noticed. 13 volts is unusual, combined with the fact you say things behaved different with USB connected, which means a separate 5v supply was provided by passing the onboard regulator. Little things that may add up to nothing, or maybe something.
-
@phaedrux I finally got a chance to try to do the DWC connection while plugged into the USB and got the same file read error. So I suppose my next item is to buy a new sd card.
-
Worth a shot.
-
@phaedrux OK this took entirely too long to get back to, but I did find that a couple of the big .GZ files in the www folder were unable to be copied out from the old card. I'm trying to find the files elsewhere in my computer, ideally just the entire www folder. what could happen if those GZip files aren't there? I can't imagine the printer itself has the utilities to unzip and use the contents thereof, right?
-
@ddxdesign the RRF web server serves the .gz files to the browser, and the browser decompresses them.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 OK so I do need to find them and get them back in there. Thanks.
-
You can find the DWC files that go in the /WWW folder along with the firmware release.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/DuetWebControl-SD.zip
-
@phaedrux Well, I found the files for my FW (3.2.2) and loaded the new card in the machine and.... nothing. the macros don't show up, the gcodes don't show up, it doesn't have anything showing in console, nothing.
-
Can you show a screen shot of your WWW folder to confirm the files are correct?
Or compare to this listing:. ├── firmware │ ├── Duet2CombinedFirmware.bin │ └── Duet2_SDiap32_WiFiEth.bin ├── gcodes ├── macros ├── sys │ ├── bed.g │ ├── config.g │ ├── config.json │ ├── homeall.g │ ├── homex.g │ ├── homey.g │ ├── homez.g │ ├── pause.g │ ├── resume.g │ ├── sleep.g │ ├── stop.g │ ├── tfree0.g │ ├── tpost0.g │ └── tpre0.g └── www ├── DuetAPI.xml ├── css │ ├── Accelerometer.5c60999b.css.gz │ ├── GCodeViewer.9597b317.css.gz │ ├── HeightMap.4d390d72.css.gz │ ├── ObjectModelBrowser.c5e13b42.css.gz │ ├── OnScreenKeyboard.7f43fe4b.css.gz │ └── app.ce075a4e.css.gz ├── favicon.ico.gz ├── fonts │ ├── materialdesignicons-webfont.147e3378.woff │ ├── materialdesignicons-webfont.147e3378.woff.gz │ ├── materialdesignicons-webfont.174c02fc.ttf.gz │ ├── materialdesignicons-webfont.64d4cf64.eot.gz │ ├── materialdesignicons-webfont.7a44ea19.woff2 │ └── materialdesignicons-webfont.7a44ea19.woff2.gz ├── img │ └── icons │ ├── android-chrome-192x192.png.gz │ ├── android-chrome-512x512.png.gz │ ├── android-chrome-maskable-192x192.png.gz │ ├── android-chrome-maskable-512x512.png.gz │ ├── apple-touch-icon-120x120.png.gz │ ├── apple-touch-icon-152x152.png.gz │ ├── apple-touch-icon-180x180.png.gz │ ├── apple-touch-icon-60x60.png.gz │ ├── apple-touch-icon-76x76.png.gz │ ├── apple-touch-icon.png.gz │ ├── favicon-16x16.png.gz │ ├── favicon-32x32.png.gz │ ├── msapplication-icon-144x144.png.gz │ ├── mstile-150x150.png.gz │ └── safari-pinned-tab.svg.gz ├── index.html.gz ├── js │ ├── Accelerometer.4a8a402b.js.gz │ ├── Accelerometer.4a8a402b.js.map.gz │ ├── GCodeViewer.95d3cd80.js.gz │ ├── GCodeViewer.95d3cd80.js.map.gz │ ├── HeightMap.a082b8e6.js.gz │ ├── HeightMap.a082b8e6.js.map.gz │ ├── ObjectModelBrowser.0b9b2798.js.gz │ ├── ObjectModelBrowser.0b9b2798.js.map.gz │ ├── OnScreenKeyboard.a880bca8.js.gz │ ├── OnScreenKeyboard.a880bca8.js.map.gz │ ├── app.24acd1b2.js.gz │ └── app.24acd1b2.js.map.gz ├── manifest.json.gz ├── precache-manifest.a4ab8f573fcc203b798fa7d11eee39d5.js.gz └── service-worker.js.gzCan you connect by USB terminal again and send some commands and tell us how it responds
M552 M552 S0 M552 S1 M122 P104 S10 M997 S1 -
@phaedrux well for now I grabbed the tree screenshot from the WWW folder sitting on my desktop (which I copied over into the SD card)
-
@phaedrux And here is the result of those commands when connected to terminal by usb. Somehow starting wifi worked, but on screen I still have no SD card content showing and the part-fans are running full tilt.
m552
WiFi module is disabled<LF>ok<LF>
m552 s0
ok<LF>WiFi module started<LF>
m552 s1
ok<LF>WiFi module is connected to access point MOTO3E2E, IP address 192.168.0.206<LF>
m122 p104 s10
Error: Failed to create folder 0:/gcodes in path 0:/gcodes/test.tst<LF>Error: M122: Failed to create file<LF>ok<LF>
m997 s1
Error: M997: File DuetWiFiServer.bin not found<LF>ok<LF> -
@ddxdesign said in Cant connect to machine over web - trying causes card failure.:
m122 p104 s10
Error: Failed to create folder 0:/gcodes in path 0:/gcodes/test.tst<LF>Error: M122: Failed to create file<LF>ok<LF>
m997 s1
Error: M997: File DuetWiFiServer.bin not found<LF>ok<LF>These errors make it seem like the SD card isn't being read at all.
Can you get a close up shot of the SD card slot showing the soldering of the pins at the back?
When and where did you purchase the Duet?
-
@phaedrux Right, that's what I was thinking. I would have to dismantle the top of the machine to get a look at the board itself. I didn't buy the Duet standalone, I bought a complete machine - SeeMeCNC Artemis 300 - about a year and a half ago. It's been the best machine ever in terms of use and print quality so this is a real downer.
-
Given the age of the machine I would think it's more likely an issue with the SD card aging, but after replacing the card that seems less likely. Perhaps it's heat cycling causing the solder to weaken on the SD card slot.
Unfortunately that would be out of warranty. We may be able to offer a refurbished replacement on exchange at reduced cost. Or perhaps on inspection of the board something else will become apparent. It may be a simple matter of touching up the solder on the SD card slot.
-
@phaedrux Just revisited my records and I bought this machine brand new, receiving it on Jan 20, 2021 - so not even 13 months ago it turns out. Really, THAT is out of warranty?? What?
-
The warranty is 1 year. 13 months is something we can work with compared to a year and a half.
Please send an email to warranty@duet3d.com and CC your reseller. Include a link to this forum thread and the details of your original purchase. You'll receive a reply with a form to fill out.
