Update your machine.xml with the latest from GitHub and it may fix the backlash issue. I faced the same (as have many others) and it was a misconfiguration on an axis I believe. I ended up scrapping the provided machine.xml in favor of a from scratch config that is ready for the second nozzle.
Thanks Mike! A couple of weeks ago I merged a whole mess of changes from the machine.xml on Github. The big change I saw today in Stephen's machine.xml is the "motion-control-type" was set to "ToolpathFeedRate" and has been switched to "ConstantAccelleration". That sure sounds related to the error I'm getting. I made the change, and my LumenPNP is behind me right now calibrating the X axis. It is probably doing it incorrectly (I forgot to hit apply when I changed the compensation method!), but it is going through a whole mess of motions, which is progress and super exciting! :)
@@patregan great! I've upgraded to the Marlin 2.1.x bug fix branch and adjusted default steps for X and Y to 80 (from 40) and microsteps to 16 (from 8) on the same. I was having issues with 0.01mm movements prior to updates and had a backlash of around 0.11mm. After the updates though I'm able to move around 0.005mm at a time.
@@atanisoftware That's interesting! That's right around where my X axis came in during compensation. OpenPNP implied that I may have done a bad job at calibrating my cameras, which is a definitely possibility! :)
@@patregan my Y axis was similar iirc. After updating the firmware with adjustments it is considerably faster, quieter and more accurate. Backlash also switched it's compensation mode (forget which now).
![MV วิถีชีวิตใต้ - ผา อัยย๊ะ [Official MV HD]](http://i.ytimg.com/vi/nODlkOUu9B0/mqdefault.jpg)
Update your machine.xml with the latest from GitHub and it may fix the backlash issue. I faced the same (as have many others) and it was a misconfiguration on an axis I believe.
I ended up scrapping the provided machine.xml in favor of a from scratch config that is ready for the second nozzle.
Thanks Mike! A couple of weeks ago I merged a whole mess of changes from the machine.xml on Github. The big change I saw today in Stephen's machine.xml is the "motion-control-type" was set to "ToolpathFeedRate" and has been switched to "ConstantAccelleration".
That sure sounds related to the error I'm getting. I made the change, and my LumenPNP is behind me right now calibrating the X axis. It is probably doing it incorrectly (I forgot to hit apply when I changed the compensation method!), but it is going through a whole mess of motions, which is progress and super exciting! :)
@@patregan great! I've upgraded to the Marlin 2.1.x bug fix branch and adjusted default steps for X and Y to 80 (from 40) and microsteps to 16 (from 8) on the same. I was having issues with 0.01mm movements prior to updates and had a backlash of around 0.11mm. After the updates though I'm able to move around 0.005mm at a time.
@@atanisoftware That's interesting! That's right around where my X axis came in during compensation. OpenPNP implied that I may have done a bad job at calibrating my cameras, which is a definitely possibility! :)
@@patregan my Y axis was similar iirc. After updating the firmware with adjustments it is considerably faster, quieter and more accurate. Backlash also switched it's compensation mode (forget which now).