I'm also sitting on some fancy rework gear and wondering if it would be beneficial for the community and environment to try and have these boards fixed by the community, including myself.
Yes, definitely! The most common repairs are replacing blown drivers (although those usually happen within the first few days so they are covered by the warranty), and blown fan mosfets. After that comes failed WiFi modules (and users wanting to replace the original module by the external antenna version), and occasionally failed processors - although when the processor has failed, unless it's on a v1.0 Duet WiFi then it's normally due to overvoltage on the +3.3V rail, so other components have probably failed too.
BTW we've shipped tens of thousands of Duets, so they are more reliable than you might think from seeing forum posts about failed ones.
I just recently started having an issue with my Duet 2 Wifi. I went to do a print the other day and started to smell something. I checked the power wires going to the Duet from power supply and the ones from power supply to the Duex5, I only smell it when the Bed is heating up. I can even hear something a little bit when it first starts to heat the bed. I know this topic was a little old but I was wondering if something needs to be replaced.
Might be best to start a new thread. This one is more dedicated to finding someone to repair something specifically. Please start a new thread with some more specifics of your setup and we can try and help troubleshoot what is going on. I'd also suggest perhaps disconnecting everything from the board and giving it all a good visual inspection before trying to use it again. Burning smells are never good and you want to try and limit the damage. See if you can find what burnt.
I realized that I had not updated this in a while. Its still a work in progress, but this PDF should print to US Letter landscape. I could use some help converting to SVG so it would be page independant.
Contribution/Objective Critique and Collaboration welcome.
Images can be copy/pasted directly when editing a post as well. (Not copied from filesystem, then you can drag and drop, but if you have a screenshot or something else copied to your clipboard it pastes right in)
In a previous life, I was the admin of a large computer network. One of the best features of the Cisco gear we used was the command "show tech-support". It spits out a huge text file with the entire configuration of the device, along with a number of diagnostic command outputs, error and operation logs, component temperatures, version info, etc.
The file could either be used in-place for diagnostics or sent to Cisco tech support for further analysis, sidestepping a lot of back-and-forth with the support people.
It occurred to me that it would not be that hard to achieve something similar, either implemented in firmware or else done in DWC. That file, uploaded to the forum (perhaps via an automated mechanism direct from DWC?) would provide a huge amount of troubleshooting data very easily.
Even better would be a way to unpack that data into a visualiser/validator tool that showed common issues, potential conflicts, firmware upgrade 'gotchas', etc. Again, this is something we had with Cisco where complex configurations led to difficult-to-spot and subtle issues. I appreciate that this is not trivial to implement but it wouldn't have to happen all at once and, once done, might actually cut down on the time spent troubleshooting, especially with 'new user'-type issues.
@peterwilli That error code means that DWS cannot get the file list from the requested path (even though it should have returned an HTTP error instead; I'll fix that). You could start a shell with the dsf user by running sudo -u dsf bash and then check if you can enter the mount point of the USB drive and list the files there. I suspect it's a permission problem.
I did my first print using your slicer version yesterday afternoon/evening.
The time estimate was spot on.
And, the print quality is vastly better than the old Cura slicer I use with my Overlord Pro and initially used for the Duet machine!
The item sides have no noticeable layer lines or ripples, just a really good result.
@t3p3tony I am working with gruna-studio to investigate the issue. To test some stuff I made a short script that does about 10 changes back and forth with some moves inbetween. This was confirmed to cause the issue as well. MoveTC10_test.gcode
To furter elaborate on the issue. Toolchanges seem to cause a growing y-offset, eventually leading to the toolchanger failing to pickup a tool and leaning prints. IIRC, a re-home of the axis resolves the issue. Also manually changing tools (selecting in DWC) many times does not seem to reproduce the issue.