I'd also be happy to test for you! A backlash system and native 4D/5D firmware compatibility would also be very nice. This anti-backlash greatly improves my print-quality and reliability (prevents congestions in the extruder because it extrudes in an area which is already filled).
For other missing features that I've added myself, you can look here:
[objects.reprap.org]
Actually, right now it does a bit more than is documented. I've made some acceleration code for non-accelerating firmware. It divides up segments of rapid travels into portions (multiple G-code lines) with different speeds so that it accelerates. Right now, about 70% of my objects have mistakes because an axis misses a few steps somewhere. I've replaced stepper drivers, tried all sorts of feedrates (an no, slower is not always better). With acceleration I hope to remove this problem and also create thinner/less strings from head travels.
Right now I'm e-mailing gcode to people that can't run my PHP conversion program properly. So, I guess the features are appreciated.
For other missing features that I've added myself, you can look here:
[objects.reprap.org]
Actually, right now it does a bit more than is documented. I've made some acceleration code for non-accelerating firmware. It divides up segments of rapid travels into portions (multiple G-code lines) with different speeds so that it accelerates. Right now, about 70% of my objects have mistakes because an axis misses a few steps somewhere. I've replaced stepper drivers, tried all sorts of feedrates (an no, slower is not always better). With acceleration I hope to remove this problem and also create thinner/less strings from head travels.
Right now I'm e-mailing gcode to people that can't run my PHP conversion program properly. So, I guess the features are appreciated.