@Vladimir_Lukashuk: For me it is a non-issue. With well placed strings all but the most extreme prints will be trapped. In that extremely rare situation you can cut the string and remove the part. This would obviously be less than optimal if you had to print a lot of large vases. In that situation, string on two sides will be sufficient to maintain the rigidity.
Now that I think about it, it would be nice to have 2" or 3" PVC columns (no cost) in the corners to regulate the distance between the plates. This will also allow me to remove 6 R8ZZ. This will also place the threaded rod in tension which will minimize any non-linearity present in the rod.
I think I like the PVC. It actually reduces the cost of the BOM by around $20. One side benefit is it gives you a place to run your wires to the top. As drawn it is 2" PVC which is actually 2.375" in diameter.
The bottom steppers mounts bug me for some reason. I feel like I am ignoring a more elegant solution. Any ideas?
@A2: I don't want to discourage but digging around in firmware code is almost a requirement for an experimental build such as this. I think you will find that the coordinate transformation code isn't that scary. For a example, look at the GDR code. If the math is a little inaccessible, I am sure someone in the community will not be able to control themselves. This is just too juicy of a math problem.
Now that I think about it, it would be nice to have 2" or 3" PVC columns (no cost) in the corners to regulate the distance between the plates. This will also allow me to remove 6 R8ZZ. This will also place the threaded rod in tension which will minimize any non-linearity present in the rod.
I think I like the PVC. It actually reduces the cost of the BOM by around $20. One side benefit is it gives you a place to run your wires to the top. As drawn it is 2" PVC which is actually 2.375" in diameter.
The bottom steppers mounts bug me for some reason. I feel like I am ignoring a more elegant solution. Any ideas?
@A2: I don't want to discourage but digging around in firmware code is almost a requirement for an experimental build such as this. I think you will find that the coordinate transformation code isn't that scary. For a example, look at the GDR code. If the math is a little inaccessible, I am sure someone in the community will not be able to control themselves. This is just too juicy of a math problem.