@T3P3Tony I think that by increasing the stability and rigidity of the structure I can achieve greater precision, less vibrations and better print quality, as well as better weight distribution. Can you tell me how I can implement this kinematics?
@Mr-Crispin he has done the kinematics calculations in his gcode generation program. so in this case the Duet does not "know" its multi axis printing. @JoergS5 has done some work in implementing variations of robot kinematics that run on the Duet boards themselves.
@Carter3DP you will need to reverse the direction of the homing moves for the proximal and distal motors, and switch the proximal and distal homing switches over from low to high end or vice versa.
@fromwastetowind I think this is an 'inverse' Polar printer, and it is irrelevant to the firmware if it is the crane that rotates or the bed. The nozzle just needs to travel along a line drawn between the centre and the circumference, ie along a radius line.
Sorry I forgot you were working with external drivers here.
As this thread has grown to nearly 100 posts and has involved several issues, I think it may be best if you can create a new thread with a detailed restatement of your current issue. Please include the basic details of your setup and the hardware used. Please include your config.g as well.
thanks to Modix3D support for idea to check M600 command.
Good catch! Sometimes the simplest answer is the best. Often we look for more complicated reasons! The 'error' (not an error, it's doing what it's told to do) message should have been the clue...
@__noemy__ send M115 to see if it reports the DueX5. If the response doesn't mention it then check that the ribbon cable is connected properly and that power is applied to the DueX5.
@Mafco77 thank you for using the kinematics and nice to hear that you're using it successful.
I probably have implemented the homing of CoreXY wrong somewhere. I'll check it. But please be patient for solving this, it's not the highest priority and you have a workaround.
@trulm to do that you have to start the macro (very rudementary explained) with splitting the z steppers into individual axis. Then assign the movement you want on each of those three axis, then when the movement is done you make each of the axis return to the starting point and combine all the threesteppers back into being Z. And "hide" the two axis you created in step 1.
