Baby step during a long linear move? Baby step other Axes?



  • You could use manual probing and manually create an actual heightmap. You might not want to do 440 points that way, but maybe a dozen wouldn' t be too bad.



  • Just another update ... after loading the heightmap with G29 S1, the printer seems to be frozen if I try any X or Y movement. But with some experimentation, it looks like it is just taking infinitely long to execute the move command.

    I did:
    G91
    G29 S1
    G1 X0.0001 ; (to move 0.1 microns)

    And the motor makes a weird humming noise). If I try just 1 micron, there is a periodic knocking noise. If 1mm, then no knocking. But I do hear the high pitched little noises that the stepper motors normally make when not moving, but it changes slightly every second or so as if it was moving extremely slow (where the high pitch noise changes pitch for each microstep. Not sure what is going on!



  • @phaedrux Yeah I think I'll have to do the manual probing as you suggested. Maybe 4 or 9 points.



  • @phaedrux I downloaded your heightmap.csv and was able to view it in DWC. The printer didn't freeze after loading it either. So I edited it with my data being careful with spaces and commas and number of decimal places. And it works! Thanks for sharing your file! Not sure what was wrong with mine. I had created the old non-working heightmap in Excel, and when I opened it in TextEdit, it appeared to have some extra commas after the header, so maybe that had something to do with it.

    Now to test to see if it will let me do the babystepping the way I wanted...



  • @jml said in Baby step during a long linear move? Baby step other Axes?:

    Just another update ... after loading the heightmap with G29 S1, the printer seems to be frozen if I try any X or Y movement. But with some experimentation, it looks like it is just taking infinitely long to execute the move command.

    When you do a G1 command WITHOUT an F parameter the G1 command moves at the speed of the last F parameter the firmware processed.

    So...
    G1 X10 F100
    then...
    G1 X20

    both move at F100

    So I'm guessing that somewhere you had a G1 command with a very small F value.

    Unless you are sure it is not moving at all. The slowest speed is hard to see.

    Frederick



  • @fcwilt Not sure what was going on when it was moving super slow (or not moving at all). I think it was actually not moving at all after some tests. But it got solved by creating a better heightmap.csv file without the extra commas that excel added for some reason.



  • And I was able to test it, and the baby stepping is as responsive as I would like - it will now respond quickly after pressing the baby stepping buttons. Hooray!

    Thanks for all the input 🙂



  • Glad you got it working.


  • administrators

    I'll consider adding a "first layer segmentation" option in a future firmware revision, so that you won't have to create an empty height map - if babystepping is only needed during the first layer.

    If you still have a height map file that crash the firmware, please post it so that I can fix that.



  • @t3p3tony another use case would be on belt printers, from my research and current project the Y-axis is used to adjust height from build surface. I've also opened a topic under firmware wishlist..


 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.