What are your favorite ways to iterate on your changes?
I recently installed and commissioned a Duet WiFi on a 3D printer, and it went smoothly. I eventually want to contribute to firmware improvements and features, and so I'd like to learn about how you approach exercising and testing the changes you make day-to-day.
What do you do to make the edit-build-deploy-run-analyze workflow efficient for you?
You missed out the most important steps: "design" and "design review" come before "edit".
If you do design and design review as part of your iterative day-to-day work, I can see why you wouldn't want to answer the question, but I can't see why you wouldn't read and understand the question.
tekkydave last edited by
Thanks for trying. That link was my first link, and it doesn't mention anything relating to efficient workflows.
I read the front matter for these repos, and while the build instructions are the closest I've seen, they still don't make recommendations for low-effort iterative experimentation.
- RepRapFirmware boils down to "use Eclipse" once you've installed and configured the cross compiler and source.
- DuetWebControl boils down to "use
build.shand upload the tarballs"
When I start fixing the performance problems in DWC, I'll write a wiki page about it and we'll see if the ivory tower responds favorably.
@wireddown I think you may receive a more detailed response when David has finished up presenting at the TCT show which is currently on. Please show some patience.