Guide for posting requests for help
-
Please help everyone to help you by including the following information in a post for assistance with Firmware, Hardware etc on the forum.
- Please be civil, we are trying to help!
- Mention which versions of RepRapFirmware, Webserver (if applicable) and Duet Web Control you are using.
- Mention which hardware you are using (Duet 2 Wifi, Ethernet, Smart Effector, Duex5 etc) and what architecture your printer has (Cartesian, CoreXY, Delta etc.). Also if it is an issue with a specific piece of hardware post in the relevant forum.
- Provide links to your config.g (and other .g files like homeing, bed etc, if they are relavent to the issue). These files are best attached to the forum post using the "upload file" button:
- If it is a question about specific hardware other than Duet 3d (e.g. a specific stepper motor) provide a link to the datasheet.
- If it is an issue since you updated the firmware, please make sure you have read the "whats new" update for all the releases in between your old and new firmware versions.
- Please have a search for other threads where people have had the same/similar issues. Do note however that RepRapFirmware gets updated frequently so if its an old thread treat with caution.
- If possible describe exactly how to recreate the problem.
- some times uploading a screen shot of the issue or a picture of how things are connected helps if that applies to your issue.
- If you are getting an error message, include the exact error message in your post.
- Keep your issue contained to a single thread, that way all your information is in one place and it's easier to track.
- When that issue is resolved, if you have another unrelated issue, start a new thread for it.
- When your issue gets resolved mark it solved for others to find in the future.
-
Please only reply to this post with other constructive things forum users should do before asking for help.
-
If possible describe exactly how to recreate the problem. If they can see it happen a quick fix is much more likely.
-
Also please state what architecture your printer has (Cartesian, CoreXY, Delta etc.) if it may be relevant.
-
Sometimes a photo says 1000 words and doesn't require translation.
-
@t3p3tony said in Guide for posting requests for help:
Please only reply to this post with other constructive things forum users should do before asking for help.
- Be civil
-
@keyz182 said in Guide for posting requests for help:
@t3p3tony said in Guide for posting requests for help:
Please only reply to this post with other constructive things forum users should do before asking for help.
- Be civil
-
If you are getting an error message, include the exact error message in your post.
-
Try and keep your issue contained to a single thread, that way all your information is in one place and it's easier to track. If your issue gets resolved mark it solved for others to find in the future.
-
...and when that issue is resolved, if you have another unrelated issue, start a new thread for it.
-
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.
adavidm
