Topics created by Jasperg

@dc42 OK great thanks! I must have made an error, I'll try again.

@Jasperg I hope you'll find the solution for your question. It may be a combination of all the topics mentioned.

It helped me a lot the last three years to look into the RRF code to understand it. This is all open source, so it is also changeable by oneself, so there is freedom to implement own ideas. For example, I added some logging to the console here and there (and recompilation) to understand the code better, especially what the different variables mean. Maybe you want to go a similar route like me.

@dc42 what I did is set the length of the move to 180 and put a very high rate. With what i think are exactly the same settings on each axis. Then gradually up the acceleration that I set in the config file on each new test, originally I was doing this to test at what point the motor stalls, as I wanted to see how effective using 2 motors driving the same belt was at increasing power and speed but at one point the x and y axis stop accelerating any faster, yet the z will continue to do so. I can't find anything that is set any differently between each axis at the moment.

@jasperg that kinematics isn't currently supported in RRF but it could be added. There is a brief overview of how to add new kinematics at https://github.com/Duet3D/RepRapFirmware/wiki/Adding-New-Kinematics. It would probably be possible to implement it as segment-free kinematics.

@o_lampe thank you so much for the tips! I am going try this weekend. With our your suggestions I think I would have given up.

@jasperg great, glad you got it sorted.

Ian